hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3DES-CBC 3'ple Data Encryption Standard - Cipher Block Chaining mode 3DES-CTR 3'ple Data Encryption Standard - CounTeR mode AC Access Controller ACL Access Control List ACR Anonymous Communication Rejection AES Advanced Encryption Standard AES... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 4 Overview | The clause briefly describes applicability of the protocols discussed further in the present document to the reference points and functional entities defined in [1] and [2] as depicted in figure 4.1. The IMS CND functions are described within the TS 185 006 [2] dedicated to Customer Network Devices. Figure 4.1: Custome... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 4.1 Protocols and Reference Points | The u reference point is described in clause 5. The C reference point is described in clause 6, detailing procedures based on UPnP™. The Gm' reference point is described in clause 7, detailing procedures based on SIP. The e3' reference point is described in clause 8, detailing procedures based on HTTP. The au reference... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 5 Procedures at the u Reference Point | NOTE: This clause is not elaborated in Release 2. Content intended for this clause is procedures based on HTTP, for example HTTP authentication and access control. Various methods for HTTP authentication will be elaborated and detailed. Examples of such authentication methods could be HTTP Cookie based authentication, ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6 Procedures at the C Reference Point | 6.1 Procedures for using UPnP™ |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1 Remote Access Functions | Architectural information is found in clauses 7.4 of TS 185 003 [1] and 8.4 in TS 185 006 [2]. The definition of the protocols on the C reference point conforms to the UPnP™ architecture. Using the C reference point for Remote Access (RA) is described in the following clauses: device discovery in clause 6.1.1.1 and per... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1.1 Device Discovery | The CNG-PPF collects available UPnP™ devices at a regular interval in accordance with UPnP™ Device Architecture 1.0 [6]. This is done using M-SEARCH and NOTIFY messages. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1.2 Push of Content | Over the C reference point this is an UPnP™ AVTransport; Play (as specified in [57]) action, etc. on home device providing UPnP™ MediaServer [5]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1.3 Pull of Content | Over the C reference point this is UPnP™ ContentDirectory; Browse (as specified in [58]) provided by the UPnP™ MediaServer [5] and AVTransport; Play (as specified in [57]) actions, etc., provided by the UPnP™ MediaRenderer [56]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1.4 Streaming of Content | Over C reference point this is behaving as the previous clause (Pull of content). NOTE: Bandwidth allocation during tunnel setup in NGN Release 2 does not take into account the different directions, e.g. RTSP in both (sendrecv) and RTP in one (recvonly). Streaming Service Provider managed IPTV content from CPN is not s... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 6.1.1.5 Remote Control | Over C reference point this is UPnP™ ScheduledRecording::CreateRecordSchedule action, etc. on home device providing UPnP™ ScheduledRecording service [59]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7 Procedures at the Gm' Reference Point | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.1 General | In this clause, procedures at the Gm' reference points are specified both for non-IMS and IMS SIP devices. • Non-IMS SIP device: devices complying with the definition of "Non-IMS capable device - SIP Device" in [2]. • IMS SIP device: devices complying to the definition of "IMS capable device" in [2], with the exception... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2 Procedures for non-IMS SIP devices | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.1 SIP Profiles | Non-IMS SIP devices complying with the present document could support IETF SIP to various degrees. These levels of support are specified by using the concept of SIP Profiles. Each SIP Profile corresponds to a defined functionality. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.1.1 Basic Conversational Profile | Support for the Basic Conversational Profile is the minimum level of SIP support for a non-IMS SIP CND. In the Basic Conversational Profile the following features shall be supported: • Registration - registration procedures are detailed in clause 7.2.3. The support for the Registration functionality over the Gm' refere... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.1.2 Extended Conversational Profile | To be compliant with the Extended Conversational Profile support of the Basic Conversational Profile shall be extended with the following features: • Indicating User Agent Capabilities in SIP - Procedures for indicating User Agent Capabilities are detailed in clause 7.2.8. • The support for Indication User Agent Capabi... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.1.3 Conversational Supplementary Services Profile | To be compliant with the Conversational Supplementary Services Profiles, support of the Basic Conversational Profile shall be extended with the following features: • Service Activation/De-activation - Procedures for Service Activation/De-activation are detailed in clause 7.2.5. • Communication Diversion - Procedures fo... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.2 IETF RFC support | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.2.1 Basic Conversational Profile | In order to be compliant with the Basic Conversational Profiles, support of the following IETF specification shall be supported: • RFC 3261 [4]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.2.2 Extended Conversational Profile | In order to be compliant with the Extended Conversational Profile, support of the following IETF specifications shall be supported: • RFC 3840 [18]. • RFC 3428 [44]. Additionally the following IETF specifications may be supported: • RFC 2833 [17]. • RFC 3994 [45]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.2.3 Conversational Supplementary Services Profile | In order to be compliant with the Conversational Supplementary Services Profile, the following IETF specifications shall be supported: • RFC 3265 [47]. • RFC 3842 [46]. • RFC 3515 [48]. • RFC 3891 [49]. • RFC 3892 [50]. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 22 |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.3 Registration | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.3.1 Registration of CND-SIP UA, general | The registration procedures for a CND-SIP UA shall be compliant with RFC 3261 [4], clause 10. A CND-SIP UA can register a user identity (local or public) with its contact address at any time after it has learned its registration domain and acquired an IP address of the CND where it is executing. However, the CND-SIP UA... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.3.2 Registration of CND-SIP UA, using local SIP-URI | The local user identity field should contain a value that is administered by the CNG-SIP Proxy B2BUA and the value of the registration domain field should be the registration domain handled by the CNG-SIP Proxy B2BUA. When a CND-SIP UA is registered in the CNG-SIP Proxy B2BUA with a local identity it will be available ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.3.3 Registration of CND-SIP UA, using public SIP-URI not preconfigured in CNG | The public user identity field should contain a value corresponding to a service provided by the NGN side of the CNG. The value of the registration domain field should be that of the service provided by the NGN side of the CNG. When a CND-SIP UA is registered in the CNG-SIP Proxy B2BUA with a public identity that is no... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4 Basic Call | The procedures for a CND-SIP UA related to Basic Calls are compliant with the following clauses within RFC 3261 [4]: • clause 7 • clause 8 • clause 9 • clause 12 • clause 13 • clause 14 • clause 15 • clause 17 • clause 18 • clause 19 ETSI ETSI TS 185 010 V2.1.1 (2009-07) 24 • clause 20 • clause 21 |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.1 Call Initiation | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.1.1 Outgoing call | On sending an INVITE request, the CND-SIP UA shall populate the header fields as follows: a) a From header set to the SIP URI that contain the local user identity of the caller (registered in the CNG-SIP B2BUA) or in cases where privacy is required, the CND-SIP UA shall set the From header display name to "Anonymous" a... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.1.2 Internal call between CND-SIP UAs | The user identity field or the Request-URI contains the value of the called user from the CND-SIP UA, in this case a user that is defined for the registration domain administered by the CNG-SIP B2BUA. The value of the domain field of the Request-URI should be the value of the registration domain handled by the CNG-SIP ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.1.3 Incoming Call Initiation, locally non-forked call | The procedures for incoming calls from NGN to the CNG-SIP B2BUA are the procedures specified for the Gm reference point in ES 283 003 [5]. When receiving an incoming INVITE at the Gm reference point, the CNG-SIP B2BUA checks the Request-URI to determine which public identity is being called. The CNG-SIP B2BUA proceeds ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.1.4 Incoming Call Initiation, locally forked call | The procedures for incoming calls from NGN to the CNG-SIP B2BUA are the procedures specified for the Gm reference point ES 283 003 [5]. When receiving an incoming INVITE at the Gm reference point, the CNG-SIP B2BUA checks the Request-URI to determine which public identity is being called. The CNG-SIP B2BUA proceeds by ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.2 Call Release of session during session establishment | When sending a CANCEL request on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 9 and 9.1. Upon receiving a CANCEL request on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 9 and 9.1. Upon receiving a CANCEL request on Gm' the CNG-SIP B2BUA shall apply... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.3 Call Release of existing session | When sending a BYE request on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 15.1 and 15.1.1. Upon receiving a BYE request on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 15.1 and 15.1.2. Upon receiving a BYE request on Gm' the CNG-SIP B2BUA shall ap... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.4 Call Modification | When generating a re-INVITE on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 14 and 14.1. Upon receiving a re-INVITE on Gm' the CND-SIP-UA shall apply the procedures specified in RFC 3261 [4], clauses 14 and 14.2. Upon receiving a re-INVITE on Gm' the CNG-SIP B2BUA shall apply the pro... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.4.5 Announcements | The following announcements methods, as specified by TS 183 028 [51], shall be supported for the non-IMS CND-SIP UAs: • Announcement received by the service during an established communication session, using the existing media stream. • Announcement received when a communication request is rejected, by the method where... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5 Conversational Supplementary Services | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.1 Activation/deactivation of services | NOTE: Activation/deactivation of services is not elaborated in Release 2. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.2 Communication Diversion | The following Communication Diversion services, as specified in TS 124 504 [8] will be supported on the Gm' reference point: CFU, CFB, CFNR, CD, CFNL and CFNRc. The following Communication Diversion service, as specified in TS 124 504 [8] will not be supported in the Gm' reference point: CDIVN. When the CND-SIP UA is o... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.3 Communication Rejection | The following Communication Rejection services, as specified in TS 124 411 [9] will be supported on the Gm' reference point: ICB, OCB and ACR. When the CND-SIP UA is originating a call the CND-SIP UA and the CNG-SIP B2BUA shall follow the procedures specified in clause 7.1.4: • If OCB or ICB has occurred, the CNG-SIP B... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.4 Explicit Communication Transfer | The Explicit Communication Transfer service is supported for the scenario, where one CND-SIP UA within the CPN has the role of a transferor, a transferee, or a transfer target. The other roles will be executed by endpoints outside the CPN for this scenario. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.4.1 CND-SIP UA is transferor | When the CND-SIP UA has the role of the transferor it shall hold the dialog established with the transferee by applying the procedures specified in clause 7.2.5.5. If the CND-SIP UA has established a dialog also with the transfer target, it shall hold that dialog by applying the procedures specified in clause 7.2.5.5. ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.4.2 CND-SIP UA is transferee | When the CNG-SIP B2BUA receives a REFER request on the NGN side, it shall apply the procedures specified in TS 125.529 [10] for an UE having the role of a transferee. The CNG-SIP B2BUA shall generate a corresponding REFER on the CPN side, keeping the Referred-By as received on the NGN side. When a REFER request is rece... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.4.3 CND-SIP UA is transfer target | The CND-SIP UA and the CNG-SIP B2BUA applies the procedures specified in clause 7.2.4. The CNG-SIP B2BUA implements the UE when having the role of a transfer target, as specified in TS 124 529 [10]. When the CNG-SIP B2BUA receives a Replaces header on the NGN side, it shall generate a corresponding Replaces header on t... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.5 Communication Hold | The CND-SIP UA and the CNG-SIP B2BUA shall follow the procedures specified in clause 7.2.4.4. In addition the CND-SIP UA shall apply the following procedures, in accordance with RFC 3264 [39], when holding or resuming a media stream: If individual media streams are affected: • for each media stream that shall be held, ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.6 Conference (3-Party) | When the CND-SIP UA has the role of the initiator of a 3-party conference it shall establish a call, hereby referred to as the primary call, with the first conference participant according to the procedures specified in clause 7.2.4. After establishment of the primary call, it shall be put on hold by applying the proce... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.7 Message Waiting Indication | The CND-SIP UA may implement the role of a MWI Subscriber, as defined in RFC 3842 [46] and RFC 3265 [47]. As an alternative, the CND-SIP UA may implement handling of unsolicited notifications, i.e. supporting an implicit subscription of the message-summary event package. In this case, the CNG-SIP B2BUA will issue the s... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.8 Originating Identification | The following Originating Identification services, as specified in TS 124 407 [27] will be supported on the Gm' reference point: OIP and OIR. To support OIP the CND-SIP UA and the CNG-SIP B2BUA shall follow the procedures specified in clause 7.2.4. To support OIR when originating a call the CND-SIP UA shall use the Fro... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.9 Terminating Identification | The following Terminating Identification services, as specified in TS 124 508 [19] will be supported: TIP and TIR, when CND-SIP UA is the terminator of the call. The following Terminating Identification services, as specified in TS 124 508 [19] will not be supported: TIP and TIR, when CND-SIP UA is the originator of th... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.5.10 Malicious Communication Identification | To support Malicious Communication Identification, the CND-SIP UA and the CNG-SIP B2BUA shall follow the procedures specified in clause 7.2.4. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.6 Messaging | The following Messaging service is supported: page-mode messaging. The following Messaging services are not supported: session-mode messaging, session-mode messaging conference. The CND-SIP UA shall send a page-mode message to another participant or a server by using a SIP MESSAGE request as defined in RFC 3428 [44]. T... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.7 DTMF | The CND-SIP UA should implement the MIME subtype "telephone-event" in the "m=" media descriptor in the SDP for audio media flows that support both audio codec and DTMF payloads in RTP packets as described in RFC 2833 [17]. For cases where RFC 2833 [17] is not supported, the CND-SIP UA shall support transport of the DTM... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.2.8 Capability Exchange | The CND-SIP UA should indicate its capabilities at registration, according to RFC 3840 [18]. The following feature tags may be indicated: sip.audio, sip.video, sip.text, sip.duplex, sip.mobility, sip.description, sip.events, sip.methods, sip.extensions, and sip.schemes. When receiving a registration request from the CN... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3 Procedures for IMS devices | The Gm' supports non-IMS and IMS devices. Non-IMS devices should comply with the procedures specified in clause 7.2. IMS devices should comply with the procedures specified for the Gm reference point, with the exception that security associations are not supported when attaching to the NGN through the Gm' reference poi... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.1 Registration of a CND-IMS UA, using an IMS identity | The IMS CND should follow the procedures specified in ES 283 003 [5] in the following clauses: • 5.1.1.2A • 5.1.1.3 • 5.1.1.4A The CNG-SIP Proxy B2BUA should forward all registration requests to the NGN in a transparent fashion. In parallel the CNG-SIP Proxy B2BUA may create a local registration entry for the CND-SIP U... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.2 Registration of a CND-IMS UA, using a local identity | The IMS CND should follow the procedures specified in ES 283 003 [5] in the following clauses: • 5.1.1.2A • 5.1.1.3 • 5.1.1.4A With the exception that a public user identity and the domain name valid in the NGN should not be used when populating the SIP header fields. Instead a local user identity and a local registrat... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.4 Basic Call | The CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 283 003 [5] and TS 183 028 [51]. The CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3.3. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5 Conversational Supplementary Services | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.1 Activation/deactivation of services | NOTE: Activation/deactivation of services is not elaborated in Release 2. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.2 Communication Diversion | When Communication Diversion is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 004 [52]. When Communication Diversion is supported, the CNG-SIP Proxy shall apply the generic procedures specified... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.3 Communication Rejection | When Communication Rejection is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 011 [53]. When Communication Rejection is supported, the CNG-SIP Proxy shall apply the generic procedures specified... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.4 Explicit Communication Transfer | When Explicit Communication Transfer is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 029 [54]. When Explicit Communication Transfer is supported, the CNG-SIP Proxy shall apply the generic proc... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.5 Communication Hold | When Communication Hold is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 010 [55]. When Communication Hold is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.6 Conference (3-Party) | When Conference (3-Party) is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 005 [34]. When Conference (3-Party) is supported, the CNG-SIP Proxy shall apply the generic procedures specified in cl... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.7 Message Waiting Indication | When Message Waiting Indication is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 006 [15]. When Message Waiting Indication is supported, the CNG-SIP Proxy shall apply the generic procedures spe... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.8 Originating Identification | When Originating Identification is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 007 [43]. When Originating Identification is supported, the CNG-SIP Proxy shall apply the generic procedures spe... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.9 Terminating Identification | When Terminating Identification is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 008 [36]. When Terminating Identification is supported, the CNG-SIP Proxy shall apply the generic procedures spe... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.10 Malicious Communication Identification | When Malicious Communication Identification is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 016 [35]. When Malicious Communication Identification is supported, the CNG-SIP Proxy shall apply th... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.11 Advice of Charge | When Advice of Charge is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 047 [40]. When Advice of Charge is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.12 Closed User Groups | When Closed User Groups is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures for a UE specified in TS 183 054 [41]. When Closed User Groups is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.13 DTMF | When DTMF is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures specified for DTMF signalling for a UE in TS 124.229 [20]. When DTMF is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3.3. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.5.14 User Capabilities | When Capability Exchange is supported, the CND-IMS UA shall apply the procedures endorsed by ES 283 003 [5] related to RFC 3840 [18] implementation and usage of the SIP OPTIONS request. Upon receiving a registration request from a CND-IMS UA that contains capability information, the CNG-SIP B2BUA should use this inform... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.6 Presence | When Presence is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures specified for a UE in ES 283 030 [16]. Where Presence is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3.3. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.7 Messaging | When Messaging is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply the generic procedures specified in clause 7.3.3 in combination with the procedures specified for a UE in TS 183 041 [33]. When Messaging is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3.3. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.3.8 SMS/MMS | When SMS/MMS is supported, the CND-IMS UA and the CNG-SIP B2BUA shall apply generic procedures specified in clause 7.3.3 in combination with the procedures specified for a UE in TS 183 051 [42]. When SMS/MMS is supported, the CNG-SIP Proxy shall apply the generic procedures specified in clause 7.3.3. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.4 Procedures for NAT traversal | If the CNG-SIP Proxy B2BUA implements a SIP Proxy, the SIP Proxy should implement SIP ALG functionality. The SIP ALG functionality assists the SIP based applications in the CND with NAT traversal. If the CNG-SIP Proxy B2BUA implements a SIP B2BUA, the SIP B2BIA shall implement SIP ALG functionality for the SIP based ap... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 7.5 CNG-SIP Proxy B2BUA Operation | In the architecture specified by TS 185 003 "TISPAN CNG Architecture and Reference Points" [1] Gm' is the reference point between CND-SIP UA and CNG-SIP Proxy B2BUA. In the same document a definition is made of the CNG-SIP Proxy B2BUA Function. This functionality may be implemented either as a SIP Proxy as specified in... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8 Procedures at the e3' reference point | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.1 General | A CND may support the e3 reference point for direct remote management from the CNGCF, as specified in TS 183 065 [21]. The e3 reference point provides a complete set of management functionalities (e.g. provisioning and configuration management, software/firmware management, diagnostics and troubleshooting, performance ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2 Procedures for using HTTP | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.1 Data model definition | As specified in TS 183 065 [21], the CND data model shall be compliant with the data models already defined by Broadband Forum in its technical reports, e.g.: • TR-106 Amendment 2 [63], generic TR-069 [89] device data model; • TR-104 [62], VoIP device data model; • TR-135 [64], IPTV STB data model; • TR-140 Issue 1.1 [... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2 Configuration and provisioning | As specified in TS 183 065 [21], configuration management and provisioning may be done through the e3 reference point. In addition, the basic provisioning of the CND may be achieved by means of the e3' protocol specified in clause 8.2.2.1: in general such a solution may be used when the CND does not support the e3 refe... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1 CND Configuration Protocol (on the e3' reference point) | The CND Configuration Protocol (CNDCP) on the e3' reference point may be used when a CND is not provided with the necessary configuration data to access the NGN services (i.e. SIP username and password, SIP domain, SIP outbound proxy), but instead the CNG has already been provisioned with all of these configuration dat... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1.1 Protocol Description | The CNDCP protocol is based on HTTP: the CNG shall behave as HTTP server and the CND as HTTP client. The CND requests are sent in the form of a HTTP GET to a specific URL sent to the address of current Default Gateway and the CNG answers with an XML message containing an error code (code 0 indicates the correct request... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1.2 CLI-CND Association | For associating a CND to a CLI, usually the first step is to ask the CNG for the CLI list (automatically or by user interaction). The CLI list request is sent by means of the HTTP GET request with the following URL (URL #1): • http://192.168.1.1/AskCli; where it is assumed that the IP address of the default gateway is ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1.3 Removing CLI Association | A CND can request the CNG to remove a CLI association. If the CND is using multiple CLI, the CLI de-association request is carried on through an association request URL (URL #2 ) where the CLI to be removed is not present. For example if CLI1=0612345678 and CLI2=0698765432 are associated to a CND that sends the followi... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1.4 Compulsory Configuration Renewal | It is required that the CNG is able to force the CNDs to request the configuration parameters by sending a specific IP/UDP message in broadcast to the LAN MAC addresses. The Compulsory Configuration Renewal Procedure (CCRP) is activated by the CNG in the following situations: • at each start-up of the CNG; • in case of... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.2.1.5 Example of XML File | 8.2.2.1.5.1 CLI LIST XML FILE Figure 8.2 shows an example of XML file sent from the CNG to the CND in the case of request for CLI List. 7 CLI are provisioned in the CNG (0112285111, 0112285112, 0112285113, 0112285114, 0112285115, 0112285116, 0112285117) and 5 of these CLIs are already associated to other CNDs (Status=R... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.3 Software management | As specified in TS 183 065 [21], software management may be done through the e3 reference point. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.4 Diagnostics | As specified in TS 183 065 [21], diagnostics may be done through the e3 reference point. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 8.2.5 Performance Monitoring | As specified in TS 183 065 [21], performance monitoring may be done through the e3 reference point. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9 Procedures at the au Reference Point | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.1 General | The au reference point is defined between the Customer Network Device and the CNG-AuF. The authenticated entity is a CND (Customer Network Device), while the authenticator is the CNG (Customer Network Gateway) as specified by TS 185 003 [1]. |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.2 Procedures for pairing CND-CNG | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.2.1 Identification of CNG | A CNG should support multiple SSIDs. This will make it possible to setup a separate SSID with separate pairing and security. Separate authentication should be used for each SSID. ETSI ETSI TS 185 010 V2.1.1 (2009-07) 46 |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.2.2 Protocols on the au Reference Point | NOTE: The following normative text applies mainly to the wireless CNDs but can be theoretically valid for every possible CND. The au reference point shall support WPA2 [30] as the secure protocol. In the case where the CND does not support WPA2 then WPA shall be supported as a fallback solution. WPA/WPA2 is specified b... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.2.2.1 Local authentication protocol | The base authentication protocol is EAP [29]. The protocol stack for a Supplicant and Authenticator conversation is shown on figure 9.2. The lower layer with respect to EAP which is used is IEEE 802.1X [28] and IEEE 802.11 [31]. The EAP method layer implements authentication algorithm, sends and receives EAP messages a... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 9.2.3 Simplified device pairing, Wi-Fi protected setup | The CNG and the CND shall support Wi-Fi Protected Setup Specification [32] as specified by Wi-Fi alliance. This standard provides a secure way to configure WPA/WPA2 without the need for the user to enter a pass phrase into the AP. The user friendly mechanism shall support Wi-Fi Alliance Protected SetupTM (PIN/PBC). The... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 10 Procedures at the e1' Reference Point | |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 10.1 Procedures for using DHCP | The e1' reference point serves the CND-AtF with appropriate configuration data to connect to a local IP network and attach to some selected services such as the P-CSCF. The protocol of choice is DHCP (RFC 2131 [23]) and the following clauses describes which DHCP options are needed to implement this function. 10.1a Proc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.