hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
7.1.1 DHCP support by the UE
|
The User Equipment (UE) shall behave as an RFC 2131 [10] compliant DHCP v4 client. The UE shall be able to send DHCP messages that support the following options: - Option 55 "Parameter List" RFC 2132 [11]. - Option 60 "Vendor Class Identifier" RFC 2132 [11]. - Option 61 "Client Identifier" RFC 2132 [11]. Option 55 shall be set to request the following options: 6, 43, 66, 67, 120 and 123. A UE supporting the autoconfiguration protocol defined by the DSL forum shall identity itself by including the string "dslforum.org" anywhere in the Vendor Class Identifier option (60). This will ensure that the name of the ACS will be sent back in the DHCP offer in the Vendor Specific Information option (43), as described in DSL Forum TR69 [9]. It is also recommended that the UE send the following options: - Option 12 "Host Name" RFC 2132 [11]. - Option 77 "User Class" RFC 3004 [12]. The UE shall be able to receive and process DHCP messages that include the following options: - Option 6 "Domain Server" RFC 2132 [11]. - Option 15 "Domain Name" RFC 2132 [11]. - Option 43 "Vendor Specific" RFC 2132 [11]. - Option 51 "IP Address Lease Time" RFC 2132 [11]. - Option 58 "Timer T1" RFC 2132 [11]. - Option 59 "Timer T2" RFC 2132 [11]. - Option 120 "SIP Servers DHCP Option" RFC 3361 [16] Support of the following options is also recommended: - Option 1 "Subnet Mask" RFC 2132 [11]. - Option 3 "Router" RFC 2132 [11]. - Option 5 "Name Server" RFC 2132 [11]. - Option 33 "Static Route" RFC 2132 [11]. - Option 42 ""NTP servers" RFC 2132 [11]. - Option 66 "TFTP Server Name" RFC 2132 [11]. - Option 67 "Bootfile-Name" RFC 2132 [11]. ETSI ETSI TS 183 019 V1.1.1 (2005-12) 15 - Option 72 "WWW Server" - Option 123 "GeoConf Option" RFC 3825 [13]. - Option 114 "URL option" - Option TBD "PANA Authentication Agent" - Option TBD "Civic Location"
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
7.1.2 DHCP support by the ARF
|
The Access Relay Function (ARF) shall behave as an RFC 2131 [10] compliant DHCP v4 Relay Agent. It shall support the DHCP Relay Agent Information option (Option 82) and insert the following sub-options: - Sub-option 1 "Agent Circuit ID" RFC 3046 [14]. - Sub-option 2 "Agent Remote ID" RFC 3046 [14]. - Sub-option 6 "Subscriber-ID" RFC 3993 [15]. The following encoding is recommended for the Agent Circuit ID: AgentCircuit-ID = AccessNodeId AggregationType slot/port ":" Layer2Id AccessNodeId = NAME AggregationType = "atm" | "eth" Slot = *DIGIT Port = *DIGIT Layer2Id = ATM_Id | Ethernet_Id ATM_Id = vpi "." vci Ethernet_Id = vlan_tag vpi = *DIGIT ; VP Identifier vci = *DIGIT ; VC Identifier vlan_tag = DIGIT ; VLAN tag DIGIT = %x30-39 ; 0-9 ALPHA = %x41-5A / %x61-7A ; A-Z / a-z NAME = ALPHA *63(ALPHA / DIGIT / "_") The Agent Remote ID shall be in the form of an ASCII string that identifies the subscriber line with regards to the Network Attachment Subsystem. The Subscriber ID shall be in the form of an ASCII string that identifies the subscriber with regards to the Network Attachment Subsystem, independently from the access technology used.
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
7.1.3 DHCP support by the NACF
|
The Network Access Configuration Function (NACF) shall behave as an RFC 2131 [10] compliant DHCP v4 server. The NACF shall support all options defined in RFC 2132 [11] and RFC 3004 [12], RFC 3046 [14], RFC 3361 [16], RFC 3825 [13] and RFC 3993 [15]. The NACF shall insert the following options in a DHCP Offer: - Option 6 "Domain Server": The domain name server option specifies a list of Domain Name System name servers available to the client. - Option 15 "Domain Name": specifies the domain name that client should use when resolving hostnames via the Domain Name System. - Option 51 "IP Address Lease Time": It is recommended that a long lease time be used. - Option 58 "Timer T1": This timer should be set to a value that is less than the default value described in RCF 2131. - Option 59 "Timer T2": This timer should be set to a value that is less than the default value described in RCF 2131. ETSI ETSI TS 183 019 V1.1.1 (2005-12) 16 - Option 120 "SIP Server": This option shall contain the P-CSCF identity. The SIP server DHCP option carries either a 32-bit (binary) IPv4 address or, preferably, a DNS name to be used by the SIP client to locate a SIP server. The NACF may also insert the following options in a DHCP Offer: - Option 42 "Network Time Protocol Servers". - Option 43 "Vendor Specific": Vendor Specific Information option used by clients and servers to exchange vendor- specific information. If a vendor potentially may encode more than one item of information using "Encapsulated vendor-specific options" (e.g. name of the CPECF). NOTE: If the CPECF is a TR69, the DHCP server shall include the two encapsulated Vendor-Specific options (URL of ACS, Provisioning Code) defined in TR69. - Option 66 "TFTP Server Name": TFTP server address. - Option 67 "Bootfile Name": Identifies a bootfile to be retrieved by the user equipment. - Option 72 "WWW server": The WWW server option specifies a list of WWW available to the client. - Option 123 "GeoConf Option": Coordinate-based Location Configuration Information option provides the coordinate-based geographic location of the client. - Option 114 "URL option" : May be used for authentication - Option TBD "PANA Authentication Agent" the PANA Authentication Agent Option carries either a 32-bit (binary) IPv4 address list or, preferably, a domain name list to be used by the PANA client to locate a PANA authentication Agent - Option TBD "Civic Location": Dynamic Host Configuration Protocol option containing the civic location of the client or the DHCP server.
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
7.2 Access network based on IPv6
|
The UE, the ARF and the NACF shall behave as an RFC 3315 [17] compliant DHCPv6 client, DHCPv6 relay agent and DHCP Server (respectively). All options defined in RFC 3315 [17] shall be supported. The following options shall also be supported: - DHCPv6 options 21 and 22 for SIP server. - OPTION_SIP_SERVER_D (21) defined in RFC 3319 [18]. - OPTION_SIP_SERVER_A (21) defined in RFC 3319 [18]. - OPTION_DNS_SERVERS (23) defined in RFC 3646 [19]. The ARF shall insert the following information: - OPTION_REMOTE_ID (tbd) defined in draft-ietf-dhc-dhcpv6-remoteid-00.txt [20]. - OPTION_SUBSCRIBER_ID (tbd) defined in draft-ietf-dhc-dhcpv6-subid-00.txt [21].
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
8 Applicability to WLAN access networks
|
This certification of WLAN devices by the Wi-Fi Alliance may only be applicable to WLAN devices that are deployed by a service provider, and may not be necessary or enforceable for devices that may be deployed in the customer premises - for example, a wireless AP that is connected to a DSL line coming in to a home. ETSI ETSI TS 183 019 V1.1.1 (2005-12) 17
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
8.1 Requirements of the WLAN access network
|
1) The WLAN device in the WLAN access network shall be Wi-Fi Alliance certified, and: a) The WLAN device shall support either 802.11b or 802.11g. 2) The access network shall support WPA/802.1X. a) The SSID used for WPA/802.1X in the beacon shall be broadcast by the WLAN device in strict accordance with the 802.11 specification. The beacon shall contain the WPA Information Element. b) The access network shall support EAPOL messages, and shall be able to transport at a minimum EAP messages of the EAP method types defined in clause 8.2. c) The access network shall provide a DHCP service, with assignment of wireless station IP address, netmask, gateway IP address and DNS server address. Specific requirements are described in clause 7 of the present document. d) The access network shall support login with username (NAI) as defined in RFC 2486bis [6]. 3) The access network may support WPA2. 4) The access network may also support UAM. In this case, the access network shall meet the following requirements simultaneously. a) The SSID used for WPA in the beacon shall be broadcast by the WLAN device in strict accordance with the 802.11 specification. The beacon shall contain the WPA Information Element. b) The SSID used for open authentication in the beacon shall be broadcast by the AP in strict accordance with the 802.11 specification. The beacon shall indicate open authentication by not requiring WEP or 802.1X. 5) If the access network supports UAM method of authentication, it shall also meet the following requirements: a) It may provide a DHCP service, with assignment of wireless station IP address, netmask, gateway IP address and DNS server address. b) It may support redirection of HTTP requests to a login webpage while in unauthenticated mode. c) It shall support login with username (NAI) as defined in RFC 2486bis [6]. d) It shall secure authentication of credentials over HTTPS. 6) The access network may support intermediary network discovery and selection to allow a wireless station to select an intermediary when in a visited network. a) If a user's service provider does not have a service agreement with a visited network provider, it may still be possible to obtain service via a roaming intermediary or exchange. If more than one intermediary is available, the choice of intermediary may affect charges, service, QoS, and other issues. In this case, it is important for the user to have an opportunity to influence that choice. b) Work in this area is being done in the IETF. Work items that should be tracked include the NAI format standard defined by RFC 2486bis [6], and the EAP Network Discovery proposal (draft-adrangi-eap-network-discovery-12 [4]).
|
e142e055458ad4dd142e50ecfb0407b8
|
183 019
|
8.2 Requirements of the chosen EAP method
|
1) The EAP method used shall support: a) Mutual authentication. b) Key-derivation. 2) TS 124 234 [2], clause 6, shall be supported when EAP-SIM and EAP-AKA are used by the WLAN UE and the WLAN access network. ETSI ETSI TS 183 019 V1.1.1 (2005-12) 18 NOTE: Requirement 1 of clause 6.5 is satisfied by the following EAP methods. It should be noted that the list below is not restrictive. EAP-SIM. PEAP/EAP-MSCHAPv2. TTLS/MS-CHAPv2. EAP-AKA. EAP-TLS. ETSI ETSI TS 183 019 V1.1.1 (2005-12) 19 Annex A (informative): Requirements of the WLAN station A.1 Requirements of the WLAN station 1) The wireless interface on the WLAN station shall be Wi-Fi Alliance certified, and: a) The WLAN station shall support either 802.11b or 802.11g. 2) The WLAN station shall be able to operate in Wi-Fi Protected Access (WPA)/802.1X mode, and: b) WLAN authentication signalling shall be based on Extensible Authentication Protocol (EAP) as specified in RFC 3748 [5]. The EAP method chosen shall follow the EAP method requirements noted in clause 8.2. c) The wireless station shall use an NAI as defined in RFC 2486bis [6] and TS 124 234 [2]. 3) The wireless station may operate in UAM mode. d) The wireless station shall be able to successfully associate to the open SSID and be 802.11 authenticated (as per 802.11-1999 specification). 4) The wireless station shall be able to differentiate between multiple BSSID capability information elements, which have the same SSID name. 5) The wireless station may operate in WPA2 mode. 6) The wireless station may support intermediary network discovery and selection to allow a wireless station to select an intermediary when in a visited network. e) If a user's service provider does not have a service agreement with a visited network provider, it may still be possible to obtain service via a roaming intermediary or exchange. If more than one intermediary is available, the choice of intermediary may affect charges, service, QoS, and other issues. In this case, it is important for the user to have an opportunity to influence that choice. f) Work in this area is being done in the IETF. Work items that should be tracked include the NAI format standard defined by RFC 2486bis [6], and the EAP Network Discovery proposal (draft-adrangi-eap-network-discovery-12 [4]). ETSI ETSI TS 183 019 V1.1.1 (2005-12) 20 Annex B (informative): Bibliography • ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". ETSI ETSI TS 183 019 V1.1.1 (2005-12) 21 History Document history V1.1.1 December 2005 Publication
|
6e795bd50d66978f3253adc5068d22be
|
183 031
|
1 Scope
|
The present document provides the necessary extensions and modifications to 3GPP TS 29.333 [1] required for use in a TISPAN NGN. 3GPP TS 29.333 [1] describes the protocol to be used on the Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) interface (Mp interface). This specification defines a profile of the Gateway Control Protocol (H.248.1), for controlling Multimedia Resource Function Processor supporting in-band user interaction, conferencing and transcoding for multimedia-services.
|
6e795bd50d66978f3253adc5068d22be
|
183 031
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
6e795bd50d66978f3253adc5068d22be
|
183 031
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] 3GPP TS 29.333: "Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp Interface - Stage 3; (Release 7)". [2] ITU-T Recommendation H.imp 248: "Implementors' Guide for the H.248 Sub-series of Recommendations ("Media Gateway Control Protocol")". [3] IETF RFC 2833: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". [4] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [5] IETF RFC 3555: "MIME Type Registration of RTP Payload Formats". [6] IETF RFC 3389: "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)". [7] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". ETSI ETSI TS 183 031 V2.0.0 (2008-02) 6 [8] ITU-T Recommendation G.711 Appendix I: "A high quality low-complexity algorithm for packet loss concealment with G.711". [9] ITU-T Recommendation G.711 Appendix II: "A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems". [10] ITU-T Recommendation H.248.45: "Gateway control protocol: MGC information package". [11] ETSI ES 201 235-3: "Access and Terminals (AT); Specification of Dual-Tone Multi-Frequency (DTMF) Transmitters and Receivers; Part 3: Receivers".
|
6e795bd50d66978f3253adc5068d22be
|
183 031
|
3 Definitions, symbols and abbreviations
| |
6e795bd50d66978f3253adc5068d22be
|
183 031
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TS 29.333 [1] apply.
|
6e795bd50d66978f3253adc5068d22be
|
183 031
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TS 29.333 [1] and the following apply: NGN Next Generation Network Endorsement notice The present document endorses 3GPP TS 29.333 [1], the contents of which apply together with the exception of clause 1 and the modifications being covered herein. Global modifications to 3GPP TS 29.333 Throughout the text of 3GPP TS 29.333 [1] Replace "MGW" with "MRFP" Replace references as shown in table 1. Table 1 Reference(s) in 3GPP TS 29.333 [1] Replaced reference(s) 1 3GPP TS 23.228: IP Multimedia Subsystem (IMS); Stage 2. ETSI TS 182 006 2 3GPP TS 23.002: Network architecture. ETSI ES 282 007 25 3GPP TS 23.333: "Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures Descriptions". Not Applicable to TISPAN NGN. 26 ITU-T Recommendation H.248.9a1 (03/2007), "Gateway control protocol: Advanced media server package (draft work in progress)". ITU-T Recommendation H.248.9 Amendment 1 (08/2007), "Gateway control protocol: Advanced media server packages - Amendment 1: ASR, TTS and Multimedia enhancements". ETSI ETSI TS 183 031 V2.0.0 (2008-02) 7 5.1 Profile Identification Modify table 5.1.1 as follows: Table 5.1.1: Profile Identification Profile name: MRF or ETSIprof_MediaServer Version: 1 5.3 Gateway Control Protocol Version Modify the text as follows: Version 2 shall be the minimum version supported. Support of this version implies conformance to ITU-T Recommendation H.248 Version 2 [3] and Corrigendum 1, and implementation of the corrections available in the latest version of the H.248 Implementors' Guide [2]. 5.7.1 Stream Descriptor Add the following table: Table 5.7.1.1.2A: Local control properties Properties associated with Local Control Descriptor supported Yes If yes Property IDs Reported Termination type Stream type MGCinfo/db RTP Any nt/jit RTP Any aassm/* RTP Audio/Video aasrec/* RTP Audio/Video vcp/level RTP Audio vlmp/mixlevel RTP Audio vlmp/nspeakmix RTP Audio mvlcp/mixpartnum RTP Audio mvlcp/vollevip RTP Audio 5.7.2 Events Descriptor Add the following three lines to table 5.7.2.1: Event ID Termination Type Stream Type vdp/* RTP Audio aasdc/* RTP Audio xdd/* RTP Audio Modify table 5.7.2.4 as follows: Table 5.7.2.4: Embedding in event Embedded events in an event descriptor: Yes Embedded signals in an event descriptor: Yes ETSI ETSI TS 183 031 V2.0.0 (2008-02) 8 5.7.4 Signals Descriptor Add the following three lines to table 5.7.4.1 Signal ID Termination Type Stream Type/ID aassm/* RTP Audio/Video indview/* RTP Any an/* RTP Audio/Video Modify table 5.7.4.5 as follows: Table 5.7.4.5: Notify completion Notify completion supported: Yes Signal ID Type of completion supported If yes cg/*, svrtn/*, xcg/*, an/*, int/*, biztn/*, conftn/* , tonegen/*, bcg/*, aasb/*, indview ALL Modify table 5.7.4.6 as follows: Table 5.7.4.6: RequestID Parameter RequestID Parameter Supported: Yes NOTE: When the event is provisioned in the media gateway, the Request Id is set to FFFFFFFF'H. Modify table 5.7.4.7 as follows: Table 5.7.4.7: Signals played simultaneously Signals played simultaneously: Yes If yes Signal Ids that can be played simultaneously: - 5.7.5 DigitMap Descriptor Modify table 5.7.5.1 as follows: Table 5.7.5.1: DigitMap Descriptor DigitMaps supported: Yes DigitMap Name Structure Timers If yes 5.8.8 ServiceChange Modify table 5.8.8 as follows: Table 5.8.8.4: Service Change Delay ServiceChangeDelay used: Yes If yes Valid time period: - ETSI ETSI TS 183 031 V2.0.0 (2008-02) 9 5.9 Generic Command Syntax and Encoding Replace table 5.9.1 as follows: Table 5.9.1: Encoding Supported Encodings: Text encoding shall be supported by both the MRFP and the MRFC. Both the long and short form of text encoding shall be supported at the receiving side. 5.14.1 Mandatory Packages Add the following line to table 5.14.1: RTP Package (ITU-T Recommendation H.248.1 [3]) rtp 1 5.14.2 Optional Packages Remove the following line to table 5.14.2 RTP Package (H.248.1, [3]) rtp 1 Add the following lines to table 5.14.2 Extended DTMF Detection (H.248.16 [10]) xdd 1 Support is mandatory if DTMF collection is supported and the AAS Digit Collection package is not supported, optional otherwise. AAS Digit collection (H.248.9 [6]) aasdc 2 Support is mandatory if ADVANCED_UI, optional otherwise. Floor Control (H.248.19 [11]) fcp 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. View (H.248.19 [11]) indview 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Volume Control (H.248.19 [11]) vcp 1 Support is mandatory if ADVANCED_CONFERENCING is supported, optional otherwise. Volume Detection (H.248.19 [11]) vdt 1 Support is mandatory if ADVANCED_CONFERENCING is supported, optional otherwise. Volume Level Mixing (H.248.19 [11]) vlm 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Mixing Volume Level Control (H.248.19 [11]) mvlc 1 Support is mandatory if ADVANCED_CONFERENCING is supported, not required otherwise. Inactivity Timer (H.248.14 [9]) it 1 Support is mandatory if UDP transport is enabled for H.248 messages. MGC Information (H.248.45 see note) MGCInfo 1 This package may be supported as an operator option. For this profile the information string shall be limited to 32 octets in length. NOTE: See [10] in TS 183 031. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 10 5.14.3 Package Usage Information Clause 5.14.3 of [1] applies with the following additions: 5.14.3.26A Extended DTMF detection package Table 5.14.3.26a: Package usage information for extended DTMF detection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command DTMF Digits (see note) M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Extended Digit Map Completion M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value Buffer Control M ALL 0 Extra Digit Disposition M ALL OFF Match Procedure M ALL base ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value digit string M ALL Not applicable termination method M ALL Not applicable Unmatched Event M ALL Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable NOTE: DTMF detection shall conform to ES 201 235-3 [11]. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 11 5.14.3.26B AAS digit collection package Table 5.14.3.26B: Package usage information for AAS digit collection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Play Collect M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Initial Prompt M ALL Not applicable Reprompt M ALL Not applicable Number of Digits Prompt M ALL Not applicable Successful announcement M ALL Not applicable Announcement Failure M ALL Not applicable Non Interruptable Play M ALL FALSE Keep digits M ALL FALSE Clear Digits Buffer M ALL FALSE Maximum Number of Attempts M ALL 1 Digit Map M ALL Not applicable Speed O ALL 0 Volume M ALL 0 Offset M ALL 0 Restart Key M ALL 0 Re-input key M ALL None Return Key M ALL None Iterations M ALL 1 Interval M ALL None End Input Key M ALL None Include End Input Key M ALL FALSE Voice Information M ALL dtmfonly Voice back M ALL novoiceback INPA Prompt timer M ALL None Events Mandatory/ Optional Used in command Audio Operation Failure M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Return Code M ALL Not applicable Play Collect Success M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Digits Collected M ALL Not applicable (see note) Number of attempts M ALL Not applicable Amount Played O ALL Not applicable ETSI ETSI TS 183 031 V2.0.0 (2008-02) 12 Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable NOTE: DTMF detection shall conform to ES 201 235-3 [11]. 5.14.3.26C Floor control package Table 5.14.3.26C: Package usage information for floor controlpackage Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Activate Floor Controller M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Not applicable Not applicable Not applicable Not applicable None Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26D View package Table 5.14.3.26D: Package usage information for view package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value Viewed by whom M ALL Not applicable Being Viewed Viewer Identity M ALL Not applicable M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value No Viewer None Events Mandatory/ Optional Used in command Not applicable Not applicable None Event Parameters Mandatory/ Optional Supported Values Provisioned Value ETSI ETSI TS 183 031 V2.0.0 (2008-02) 13 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26E Volume control package Table 5.14.3.26E: Package usage information for volume control package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Volume Level M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26F Volume detection package Table 5.14.3.26F: Package usage information for volume detection package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command M ADD, MODIFY, NOTIFY, AUDITVALUE, AUDITCAPABILITY Event Parameters Mandatory/ Optional Supported Values Provisioned Value Volume Threshold M ALL Not applicable Volume Activity Detection ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value ETSI ETSI TS 183 031 V2.0.0 (2008-02) 14 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value None Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26G Volume level mixing package Table 5.14.3.26G: Package usage information for volume level mixing package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Volume Mixing Level M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable N Speakers Mixing O ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.14.3.26H Mixing volume level control package Table 5.14.3.26H: Package usage information for mixing volume level control package Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Mix Participant Number M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Volume Level Input to Mix M ADD, MODIFY, AUDITVALUE, AUDITCAPABILITY ALL Not applicable Signals Mandatory/ Optional Used in command Duration Provisioned Value Not applicable Not applicable Not applicable Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value None Not applicable Not applicable Not applicable Not applicable ETSI ETSI TS 183 031 V2.0.0 (2008-02) 15 Properties Mandatory/ Optional Used in command Supported Values Provisioned Value Events Mandatory/ Optional Used in command Not applicable Not applicable Event Parameters Mandatory/ Optional Supported Values Provisioned Value Not applicable Not applicable Not applicable Not applicable ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value None Not applicable Not applicable Not applicable Not applicable Statistics Mandatory/ Optional Used in command Supported Values None Not applicable Not applicable Not applicable Error Codes Mandatory/Optional None Not applicable 5.17 Procedures Replace the contents of clause 5.17 with the contents of annex ZB of the present document. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 16 Annex ZA (normative): MRFP Functional requirements Support of the packages identified in the profile definition implies support of the underlying functionality. This annex identifies additional functional requirements that media resource function processors conforming to the present document shall comply with: • Media Resource Function Processors (MRFP) shall support IPv4 and may support IPv6. • Media Resource Function Processors (MRFP) shall support G.711 A-law voice codec and may support other codecs. Media Resource Function Processors supporting transcoding are expected to support a wide range of well-known codecs. The list of codecs is outside the scope of the present document. • Media Resource Function Processors (MRFP) shall support the procedures defined in RFC 2833 [3] to generate, detect and forward DTMF digits. DTMF shall be identified by name (see mode "Named Telephone Events" in clause 3 of RFC 2833 [3]), as opposed to their waveform properties. • All properties of tones requested by the MRFC shall be provisioned in the MRFP. The MRFC is not required to send the physical characteristics of tones to Media Resource Function Processors (MRFP). ETSI ETSI TS 183 031 V2.0.0 (2008-02) 17 Annex ZB (normative): Procedures ZB.1 General procedures Media Resource Function Processors shall discard packets with RTP payload types (PT) that do not match the Local Descriptor contents. NOTE: Besides an incorrect RTP PT field might be also other reasons for discarding packets (invalid SSRC field, invalid CRC, etc.). When sending packets from a termination, Media Resource Function Processors shall use the address and port in the Local Descriptor as a source address and port. ZB.2 Use of voice codecs ZB.2.1 Comfort noise insertion and silence suppression for voice codecs If a codec has built-in support for silence suppression and comfort noise insertion, the activation or deactivation of these features shall be indicated using the a= line according to RFC 3551 [4] and RFC 3555 [5]. If the selected codec does not have built in support for silence suppression and Comfort Noise (CN) insertion, the CN payload code [6] may be included in the media description. E.g. for ITU-T Recommendation G.711 [7], A-Law: v= 0 c= IN <address type> <connection address> m = audio <port number> RTP/AVP 8 13 a= ptime: 10 If the CN payload is included in the Local Descriptor, the MRFP shall be prepared to receive CN packets during silence periods. This action also corresponds to an implicit enabling of the silence suppression mode in receiving direction. If the CN payload is included in the Remote Descriptor, the MRFP shall send CN packets during silence periods. This action corresponds to an implicit enabling of the silence suppression mode in sending direction. Comfort noise generation, voice activity detection and discontinuous transmission algorithms are outside the scope of the present document. ZB.2.2 DTMF transmission When a G.711 codec is used, Media Resource Function Processors shall be able to generate, detect and forward DTMF tones inband. When other codecs are used, the MRFC should request the use of the procedures defined in RFC 2833 [3] to send and receive DTMF tones. • If the Local Descriptor sent by the MRFC includes the support for RFC 2833 [3], Media Resource Function Processors (MRFP) shall be prepared to receive and detect DTMF tones in the form of named events. • If the Remote Descriptor indicates that RFC 2833 [3] is supported, Media Resource Function Processors (MRFP) shall be prepared to relay in the form of named events, any DTMF tone that may be received from other ephemeral terminations. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 18 • Media Gateways supporting conferencing or transcoding shall support transcoding between in-band DTMF and named events defined RFC 2833 [3], based on the contents of the Local and Remote descriptors of the involved terminations. A Dynamic Payload type shall be used to indicate support of RFC 2833 [3] for DTMF relay. EXAMPLE: v= 0 c= IN <address type> <connection address> m= audio <port number> RTP/AVP 18 110 a= ptime: 10 a= rtpmap: 110 telephone-event/8000 a= fmtp: 110 0-15 ZB.2.3 Support of G.711 variants ZB.2.3.1 G.711 Encoding law Media Resource Function Processors conforming to the present document are required to support G.711 A-Law and may also support μ-Law in order to avoid call failure or transcoding in case the remote entity supports μ-Law only. How and where to perform transcoding in IP networks in case both terminals/gateways do not support the same variant is outside the scope of this profile. ZB.2.3.2 G.711 packet loss concealment G.711-over-IP may be operated with or without error loss concealment. Typically is that decision dependent on the IP packet loss rate conditions. G.711 error loss concealment is based on RTP packet granularity, therefore called as Packet Loss Concealment (PLC). ITU-T Recommendation G.711 Appendix I [8] provides a framework for G.711 PLC mode. ZB.2.3.3 G.711 silence suppression mode G.711-over-IP may be operated with or without silence suppression. In case of silence suppression, comfort noise generation shall be based on ITU-T Recommendation G.711 Appendix II [9]. These features may be enabled/disabled on a per session basis, using the procedure described in clause ZB.4. ZB.3 Procedures for basic user interaction User Interaction procedures are applied to the ephemeral termination representing the media flow to/from the user involved in the interaction procedure. The ephemeral termination may already be in a context or may have to be created in a new context. Signals representing tones and announcements are applied to this termination and played towards the exterior of the context. Events representing DTMF digits are detected on this termination. ZB.4 Procedures for advanced user interaction User Interaction procedures are applied to the ephemeral termination representing the media flow to/from the user involved in the interaction procedure. The ephemeral termination may already be in a context or may have to be created in a new context. Signals representing tones and announcements are applied to this termination and played towards the exterior of the context. Events representing DTMF digits or recognized speech segments are detected on this termination. Voice-messaging services are implemented by applying the playrec signal from the AAS Recording package and detecting related event on this termination. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 19 ZB.5 Procedures for conferencing Conference services are implemented by creating H.248 contexts with the appropriate number of terminations using native H.248 mixing and transcoding capabilities. Each conference participant is represented by an ephemeral termination. Floor control procedures are implemented according to the procedures described in H.248.19 (reference [11] in 3GPP TS 29.333). ZB.6 Procedures for transcoding The MRFP may be required to perform transcoding in the context of a conference setup or in the context of basic two party calls. This clause describes the procedures for controlling transcoding in case of a two party call. Procedures for controlling transcoding in conferences are described in clause ZB.5. NOTE: Media Transcoding is performed by the MRFP under the control an MRFC. The criteria that trigger the insertion of an MRFC in the SIP signalling path is outside the scope of the present document. On receipt of a transcoding request for a two-party session between A and B, the MRCF shall request the MRFP to create a context with one ephemeral termination representing the A party (Ta) and one ephemeral termination representing the B party (Tb). Remote and Local Descriptors shall be populated as follows: • The Remote Descriptor for termination Ta shall be set according to the SDP Offer initially received from the A party. • The Remote Descriptor for termination Tb shall be set according to the SDP Answer received from the B party. • The media format in the Local Descriptor for termination Ta shall be set according to the SDP Offer initially received from the A party. The IP address and port shall be wildcarded. • The media format in the Local Descriptor for termination Tb shall be set according to the SDP Answer received from the B party. The IP address and port shall be wildcarded. The value of the Local Descriptor returned by the MRFP for the termination Ta shall be sent as an SDP Answer to the A party (via the S-CSCF/AS). The value of the Local Descriptor returned by the MRFP for the termination Tb shall be sent as a new SDP Offer to the B party (via the S-CSCF/AS). The MRFC is responsible for sending the SDP information in SIP messages that are compatible with the state of the SIP dialogue. ETSI ETSI TS 183 031 V2.0.0 (2008-02) 20 History Document history V2.0.0 Febuary 2008 Publication
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
1 Scope
|
The present document specifies the stage three (protocol description) of the Explicit Communication Transfer (ECT) simulation service, based on stage one and two of the ISDN ECT supplementary service.
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] ETSI TS 124 429: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); ECT (3GPP TS 24.429 Release 7)". ETSI ETSI TS 183 029 V1.4.0 (2008-06) 6
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
3 Definitions and abbreviations
| |
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 429 [10] apply:
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 429 [10] apply:
|
bd34fa72f1340d2659f6c02dcc9e311c
|
183 029
|
4 Explicit Communication Transfer (ECT)
|
The provisions of the present document are contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 9 Annex C (informative): Example charging model Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 10 Annex D (informative): Bibliography Information is contained in TS 124 429 [10]. ETSI ETSI TS 183 029 V1.4.0 (2008-06) 11 History Document history V1.1.1 April 2006 Publication V1.2.1 April 2007 Publication V1.3.2 October 2007 Publication V1.4.0 June 2008 Publication
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Malicious Call Communication Identification (MCID) service.
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 6 [12] ETSI TS 124 516: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification (3GPP TS 24.516 Release 8)".
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
3 Definitions and abbreviations
| |
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 516 [12] apply.
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 516 [12] apply.
|
50752ebe4c950afe359a9d1527e5fa13
|
183 016
|
4 Malicious Communication Identification (MCID)
|
The provisions of the present document are contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 9 Annex C (informative): Change history Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 10 Annex D (informative): Bibliography Information is contained in TS 124 516 [12]. ETSI ETSI TS 183 016 V2.6.0 (2008-06) 11 History Document history V2.5.0 July 2007 Publication V2.6.0 June 2008 Publication
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Communication Waiting (CW) service.
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 124 615: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification; (Release 8)".
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
3 Definitions and abbreviations
| |
303e74d8013c9a80fc5072ebde975465
|
183 015
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 615 [1] apply.
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 615 [1] apply. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 6
|
303e74d8013c9a80fc5072ebde975465
|
183 015
|
4 Communication Waiting (CW)
|
The provisions of the present document are contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 615 [1]. ETSI ETSI TS 183 015 V2.1.1 (2009-04) 9 History Document history V2.1.1 April 2009 Publication
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage one and two of the ISDN supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB).
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 011 V2.0.0 (2008-06) 6 [12] Void. [13] Void. [14] Void. [15] Void. [16] Void. [17] Void. [18] ETSI TS 124 411: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification (Release 8)".
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] Void.
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
3 Definitions and abbreviations
| |
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 411 [18] apply.
|
63ffe60a200b805cb953d0d9093efd05
|
183 011
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 411 [18] apply. 4 Anonymous Communication Rejection (ACR) and Communication Barring (CB) The provisions of the present document are contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V2.0.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V2.0.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V2.0.0 (2008-06) 9 Annex C (informative): Change history Information is contained in TS 124 411 [18]. ETSI ETSI TS 183 011 V2.0.0 (2008-06) 10 History Document history V2.0.0 June 2008 Publication
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Communication Hold (HOLD) services, based on stages one and two of the ISDN Hold (HOLD) supplementary services.
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] ETSI TS 124 410: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification (3GPP TS 24.410 Release 8)". ETSI ETSI TS 183 010 V2.0.0 (2008-06) 6
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
3 Definitions and abbreviations
| |
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 410 [7] apply.
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 410 [7] apply.
|
45813f4893d229a0f50bab8d0dc65195
|
183 010
|
4 Communication Hold (HOLD)
|
The provisions of the present document are contained in TS 124 410 [7]. ETSI ETSI TS 183 010 V2.0.0 (2008-06) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 410 [7]. ETSI ETSI TS 183 010 V2.0.0 (2008-06) 8 History Document history V2.0.0 June 2008 Publication
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
1 Scope
|
The present document specifies the stage three protocol description of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services.
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 6 [13] Void. [14] Void. [15] Void. [16] Void. [17] Void. [18] ETSI TS 124 508: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification (3GPP TS 24.508 Release 8)".
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
3 Definitions and abbreviations
| |
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 508 [18] apply.
|
cf3dd9d16685a624f3065e75d79a3934
|
183 008
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 508 [18] apply. 4 Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) The provisions of the present document are contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 9 Annex C (informative): Bibliography Information is contained in TS 124 508 [18]. ETSI ETSI TS 183 008 V2.8.0 (2008-06) 10 History Document history V2.4.1 August 2007 Publication V2.7.0 January 2008 Publication V2.8.0 June 2008 Publication
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
1 Scope
|
The present document specifies the stage three (protocol description) of the Originating Identification Presentation (OIP) simulation service and the Originating Identification Restriction (OIR) simulation services.
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 6 [13] Void. [14] ETSI TS 124 407 : "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification" (3GPP TS 24.407 Release 8).
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
3 Definitions and abbreviations
| |
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 407 [14] apply.
|
b36a88927c23ee6dcefdad931f1db82d
|
183 007
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 407 [14] apply. 4 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) The provisions of the present document are contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 407 [14]. ETSI ETSI TS 183 007 V2.0.0 (2008-06) 9 History Document history V2.0.0 June 2008 Publication
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
1 Scope
|
The present document specifies the stage three Protocol Description of the Message Waiting Indication (MWI) service, based on stage one and two of the ISDN MWI supplementary services.
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 6 [13] Void. [14] ETSI TS 124 406: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification (Release 8)".
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
3 Definitions and abbreviations
| |
0932a73014cee3bb138c11baa917f008
|
183 006
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 406 [14] apply.
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 406 [14] apply.
|
0932a73014cee3bb138c11baa917f008
|
183 006
|
4 Message Waiting Indication (MWI)
|
The provisions of the present document are contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 7 Annex A (informative): Example signalling flows of Message Waiting Indication (MWI) service operation Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 8 Annex B (informative): Example of a filter criteria Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 9 Annex C (informative): Bibliography Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 10 Annex D (informative): Change history Information is contained in TS 124 406 [14]. ETSI ETSI TS 183 006 V2.0.0 (2008-06) 11 History Document history V2.0.0 June 2008 Publication
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service.
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 6 [12] ETSI TS 124 505: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification (3GPP TS 24.505 Release 8)".
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
3 Definitions and abbreviations
| |
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 505 [12] apply.
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 505 [12] apply.
|
175afaf5bce693d8f68e5589b88b7b21
|
183 005
|
4 CONFerence (CONF)
|
The provisions of the present document are contained in TS 124 505 [12]. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 7 Annex A (informative): Signalling flows Information is contained in TS 124 505 [12]. ETSI ETSI TS 183 005 V2.6.0 (2008-06) 8 History Document history V2.5.0 January 2008 Publication V2.6.0 June 2008 Publication
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
1 Scope
|
The present document defines a specification applicable to the Rr interface between Generic Resource Admission Control Function (x-RACF) instances, based on the Diameter protocol. Other alternative protocols which may also be used for this interface such as ANCP are not specified in the present document. Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 003 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [3] ETSI ES 282 004 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub- System (NASS)". [4] ETSI ES 283 034 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol". [5] ETSI TS 183 017 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [6] IETF RFC 4006: "Diameter Credit-Control Application". ETSI ETSI TS 183 071 V3.1.1 (2010-02) 8 [7] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209)". [8] IETF RFC 3588: "Diameter Base Protocol". [9] IETF RFC 4005: "Diameter Network Access Server Application". [10] ETSI TS 183 026 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access Resource and Admission Control Function (A-RACF) In the Resource and Protocol specification". [11] ETSI TS 133 210: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210 )". [12] IETF RFC 4960: "Stream Control Transmission Protocol". [13] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)". [14] IETF RFC 3554: "On the Use of Stream Control Transmission Protocol (SCTP) with IPSec". [15] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329)".
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
3 Definitions and abbreviations
| |
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: delegated x-RACF: x-RACF instance which works in the Rr delegated Model and performs admission control for the resources delegated by the delegating x-RACF delegating x-RACF: x-RACF instance which works in the Rr delegated Model and delegates a bulk of resources to another x-RACF instance for admission control
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AAA AA-Answer AAR AA-Request ABNF Augmented Backus–Naur Form AF Application Function ANCP Access Node Control Protocol ASA Abort-Session-Answer ASR Abort-Session-Request ETSI ETSI TS 183 071 V3.1.1 (2010-02) 9 ATM Asynchronous Transfer Mode AVP Attribute-Value Pair CCA CC-Answer CCR CC-Request CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request DHCP Dynamic Host Configuration Protocol FQDN Fully Qualified Domain Name IANA Internet Assigned Numbers Authority ID IDentifier IETF Internet Engineering Task Force IP Internet Protocol IPSec IP Security NASREQ Network Access Server Application NASS Network Attachment Sub-System PNA Push-Notification-Answer PNR Push-Notification-Request QoS Quality of Service RAA Re-Auth-Answer RACS Resource and Admission Control Sub-System RAR Re-Auth-Request RCEF Resource Control Enforcement Function RFC Request For Comments Rr reference point Rr RTCP Realtime Transport Control Protocol SCTP Stream Control Transport Protocol SDI Session Description Information SPDF Service-based Policy Decision Function STA Session-Termination-Answer STR Session-Termination-Request TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking UDA User-Data-Answer UDR User-Data-Request UE User Equipment VC Virtual Channel VP Virtual Path x-RACF Generic Resource Admission Control Function ETSI ETSI TS 183 071 V3.1.1 (2010-02) 10
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
4 Overview
|
The present document specifies the Diameter protocol for the RACS Rr interface. The Rr interface is used for QoS resource reservation between x-RACF instances of RACS within a single administrative domain. The functional requirements and the stage 2 specifications of the Rr interface are contained in ES 282 001 [1] and ES 282 003 [2]. Figure 4.1: Rr interface
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5 Procedure descriptions
| |
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.1 General
| |
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.1.1 Information elements
|
The following clauses describe the realization of the functional procedures defined in the RACS (ES 282 003 [2]) using Diameter commands described in clauses 6 and 7. This involves describing a mapping between the Information Elements defined in the RACS specification (ES 282 003 [2]) and Diameter AVPs. In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional: • A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. • A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled: - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. If multiple Information Elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP. Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd’, Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd’, Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf ETSI ETSI TS 183 071 V3.1.1 (2010-02) 11 - If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message. • An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2 Procedures on the Rr interface
| |
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1 Resource control procedures for Request Model
|
The resource control process supports the following operations: 1) Resource Reservation: the resources are admitted by the requested entity (e.g. lower-tier x-RACF). In relation to the enforcement operations performed in the co-located RCEF, it can be divided into the following categories: - Reservation only: the resources are reserved but not allocated. - Commit only: the pre-reserved resources are allocated. - Reservation and commit: the resources are reserved and allocated. 2) Resource Modification: the pre-reserved/committed resources are updated upon the request of the originating entity (e.g. top-tier x-RACF). 3) Resource Release: the pre-reserved/committed resources are terminated upon the request of the originating entity. 4) Event notification: a specific action is requested when a pre-defined event occurs (e.g. reservation expiration). The Flow-Status AVP is used to define the action to be taken for each AA-Request made by the top-tier x-RACF to the lower-tier x-RACF. The rules for interpreting the Flow-Status AVP are the following: • Resource Reservation: can be invoked by any of the following status: - Reservation only: New Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) with Flow-Status AVP(s) set to DISABLED (3). - Commit only: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). - ReservationAndCommit: New Media-Component-Description AVP(s) and optionally Media-Sub-Component AVP(s). Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). NOTE: For the purpose of the resource admission and reservation, any of above status triggers the procedure. The distinction of above flow status is only meaningful in the case the lower-tier x-RACF needs to control the enforcement operations (e.g. Opening the gate) in the co-located RCEF. • Resource Modification: Updated Media-Description-Component AVP(s) and Media-Sub-Component AVP(s). Flow-Status AVP not modified, unless the state needs to be modified (e.g. for committing a resource reservation, or for releasing a resource reservation). • Resource Release: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to REMOVED (4). ETSI ETSI TS 183 071 V3.1.1 (2010-02) 12 These resource control operations are described in the following clauses. During the operations Diameter AVPs are passed between the top-tier x-RACF and the lower-tier x-RACF.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1.1 Procedures at the Top-tier x-RACF
| |
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1.1.1 Resource Reservation Session Establishment and Initial Resource Reservation
|
Upon the receipt of a new request from the SPDF, the top-tier x-RACF sends an initial request to the lower-tier x-RACF for initiating a resource reservation session. The AA-Request issued to request an initial reservation contains a new Session-Id assigned by the top-tier x-RACF. As specified in RFC 3588 [8], the Session-Id is globally unique and is meant to uniquely identify a resource session without reference to any other information. The Session-Id begins with the sender's identity encoded in the DiameterIdentity type. This AA-Request message contains one or more Media-Component-Description Attribute-Value Pair(s) (AVP(s)). Each Media-Component-Description AVP describes the set of flows of a particular media type (i.e. it may contain one or more Media-Sub-Component AVP(s) and requirements for the flows). The top-tier x-RACF may forward an AF-Charging-Identifier AVP from the SPDF in the message for charging correlation purposes between AF and RACS. The resource admission and reservation operation that shall be performed by the lower-tier x-RACF for each individual media and flow is triggered by the following value of the Flow-Status AVP, as indicated in table 5.1: • Reservation; the value of the Flow-Status AVP shall be set to DISABLED (3). • ReservationAndCommit; the value of the Flow-Status AVP shall be set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). • The Flow-Status AVP shall be specified in the Media-Component-Description AVP and in the Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to the same value in both these AVPs. Table 5.1: Initial Reservation operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media AAR New Media, DISABLED New flow, DISABLED Reserve Resources for all the flows in the request. The media(s) and flow(s) descriptions MUST be new ones. AAR [New Media, ENABLE*] New flow, ENABLE* Reserve Resources. In addition, instruct the co-located RCEF to commit resources for some of the flows. The media(s) and flow(s) descriptions MUST be new ones (see note). NOTE: The control of committing resources in the co-located RCEF is an implementation choice and out of scope in the present document. As specified in clause 8.9 of RFC 3588 [8], the top-tier x-RACF may specify the Authorization-Lifetime AVP in the AA-Request to request a maximum lifetime for a session. To request a hard-state session the top-tier x-RACF shall omit the Authorization-Lifetime AVP in the AA-Request. To request a soft-state session the top-tier x-RACF shall specify this AVP in the AA-Request. The AA-Answer may contain the Authorization-Lifetime AVP. The AA-Answer may contain the Auth-Grace-Period AVP in addition to the Authorization-Lifetime AVP. The Authorization-Lifetime AVP specifies the maximum number of seconds before the Session must be refreshed by the top-tier x-RACF. The Auth-Grace-Period AVP contains the number of seconds the lower-tier x-RACF will wait for a Refresh following the expiration of the Authorization- Lifetime AVP. Whether the Authorization-Lifetime AVP and Auth-Grace-Period need to be included in the AA-Answer is a local decision of the lower-tier x-RACF. This means that the top-tier x-RACF may be offered a soft-state reservation although it asked for hard-state or a hard-state reservation although it asked for soft-state. Should the top-tier x-RACF not accept what is offered by the lower-tier x-RACF it must explicitly release the resources through issuing another AAR command. The top-tier x-RACF may specify, in the Specific-Action AVP of the AA-Request through which the initial reservation request is made, the events of which it wants to be informed. The supported events are listed in clause 6.5.9. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 13 The behaviour when the top-tier x-RACF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1.1.2 Resource Modification and Release for Media Flows
|
The top-tier x-RACF may modify an existing session by sending an AA-Request to the lower-tier x-RACF with zero or more updated Media-Component-Description AVP(s) and optional Media-Sub-Component AVP(s). The Session-Id shall be an existing one and refer to the session that is to be modified. The top-tier x-RACF may perform the following operations: • Add a new flow within a media component by providing a new Media-Sub-Component AVP within the corresponding Media-Component-Description AVP. • Add a new flow within a new media component by providing a new Media-Component-Description AVP. • Modify a media component by updating the corresponding Media-Component-Description AVP (e.g. increase or decrease the allocated bandwidth). • Modify a flow within a media component by updating the corresponding Media-Sub-Component AVP. • Modify a media flow state from Reserved to Committed by providing a Flow-Status AVP of the corresponding Media-Component-Description AVP and/or Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to one of the values ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, according to the direction in which the resources are to be committed. This operation requires that the media and flows are in the Reserved state prior to the AA-Request. • Release a media component by providing the corresponding Media-Component-Description AVP with the Flow-Status AVP set to the value REMOVED. • Release a flow within a media by providing the corresponding Media-Sub-Component AVP with the Flow-Status AVP set to the value REMOVED. • Refresh a soft-state session by providing an AA-Request message containing the Session-Id of the session that is to be refreshed. The AA-Request may contain the Authorization-Lifetime AVP to request a maximum lifetime of the refreshed session. If this AVP is not included, the refresh message requests the lifetime to be extended by a default value. The AA-Request may contain Media-Component-Description AVP(s) and Media-Sub-Component AVP(s) (e.g. to modify media, flows and/or commit status). The Flow-Status AVP in the Media-Sub-Component AVP shall always be the same as the Flow-Status AVP in the Media-Component-Description AVP containing the Media-Sub-Component AVP. The top-tier x-RACF SHALL NOT use the RAA to modify the session service information. As an option, the top-tier x-RACF MAY send an AAR command following an RAA to update the session service information after the local RACF responds with the RAR. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 14 Table 5.2: Modification operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media AAR Existing Media Existing Flow, Unchanged Flow-Status Modify a media. In addition, modify a flow according to the new parameters specified in the Media-Sub-Component AVP. The Media and Flow must exist (see notes 1, 2 and 5). AAR Existing Media New flow. Same Flow-Status AVP as in the media. (see note 3) Modify a media. In addition, add a new flow in a media. The Flow must be new (see notes 3 and 5). AAR Existing Media (see note 4) REMOVED Modify a media. In addition, release an existing flow within an existing media. If the flow does not exist, the request shall be ignored by the lower-tier x-RACF (see notes 2 and 5). AAR Existing Media, Modified Flow-Status AVP = REMOVED Existing Flow, Flow-Status AVP = REMOVED Release the resources of the media. AAR Existing Media Existing Flow (see note 5). NOTE 1: If the media is not an existing one, the AAR is interpreted as a reservation for a new media (clause 5.2.1.1). NOTE 2: The parameters specified at flow-level (in the Media-Sub-Component AVP(s)) take precedence over the parameters specified at media-level (in the updated Media-Component-Description AVP). NOTE 3: The Flow-Status AVP of a new flow within a media shall be the same as the Flow-Status of the media. NOTE 4: As the Modification operation is also used for the Commit operation, the Flow-Status AVP of the Media-Component-Description AVP may actually be modified. NOTE 5: In the case of a soft-state reservation, extend its lifetime. The behaviour when the top-tier x-RACF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document.
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1.1.3 Termination and Release of the Resources for a Resource Reservation Session
|
The top-tier x-RACF may issue a Session-Termination-Request (STR) command to the lower-tier x-RACF when it decides to terminate a resource reservation session and release all the resources. The session termination may be triggered by the explicit request from the SPDF or the expiry of the session or the inactivity of applications based on network policy. This command releases all the resources associated with the session identified by the provided Session-Id AVP. Table 5.3: Resource release operations Message Type Flow-Status AVP at the level of Meaning Media Sub-Media STR Release a session: all the media(s) and flow(s) within that session are released. When receiving an Abort-Session-Request (ASR) message from the lower-tier x-RACF, the top-tier x-RACF shall – if the session involves the resources in other network segments – release those resources and inform the SPDF of that the resources identified by the Session-Id AVP have been released. If the ASR message contains one or more Session-Bundle-Id AVPs the top-tier x-RACF shall perform these procedures for all sessions associated with the Session-Bundle-Id AVP(s).
|
94c82513a2001364c90e5aadbf7f640d
|
183 071
|
5.2.1.1.4 Event notification
|
Notifications for specific events may be implicitly requested through policies established in the lower-tier x-RACF. The top-tier x-RACF may further specify, in the Specific-Action AVP of an initial AA-Request command, the events of which it wants to be informed. The supported events are listed in clause 6.5.9. ETSI ETSI TS 183 071 V3.1.1 (2010-02) 15
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.