hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
049271446448601336483ab2574d528a
|
185 003
|
4.3.3.4 CNG-AuF: CNG-Authentification Function
|
The CNG-AuF shall manage the authentication of CNDs to be connected to the CPN. A CND requesting for a CPN Wireless attachment should be authorized by the access point embedded in the CNG. The CNG-AuF may thus be configured by the user for such a case, using the CNG-User Interface Function (CNG-UIF).
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.3.5 CNG-LF: CNG-Location Function
|
The CNG-LF functional entity may allow an internal application providing location information, to perform for instance emergency calls or deliver some local video content. This information may be configured by the owner of the CNG, received from the CLF or obtained from the network, via the CNG-AtF (typically through DHCP option 82). The information should also come from the CLF. In this case the CNG-LF may not be used. 4.3.4 The CNG-Resource and Admission Control Functional entities (C-RACF)
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.4.1 CNG-ACF: CNG-Admission Control Function
|
The CNG-ACF should receive and send QoS messages from/to the CNG-SIP proxy B2BUA Function. In particular it should: a) check resources availability on each link/device involved in the communication requesting a QoS reservation/allocation, through an internal database; b) perform the appropriate resources reservation, through the CNG-PCF. Thus, the CNG-ACF should manage session limitations for instance or the priority of media streams. This applies to upstream flows but there may also be an opportunity to do so for downstream flows. The CNG-ACF is only able to take into account sessions that pass through the SIP B2BUA. Sessions using encrypted signalling or different signalling protocols will not be included. In the latter case the CNG-ACF might allow more sessions through the access line that it should have. As RACS has a full view on all sessions over the access line, it will deny the session setup thus preventing an overload situation [i.7]. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 15
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5 The CNG-Service-related Functional entities (CNG-SF)
|
Depending on the services supported, a CNG may include one or more Service-related Functions. The present version of the present document identifies four types of SCFs intended to support SIP-based applications. It should be noted that not all applications require a Service-related Function to be involved (e.g. P2P applications usually do not require such functions).
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5.1 VGCF: Voice Gateway Control Function
|
The VGCF within the CNG is the equivalent of an MGC embedding a SIP User Agent. A CNG should include several UAs in case of multi analogue and/or ISDN Customer Network Device within the CPN. The VGCF should control the CNG-CSMF (i.e. the R-MGF as defined in ES 282 001 [1]). The VGCF should perform the service authentication and manage signalling flows securely. NOTE: The VGCF together with the CNG-CSMF provides the function of a R-VGW as defined in TS 182 012 [6]. In case of AKA authentication, the VGCF shall have access to the authentication parameters through an ISIM/UICC functionality. To be noticed that HTTP Digest is for an early deployment whereas IMS AKA is the target solution.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5.2 CNG-SIP Proxy B2BUA Function
|
The CNG-SIP Proxy B2BUA should implement: a) a Local SIP Registrar without any authentication needed; b) an outbound SIP Proxy, a SIP access point for the P-CSCF, forwarding the register messages to the P-CSCF if necessary. Moreover, it may be: c) a protocol adaptation module performing an adaptation of non-IMS compliant IETF SIP protocols towards one IMS compliant SIP protocol. This functionality could also be performed by the NGN. NOTE: Some adaptation may be performed by the CNG so as to support non-IETF SIP CNDs in the CPN (proprietary SIP) but this case is out of the scope of the present document. d) a protocol adaptation module performing remote access communication establishment. This functionality is called Remote Access Transport Agent (RATA). The CNG-SIP Proxy B2BUA Function should be aware of each SIP CND (could be an IMS CND) capability within the CPN environment. The CNG-SIP Proxy B2BUA Function shall at last be able to manage two SIP dialogues and the associated identities (possibly through an ISIM module), from both the NGN and the CND sides. This gives the opportunity to transfer an IMS session from a device to another or to forward an incoming call to the appropriate CNDs (forking). The responsibility of the RATA is to provide a communication channel enabling interaction between remote and in the home network located UPnP capable CND’s. In case of AKA authentication, the SIP Proxy B2BUA shall have access to the authentication parameters through an ISIM/UICC functionality. To be noticed that HTTP Digest is for an early deployment whereas IMS AKA is the target solution.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5.3 CNG-PPF: CNG-Plug and Play Function
|
The CNG-PPF may obtain some CND information (service discovery, description) and allow their control. Also, the CNG-PPF should allow a communication between many types of Customer Network Device within the CPN, not only conversational (based on UPnP for instance). The CNG-PPF may also support this kind of communication through the CNG between NGN devices and CND devices. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 16 While facilitating such communication, ALG functionality may be needed by the CNG-PPF, interfacing the CNG-NFF. Since some of the communication sessions supported by the CNG-PPF result in media sessions, the CNG-PPF may need to interface the CNG-ACF in order to support QoS provisioning for these types of services. The Remote Access Discovery Agent (RADA) discovers and maintains a device-list for the services provided. The list is continuously updated, kept and provided for facilitating communication between devices. When sessions (for example UPnP based) are initiated between a CND and a remote NGN device, they may be established by IMS SIP session establishment and then described in the SDP parts of the IMS SIP signalling. When establishing the UPnP session between the NGN and CPN endpoints the CNG-PPF needs to perform ALG functionality, by re-writing any CPN references within the UPnP messages and also control port forwarding through the CNG-NFF. Informative flows for the Remote Access feature are detailed in clause 7.4.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5.4 CNG-UIF: CNG-User Interface Function
|
The CNG-UIF entity should allow the user to configure many CNG parameters for the transport layer: a) firewall rules, possibly defined for each user (e.g. parental control); b) CNDs authorized within the CPN, with possible bandwidth restrictions. The operator shall be able to prevent a user from modifying a specific subset of CPN parameters. Thus this entity may have reference points with the CNG-AuF and the CNG-NFF of the CNG.
|
049271446448601336483ab2574d528a
|
185 003
|
4.3.5.5 ISIM module
|
The ISIM (see figure 4) is a network access application dedicated to IMS access contained in a UICC. It may be implemented in a CNG. Figure 4: Example of "UICC Card composition" The ISIM includes: a) The IMPI (IMS private identity). b) At least one IMPU (IMS public Identity). c) The operator's NGN Domain Name. d) Support for sequence number checking in the context of the IMS Domain. e) The same framework for algorithms as specified for the USIM applies for the ISIM. f) An authentication element so as to support the AKA authentication. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 17 The ISIM is located in the ISIM Application Dedicated File (ADFISIM) and contains service and network related information. The ADFISIM provides various data contained in Elementary Files (EF), for instance the EFIMPI containing the private user identity. Details about this file structure can be found in TS 131 103 [9].
|
049271446448601336483ab2574d528a
|
185 003
|
5 The CNG Reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.1 CND side Reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.1.1 Network attachment reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.1.1.1 e1' reference point
|
The e1' reference point is defined between the CND and the CNG-AtF. The CNG-AtF provides IP addresses (IPv4 or IPv6 format) to the CND through the CND-AtF, it may also send some configuration information for the CND (typically through DHCP). The CND and CNG shall mutually exchange their identities (e.g. MAC address, DeviceID, etc.) on e1' reference point. The CNG has to know which CNDs are behind itself within the CPN and each CND has to know its CNG. This reference point is mandatory if the CNG runs in a routed mode
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.1.2 e3' reference point
|
The e3' reference point is defined between the CND and the CNG-CMF. The CNG-CMF may provide the CND with parameters that are pre-configured in the CNGCF and sent to the CNG through the e3 reference point or, as an alternative, directly defined by the user. The CNG-CMF also configures the CNG, using information received from the CNGCF or supplied by the user himself. The CND should provide information on CND status to allow the CNGCF to make some diagnostic and performance tests through the CNG-CMF. To sum up, the e3' reference point supports a variety of functionality to manage a collection of user equipment (CNG/Customer Network Devices), including the following capabilities: a) auto-configuration and service provisioning; b) software/firmware management; c) status and performance monitoring; d) diagnostics. This reference point is recommended as the e3 reference point could also be used. The above mention functionalities can be also implemented directly using a direct e3 reference point between CND and CNGCF as an e3 reference point defined in ES 282 004 [3]. The direct reference point between CND and CNG, e3', could be limited to service provisioning functions; this may be used as an alternative to the corresponding functionalities on the e3 reference point between CND and CNGCF. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 18
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.1.3 au reference point
|
The au reference point is defined between the Customer Network Device and the CNG-AuF. There may be two types of authentication/authorization, according to: a) CPN pairing (attachment, encryption and security processes (WEP, WPA2, etc.)) based on specific CPN technologies (e.g. Wifi SSID, PLC technology). b) Access rights for some LAN services like the CNG Configuration (through the CNG-UIF). This reference point is recommended, except if a wireless access point is embedded in the CNG in which case it is mandatory.
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.2 Transport level reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.1.2.1 Dj reference point
|
The Dj reference point is responsible for the exchange of media flows between the User Equipment (CNG or CND) and the access node. This reference point is mandatory. It is based on the ES 282 001 [1] specification.
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.2.2 Dj' reference point
|
The Dj' reference point is responsible for the exchange of media flows between the IPTV CND and the CNG. It is applicable only in case the CNG is supporting IPTV in routed mode, as specified in TS 185 009 [13]. Through Dj', the IPTV CND communicates with the CNG-IPTVF and its related functionalities (IGMP proxy and snooping). This reference point is mandatory for IPTV CNDs performing CoD service (using RTSP) and BC service (using IGMP).
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.3 Service-related reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.1.3.1 Gm' reference point
|
The Gm' reference point supports the communication between a CND and the CNG, e.g. related to registration and session control. The difference between Gm and Gm' is related to the conformance to the IMS and to the need to go through the B2BUA to support local services. Further details about Gm' possible implementations can be found in the TR 185 007 [i.1]. This reference point is recommended.
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.3.2 u reference point
|
The u reference point gives the possibility to one or several users authorized (via the CNG-AuF) to have access to the CNG Configuration, through the CNG-UIF. The liaison should be as secure as possible (using HTTPs for instance). This reference point is recommended. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 19
|
049271446448601336483ab2574d528a
|
185 003
|
5.1.3.3 C reference point
|
The C reference point is defined between the CNG-PPF and the CND-PPF. It provides some CND information (service discovery, description) to the CNG and allow its control. Also, a communication between many types of Customer Network Device within the CPN may be established through the C reference point, using UPnP for instance. This reference point is optional.
|
049271446448601336483ab2574d528a
|
185 003
|
5.2 NGN side Reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.2.1 Network attachment reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.2.1.1 e1 reference point
|
This reference point is based on the TS 183 019 [7] specification. The e1 reference point is dedicated to the network attachment of the User Equipment. The e1 reference point is mandatory (in coherence with WG2 specifications).
|
049271446448601336483ab2574d528a
|
185 003
|
5.2.1.2 e3 reference point
|
This reference point is based on the ES 282 004 [3]. The e3 reference point is defined between the CNG-CMF and the CNGCF and should be extended also between the CNG-CMF and the CND for configuration purposes. Through a remote management protocol it is possible to support a variety of functionalities to manage a collection of user equipment (CNG/Customer Network Devices), including the following capabilities: a) auto-configuration and service provisioning; b) software/firmware management; c) status and performance monitoring; d) diagnostics. The e3 implementation between the CNG-CMF and the CNGCF is mandatory (in coherence with WG2 specifications), whereas the e3 implementation between the CNG-CMF and the CND-CMF is recommended, as e3' should be an alternative.
|
049271446448601336483ab2574d528a
|
185 003
|
5.2.2 Service-related reference points
| |
049271446448601336483ab2574d528a
|
185 003
|
5.2.2.1 Gm reference point
|
The Gm reference point supports the communication between UE and the IMS, e.g. related to registration and session control. Gm between the P-CSCF and the SIP proxy B2BUA is used to support several actions: a) send SIP messages to/from the NGN; b) call forking at the CNG level. The protocol used for the Gm reference point is SIP. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 20 To be noticed that the definition is extracted from the ES 282 007 [4]. This reference point is in line with the following specifications: a) ES 283 003 [5]. b) TS 182 012 [6]. c) TS 131 103 [9]. This reference point is mandatory (in coherence with WG2 specifications).
|
049271446448601336483ab2574d528a
|
185 003
|
5.2.2.2 Ut reference point
|
The Ut reference point enables the user to manage information related to his services, such as creation and assignment of Public Service Identities, management of authorization policies that are used e.g. by Presence service, conference policy management, etc. This reference point is in line with the ES 282 007 [4]. This reference point is optional (in coherence with WG2 specifications).
|
049271446448601336483ab2574d528a
|
185 003
|
6 The CNG Data Model
|
In case of an xDSL access network, the CNG shall support the gateway data model proposed by Broadband Forum in TR-098 [i.4] (data model for an internet gateway device). In order to support IPTV CNDs, the CNG shall be compliant with Broadband Forum TR-069 [i.3] amendment 1 annex F (device - gateway association) and in order to solve the NAT traversal problem for ACS initiated session setup the CNG shall support the dynamic port mapping creation function as specified in TR-098 [i.4]. In order to support non IMS CND, the CNG shall support the set of parameters defined by Broadband Forum in TR-104 [i.5] (data model for VoIP functionalities). The data model for cable-based CNG is for further studies.
|
049271446448601336483ab2574d528a
|
185 003
|
7 Information flows
|
NOTE: This clause is informative text reported in the form of examples, to give a better understanding of the relationships between the CPN entities and functionalities. Exhaustive information flows will be given in a stage 3 document. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 21
|
049271446448601336483ab2574d528a
|
185 003
|
7.1 Attachment flows
|
The candidate protocol on e1' is DHCP specified in RFC 2131 [10]. In figure 5 the basic information flow is given. CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack Figure 5: CND Attachment on e1' In order to mutually exchange the hardware identities between the CND and the CNG, the hardware identity can be defined for example as in TR-069 [i.3] (DeviceId) and the DHCP Option 125 can be used for the CND-CNG association as specified in TR-069, annex F [i.3].
|
049271446448601336483ab2574d528a
|
185 003
|
7.2 Configuration and management flows
|
The following information flow is an example of service provisioning functions supported by CNG (see figure 6). CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Set Identity) 200 OK (GET Response) CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Set Identity) 200 OK (GET Response) Figure 6: Provisioning on e3' With the first HTTP GET (Ask Identity), the CND asks the CNG for the list of available identities (IMPI, IMPU, etc.), and the CNG answers with the identities list in the HTTP GET Response. Then the CND chooses one identity and, in the second HTTP GET (Set Identity), provides the choice to the CNG, which then answers with confirmation in the HTTP Get Response. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 22
|
049271446448601336483ab2574d528a
|
185 003
|
7.3 Signalling flows
|
The candidate protocol on Gm' is SIP specified in RFC 3261 [8], and optionally HTTP Digest as an authentication method as specified in RFC 2617 [14]. The candidate protocol on Gm is SIP specified in TS 124 229 [11] and ES 283 003 [5].
|
049271446448601336483ab2574d528a
|
185 003
|
7.3.1 CND attachment and local/IMS registration
|
The non-IMS devices considered in this case are devices associated to the VoIP phone number of the CNG. Different kinds of devices are foreseen (see also TS 185 006 [12]), some examples are: a) Fixed or Wireless SIP phone. b) SIP Multi-mode (e.g. dual WI-Fi/3G phone). c) SIP softphone on PC. d) Other: playstation, STB, etc. These SIP non-IMS devices have a local SIP identity, as defined as local SIP URI (e.g. device_kitchen) or public SIP URI (e.g. John123): a) Vendor provides a local SIP identity for all SIP devices. This enables "Plug and play" functionality. User does not need to configure the SIP device. By default, this local identity can be the MAC address. b) User can change the local identity provided by the vendor to another local identity or public SIP URI. The customer can change this parameterization, and select a specific name. Or a local phone number for each device. The attachment phase is: 1) For non IMS CND's the Gm' reference point is used (for local services), the DHCP server of the CNG will return the DHCP option 120 to the CND, standardized to provision CNG SIP proxy IP address or domain-name. This option will contain the IP address of the CNG on the CPN side (ex: 192.168.1.1). 2) The device registers locally to the CNG SIP-IMS proxy (Registrar) using its local SIP URI. SIP REGISTER message is sent by the CNG to the NGN with the IMPU of the CNG which maps to the CND local SIP URI. 3) So as to allow the device to communicate through the NGN, the customer can configure the association between the local SIP URI of the device (pre-configured in the device) and the CNG's public IMS identity (IMPU), or the device can use its own public SIP URI (pre-configured in the device) to send the register through the CNG SIP proxy. The authentication is handled directly by the CNG-SIP proxy B2BUA. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 23 CNG-B2BUA REGISTER (local SIP URI) 200 (OK) REGISTER (IMPI,IMPU, Aut_header) 200 OK Adds challenge response 401 (Unauthorized) REGISTER (IMPI,IMPU, response) Adds Authorization header IMS Core Network CND with a local Id CNG-B2BUA REGISTER (local SIP URI) 200 (OK) REGISTER (IMPI,IMPU, Aut_header) 200 OK Adds challenge response 401 (Unauthorized) REGISTER (IMPI,IMPU, response) Adds Authorization header IMS Core Network CND with a local Id Figure 7: Non-IMS capable CND attachment and local/IMS registration Other devices shall use their own IMPU (pre-configured in the device) to send the register directly to the NGN proxy. This should also be done through the CNG SIP proxy. It should be the case for instance for a nomadic device which should be able to register locally at the CNG level as it could use the option 120 not to know its registrar already provisioned, but to discover the outbound proxy within the CNG. This would give the opportunity for an IMS device to be involved in local SIP communications managed through the CNG SIP Proxy (e.g. call transfer). This case is described in figure 8. with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP proxy 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP proxy B2BUA 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) IMS CND Figure 8: IMS capable CND attachment and IMS registration NOTE: This scenario is not possible in case of IMS device implementing the AKA authentication mechanisms (IPsec tunnel through the CNG). ETSI ETSI TS 185 003 V2.3.1 (2009-06) 24
|
049271446448601336483ab2574d528a
|
185 003
|
7.3.2 Outgoing call
| |
049271446448601336483ab2574d528a
|
185 003
|
7.3.2.1 SIP non-IMS CND
|
The SIP non-IMS device is provided with a public SIP URI or a local identity, as is the case in figure 9. INVITE (local SIP URI) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "fixed" terminal IMS core network 1xx ACK INVITE (IMPU) RTP/RTCP CND with a local Id (eg device_kitchen) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "fixed" terminal CNG SIP Proxy ACK INVITE (IMPU) RTP/RTCP CND with a local Id (eg device_kitchen) 200 OK 1xx ACK INVITE (local SIP URI) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "fixed" terminal IMS core network 1xx ACK INVITE (IMPU) RTP/RTCP CND with a local Id (eg device_kitchen) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "fixed" terminal CNG SIP Proxy ACK INVITE (IMPU) RTP/RTCP CND with a local Id (eg device_kitchen) 200 OK 1xx ACK NOTE: The 407 (challenge) is optional. Figure 9: Outgoing call for a non-IMS CND For SIP non-IMS CND, the CNG SIP proxy can replace the device local SIP URI with its own IMPU in the SIP INVITE, in case the CNG IMPU is associated with several CNDs (only one register is sent to the P-CSCF for several devices with the same tel number). ETSI ETSI TS 185 003 V2.3.1 (2009-06) 25
|
049271446448601336483ab2574d528a
|
185 003
|
7.3.2.2 IMS CND
|
INVITE (IMPU) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "nomadic" terminal SIP-IMS Proxy SIP core network 1xx ACK INVITE (IMPU) RTP/RTCP IMS CND CNG-SIP Proxy B2BUA IMS Core Network 407 (challenge) INVITE (IMPU, IMPI, challenge response 1xx 200 OK ACK NOTE: The 407 (challenge) is optional. Figure 10: Outgoing call for a IMS CND
|
049271446448601336483ab2574d528a
|
185 003
|
7.3.3 Internal call
|
The CNG SIP proxy can route local call between two devices of the CPN. No NGN resource is used to establish internal call. SIP signalling is not forwarded to core network and media streams are kept on the CPN directly between endpoints. The SIP proxy identifies internal call after the analysis of the called party number. The customer can dial: a) Directly the local identity of the device (ex: kitchen, dect, John, etc.). b) Or a private numbering plan. The commutation table is configurable for instance by the customer on the web server of the CNG. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 26 Figure 11: Internal call
|
049271446448601336483ab2574d528a
|
185 003
|
7.3.4 Admission Control
|
The CNG-Admission Control Function (CNG-ACF) module calculates the available resources on the access line during the establishment of a new session, possibly limiting the number of sessions in advance, before the direct intervention of the RACS on the NGN side. As it has no means of reading signalling protocols other than unencrypted SIP, the result of this calculation may be wrong for the access line because of an underestimation of the total number of sessions. Still RACS will assure the proper result for the connection admission control over the access line and limit the session setup [i.7]. The module is considered as optional (as Gm' and Gm interfaces related to the SIP proxy). The objective is to guaranty the quality of service for each new session and existing sessions previously established. The B2BUA extracts from SIP message the SDP offer and announced capabilities (codec audio, video, etc.). It asks to the CNG-ACF if announced capabilities are compliant with the available resource. The CNG-ACF module returns 3 responses: a) OK: a) The resource is available for all announced codecs. b) The initial SIP message is forwarded without any change on SDP part. SIP 1 SIP 2 CNG - SIP Proxy B2BUA INVITE (local SIP URI_2) INVITE (local SIP URI_2) 1xx 1xx 200 OK 200 OK ACK ACK RTP/RTCP SIP 1 SIP 2 CNG - SIP Proxy B2BUA INVITE (local SIP URI_2) INVITE (local SIP URI_2) 1xx 1xx 200 OK 200 OK ACK ACK RTP/RTCP ETSI ETSI TS 185 003 V2.3.1 (2009-06) 27 b) OK with restriction: a) The initial SIP message is modified (incompatible codecs are suppressed from SDP part) and then forwarded. b) The session can be established with an acceptable codec for network resource. c) Not OK: a) The B2BUA rejects the session establishment. NOTE: The SIP profiles can be different from one side of the B2BUA to another. Figure 12: Admission Control within the CNG L2 CNG Caller CNG SIP Proxy B2BUA Callee SIP messagewith a SDPoffer 1. Analysis of L2 available resources 2. Analysis of announced codecs 3. Selection of the codecs compatible with available bitrate If CAC returns that all announced codecsare compatible with available bitrate , the SIP messageis forwardedwithoutmodification If no codec is compatiblewith available bitrate, SIP error responseis sent If CAC returns that some codecs are incompatible with available bitrate , the SIP-IMS proxy modifies the original SDP by suppressing these codecs and forwarding this modified SIP message CND LAN WAN SIP Codecreference • G711: bitrate = 100Kbps ; cpu=7% • G722: bitrate = 100Kbps ; cpu =7% • G729: bitrate = 45Kps ; cpu = 5% • H263:bitrate = 156Kbps ; cpu=9% SIP Dynamical pointers # bitrate #CPU ACF media CNG SIP Proxy B2BUA CNG ETSI ETSI TS 185 003 V2.3.1 (2009-06) 28
|
049271446448601336483ab2574d528a
|
185 003
|
7.4 Remote Access flows
| |
049271446448601336483ab2574d528a
|
185 003
|
7.4.1 Remote Access Connection Set-up
|
This clause describes one procedure where information of which CND's are registered in the CNG and therefore accessible via Remote Access, is retrieved by the remote UE. The UE provides an application linking the procedures for Remote Access services. Figure 13: Remote Access Connection Setup Prerequisite, the CND in the CPN has to be registered (e.g. using UPnP or similar procedure) to the CNG before the following take place: 1) The remote access menu initiates SIP INVITE to the users home CNG. The request is granted by the IMS NW and sent to CNG. 2) CNG checks if the request shall be granted. It initiates mapping of addresses and ports and prepares for the remote access procedures by returning SIP 200 OK. Optionally a secure tunnel is then setup between the remote UE and the CNG. 3) HTTP GET carries (e.g. DLNA or similar procedure) requesting CND information including device types and identities to be provided. 4) CNG checks its present CND registrations, DB info (e.g. DLNA or similar) and returns the CND's device type, identity and pointer to CND in HTTP 200 OK. 5) This session is terminated with SIP BYE. The Remote UE now holds the list of available CND's, their identities and types. The end user chooses the CND of interest and initiates a new session according to the following. 6) SIP INVITE is now sent addressing the CND (in the SDP part). The request is granted by the IMS NW and sent to the CNG. SIP ACK SIP ACK Remote UE IMS Core Network CNG CND CND (1) SIP INVITE:(Home CNG) SIP INVITE:(Home CNG) CNG – CND Info exchange CNG – CND Info exchange (2) SIP 200 OK SIP 200 OK (3) HTTP GET: Device info request (4) HTTP 200 OK: Device info response (5) SIP BYE (6) SIP INVITE:((HomeCNG(CND)) SIP INVITE:(HomeCNG(CND)) (7) SIP 200 OK SIP 200 OK ETSI ETSI TS 185 003 V2.3.1 (2009-06) 29 7) CNG checks if the request shall be granted. It initiates mapping of addresses and ports and prepares for the remote access procedures by returning SIP 200 OK. Optionally a secure tunnel is then setup between the remote UE and the CNG. NOTE: This initiated session will be terminated (SIP BYE) in the end of the sequence.
|
049271446448601336483ab2574d528a
|
185 003
|
7.4.2 Download of content using HTTP
|
This clause describes the procedure where content is downloaded from a particular CND to the remote UE. The information about which CND's are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connection set-up procedure displayed in clause 7.4.1: 1) The Remote UE points out the CND of interest using the path descriptor received under point 4 in clause 7.3.1. 2) CND sends an acknowledgement back to the Remote UE also indicating where to retrieve additional info. 3) The Remote UE sends a request (e.g. UPnP or similar) to the CND for additional device and service information. 4) CND responds with information about the services supported in the device. 5) The Remote UE browses the directories (e.g. with UPnP or similar procedure) where available content for download are located and makes a choice. 6) CND is responding with information (e.g. UPnP or similar) about the content URL/URI. 7) The Remote UE requests the download of data by addressing the content URL/URI. 8) The particular file is downloaded to the UE. 9) The connection is terminated with SIP BYE tearing down the session initiated by SIP INVITE in RA Connection setup described in clause 7.3.1, point 6. In case of consecutive download requests the first four steps do not need to be repeated if the CND device and service information is cached in the Remote UE. In the following flows the HTTP protocol is shown as an example although other alternative choices could be considered. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 30 Remote UE IMS Core Network (1) HTTP GET (Path Descriptor) (5) HTTP (Content Directory Browse) (7) HTTP GET (URL to content) (9) SIP BYE Connection setup procedure (2) HTTP 200 OK (3)HTTP GET (Device and service info) (4) HTTP 200 OK (8) HTTP 200 OK (Content download) (6) HTTP (Content URL) CNG CND Figure 14: Download of content using HTTP
|
049271446448601336483ab2574d528a
|
185 003
|
7.4.3 Upload of content using HTTP
|
This clause describes the procedure where content is uploaded to a particular CND from the remote UE. The information about which CND's are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connection Setup procedure in clause 7.4.1: 1) The Remote UE points out the CND of interest using the path descriptor received under point 4 in clause 7.3.1. 2) CND sends an acknowledgement back to the Remote UE also indicating where to retrieve additional information. 3) The Remote UE sends a request (e.g. UPnP or similar) to the CND for additional device and service information. 4) CND responds with information about the services supported in the device. 5) The Remote UE browses the directories where content can be uploaded. 6) CND is responding with information about the content directory URL/URI. 7) The user selects the folder where content will be uploaded. An object is created for the pending file. 8) The Object description and URL/URI address is received by Remote UE. 9) The particular file (object) is uploaded to the CND. 10) CND is acknowledging the upload of content. 11) Disconnection is initiated with SIP BYE terminating the session initiated by SIP INVITE in RA Connection setup described in clause 7.3.1, point 6. In case of consecutive upload requests the first four steps do not need to be repeated if the CND device and service information is cached in the Remote UE . ETSI ETSI TS 185 003 V2.3.1 (2009-06) 31 In the following flows the HTTP protocol is shown as an example although other alternative choices could be considered. (1) HTTP GET (Path Descriptor) (5) HTTP (Content Directory Browse) (9) HTTP POST (Content) (11) SIP BYE Connection setup procedure (2) HTTP 200 OK (3) HTTP GET (Device and service info) (4) HTTP 200 OK (10) HTTP 200 OK (6) HTTP (Content URL) (7) HTTP (Create Object) (8) HTTP 200 OK (URL and Object Id) Remote UE IMS Core Network CNG CND Figure 15: Upload of content using HTTP ETSI ETSI TS 185 003 V2.3.1 (2009-06) 32 Annex A (informative): Bibliography ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". HGI Forum specifications. IETF NAPT traversal Working Groups: BEHAVE for STUN TURN methods, MMUSIC for ICE, SIP for SIP Outbound. ETSI ETSI TS 185 003 V2.3.1 (2009-06) 33 Annex B (informative): Change History Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 06-05-08 WG5-02-008 001 1 F Clarification on CNG Admission Control Function 2.0.0 2.0.1 06-05-08 WG5-02-009 002 1 F Clarification on CNG Communication Services Media Function 2.0.0 2.0.1 06-05-08 WG5-02-010 003 F Clarification on SIP Multi-mode 2.0.0 2.0.1 06-05-08 WG5-02-013 004 1 F Early deployment IMS signalling path through CNG- Proxy B2BUA 2.0.0 2.0.1 02-07-08 18WTD119 005 1 F Correction of the RA setup signalling flows 2.0.1 2.0.2 02-07-08 18WTD233 006 1 D Clarifications in relation to Remote Access concerning RADA and RATA 2.0.1 2.0.2 02-07-08 18WTD336 007 D Clarification in specification due to comments from HGI 2.0.1 2.0.2 11-07-08 All CRs approved at TISPAN#18 2.0.2 2.1.1 26-09-08 18bTD323 008 1 D CNG – HGI Alignment 2.1.1 2.1.2 07-11-08 All CRs approved at TISPAN#19 2.1.2 2.2.1 22-01-09 19tTD223R1 009 1 F Dj' reference point between the IPTV CND and the CNG 2.2.1 2.2.2 Publication 2.2.2 2.3.1 ETSI ETSI TS 185 003 V2.3.1 (2009-06) 34 History Document history V2.0.0 March 2008 Publication V2.3.1 June 2009 Publication
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
1 Scope
|
The present document provides a set of generic QoS concepts for NGN, provides a QoS Framework Model and describes the requirements for the delivery of QoS in TISPAN NGN. The present document is release independent.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
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. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. [1] ITU-T Recommendation G.1000 (2001): "Communications Quality of Service: A framework and definitions". [2] ITU-T Recommendation G.1010 (2001): "End-user multimedia QoS categories". [3] ITU-T Recommendation M.2301 (2002): "Performance objectives and procedures for provisioning and maintenance of IP-based networks". [4] ITU-T Recommendation Y.1540 (2002): "Internet protocol data communication service - IP packet transfer and availability performance parameters". [5] ITU-T Recommendation Y.1541 (2002): "Network performance objectives for IP-based services". [6] ETSI TS 123 107: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Quality of Service (QoS) concept and architecture (3GPP TS 23.107 Release 6)". [7] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". [8] ITU-T Recommendation G.729: "Coding of speech at 8 kbit/s using conjugate-structure algebraic- code-excited linear-prediction (CS-ACELP)". [9] IETF RFC 3951: "Internet Low Bit Rate Codec (iLBC)". [10] ITU-T Recommendation G.722.2: "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)". [11] ISO/IEC 14496-3: "Information technology - Coding of audio-visual objects - Part 3: Audio". [12] ITU-T Recommendation H.263: "Video coding for low bit rate communication". [13] ITU-T Recommendation H.264: "Advanced video coding for generic audiovisual services". ETSI ETSI TS 185 001 V1.1.1 (2005-11) 7
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
3 Definitions and abbreviations
| |
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: guaranteed QoS: traffic delivery service with numerical bounds on some or all of the QoS parameters NOTE: These bounds may be physical limits, or enforced limits such as those encountered through mechanisms like rate policing. The bounds may result from designating a class of network performance objectives for packet transfer. relative QoS: traffic delivery service without absolute bounds on the achieved bandwidth, packet delay or packet loss rates NOTE: It describes the circumstances where certain classes of traffic are handled differently from other classes of traffic, and the classes achieve different levels of QoS.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AMR Adaptive MultiRate speech codec ATM Asynchronous Transfer Mode BER Bit Error Rate CCRP Call/Connection Control Reference Point CDMA Code Division Multiple Access COPS Common Open Policy Service DCME Digital Circuit Multiplication Equipment DECT Digital Enhanced Cordless Telecommunications DSL Digital Subscriber Line ER Error Ratio GSM Global System for Mobile communication IPDV IP Packet Delay Variation IPER IP Packet Error Ratio IPLR IP Packet Loss Ratio IPTD IP Packet Transfer Delay LAN Local Area Network MPEG Moving Picture Experts Group MPLS Multi Protocol Label Switching NCRP Network Control Reference Point NGN Next Generation Network NSIS Next Steps In Signalling PSTN Public Switched Telephone Network QoS Quality of Service RACF Resource and Admission Control Functions RACS Resource and Admission Control Subsystem RSVP Resource ReserVation Protocol SCRP Switch Control Reference Point SDU Service Data Unit SIP Session Initiation Protocol SPDF Service Policy Decision Functions UMTS Universal Mobile Telecommunication System UNI User-to-Network Interface VoIP Voice over IP VTC Video TeleConferencing service WB-AMR Wide Band - Adaptive MultiRate speech codec WLAN Wireless Local Area Network ETSI ETSI TS 185 001 V1.1.1 (2005-11) 8
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
4 Introduction
|
The present document defines the generic QoS concepts for NGN and provides a QoS Framework Model. The present document is release independent. TISPAN deliverables which have a bearing on QoS should indicate, which QoS requirements are met for each release. The QoS requirements include QoS classes, codecs, QoS control mechanisms, QoS architecture, QoS signalling. Annex A identifies, for information, a list of Audio and Video Codecs for conversational applications.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
5 QoS Generic concepts
| |
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
5.1 QoS and Network Performance
|
The distinction between QoS and Network Performance, as well as the various viewpoints of QoS, are illustrated in ITU-T Recommendation G.1000 [1]. The end-to-end service as well as a number of in-network services have QoS requirements. These must be fulfilled by the network in order to meet the QoS requirements. In terms of network performance, we engineer and monitor the network so that services get the QoS they require.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
5.2 Performance objectives
|
The NGN performance objectives should be based on the ITU-T Recommendation M.2301 [3]. This recommendation provides performance objectives and procedures for provisioning and maintenance of IP networks owned by different operators. This is regardless of the transport technology supporting the IP network and the higher layers to be implemented over IP. These objectives include error performance, delay performance and availability. This Recommendation defines the parameters and their associated objectives based on the principles in ITU-T Recommendation Y.1540 [4]. ITU-T Recommendation Y.1540 [4] also provides, in an Appendix, guidance on the performance objectives and limits for IP network resources (e.g. routers, sub-networks etc.), which are owned and managed by a single operator. However, the allocation of performance inside an IP network operator's domain or network portion is the responsibility of each operator to ensure the end-to-end performance over their domain or network portion meets the limits given in ITU-T Recommendation Y.1540 [4]. ITU-T Recommendation Y.1540 [4] provides a general framework for applying these limits (see clause 8).
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
5.3 End-to-end and bearer QoS
|
The standardization work traditionally distinguishes between tele-services, which operated across terminals and networks (e.g. mouth-ear for voice) and bearer services that excluded terminals (from UNI to UNI). In an opened and deregulated market, it is not always possible to control the user's domestic installation. Previously, the QoS specifications have been focused on end-to-end QoS. But in an NGN environment, the QoS at the bearer service level should be taken into account. The bearer service level is the level addressed by ITU-T Recommendation Y.1541 [5] and TS 123 107 [6]. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 9 NGN Access domain NGN Core domain #1 CPN NNI UNI NNI Access Network Access Network Core Network Core Network Access Network Access Network NGN Core domain #2 NGN Access domain NNI UNI CPN Bearer QoS End-to-end QoS Figure 1: End-to-end QoS and Bearer QoS
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
5.4 Guaranteed and relative QoS
|
NGN shall support the development of two different models of service assurance: guaranteed and relative QoS. Guaranteed QoS: This term refers to a traffic delivery service with numerical bounds on some or all of the QoS parameters. These bounds may be physical limits, or enforced limits such as those encountered through mechanisms like rate policing. The bounds may result from designating a class of network performance objectives for packet transfer. Relative QoS: This term refers to a traffic delivery service without absolute bounds on the achieved bandwidth, packet delay or packet loss rates. It describes the circumstances where certain classes of traffic are handled differently from other classes of traffic, and the classes achieve different levels of QoS.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
6 QoS Framework Model
| |
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
6.1 Framework Model
|
In order to provide a global and homogenous view of functions needed to support end-to-end services in NGN, a framework model is useful. This model should allow the possibility to identify the different processes and functions implied in QoS both in service and transport stratum. This model is not an architecture model. The mapping of this model on a functional architecture is outside the scope of the present document. The decision to standardize or not the functions identified in this model is also outside the scope of the present document. The framework model is based upon the customer-provider relationship. The provider provides a service to the customer. The customer could be either an end-user or another provider. A customer sends a request to initiate a demand to the provider. The framework (figure 2) introduces horizontally three processes, and vertically six levels to structure functions and data. A seventh vertical level is devoted to network element functions, also called transport functions. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 10 SERVICE MEDIATION SERVICE EXECUTION OFFERS RESOURCE PROCESSING NETWORK ELEMENT INVOCATION (DYNAMIC CONTROL PLANE) SUBSCRIPTION/ PROVISIONING Customer AFTER - SALES PROCESSES / LEVELS Service request Service use Transport RESOURCE MEDIATION NETWORK PROCESSING NETWORK ELEMENT PROCESSING SERVICE PROCESSING Figure 2: Framework model
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
6.1.1 Processes
|
Processes are related to the service lifecycle. They structure actions undertaken by providers in answer to customers' requests. The proposed processes are the following: 1) Subscription/Provisioning: this process deals with actions that follow customers' subscriptions: customer care (contracts, customer profiles), dimensioning, deployment and network configuration management. 2) Invocation: following a service invocation request, this process is in charge of service and resource controls to support services in real-time (or on-demand). 3) After-Sales: network performance report, quality of services and faults are handled by this process. It also manages measurements and monitoring. Customers might ask for QoS information relevant to the service. In this framework, we identify two management processes (Subscription/Provisioning and After-Sales), and one process which corresponds to the dynamic control plane (Invocation).
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
6.1.2 Levels
|
Each process is divided into two parts: Services Processing and Resources Processing, each comprising of three levels. The proposed levels are the following: 1) Service Mediation or Front Office: this optional level is intermediary between the customer and service offers. It manages catalogues of service providers, for example in the form of "yellow pages" indicating the main attributes of provided services. It can deal with user requests to direct them to the appropriate service providers. 2) Offers or Back Office: this level is intermediary between the service mediation and service execution. It proposes offers, i.e. bundles of one or more services to the customer. It also deals with the customer's subscription, the customer's identification and authentication in order to allow him to use the subscribed services in an offer. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 11 3) Service Execution: this level is in charge of the planning and the development of services. In the Invocation process, it ensures the execution of a telecommunications service that is dynamically requested by the customer. 4) Resource Mediation: this level is intermediary between Service Execution and resource processing. It first ensures the adaptation between service instance and resources by translating service parameters into resource parameters. This level is then in charge of resource positioning in order to support the customer's service. It identifies the sub-networks in accordance with the needed QoS. This level makes the Resource Processing independent from the Service Processing and therefore is particularly relevant in NGN architectures. 5) Network Resource Processing: this level is in charge of network resource deployment in order to meet demands of the customer's service. It identifies and monitors resources required to support the service. It computes topological paths (nodes, interfaces/links) and constraints to transfer flows. 6) Network Element Resource Processing: this level is in charge of resource network element deployment. It identifies and monitors resources at the Network Element level (matrix connection, interface, port, etc.). These functions are in charge of two main actions in the Invocation process: to select physical paths and to route data. 7) Network Element or Transport: this level corresponds to transport functions. An example is termination functions (traffic filtering, policing, etc.).
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
6.2 Application to QoS
|
The previous general framework model can be applied to QoS (figure 3). SERVICE MEDIATION SERVICE EXECUTION OFFERS Service Use Request (QoS) Service use RESOURCE MEDIATION NETWORK PROCESSING NETWORK ELEMENT PROCESSING QoS SUBSCRIPTION SELECTION OF SERVICE PROVIDER , QoS , COST QoS REQUIREMENT E2E RESOURCE QoS PERFORMANCE QoS-BASED RESOURCE SELECTION QoS - BASED NETWORK RESOURCE CONFIGURATION NETWORK RESOURCE QoS CONTROL MEASURED RESOURCE STATE NET. ELEMENT CONFIG. & QoS RESOURCE PROVISIONAL STATES NET. ELEMENT RESOURCE QoS CONTROL FINAL QoS QoS Monitoring & Measures Provisioning (in advance) Invocation (on demand) EXECUTION MEASURED RESOURCE STATE Customer FINAL QoS INVOCATION (CONTROL PLANE) SUBSCRIPTION/ PROVISIONING AFTER - SALES 1 1 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 14 14 15 15 Transport QoS ACTIVATION 2 2 MEASURED RESOURCE STATE 13 13 NETWORK ELEMENT Service Subscription Request Figure 3: QoS Framework Model ETSI ETSI TS 185 001 V1.1.1 (2005-11) 12 Following a customer's subscription request, in the Subscription/Provisioning process: 1) The Offers level functions manage service subscription. It formalizes QoS contract negotiated between the customer and the provider. 2) The Service Execution level functions activate the QoS contract and orders the Resource Mediation level. 3) The Resource Mediation level functions manage information related to end-to-end resource performances (connection, access network, etc.). It binds QoS characteristics and network resource performances. 4) The Network Resource Processing level functions manage network resource configuration and takes into account QoS constraints to dimension necessary resources in macroscopic way: interface, buffer, etc. 5) The Network Element Resource Processing level functions manage network element configuration parameters and maintains provisional states of resource occupation. Following a customer's service invocation (or use) request, in the Invocation process: 6) The Offers level functions control the correspondence between the QoS subscribed by the customer and the QoS requested by the customer. 7) The Service Execution level function handles QoS data suitable to the customer's request. 8) The Resource Mediation level functions select the end-to-end resource support (access network, sub-networks, core network, etc.) corresponding to the above QoS constraints, with respect to resource performances and the state of resources managed in the Subscription/Provisioning process. 9) The Network Resource Processing level functions control and includes an admission control on the basis of QoS constraints with regards to the estimated network resources state, obtained by QoS monitoring and measures in the After-Sales process, and potentially to the amount of reserved resources. 10) The Network Element Resource Processing level functions control and includes an admission control on the basis of the real resources states node per node. This function is vital to guarantee QoS on-demand. At the resources level, flows are switched/forwarded in accordance with the traffic contract. Finally, in the After-Sales process (11 to 15), based on the network monitoring and measurements, information is obtained about the estimated (or operational) state of resources (residual bandwidth, queue occupation, etc.), and the QoS experienced by the customer's service use. All this information would be used to improve the resource planning and the QoS offered to customers. In order to support to the absolute QoS, it would be useful to calculate the real state of reserved resources. Thus the Reserved Resource State database, previously identified in the Subscription/Provisioning process, is essential to provide absolute QoS.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
7 NGN QoS Requirements
|
The TISPAN_NGN should be able to support a wide range of QoS-enabled services. To offer these QoS services, it is necessary to define QoS Control mechanisms, QoS Control Architecture and Control mechanisms and QoS Control Signalling. The present document is release independent. TISPAN deliverables which have a bearing on QoS should indicate, which QoS requirements are met for each release. The NGN QoS classes should be based on the ITU-T Recommendation Y.1541 [5] "IP Network QoS classes" and TS 123 107 [6] "UMTS QoS classes". The NGN should support different types of codecs and shall support a codecs negotiation between NGN entities (terminal, network elements). The NGN should take account different QoS control mechanisms corresponding to different technologies and possibly different business models. The following three scenarios have been identified: a) Proxied QoS with policy-push: The client's terminal or Home gateway does not itself support native QoS signalling mechanisms. It requests a specific service to the Application Manager, which determines the QoS needs for this service (as in xDSL network). ETSI ETSI TS 185 001 V1.1.1 (2005-11) 13 b) User-requested QoS with policy-push: The client is able to request its QoS needs and the terminal or the Home gateway is capable to send QoS requests over signalling and/or management protocols for its own QoS needs, but requires prior authorization from an Application Manager (as in Mobile Network). c) User-requested QoS with policy-pull: The user's terminal or Home gateway is capable of sending QoS Request over signalling and management protocols for its own QoS needs, and does not require prior authorization. The NGN QoS architecture should be able to manage different types of access network (e.g. xDSL, 3GPP access network, etc.). The NGN QoS Control Signalling should be based on already defined protocols or protocols under development (e.g. RSVP, COPS, NSIS, etc.).
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8 QoS Classes
|
The standardization work traditionally distinguishes between teleservices, which operated across terminals and networks (e.g. mouth-ear for voice) and bearer services that excluded terminals (from UNI to UNI). In an opened and deregulated market, it is not always possible to control the user's domestic installation. Previously, the QoS specifications have been focused on end-to-end QoS. But in an NGN environment, the network performance at the bearer service level should be taken into account. The NGN QoS classes should be based on the ITU-T Recommendation Y.1541 [5] "IP Network QoS classes" and TS 123 107 [6] "UMTS QoS classes".
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.1 ITU-T Recommendation Y.1541 QoS Classes
|
Table 1 illustrates the ITU-T Recommendation Y.1541 [5] QoS classes and associated network performance objectives These specifications apply between user-network interfaces that delimit end-to-end IP flows. Table 1: Provisional IP network QoS class definitions and network performance objectives (ITU-T Recommendation Y.1541 [5]) QoS Classes Network performance parameter Nature of network performance objective Class 0 Class 1 Class 2 Class 3 Class 4 Class 5 Unspecified IPTD Upper bound on the mean IPTD 100 ms 400 ms 100 ms 400 ms 1 s U IPDV Upper bound on the 1 to 10-3 quantite of IPTD minus the minimum IPTD) 50 ms 50 ms U U U U IPLR Upper bound on the packet loss probability 1 × 10–3) 1 × 10–3 1 × 10–3 1 × 10–3 1 × 10–3 U IPER Upper bound 1 × 10–4 U NOTE: For clarity several important footnotes to this table contained in ITU-T Recommendation Y.1541 [5] have been omitted from the present document. Providers should consult the full table and notes in ITU-T Recommendation Y.1541 [5] before implementing these Classes. "U" means "unspecified" or "unbounded". Table 2 gives some guidance for the applicability and engineering of the network QoS Classes. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 14 Table 2: Guidance for IP QoS classes (ITU-T Recommendation Y.1541 [5]) QoS class Applications (examples) Node mechanisms Network techniques 0 Real-time, jitter sensitive, high interaction (VoIP, VTC) Constrained routing and distance 1 Real-time, jitter sensitive, interactive (VoIP, VTC) Separate queue with preferential servicing, traffic grooming Less constrained routing and distances 2 Transaction data, highly interactive (Signalling) Constrained routing and distance 3 Transaction data, interactive Separate queue, drop priority Less constrained routing and distances 4 Low loss only (short transactions, bulk data, video streaming) Long queue, drop priority Any route/path 5 Traditional applications of default IP networks Separate queue (lowest priority) Any route/path
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.2 TS 123 107 QoS Classes
|
Table 3 illustrates the TS 123 107 QoS classes. Table 3: Value ranges for UMTS Bearer Service Attributes (TS 123 107 [6]) Traffic class Conversational class Streaming class Interactive class Background class Maximum bitrate (kbps) ≤ 16 000 ≤ 16 000 ≤ 16 000 - overhead ≤ 16 000 - overhead Delivery order Yes/No Yes/No Yes/No Yes/No Maximum SDU size (octets) ≤ 1 500 or 1 502 ≤ 1 500 or 1 502 ≤ 1 500 or 1 502 ≤ 1 500 or 1 502 SDU format information Delivery of erroneous SDUs Yes/No/- Yes/No/- Yes/No/- Yes/No/- Residual BER 5*10-2, 10-2, 5 × 10-3, 10-3, 10-4, 10-5, 10-6 5 × 10-2, 10-2, 5 × 10-3, 10-3, 10-4, 10-5, 10-6 4 × 10-3, 10-5, 6 × 10-8 (7) 4 × 10-3, 10-5, 6 × 10-8 (7) SDU error ratio 10-2, 7 × 10-3, 10-3, 10-4, 10-5 10-1, 10-2, 7 × 10-3, 10-3, 10-4, 10-5 10-3, 10-4, 10-6 10-3, 10-4, 10-6 Transfer delay (ms) 100 - maximum value 300 (8) - maximum value Guaranteed bit rate (kbps) ≤ 16 000 ≤ 16 000 Traffic handling priority 1, 2, 3 Allocation/Retention priority 1, 2, 3 1, 2, 3 1, 2, 3 1, 2, 3 Source statistic descriptor Speech/unknown Speech/unknown Signalling Indication Yes/No 8.3 Mapping between ITU-T (Y.1541) and 3GPP (TS 123 107) QoS Classes
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.3.1 Context
|
The mapping between ITU-T Recommendation Y.1541 [5] and TS 123 107 [6] QoS Classes proposed in this clause is intended to allow both sets of Classes to be implemented in NGNs as they are. Modification and/or alignment of these two standards is not practicable so a mapping may be necessary for interworking purposes. The mapping proposed in this clause is optional. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 15
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.3.2 Hypothesis
|
This clause describes a QoS mapping (in each direction) between two networks: a 3GPP network providing UMTS service in accordance with the TS 123 107 QoS classes and bearer service attributes, and an IP network supporting assured-quality IP flows in accordance with ITU-T Recommendation Y.1541 [5]. For simplicity, the UMTS SDU is assumed to correspond to an IP packet. The end-to-end IP packet transfer service provided by the networks is intended to meet the end-to-end QoS objectives of ITU-T Recommendation Y.1541 [5]. The objective in mapping QoS classes (and bearer attribute values) between the UMTS network and the IP network is to divide the end-to end "impairment budget" for each ITU-T Recommendation Y.1541 [5] performance parameter (delay, delay variation, packet loss, packet error) appropriately between them. An equal division is assumed, e.g. each network would get 50 ms of a 100 ms end-to-end IPTD objective. A QoS translator in the interworking function between the UMTS network and the IP network maps QoS classes and attribute values between the two networks so as to ensure, where possible, that the end-to-end QoS objectives are met.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.3.3 Y.1541 to TS 123 107
|
The QoS translator maps Y.1541 class 0 to the UMTS conversational class, selecting the 10-4 value for the SDU error ratio attribute. The UMTS SDU transfer delay value (100 ms maximum) may or may not meet the example objective for the UMTS network portion (50 ms mean), depending on the SDU transfer delay distribution. The UMTS SDU error ratio value (10-4) meets the Y.1541 IPLR and IPER objectives assumed for the UMTS network portion (5 × 10-4, 5 × 10-5), since the former parameter definition combines the Y.1541 packet loss and packet error outcomes. The UMTS conversational class requirement to 'preserve time relation (variation) between information entities of the stream' relates qualitatively to the Y.1541 IPDV objective, but the end-to-end objective is not assured since the UMTS specification does not currently limit IPDV. ITU-T Recommendation Y.1541 [5] class 1 is mapped to the UMTS streaming class, selecting the 10-4 SDU error ratio value. The UMTS SDU transfer delay value (300 ms maximum) might or might not meet the example objective for the UMTS network portion (200 ms mean), depending on the delay distribution. The UMTS SDU error ratio value meets the example Y.1541 IPLR and IPER objectives as described for class 0 above. The Y.1541 IPDV objective is addressed qualitatively but without end-to-end assurance as noted above. ITU-T Recommendation Y.1541 [5] classes 2 to 4 is mapped to the UMTS interactive class with a 10-4 SDU error ratio. The three Y.1541 classes are mapped to different UMTS interactive class priority levels to reflect their different IPTD objectives; but as noted in TS 123 107 [6], these relative priorities may not provide assured quality levels. If more assured IPTD values are required, ITU-T Recommendation Y.1541 [5] classes 2 to 4 can be mapped to the UMTS conversational or streaming class. The SDU transfer delay limit of the UMTS conversational class (100 ms maximum) may or may not meet the example IPTD objective of class 2 (50 ms mean); it definitely meets the assumed IPTD objectives of classes 3 and 4 (200 ms and 500 ms mean, respectively). Similarly, the SDU transfer delay limit of the UMTS streaming class (300 ms maximum) may or may not meet the assumed IPTD objectives of classes 2 and 3 (50 ms and 200 ms mean respectively), but definitely meets the assumed IPTD objective of class 4 (500 ms mean). ITU-T Recommendation Y.1541 [5] class 5 is mapped to the UMTS background class. The mappings suggested above are probably the most reasonable ones, and they could meet the postulated IPLR and IPER requirements for all of theY.1541 classes. The suggested mappings do not meet the end-to-end delay requirements for some classes, and, as noted, place no quantitative bounds on end-to-end IPDV.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.3.4. TS 123 107 to Y.1541
|
The mapping from UMTS QoS classes to Y.1541 QoS classes essentially reverses that described in previous clause. The UMTS conversational class is mapped to Y.1541 class 0. The UMTS streaming class is mapped to Y.1541 class 1. The UMTS interactive class can be mapped to Y.1541 class 2, 3 or 4 depending on the specified traffic handling priority; the Y.1541 classes provide quantitative limits supporting up to three priority levels. The UMTS background class is mapped to Y.1541 class 5. These mappings do not meet the end-to-end delay requirements for some classes and place no quantitative bounds on end-to-end IPDV. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 16 Table 4 summaries the Relationships among ITU-T Recommendation Y.1541 [5] and TS 123 107 [6] UMTS QoS classes, parameters, and bearer attributes. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 17 Table 4: Relationships among ITU-T (Y.1541 [5]) and 3GPP (TS 123 107 [6]) UMTS QoS classes, parameters, and bearer attributes Real Time Best Effort Conversational - Preserve time relation (variation) between info entities of the stream - Conversational pattern (stringent and low delay) Streaming - Preserve time relation (variation) between info entities of the stream Interactive - Request/response pattern - Preserve payload content Background - Destination is not expecting data within a certain time - Preserve payload content 3GPP UMTS QoS Class (and Relevant Attribute Values) Y.1541 QoS Class (and Relevant Parameter Values) - Transfer delay: 100 ms (maximum value) - SDU error ratio (ER): 10-2, 7 × 103, 10-3, 10-4, 10-5 - Transfer delay: 300 ms (maximum value) - SDU error ratio (ER): 10-1, 10-2, 7 × 10-3, 10-3, 10-4, 10-5 - Transfer delay: "traffic handling priority" - SDU error ratio (ER): 10-3, 10-4, 10-6 - SDU error ratio (ER): 10-3, 10-4, 10-6 Class 0 IPTD < 100 ms IPDV < 50 ms IPLR < 10-3 IPER < 10-4 - IPTD is a mean value; transfer delay is a maximum - Y.1541 specifies IPDV limit - Y.1541 specifies IPLR/IPER; TS 123 107 [6] specifies SDU ER Class 1 IPTD < 400 ms IPDV < 50 ms IPLR < 10-3 IPER < 10-4 - IPTD is a mean value; transfer delay is a maximum - Y.1541 specifies IPDV limit - Y.1541 specifies IPLR/IPER; TS 123 107 [6] specifies SDU ER Class 2 IPTD < 100 ms IPLR < 10-3 IPER < 10-4 Class 3 IPTD ≤ 400 ms IPLR ≤ 10-3 IPER < 10-4 Class 4 IPTD < 1 second IPLR < 10-3 IPER < 10-4 - Y.1541 specifies IPTD limits; TS 123 107 [6] specifies "traffic handling priority" - Y.1541 specifies IPLR/IPER; - TS 123 107 [6] specifies SDU ER "target" Class 5 Best Effort - TS 123 107 [6] specifies SDU ER "target" ETSI ETSI TS 185 001 V1.1.1 (2005-11) 18
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
8.3.5 Limitations
|
The most problematic limitation for this mapping is the transfer delay. Transfer delay specifications are not translatable between the two recommendations as ITU-T Recommendation Y.1541 [5] specifies IPTD as a mean value, while TS 123 107 [6] specifies SDU transfer delay as a maximum. IPDV cannot currently be limited end-to-end because the UMTS specification does not define or quantitatively limit delay variation. The translations are more complicated in situations where the SDU and IP packet sizes substantially differ.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
9 Codecs
|
As the NGN should be open to the different networks (PSTN, UMTS, IP Network), the following principles define the use of audio and video codecs: 1) The NGN should support different types of codecs. It is recognized that some codecs play an important role in existing and emerging networks for audio and video services. EXAMPLE: ITU-T Recommendation G.711 [7] in circuit switched oriented networks, ITU-T Recommendation G.729 [8] in packet-based networks, AMR (and WB-AMR for Wideband telephony) in 3G UMTS networks. 2) The NGN shall support a wide and open list of codecs negotiation between NGN entities (terminal, network elements). 3) If needed, audio transcoding is performed to ensure end-to-end service interoperability. This may be performed for example by Residential or Home Gateways in customer premises, in Access, Media or Network Interconnect Gateways depending on the communication configuration. 4) Transcoding should be avoided wherever possible.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
10 QoS Scenarios
|
In NGN, different QoS control mechanisms could be used, corresponding to different technologies and possibly different business models. Those QoS support mechanisms have a strong influence on the architecture that may be needed to provide them. As a matter of fact, there exists several different alternatives, depending for instance on user terminal capabilities or on service needs. Three main scenarios can be identified from the viewpoint of the user terminal: 1) Proxied QoS with policy-push: The user terminal or the home gateway does not itself support native QoS signalling mechanisms. It requests a specific service to the Service controller, which determines the QoS needs for this service (as in xDSL network). 2) User-requested QoS with policy-push-pull: The user terminal or the home gateway is able to send explicit QoS requests for its own QoS needs, but before doing this, prior authorization from the Service controller is required (as in Mobile network). 3) User-requested QoS with policy-pull: The user's terminal or Home gateway is capable of sending QoS Request over signalling and management protocols for its own QoS needs using a Layer 3 QoS signalling protocol for its own QoS needs. The authorization for the QoS request is performed by the network on receipt of that request without prior authorization. Irrespective of the mechanism used to request QoS from the terminal, there exist several mechanisms to propagate QoS requests in a network and across network. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 19
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
10.1 Scenario 1 - Proxied QoS with policy-push
|
In the "Proxied QoS with policy-push" scenario, the user terminal or home gateway does not itself support native QoS signalling mechanisms. It requests an application-specific service by sending a "Service Request" to the Service controller. It is then the Service controller's responsibility to determine the QoS needs of the requested service, to request network authorization from the Network Resource Controller which then requests resource reservation to Core network and to Access network. A flow diagram for this scenario is provided in figure 4. For clarity, the flow diagrams do not show any ack/confirmation. Access network Core network NGN Transport Layer NGN Service Layer Core network Service controller NGN access domain NGN core domain #1 NGN core domain #2 CPN NNI UNI NNI NNI Service controller 1. Service Request 1bis. Service Request 2. Resource Request 3. Resource Reservation RACS Figure 4: Scenario 1 - Proxied QoS with policy-push This scenario does not require any resource reservation signalling capabilities on the user terminal and does not recommend any protocol for the service session requests. It is required to always go through the Service controller for any service request, including bandwidth reservation changes during a session. This scenario 1 supports single-phase resource reservation or two-phase resource reservation. • In the first case, the network enables immediate activation and usage of network resources by the end-user. • In the second case, the Service controller first asks for network QoS resources to be authorized and reserved. Once these resources have been reserved, the Service controller continues its dialogue with the user concerning the service. This two-phase reserve/commit model guarantees that access-network resources are available before offering service to the user and can also help protect against unauthorized use of service. In current xDSL networks, the QoS management is in conformance with this scenario 1. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 20
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
10.2 Scenario 2 - User-requested QoS with policy-push-pull
|
In scenario 2, "User-requested QoS with policy-push-pull", the user terminal or home gateways is capable of signalling and managing its own QoS resources but requires prior authorization of these requests via the Service controller. It requests an application-specific service by sending a "Service Request" to the Service controller. The Service controller is in charge of determining the QoS needs of the requested service and of requesting the network authorization from the Network resource controller. The Service Controller may relay to the end-user an associated Authorization token. Then, the terminal uses a specific signalling to request resource reservation (and commitment), for example a Layer 3 QoS signalling mechanism. The authorization token may be included in the QoS signalling request in order to facilitate authorization of the QoS request. This request could be managed in the Access Network with authorization of the Network Resource Controller (as in UMTS) or directly by the Network Resource Controller. A flow diagram for this scenario is provided in figure 5. This scenario has the ability to establish QoS reservation end-to-end since the IP QoS signalling proceeds on-path end- to-end and thus can be used (if desired) at any step along the end-to-end path (e.g. in Access network, in Core network, in subsequent core networks, in remote access networks, etc.), and allow multi-homing access which increases resiliency. It requires supporting a Layer 3 QoS signalling capability on the user terminal. Access network Core network NGN Transport Layer NGN Service Layer Core network Service controller NGN access domain NGN core domain #1 NGN core domain #2 CPN NNI UNI NNI NNI Service controller 1. Service Request 1bis. Service Request 4. QoS Authorization 3. QoS Signalling RACS 2. Policy enforcement 5. Resource Reservation Figure 5: Scenario 2 - User-requested QoS with policy-push-pull
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
10.3 Scenario 3 - User-requested QoS with policy-pull
|
The user's terminal or Home gateway is capable of sending QoS Request over signalling and management protocols for its own QoS needs, and does not require prior authorization. The user's terminal or Home gateway is capable of sending QoS Request over Layer 3 QoS signalling for its own QoS needs. Authorization for the QoS request is obtained 'on the fly' at the time where the QoS request is actually signalled. Unlike in Scenario 2, no communications with the Service Controller is needed prior to making the QoS request to obtain the corresponding authorization . A flow diagram for this scenario is provided in figure 6. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 21 This scenario does not require any communications with the Service Controller (in particular to obtain prior authorization for each QoS request), to avoid the need for the Network Resource Controller to maintain awareness of the relationship between end-users and their corresponding Policy Enforcement Functions, and to allow multi-homing access which increases resiliency. It is able to establish QoS reservation end-to-end since the IP QoS signalling proceeds on-path end-to-end and thus can be used (if desired) at any step along the end-to-end path (e.g. in Access network, in Core network, in subsequent core networks, at the boundary between core networks, in remote access networks, etc.). It requires supporting a Layer 3 QoS signalling capability on the user terminal. Access network Core network NGN Transport Layer NGN Service Layer Core network NGN access domain NGN core domain #1 NGN core domain #2 CPN NNI UNI NNI NNI Service controller 2. QoS Authorization 1. QoS Signalling RACS 3. Resource Reservation Figure 6: Scenario 3 - User-requested QoS with policy-pull
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
11 QoS Architecture Requirements
| |
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
11.1 Architectural requirements
|
The NGN QoS architecture should be able to manage different types of access network (xDSL, 3GPP access network, etc.) and different types of core networks, which could be in the same administrative domain or in different administrative domains. The NGN QoS Architecture should support the following requirements: 1) Support functions for QoS resource reservation, admission control service based local policy, network policy control and gate control. 2) Provide a mechanism to Application Functions in different multimedia service subsystems to reserve resources in the access transport and the core transport. 3) Support resource and admission control across multiple administrative domains. 4) Support the three QoS scenarios defined in clause 9, namely "Proxied QoS with policy-push", "User-requested QoS with policy-push" and "User-requested QoS with policy-pull". 5) Support both guaranteed QoS control and relative QoS control. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 22 6) Support different access transport technologies, including xDSL, UMTS, Cable, LAN, WLAN, Ethernet, MPLS, IP, ATM, etc. 7) Support different core transport technologies. 8) Be able to export charging information and session metrics.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
11.2 QoS architecture
|
The QoS architecture describes in figure 7 support the previous requirements. SPDF NCRP NGN Service stratum NGN Transport stratum Application Functions CCRP Other domains Core RACF 2 Core RACF 1 Access RACF n Access RACF 1 SCRP SCRP SCRP SCRP NCRP CPE Access Transport Functions Core Transport Functions Figure 7: QoS architecture The main component that manages QoS in NGN is the SPDF (Service Policy Decision Functions) and the RACF (Resource and Admission Control Functions). The SPDF makes policy decisions using policy rules and communicates these decisions to the RACF. The SPDF provides mediation between one or many Service Providers and one or many Network Resource Providers. The SPDF provides an abstract view of the transport functions to the content or application services. Its main advantage in the NGN architecture is to simplify and fasten the development of services by Service Providers. It also allows enforcing a clear separation between service-related functions and transport-related technologies as requested for the NGN. The SPDF acts as intermediary between service execution and resource processing. It first ensures the adaptation between service instance and resources by translating service parameters into resource parameters. This mediation is then in charge of resource positioning in order to support the customer's service. The SPDF is in charge of determining which Network Resource Providers should be involved in the support of a given service. It will then interact with each of them to obtain the necessary resources for the service. The SPDF makes the Resource Processing independent from the Service Processing. The functions includes in SPDF could evolve with the TISPAN Releases. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 23 The RACF receives requests for QoS resources from the SPDF indicating QoS characteristics (e.g. bandwidth). The RACF shall use the QoS information received from the SPDF to perform admission control, i.e. the RACF checks whether the requested QoS resources can be made available for the involved access. The RACF shall indicate to the SPDF whether a request for resources is granted or not. Two types of RACF should exist: • Access RACF (A-RACF). • Core RACF (C-RACF). Different instances of RACF could exist, both for A-RACF and C-RACF, depending of the network architecture. As the core network could involve different domains and different core network providers, each core network should have its own Core RACF. The NGN takes into account different types of access networks (e.g. Mobile network, DSL network, etc.). Each of these networks has it own characteristics and could also be managed by a specific provider. Each of these providers should have his own Access RACF. Three reference points are defined: • CCRP: Call/Connection Control Reference Point; • NCRP: Network Control Reference Point; • SCRP: Switch Control Reference Point.
|
ce0695ed7aa1e9a5cdc0ce2d8895c007
|
185 001
|
12 QoS Signalling Requirements
|
12.1 QoS Signalling Requirements in Call/Connection Control Reference Point The QoS signalling between the Service stratum and the RACS of Transport stratum on Call/Connection Control Reference Point should accomplish the following functions: • Request for resources: - Service stratum initiates a QoS request to the RACS of Transport Stratum. • Modification of the request: - In respect with some services, it may be necessary to modify the QoS requirements at anytime during the service running. According to Service stratum requirements, RACS of Transport Stratum modifies the bandwidth it applied for use last time. Multi-time modification is supported. • Resource status report: - In case of any change with the allocated resources (e.g. the resource seized by the connection is no longer available), the Transport Stratum should report it to the Service stratum. • Release of resources to support service: - When a service is terminated, the Service stratum should initiate a request to RACS of Transport Stratum for releasing the resource that has been requested to allocate. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 24 12.2 QoS Signalling Requirements in Network Control Reference Point For dynamic negotiation of QoS between service and access providers, as well as between service providers, a mechanism based on SLAs shall be provided. Optionally, QoS signalling over the Network Control Reference Point (NCRP) may be provided, depending on the interconnection schemes and agreements. The following basic functions should be accomplished in such case: • Request for resources. • Modification of request. • Resource status report (for reporting changes in the status of the allocated resources). • Release of resources. 12.3 QoS Signalling Requirements in Switch Control Reference Point Since the Switch Control Reference Point (SCRP) carries the configuration information related to QoS requests, the parameters of these messages may vary for different network layer technologies. This reference point transports the QoS parameters after being translated into network technology dependent parameters. There are the following requirements for QoS signalling between the RACS of Transport Stratum and the Transport Functions of Transport Stratum. • QoS configuration information delivery. • Modification of the QoS configuration information. • Resource status report. • Release of QoS configuration. ETSI ETSI TS 185 001 V1.1.1 (2005-11) 25 Annex A (informative): List of Audio and Video Codecs for conversational applications The following list identifies the most important and widely used audio and video codecs for conversational applications and the main foreseen ones (under ongoing standardization process). It is not an exhaustive list: Regional Standards or other Codecs with more limited use are not mentioned. For instance, Codecs dedicated to specific applications like military applications, satellite transmissions for which transmission conditions are very bad are not listed (these codecs have a very limited quality and aims rather at intelligibility). This list covers Audio Codecs in Narrow Band (300 Hz to 3 400 Hz) and in WideBand (≥7 kHz). ETSI ETSI TS 185 001 V1.1.1 (2005-11) 26 A.1 Audio Narrow Band (300 Hz to 3 400 Hz) Table A.1 Codec Name Annexes Bit rate (kbit/s) Main applications Comments G.711 64 Fixed Networks (Historical PSTN Networks, etc.), Intranets, Internet (Mandatory for H.323) G.726 A: uniform-quantized input and output B: Packet format 16 / 24 / 32 / 40 DECT Telephony G.727 A: uniform-quantized input and output 16 / 24 / 32 / 40 Transmission applications (DCME) Not widely deployed G.728 H: variable bit rate I: packet concealment J: voiceband-data applications in DCME 16 Videophony Very short frame (5 ms) enables low delay. Sensitive to transmission errors G.723.1 A: DTX/VAD/CNG B: floating point C: for mobiles 6.3 / 5.3 Videophony over PSTN and internet (H324) Frame = 30 ms Annex A variant mainly used G.729 A: Low complexity B: DTX/VAD/CNG C: Main Body in floating point C+: Annexes B, D and E in floating point D: 6.4 kbit/s E: 11.8 kbit/s F: DTX for Annex D G: DTX pour Annex E H: Switching between D & E I: Fixed point package of Main Body + Annexes B, D and E 8 Telephony over IP Frame = 10 ms Annexes A and B variants mainly used EFR 12.2 GSM Frame = 20 ms Most widely used GSM codec FR 13 First generation GSM codec Frame = 20 ms HR 5.6 GSM Frame = 20 ms ; Used locally for capacity reasons AMR + Annexes for VAD/DTX/CNG and erased frames 12.2 / 10.2 / 7.95 / 7.40 / 6.70 / 5.90 / 5.15 / 4.75 GSM and 3G mobile networks Frame = 20 ms AMR codec = 8 modes 12.2 / 10.2 / 7.95 / 7.40 / 6.70 / 5.90, 5.15 and 4,75 kbit/s. One mode (12,2 kbit/s) uses the same algorithm as EFR EVRC 8.55 / 4 / 0.8 Telephony over mobile CDMA (IS127) networks (USA, Asia., etc.) IS127 CDMA TIA and 3GPP2 Standard ETSI ETSI TS 185 001 V1.1.1 (2005-11) 27 Codec Name Annexes Bit rate (kbit/s) Main applications Comments SMV 8.55 / 4 /2 / 0.8 Telephony over mobile CDMA 2000 networks (USA, Asia, etc.) 3GPP2 Standard iLBC 13.33 / 15.2 Voice over IP IETF RFC 3951 [9] Patent free A.2 Audio Wide Band (50 Hz to 7 000 Hz) Table A.2 Codec Name Annexes Bit rate (kbit/s) Main applications Comments G.722 48 / 56 / 64 Teleconferencing Only on dedicated terminals G.722.1 A: Packet format, capability identifiers and capability parameters B: Floating-point implementation C: Broadband (14 kHz), low complexity 24 / 32 / 48 Teleconferencing Frame = 20 ms Quality limitation G.722.2/ AMRWB A: CNG B: DTX/VAD C: Floating point D: Test Vectors E: Frame Structure F: AMRWB in H245 I: Error Concealment for DTX/VAD/CNG 23.85 / 23.05/ 19.85 / 18.25/ 15.85 / 14.25/ 12.65 / 8.85/ 6.6 Wide Band Telephony Services (for fixed and mobile 3G networks) 3GPP/AMRWB = ITU-T Recommendation G.722.2 [10] UIT-T and 3GPP Standard Frame = 20 ms Only the mode 23.85 / 15.85 / 12.65 / 8.85 / 6.6 are mandatory in the 3GPP terminals. Nothing mandatory in the network VMR-WB Rate Set 2 13.3 / 6.2 / 2.7 / 1 WideBand Telephony Services (for CDMA2000) 3GPP2 Codec Frame = 20 ms One mode interoperable with AMRWB /G.722.2 @ 12.65 ETSI ETSI TS 185 001 V1.1.1 (2005-11) 28 A.3 Audio Narrow and WideBand Table A.3 Codec Name Annexes Bit rate (bit/s) Main applications Comments CELP MPEG Narrow Band: 3850, 4250, 4650, 4900, 5200,5500, 5700, 6000, 6200, 6300, 6600,6900, 7100, 7300, 7700, 8300, 8700, 9100, 9500, 9900, 10300, 10500, 10700, 11000, 11400, 11800,12000, 12200 Wide Band: 10900, 11500, 12100, 12700, 13300, 13900, 14300, 14700, 15900, 17100, 17900, 18700, 19500, 20300, 21100, 13600, 14200, 14800, 15400, 16000, 16600, 17000, 17400, 18600, 19800, 20600, 21400, 22200, 23000, 23800 Voice over IP Digital Radio Broadcast MPEG ISO/IEC 14496-3 [11] Standard (audio). Scalable mode possible but not used A.4 Foreseen extensions of existing Codecs (new Annexes under standardization in ITU-T) Ongoing standardization of 2 extensions of existing Standards (annexes) G.729: Wideband Scalable extension of G729. Table A.4 Codec Name Annexes Bit rate (kbit/s) Main applications Comments G729 J (called "G729EV") Scalable from 8 kbit/s to 32 kbit/s (Narrow Band to Wide Band) Wide Band Voice over IP, Internet applications Scalable embedded core compatible with ITU-T Recommendation G.729 [8]. Currently in Qualification phase ETSI ETSI TS 185 001 V1.1.1 (2005-11) 29 A.5 Video Table A.5 Codec Name Annexes Main applications Comments H.261 Standardized codec for H.320(ISDN)/H.323 videotelephony H.263 profile 0 level 10(QCIF-64 kbps max) to level 70 (720x576 – 16 384 kbit/s max) Standardized codec for H.323/H.324/SIP videotelephony. Used in MMS, streaming and broadcast services in 3GPP services Mandatory in 3GPP conversational and MMS services until release 6 H.263 Profile 3 (H.263+) level 10(QCIF-64 kbps max) to level 70(720x576 – 16 384 kbit/s max) Standardized codec for H.323/H.324/SIP videotelephony. Used in MMS, streaming and broadcast services in 3GPP services Optional in 3GPP conversational and mms services until release 6 Better error-robustness and subjective quality than profile 0 MPEG4 visual Simple Profile Level 0 H.264 Baseline profile, Baseline compatible main profile Standardized codec for H.323/H.324/SIP videotelephony. Introduced in MMS, streaming and broadcast services in 3GPP services Equal quality to ITU-T Recommendation H.263 [12] at half of the H.263 bitrate. Improve error-resilience capacity. Introduced in 3GPP services for release 6 ITU Standardization: ITU-T Recommendation H.264+ [13] (a lot of work items like reducing complexity, etc.) ETSI ETSI TS 185 001 V1.1.1 (2005-11) 30 History Document history V1.1.1 November 2005 Publication
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
1 Scope
|
The purpose of the present document is to provide the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for Network Integration Testing (NIT) to verify the overall compatibility of SIP networks based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in ES 283 003 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5]. The content of the present document is written according to the guidelines of ISO/IEC 9646-1 [3] and ETS 300 406 [5]. The following test specification and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. 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.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI ES 283 003 (V2.6.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [2] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [3] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 6 [5] ETSI ETS 300 406: "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology". [6] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [7] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)". [8] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI)". [9] ETSI TS 186 001-3 (V1.0.0): "Technical Committee for IMS Network Testing (INT); Network Integration Testing; Part 3: Test Suite Structure and Test Purposes (TSS&TP) for SIP-SIP". [10] ETSI TS 102 027-3 (V3.1.1): "Methods for Testing and Specification (MTS); Conformance Test Specification for SIP (IETF RFC 3261); Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma". [11] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [12] ETSI EG 202 568: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Testing: Methodology and Framework". [13] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". [14] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 124 504 (V8.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification (3GPP TS 24.504 version 8.5.0 Release 8)". [i.2] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification". [i.3] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method". [i.4] IETF RFC 3313: "Private Session Initiation Protocol (SIP) Extensions for Media Authorization". [i.5] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". [i.6] IETF RFC 3327: "Session Initiation Protocol (SIP) Extension Header Field for Registering Non- Adjacent Contacts". [i.7] IETF RFC 3329: "Security Mechanism Agreement for the Session Initiation Protocol (SIP)". [i.8] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". [i.9] IETF RFC 3455: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)". [i.10] IETF RFC 3608: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)". [i.11] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 7
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
3 Definitions and abbreviations
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [4] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [3]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3]. Lower Tester (LT): Refer to ISO/IEC 9646-1 [3]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CSCF Call Session Control Function EDS Encoding/Decoding System ETS Executable Test Suite IBCF Interconnection Border Control Function I-CSCF Interrogating CSCF IMS IP Multimedia Subsystem IP Internet Protocol IUT Implementation Under Test LT Lower Tester NIT Network Integration Testing PA Platform Adapter P-CSCF Proxy CSCF PICS Protocol Implementation Conformance Statement PIXIT Partial Protocol Implementation eXtra Information for Testing SA SUT Adapter S-CSCF Serving CSCF SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TC Test Case TCI TTCN-3 Control Interface TCP Transmission Control Protocol TE TTCN-3 Executable TL Test Logging TM Test Management TP Test Purpose TRI TTCN-3 Runtime Interface TS Test System TSI Test System Interface ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 8 TSS Test Suite Structure TTCN Testing and Test Control Notation TTCN-3 Testing and Test Control Notation version 3 UDP User Datagram Protocol UE User Equipment
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4 Abstract Test Method (ATM)
|
This clause describes the ATM used to test TS 186 001-3 [9].
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.1 Network architecture
|
The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF and possibly IBCF. Figure 1: SUT test interface
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.2 Protocol architecture
|
The Implementation Under Test (IUT) for which this test case specification applies consists of the IMS Supplementary Services, the underlying SIP Core Network and the SIP protocol (see figure 2). UE1 SUT (IMS) Gm UEx UE2 Gm UEy SIP protocol SIP protocol ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 9 IMS Supplementary Services SUT IMS CN SIP/IMS Extension SIP RFC 3891 SIP RFC 3261 Compression algorithms (Note 2) UDP TCP Security Algoritms (Note 2) IPV4/IPV6 (Note 1) (LAN) NOTE 1: Both IPV4 and IPV6 addressing should be supported. NOTE 2: Optional security and compression algorithms should be supported. Figure 2: SIP protocol architecture
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3 Test architecture
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.1 Test configuration
|
The target SUT to be covered by the test purposes of TS 186 001-3 [9] addresses the IMS functional entities that are accessible via the Gm interface. This clause introduces the test configuration that has been used for the test purpose definitions. The Test System (TS) simulates the behaviour of one or more UEs.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.1.1 Configurations using Gm interface only
|
The Gm interface is located between UE and the SUT. Figure 3: Test configuration CF_1 IMS SUT ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 10 Figure 4: Test configuration CF_2 Figure 5: Test configuration CF_3
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2 Test system architecture
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.1 General
|
Test systems that implement this ATS shall conform to the requirements as defined in this clause.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.2 Structure
|
An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 6 and also stated in ES 201 873-5 [7]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (SA) Platform Adapter (PA) Figure 6: Abstract Test System Architecture IMS SUT ue1home ue2home ue3home ue4home UE1 UE2 UE3 UE4 gm gm gm gm UE1atSUThome UE2atSUThome UE3atSUThome UE4atSUThome IMS SUT ue1home ue2home ue3home UE1 UE2 UE3 gm gm gm UE2atSUThome UE3atSUThome UE1atSUThome ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 11 A TS has two interfaces, the TTCN-3 Control Interface (TCI) and the TTCN-3 Runtime Interface (TRI), which specify the interface between Test Management (TM) and TTCN-3 Executable (TE) entities, and TE, SUT Adapter (SA) and Platform Adapter (PA) entities, respectively. Out of these two interfaces the TRI has been standardized in ES 201 873-5 [7], whereas the specification and implementation of the TCI is in ES 201 873-6 [8]. The part of TS that deals with interpretation and execution of TTCN-3 modules, i.e. the Executable Test Suite (ETS), is shown as part of the TTCN-3 Executable (TE). This ETS corresponds either to the executable code produced by a TTCN-3 compiler or a TTCN-3 interpreter from the TTCN-3 ATS in a TS implementation. The remaining part of the TS, which deals with any aspects that cannot be concluded from information being present in the TTCN-3 ATS alone, can be decomposed into Test Management (TM), SUT Adapter (SA) and Platform Adapter (PA) entities. In general, these entities cover a TS user interface, test execution control, test event logging, communication of test data with the SUT, and timer implementation. The part of SA used for SIP message transfer shall implement the TRI adaptation as well as the SIP transport protocol architecture described in clause 4.2. The Encoding/Decoding System (EDS) entity, as far as applied to SIP messages, with the TE and Test Logging (TL) entity within the TM shall comply with the conventions defined in clause 4.3.2 of TS 102 027-3 [10].
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA)
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.3.1 Sending and receiving SIP/IMS messages
|
Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (shown in figure 6). In order to forward messages received in the SA to the test suite and to send them to the SUT a clear und unique association between the TTCN-3 TSI ports and the real IP and port addresses used by the SUT is needed during test execution. The SA retrieves this information via values of TTCN-3 module parameters, i.e. PIXITs, and mappings to TSI ports, i.e. triMap operation invocations. TSI port names are the main source for the relating TSI ports with SUT IP addresses and ports. Table 1 provides the relationships for TSI ports and SUT IP addresses and ports. Table 1: TSI port mappings TSI port SUT (IP address, Port Id) Test system (IP address, Port id) UE1 PX_IMS_SUT_PCSCF1_IPADDR, PX_IMS_SUT_PCSCF1_PORT PX_IMS_TS_UE1_IPADDR, PX_IMS_TS_UE1_PORT UE2 PX_IMS_SUT_PCSCF2_IPADDR, PX_IMS_SUT_PCSCF2_PORT PX_IMS_TS_UE2_IPADDR, PX_IMS_TS_UE2_PORT UE3 PX_IMS_SUT_PCSCF3_IPADDR, PX_IMS_SUT_PCSCF3_PORT PX_IMS_TS_UE3_IPADDR, PX_IMS_TS_UE3_PORT UE4 PX_IMS_SUT_PCSCF4_IPADDR, PX_IMS_SUT_PCSCF4_PORT PX_IMS_TS_UE4_IPADDR, PX_IMS_TS_UE4_PORT NOTE 1: TSI portnames are defined in AtsNIT_SipSip_TestSystem module as part of the TestComponent type. Module parameters for the address information are defined in LibIms_PIXIT module (cp. section ATS library). NOTE 2: For each test configuration listed above a TTCN-3 configuration functions has been implemented with the required mapping and unmapping statements (cp. module AtsNIT_SipSip_TestConfiguration). Figure 7 illustrates the interconnection of TS and SUT in terms of signalling message associations. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 12 Figure 7: Abstract port association
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.3.2 Security and messages compression feature
|
Security transport layer, and signalling compression may be used transparently to the ATS.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.3.3 Additional SA constraints
|
In order to execute this test suite the SA should support: • communication channel handling (at least UDP and possibly also TCP); • IPv4 transport.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.4 Encoding/Decoding requirements
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers
|
SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use a EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messages. This EDS is not part of the ATS. Still all encoded messages, i.e. the messages as they are transmitted by the SA to or received by the SA from the SUT, shall be logged. The following terms shall be used for the conventions defined below: Syntactic delimiter syntactic delimiters are characters like "=" or ";" that are used to separate encoded values. LWS linear white spaces as defined in RFC 3261 [2]. Parameter name name of header parameters as defined in RFC 3261 [2]. Parameter value the value of a parameter as defined in RFC 3261 [2]. Undefined method an undefined method is a method other than: "INVITE", "ACK", , "BYE", "CANCEL" and "REGISTER", "MESSAGE", "REFER", "SUBSCRIBE", "NOTIFY", "PRACK", "UPDATE". TS ue1 port:sip ue2 port:sip SUT IMS ue3 ue4 port:sip port:sip IMSCN2 IMSCN1 IMSCN3 IMSCN4 ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 13 Undefined header an undefined header is a header other than general-header, entity-header, request-header and response header as defined in RFC 3261 [2]. Unexpected header an unexpected header is a header, which shall not be present in a specific request message. This definition complies to the definition of NOT APPLICABLE in RFC 3261 [2], section 20 for request messages. Decoder requirements TTCN-3 fields should not contain syntactic delimiters like white space, semicolon, equal characters etc. in fully decoded fields. Instead the information provided by a parser shall be used to build the decoded message in TTCN-3. Decoded messages shall use the TTCN-3 enumeration types where ever appropriate, e.g. for the method and the header field name. For charstring fields the following decoding rules shall be applied by the EDS: 1) Subsequent LWS shall compress to a single space character " ". 2) Decoded parameter names shall use only lower case letters. 3) Parameter values containing an integer value shall be decoded to a TTCN-3 integer value where a TTCN-3 integer type is used for a SIP parameter value. The following decoding rules shall be applied by the EDS to each received message in the following order: 1) In case a request message indicating an undefined method is received by the test system, the message shall not be passed in the TE to the ETS. However the message is subject to logging as defined in clause 4.3.3 ("Logging conventions"). 2) In case an undefined header has been received the header field shall be decoded as UndefinedHeader field. RFC 3261 [2] allows for multiple header field values of the same kind to either arrive in one or multiple occurrences of the corresponding header field. The SIP ATS has been written assuming only the first format. Therefore, should the EDS receive multiple header fields of the same kind in a SIP message, e.g. of a Via header field, it shall convert them into the equivalent single header field with multiple values. This can be achieved by adding the value of, e.g. the second received Via header field as the last value to the value(s) of the first Via header field. Encoder requirements Encoders shall follow all encoding rules that are defined in RFC 3261 [2] when encoding structured values received from templates. This applies in particular to but it is not restricted to section 7.3.1 of RFC 3261 [2]. Values of type Raw shall be send to the SUT without any modification. 4.3.2.4.2 Encoding/Decoding System requirements for basic SIP and SIP/IMS specific messages and headers In order to execute this test suite the following SIP messages and specific header should be supported by the encoding/decoding system. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 14 Table 2: IMS Basic and Specific messages Msg-Name RFC Gm tx Gm rx Requests ACK 3261 [2] x x BYE 3261 [2] x x INVITE 3261 [2] x x CANCEL 3261 [2] x x MESSAGE 3428 [i.8] x x NOTIFY 3265 [i.2] x x SUBSCRIBE 3265 [i.2] x - UPDATE 3311 [i.3] x x PRACK 3262 [i.5] x x Responses 100 3261 [2] x x 180 3261 [2] x x 181 3261 [2] x x 200 3261 [2] x x 3xx 3261 [2] x x 4xx 3261 [2] x x 401 3261 [2] x x 408 3261 [2] x x 480 3261 [2] x x 488 3261 [2] x x 5xx 3261 [2] x x Table 3: IMS specific headers Header-Name RFC Gm Min-SE 4028 [i.11] x Path 3327 [i.6] - P-Access-Network-Info 3455 [i.9] x P-Asserted-Service draft-drage- sipping-service- identification-01 - P-Called-Party-ID 3455 [i.9] - P-Charging-Function-Addresses 3455 [i.9] x P-Charging-Vector 3455 [i.9] x P-Media-Authorization 3313 [i.4] x P-Visited-Network-ID 3455 [i.9] - Security-Client 3329 [i.7] x Security-Server 3329 [i.7] x Security-Verify 3329 [i.7] x Service-Route 3608 [i.10] x Session-Expires 4028 [i.11] x
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.