hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 10.2.1 TR-069 provisioned DHCP parameters | If the CNG implements the CWMP protocol specified in TR-069 amendment 2 [25], it should implement the DHCP server provisioning data model as defined in TR-098 amendment 2 [26]. This allows the operator to configure the correct DHCP option response values for the CNDs as defined in TS 183 019 [24], clause 7.1.1 or for I... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 10.2.2 DHCP INFORM to obtain parameters | If the DHCP server response parameters in the CNG can not be provisioned according to 10.2.1 the CNG should implement a DHCP INFORM function for any unknown device requesting configuration. In this case the CNG may not have the knowledge about the device that has identified itself by the DHCP option 125 and instead of ... |
bdb476a5c99a057a039583429b41eaf8 | 185 010 | 10.2.3 DHCP REQUEST to obtain parameters | If the outbound DHCP server does not support DHCPINFORM the CNG may fall back on a DHCPREQUEST with the credentials of the CND. If this method is supported the CNG must send a DHCPREQUEST message with the IP address of the CNG in the "server identifier" field to decline the offered IP address but use the offered parame... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 1 Scope | The present document defines the stage 2 Customer Network Devices for IPTV services (IPTV-CND) specifications. It is therefore addressing the overall architecture of the customer network device (CND) enabling the IPTV service consumption. The architectural definition is covering both transport and service layer related... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 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... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 181 016: "Telecommunications and Internet con... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 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 004: "Telecommunications and Interne... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 3 Definitions and abbreviations | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Customer Network Device (CND): physical device enabling service(s) usage NOTE: CNDs can be dedicated to the internet, conversational and audio-video services, but they could be also Consumer Electronics equipment and other devices whic... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACF Access Configuration Function AtF Attachment Function B2BUA Back-to-Back User Agent BC BroadCast BF Browser Function BTA Broadcast TV Application C-BGF Core Border Gateway Function CDA CoD Application CF Configuration Function CMF Configur... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4 High level functional architecture for IPTV-CNDs | The high level functional architecture of IPTV-CND is composed of 3 layers as represented in figure 4.1. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4.1 Architecture layers | Application & User Experience Layer Transport Layer Service Layer CND Figure 4.1: Architecture layers |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4.1.1 Transport layer | This layer comprises functional entities that provide relevant IPTV transport level functions such as network attachment and media processing and streaming functions. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4.1.2 Service layer | This layer comprises functional entities that provide relevant IPTV functionality to applications above and also include entities that are used for management and control of platform itself. Depending on the type of services, the service layer entity must communicate either with other devices in the customer network or... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4.1.3 Application and User Experience layer | This layer comprises IPTV applications that have user interface (user driven input and /or output) and use the services provided by the underlying Service Layer to drive end user experience. Examples of applications include: • VOD. • Broadcast TV. • IPTV Service Guide interface, etc. The user may be a customer or a ser... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 4.2 IPTV operating modes | IPTV CNDs can be simple terminals connected to the NGN or be part of a CPN in connection with the CNG. Different configuration are discussed in TR 185 004 [i.1]. Consequently, the IPTV CND can work in different modes in relation with the CNG. • Bridged mode: In this mode, the IPTV CND is working in compliance with TS 1... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5 IPTV Customer Network Device Architecture | The present document categorizes IPTV-CNDs into two types depending on TISPAN IPTV solutions that have been developed by WG2. They are: • Devices compatible with the IPTV dedicated subsystem solution. • Devices compatible with the IMS based IPTV solution. ETSI ETSI TS 185 009 V2.2.1 (2009-05) 11 Devices compatible with... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1 IMS based IPTV compatible devices | IMS based IPTV compatible means compliance with TS 182 027 [2]. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1 Detailed Architecture | Application & User Experience Layer Configuration Management & Monitoring Media Player Control and Media Delivery SIP User Agent MetaData Processing Transport Layer Service Layer CND Xa Gm, Gm’ xc, xd (Dj) e3, e3’, e1, e1’, Metadata App Media /Packet Processing Function Service Profile Management Ut Service Profile App... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.1 Transport Layer Functions | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.1.1 Network attachment functions | IPTV CND attachment functions are compliant with the specifications for CNDs TS 185 006 [7]. They include: • IPTV-CND-CMF: Customer Network Device - Configuration and Maintenance Function. • IPTV-CND-AtF: Customer Network Attachment Function. • IPTV-CND-LAF: Customer Network Device - Local Authentication Function. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.1.2 Transfer functions | IPTV CND transfer functions are compliant with the specifications for CNDs TS 185 006 [7]. • IPTV-CND-NTF: NAPT Traversal Function. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.1.3 Transport functions | 5.1.1.1.3.1 IPTV-CND-MPPF: IPTV Customer Network Device-Media Packet Processing Function The MPPF is the termination point for media flows encrypted or not encrypted, over the Dj interface connecting the UE to the NGN C-BGF as defined in ES 282 001 [8]. NOTE 1: The handling of encrypted media flows is out of scope of t... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2 Service layer functions | NOTE: The security aspects are not specified in this release. The term security is to be taken here in a general sense covering several aspects including content protection, conditional access, privacy and parental control. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.1 IPTV-CND-SIP UA: IPTV Customer Network Device SIP UA | This block implements the Gm, Gm' interfaces on IPTV CND compatible with the IMS based IPTV solution. This SIP UA shall perform the service authentication and manage signalling flows securely following in that what is already described in clause 6 on Authentication in TS 185 006 [7]. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.2 IPTV-CND-SPM: IPTV Service Profile Management function | This block implements the Ut interface; the Ut enables the access to an Application Sever to support the user in configuration services update. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.3 IPTV-CND-MDP: IPTV Customer Network Device MetaData Processing | This functional entity utilizes Xa, Gm and/or Xd to receive service related metadata (e.g. IPTV services plans, EPG, VOD catalogue, customer applications). ETSI ETSI TS 185 009 V2.2.1 (2009-05) 13 |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.4 IPTV-CND-MPC: IPTV Customer Network Device Media Player Control | This functional entity utilizes Xc for control of media delivery (e.g. RTSP set up, Play, stop, etc.). |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.5 IPTV-CND-MD: IPTV Customer Network Media Delivery | This functional entity implements the Xd interface for the media streaming (e.g. RTP streams). |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.6 IPTV-CND-CMM: Configuration Management and Monitoring | This function provides support for the IPTV-CND-CMF for service layer configuration, middleware management, performance monitoring (providing feedback on QoS/QoE including packet losses, packet delay and delay jitter, frame loss, pixilation) and diagnostics through the e3 reference point and e3' reference point. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.7 IPTV-CND-PPF: IPTV Customer Network Device - Plug and Play Function | The CND-PPF in the CNG may exchange some device information (discovery, description) with other devices and allow their control. Particularly, the entity should allow a communication between many types of Customer Device within the CPN, based for instance on UPnP. Additional functions may be present in the CNG and the ... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.2.8 IPTV-CND-cPVR: IPTV client PVR Function | This functional entity has a normal PVR's capabilities, i.e. it records linear TV program and plays the recorded TV program; in addition, it provides also time-shift capability. The interface between IPTV application cPVR and the cPVR function is internal; therefore it can be proprietary. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.3 Applications and user experience layer functions | The functions in this layer may be supported directly on the CND by native applications or they may be executed in a browser-based environment. Both types of applications may coexist on the CND implementing a hybrid concept. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.3.1 IPTV Applications | The IPTV Applications provide support for a variety of IPTV Services and functions. They include: 5.1.1.3.1.1 IPTV-CND-CDA: The CoD Application This application function allows a user to select and control playback of a CoD stream. 5.1.1.3.1.2 IPTV-CND-BTA: Broadcast TV Application This application function allows a us... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.3.2 IPTV-CND-SPA: Service Profile Application | This application function allows users to manage IPTV service profile information. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.3.3 IPTV-CND-MDA: MetaData Application | This functional entity enables the user to exchange service selection data/metadata (using the IPTV-CND-MDP) that enriches IPTV service experience and may be exchanged with the SSF (EPG guide, CoD catalogue, etc.), MDF or the SCF. Implementations of the IPTV-CND-MDA shall contain: • EPG services as required in TS 181 0... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 5.1.1.3.4 IPTV-CND-BF: Browser Function | The Browser Function (BF) loads web based IPTV Application (for example, COD, Broadcast TV and NPVR) from the Service Selection Function (SSF) via the Xa reference point defined in TS 182 027 [2]. It should be able to run IPTV applications (web based) for presentation of user interface and including scripting support f... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6 Reference points | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6.1 Reference points for IMS based IPTV compatible devices | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6.1.1 Transport layer Reference points | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6.1.1.1 Transport Reference points | Dj: This reference point is used to carry all data between the UE and the access point in the NGN. As such, in the case of IPTV CND, the Dj reference point is used to send and receive media data and media control flows to/from the NGN as specified in TS 182 027 [2]. The Dj reference point complies with the ES 282 001 [... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6.1.1.2 Network attachment Reference points | e1: This reference point between the IPTV-CND and NACF is used by the IPTV CND for attaching itself to the IMS IPTV service provider network. The usage of the e1 reference point conforms to TS 185 006 [7]. e1': This reference point between the IPTV CND and CNG (in "routed mode") provides network attachment functions an... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 6.1.2 Service layer Reference points | C: This reference point is between the Plug and Play function in the IPTV CND and the CNG-PPF in accordance with definition given in TS 185 006 [7] and TS 185 003 [6]. This reference point is optional and is used only in the Routed NGN mode and the Routed CPN mode. In these modes, the reference point C allows the estab... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 7 The IPTV - CND Data Model | The IPTV CND shall support the device data model for remote management as proposed by DSL Forum, the TR135 model for STB published December 2007. Additionally, any relevant TR135 object extensions specified in TS 183 063 [3] required to support IPTV Service Provider/SDF Discovery as per "TR-069 Based SDF Discovery proc... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 8 Deployment's scenarios | In the CPN the IPTV service can be provided in at least two deployment's scenario. Below are two such options provided: • Option 1: All IPTV functionalities are implemented in the IPTV-CND. • Option 2: Some IPTV functionalities are implemented in the IPTV-CND and the others in the CNG. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 8.1 Option 1 | In the deployment's scenario "Option 1" all functionalities described in the present document are implemented in the IPTV-CND. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 8.2 Option 2 | In the deployment's scenario "option 2", according to TS 185 003 [6], a subset of functionalities described in the present document are implemented in the IPTV-CND. Table 8.1 lists the functionalities that are implemented on the CNG and on the IPTV-CND. Table 8.1: Deployment's scenario "option 2" Layer Function CNG IPT... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9 Information Flows | NOTE: Information flows clause is non normative text reported in form of examples to better understand the relationships between the IPTV CND and the NGN, the CNG and other CNDs. The list of flows given hereafter is not exhaustive. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1 Information flows between IPTV-CND and NGN | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.1 Example message flows on Xa | Figure 9.1: Message flows for service selection The message flow in figure 9.1 is an example of service selection function. With the HTTP GET, the CND asks the NGN for the program information, such as CoD catalogue, BC channels. And NGN returns the program information to the CND. This procedure example for service sele... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.2 Example message flows on Ut | Figure 9.2: Message flows for service related information configuration The message flow in figure 9.2 is an example of service related information configuration function. With HTTP GET and PUT methods, the CND retrieves and modifies its service related information. The procedure example for service related information... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.3 Example message flows on Gm | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.3.1 Registration | The NGN registration flows are compliant with TS 183 063 [3]. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.3.2 Session Initiation and Termination | The Session Initiation and Termination flows are compliant with TS 183 063 [3]. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.3.3 IPTV Service Action Data Delivery | The IPTV service action data delivery flows are compliant with TS 183 063 [3]. Figure 9.3: Message flows for IPTV service action data delivery IPTV service action data, such as BC bookmarks, Available CoD and NPVR items, are delivered to CNG-SIP via SIP INFO or MESSAGE method. IPTV-CND-SIP UA (1) SIP INFO or MESSAGE (2... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.4 Example message flows on Xc and Xd | IPTV application utilizes Xc for media control, such as RTSP setup, play, teardown, and utilizes Xd for media streaming, such as RTP stream. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.4.1 Message flows for CoD service | Figure 9.4: Information flows for media content control and delivery This procedure example for media control using RTSP is compliant with TS 183 063 [3]. This procedure example is applicable for the IPTV-CND in the bridged mode. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.4.2 Message flows for BC service | Figure 9.5: Information flows for media content control and delivery IPTV-CND-MPC (1) Join Multicast Group MF (2) Leave Multicast Group (2) RTP/RTCP IPTV-CND-MPC (1) RTSP SETUP (2) 200 OK MF (3) RTSP PLAY (4) 200 OK (6) RTSP TEARDOWN (7) 200 OK (5) RTP/RTCP ETSI ETSI TS 185 009 V2.2.1 (2009-05) 20 This procedure exampl... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.5 Example message flows on e3 | Figure 9.6: Message flows for configuration and management IPTV applications utilize e3 for auto-configuration, software management and diagnostics. This procedure example is applicable for the IPTV-CND in the bridged mode. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.1.6 Example message flows on e1 | Figure 9.7: Message flows for network attachment 1) The CND broadcasts a DHCPDISCOVER message with its client identifier and some request parameters, such as Domain name and P-CSCF address, etc. 2) Multiple DHCP servers return DHCPOFFERs with parameters to the CND. 3) The CND choose one DHCPOFFER, and broadcasts DHCPRE... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2 Information flows between IPTV-CND and CNG | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.1 Example message flows on C | In UPnP environment, the control point can retrieve the information of device of interest. The information includes the device description and service description describing the capabilities exposed by the device. After getting this information, control point sends suitable control message to perform control action. Th... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.1.1 Message flows for device and service information exchange | The information includes the device description and service description describing the capabilities exposed by the device. Two cases are shown in Figures 9.8(a) and 9.8(b) respectively. Figure 9.8(a): Message flows for device information exchange based on UPnP In figure 9.8(a): 1) When the CNG is added to the network, ... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.1.2 Message flows for device control | Figure 9.9: Message flows for device control based on UPnP The capabilities exposed by CNG are various, such as QoS provisioning, local user identity, etc. clause 6.1.3 gives the details. All these capabilities can be defined in its service description and be performed by sending control message using SOAP. 1) IPTV-CND... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.2 Example message flows on Gm' | |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.2.1 Registration | The NGN registration flow is compliant with the specifications for CNDs TS 185 006 [7] in clause 8.3.1. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.2.2 IPTV Service Action Data Delivery | Figure 9.10: Message flows for IPTV service action data delivery IPTV service action data, such as BC bookmarks, Available CoD and NPVR items, are delivered to CNG-SIP via SIP INFO or MESSAGE method. The procedure example for service action data delivery is compliant with TS 183 063 [3]. This procedure example is appli... |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.3 Example message flows on e1' | The message flows on e1' are compliant with the specifications for CNDs TS 185 006 [7] in clause 8.1. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.4 Example message flows on e3' | The message flows on e3' are compliant with the specifications for CNDs TS 185 006 [7] in clause 8.2. |
8688de3cee95f298ed1b9871565231ce | 185 009 | 9.2.5 Example message flows on au | Figure 9.11: Information flows for IPTV CND connecting to CPN This procedure example is applicable for the IPTV-CND in the routed mode. IPTV-CND-LAF (1) Request for CPN connection (2) Authentication procedure CNG-AuF IPTV-CND-SIP UA (1) SIP INFO or MESSAGE (2) 200 OK CNG-SIP ETSI ETSI TS 185 009 V2.2.1 (2009-05) 24 Ann... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 1 Scope | The present document specifies the network Test Suite Structure and Test Purposes (TSS&TP) Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol (BICCP) or ISDN User Part (ISUP) for the Profile C (SIP-I) described in the Recommendation ITU-T Q.1912.5 [1] and EN 383 001 [2].... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 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 ar... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Recommendation ITU-T Q.1912.5: "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part". [2] ETSI EN 383 001: "Telecommunications and Internet converged Servic... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 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] Void. [i.2] Recommendation ITU-T Q.731: "Stage 3 description for the number identification supplementary services using SS No.7". [i.3] Recommendation... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 3 Definitions and abbreviations | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: • terms defined in SIP/ISUP interworking reference specification; • terms defined in ISDN layer 3 reference specification; • terms defined in ISDN User Part (ISUP) reference specification terms defined in ISO/IEC 9646-1 [6], ISO/IEC 96... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3PTY Three-Party ACM Address Complete Message ANM ANswer Message ASP Abstract Service Primitive ATC Abstract Test Case ATM Abstract Test Method ATP Access Transport Parameter ATS Abstract Test Suite AVP Attribute-Value Pairs ETSI ETSI TS 186 0... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4 Test Suite Structure (TSS) | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.1 Interworking from SIP to BICC/ISUP (outgoing call) | SIP -ISUP basic call Sending of the Initial Address Message (IAM) TP101xxx Sending of the Subsequent Address Message (SAM) TP102xxx Sending of COT TP103xxx Receipt of the Address Complete Message (ACM) TP104xxx Receipt of the Call Progress Message (CPG) TP105xxx Receipt of the ANswer Message (ANM) TP106xxx Receipt of t... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.2 Interworking from BICC/ISUP to SIP (incoming call) | ISUP-SIP basic call Sending of the INVITE message TP301xxx Receipt of the Subsequent Address Message (SAM) TP302xxx Sending of the Address Complete Message (ACM) TP303xxx Sending of the Call Progress Message (CPG) TP304xxx Sending of the ANswer Message (ANM) TP305xxx Sending of the CONnect message (CON) TP306xxx Receip... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.3 Supplementary services supported by encapsulation | ISUP-SIP/SIP-ISUP Calling Line Identification Presentation (CLIP) TP401xxx Calling line Identification Restriction (CLIR) TP402xxx COnnected Line identification Presentation (COLP) TP403xxx COnnected Line identification Restriction (COLR) TP404xxx Terminal Portability (TP) TP405xxx SUBaddressing (SUB) TP406xxx Maliciou... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.4 Void | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.5 Void | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 4.6 Void | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5 Test Purposes (TP) | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.1 Introduction | For each test requirement a Test Purpose (TP) is defined. |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.1.1 Test Purpose (TP) naming convention | For each test requirement a Test Purpose (TP) is defined. All test purposes belong to the main group ISUP_SIP_Interworking. Groups are organized according to the Test Suite Structure (TSS). Each test purpose is presented in a separate table. The first row of the table contains the following items: • TP: Identifier of t... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.1.2 Source of test purpose definition | The Test Purposes (TPs) have been developed based on Recommendation ITU-T Q.1912.5 [1]. ETSI ETSI TS 186 002-3 V1.3.2 (2014-10) 15 |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.1.3 Test purpose structure | The Test Purpose (TP) structure is according to the Test Suite Structure (TSS). |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2 Test purposes for the basic cal | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1 Interworking from SIP-I to ISUP (outgoing call) | |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.1 Sending of the Initial Address Message (IAM) | TP101001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.1.2 (i,1) TSS reference SIP-ISUP/Basic call/Sending of the Initial Address Message (IAM) SIP selection criteria NOT PICS 4/4 AND NOT PICS 4/5 ISUP selection criteria NOT PICS 1/6 Test purpose Ensure that if the SUT upon receipt of the first INV... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.2 Sending of the Subsequent Address Message (SAM) | TP102001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.2 a) TSS reference SIP-ISUP/Basic call/ Sending of the Subsequent Address Message (SAM)/ SIP selection criteria PICS 3/4 ISUP selection criteria PICS 3/8 Test purpose Ensure that the SUT receives an INVITE with the same Call-ID and From tag as ... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.3 Sending of COT | TP103001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.3 TSS reference SIP-ISUP/Basic call/COT SIP selection criteria PICS 4/4 AND PICS 4/5 ISUP selection criteria PICS 1/4 AND PICS 4/1 Test purpose Ensure that the when the SUT determines that all the preconditions on the incoming SIP side have bee... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.4 Receipt of the Address Complete Message (ACM) | TP104001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.5 2) TSS reference SIP-ISUP/Basic call/ Receipt of the Address complete message (ACM)/ SIP selection criteria ISUP selection criteria Test purpose Ensure that the SUT on receipt of an ACM message where the Called party status indicator is set t... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.5 Receipt of the Call progress message (CPG) | TP105001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.6 TSS reference SIP-ISUP/Basic call/ Receipt of the Call progress message (CPG). SIP selection criteria ISUP selection criteria Test purpose Ensure that the SUT, having received the ACM message, on receipt of a CPG message where the event infor... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.6 Receipt of the Answer message (ANM) | TP106001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.7 TSS reference SIP-ISUP/Basic call/ Receipt of the Answer message (ANM). SIP selection criteria ISUP selection criteria Test purpose Ensure that the SUT, having received the ACM message, on receipt of an ANM message: • sends a 200 OK INVITE; •... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.7 Receipt of the Connect message (CON) | TP107001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clauses 6.4 and 6.7 TSS reference SIP-ISUP/Basic call/ Receipt of the CONNECT message (CON). SIP selection criteria ISUP selection criteria Test purpose SDP offer was received in the initial INVITE. Ensure that the SUT, on receipt of an CON message: • s... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.8 Receipt of the REL message | TP108001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.11.2 TSS reference SIP-ISUP /Basic call/ Receipt of the Release message (REL)/ SIP selection criteria ISUP selection criteria Test purpose Ensure that the SUT in the Idle state on receipt of a INVITE message, sending out an IAM message, on rece... |
32ad4a8d2d51f55609bc20539b112f1c | 186 002-3 | 5.2.1.9 Autonomous release at I-IWU | TP109001 SIP reference: RFC 3261 [4] ISUP reference: Q.1912.5 [1], clause 6.11.3 TSS reference SIP-ISUP/Basic call/ Autonomous release at I-IWU SIP selection criteria ISUP selection criteria PICS 4/6 Test purpose Ensure that when a an automatic repeat attempt initiated by the SUT is not successful (because the call is ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.