hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
2.2M
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
7.3.1.5 Message Waiting Indication for analogue access
On receipt of a Service Notification internal primitive reporting the "message-summary" event, the PES access point shall request the media gateway to apply the Generic Data Signalling signal of the andisp package defined in Recommendation H.248.23 [13]. The value of the TAS parameter is provisioned in the media gatewa...
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
7.3.1.6 Procedures for ISDN access
FFS.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
7.3.2 PES Media Gateway
The PES media gateway shall support the H.248 procedures specified in ES 283 002 [5] appropriate to an MG. ETSI ETSI TS 183 043 V2.3.1 (2009-03) 49
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8 Protocol using DSS1 for PES
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.1 Introduction
This clause identifies the functional entities of the IMS-based PES architecture [3] that play a specific role in the provision of PES services with regards to DSS.1 processing.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.2 Functional Entities
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.2.1 User Equipment (UE)
Conventional SIP UEs do not exist in PES (see clause 5.2.1). For the purpose of the PES, the VGW shall implement the role of a PES endpoint as described in clause 8.3.1.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.2.2 Access Gateway Control Function (AGCF)
For the purpose of the PES, the AGCF shall implement the role of the PES access point as described in clause 8.3.2. The AGCF entity encompasses the functionality of a Media Gateway Controller (MGC) and of a SIP User Agent.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.2.3 Signalling Gateway Function (SGF)
For the purpose of the PES, the SGF shall implement the role of the PES signalling gateway as described in clause 8.3.3. The AGCF entity encompasses the functionality of a Media Gateway Controller (MGC) and of a SIP User Agent.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.2.4 Voice over IP gateway (VGW)
For the purpose of the PES, the VGW shall implement the role of the PES endpoint as described in clause 8.3.1. The VGW entity encompasses the functionality of a Media Gateway Controller (MGC), Media Gateway (MG) and a SIP User Agent.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.3 Roles
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.3.1 PES Endpoint
The PES Endpoint shall support the DSS1 protocol according to EN 300 403-1 [41].
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.3.2 PES Access Point
The PES Access point shall support the DSS1 protocol according to EN 300 403-1 [41] and one or more backhaul procedures described in ES 283 002 [5] for relaying ISDN D-channel information, depending on the type of ISDN access supported.
7dd8c10c1a9b124ff7a27c3e74b13587
183 043
8.3.3 PES Signalling Gateway
The PES signalling gateway shall support one or more backhaul procedures described in ES 283 002 [5] for relaying ISDN D-channel information, depending on the type of ISDN access supported and one or more backhaul procedures described in ES 283 002 [5] for relaying ISDN D-channel information, depending on the type of I...
86a8cb2417653fdbaee677b0a1930040
183 020
1 Scope
The present document describes the protocol specifications and profiles for the interface between the UAAF in the visited NGN network (UAAF-proxy) and the UAAF in the home NGN network (UAAF-server). The specifications of this interface will be common for both xDSL and WLAN access networks, including possible other acce...
86a8cb2417653fdbaee677b0a1930040
183 020
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • ...
86a8cb2417653fdbaee677b0a1930040
183 020
3 Definitions and abbreviations
86a8cb2417653fdbaee677b0a1930040
183 020
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: access network: collection of network entities and interfaces that provide the underlying IP transport connectivity between end user devices and NGN entities Attribute-Value Pair: see RFC 3588 [15], it corresponds to an Information Ele...
86a8cb2417653fdbaee677b0a1930040
183 020
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Project Partnership AAA Authentication, Authorization and Accounting AAA-H AAA-Home AAA-V AAA-Visited AMF Access Management Function AP Access Point ATA Analogue Terminal Adaptor AVP Attribute Value Pair CNG Customer Netw...
86a8cb2417653fdbaee677b0a1930040
183 020
4 NGN General Architecture
ES 282 001 [1] provides a description of the general network architecture of the NGN. The model is depicted in figure 1. UE Visited NGN Network Home NGN Network e1 e5 Figure 1: General NGN Network Model Interface e1 is an access-network-specific interface, and is dependant on the access technology being used (xDSL, WLA...
86a8cb2417653fdbaee677b0a1930040
183 020
4.1 Overview of Interface e5
The present document details the protocols and profiles for interface e5. This interface is intended to be used between a UAAF-proxy and a UAAF-server, which may be in different distractive domains. This interface allows the UAAF-proxy to request the UAAF-server for user authentication and authorization, based on user ...
86a8cb2417653fdbaee677b0a1930040
183 020
5 Protocols and profiles for Interface e5
86a8cb2417653fdbaee677b0a1930040
183 020
5.1 802.1X-based Authentication
Figure 4 depicts a typical protocol stack for 802.1X-based authentication. Further details may be found in Wi-Fi Alliance [4]. The EAP messages are carried over EAPOL (EAP over LAN) frames between the UE and the AP and then re-encapsulated in RADIUS or Diameter messages when sent from the AP to the home AAA Server (via...
86a8cb2417653fdbaee677b0a1930040
183 020
5.2 Intermediaries
An intermediary may be defined as an entity that manages and facilitates AAA transactions in real time between 2 service provider network entities. One or more intermediaries may exist between the visited and the home NGN networks, as shown in figure 5. The existence of these intermediaries should be transparent to the...
86a8cb2417653fdbaee677b0a1930040
183 020
5.3 Requirements of the visited NGN network
One endpoint of interface e5 is the visited NGN network. Specifically, the access network within the visited NGN network should support the following requirements, and interface e5 for AAA logically extends all the way from the access network to the UAAF in the home NGN network. 1) The visited NGN network shall comply ...
86a8cb2417653fdbaee677b0a1930040
183 020
5.4 Requirements of the home NGN network
1) The home NGN network shall comply with the relevant requirements in TS 129 234 [3], clauses 4 and 5. In TS 129 234 [3], all references to "3GPP AAA Proxy" implies the requirements shall be met by the visited NGN network (specifically the access network), and all references to "3GPP AAA Server" implies the requiremen...
86a8cb2417653fdbaee677b0a1930040
183 020
5.5 Subscriber Profile Transfer
The protocol used on the e5 interface shall support the transport of subscriber profile information as defined in ES 282 004 [2]. Table 1 provides the list of information elements to be carried over the interface for that purpose and indicates the list of Diameter attributes that shall be supported to achieve it. Table...
86a8cb2417653fdbaee677b0a1930040
183 020
5.5.1 Privacy-Indicator AVP
The Privacy-Indicator AVP (AVP code 440 13019) is of type Grouped and provides policy rules for disclosure of subscriber profile elements to applications. AVP Format: Privacy-Indicator ::= < AVP Header: 440 13019 > * {Requested-Information} * [AF-Application-Identifier] Each Requested-Information AVP identifies a profi...
f92d6483a77f6b4220575ae1402a53f3
183 042
1 Scope
The present document specifies the, stage three Protocol Description of the Completion of Communications to Busy Subscriber (CCBS) service and the Completion of Communication on no Reply (CCNR) service
f92d6483a77f6b4220575ae1402a53f3
183 042
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 accept...
f92d6483a77f6b4220575ae1402a53f3
183 042
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 642: "Digital cellular telecommunications...
f92d6483a77f6b4220575ae1402a53f3
183 042
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.
f92d6483a77f6b4220575ae1402a53f3
183 042
3 Definitions and abbreviations
f92d6483a77f6b4220575ae1402a53f3
183 042
3.1 Definitions
For the purposes of the present document, the terms, definitions given in TS 124 642 [1] apply.
f92d6483a77f6b4220575ae1402a53f3
183 042
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TS 124 642 [1] apply. ETSI ETSI TS 183 042 V2.1.1 (2009-01) 6 4 Completion of Communications to Busy Subscriber (CCBS) The provisions of the present document are contained in TS 124 642 [1]. ETSI ETSI TS 183 042 V2.1.1 (2009-01) 7 Annex A (informative...
e142e055458ad4dd142e50ecfb0407b8
183 019
1 Scope
The present document describes the protocol specifications and profiles for supporting network attachment procedures at the interface between the User Equipment and the access network in an NGN network.
e142e055458ad4dd142e50ecfb0407b8
183 019
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 accept...
e142e055458ad4dd142e50ecfb0407b8
183 019
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: " Telecommunications and Internet co...
e142e055458ad4dd142e50ecfb0407b8
183 019
3 Definitions and abbreviations
e142e055458ad4dd142e50ecfb0407b8
183 019
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: Access Network (AN): collection of network entities and interfaces that provide the IP transport connectivity between end user devices and NGN entities Core Network (CN): portion of the delivery system composed of networks, systems equ...
e142e055458ad4dd142e50ecfb0407b8
183 019
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Project Partnership AAA Authentication, Authorization and Accounting AC Access Controller AMF Access Management Function AN Access Network AP Access Point ARF Access Relay Function ATA Analog Terminal Adaptor CHADDR Clien...
e142e055458ad4dd142e50ecfb0407b8
183 019
4 NGN general architecture
ES 282 001 [1] provides a description of the general network architecture of the NGN. The model is depicted in figure 1. UE Visited NGN network Home NGN network e1 e5 Figure 1: General NGN network model Interface e1 is a user-network interface supporting attachment of user equipment to a network. The present document p...
e142e055458ad4dd142e50ecfb0407b8
183 019
4.1 Overview of interface e1
The present document details the protocols and profiles for e1 - the interface for authentication, authorization and IP address allocation. This interface enables the UE to initiate authentication and authorization requests, as well as initiate requests for IP address allocation, DNS allocation, and other network confi...
e142e055458ad4dd142e50ecfb0407b8
183 019
4.1.1 Authentication
This interface specifies the protocols and profiles used for authentication of the UE to the network, and vice-versa. The credentials used for authentication depend on the authentication method used as well as the preferences of the network service provider. Possible credential types include, SIM, certificates and user...
e142e055458ad4dd142e50ecfb0407b8
183 019
4.1.2 IP address and network configuration
Once the UE is authenticated successfully, it shall be able to obtain an IP address in order to access the different services offered by the service provider. This interface also provides a method to transport IP address and network configuration information to the UE to enable IP access. ETSI ETSI TS 183 019 V2.3.0 (2...
e142e055458ad4dd142e50ecfb0407b8
183 019
5 PPP-based access network configuration
e142e055458ad4dd142e50ecfb0407b8
183 019
5.1 Authentication phase
5.1.1 PPP link establishment phase (LCP) with authentication (PAP/CHAP/EAP) A generic description of the PPP-based authentication model is provided in TS 124 234 [2], clause 7.2 and annex B. There are currently no specific requirements on PPP-based authentication scenarios. This may be further studied and defined in fu...
e142e055458ad4dd142e50ecfb0407b8
183 019
5.2 Network Configuration Phase (NCP)
e142e055458ad4dd142e50ecfb0407b8
183 019
5.2.1 PPP Network Configuration Phase for IP Networks (NCP/IPCP)
e142e055458ad4dd142e50ecfb0407b8
183 019
5.2.1.1 PPP and ARF
The Access Relay Function (ARF) acts as a relay between the user equipment and the NASS. It receives network access requests from the user equipment and forwards them to the NASS. Before forwarding a request, the ARF may also insert local configuration information and apply protocol conversion procedures. In PPPoE case...
e142e055458ad4dd142e50ecfb0407b8
183 019
5.2.1.2 PPP and AMF
The Access Management Function (AMF) translates network access requests issued by the UE. It forwards the requests for allocation of an IP address and possibly additional network configuration parameters to/from the NACF. In case PPP is applied, the AMF terminates the PPP connection and provides the inter-working with ...
e142e055458ad4dd142e50ecfb0407b8
183 019
6 Ethernet-based access network configuration
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1 Authentication phase
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.1 EAP over Ethernet (802.1X)
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.1.1 General
The 802.1X IEEE standard [7] describes a protocol to exchange authentication information over IEEE 802 networks. This protocol is called EAP over LAN (EAPOL) and aims to carry EAP messages over the access transport network. ETSI ETSI TS 183 019 V2.3.0 (2008-02) 12 802.1X defines three functions involved in the authenti...
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.1.2 802.1X and ARF
The Access Relay Function (ARF) acts as a relay between the user equipment (UE) and the AMF. In the 802.1X case the ARF is always co-located with the AMF. The ARF is in charge of providing access loop identification information and transfer it to the AMF.
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.1.3 802.1X and AMF
In the 802.1X case, the Access Management Function (AMF) incorporates the authenticator function. It shall be implemented one L2 hop far from the Supplicant implemented in the UE. The AMF constructs a proper AAA message sent to the UAAF with the following elements: The access loop identification information provided ...
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.2 802.1X-based xDSL/FTTx (wireline) access network
This clause provides further details on the use of 802.1x when the access network uses xDSL or FFTx technology. Authentication process and protocol exchanges between the different entities are compliant with the description provided in clause 6.1.1. The xDSL/FTTx (wireline) access network will physically consist of at ...
e142e055458ad4dd142e50ecfb0407b8
183 019
6.1.3 802.1X-based WLAN access network functional architecture
The WLAN Access Network will physically consist of at least one Access Point (AP), which will provide the radio connectivity for the WLAN UE devices. The Access Network or the core network may also contain an Access Controller (AC), that may manage a number of APs. For the WLAN scenario, the UE (mobile station) acts as...
e142e055458ad4dd142e50ecfb0407b8
183 019
6.2 Network configuration phase
e142e055458ad4dd142e50ecfb0407b8
183 019
6.2.1 DHCP procedures
The Network Access Configuration Function (NACF) is responsible for the IP address allocation to the UE. It may also distribute other network configuration parameters such as address of DNS server(s) and address of signalling proxies for specific protocols. A NACF may be realized as a DHCP server. Once the UE has been ...
e142e055458ad4dd142e50ecfb0407b8
183 019
7 DHCP Support for Interface e1
e142e055458ad4dd142e50ecfb0407b8
183 019
7.1 Access Network based on IPv4
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 50 "Requested IP@" RFC 2132 [11], RFC 2131 [10]. Option 55 "Parameter List" RFC 2132 [11]. Option 60 "Vendor Class Identifier" RFC 2132 [11]. Option 61...
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...
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 ...
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. ETSI ETSI TS 183 019 V2.3.0 (2008-02)...
e142e055458ad4dd142e50ecfb0407b8
183 019
8 Applicability to WLAN access networks
This certification of WLAN devices by the Wi-Fi Alliance [3] 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.
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 [3] 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 sp...
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. NOTE: Requirement 1 of clause 6.5 is satisfied by the following EAP methods. It should be noted that the list b...
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 speci...
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 accept...
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 Control...
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...
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 accept...
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] Voi...
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 1...
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 accept...
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] Voi...
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 1...
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 accept...
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...
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...