hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3 Requirements derived from service scenarios | A number of detailed requirements for the customer networks can be derived from the use case illustrated in the previous clauses. Requirements are split in: • General requirements on Customer Network Gateway. • General requirements on Customer Devices. ETSI ETSI TS 185 005 V2.0.0 (2007-07) 14 • Specific Requirements fo... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.1 General Requirements on Customer Network Gateway | 1) The CNG shall be equipped with a WAN interface towards the NGN, implementing layer 1 and 2 functionalities ("one-box" solution). 2) LAN interfaces. The CNG shall be equipped with at least one Ethernet (minimum 100 Mbit/s) is interface. Optional interfaces could be present, e.g.: wireless LAN Wi-Fi Alliance certified... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.2 General requirements on Customer Network Devices | 20) A CND, as defined in clause 3, may use the CNG to access NGN services. 21) Authorized users shall be able to access NGN-based services using any NGN supported home device. 22) Both IMS capable devices with or without UICC and non-IMS capable devices without UICC shall be supported. 23) If the CND contains an ISIM/U... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.3 Specific Requirements for communication services support | 35) Multiple identities should be supported within the same subscription. Personal service profiles per each identity within the same subscription should be supported. A shared public identity on several terminals, with different private identities, shall be supported (shared IMPU). 36) Multiple public identities on th... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.4 Specific Requirements for entertainment and information services | 43) The CNG shall support mechanisms for managing IPTV flows provided both in unicast and multicast mode. 44) In case of multicast flows the CNG shall keep a record of which devices are subscribed to which multicast group. 45) An IPTV media flow shall be terminated by a STB or by a specific device called "media gateway... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.5 Specific Security requirements | 55) The CNG shall support mechanisms to authenticate itself to the NGN for connectivity purposes. 56) The CNG shall support mechanisms to authenticate itself to the NGN for service usage purposes. 57) The CNG shall support mechanisms to authenticate CNDs to the NGN for service usage purposes if they are not able to ful... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.6 Specific QoS requirements | 65) The CNG and the CPN shall support adequate Quality of Service mechanisms (e.g. prioritize the traffic in the event that there is not sufficient bandwidth in the customer network in order to ensure the correct network performances to each traffic flow). To achieve this objective a number of functionalities shall be ... |
1d84fce3a470e98ffaf2db0ceda27996 | 185 005 | 4.3.7 Specific Management requirements | 78) CNG shall be equipped with an application client to be remotely manageable by the service providers for configuration, monitoring, firmware upgrade purposes. In case of multiple service providers multiple clients configuring different sets of parameters (for example referring to different services) may be present. ... |
049271446448601336483ab2574d528a | 185 003 | 1 Scope | The present document provides an overview of Customer Network Gateway (CNG) functional architecture and reference points and the way it interacts with an NGN, as described in ETSI TISPAN Release 1 and Release 2 standards (see ES 282 001 [1]). The present document describes architectural building blocks to be included i... |
049271446448601336483ab2574d528a | 185 003 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
049271446448601336483ab2574d528a | 185 003 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001: "Telecommunications and Internet con... |
049271446448601336483ab2574d528a | 185 003 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 185 007: "Telecommunications and Interne... |
049271446448601336483ab2574d528a | 185 003 | 3 Definitions and abbreviations | |
049271446448601336483ab2574d528a | 185 003 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: CPN Device: device that is physically installed in the CPN allowing user access to network services; this can be a Customer Network Gateway with gateway functionalities towards the NGN, or a Customer Network Device being the end user t... |
049271446448601336483ab2574d528a | 185 003 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACS Auto-Configuration Server AKA Authentication and Key Agreement ALG Application Layer Gateway A-MGF Access-Media Gateway Function ARF Access Relay Function B2BUA Back-to-Back User Agent BC Broadcast Content CLF Connectivity session Location... |
049271446448601336483ab2574d528a | 185 003 | 4 The CNG Architecture | |
049271446448601336483ab2574d528a | 185 003 | 4.1 Introduction | The following clauses present the functional entities for the CNG. Examples of Customer Network Devices may be connected to the CNG: a) Analogue phones connected through the CNG to the NGN network. b) IMS Customer Network Devices connected through a CNG to the NGN network [5]. c) Non IMS SIP IETF Customer Network Devic... |
049271446448601336483ab2574d528a | 185 003 | 4.2 CPN and NGN side requirements | The list of the CNG requirements is provided by the TS 185 005 [i.6]. specification for Service requirements and capabilities for customer networks connected to TISPAN NGN. |
049271446448601336483ab2574d528a | 185 003 | 4.2.1 Analogue phone connected to the NGN through a CNG | In this case, the CNG includes all the CPN functionalities necessary to fulfill a service between the analogue phone and the NGN, as shown in figure 1. CNG Access node P-CCSF CNGCF ARF Voice Gateway Control Functions (VGCF) Gm e3 e1 Z Customer Network Gateway Analog CND Dj AS Ut CNG-Attachment Function (CNG-AtF) The CP... |
049271446448601336483ab2574d528a | 185 003 | 4.3 CNG functions | |
049271446448601336483ab2574d528a | 185 003 | 4.3.1 The transfer level functions | |
049271446448601336483ab2574d528a | 185 003 | 4.3.1.1 CNG-NFF: CNG-NAPT and Firewall Function | The CNG-NFF entity shall provide gate control functionality i.e. dynamic NAPT and firewall functions at the boundary between the CPN and the NGN. |
049271446448601336483ab2574d528a | 185 003 | 4.3.2 The transport level functions | |
049271446448601336483ab2574d528a | 185 003 | 4.3.2.1 CNG-CSMF: CNG-Communication Services Media Function | The CNG-CSMF is the termination point for the access node, it shall perform an adaptation so as to deliver media flows from the NGN network to an analogue or IP Customer Network Device. The CNG-CSMF is used for analogue (or digital in the case of ISDN CNDs) to IP media conversion - in which case it corresponds to the R... |
049271446448601336483ab2574d528a | 185 003 | 4.3.2.2 CNG-IPTVF: CNG-IPTV Function | When supporting IPTV services, the CNG shall be able to forward inbound multicast packets only to the physical interfaces connected to devices that have joined the specific multicast group. This mechanism should be implemented acting on layer 2 and layer 3 multicast signalling flows (e.g. IGMP based). The CNG shall be ... |
049271446448601336483ab2574d528a | 185 003 | 4.3.3 The CNG Network Attachment Subsystem entities (CNG-NASS) | |
049271446448601336483ab2574d528a | 185 003 | 4.3.3.1 CNG-CMF: CNG-Configuration and Management Function | The CNG-CMF shall manage a mutual authentication between the CNGCF and the CNG. The CNG-CMF shall enable the CNG configuration and firmware upgrade. The CNG-CMF entity should enable transmission of configuration information to CNDs, obtained from the CNGCF. As a result the CNG-CMF should be able particularly to store c... |
049271446448601336483ab2574d528a | 185 003 | 4.3.3.2 CNG-AtF: CNG-Attachment Function | The CNG-AtF entity shall be responsible for allocation of IP addresses to user premises equipment (CND), and to the CNG from the NACF via the ARF. |
049271446448601336483ab2574d528a | 185 003 | 4.3.3.3 CNG-PCF: CNG-Policy Control Function | The CNG-PCF may integrate a database containing the access profile. This includes bandwidth and QoS parameters for the CNG Customer Network Device side applications and terminals, which could be configured by a user. For instance, congestion issues within the CPN may be solved defining resources for several SSID. |
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 D... |
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, t... |
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 app... |
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 authentic... |
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 complia... |
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... |
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 su... |
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) Suppo... |
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, De... |
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... |
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 rig... |
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 sno... |
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... |
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 in... |
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 collect... |
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 poi... |
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]. Th... |
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 o... |
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 ex... |
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 ... |
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,... |
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 (challen... |
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. Figu... |
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 numbe... |
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 t... |
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 t... |
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 Conne... |
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 Connect... |
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. • ... |
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 boun... |
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... |
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 m... |
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 ter... |
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 ... |
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. P... |
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 throug... |
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... |
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), dim... |
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... |
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 PERFORMANC... |
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 ... |
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. Pr... |
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.... |
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 Ye... |
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... |
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 U... |
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. T... |
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 t... |
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 e... |
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. E... |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.