hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.1.1.3 Use of service selection information
|
The UE uses service selection information as defined in clause 6.1.1.5.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.2 Service Selection Function (SSF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.2.1 Procedure for service selection
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.2.1.1 Delivery of DVB service discovery and selection data
|
In the DVB push model of multicast delivery of DVB SD&S data, the DVBSTP protocol shall be used conforming to TS 102 034 [3], clause 5.4.1.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.2.1.2 Delivery of DVB broadband content guide
|
In the DVB push model of multicast delivery of a DVB BCG data, the DVBSTP protocol shall be used conforming to TS 102 539 [13], clause 4.1.2.2.1. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 123
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10 Procedures using FLUTE for IMS-based IPTV
|
NOTE: This clause applies when using OMA BCAST multicast delivery for service provider and guide discovery.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1 User Equipment (UE)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.1 Procedure for service selection
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.1.1 Request of OMA BCAST service discovery and selection data
|
In the OMA BCAST push model of multicast delivery of OMA BCAST ESG provider discovery data, the UE shall subscribe to the FLUTE streams identified within the response from the SDF, conforming to clause 9.2 in TS 102 471 [4] and clause 6 of TS 102 472 [5].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.1.2 Request of OMA BCAST service guide
|
In the OMA BCAST push model of multicast delivery of an OMA BCAST ESG, the UE shall subscribe to the FLUTE streams identified within the response from SDF or within the Service Selection information returned by the SSF, conforming to TS 102 471 [4], clause 8.1, OMA-TS BCAST_DVB_Adaptation-V1_0 [6], clause 6.3.5 and OMA-TS-BCAST_Service_Guide-V1_0, clause 5.4 [5].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.1.3 Use of service selection information
|
The UE uses service selection information as defined in clause 6.1.1.5.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.2 Procedure for multicast download
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.1.2.1 Request for multicast download
|
In the optionally supported multicast content delivery for content download, the UE shall subscribe to the FLUTE streams identified within the service request response, conforming to CDS in TS 102 034 [3] conform to clause 10 there. NOTE: The details about acquiring and initiating multicast download are not specified in this specification as indicated in clause 5.1.18.2. The procedures need to conform to CDS in TS 102 034 [3] and will be similar to the procedures for unicast download (clause 5.1.18.1).
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.2 Service Selection Function (SSF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.2.1 Procedure for service selection
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.2.1.1 Delivery of OMA BCAST service discovery and selection data
|
In the OMA BCAST push model of multicast delivery of OMA BCAST ESG provider discovery data, the FLUTE protocol shall be used, conforming to TS 102 471 [4], clause 9.2 and OMA-TS-BCAST_DVB_Adaptation-V1_0, clause 6.3.5 [6].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.2.1.2 Delivery of OMA BCAST service guide
|
In the OMA BCAST push model of multicast delivery of an OMA BCAST ESG, the FLUTE protocol shall be used, conforming to TS 102 471 [4], clause 8.1, OMA-TS-BCAST_DVB_Adaptation-V1_0 [6], clause 6.3.5 and OMA-TS- BCAST_Service_Guide-V1_0 [5], clause 5.4. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 124
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.3 Media Delivery Function (MDF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
10.3.1 Procedure for multicast download
|
If the optional multicast content download is used for the PushCOD it shall be comprised of parts that further specify how FLUTE is used in TS 102 034 [3] (as in clause 10 Content Download Service). The purpose of file delivery is to deliver content items in files. A file may contain any type of data (e.g. Audio/Video file, Binary data, still images, Text). 11 Procedures using UDP/RTP/RTCP for IMS-based IPTV The IPTV content is transported over the IP network. In order to do so, several encapsulation are possible: • MPEG2TS: the content is encapsulated into MPEG2TS packets: - MPEG2TS over UDP: the MPEG2TS packets are directly transported over the UDP layer. - MPEG2TS over RTP: the MPEG2TS packets are transported over the RTP layer. • Direct RTP: no MPEG2TS encapsulation is used, the Elementary streams are directly transported over the RTP layer.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1 User Equipment (UE)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1.1 Procedure for real-time transport
|
The UE shall support at least one of the following transport technologies: • MPEG2TS encapsulation. • Direct RTP transport.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1.1.1 Transport using MPEG2TS
|
The UE may be able to receive the content encapsulated in MPEG2TS packets. When using the MPEG2TS encapsulation technology, the UE shall support both: • MPEG2TS over UDP conforming to TS 102 034 [3], clause 7.1.2. • MPEG2TS over RTP conforming to TS 102 034 [3], clause 7.1.1 excluding clause 7.1.1.1. - As specified in ES 283 003 [20], it is possible to negotiate RTCP bandwidth - and thus to control UE receiver report generation - for unicast IPTV services during SIP session setup. NOTE 1: Handling of RTCP Receiver reports for BC services is out of scope of the present document. NOTE 2: The default behaviour in the case that - for m-lines indicating RTP/RTCP usage - no RTCP bandwidth negotiation is performed, is described in ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1.1.2 Transport using direct RTP encapsulation
|
The UE may be able to receive the content directly over the RTP layer (e.g. H264 over RTP). As specified in ES 283 003 [20], it is possible to negotiate RTCP bandwidth - and thus to control UE receiver report generation - for unicast IPTV services during SIP session setup. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 125 NOTE 1: Handling of RTCP Receiver reports for BC services is out of scope of the present document. NOTE 2: The default behaviour in the case that - for m-lines indicating RTP/RTCP usage - no RTCP bandwidth negotiation is performed, is described in ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1.2 Procedure for real-time transport eError correction
|
The UE may support a transport error correction mechanism.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.1.2.1 Unidirectional transport error correction
|
When unidirectional transport error correction is used, the UE shall be able to receive an application Layer FEC, conforming to TS 102 034 [3], annex E. NOTE: Only the base layer of the DVB-IP AL-FEC is supported in the present document, the enhancement layer support is out of scope.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2 Media Delivery Function (MDF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.1 Procedure for real-time transport
|
The MDF shall send the content using one of the following transport technologies: • MPEG2TS encapsulation. • Direct RTP transport.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.1.1 Transport using MPEG2TS
|
The MDF may be able to send the content encapsulated into MPEG2-TS.In that case, one of the following shall be used: • The transport of the IPTV content within MPEG2TS layer over RTP shall be done conforming to TS 102 034 [3], clause 7.1.1. • The transport of the IPTV content within MPEG2TS layer over UDP shall be done conforming to TS 102 034 [3], clause 7.1.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.1.2 Transport using direct RTP encapsulation
|
The MDF may be able to send the content directly over the RTP layer (e.g. H264 over RTP).
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.2 Procedure for real-time transport error correction
|
The MDF may support a transport error correction mechanism.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.2.1 Unidirectional transport error correction
|
For unidirectional transport error correction the MDF shall use an application Layer FEC mechanism, conforming to TS 102 034 [3], annex E. NOTE: Only the base layer of the DVB-IP AL-FEC is supported in the present document, the enhancement layer support is out of scope.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.2.3 Procedures for inter-destination media synchronization
|
The use of inter-destination media synchronization requires the MDF to support transport using either MPEG2TS layer over RTP, see clause 11.2.1.1., or direct RTP encapsulation, see clause 11.2.1.2. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 126
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.3 Synchronization Client (SC)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.3.1 Procedure for real-time transport
|
The SC shall support at least one of the following transport technologies: • MPEG2TS encapsulation. • Direct RTP transport.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.3.1.1 Transport using MPEG2TS
|
The SC may be able to process content that is encapsulated in MPEG2TS packets. When using the MPEG2TS encapsulation technology, the SC shall support MPEG2TS over RTP as described in clause 11.1.1.1. NOTE 1: The limitation to MPEG2TS over RTP is necessary since RTCP is used. NOTE 2: As specified in ES 283 003 [20], it is possible to negotiate RTCP bandwidth - and thus to control SC receiver report generation - for unicast IPTV services during SIP session setup. The SC shall support RTCP Extensions for Single-Source Multicast Sessions (i.e. BC services) with Unicast Feedback [43].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.3.1.2 Transport using direct RTP encapsulation
|
The SC may be able to process content that is transported directly over the RTP layer (e.g. H264 over RTP). As specified in ES 283 003 [20], it is possible to negotiate RTCP bandwidth - and thus to control SC receiver report generation - for unicast IPTV services during SIP session setup. The SC shall support RTCP Extensions for Single-Source Multicast Sessions (i.e. BC services) with Unicast Feedback as specified in [43].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.3.2 Procedures for inter-destination media synchronization
|
The SC shall send RTCP Receiver Reports (RRs) to media-level MSAS address, which is the specified IP address and port number in the SDP description or to a pre-configured media-level MSAS address in case of mapping the UE on a Transport Processing Function, see clause 4.2.8. The SC shall extend the RRs with synchronization status information, using an RTCP eXtended Report (XR), as specified in clause W.1. The synchronization status information shall include the SSRC of source, the Packet Received NTP timestamp and the Packet Received RTP timestamp. It should include thePacket Presented NTP timestamp The SC shall populate the Media Stream Correlation Identifier with the SyncGroupId parameter as specified in clause W.1. The SC shall be able to receive RTCP reports from the MSAS, on the regular RTCP receive port. The SC shall be able to receive RTCP eXtended Reports (XR) containing synchronization settings instructions, as specified in annex W.1. The RTCP XRs with synchronization settings instructions shall include the SSRC of source, and packet arrival time information, specifically the reference Packet Received NTP timestamp and the reference Packet Received RTP timestamp receipt time stamp. It should include the reference Packet Presented NTP timestamp. These RTCP XRs may be both appended to RTCP Sender Reports (SRs), but may also be received separately. NOTE 1: Synchronization settings instructions may be interpreted as the synchronization status information of a virtual SC to which this SC may try to synchronize. The SC shall be NTP synchronized [56]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 127 NOTE 2: The quality of the underlying NTP synchronization of SCs is a determining factor in inter-destination media synchronization. Recommendation ITU-T G.114 [i.8] recommends maximum one-way transmission time for an international telephone connection to achieve transparent interactivity. G.114 contains the following statements: "if delays can be kept below (150 ms), most applications, both speech and non-speech, will experience essentially transparent interactivity" and "delays above 400 ms are unacceptable for general network planning purposes". As the purpose of inter-destination media synchronization is typically achieving transparent interactivity (see also TS 181 016 [60] clause A.9.6), the Recommendation ITU-T G.114 [i.8] is a useful guideline. The SC shall not require to receive any RTCP eXtended Reports (XR) containing synchronization settings instructions. The absence of such instructions shall not be taken as a sign that something is wrong. NOTE 3: The SC may not receive synchronization settings instructions because RTCP is normally transported using the unreliable UDP protocol. The SC may also not receive any instructions if it is the most delayed SC in its synchronization group, if it is the only member of its group or if buffering is carried out in the ECF/EFF, see clause 11.5.1. If the SC is co-located with the MSAS, then the exchange of synchronization status information and synchronization settings instructions is internal to the functional entity in which they reside. NOTE 4: An example of co-located SC+MSAS functionality is when UEs exchange synchronization status information and synchronization settings instructions over an existing direct communication channel, see clause A.5.2.3. NOTE 5: The algorithm that is used by the SC to synchronize the media based on the synchronization settings instructions is a vendor implementation decision. See [i.6] for an overview of techniques.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.4 Media Synchronization Application Server (MSAS)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.4.1 Procedures for inter-destination media synchronization
|
In the case of synchronization for a broadcast stream, the MSAS shall function as a Feedback Target, specified in [43]. Before forwarding RTCP Receiver Reports to the appropriate MF, the MSAS shall read and remove RTCP eXtended Reports containing synchronization status information, which are specified in annex W. The MSAS shall send synchronization settings instructions to the SC using RTCP eXtended Reports, which are specified in annex W. The synchronization settings instructions take the form of RTP timestamps, combined with NTP timestamps. The NTP timestamp indicates the clock shared by the synchronization group, the RTP time stamps indicate the expected receipt and/or presentation time. The MSAS shall send expected receipt times. It should send expected presentation time stamps. NOTE 1: Synchronization settings instructions may be interpreted as the synchronization status information of a virtual SC to which the addressed SCs may try to synchronize. NOTE 2: The algorithm that is used by the MSAS to derive the synchronization settings instructions from the received synchronization status information is a vendor implementation decision. See [i.6] for an overview of techniques. For synchronization of Content on Demand or other unicast streams, the MSAS shall forward RTCP Receiver Reports to the appropriate MF. Before forwarding RTCP Receiver Reports, the MSAS shall read and remove RTCP eXtended Reports containing synchronization status information, which are specified in annex W. The MSAS shall forward RTCP Sender Reports to the appropriate SC, appending synchronization settings instructions to the SC using RTCP eXtended Report. The MSAS may send synchronization settings instructions to the SC using a separate RTCP XR. The RTCP XR for sending synchronization settings instructions is specified in annex W. In case of synchronization in the presence of functional entities that modify or re-originate media streams (e.g. a transcoder or a mixer in an MDF), the MSAS shall function as a Third Party Monitor [44]. It shall be able to receive and process synchronization correlation information as specified in clause 11.6.2. NOTE 3: Synchronization correlation information enables an MSAS to correlate the timing of two related media streams. By using NTP time as a reference, the MSAS can determine which RTP timestamp of the one media stream corresponds with which RTP timestamp of the other media stream. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 128 For scalability, the MSAS may consist of multiple entities organized in a hierarchical way. A "proxy" MSAS may aggregate synchronization status information of multiple SCs by forwarding only the status information of the most delayed SC in a synchronization group to an MSAS that is located hierarchically up the chain. If a "proxy" MSAS aggregates information in this manner, it shall keep track of the SCs that are part of the synchronization group, and it shall relay synchronization settings instructions to the different SCs. NOTE 4: [43] specifies that 'the Feedback Target instances MAY be organized in arbitrary topological structures: in parallel, hierarchical, or chained'. Such topological structures can be used for aggregation purposes to improve scalability.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.5 ECF/EFF
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.5.1 Procedures for inter-destination media synchronization
|
In one mapping of the SC is an adjunct function that may be co-resident with any of the appropriate elements of the Transport Processing Function, see clause 4.2.8. If the SC is an adjunct function of the ECF/EFF, then ECF/EFF shall: • Send synchronization status information to the MSAS using an RTCP eXtended Report (XR), as specified in annex W. • Be able to receive RTCP eXtended Reports (XR) containing synchronization settings instructions, as specified in annex W. The ECF/EFF may have partial SC functionality, supporting SC functionality in the UE. This requires that the SC in the ECF/EFF is in the path between the UE and the MSAS used. In this case the ECF/EFF shall be able to: • Monitor and possibly adjust synchronization status reports going from UE to MSAS. Reported arrival times need to be adjusted for the current buffer time the ECF/EFF has introduced. • Determine the arrival time for the indicated stream at the SC in the ECF/EFF. • Intercept and carry out synchronization settings instructions. Synchronization settings instructions may or may not be forwarded to the SC in the UE. NOTE: Combining an SC in a UE with an SC in the ECF/EFF may have advantages for channel changing times and synchronization accuracy. When buffering at a UE, channel changing times during the use of a shared service session may be quite large if one of the participants is severely lagging behind the others. Buffering in the ECF/EFF can reduce channel changing times. This requires the ECF/EFF to pre-buffer the channel to which the UE is changing. Furthermore, if buffering is applied in the ECF/EFF, measurements from a UE can be used to increase synchronization accuracy.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.6 Synchronization Client' (SC')
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.6.1 Procedure for real-time transport
|
Clause 11.3.1 is also applicable to SC'.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
11.6.2 Procedures for inter-destination media synchronization
|
The SC' shall send synchronization correlation information to the MSAS, which acts as a Third Party Monitor [44] with respect to the SC'. Synchronization correlation information has the following components. • RTCP eXtended Report (XR) related to the incoming media stream. • RTCP eXtended Report (XR) related to the outgoing media stream. XR related to the incoming media steam is specified in annex W. The XR contains the SSRC of the incoming media stream, the NTP timestamp and the Packet Received RTP timestamp. The Packet Presented RTP timestamp field shall be set empty. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 129 XR related to the outgoing media stream is specified in annex W. The XR contains the SSRC of the outgoing media stream, the NTP timestamp and the RTP time stamp. The Packet Presented RTP timestamp field shall be set empty.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
12 IPTV user profile schema
|
The IPTV user profile is described by an XML document. This XML document complies with the XML schema defined in annex C. Although it is not explicit in the XML schema described in annex C, the IPTV user profile shall comprise at least one BC profile or CoD profile. The "Global Settings" element is set to "optional" in the IPTV user profile. However, in the case where this element would not be provided, default values should be used: - the User Action Recordable Boolean should be assumed to be set to "false"; - the preferred language value should be assumed to be to one that is globally defined by the service provider (hence applicable to all users). In the case where the ParentalControlLevel is not provided, its value is assumed to be the default level defined by the service provider (hence applicable to all users). In the case where the quality definition is not provided, its default value shall be "SD".
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
13 IPTV service action data schema
|
For convenience purposes, each object class of the IPTV service action data is described by a separate XML documents. Those XML document comply with the XML schema defined in annex D. Although they are defined as optional in the XML schema described for "NPVR items" in annex D, the "BCServiceId", "RecordStartDate" and "RecordEndDate" attributes are required in the case where the NPVRContentID attribute does not refer to a Programme Id (i.e. an entry in the EPG). Bookmark and RecordStartDate attributes shall either take the form of an xs:dateTime type, or be equal to "NOW". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 130 Annex A (informative): Functional entity relations and example signalling flows of IMS based IPTV operations A.0 Example signalling flows for IPTV services Any signalling flow in annex A will follow procedures implementation details described in procedures clauses (clauses from 5 to 11). Signalling flows listed in this clause are only informative examples for selected IPTV services. If signalling flows for other IPTV services are not explicitly mentioned in annex A then signalling flows should follow procedures as described in [2], clause 8. A.1 Functional entities relations and overview of the IMS based IPTV procedures NOTE 1: This figure represents relationships and protocols between the functional entities at high level. The details of corresponding procedures and signalling flows are in the following clauses of this annex. NOTE 2: As described in TS 182 027 [2], clause 6.4 and 6.5, Xc and Xd are logical reference points that can be decomposed of Dj and possibly Di, Ds or Iz reference points depending on the location of the MCF or MDF. Figure A.1: IMS based IPTV - protocol model with FE relation 0) First of all it is needed to start or boot a UE (like a set-top-box, PC, mobile or any device with an IPTV client) and achieve network attachment to obtain network parameters (like an IP address, P-CSCF address, etc.). 1) After network attachment the UE initiate the IMS registration process with core IMS (as described in clause 5.1.1). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 131 2) UE will perform IPTV service attachment functions including SIP based service discovery to perform SDF tasks (as described in clause 5.1.2). 3) Then UE is able to initiate the service selection procedures with SSF via Xa (using HTTP over Xa as described in clause 6.1.1, using DVBSTP as in clause 9 or FLUTE 10) to receive service selection information. 4) The IMS based IPTV UE needs to know and used received service selection information to establish appropriate multimedia session by generating SIP INVITE messages during service initiation procedure (over Gm towards home C-CSCF) send via IMS core to SCF. NOTE 1: SIP based request for service initiation (SIP procedures is applicable also for service termination or termination) is used for BC service (as in clause 5.1.3), CoD service (as in clause 5.1.4) or for N-PVR Service (as in clause 5.1.7). NOTE 2: The core IMS is able to initiate resource reservation process for network resources needed by the IPTV streams according to the capabilities of the UE. The resource reservation and allocation is performed using standardized transport control functions of NGN RACS connected to the core IMS. 5) to 6) After the successful session initiation, the SCF informs the MCF via core IMS and y2 interface (or UE in some case like BC) about identification of selected content from the Media Delivery Function (or ECF/EFF in the case of BC services) to initiate start streaming the selected multimedia content (CoD, N- PVR). 7) The UE may control CoD media stream over the Xc (see note 2 for figure A.1) interface (between the UE and the MCF) to control media delivery with RTSP protocol (as in clause 7). The UE may control BC media stream over the Dj interface (between the UE and the ECF/EFF) to control media delivery with IGMP/MLD protocol (as in clause 8). 8) The MDF performs media delivery over the Xd (see note 2 for figure A.1) interface is based on UDP/RTP stream delivery and several transport variants (as described in clause 11). A.2 Example signalling flows of service discovery operation A.2.1 Push mode This clause describes an example of signalling flow of the service discovery based on the Push mode. Figure A.2: Service discovery of Push mode operation 1) The UE sends a REGISTER request to the Core IMS. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 132 2) Core IMS finishs the registration, and sends the SIP 200 OK to the UE. 3) Core IMS matches the iFC of the service profile belong to the user, and finds out the SDF that user has subscribed. 4) Core IMS sends the third-party REGISTER request to the SDF. 5) The SDF acquires the register status of the UE, and sends the SIP 200 OK to the Core IMS. 6) The SDF sends the Service Attachment Information to the UE by the SIP MESSAGE request. The SDF could trigger service discovery logic, and configure the appropriate service attachment information for the user. Here the SDF could retrieve the user's location, UE's capability etc from IPTV user profile. for configure the service attachment information. 7) The Core IMS relays the SIP MESSAGE to the UE. 8) The UE receives the SIP MESSAGE with Service Attachment Information, and sends the SIP 200 OK to the SDF. 9) The Core IMS relays the SIP 200 OK to the SDF. A.2.2 Pull Mode This clause describes an example of signalling flow of the service discovery based on the Pull mode. NOTE: The UE may retrieve the PSI/address of the SDF based on mechanisms defined in annex I. Figure A.3: Service discovery of Pull mode operation 1) The UE sends a SUBSCRIBE request to the Core IMS. The SUBSCRIBE could also contain a body to carry the UE's capabilities. 2) to 3) The Core IMS forwards the SUBSCRIBE to the SDF. The Core IMS could forwards the SUBSCRIBE based on the PSI or iFC. 4) After a successful subscription, the SDF generates a SIP 200 OK in response to the SUBSCRIBE. When the SUBSCRIBE carry the UE's capabilities in the message body, the SDF examines and records UE capabilities information as part of the IPTV user profile data. 5) The Core IMS relays the SIP 200 OK to the UE. 6) The SDF generates the NOTIFY for the service attachment information. The SDF could retrieve the UE's capabilities to generate the personalized service attachment information. 7) The Core IMS relays the NOTIFY to the UE. 8) The UE receives the NOTIFY with the service attachment information, and sends the SIP 200 OK to the SDF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 133 9) The Core IMS relays the SIP 200 OK to the SDF. A.3 Example signalling flows of CoD operation A.3.1 UE-initiated session initiation NOTE: As stated in TS 182 027 [2], the SCF may originate requests to the MF without involving the core-IMS. A.3.1.1 Session initiation flows for case of establishing content control channel and content delivery channels separately using RTSP method 2 This clause describes an example signalling flow using RTSP method 2, see clauses 5.4.1.2.2, 7.1.2 and 7.2.2. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 134 NOTE 1: The procedure and flow between the CoD-MCF and CoD-MDF is out of scope of the current release. NOTE 2: After successful authorization of the service initiation request, the delivery of the keying data (with security metadata) to the UE may be initiated. This would be done in accordance to the media content protection model for IPTV as described in TS 187 003 [10]. Figure A.4 1) Initial INVITE request to Core-IMS. The INVITE offers a SDP of a media description for RTSP connection. 2) Core-IMS requires for RACS to reserve resources of RTSP connection according to the Initial INVITE. 3) Core-IMS forwards the Initial INVITE to the CoD-SCF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 135 4) When the CoD-SCF receives the Initial INVITE request from the UE, the CoD-SCF may perform service authorization. The CoD-SCF selects a CoD-MF. 5) to 6) The initial INVITE request is sent to the CoD-MF selected by the CoD-SCF. 7) to 9) SIP 200 OK for Initial INVITE is sent from CoD-MF to the Core-IMS. 10) Core-IMS requires for RACS to commit the reservation. 11) SIP 200 OK response is sent back to the UE. 12) to 15) The UE sends ACK to CoD-MF. 16) A TCP connection for RTSP is established. 17) Since a SIP dialog is established and a TCP connection for RTSP is established, the UE invokes RTSP DESCRIBE request to the CoD-MF through the established TCP connection. 18) The CoD-MF sends a SIP 200 OK with SDP. The SDP contains the media descriptions of RTP stream to be used. 19) The UE extracts the media descriptions from the SDP of the SIP 200 OK. 20) The UE sends RTSP SETUP requests to the CoD-MF through the established TCP connection. 21) SIP 200 OK for SETUP is sent back to the UE. 22) The UE sends a re-INVITE request to Core-IMS. The SDP of re-INVITE contains as follows: The session description and media description for RTSP are same as that of Initial INVITE. The media descriptions for RTP content stream(s) are same as the media descriptions of SIP 200 OK (DESCRIBE) except for address, port number, and direction attribute. The address and port number are replaced by that of UE's, and "a=recvonly" direction attribute is inserted. 23) Core-IMS requires for RACS to reserve additional resources of RTP streams according to the re-INVITE. 24) to 26) re-INVITE is sent to CoD-MF. 27) to 29) SIP 200 OK for re-INVITE is sent back to UE. 30) Core-IMS requires for RACS to commit the reservation. 31) SIP 200 OK for re-INVITE is sent back to the UE. 32) to 35) The UE sends ACK to CoD-MF. 36) RTSP PLAY request is sent to the CoD-MF. 37) SIP 200 OK for PLAY is sent back to the UE. 38) The CoD-MF starts sending RTP content streams to the UE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 136 A.3.1.2 Session initiation flows for case of establishing content control channel and content delivery channels using RTSP method 2 (1) INVITE (9) 200 OK ( INVITE) (10) ACK UE (2) INVITE (5) INVITE (6) 200 OK (INVITE) (8) 200 OK (INVITE) (11) ACK (13) ACK (4) INVITE (7) 200 OK (INVITE) (12) ACK CoD-MF Core-IMS CoD-SCF (14) Establish TCP Connection for RTSP (15) SETUP (16) 200 OK (18) 200 OK (17) PLAY (19) RTP RACS resource reservation resource commit content selection (3) Select CoD-MF Figure A.5 1) to 2) The UE sends the initial SIP INVITE request to the SCF. 3) The SCF can deny service requests packages depending on operator policy e.g. based on UE location (provided by the NASS), UE capabilities or the User Profile. The SCF selects the appropriate MF. 4) to 5) The SCF sends initial SIP INVITE request to the selected MF. 6) to 9) SIP 200 OK of initial SIP INVITE is sent back to the UE as for final session agreement. 10) to 13) SIP ACK is sent back to the MF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 137 14) TCP connection for the RTSP content control channel is established between the UE and the MF. The UE detects that the RTSP related SDP data negotiated during the preceding steps. If the RTSP session ID parameter is missing in this SDP, as described in clause 5.1.4.2.1, the UE knows that no RTSP session exists at the MF. Therefore the UE will use RTSP SETUP to trigger RTSP session initiation. 15) The UE sends an RTSP SETUP request to the MF. 16) RTSP 200 OK for RTSP SETUP is sent back to the UE. The RTSP network parameters exchanged during steps 15 and 16 equal the RTSP network parameters as agreed in steps 1 to 13. If the MF or the UE detect deviating parameters they react with appropriate error messages and terminate SIP and RTSP sessions. 17) RTSP PLAY request is sent to the MF. 18) RTSP 200 OK for RTSP PLAY is sent back to the UE. 19) The RTP stream is sent to the client IP address as indicated by SIP SDP and RTSP SETUP. A.3.1A SCF-initiated session initiation The procedures for SCF-initiated CoD session are based on RFC 3725 [i.16] - Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP), Flow I., see figure A.5A. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 138 CoD-SCF UE CoD-MF Core IMS RACS 7. INVITE 9. 200 OK 6. Select CoD-MF 1. INVITE no SDP 2. INVITE no SDP 8. INVITE 10. 200 OK 3. 200 OK 5. 200 OK 11. ACK 12. ACK 13. ACK 15. ACK 4. Resource Reservation 14. Resource Commit Method 1: Steps 16 onwards from Figure A.4 in A.3.1.1 Method 2: Steps 14 onwards from Figure A.5 in A.3.1.2 Figure A.5A: SCF-initiated CoD session 1) The SCF sends an initial INVITE to the Core IMS. For example when a user has preselected content 2) The INVITE is forwarded to the UE 3) The UE accepts the INVITE and send a SIP 200 OK to the Core IMS 4) The Core IMS reserves resources based on the SDP offer from the UE 5) The Core IMS forwards the SIP 200 OK to the SCF 6) The SCF selects a CoD-MF 7) The SCF sends an INVITE with the offer of the UE to the selected MF through the Core IMS 8) The Core IMS forwards the INVITE to the MF 9) The MF accepts the request and sends a SIP 200 OK with an SDP answer to the Core IMS 10) The Core IMS forwards the SIP 200 OK to the SCF 11) The SCF sends an ACK to the MF through the Core IMS ETSI ETSI TS 183 063 V3.6.1 (2014-08) 139 12) The Core IMS forwards the ACK to the MF 13) The SCF sends an ACK with an SDP answer to the UE through the Core IMS 14) The Core IMS commits the resource reservation 15) The Core IMS forward the ACK to the UE After receiving the ACK the UE can use one of two methods to start receiving the media stream. These are the same for UE-initiated CoD session initiation and SCF-initiated CoD session initiation, and figure A.5 refers to these steps described in clause A.3.1. A.3.2 Session termination NOTE: The procedure and flow between the CoD-MCF and CoD-MDF is out of scope of the current release. Figure A.6 1) TEARDOWN request is sent to CoD-MF. 2) CoD-MF stops sending RTP content streams. 3) The CoD-MF responds with RTSP 200 OK response. 4) The UE disconnects the TCP connection of RTSP. 5) The UE sends the BYE request towards Core-IMS. 6) Core-IMS requires for RACS to release resources. 7) to 9) BYE is sent to CoD-MF. 10) to 13) SIP 200 OK is sent back to the UE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 140 A.3.3 Session modification A.3.3.1 Session modification initiated by MF UE RACS Core-IMS CoD-SCF CoD-MF 1. INVITE 3. INVITE 6. INVITE 7. 200 OK 12. ACK 15. ACK 22. 200 OK 5. INVITE 4 . select CoD-MCF 11. 200 OK 16. Establish TCP Connection for RTSP 13. ACK 14. ACK 18. re- INVITE 19. re- INVITE 24. 200 OK 25. 200 OK 2. Resource Reservation 10. Resource Commit 20. Resource Reservation 23. Resource Commit 30. ACK 27. ACK 28. ACK 29. ACK 8. 200 OK 9. 200 OK content selection 21. re- INVITE 26. 200 OK 17. re- INVITE NOTE: The procedure and flow between the CoD-MCF and CoD-MDF is out of scope of the current release. Figure A.7 1) Initial INVITE request to Core-IMS. The INVITE offers a SDP of a media description for RTSP connection. 2) Core-IMS requires for RACS to reserve resources of RTSP connection according to the Initial INVITE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 141 3) Core-IMS forwards the Initial INVITE to the CoD-SCF. 4) When the CoD-SCF receives the Initial INVITE request from the UE, the CoD-SCF may perform service authorization. The CoD-SCF selects a CoD-MF. 5) to 6) The initial INVITE request is sent to the CoD-MF selected by the CoD-SCF. 7) to 9) SIP 200 OK for Initial INVITE is sent from CoD-MF to the Core-IMS. 10) Core-IMS requires for RACS to commit the reservation. 11) SIP 200 OK response is sent back to the UE. 12) to 15) The UE sends ACK to CoD-MF. 16) A TCP connection for RTSP is established. 17) The CoD-MF sends a re-INVITE request to Core-IMS to establish the content delivery channel. 18) to 19) The re-INVITE request is routed back to Core-IMS via the CoD-SCF. 20) Core-IMS requires for RACS to reserve additional resources of RTP streams according to the re-INVITE. 21) re-INVITE is sent to the UE. 22) The UE sends SIP 200 OK with SDP. The SDP contains the media descriptions of RTP stream to be used. 23) Core-IMS requires for RACS to commit the reservation. 24) to 26) SIP 200 OK is sent to the CoD-MF. 27) to 30) The CoD-MF returns ACK to the UE. A.4 Example signalling flows of BC operation A.4.1 UE-initiated session initiation This clause describes an example of signalling flow of session initiation when the UE retrieves network parameters from the SSF. Figure A.8: Session initiation of BC operation ETSI ETSI TS 183 063 V3.6.1 (2014-08) 142 1) The UE initiates BC Service. The SIP INVITE message contains BW requirements for this session and a list of Service packages and multicast addresses to be authorized during the session. 2) Core IMS identifies this is as a BC service session initiation and reserves the resources with RACS. 3) The INVITE message is forwarded to the SCF. The SCF validates the list of requested service packages against the subscriber profile associated with the UE. The SCF may remove some service packages or replace one with a list of multicast addresses. 4) The IPTV application sends the positive result to the IMS core. 5) Core IMS modifies the reservation and aligns it with any modification the SCF made, as described in step 2. Core IMS commits the reservation with RACS. 6) Core IMS forwards the result to the UE. 7) UE sends ACK towards SCF. 8) Core-IMS routes the ACK message to SCF. 9) The UE joins the multicast address indicated in the response. 10) Content is delivered. NOTE: After successful authorization of the service initiation request, the derivation and delivery of further necessary keying material to the UE may be initiated to enable decryption of BC streams in real time (in accordance to the media content protection model for IPTV as described in TS 187 003 [10]). This can be done statically prior to the content delivery or dynamically during the content delivery. A.4.1A SCF-initiated session initiation BC-SCF UE ECF/EFF Core IMS RACS 1. INVITE 3. INVITE 4. 200 OK 6. 200 OK 7. ACK 8. ACK 2. Resource Reservation 5. Resource Commit 9. Multicast Join 10. Media Stream Figure A.8A: SCF-initiated BC session 1) The SCF sends an initial INVITE to the Core IMS. For example when a user has preselected content. 2) The Core IMS reserves resources based on the SDP offer from the SCF. 3) The INVITE is forwarded to the UE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 143 4) The UE accepts the INVITE and send an 200 OK to the Core IMS. 5) The Core IMS commits the resource reservation. 6) The Core IMS forwards the SIP 200 OK to the SCF. 6) The SCF sends an ACK the the UE. 8) The Core IMS forwards the ACK to the UE. 9) The UE joins the multicast address. 10) Content is delivered. A.4.2 Session termination This clause describes an example of signalling flow of session termination. Figure A.9: Session termination of BC operation 1) The UE sends a multicast Leave request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD)) to stop receiving multicast media stream. The UE populates the message as follows: - Multicast Address field is set to the multicast address to be left. - If the protocol is IGMPv3 or MLDv2: If source addresses have been set in the Join message, the same source address list is excluded from the listening interface; the Record Type is set to "BLOCK_OLD_SOURCES" and Source list is set to the source address. If no source address has been set in the Join message, Filter Change record is set to INCLUDE with an empty source list. 2) The UE sends a BYE request to Core-IMS. 3) Core-IMS requires for RACS to release resources. 4) Core-IMS forwards a BYE to the BC-SCF. 5) to 6) The BC-SCF responds with SIP 200 OK response and the SIP session is terminated. A.4.3 Channel switching This clause describes two examples of signalling flow of channel switching. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 144 A.4.3.1 Join after leave Figure A.10: Changing multicast channels of BC operation (2 messages) 1) The UE sends a multicast Leave request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD)) to stop receiving the multicast media stream of the old channel. 2) The UE sends a multicast Join request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD)) to start receiving the multicast media stream of the new channel. 3) to 4) If the UE remains on the selected channel for a period of time greater than a preconfigured value (example 10 seconds), the UE may inform the SCF of selected channel. 5) to 6) The SCF replies with a SIP 200 OK. A.4.3.2 Leave and Join at the same time If the Transport Function is using IGMPv3 or MLDv2, the UE may choose to send a single IGMP message containing the Leave request and the Join request, for leaving the old channel and joining the new channel. This is depicted in figure A.11. Figure A.11: Changing multicast channels of BC operation (single message) 1) The UE sends a combined multicast Leave/Join request (Membership Report Message (IGMP) or Multicast Listener Report Message (MLD)) to stop receiving the multicast media stream of the old channel and start receiving the multicast media stream of the new channel. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 145 A.5 Example signalling flows for inter-destination media synchronization A.5.1 Inter-destination media synchronization flows for SIP signalling A.5.1.0 General The functional entity "MSAS" in this clause refers to the session-level MSAS, see also clause 4.2.8. A.5.1.1 Inter-destination media synchronization of a BC service This clause describes an example SIP signalling flow to initiate up a using synchronization session initiation from clause 5.7.1.1. Figure A.12: SIP signalling for the session set-up of inter-destination media synchronization of a BC service NOTE: To simplify signalling flows, details on the inclusion of the IMS Core, resource reservations, on specific content control and delivery flows, etc. have been omitted. Only those parts of the SIP signalling flow are shown that are relevant for inter-destination media synchronization. See clauses 5.1.3. and 5.3.1. for further details on BC operation. 1) The SC sends the initial SIP INVITE request to the MSAS. This SIP INVITE requests contains the synchronization group identifier (SyncGroupId). See clause 5.7.1.1 for details on the use of SyncGroupId. 2) The MSAS responds with a SIP 200 OK, which contains the SyncGroupId and adds the MSAS parameters (SSRC-ID, address and port number and RTCP SyncGroupID) in the SDP description. Since the MSAS modifies the SC offer, it acts as a B2BUA. 3) SIP ACK is sent back to the MSAS. A.5.1.2 Inter-destination media synchronization of a CoD service using RTSP method 1 This clause describes an example SIP signalling flow to initiate a synchronization session from clauses 5.4.10.1, 5.7.1.1 and 5.8.1.1 using RTSP method 1. SC 1. INVITE 2. 200 OK 3. ACK MSAS ETSI ETSI TS 183 063 V3.6.1 (2014-08) 146 Figure A.13: SIP signalling for the session set-up of inter-destination media synchronization of a COD service using RTSP method 1 NOTE: To simplify signalling flows, details on the inclusion of the IMS Core, resource reservations, on specific content control and delivery flows, etc. have been omitted. Only those parts of the SIP signalling flow are shown that are relevant for inter-destination media synchronization. See clauses 5.1.4, 5.3.2 and 5.4.1 for further details on CoD RTSP method 1 operation. 1) The SC sends the initial SIP INVITE request to the MSAS. This SIP INVITE requests contains the synchronization group identifier (SyncGroupId). See clause 5.7.1.1 for details on the use of SyncGroupId. 2) The MSAS forwards the SIP INVITE to the MF, adding the MSAS parameters details (address and port number and RTCP SynGroupID) in the SDP description. Since the MSAS modifies the SC offer, it acts as a B2BUA. 3) The MF assigns SSRC to the media RTP stream and sends a SIP 200 OK to the MSAS, adding the SSRC to the SDP description of the media. 4) The MSAS forwards the SIP 200 OK to the SC, containing the SyncGroupId, the MSAS address and the SSRC. 5) to 6) SIP ACKs are sent. A.5.1.3 Inter-destination media synchronization of a CoD service using RTSP method 2 This clause describes an example combined SIP and RTSP signalling flow to initiate a using synchronization session initiation from clauses 5.4.10.1, 5.7.1.1 and 5.8.1.1, 7.2.4 and 7.3.1, using RTSP method 2. SC MSAS MF 1. INVITE 2. INVITE 3. 200 OK 4. 200 OK 5. ACK 6. ACK ETSI ETSI TS 183 063 V3.6.1 (2014-08) 147 Figure A.14: Combined SIP and RTSP signalling for the session set-up of inter-destination media synchronization of a COD service using RTSP method 2 NOTE 1: To simplify signalling flows, details on the inclusion of the IMS Core, resource reservations, on specific content control and delivery flows, etc. have been omitted. Only those parts of the combined SIP and RTSP flow are shown that are relevant for inter-destination media synchronization. See clauses 5.1.4, 5.3.2, 5.4.1, 7.1.2 and 7.2.2. for further details on CoD RTSP method 2 operation. 1) The SC sends the initial SIP INVITE request to the MSAS. This SIP INVITE requests contains the synchronization group identifier (SyncGroupId). see clause 5.7.1.1 for details on the use of SyncGroupId. 2) The MSAS forwards the SIP INVITE to the MF, adding the MSAS parameters details (address and port number and RTCP SynGroupID) in the SDP description. Since the MSAS modifies the SC offer, it acts as a B2BUA. 3) This step flows step 3 of clause A.5.1.2. NOTE 2: The MF is allowed to wait assigning an SSRC and to send a SIP 200 OK to the MSAS without adding the SSRC to the SDP description of the media. 4) This step flows step 4 of clause A.5.1.2. NOTE 3: It is allowed that the MSAS forwards the SIP 200 OK to the SC, containing only the SyncGroupId and the MSAS address. 5) to 6) SIP ACKs are sent. 7) The SC invokes RTSP DESCRIBE request to the MF.s 8) If the MF has not conveyed the SSRC towards the MSAS in step 3, the MF assigns an SSRC and sends 200 OK with SDP. The SDP contains the SSRC as an attribute in the SDP description. A.5.2 Inter-destination media synchronization flows for RTCP signalling A.5.2.0 General The functional entity "MSAS" in this clause refers to the media-level MSAS, see also clause 4.2.8. SC MSAS MF 1. INVITE 2. INVITE 3. 200 OK 4. 200 OK 5. ACK 6. ACK 7. DESCRIBE 8. 200 OK ETSI ETSI TS 183 063 V3.6.1 (2014-08) 148 A.5.2.1 Inter-destination media synchronization of BC service This clause describes an example RTCP signalling flow for the exchange of using synchronization status and settings instructions exchange from clause 11.3 and 11.4. Figure A.15: RTCP signalling for the exchange of synchronization status and settings instructions for a BC service NOTE 1: To simplify signalling flows, details on the inclusion of the IMS Core, resource reservations, on specific content control and delivery flows, etc. have been omitted. Only those parts of the flow are shown that are relevant for inter-destination media synchronization. 1) The SC sends RTCP Receiver Report (RR) to the MSAS. This report includes t includes an eXtended Report (XR) containing the synchronization status information according to annex W. 2) The MSAS sends an RTCP XR containing synchronization settings instructions directly to the SC, according to annex W. NOTE 2: The MSAS may forward RTCP RR to the source of the media, see also clause 11 on the use of RTCP. RTCP SR are sent directly from media source to SC. A.5.2.2 Inter-destination media synchronization of CoD service This clause describes an example RTCP signalling flow for the exchange of using synchronization status and settings exchange from clauses 11.3 and 11.4. Figure A.16: RTCP signalling for the exchange of synchronization status and settings instructions for a CoD service 1. RTCP RR + XR(status) 2. RTCP XR(settings) SC MSAS SC MSAS MF 1. RTCP RR + XR(status) 2. RTCP RR 3. RTCP SR 4. RTCP SR + XR(settings) ETSI ETSI TS 183 063 V3.6.1 (2014-08) 149 NOTE: To simplify signalling flows, details on the inclusion of the IMS Core, resource reservations, on specific content control and delivery flows, etc. have been omitted. Only those parts of the flow are shown that are relevant for inter-destination media synchronization. 1) The SC sends RTCP Receiver Report (RR) to the MSAS. This report includes includes an eXtended Report (XR) containing the synchronization status information, according to annex W. 2) The MSAS removes the XR from the RR and forwards the RR to the source of the media. 3) The MF sends its RTCP Sender Reports (SR) to the MSAS. 4) The MSAS adds the XR containing the settings instructions to the SR according to annex W, and forwards this to the SC. A.5.2.3 RTCP exchange between UEs directly This clause describes an example RTCP flow for inter-destination media synchronization between two UEs directly. Both UE1 and UE2 have SC functionality. UE1 acts also as MSAS, see figure A.17. If the RTP/RTCP flows are handled by a server (e.g. a conference bridge), then the MSAS functionality may also be located there. UE1 UE2 SC2 SC1 MSAS Sync Figure A.17: UE acting as MSAS for inter-destination media synchronization between UEs Figure A.18 shows an example RTCP flow for inter-destination media synchronization between two UEs directly. MF SCF UE1 (MSAS) UE2 (SC) 1. RTP/RTCP exchange 4. RTCP RR + XR (status) 5. RTCP XR (settings) 2. BC/CoD session 3. BC/CoD session Figure A.18: RTCP signalling for the exchange of synchronization status and settings instructions between UEs directly ETSI ETSI TS 183 063 V3.6.1 (2014-08) 150 1) UE1 and UE2 have a media session, which includes regular RTP/RTCP exchange for the media transport and transport control. 2 to 3) UE1 and UE2 each have a BC or CoD session for the same service and content. 4 to 5) UE1 and UE2 reuse their regular RTCP SRs and RRs to append RTCP Extended Reports (XR) [45] for the exchange of synchronization information. See also clauses 11.3 and 11.4. UE1 and UE2 have to obtain the SyncGroupID, the SSRC value and the MSAS address (=UE1 address) before step 4. These may be obtained using the procedures as described in clauses 5.4.10, 5.7.1.1, 5.8.1.1 and 7.3. A.5.2.4 RTCP exchange for sync' This clause describes an example RTCP flow for sync', see figure A.19. MSAS SC’ 1. RTCP XR (correlation) Figure A.19: RTCP flow for sync' 1) SC' sends MSAS synchronization correlation information: RTCP eXtended Reports (XR) related to the incoming media stream and RTCP eXtended Reports (XR) (annex W) related to the outgoing media stream, see annex W. Synchronization correlation information may be sent from SC' to MSAS at regular pre-configured time intervals. Figure A.20 are example RTCP XR messages for sync', see also annex W. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 151 Figure A.20: Example RTCP messages for sync' A.6 Example signalling flows of content insertion A.6.1 Content insertion at the UE This flow shows an example of content insertion that is triggered by an event detected at the SCF, e.g. for targeted ad insertion. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |V=2|P|reserved | PT=XR=207 | length=9 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of packet sender SC' | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | BT=9 |SPST=3 |0| block length=7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PT | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Media Stream Correlation Identifier, same for in and out | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of incoming media stream | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, most significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, least significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received RTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Presented NTP timestamp = empty | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ |V=2|P|reserved | PT=XR=207 | length=9 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of packet sender SC' | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | BT=9 |SPST=4 |0| block length=7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PT | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Media Stream Correlation Identifier, same for in and out | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of outgoing media stream | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, most significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, least significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received RTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Presented NTP timestamp = empty | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ ETSI ETSI TS 183 063 V3.6.1 (2014-08) 152 Figure A.21 0) An ongoing session exists between UE and MF for BC with trick play or CoD. 1) The SCF detects an event that triggers the content insertion and selects the appropriate content to be inserted. The SCF can determine the duration of the content insertion depending on e.g. the (expected) length of the time interval that is available for content insertion, the user identity, the semantic context of the content in the ongoing session, the geographic location of the UE and its local time. 2) The SCF sends a notification to the UE concerning content insertion with SIP INFO, according to clause 5.3.12.1. 3) The UE sends initiates a new session for the inserted content with SIP INVITE. The INVITE contains Service Action Data, according to clause 5.1.13. 4) A new session starts for content insertion. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 153 A.6.2 Content insertion at the UE during pause This flow shows an example of content insertion that is triggered at a user request, when a user pauses CoD content. Figure A.22 0) An ongoing session exists between UE and MF for BC with trick play or CoD. 1) The UE sends an RTSP PAUSE to the MF. 2) The UE informs the SCF of the paused content with SIP INFO. 3) The SCF selects the appropriate content to be inserted. The SCF can determine the duration of the content insertion depending on e.g. the (expected) length of the time interval that is available for content insertion, the user identity, the semantic context of the content in the ongoing session, the geographic location of the UE and its local time. In the case of content insertion during a pause, The (expected) length of the time interval is indicated by the UE in the INFO message. 4) The SCF sends a notification to the UE concerning content insertion with SIP INFO, according to clause 5.3.12.1. 5) The UE sends initiates a new session for the inserted content with SIP INVITE. The INVITE contains Service Action Data, according to clause 5.1.13. 6) A new session starts for content insertion. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 154 A.7 Example signalling flows for session transfer The call flow shows an example of session transfer push mode where the session is pushed from the transferor to the transferee. Note that in the call flow it is assumed that the SCC application server is embedded in the SCF. This is for convenience and can indeed be a stand alone accplication server with no change to the general procedure. The following is a brief description of the steps in the call flow: a) Initially the transferor has established a CoD session as per clause 5.4.1. b) To select the device to which the transferor can push the session, the transferor subscribes to the registration event package to receive a list of registered devices. This is accomplished in steps 1 and 2 in the call flow. c) The UE receives the list of registered in devices in the SIP NOTIFY in step 3, and responds to it in step 4 with a SIP 200 OK. d) The transferor selects the device, and then sends a SIP REFER targeted to that device. This is accomplished in steps 5 and 6. e) The transferee receives the SIP REFER, extracts the pertinent information and responds with a SIP 200 OK Accepted to the transferee in steps 7 and 8. f) The transferor now attempts to establish the new CoD session as per the procedure defined in clause 5.4.1. g) Following the successful establishment of the session, the SCC AS clears the old session; This is accomplished through steps 10 and 11. h) The transferee than notifies the transferor of the successful transfer of the session through steps 12 to 15. i) The transferee then starts playing the content from the received bookmark and the transfer procedure has now been successfully completed. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 155 Annex B (normative): IPTV services XCAP application usage B.1 General For the purpose of manipulating data stored in an application server the XML Configuration Access Protocol (XCAP) defined in RFC 4825 [9] is used. XCAP allows a client to read, write and modify application configuration data, stored in XML format on a server. XCAP maps XML document sub-trees and element attributes to HTTP URIs, so that these components can be directly accessed by HTTP. XCAP uses the HTTP methods PUT, GET and DELETE to operating on XML documents stored in the server. In the case of IPTV services, the data stored in a server is related to the execution of that given service. The present document defines a new XCAP Application Usage for the purpose of allowing a client to manipulate data related to IPTV services. This application usage defines the XML schema for the data used by the application, along with other key pieces of information. XCAP defines two logical roles: XCAP client and XCAP servers. An XCAP client is an HTTP/1.1 compliant client. Similarly an XCAP server is an HTTP/1.1 compliant server. The XCAP server acts as a repository of XML documents that customize and modify the execution of IPTV services. XCAP focuses on the definition of XML documents that are compliant with the XML schema and constrains defined for a particular XCAP application usage. XCAP allows application to provide XML documents that are common for all users or XML documents that affect the service of a given user. Central to XCAP is the construction of the HTTP URI that points to particular XML document or certain components of it. A component in an XML document can be an XML element, attribute, or the value of it. B.2 XCAP application usage XCAP requires application usages to fulfil a number of steps in the definition of such application usage. The remainder of this clause specifies the required definitions of the IPTV services XCAP Application Usage. Application Unique ID (AUID): Each XCAP application usage is associated with a unique name called the Application Unique ID (AUID). The AUID defined by this application usage falls into the vendor-proprietary namespace of XCAP AUID, where ETSI is considered a vendor. The AUID allocated to the NGN IPTV services XCAP application usage is: org.etsi.ngn.iptv XML schema: Implementations in compliance with the present document shall implement the XML schema defined in annex C default namespace: XCAP requires application usages to declare the default namespace. The default namespace of the IPTV services XCAP application usage is: urn:org:etsi:ngn:params:xml:ns:iptv MIME type: The MIME type of IPTV services XML documents is: application/vnd.etsi.iptvprofile+xml validation constraints: The present document does not specify any additional constraint beyond those defined by XCAP. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 156 data semantics: The XML schema does not accept URIs that could be expressed as a relative URI reference causing a resolution problem. However, each of the supplementary services should consider if relative URIs are allowed in the subdocument tree, and in that case, they should indicate how to resolve relative URI references. In the absence of further indications, relative URI references should be resolved using the document URI as the base of the relative URI reference. naming conventions: By default, NGN IPTV services XML documents are stored under the user's Home Directory (which is located under the "users" sub-tree). In order to facilitate the manipulation of an NGN IPTV services XML document, we define a default XML file name: iptvprofile.xml resource interdependencies: The present document does not specify additional resource interdependency beyond those specified in the XML schema. authorization policies: The default XCAP authorization policy is used in the application usage defined by the present document. NOTE: The default policy indicates that the creator of the XML document is the one that is authorized to manipulate it. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 157 Annex C (normative): XML Schema for the IPTV profile This annex specifies an XML schema for creating documents representing instances of the IPTV profile described in TS 182 027 [2]. This XML schema is used when IPTV profile is manipulated with the XCAP procedure described in clauses 6.1.2.1, 6.2.1.2, and annex B. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns:iptvueprofile" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvueprofile" schemaLocation="Annex P_XML Schema for UE Profile.xsd"/> <xs:element name="IPTVProfile"> <xs:annotation> <xs:documentation> XML Schema for representing the IPTV Profile object identified in TS 182 027 clause 7.3.1 </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="UEProfile" type="uep:tUEProfile" minOccurs="0"/> <xs:element name="GlobalSettings" type="tGlobalSettings" minOccurs="1"/> <xs:element name="BCProfile" type="tBCProfile" minOccurs="0"/> <xs:element name="CoDProfile" type="tCoDProfile" minOccurs="0"/> <xs:element name="PVRProfile" type="tPVRProfile" minOccurs="0"/> <xs:element name="PChProfile" type="tPChProfile" minOccurs="0"/> <xs:element name="UGCProfile" type="tUGCProfile" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="ProfileId" type="xs:ID" /> <xs:anyAttribute/> </xs:complexType> </xs:element> <xs:complexType name="tBCProfile"> <xs:sequence> <xs:element name="BCServicePackage" type="tBCServicePackage" minOccurs="1" maxOccurs="unbounded"/> <xs:element name="IPTVContentMarkerAuthorizedViewUser" type="xs:string" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="IPTVContentMarkerSourceUser" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tBCServicePackage"> <xs:sequence> <xs:element name="BCPackageId" type="tBCServicePackageID" minOccurs="1"/> <xs:element name="Description" type="tBCServicePackageDescription" minOccurs="0"/> <xs:element name="BCService" type="tBCService" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tBCServicePackageID" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 158 <xs:simpleType name="tBCServicePackageDescription" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="64"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tBCService"> <xs:sequence> <xs:element name="BCServiceId" type="tBCServiceID" minOccurs="1"/> <xs:element name="QualityDefinition" type="tQualityDefinition" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tBCServiceID" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tQualityDefinition" final="list restriction"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">SD</label> <definition xml:lang="en">Standard Definition</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> <label xml:lang="en">HD</label> <definition xml:lang="en">High Definition</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tCoDProfile"> <xs:sequence> <xs:element name="ParentalControl" type="tParentalControlLevel" minOccurs="0"/> <xs:element name="IPTVContentMarkerAuthorizedViewUser" type="xs:string" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="IPTVContentMarkerSourceUser" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tParentalControlLevel" final="list restriction"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="5"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">ALL</label> <definition xml:lang="en">All contents</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 159 <xs:annotation> <xs:documentation> <label xml:lang="en">Level 1</label> <definition xml:lang="en">Level 1 contents</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="2"> <xs:annotation> <xs:documentation> <label xml:lang="en">Level 2</label> <definition xml:lang="en">Up to level 2</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="3"> <xs:annotation> <xs:documentation> <label xml:lang="en">Level 3</label> <definition xml:lang="en">Up to level 3</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="4"> <xs:annotation> <xs:documentation> <label xml:lang="en">Level 4</label> <definition xml:lang="en">Up to level 4</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="5"> <xs:annotation> <xs:documentation> <label xml:lang="en">Level 5</label> <definition xml:lang="en">Up to level 5</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tPVRProfile"> <xs:sequence> <xs:annotation> <xs:documentation> Unit of the StorageLimitInVolume element is the GigaOctet </xs:documentation> </xs:annotation> <xs:element name="PVRPreference" type="tPVRPreference"/> <xs:element name="StorageLimitInTime" type="tNPVRStorageLimitInTime" minOccurs="0"/> <xs:element name="StorageLimitInVolume" type="tNPVRStorageLimitInVolume" minOccurs="0"/> <xs:element name="AuthorizedControlUser" type="tAuthorizedControlUser" minOccurs="0"/> <xs:element name="IPTVContentMarkerAuthorizedViewUser" type="xs:string" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="IPTVContentMarkerSourceUser" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tPVRPreference" final="list restriction"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">Network</label> <definition xml:lang="en">Recording is done in the network</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 160 <label xml:lang="en">User_Equipment</label> <definition xml:lang="en">Recording is done on the user equipment</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:simpleType name="tNPVRStorageLimitInTime"> <xs:restriction base="xs:duration"> <xs:minInclusive value="PT0H"/> <xs:maxInclusive value="PT1000000000H"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tNPVRStorageLimitInVolume"> <xs:restriction base="xs:nonNegativeInteger"/> </xs:simpleType> <xs:simpleType name="tAuthorizedControlUser" final="list restriction"> <xs:restriction base="xs:string"/> </xs:simpleType> <xs:complexType name="tGlobalSettings"> <xs:sequence> <xs:element name="LanguagePreference" type="tLanguage" minOccurs="0"/> <xs:element name="UsersActionRecordable" type="tUserActionRecordable"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tLanguage"> <xs:restriction base="xs:string"> <xs:annotation> <xs:documentation> <definition xml:lang="en">ISO 639-2 Language code</definition> </xs:documentation> </xs:annotation> <xs:minLength value="3"/> <xs:maxLength value="3"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tUserActionRecordable"> <xs:restriction base="xs:boolean"/> </xs:simpleType> <xs:complexType name="tPChProfile"> <xs:sequence> <xs:element name="PChList" minOccurs="1" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="PChItem" minOccurs="1" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="PChItemServiceType" type="xs:string" /> <xs:element name="PChItemContentId" type="xs:anyURI" /> <xs:element name="PChItemStartTime" type="xs:dateTime" /> <xs:element name="PChItemEndTime" type="xs:dateTime" /> <xs:element name="PChItemOffset" type="xs:duration" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="PChId" type="xs:anyURI" use="required"/> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 161 <xs:complexType name="tUGCProfile"> <xs:sequence> <xs:element name="UGCProfile" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="UGCStorageLimit" type="xs:unsignedInt"/> <xs:element name="AuthorizedControlUser" type="xs:string" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:schema> NOTE 1: The list of parameter that could be sent to the UE over UT is specified in the procedures clause. NOTE 2: The UE profile used for service discovery may be considered in the same XML schema, indicating explicitly which part to used for the different purposes. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 162 Annex D (normative): XML Schema for IPTV commands <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvactiondatacommand" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvactiondatacommand" xmlns:bc ="urn:org:etsi:ngn:params:xml:ns:iptvbcserviceactiondata" xmlns:co ="urn:org:etsi:ngn:params:xml:ns:iptvcodserviceactiondata" xmlns:np ="urn:org:etsi:ngn:params:xml:ns:iptvnpvrserviceactiondata" xmlns:cp ="urn:org:etsi:ngn:params:xml:ns:iptvcpvrserviceactiondata" xmlns:ci ="urn:org:etsi:ngn:params:xml:ns:iptvcontentinsertionserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvbcserviceactiondata" schemaLocation="Annex K_XML Schema for BC service related data.xsd"/> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvcodserviceactiondata" schemaLocation="Annex K_XML Schema for CoD service related data.xsd"/> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvnpvrserviceactiondata" schemaLocation="Annex K_XML Schema for N-PVR service related data.xsd"/> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvcpvrserviceactiondata" schemaLocation="Annex K_XML Schema for CPVR service related data.xsd"/> <xs:import namespace="urn:org:etsi:ngn:params:xml:ns:iptvcontentinsertionserviceactiondata" schemaLocation="Annex K_XML Schema for Content Insertion service related data.xsd"/> <xs:element name="IPTVActionDataCommand"> <xs:complexType> <xs:choice> <xs:element name="Notify" type="tNotify" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Record" type="tRecord" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SwitchToTM" type="tSwitchToTM" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SwitchToBC" type="tSwitchToBC" minOccurs="0" maxOccurs="unbounded"/> </xs:choice> </xs:complexType> </xs:element> <xs:complexType name="tNotify"> <xs:choice> <xs:element ref="bc:IPTVBcActionData" /> <xs:element ref="co:IPTVCodActionData" /> <xs:element ref="np:IPTVNpvrActionData" /> <xs:element ref="cp:IPTVCpvrActionData" /> <xs:element ref="ci:IPTVContentInsertionActionData"/> </xs:choice> </xs:complexType> <xs:complexType name="tRecord"> <xs:choice> <xs:element ref="bc:IPTVBcActionData" /> <xs:element ref="np:IPTVNpvrActionData" /> <xs:element ref="cp:IPTVCpvrActionData" /> </xs:choice> </xs:complexType> <xs:complexType name="tSwitchToTM"> <xs:choice> <xs:element ref="bc:IPTVBcActionData" /> </xs:choice> </xs:complexType> <xs:complexType name="tSwitchToBC"> <xs:choice> <xs:element ref="bc:IPTVBcActionData" /> </xs:choice> </xs:complexType> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 163 </xs:schema> NOTE: Table D.1 recaps the presence of each element in the Service Action Data for the different commands. Table D.1 Notify UE - > CN Notify UE < - CN Record UE - > CN SwitchToTM UE - > CN SwitchToBC UE - > CN IPTVBcActionData BCServiceId O M M M M ProgrammeId O O O x x Bookmark O O M x x BookmarkExpiryTime O O O x x IPTVCodActionData CoDId M M NA NA NA CoDDeliveryStatus M(parked) M CoDOffset M M CoDOffsetExpiryTime x O IPTVNpvrActionData NPVRContentId NA M O NA NA BCServiceId M M RecordStartDate M O RecordEndDate M O RecordStatus M x RecordOffset M O RecordOffsetExpiryTime O x RecordExpiryTime O x IPTVCpvrActionData CPVRContentId NA M O NA NA BCServiceId M M TargetUEId M M RecordStartDate M O RecordEndDate M O RecordStatus M X IPTVContentInsertionActionData IPTVContentIdentifier M M NA NA NA InsertedContentIdentifier M M InsertionTime O O InsertionStatus M M NOTE: M = Mandatory. O = Optional. X = Not included. NA = Not Applicable. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 164 Annex E (normative): XML schema for IPTV presence document extension This XML schema is to be used when the presence documents are published by the UE as described in clause 5.1.6. <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvpresence" xmlns:ns="urn:org:etsi:ngn:params:xml:ns:iptvpresence" xmlns:oma="urn:oma:xml:prs:pidf:oma-pres" xmlns:ss="urn:org:etsi:ngn:params:xml:ns:iptv" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:complexType name="tBCServicePresence"> <xs:sequence> <xs:element name="CurrentBCServiceID" type="ns:tBCServiceID" minOccurs="0"/> <xs:element name="CurrentBCProgramID" type="ns:tCurrentBCProgramID" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tCoDServicePresence"> <xs:sequence> <xs:element name="CurrentCODContentID" type="ns:tCurrentContentID" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tNPVRServicePresence"> <xs:sequence> <xs:element name="CurrentNPVRContentID" type="ns:tCurrentContentID" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tCurrentBCProgramID" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="256"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tCurrentContentID" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="256"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tBCServiceID" final="list restriction"> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tServiceAccessHistory"> <xs:sequence> <xs:element name="ServiceType" type="ns:tServiceType" minOccurs="0"/> <xs:element name="ReferencedContentID" type="ns:tReferencedContentID" minOccurs="0"/> <xs:element name="Rating" type="ns:tRating" minOccurs="0"/> <xs:element name="AccessStartTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="AccessEndTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="HistoryExpireTime" type="ns:tHistoryExpireTime" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tServiceType" final="list restriction"> <xs:restriction base="xs:string"> <xs:enumeration value="BC"/> <xs:enumeration value="CoD"/> <xs:enumeration value="PVR"/> <xs:enumeration value="Time Shift"/> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 165 <xs:enumeration value="UGC"/> <xs:enumeration value="SSC"/> <xs:enumeration value="PSC"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tReferencedContentID" final="list restriction"> <xs:annotation> <xs:documentation xml:lang="en"> Identifier of the associated content accessed by the user in the context of specific ServiceType. </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tRating" final="list restriction"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="5"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tHistoryExpireTime" final="list restriction"> <xs:restriction base="xs:duration"> <xs:minInclusive value="PT0H"/> <xs:maxInclusive value="PT10000H"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tServiceStateDataPresence"> <xs:sequence> <xs:element name="IPTVServiceState" type="ns:tIPTVServiceState" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tIPTVServiceState"> <xs:annotation> <xs:documentation xml:lang="en"> Depending on the value of the ServiceType some elements may or may not be applicable. This XML Schema is recursive for ServiceTypes "SSC" and "PSC". </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="ServiceType" type="ns:tServiceType" minOccurs="0"/> <xs:element name="ReferencedContentID" type="ns:tReferencedContentID" minOccurs="0"/> <xs:element name="ServiceState" type="ns:tServiceState" minOccurs="0"/> <xs:element name="ServiceStateInformation" type="xs:string" minOccurs="0"/> <xs:element name="ServiceStateExpireTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="TrickPlayActivated" type="xs:boolean" minOccurs="0"/> <xs:element name="SSCRoomID" type="xs:string" minOccurs="0"/> <xs:element name="PSCid" type="xs:string" minOccurs="0"/> <xs:element name="IPTVServiceState" type="ns:tIPTVServiceState" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tServiceState"> <xs:simpleContent> <xs:extension base="ns:tServiceStateEnumeration"> <xs:attribute name="extension" type="xs:string"/> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:simpleType name="tServiceStateEnumeration"> <xs:restriction base="xs:string"> <xs:enumeration value="Play"/> <xs:enumeration value="Pause"/> <xs:enumeration value="Recording"/> <xs:enumeration value="Fast-forward"/> <xs:enumeration value="Rewinding"/> <xs:enumeration value="Picture-in-picture"/> <xs:enumeration value="Extension"/> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 166 </xs:restriction> </xs:simpleType> </xs:schema> NOTE: Here are two examples of tServiceState. <tServiceState>Play</tServiceState> <tServiceState extension="Skipping">Extension</tServiceState> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 167 Annex F (informative): Example of presence information update after channel-change UE Core-IMS PS 3. IFC 1. IGMP join 2. PUBLISH 6. 200 (OK) 4. PUBLISH 5. 200 OK Tcc Figure F.1 1) IGMP Join request (UE to Core-IMS): The User wishes to change watching channel. The UE sends an IGMP join request to the multicast group corresponding to the selected channel. The timer Tcc is started. 2) PUBLISH request (UE to Core-IMS): After Tcc timer expiration, to initiate the publication, the UE generates a PUBLISH request according to ES 283 030 [21]. The UE indicates the new watched channel in the present document. 3) IFC: The S-CSCF routes the request to the Presence Server according to the IFC. 4) PUBLISH request (Core-IMS to Presence Server): The Core-IMS forwards the PUBLISH request to the presence server thanks to the configured IFC. For example, for user1_public1@home1.net the Core-IMS has originating initial Filter Criteria with Service Point Trigger of Method = PUBLISH AND Event = "presence" AND Request-URI = "sip:user1_public1@home1.net" that informs the S-CSCF to route the PUBLISH request to the PS ps.home1.net. 5) 200 (OK) response (PS to Core-IMS): The Presence Server evaluates the PUBLISH request and update presence information (i.e. currently watched channel). It replies with a SIP 200 OK to the Core IMS. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 168 6) 200 (OK) response (Core-IMS to UE): The Core-IMS forwards the SIP 200 OK to the UE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 169 Annex G (informative): Example of presence document extension The following example describes the particular case of a BC service: <tuple id="serv11"> <status> <basic>open</basic> </status> <oma:service-description> <oma:service-id>IPTV-BC</oma:service-id> <oma:version>x.y</oma:version> <oma:description>IPTV BroadCast service</oma:description> </oma:service-description> <caps:servcaps> <caps:audio>true</caps:audio> <caps:video>true</caps:video> </caps:servcaps> <BC> <currentBCServiceID>tv:BBC1.co.uk</currentBCServiceID> <currentBCProgramID>cid:the_weakest_link@bbc1.co.uk</currentBCProgramID> </BC> <rpid:class>IPTV</rpid:class> <dm:deviceID>mac:8asd7d7d70</dm:deviceID> <note>comment1</note> </tuple> The following example describes the particular case of a BC service access history item: <tuple id="serv18"> <status> <basic>open</basic> </status> <oma:service-description> <oma:service-id>IPTV-SAH</oma:service-id> <oma:version>x.y</oma:version> <oma:description>IPTV service access history</oma:description> </oma:service-description> <caps:servcaps> <caps:audio>true</caps:audio> <caps:video>true</caps:video> </caps:servcaps> <SAH> <ServiceType>BC</ServiceType> <ReferencedContentID>tv:BBC1.co.uk</ReferencedContentID> <Rating>2</Rating> <AccessStartTime>2009-08-06T20:08:00</AccessStartTime> <AccessEndTime>2009-08-06T20:40:25</AccessEndTime> <HistoryExpireTime>PT24H</HistoryExpireTime> </SAH> <rpid:class>IPTV</rpid:class> <dm:deviceID>mac:8asd7d7d70</dm:deviceID> <note>comment1</note> </tuple> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 170 Annex H (informative): Summary of standards and protocols for IMS based IPTV This informative annex provides summary of standards and protocols version (specification compliance) required by IMS based IPTV in mentioned reference points. NOTE: In case of any inconsistencies with the normative text, the normative text applies. H.1 SIP/SDP protocol Usage the SIP/SDP protocol across the following reference points is described in clause 5: - reference point Gm; - reference point ISC; - reference point y2. Following functional entities are SIP/SDP capable: - UE, SCF, SDP, MCF, Core IMS. Following SIP protocol model explain which SIP request method are used for particular procedure. Figure H.1: IMS based IPTV - SIP protocol model A. UE send REGISTER to Core IMS and SDF. B. Service discovery Push mode - SDF send message MESSAGE with discovery information. C. Service discovery Pull mode - UE used SUBSCRIBE to SDF over Core IMS, SDF send NOTIFY with service discovery information (also when changed). D. Service initiation, modification and teardown from UE via Core IMS to SCF (INVITE, re-INVITE or UPDATE, BYE). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 171 E. UE sends a SIP MESSAGE request to SCF requiring NPVR service (SCF send MESSAGE to MCF). F. Optional - procedures for join multicast group (clause 8.1.1) the UE may inform SCF of the selected channel (sending INFO message). G. INFO message to send COD Service action data information to SCF. H. Service Attachment - PULL mode is used SUBSCRIBE and NOTIFY methods. I. Optional - Presence used for channel watching information. H.1.1 Protocol specifications used for SIP/SDP This clause contains list of protocol specifications required for IMS based IPTV implementation used as references in clause 5 or other related to SIP/SDP specifications. This clause contains also summary of methods required for implementation as mandatory and also optional. Several Core IMS procedures are explicitly used by IMS based IPTV (not limited) like IMS registration, session initiation, modification and termination. SIP methods like REGISTER, INVITE, UPDATE, PUBLISH, NOTIFY, MESSAGE, SUBSCRIBE are used in IMS based IPTV. The following tables explain relation of used specification for specified function entity towards other entities. Last column summarizes requirements for implementation for specified functional entity (which specification are required for implementation). Table H.1: SIP/SDP protocol related specification for UE Specifications for: UE IMS core SDF SCF MCF Summary of required implementation Ref. point Gm <-> Via IMS core <-> Via IMS core <-> --- UE REGISTER [20] (M) (M) 3rd party (M) INVITE, re-INVITE or UPDATE, BYE [20] (M) (M) (M) MESSAGE [23] and [20] MESSAGE is used only by "Push mode" service discovery and "N- PVR" service (M) (M) PUBLISH [21] for IPTV presence (optional) (O) (O) SUBSCRIBE [20] Pull mode (M) clause 5.1.2A.1 (M) NOTIFY [25] In pull mode (M) (M) SIP INFO [20] (O) (O) Annex Y in pull mode (M) (M) OMA-TS-Presence-SIMPLE-V1 [23] (O) (O) RFC 5875 [26] (O) (O) RFC 5874 [15] (O) (O) ETSI ETSI TS 183 063 V3.6.1 (2014-08) 172 Table H.2: SIP/SDP protocol related specification for Core IMS Specification: IMS core UE SDF SCF MCF Summary of required implementation Ref. point Gm <-> ISC <-> ISC <-> y2 <-> IMS core ES 283 003 [20] (M) (M) ISC (M) ISC (M) Core IMS entities REGISTER, INVITE [20] (M) (M) (M) NOTIFY [25] [29] Pull mode (M) (M) (M) NOTE: Table mentions just SIP methods explicitly used in IMS based IPTV procedures but does not exclude any other usage of other methods. Table H.3: SIP/SDP protocol related specification for SDF Specification: SDF UE IMS core SCF MCF Summary of required implementation Ref. point Push mode -> Pull mode <-> Via IMS core ISC <-> --- --- SDF REGISTER [20] third-party registration Push mode [20] (M) (M) Pull mode NOTIFY [29] (M) clause 5.7.1.4 (M) clause 5.7.1.4 Pull mode user's identity verification [29] (M) (M) Table H.4: SIP/SDP protocol related specification for SCF Specification: SCF UE IMS core SDF MCF Summary of required implementation Ref. point Ut <-> ISC <-> Via IMS core Via IMS core SCF ES 283 003 [20] SCF act as an AS acting as a terminating UA for BC service or SCF act as an AS acting as an originating UA for BC service SCF act as a B2BUA when N- PVR service is used (SIP dialog is established UA<=>SCF and SCF<=> MCF) SCF is a proxy or a B2BUA when CoD service is used INVITE, re-INVITE or UPDATE, BYE [20] (M) (M) (M) Via IMS core Table H.5: SIP/SDP protocol related specification for MCF Specification: MCF UE IMS core SDF SCF Summary of required implementation Ref. point y2 <-> Via IMS core MCF ES 283 003 [20] (M) (M) MCF act as a generic terminating UA (M) REDIRECT SIP [2] BC with Trick play (M) (M) (O) clause 5.1.3.3 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 173 H.2 HTTP protocol Usage of the HTTP protocol across the following interfaces is described in clause 6: - interface Xa; - interface Ut. HTTP capable functional entities: - UE, SCF, SSF. Table H.6: Summary of specifications compliancy for HTTP capable FEs Specification: UE SSF SCF RFC 4825 [9] XCAP client (M) NA XCAP sever (M) HTTP PUT, HTTP GET or HTTP DELETE RFC 5246 [32] (M) (M) (M) TS 187 003 [10] (M) (M) NA TS 124 109 [11] NA (O) (O) TS 183 023 [12] NA (O) (O) TS 102 034 [3] clause 5.4.2.2 (M) clause 5.2.6 (M) NA TS 102 539 [13] clauses 4.1.2.2.2 and 4.2 (M) clauses 4.1.2 and 4.2 (M) NA TS 133 222 [14] (O) (O) NA RFC5874 [15] (O) NA (O) OMA OMA-TS- BCAST_Service_Guide- V1_0 [6] clause 5.4.3 (M) clause 5.4.3.3 (M) NA NOTE: (M) - Mandatory. (O) - Optional. NA - NOT Applicable. H.3 RTSP/SDP protocol Usage of the RTSP/SDP protocol across the following interfaces is described in clause 7: - interface Di, Dj, Ds or lz. RTSP/SDP capable functional entities: - UE, MCF. H.3.1 Protocol specifications used for RTSP/SDP This clause contains a summary of RTSP methods required for implementation in IMS based IPTV as mandatory or optional (as references to clause 7 or other related to RTSP). Table H.7 shows the differences by using RTSP method in comparison with RFC 2326 [8]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 174 Table H.7 RTSP Method Direction: C = client - UE; S = Server - MCF; RFC 2326 [8] DVB Requirement TS 102 034 [3] TISPAN IMS based IPTV LMB MBwTM and CoD Method 1 Method 2 ANNOUNCE C→S MAY MAY MAY N.A. N.A. ANNOUNCE S→C MAY SHOULD SHOULD (M) (M) DESCRIBE C→S SHOULD SHOULD SHOULD N.A. (M) GET_PARAMETER C→S MAY SHOULD SHOULD (M) N.A. GET_PARAMETER S→C MAY MAY MAY N.A. N.A. OPTIONS C→S SHALL SHALL SHALL (M) N.A. OPTIONS S→C MAY MAY MAY N.A. N.A. PAUSE C→S SHOULD N.A. SHALL (M) (M) PLAY C→S SHALL SHALL SHALL (M) (M) REDIRECT S→C MAY SHALL SHALL N.A. N.A. SETUP C→S SHALL SHALL SHALL N.A. (M) TEARDOWN C→S SHALL SHALL SHALL N.A. (M) SET_PARAMETER C→S MAY N.A. N.A. (M) N.A. SET_PARAMETER S→C MAY N.A. N.A. N.A. N.A. RECORD C→S MAY N.A. N.A. N.A. N.A. NOTE: (M) = Mandatory. (O) = Optional. N.A. = Not Applied. The text in bold shows differences compared to RFC 2326 [8] table 2. H.4 UDP/RTP/RTCP protocol Usage of the UDP/RTP/RTCP protocol across the following interfaces is described in clause 11: - interface Xd; - interface Di, Dj, Ds or Iz. UDP/RTP/RFTCP capable functional entities: - UE, MDF, MSAS, SC, SC'. H.5 IGMP/MLD protocol Usage of the IGMP/MLD protocol across the following interfaces is described in clause 8: - interface Dj, Di, Ds, or Iz. IGMP/MLD capable functional entities: - UE, Transporting functions (ECF/EFF), MDF. If IPv4 is used for the transport, the UE conforms to RFC 3376 [28] (IGMPv3). If IPv6 is used for the transport, the UE conforms to RFC 3810 [29] (MLDv2). Backward compatibility rules between the UE and the Transport Function have to be done conforming to RFC 3376 [28], clause 7 and RFC 3810 [29], clause 8. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 175 UE need to support at least: - IGMP v3 unsolicited Membership Report or a MLDv2 Multicast Listener Report Message. - IGMP v3 Membership Report Message or MLD v2 Multicast Listener Report Message. H.6 Diameter protocol Use of Diameter complies to the following specifications: - TS 183 017 [i.2] in case of the Gq' interface. - ES 283 035 [36] in case of the e2 interface. - TS 183 033 [i.3] in case of the Cx and Dx' interfaces. - TS 129 329 [i.4] in case of the Sh and Dh interfaces. Diameter capable functional entities: - CoreIMS, SCF, SDF. H.7 DVBSTP protocol Usage of the DVBSTP protocol across the following interface is described in clause 9: - interface Xa. DVBSTP capable functional entities (Optionally): - UE, SSF. H.8 FLUTE protocol Usage of the FLUTE protocol across the following interface is described in clause 10: - interface Xa. FLUTE capable functional entities (Optionally): - UE, SSF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 176 Annex I (normative): Procedures for discovery of SDFs prior to service attachment This annex describes a set of alternatives for the UE to identify the SDFs and/or the service provider domain information associated with them prior to service attachment procedures. The order in which these alternatives are executed or priority between the alternatives when executed simultaneously is outside of the scope of the present document. I.1 Manual configuration based manual discovery The UE may be manually configured with the one or more instances of the following information. • The Service Provider Name: This provides the name of the Service Provider to connect to first. It is of variable length. • ServiceProviderDomainName: This provides the domain name corresponding to Service provider. It is of variable length. • ServiceDiscoveryServer: This specifies the address of the SDF associated with the SP and it is specified as an IMS Public Service Identifier or IP address or URL. • The IMS PSI value shall be specified for IMS-based Service Discovery Function. • The IPAddress or URL may be specified for non-SIP-AS based Service Discovery Function. I.2 DHCP-based discovery In addition to acquiring its IP address from the DHCP server, in this mechanism the UE can acquire information on SDFs and associated Service Provider(s) information using appropriate vendor class identifier DHCP options. I.2.1 Using DHCP option 43/60 The client may send a Vendor class Identifier DHCP option 60 as specified in ES 283 003 [20] when it requests a DHCP lease for server. The option is specified with the vendor-class identifier as "ETSI_TISPAN_IPTV_SDS". The DHCP server delivers the SDF information via Vendor-Specific Information DHCP option 43 packed in a binary buffer as defined in ES 283 003 [20]. The format of the binary buffer containing the SDF information is specified in clause I.2.3. I.2.2 Using DHCP option 124/125 This vendor identifier specific DHCP option is recommended to be used when there is a need to support DHCP options from multiple vendors as specified in RFC 3925 [17]. The client may send a Vendor -Identifying Vendor Class option 124 as specified in RFC 3925 [17] when it requests a DHCP lease for server. The option is specified with an enterprise-number of 13019 (ETSI) and the vendor-class-data identifier as "ETSI_TISPAN_IPTV_SDS". The DHCP server delivers the SDF information via Vendor-Identifying Vendor-Specific Information DHCP option 125 packed in a binary buffer as defined in RFC 3925 [17]. The enterprise-number shall be set as 13109 (ETSI). The format of the binary buffer containing the SDF information is specified in clause I.2.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 177 I.2.3 Format of DHCP payload The format of the vendor-specific binary buffer containing SDF addresses returned by the DHCP server is as follows. It is a list of sub-options starting with sub-option number (one byte), its length (one byte) and its value (list of bytes). The following vendor-specific sub-options are defined: • Sub-Option: IMS_IPTV_SP: Code = 0x01. This option provides the name of the Service Provider to connect to first. It is of variable length and it is Optional. • Sub-Option: IMS-IPTV-SPDOMAIN: Code= 0x02. This option provides the domain name corresponding to Service provider. It is of variable length and it is Optional. • Sub-Option: IMS-IPTV-SDF: Code=0x03. This option carries either the (1) IMS PSI value, (2) the IPAddress of SDF or (3) the fully-qualified domain name of the Service Discovery Server associated with the Service Provider. This is Mandatory. • A one byte "enc" field is used to indicate the type of encoding. - If the "enc" field has a value of _0x00, then this indicates an IMS PSI value. The "enc" field is followed by the bytes corresponding to the IMS PSI. This value shall be used for IMS-based service discovery function. - If the "enc" field has a value of _0x01, then this indicates an IP Address. The "enc" field is followed by 4 bytes corresponding to the IPAddress. This value may be used for non-SIP AS service discovery function. - If the "enc" field has a value of 0x02, then this indicates a DNS hostname. The "enc" field is followed by a sequence of labels, encoded according to clause 3.1 of RFC 1035 [18]. This value may be used for non-SIP AS service discovery function. • The code of 0xFF is used to indicate end of the buffer. The availability of the service provider SDF information at the Network Provider DHCP server is subject to business policies between the service provider and network provider. I.3 DNS Service Records (SRV) - based discovery In this case, the SD servers are discovered using the DNS SRV mechanism in accordance with RFC 2782 [31], with the following input parameters: • Service: Defined as "tispan-iptv-service". This is the symbolic name of the desired service; to be defined and registered with IANA. • Protocol: Can take values "http" or "sip". Specifies the protocol to contain the particular service. • Domain name: the domain for which the returned records are valid; the value can be derived from the following: - Domain from manual configuration. - Domain from network attachment phase (DHCP server). - Domain from IMS home domain. The output of the DNS SRV lookup is an ordered list of domain name, each pointing to a SDF server available within the specified Domain name. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 178 I.4 TR-069 based discovery In this case, the UE discovers the addresses of the SDFs and associated Service Provider information during remote configuration procedures using the TR-069 [37] protocol. Specifically, upon successful UE network attachment and successful creation of a management session with the remote configuration server, the CNGCF may provide the UE with a listing of IPTV service providers and associated SDF servers that it knows about. How the remote configuration server at the CNGCF is provided with this information is beyond the scope of the present document. An ordered listing of one or more instances of the following elements may be delivered: • The Service Provider Name: This provides the name of the Service Provider to connect to first. It is of variable length. • ServiceProviderDomainName: This provides the domain name corresponding to Service provider. It is of variable length. • ServiceDiscoveryServer: This specifies the address of the SDF associated with the SP and it is specified as an IMS Public Service Identifier or IP address or URL: - The IMS PSI value shall be specified for IMS-based Service Discovery Function. - The IPAddress or URL may be specified for non-SIP-AS based Service Discovery Function. NOTE: The exact object extension used to carry the above information during remote configuration is beyond scope of the present document. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 179 Annex J (informative): Integration of non SIP AS service discovery function J.1 Integration of non SIP AS service discovery Function based on DVB IPTV J.1.1 User Equipment (UE) J.1.1.1 Procedure for service attachment In order to discover the list of SDF, the UE will follow the entry points discovery steps as defined in TS 102 034 [3], clause 5.2.4. The UE will use HTTP or DVBSTP protocols in order to retrieve the service provider discovery information, conforming to TS 102 034 [3], clause 5.4. NOTE: It is also possible that the UE holds a hard-coded parameter containing the entry point information, or that an out-of-band mechanism exists for the UE to retrieve this information. J.1.1.2 Procedure for service selection J.1.1.2.1 Request of DVB SD&S The UE will use HTTP or DVBSTP protocols in order to retrieve the SD&S information, conforming to TS 102 034 [3], clause 5.4. J.1.1.2.2 Request of DVB BCG The UE will use HTTP, DVBSTP or HTTP/SOAP protocols in order to retrieve the BCG information, conforming to TS 102 539 [13], clause 4. J.1.2 Service Discovery Function (SDF) J.1.2.1 Procedure for service attachment The SDF will provide to the UE the service provider discovery information conforming to TS 102 034 [3], clause 5.2.5. The SDF will use HTTP and DVBSTP protocols, conforming to TS 102 034 [3], clause 5.4. J.1.3 Service Selection Function (SSF) J.1.3.1 Procedure for service selection J.1.3.1.1 Delivery of DVB SD&S The SSF will provide to the UE the SD&S information conforming to TS 102 034 [3], clause 5.2.6. The SSF will use HTTP and DVBSTP protocols, conforming to TS 102 034 [3], clause 5.4. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 180 J.1.3.1.2 Delivery of DVB BCG The SSF will provide to the UE the BCG information conforming to TS 102 539 [13]. The SSF will use HTTP, DVBSTP, and HTTP/SOAP protocols, conforming to TS 102 539 [13], clause 4. J.2 Integration of non SIP AS service discovery function based on OMA BCAST ESG J.2.1 User Equipment (UE) J.2.1.1 Procedure for service attachment It is assumed that each service provider publishes a single ESG. Thus, an ESG provider is equal to a service provider. For discovering the available service providers the list of SDFs, the UE can follow the ESG bootstrapping method as defined in OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5 or other signalling methods. It is assumed that there is an ESG bootstrap session where service guides are described with ESGProviderDiscovery Descriptors, as specified in clause 9 of TS 102 471 [4]. This also applies to describing OMA BCAST service guides [6]. In the push situation, the ESG bootstrap session will be a FLUTE session as specified in TS 102 471 [4]. In the pull situation, the bootstrap session uses HTTP. NOTE: It is also possible that the UE holds a hard-coded parameter containing the entry point information, or that an out-of-band mechanism exists for the UE to retrieve this information. J.2.1.2 Procedure for service selection J.2.1.2.1 Request of ESG provider discovery information The UE uses the FLUTE protocol in order to retrieve the ESGProviderDiscovery Descriptor information, conforming to TS 102 471 [4], clause 9.2 and OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5 or it uses the HTTP protocol. J.2.1.2.2 Request of OMA BCAST ESG The UE uses HTTP or FLUTE protocols in order to retrieve the ESG information, conforming to TS 102 471 [4], clause 8.1, OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5 and OMA-TS-BCAST_Service_Guide-V1 [6], clause 5.4. J.2.2 Service Discovery Function (SDF) J.2.2.1 Procedure for service attachment The SDF will provide to the UE the service provider discovery information in the form of ESGProviderDiscovery Descriptors, conforming to TS 102 471 [4], clause 9.1.1. For providing the UE with this information, the SDF will use HTTP and FLUTE protocols, conforming to TS 102 471 [4], clause 9.2, OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5 and OMA-TS-BCAST_Service_Guide-V1 [6], clause 5.4. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 181 J.2.3 Service Selection Function (SSF) J.2.3.1 Procedure for service selection J.2.3.1.1 Delivery of ESG provider discovery information The SSF will provide to the UE the ESGProviderDiscovery Descriptor conforming to TS 102 471 [4], clause 9.1.1. The SSF use thes FLUTE protocol, conforming to TS 102 471 [4], clause 9.2 and OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5. or it uses the HTTP protocol. J.2.3.1.2 Delivery of OMA BCAST ESG The SSF will provide to the UE the ESG information conforming to OMA-TS-BCAST_Service_Guide-V1_, clause 5.4. The SSF will use HTTP or FLUTE protocols, conforming to TS 102 471 [4], clause 8.1, OMA-TS-BCAST_DVB_Adaptation-V1_0 [7], clause 6.3.5 and OMA-TS-BCAST_Service_Guide-V1 [6], clause 5.4. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 182 Annex K (normative): XML Schemas for the IPTV service action data This annex specifies XML schemas for creating documents representing instances of the IPTV service action data. XML Schema for BC service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvbcserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvbcserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVBcActionData"> <xs:complexType> <xs:sequence> <xs:element name="BCBookmark" type="tBCBookmark" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tBCBookmark"> <xs:sequence> <xs:element name="BCServiceId" type="xs:string" /> <xs:element name="ProgrammeId" type="xs:string" minOccurs="0"/> <xs:element name="Bookmark" type="xs:dateTime" /> <xs:element name="BookmarkExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> XML Schema for CoD service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvcodserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvcodserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVCodActionData"> <xs:complexType> <xs:sequence> <xs:element name="AvailableCoD" type="tAvailableCoD" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tAvailableCoD"> <xs:sequence> <xs:element name="CoDId" type="xs:string"/> <xs:element name="CoDDeliveryStatus" type="tCodDeliveryStatus"/> <xs:element name="CoDOffset" type="xs:string" minOccurs="0"/> <xs:element name="CoDOffsetExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="expectedDuration" type="xs:duration" use="optional"/> </xs:complexType> <xs:simpleType name="tCodDeliveryStatus" final="list"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="4"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">Ordered</label> <definition xml:lang="en">Content has been ordered</definition> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 183 </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> <label xml:lang="en">Ongoing</label> <definition xml:lang="en">Streaming delivery has started</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="2"> <xs:annotation> <xs:documentation> <label xml:lang="en">Failed</label> <definition xml:lang="en">Some error has occurred while delivering the content</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="3"> <xs:annotation> <xs:documentation> <label xml:lang="en">Parked</label> <definition xml:lang="en">The content was parked and will be pickep up later</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="4"> <xs:annotation> <xs:documentation> <label xml:lang="en">Paused</label> <definition xml:lang="en">The content is paused for the amount of time indicated by the expectedDuration attribute</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> XML Schema for N-PVR service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvnpvrserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvnpvrserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVNpvrActionData"> <xs:complexType> <xs:sequence> <xs:element name="NPVRItem" type="tNPVRItem" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tNPVRItem"> <xs:sequence> <xs:element name="NPVRContentId" type="xs:string" minOccurs="0"/> <xs:element name="BCServiceId" type="xs:string" /> <xs:element name="RecordStartDate" type="xs:string" minOccurs="0"/> <xs:element name="RecordEndDate" type="xs:dateTime" minOccurs="0"/> <xs:element name="RecordStatus" type="tRecordStatus" minOccurs="0"/> <xs:element name="PlaybackOffset" type="xs:string" minOccurs="0"/> <xs:element name="PlaybackOffsetExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="NPVRContentExpiryTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tRecordStatus"> <xs:restriction base="xs:unsignedByte"> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 184 <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">Scheduled</label> <definition xml:lang="en">Recording is scheduled</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> <label xml:lang="en">Started</label> <definition xml:lang="en">Recording has started</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="2"> <xs:annotation> <xs:documentation> <label xml:lang="en">Available</label> <definition xml:lang="en">Recording is available</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="3"> <xs:annotation> <xs:documentation> <label xml:lang="en">Failed</label> <definition xml:lang="en">Recording has failed</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> XML Schema for CPVR service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvcpvrserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvcpvrserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVCpvrActionData"> <xs:complexType> <xs:sequence> <xs:element name="CPVRItem" type="tCPVRItem" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tCPVRItem"> <xs:sequence> <xs:element name="CPVRContentId" type="xs:string" minOccurs="0"/> <xs:element name="BCServiceId" type="xs:string" /> <xs:element name="TargetUEId" type="xs:string" /> <xs:element name="RecordStartDate" type="xs:string" minOccurs="0"/> <xs:element name="RecordEndDate" type="xs:dateTime" minOccurs="0"/> <xs:element name="RecordStatus" type="tRecordStatus" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tRecordStatus"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="3"/> <xs:enumeration value="0"> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 185 <xs:annotation> <xs:documentation> <label xml:lang="en">Scheduled</label> <definition xml:lang="en">Recording is scheduled</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> <label xml:lang="en">Started</label> <definition xml:lang="en">Recording has started</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="2"> <xs:annotation> <xs:documentation> <label xml:lang="en">Available</label> <definition xml:lang="en">Recording is available</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="3"> <xs:annotation> <xs:documentation> <label xml:lang="en">Failed</label> <definition xml:lang="en">Recording has failed</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> XML Schema for UGC service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvugcserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvugcserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVUGCActionData"> <xs:complexType> <xs:sequence> <xs:element name="UGCItem" type="tUGCItem" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="message-id" type="xs:string" /> </xs:complexType> </xs:element> <xs:complexType name="tUGCItem"> <xs:sequence> <xs:element name="UGCContentId" type="xs:string" minOccurs="0"/> <xs:element name="UGCCreationTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="UGCGenre" type="xs:string" minOccurs="0"/> <xs:element name="UGCTitle" type="xs:string" minOccurs="0"/> <xs:element name="UGCOriginator" type="xs:string" minOccurs="0"/> <xs:element name="UGCDescription" type="xs:string" minOccurs="0"/> <xs:element name="UGCAuthorizedViewUser" type="xs:string" minOccurs="0"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 186 XML Schema for Content Insertion service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvcontentinsertionserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvcontentinsertionserviceactiondata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVContentInsertionActionData"> <xs:complexType> <xs:sequence> <xs:element name="InsertionData" type="tInsertionData" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tInsertionData"> <xs:sequence> <xs:element name="IPTVContentIdentifier" type="xs:string"/> <xs:element name="InsertedContentIdentifier" type="xs:string" /> <xs:element name="InsertionTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="InsertionStatus" type="tInsertionStatus"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tInsertionStatus"> <xs:restriction base="xs:string"> <xs:enumeration value="Accepted"> <xs:annotation> <xs:documentation> <definition xml:lang="en">Insertion is accepted</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="Rejected"> <xs:annotation> <xs:documentation> <definition xml:lang="en">Insertion is rejected</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="Started"> <xs:annotation> <xs:documentation> <definition xml:lang="en">Insertion has started</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="Finished"> <xs:annotation> <xs:documentation> <definition xml:lang="en">Insertion is finished</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="Failed"> <xs:annotation> <xs:documentation> <definition xml:lang="en">Insertion has failed</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> XML Schema for PCh service related data: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvpchserviceactiondata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvpchserviceactiondata" ETSI ETSI TS 183 063 V3.6.1 (2014-08) 187 xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVPChActionData"> <xs:complexType> <xs:sequence> <xs:element name="PChList" type="tPChList" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="transaction-id" type="xs:string" use="optional"/> </xs:complexType> </xs:element> <xs:complexType name="tPChList"> <xs:sequence> <xs:element name="PChItem" minOccurs="1" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="PChItemServiceType" type="xs:string" /> <xs:element name="PChItemContentId" type="xs:anyURI" /> <xs:element name="PChItemStartTime" type="xs:dateTime" /> <xs:element name="PChItemEndTime" type="xs:dateTime" /> <xs:element name="PChItemOffset" type="xs:duration" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="PChId" type="xs:anyURI" use="required"/> </xs:complexType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 188 Annex L (normative): Mapping of IPTV parameters to service selection L.1 Mapping of service attachment This clause presents how several IPTV technologies are mapped into TISPAN metadata (XML schema as specified in annex M) concerning the discovery of SSF entities. In the current release DVB and OMABCAST technologies mapping are described. Within the XML schema, some fields are specific to TISPAN, they are marked as "TISPAN defined field" in the following tables. L.1.1 Mapping of DVB SD&S SP discovery records to XML schema for service attachment This clause describes the mapping of DVB SD&S Service Provider discovery record to the generic XML schema for service attachment defined in annex M and clause 5.2.2.3. TISPAN Element Name (copied from clause 5.2.2.3) Corresponding DVB SD&S element in TS 102 034 [3], clause 5.2.5, table 2 (TS 102 034 [3] XML Schema clause reference) SSF @ID TISPAN defined field @Technology when a DVB SSF is advertised, this field shall be "dvb.org_iptv" @Version TISPAN defined field Description TISPAN defined field ServiceProvider ServiceProvider (Clause C.1.4.6) @DomainName ServiceProvider@DomainName (Clause C.1.4.6) @LogoURI ServiceProvider@LogoURI (Clause C.1.4.6) Name ServiceProvider.Name (Clause C.1.4.6) Description ServiceProvider.Description (Clause C.1.4.6) Pull OfferingListType.Pull (Clause C.1.3.15) @Location Pull@Location (Clause C.1.3.15) DataType PayloadId There is a direct mapping between the DVB PayloadId values and this field. (Clause C.1.3.19) @Type PayloadId@Id refer to table 1 in TS 102 034 [3] and to table 2 in TS 102 539 [13] TS 102 034 [3] defines the values 0x00 to 0x06, TS 102 539 [13] defines the values 0xA1 to 0xA7. The present document defines an additional value 0xA0: when using 0xA0, it means that the Pull@Location URL refers to an SSF that is a DVB-BCG server using the SOAP protocol, instead of the pull HTTP delivery. When 0xA0 is used, no Segment element shall be exposed. (Clause C.1.3.19) Segment PayloadId.Segment (Clause C.1.3.19) This parameter is mandatory for DVB Pull mode @ID PayloadId.Segment@Id (Clause C.1.3.19) ETSI ETSI TS 183 063 V3.6.1 (2014-08) 189 TISPAN Element Name (copied from clause 5.2.2.3) Corresponding DVB SD&S element in TS 102 034 [3], clause 5.2.5, table 2 (TS 102 034 [3] XML Schema clause reference) @Version PayloadId.Segment@Version (Clause C.1.3.19) Push OfferingListType.Push (Clause C.1.3.15, C.1.3.4) @IPVersion @MulticastAddress @Address (Clause C.1.3.11) @MulticastPort @Port (Clause C.1.3.11) @SourceAddress @Source (C.1.3.11) DataType PayloadId (refer to table 1 in TS 102 034 [3] and to table 2 in TS 102 539 [13]) (Clause C.1.3.19) @Type PayloadId@Id There is a direct mapping between the DVB PayloadId values and this field (Clause C.1.3.19) Segment PayloadId.Segment (C.1.3.19) This parameter is optional for DVB Push mode @ID PayloadId.Segment@Id (Clause C.1.3.19) @Version PayloadId.Segment@Version (Clause C.1.3.19) L.1.2 Mapping of OMA BCAST ESG delivery descriptors to XML schema for service attachment This clause describes the mapping of OMA BCAST ESG delivery descriptors to the generic XML schema for service attachment defined in annex M and clause 5.2.2.3. The mandatory/optional nature of the fields can be derived from there. TISPAN Element Name (copied from clause 5.2.2.3) Corresponding OMA BCAST ESG element in OMA-TS- BCAST_Service_Guide-V1_0 [6], clause 5.4 and TS 102 471 [4], clause 9.1 SSF @ID TISPAN defined field @Technology When an OMA BCAST SSF is advertised, this field shall be "openmobilealliance.org_bcast" @Version TISPAN defined field Description TISPAN defined field ServiceProvider @DomainName ProviderURI (TS 102 471 [4], clause 9.1.1) @LogoURI ProviderLogo ([7], clause 9.1.1) Name ProviderName (TS 102 471 [4], clause 9.1.1) Description Pull @Location This URI encodes the location of the Service Guide Delivery Descriptors and/or the Service Guide Delivery Units ([6], clause 5.4) DataType Specifies the type of Service Guide data fragment. ([6], clause 5.4) ETSI ETSI TS 183 063 V3.6.1 (2014-08) 190 TISPAN Element Name (copied from clause 5.2.2.3) Corresponding OMA BCAST ESG element in OMA-TS- BCAST_Service_Guide-V1_0 [6], clause 5.4 and TS 102 471 [4], clause 9.1 @Type Options are "sgdd", "sgdu" and "sgdd+sgdu". The value is used to populate the body of the HTTP request ([6], clause 5.4.3.1) Segment Service Guide Delivery Descriptor or Service Guide fragment. ([6], clause 5.4.1) This parameter is mandatory for OMABCAST Pull mode @ID Service Guide Delivery Descriptor or Service Guide fragment identifier. Can be mapped to "id", "fragmentID" or "fragmentTransportID". Format is anyURI ([6], clause 5.4.1.1) @Version Version of the Service Guide Delivery Descriptor or Service Guide fragment identifier. Can be mapped to "version" or "fragmentVersion". Format is unsignedInt ([6], clauses 5.4.1.3 and 5.4.1.5.2) Push @IPVersion IPVersion6, format is bit string. This is a binary flag, which, if set to "1", indicates IPv6 usage (TS 102 471 [4], clause 9.1.2) @MulticastAddress Specifies the IP address of the FLUTE session transporting the ESG (TS 102 471 [4], clause 9.1.2) @MulticastPort Specifies the port number of the IP stream of the FLUTE session transporting the ESG (TS 102 471 [4], clause 9.1.2) @SourceAddress Specifies the source IP address of the FLUTE session transporting the ESG (TS 102 471 [4], clause 9.1.2) DataType Specifies the type of Service Guide data fragment (TS 102 471 [4], clause 5.4) @Type Options are "application/vnd.oma.bcast.sgdd+xml" and "application/vnd.oma.bcast.sgdu" ([6], clause 5.4.2) Segment Service Guide Delivery Descriptor or Service Guide fragment (TS 102 471 [4], clause 5.4.1) This parameter is mandatory for OMABCAST Push mode @ID Service Guide Delivery Descriptor or Service Guide fragment identifier. Can be mapped to "id", "fragmentID" or "fragmentTransportID". Format is anyURI ([6], clause 5.4.1.1) @Version Version of the Service Guide Delivery Descriptor or Service Guide fragment identifier. Can be mapped to "version" or "fragmentVersion". Format is unsignedInt ([6], clauses 5.4.1.3 and 5.4.1.5.2) L.1.3 Mapping of service action data record discovery records to XML schema for service attachment This clause describes the mapping of Service Action Data record to the generic XML schema for service attachment defined in annex M and clause 5.2.2.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 191 TISPAN Element Name (copied from clause 5.2.2.3) Corresponding Service Action Data field SSF @ID TISPAN defined field @Technology when a Service Action Data record is advertised, this field shall be "tispan.org_sad" @Version TISPAN defined field Description TISPAN defined field ServiceProvider Service Provider information @DomainName An internet DNS domain name registered by the Service Provider that uniquely identifies the Service Provider @LogoURI Pointer to a Service Provider logo for potential display Name Name of the Service Provider for display in one or more languages; one Service Provider name is allowed per language code, and at least one language shall be provided Description Description of the Service Provider for potential display in one or more languages; one description is allowed per language code Pull @Location Location of the Service Action data Record DataType Type of Service Action Data (BC bookmark, N-PVR, CoD) @Type 0x00 defines All service action data 0x01 defines BC service action data 0x02 defines CoD service action data 0x03 defines N-PVR service action data Segment Not applicable @ID Not applicable @Version Not applicable Push Not applicable @IPVersion @MulticastAddress Not applicable @MulticastPort Not applicable @SourceAddress Not applicable DataType Not applicable @Type Not applicable Segment Not applicable @ID Not applicable @Version Not applicable L.2 Mapping of BC service L.2.1 Mapping of BC service for DVB technology Table L.1: Mapping of SIP parameters for BC service IPTV SIP parameters DVB Request-URI Not retrieved from SSF ETSI ETSI TS 183 063 V3.6.1 (2014-08) 192 Table L.2: Mapping of SDP parameters for BC service IPTV SDP parameters for each media stream Corresponding DVB SD&S element in TS 102 034 [3], clause 5.2.6.2 tables 4, 5 and 8 (TS 102 034 [3] XML Schema clause reference) BC content stream Connection Data c=<network type> <address type> <connection address> <network type> Not retrieved from SSF <address type> Not retrieved form SSF <connection address> IPMulticastAddress@Address (Clauses C.1.3.10 and C.1.3.11) Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> "video", not retrieved from SSF <port> IPMulticastAddress@Port (Clauses C.1.3.10 and C.1.3.11) <transport> "RTP/AVP" if IPMulticastAddress@Streaming="rtp" or if IPMulticastAddress@Streaming is not present "UDP/H2221/MP2T" or "UDP/RAW/RAW" if IPMulticastAddress@Streaming="udp" (Clauses C.1.3.10 and C.1.3.11) <fmt> "33", not retrieved from SSF Bandwidth b=AS:<bandwidth> MaxBitrate (Clause C.1.3.8) BCServiceId TextualIdentifier@ServiceName ":"TextualIdentifier@DomainName (Clause C.1.3.24) Note that the TextualIdentifier@DomainName is an optional attribute; therefore if it's not present, the field is copied from the OfferingBase@DomainName (Clause C.1.3.14) BCPackageId Package@Id (Clause C.1.3.16) FEC stream Note that the multicast address and source address of the FEC stream can be the same as the BC content stream Media Announcements for FEC delivery m=<media> <port> <transport> <fmt list> see note <media> "application", not retrieved from SSF <port> IPMulticastAddress.FECBaseLayer@Port (Clauses C.1.3.10 and C.1.3.6) <transport> RTP/AVP <fmt> Dynamic payload type a=rtpmap:<fmt> <encoding_name/clock_rate> <encoding_name/clock_rate> referring to the DVB-IP AL-FEC Base layer and is equal to: "vnd.dvb.iptv.alfec-base/90000" Connection Data at media level c=<network type> <address type> <connection address> <network type> Not retrieved from SSF <address type> Not retrieved from SSF <connection address> IPMulticastAddress.FECBaseLayer@Address (Clauses C.1.3.10 and C.1.3.6) NOTE: The FEC delivery can only be associated to a RTP delivered content. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 193 Table L.3: Mapping of IGMP parameters for BC service IPTV IGMP parameters Corresponding DVB SD&S element in TS 102 034 [3], clause 5.2.6.2, tables 4 and 5 (TS 102 034 [3] XML Schema clause reference) BC content stream <Multicast Address> IPMulticastAddress@Address (Clauses C.1.3.10 and C.1.3.11) <Source Address> IPMulticastAddress@Source (Clauses C.1.3.10 and C.1.3.11) FEC stream Note that the multicast address and source address of the FEC stream can be the same as the Live content stream <Multicast Address> If the FEC multicast address is not the same as the live stream address: IPMulticastAddress.FECBaseLayer@Address (Clauses C.1.3.10 and C.1.3.6) <Source Address> If the source address is not the same as the live stream: IPMulticastAddress.FECBaseLayer@Source (Clauses C.1.3.10 and C.1.3.6) L.2.2 Mapping of BC service for OMA BCAST technology Clause L.2.2 describes the mapping of OMA BCAST ESG delivery descriptors to the TISPAN XML schema for service attachment. This mapping procedure allows for retrieving OMA BCAST ESG fragments from an SSF. The various types of ESG fragments and the relation between them is described in clause 5.1.1 of OMA-TS-BCAST_ServiceGuide-V1_0 [6] and shown in figure 1 of that clause. An ESG has separate fragments to describe the service (e.g. TV channel) and to describe the access to that service. From a Service fragment (clause 5.1.2.1 in [6]) a unique identifier can be obtained to map to the BCServiceID. The Access fragment can either contain or refer to an Session Description, which can take the form of an SDP. Thus, from an OMA BCAST SSF a UE can obtain TV channel identification, description and access information, where the latter is in the form of an SDP. Table L.4: Mapping of SIP parameters for BC service IPTV SIP parameters OMA BCAST Request-URI Not retrieved from SSF Table L.5: Mapping of SDP parameters for BC service IPTV SDP parameters for each media stream Corresponding OMA BCAST element in OMA-TS- BCAST_ServiceGuide-V1_0 [6] Connection Data c=<network type> <address type> <connection address> <network type> SDP <address type> SDP <connection address> SDP Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> SDP <port> SDP <transport> SDP <fmt list> SDP Bandwidth b=AS:<bandwidth> SDP BCServiceId globalServiceID BCPackageId globalPurchaseItemID ETSI ETSI TS 183 063 V3.6.1 (2014-08) 194 Table L.6: Mapping of IGMP parameters for BC service IPTV IGMP parameters OMA BCAST <Multicast Address> SDP <Source Address> SDP L.2.2A Mapping of BC service for TV-Anytime Phase 2 technology Clause L.2.2A describes the mapping of TV-Anytime Phase 2 elements to the TISPAN XML schema for service attachment. This mapping procedure allows for using TV-Anytime Phase 2 information in TISPAN IMS based IPTV procedures. Table L.7A: Mapping of SDP parameters for BC service IPTV SDP parameters for each media stream Corresponding TV-Anytime Phase 2 element in TS 102 822-3-1 [33], TS 102 822-4 [35], and TS 102 822-3-3[55] Connection Data c=<network type> <address type> <connection address> <network type> ContentReferencingTable @ Result@ LocationsResult@ Locator <address type> ContentReferencingTable @ Result@ LocationsResult@ Locator <connection address> ContentReferencingTable @ Result@ LocationsResult@ Locator Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> ProgramInformationTable@ProgramInformation@AVAttributes <port> ContentReferencingTable @ Result@ LocationsResult@ Locator <transport> ContentReferencingTable @ Result@ LocationsResult@ Locator <fmt list> ProgramInformationTable@ProgramInformation@AVAttributes Bandwidth b=AS:<bandwidth> ProgramInformationTable@ProgramInformation@AVAttributes@Bitrate BCProgramId ProgramInformationTable@ProgramInformation@programId BCServiceId ServiceInformationTable@ServiceInformation@serviceId BCPackageId PackageTable@Package@crid Table L.7B: Mapping of IGMP parameters for BC service IPTV IGMP parameters TV-Anytime Phase 2 <Multicast Address> SDP <Source Address> SDP L.2.3 Use of the TV URI in the mapping of BC service for DVB technology and OMA BCAST technology TS 184 009 [16] specifies the TV URI as globally unique identifier to identify broadcast television channels. The TV URI is used in the mapping of BC service for DVB technology and OMA BCAST technology as follows. L.2.3.1 DVB technology If DVB technology (see clause L.2.1) is used, then the ServiceName attribute of the TextualIdentifier should be populated with the TV URI identifying the television channel. L.2.3.2 OMA BCAST technology If OMA-BCAST technology is used (see clause L.2.2), then the globalServiceID should be populated with the TV URI identifying the television channel. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 195 L.2.3.3 TV-Anytime Phase 2 technology If TV-Anytime Phase 2 technology is used (see clause L.2.2A), then the serviceId should be populated with the TV URI identifying the television channel. L.3 Mapping of CoD service L.3.1 Mapping of CoD service for DVB technology Table L.7C: Mapping of SIP parameters for CoD service - DVB technology IPTV SIP parameters DVB BCG Request-URI Locator defined in TS 102 822-4 [35], in sip-uri format NOTE: the user part of the Request-URI is a free string format corresponding to a unique content instance for one service provider, e.g. sip: cod_content1_hd@service_provider1.com. Table L.8: Mapping of SDP parameters for CoD service - DVB technology IPTV SDP parameters DVB BCG Connection Data at session level c=<network type> <address type> <connection address> Not retrieved from SSF <network type> Not retrieved from SSF <address type> Not retrieved from SSF <connection address> Not retrieved from SSF Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> "video" - Not retrieved from SSF <port> Client port- Not retrieved from SSF <transport> "RTP/AVP" or "UDP/H2221/MP2T" or "UDP/RAW/RAW depending on the transport layer used for the content, see clause 5.1.4.1 <fmt> "33" - Not retrieved from SSF Bandwidth BitRatetype as defined in TS 102 822-3-1 [33], clause 6.3.5 Media Announcements for FEC delivery m=<media> <port> <transport> <fmt list> see note <media> "application", not retrieved from SSF <port> Client port, not retrieved from SSF <transport> RTP/AVP <fmt> Dynamic payload type a=rtpmap:<fmt><encoding_name/clock_rate> <encoding_name/clock_rate> referring to the DVB- IP AL-FEC Base layer and is equal to: "vnd.dvb.iptv.alfec-base/90000" Connection Data at media level c=<network type> <address type> <connection address> <network type> Not retrieved from SSF <address type> Not retrieved form SSF <connection address> Not retrieved from SSF NOTE: The FEC delivery can only be associated to an RTP delivered content. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 196 L.3.2 Mapping of CoD service for OMA BCAST technology Table L.9: Mapping of SIP Parameters for CoD Service IPTV SIP parameters OMA BCAST Request-URI - Table L.10: Mapping of SDP Parameters for CoD Service IPTV SDP parameters OMA BCAST Connection Data at session level c=<network type> <address type> <connection address> <network type> N/A UE local data <address type> N/A UE local data <connection address> N/A UE local data Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> FFS <port> N/A UE local data <transport> FFS <fmt list> L.3.3 Mapping of CoD service for TV-Anytime Phase 2 technology Table L.11: Mapping of SIP Parameters for CoD Service IPTV SIP parameters TV-Anytime Phase 2 Request-URI - Table L.12: Mapping of SDP Parameters for CoD Service IPTV SDP parameters Corresponding TV-Anytime Phase 2 element in TS 102 822-3-1 [33], TS 102 822-4 [35] Connection Data at session level c=<network type> <address type> <connection address> <network type> ContentReferencingTable @ Result@ LocationsResult@ Locator <address type> ContentReferencingTable @ Result@ LocationsResult@ Locator <connection address> ContentReferencingTable @ Result@ LocationsResult@ Locator Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> ProgramInformationTable@ProgramInformation@AVAttributes <port> N/A UE local data <transport> ContentReferencingTable @ Result@ LocationsResult@ Locator <fmt list> ProgramInformationTable@ProgramInformation@AVAttributes ETSI ETSI TS 183 063 V3.6.1 (2014-08) 197 L.4 Mapping of IPTV Content Marker retrieval records to XML schema for service attachment This clause describes the mapping of IPTV Content Marker retrieval records to the generic XML schema for service attachment defined in annex M and clause 5.2.2.3. This clause describes the mapping of IPTV Content Marker record to the generic XML schema for service attachment defined in annex M and clause 5.2.2.3. Table L.13 TISPAN Element Name (copied from clause 5.2.2.3) Corresponding IPTV Content Marker field SSF @ID TISPAN defined field @Technology When IPTV Content Marker retrieval is advertised, this field shall be "tispan.org_iptvcontentmarker" @Version TISPAN defined field Description TISPAN defined field ServiceProvider Service Provider information @DomainName An internet DNS domain name registered by the Service Provider that uniquely identifies the Service Provider @LogoURI Pointer to a Service Provider logo for potential display Name Name of the Service Provider for display in one or more languages; one Service Provider name is allowed per language code, and at least one language shall be provided Description Description of the Service Provider for potential display in one or more languages; one description is allowed per language code Pull @Location Location of IPTV Content Marker retrieval DataType Type of IPTVContent Marker @Type Not applicable Segment Not applicable @ID Not applicable @Version Not applicable Push Not applicable @IPVersion @MulticastAddress Not applicable @MulticastPort Not applicable @SourceAddress Not applicable DataType Not applicable @Type Not applicable Segment Not applicable @ID Not applicable @Version Not applicable L.5 Mapping of Download service for DVB technology Table L.14: Mapping of SIP parameters for Download service - DVB technology IPTV SIP parameters DVB BCG Request-URI Locator defined in TS 102 034 [3] NOTE: The Request-URI is an HTTP URI as defined in TS 102 034 [3] clause 10.3.2.2, e.g. http://announcements.provider1.org:80/dvb/cds/session_description?Segment=a0ff#?dvb- cds-session-id=102. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 198 Table L.15: Mapping of SDP parameters for Download service - DVB technology IPTV SDP parameters DVB BCG Connection Data at session level c=<network type> <address type> <connection address> Not retrieved from SSF <network type> Not retrieved from SSF <address type> Not retrieved from SSF <connection address> Not retrieved from SSF Media Announcements for content delivery m=<media> <port> <transport> <fmt list> <media> "application" - Not retrieved from SSF <port> 9- Not retrieved from SSF <transport> TCP, Not retrieved from SSF <fmt> " iptv_http " - Not retrieved from SSF Bandwidth BitRatetype as defined in TS 102 822-3-1 [33], clause 6.3.5 Connection Data at media level c=<network type> <address type> <connection address> <network type> Not retrieved from SSF <address type> Not retrieved form SSF <connection address> Not retrieved from SSF ETSI ETSI TS 183 063 V3.6.1 (2014-08) 199 Annex M (normative): XML Schema for service attachment information This annex describes the XML schema for the service attachment information to be returned to UE by SDF. This XML schema is used when the service attachment information is transported via SIP Push mode and Pull mode as described in clauses 5.2.2.1 (Push mode) and 5.2.2.2 (Pull mode). <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="SSFList" type="tSSFList"> <xs:annotation> <xs:documentation>XML Body of the SDF SIP Notify Response</xs:documentation> </xs:annotation> </xs:element> <xs:complexType name="tSSFList"> <xs:sequence> <xs:element name="SSF" type="tSSF" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:complexType name="tSSF"> <xs:sequence> <xs:element name="Description" type="tMultilingual" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="ServiceProvider" type="tSSFServiceProvider" minOccurs="0"/> <xs:element name="Pull" type="tSSFPull" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Push" type="tSSFPush" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="ID" type="tHexadecimal16bit" use="required"/> <xs:attribute name="Technology" type="xs:string" use="required"/> <xs:attribute name="Version" type="tVersion"> <xs:annotation> <xs:documentation>The version number is incremented when one or more attributes of the SSF element have changed, so that the receiver knows whether it should update its data or not.</xs:documentation> </xs:annotation> </xs:attribute> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> <xs:simpleType name="tVersion"> <xs:restriction base="xs:integer"> <xs:minInclusive value="0"/> <xs:maxInclusive value="255"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tSSFServiceProvider"> <xs:sequence> <xs:element name="Name" type="tMultilingual" maxOccurs="unbounded"/> <xs:element name="Description" type="tMultilingual" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> </xs:sequence> <xs:attribute name="DomainName" type="tDomain" use="required"> <xs:annotation> <xs:documentation>It is recommended that the DomainName complies with the "preferred name syntax" of RFC1034 clause 3.5</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="LogoURI" type="xs:anyURI" use="optional"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 200 <xs:simpleType name="tDomain"> <xs:restriction base="xs:string"> <xs:pattern value="((.|\n|\r)*)?(\.(.|\n|\r)*)+"/> </xs:restriction> </xs:simpleType> <xs:complexType name="tSSFPull"> <xs:complexContent> <xs:extension base="tDataTypeList"> <xs:attribute name="Location" type="xs:anyURI" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"> <xs:annotation> <xs:documentation>Extension attribute to define further data</xs:documentation> </xs:annotation> </xs:anyAttribute> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="tSSFPush"> <xs:complexContent> <xs:extension base="tDataTypeList"> <xs:attribute name="IpVersion" type="tVersion" use="optional"/> <xs:attribute name="MulticastAddress" type="xs:string" use="required"/> <xs:attribute name="MulticastPort" type="xs:unsignedShort" use="required"/> <xs:attribute name="SourceAddress" type="xs:string" use="optional"/> <xs:anyAttribute namespace="##other" processContents="lax"> <xs:annotation> <xs:documentation> Extension attribute to define further data </xs:documentation> </xs:annotation> </xs:anyAttribute> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="tDataTypeList"> <xs:sequence maxOccurs="unbounded"> <xs:element name="DataType"> <xs:complexType> <xs:sequence minOccurs="0" maxOccurs="unbounded"> <xs:element name="Segment"> <xs:annotation> <xs:documentation>Segments are used to logically separate Service Selection information</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="ID" type="tHexadecimal16bit" use="required"/> <xs:attribute name="Version" type="tVersion" use="optional"/> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="Type" type="tHexadecimal8bit" use="required"> <xs:annotation> <xs:documentation> Specify the type of Service Selection Information that is delivered by the SSF </xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tMultilingual"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute name="Language" type="tLanguage" use="required"/> </xs:extension> </xs:simpleContent> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 201 </xs:complexType> <xs:simpleType name="tLanguage"> <xs:restriction base="xs:string"> <xs:annotation> <xs:documentation> <definition xml:lang="en">ISO 639-2 Language code</definition> </xs:documentation> </xs:annotation> <xs:minLength value="3"/> <xs:maxLength value="3"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tHexadecimal8bit"> <xs:restriction base="xs:string"> <xs:pattern value="[0-9a-fA-F]{1,2}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tHexadecimal16bit"> <xs:restriction base="xs:string"> <xs:pattern value="[0-9a-fA-F]{1,4}"/> </xs:restriction> </xs:simpleType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 202 Annex N: Void NOTE: The content in annex N is modified and moved to new annex Z. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 203 Annex O (normative): Procedure for definition of new SSF technologies New SSF technologies may be defined for support of the TISPAN IPTV services. Two technologies are defined so far in the present document, OMA BCAST and DVB-IPTV. This annex describes how new technologies (e.g. browser based technologies) can be defined by organizations willing to use the framework provided in the present document. The following procedure specifies how to define new technologies: 1) Definition of a technology. The Technology attribute of the XML schema defined in annex M is a string. The format of the Technology attribute shall be: <organization_name>_<subtechnology> where: - The organization_name shall be the ICANN registered domain name of the organization that defines its technology. - The subtechnology name identifies the SSF technology defined by the organization. It shall be unique within the context of the organization. It consists of one or more characters. Allowed characters are alphanumeric (i.e. 'a'-'z', 'A'-'Z', '0'-'9') plus the hyphen character ('-'). 2) Definition of the service attachment XML schema defined in annex M as applicable to the newly defined technology. The technology uses the XML structure to carry all relevant information, following the definition described in clause 5.2.2.3. For example, the DataType XML element is used to carry information which is meaningful only with regards to the technology. Example of completed XML schemas can be found in clause L.1. 3) Definition of the service selection procedures associated with the newly specified technology, for the Pull mode and the Push mode, if used. Procedures defined within the present document may be reused. 4) Mapping of the service selection information to the IPTV services defined in the present document. Below is the mapping that has to be completed (provided the IPTV service is defined with the technology). - Mapping for BC Service (example is found in clause L.2). - Mapping for CoD Service (example is found in clause L.3). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 204 Annex P (normative): XML Schema for UE Profile This XML Schema defines the UE information that is specified by UE during service attachment and may be carried within body of the SIP SUBSCRIBE request. The format of the attributes UserEquipmentID and IPEncapsulation is outside of the scope of the present document. The usage and personalization of the service selection data based on the attributes UserEquipmentClass and IPEncapsulation is outside of the scope of the present document. <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvueprofile" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvueprofile" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tva="urn:tva:metadata:2005" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="urn:tva:metadata:2005" schemaLocation="tva_metadata_3-1_v131.xsd"/> <xs:annotation> <xs:documentation xml:lang="en"> Defines the capabilities of the UE that is currently associated with the user </xs:documentation> </xs:annotation> <xs:element name="UEInformation" type="tUEProfile"/> <xs:complexType name="tUEProfile"> <xs:sequence> <xs:element name="UserEquipmentID" type="tUEID"/> <xs:element name="UserEquipmentClass" type="tUserEquipmentClass"/> <xs:element name="Resolution" type="tResolution" minOccurs="0"/> <xs:element name="SupportedEncodings" type="tSupportedEncodings" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="IPEncapsulations" type="tIPEncapsulations" minOccurs="0" maxOccurs="unbounded"/> <!-- extension mechanism --> <xs:element name="any" type="AnyType"></xs:element> <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="AnyType"> <xs:sequence> <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tUEID" final="list restriction"> <xs:annotation> <xs:documentation> <label xml:lang="en">User Equipment ID</label> <definition xml:lang="en">Unique Identifier for the UE(eg; Could be MAC address of UE) </definition> </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="0"/> <xs:maxLength value="16"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="tUserEquipmentClass" final="list restriction"> <xs:annotation> <xs:documentation> <label xml:lang="en">User Equipment class</label> <definition xml:lang="en">Specifies the type of UE </definition> </xs:documentation> </xs:annotation> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 205 <xs:restriction base="xs:string"> <xs:enumeration value="STB"> </xs:enumeration> <xs:enumeration value="PC"> </xs:enumeration> <xs:enumeration value="Handset"> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:complexType name="tResolution"> <xs:attribute name="HorizontalSize" type="xs:integer"> <xs:annotation> <xs:documentation>horizontal size in pixels of the screen</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="VerticalSize" type="xs:integer"> <xs:annotation> <xs:documentation>vertical size in pixels of the screen</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="Rotate" type="xs:boolean"> <xs:annotation> <xs:documentation>set to TRUE if the screen can be rotated (horizontal becomes vertical)</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> <xs:complexType name="tSupportedEncodings"> <xs:annotation> <xs:documentation> <label xml:lang="en">encodings</label> <definition xml:lang="en">Specifies the supported combinations of audio and video encodings (eg. MPEG2,H264 AC3, AAC etc)</definition> </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="AudioEncoding" type="tAudioEncoding" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="VideoEncoding" type="tVideoEncoding" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tAudioEncoding"> <xs:annotation> <xs:documentation> <label xml:lang="en">Audio Encoding</label> <definition xml:lang="en">Specifies supported audio encoding properties</definition> </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="Encoding" type="tva:ControlledTermType"/> <!-- extension mechanism --> <xs:element name="any" type="AnyType"></xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="tVideoEncoding"> <xs:annotation> <xs:documentation> <label xml:lang="en">Video Encoding</label> <definition xml:lang="en"> Specifies supported video encoding properties </definition> </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="Encoding" type="tva:ControlledTermType"/> <xs:element name="SupportedFrameRate" type="tva:FrameRateType" minOccurs="0" maxOccurs="unbounded"/> <!-- extension mechanism --> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tIPEncapsulations"> <xs:annotation> <xs:documentation> <label xml:lang="en">encapsulation</label> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 206 <definition xml:lang="en">Specifies the IP encapsulation that is supported on device ("UDP/RTP" or "UDP/M2TS" or "UDP/RTP/M2TS") </definition> </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="UDP/RTP"> </xs:enumeration> <xs:enumeration value="UDP/M2TS"> </xs:enumeration> <xs:enumeration value="UDP/RTP/M2TS"> </xs:enumeration> </xs:restriction> </xs:simpleType> </xs:schema> Example of XML document conforming to this structure. The SupportedEncoding field carries the list of the several coding format that the device can handle. The Name element is optional, it is presented herein for user readability. <?xml version="1.0" encoding="UTF-8"?> <UEInformation xmlns="?" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserEquipmentID>STB-dc14b2</UserEquipmentID> <UserEquipmentClass>STB</UserEquipmentClass> <Resolution Horizontal="720" Vertical="576" Rotate="FALSE"/> <SupportedEncodings> <AudioEncoding> <Encoding href="urn:mpeg:mpeg7:cs:AudioCodingFormatCS:2001:3"> <Name>MPEG-1 Audio</Name> </Encoding> </AudioEncoding> <AudioEncoding> <Encoding href="urn:mpeg:mpeg7:cs:AudioCodingFormatCS:2001:5.4"> <Name>MPEG-4 Main Audio Profile</Name> </Encoding> </AudioEncoding> <AudioEncoding> <Encoding href="urn:mpeg:mpeg7:cs:AudioCodingFormatCS:2001:5.5"> <Name>MPEG-4 High Quality Audio Profile</Name> </Encoding> </AudioEncoding> <AudioEncoding> <Encoding href="urn:dvb:metadata:cs:AudioCodecCS:2007:1"> <Name>MPEG-4 DVB Audio</Name> </Encoding> </AudioEncoding> <VideoEncoding> <Encoding href="urn:mpeg:mpeg7:cs:VisualCodingFormatCS:2001:1"> <Name>MPEG-1 Video</Name> </Encoding> </VideoEncoding> <VideoEncoding> <Encoding href="urn:mpeg:mpeg7:cs:VisualCodingFormatCS:2001:2.2"> <Name>MPEG-2 Video Main Profile</Name> </Encoding> </VideoEncoding> <VideoEncoding> <Encoding href="urn:dvb:metadata:cs:VideoCodecCS:2007:1.1"> <Name>H264 Baseline Profile</Name> </Encoding> <SupportedFrameRate>30</SupportedFrameRate> </VideoEncoding> <VideoEncoding> <Encoding href="urn:dvb:metadata:cs:VideoCodecCS:2007:1.2"> <Name>H264 Main Profile</Name> </Encoding> <SupportedFrameRate>30</SupportedFrameRate> <SupportedFrameRate>24</SupportedFrameRate> </VideoEncoding> </SupportedEncodings> <IPEncapsulation>M2TS/UDP</IPEncapsulation> <IPEncapsulations>M2TS/RTP</IPEncapsulations> </UEInformation> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 207 Annex Q (informative): Combination of SIP and RTSP protocols for content on demand The SIP procedures described in clause 5 influence which of the two RTSP methods described in clause 7 to be used. Figures Q.1 and Q.2 specify the decision logic of the UE and the MCF respectively. Q.1 User Equipment (UE) side RTSP method decision logic Figure Q.1 shows the UE-side RTSP method decision logic. Method 2 Method 1 RTSP session ID is received in the answer for initial INVITE? Use RTSP DESCRIBE and RTSP SETUP to get media delivery m-line information Use RTSP SETUP to get the RTSP session ID Use SIP ReINVITE to reserve the bandwidth for media stream YES NO NO UE sets m-line parameters for both media control and media delivery channel? UE sends initial INVITE with both media control and media delivery m-line parameters YES Are the m-line parameters received for media control? Abort! NO YES Figure Q.1: UE-side RTSP method decision logic ETSI ETSI TS 183 063 V3.6.1 (2014-08) 208 Q.2 Media Control Function (MCF) side RTSP method decision logic Figure Q.2 shows the MCF-side RTSP method decision logic. Method 2 MCF chooses Method 1 Method 1 Initial INVITE received by MCF NO YES YES NO Network parameters received for media control and media delivery channel? Include RTSP Session ID in SIP 200OK Figure Q.2: MCF-side RTSP method decision logic ETSI ETSI TS 183 063 V3.6.1 (2014-08) 209 Annex R (informative): Initial Filter Criteria Beyond the method name, (SUBCRIBE, INVITE, etc.), the following elements may be used a service trigger point to build initial filter criteria enabling Application Servers to be involved in the processing of IPTV procedures: - The event name of a SUBSCRIBE request. - The contents of the Accept header in a SUBSCRIBE request (e.g. MIME types). - The contents of the P-Preferred-Service header or the Accept-Contact header (i.e. ICSI). - The Request-URI, in which case the content tag will typically contain an Extended Regular Expressions (ERE) as defined in clause 9 in IEEE 1003.1-2004 [i.5] such that any Request-URI that includes a particular pattern (e.g. a domain name) matches the criteria. The actual list of criteria depends on whether the public user identity is dedicated to the IPTV service or not. The following example illustrates the case of an IFC used to trigger an application server that provides the SDF function only. <InitialFilterCriteria> <Priority>0</Priority> <TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <Method>INVITE</Method> </SPT> <SPT> <ConditionNegated>0</ConditionNegated> <Group>0</Group> <RequestURI>@iptvdiscovery.homedomain.com$</RequestURI> </SPT> </TriggerPoint> <ApplicationServer> <ServerName>sip:SDF-AS1@homedomain.com</ServerName> <DefaultHandling>0</DefaultHandling> </ApplicationServer> </InitialFilterCriteria> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 210 Annex S (normative): XML Schema for IPTV Notification <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvnotification" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvnotification" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:nt="urn:org:etsi:ngn:params:xml:ns:iptvnotification" attributeFormDefault="unqualified"> <xs:element name="IPTVNotification" type="tIPTVNotification" /> <xs:complexType name="tIPTVNotification"> <xs:sequence> <xs:element name="NotificationReason" type="tNotificationReason" minOccurs="1" maxOccurs="1" /> <xs:element name="NotificationSender" type="xs:string" minOccurs="0" /> <xs:element name="ContentIdentifier" type="xs:anyURI" minOccurs="0" /> <xs:element name="NotificationReceiver" type="xs:string" minOccurs="0" /> <xs:choice> <xs:element name="MediaPathNotificationInfo" type="tMediaPathNotificationInfo" /> <xs:element name="ContentInsertionInfo" type="tContentInsertionInfo" /> <xs:element name="IncomingCallInfo" type="tIncomingCallInfo" /> <xs:element name="CPVRRecordInfo" type="tCPVRRecordInfo" /> <xs:element name="ContentRecommendationInfo" type="tContentRecommendationInfo" /> <xs:element name="Extension" type="tExtension" minOccurs="0" maxOccurs="unbounded"/> </xs:choice> </xs:sequence> </xs:complexType> <xs:simpleType name="tNotificationReason"> <xs:restriction base="xs:string"> <xs:enumeration value="ContentInsertion" /> <xs:enumeration value="InstantMessage" /> <xs:enumeration value="IncomingCall" /> <xs:enumeration value="CPVRRecord" /> <xs:enumeration value="ContentRecommendation" /> </xs:restriction> </xs:simpleType> <xs:complexType name="tMediaPathNotificationInfo"> <xs:sequence> <xs:element name="MulticastAddress" type="xs:string" minOccurs="1" /> <xs:choice> <xs:element name="InstantMessageInfo" type="xs:string" minOccurs="0" /> <xs:element name="Extension" type="tExtension" minOccurs="0" /> </xs:choice> </xs:sequence> </xs:complexType> <xs:complexType name="tContentInsertionInfo"> <xs:sequence> <xs:element name="SessionId" type="xs:string" minOccurs="1" /> <xs:element name="ContentInsertionReason" type="tContentInsertionReason" minOccurs="1" /> <xs:element name="ContentInsertionTime" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="ContentInsertionStartTime" type="xs:dateTime" /> <xs:element name="ContentInsertionDuration" type="xs:duration" /> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element name="MulticastContent" type="xs:anyURI" /> <xs:element name="UnicastContent" type="xs:anyURI" /> </xs:choice> </xs:sequence> </xs:complexType> <xs:simpleType name="tContentInsertionReason"> <xs:restriction base="xs:string"> <xs:enumeration value="Advertising" /> <xs:enumeration value="PausedContent" /> <xs:enumeration value="Generic" /> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 211 <xs:enumeration value="Extension" /> </xs:restriction> </xs:simpleType> <xs:complexType name="tIncomingCallInfo"> <xs:sequence> <xs:element name="CallerID" type="xs:anyURI" minOccurs="1" /> </xs:sequence> </xs:complexType> <xs:complexType name="tCPVRRecordInfo"> <xs:sequence> <xs:element name="CPVRContentID" type="xs:anyURI" minOccurs="0" /> <xs:element name="BCServiceId" type="xs:anyURI" minOccurs="1" /> <xs:element name="RecordEndDate" type="xs:dateTime" minOccurs="1" /> </xs:sequence> </xs:complexType> <xs:complexType name="tContentRecommendationInfo" > <xs:sequence> <xs:element name="ContentIdentifer" minOccurs="1" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:anyURI"> <xs:attribute name="ServiceType" type="xs:string" use="optional"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:annotation> <xs:documentation> This element is reserved for further extensions </xs:documentation> </xs:annotation> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 212 Annex T (normative): XML Schema for Restricted Trick Play <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns:iptvrestrictedtrickplay" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVRestrictedTrickPlay"> <xs:complexType> <xs:sequence> <xs:element name="RestrictedTrcikPlayPolicy" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="RestrictedTrickPlayPolicy"> <xs:complexType> <xs:sequence> <xs:element name="ContentID" type="xs:string" minOccurs="0"/> <xs:element name="StartTime" type="xs:string" minOccurs="0"/> <xs:element name="EndTime" type="xs:string" minOccurs="0"/> <xs:element name="RTSPOperation" type="tRTSPOperation" maxOccurs="unbounded"/> <xs:element name="Extension" type="tExtension" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tRTSPOperation"> <xs:restriction base="xs:unsignedByte"> <xs:minInclusive value="0"/> <xs:maxInclusive value="1"/> <xs:enumeration value="0"> <xs:annotation> <xs:documentation> <label xml:lang="en">FastForward</label> <definition xml:lang="en">Reqeust to fast forward</definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="1"> <xs:annotation> <xs:documentation> <label xml:lang="en">Pause</label> <definition xml:lang="en">Request to pause</definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 213 Annex U (normative): XML Schema for PCh Conflict Option & Choice data <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvpchdata" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvpchdata" xmlns:ns="urn:org:etsi:ngn:params:xml:ns:iptvpchdata" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="PChConflictOptionData"> <xs:complexType> <xs:sequence> <xs:element name="ConflictOption" type="tPChConflictOption" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="PChConflictChoiceData" type="tPChConflictOption" /> <xs:simpleType name="tPChConflictOption"> <xs:restriction base="xs:string"> <xs:enumeration value="PlayAndRecord"> <xs:annotation> <xs:documentation> <definition xml:lang="en"> Keeps the on-going session alive and initiates another task for recording the upcoming BC content </definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="PlayAndDelay"> <xs:annotation> <xs:documentation> <definition xml:lang="en"> Keeps the on-going session alive and delay the play of the upcoming CoD content by modifying the PCh profile info </definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SwitchAndMark"> <xs:annotation> <xs:documentation> <definition xml:lang="en"> Teardown the on-going session, mark the current CoD content play information, and switch to the next PCh item as indicated </definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SwitchAndRecord"> <xs:annotation> <xs:documentation> <definition xml:lang="en"> Teardown the on-going session, record the current BC content, and switch to the next PCh item as indicated </definition> </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="PlayAndSwitch"> <xs:annotation> <xs:documentation> <definition xml:lang="en"> Keep the on-going session alive till its end and switch to the next PCh item as indicated </definition> </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 214 Annex V (normative): XML Schema for IPTV Content Marker <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="urn:org:etsi:ngn:params:xml:ns:iptvinformation" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:org:etsi:ngn:params:xml:ns:iptvinformation" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVContentMarkerRequest"> <xs:complexType> <xs:sequence> <xs:element name="IPTVInformationDataCommand" type="tIPTVInformationDataCommand" /> <xs:element name="IPTVContentMarker" type="tIPTVContentMarker" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:simpleType name="tIPTVInformationDataCommand"> <xs:restriction base="xs:string"> <xs:enumeration value="Update" /> <xs:enumeration value="Retrieval" /> </xs:restriction> </xs:simpleType> <xs:complexType name="tIPTVContentMarker"> <xs:sequence> <xs:element name="IPTVContentMarkerID" type="xs:string"/> <xs:element name="OwnerUserID" type="xs:string" /> <xs:element name="ForbiddenViewUser" type="xs:string" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="IPTVServiceType" type="xs:string" /> <xs:element name="StartTimeOfIPTVContentMarker" type="xs:dateTime" minOccurs="0"/> <xs:element name="EndTimeOfIPTVContentMarker" type="xs:dateTime" minOccurs="0"/> <xs:element name="Tag" type="xs:string" minOccurs="0"/> <xs:element name="Rank" type="xs:string" minOccurs="0"/> <xs:element name="UserComment" type="xs:string"/> <xs:element name="GenerationTime" type="tExtension" minOccurs="0"/> <xs:element name="ExpiryTime" type="tExpiryTime" minOccurs="0"/> <xs:element name="RetrievalCount" type="xs:nonNegativeInteger" minOccurs="0"/> <xs:element name="RetrievalTime" type="xs:dateTime" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="tExtension"> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:simpleType name="tExpiryTime" > <xs:union memberTypes="tExpiryTimeException xs:dateTime"/> </xs:simpleType> <xs:simpleType name="tExpiryTimeException"> <xs:restriction base="xs:integer"> <xs:pattern value="(-1|0)"/> </xs:restriction> </xs:simpleType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 215 Annex W (normative): Inter-destination media synchronization W.1 RTCP XR Block Type for inter-destination media synchronization Figure W.1 describes the RTCP XR Block Type for reporting inter-destination media synchronization information on an RTP media stream, as specified in [71]. Its definition is based on [45]. The RTCP XR is used to report information on receipt times and presentation times of RTP packets to e.g. a Sender [44], a Feedback Target [43] or a Third Party Monitor [44]. The RTCP XR is also used to indicate synchronization settings instructions to a receiver of the RTP media stream. Figure W.1: RTCP XR Block Type for inter-destination media synchronization The first 64 bits form the header of the RTCP XR, as defined in [45]. The SSRC of packet sender identifies the sender of the specific RTCP packet. • Block Type (BT): 8 bits. It identifies the block format. Its value shall be set to 12, as specified in [71]. NOTE: The value BT=12 has been registered by IANA [i.12]. • Synchronization Packet Sender Type (SPST): 4 bits. This field identifies the role of the packet sender for this specific eXtended Report. It can have the following values. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |V=2|P| Resrv | PT=XR=207 | length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of packet sender | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | BT=12 | SPST |Resrv|P| block length=7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PT | Resrv | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Media Stream Correlation Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of media source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, most significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received NTP timestamp, least significant word | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Received RTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Presented NTP timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ETSI ETSI TS 183 063 V3.6.1 (2014-08) 216 Table W.1: Synchronization Packet Sender Types (SPST) SPST value Role of packet sender Details Reference 0 Reserved For future use. [71] 1 SC, see clause 5.7. The packet sender uses this XR to report synchronization status information. Timestamps relate to the SC input. [71] 2 MSAS, see clause 5.8. The packet sender uses this XR to report synchronization settings instructions. Timestamps relate to the input of a virtual SC, which acts as reference to which the SCs connected to this MSAS are synchronized. The present document 3 SC' input The packet sender uses this XR to report synchronization correlation information related to the incoming media stream of SC'. Timestamps relate to the SC' input. The present document 4 SC'output The packet sender uses this XR to report synchronization correlation information related to the outgoing media stream of SC'. Timestamps relate to the SC' input. (see note) The present document 5 to 15 Reserved For future use. [71] NOTE: Following the RTP/RTCP specification [44], RTP timestamps relate to the arrival time of the first octet of an RTP packet. In case of SPST=4 (SC' output), there is not such an arrival time as the media stream is re-originated at the SC'. In this case, the timestamp would relate to the arrival time of the equivalent octet (representing e.g. the same video pixel or audio sample) of the incoming media steam. • Reserved bits (Resrv): 3 bits. These bits are reserved for future use and shall be set to 0. • Packet Presented NTP timestamp flag (P): 1 bit. Bit set to 1 if the Packet Presented NTP timestamp contains a value, 0 if it is empty. If this flag is set to zero, then the Packet Presented NTP timestamp shall not be inspected. • Block Length: 16 bits. This shall be set to 7, as this RTCP Block Type has a fixed length. • Payload Type (PT): 7 bits. This field identifies the format of the media payload, according to [57]. The media payload is associated with an RTP timestamp clock rate. This clock rate provides the time base for the RTP timestamp counter. • Reserved bits (Resrv): 25 bits. These bits are reserved for future use and shall be set to 0. • Media Stream Correlation Identifier: 32 bits. This identifier is used to correlate synchronized media streams. The value 0 (all bits are set "0") indicates that this field is empty. The value 2^32-1 (all bits are set "1") is reserved for future use. If the RTCP Packet Sender is an SC or an MSAS (SPST=1 or SPST=2), then the Media Stream Correlation Identifier maps on the SyncGroupId. If the RTCP Packet Sender is an SC' (SPST=3 or SPST=4), related incoming and outgoing media streams have the same Media Stream Correlation Identifier. • SSRC: 32 bits. The SSRC of the media source shall be set to the value of the SSRC identifier carried in the RTP header [44] of the RTP packet to which the XR relates. • Packet Received NTP timestamp: 64 bits. This NTP timestamp [56] is the arrival wallclock time of the first octet of the RTP packet to which the XR relates. For SPST=2 it relates to a virtual SC to which the other SCs in the synchronization group may synchronize. For SPST=4 the SC' should calculate backwards when the content (video frame, audio sample) associated with the first octet of the RTP packet arrived. As specified in Clause 11.3.2, SCs shall be NTP synchronized. • Packet Received RTP timestamp: 32 bits. This timestamp has the value of the RTP time stamp carried in the RTP header [44] of the RTP packet to which the XR relates. • Packet Presented NTP timestamp: 32 bits. This timestamp reflects the NTP time when the data contained in the first octet of the associated RTP packet is presented to the user. It consists of the least significant 16 bits of the NTP seconds part and the most significant 16 bits of the NTP fractional second part. If this field is empty, then it shall be set to 0 and the Packet Presented NTP timestamp flag (P) shall be set to 0. It shall be empty for SPST=3 and SPST=4. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 217 W.2 SDP parameter for inter-destination media synchronization The SDP parameter sync-group is used to signal the use of the RTCP XR block for inter-destination media synchronization specified in clause W.1. This SDP parameter extends rtcp-xr-attrib as follows, using Augmented Backus-Naur Form [61]. rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF; Original definition from RFC 3611 [45], clause 5.1 xr-format =/ grp-sync; Extending xr-format for inter-destination media synchronization grp-sync = "grp-sync" [",sync-group=" SyncGroupId] SyncGroupId = 1*DIGIT; Numerical value from 0 till 4294967295 DIGIT = %x30-39 SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. SyncGroupId identifies a group of SCs for inter-destination media synchronization. It maps on the Media Stream Correlation Identifier of clause W.1 for SPST=1 and SPST=2. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. The following is an example of the SDP attribute for inter-destination media synchronization. • a=rtcp-xr:grp-sync,sync-group=42 NOTE: The parameter "grp-sync" for the SDP attribute "a=rtcp-xr" has been registered by IANA [i.13]. W.3 Introduction to inter-destination media synchronization (informative) This clause provides an informal introduction to inter-destination media synchronization to aid the understanding of annex W. Detailed procedures are provided in the main body of this specification. The purpose of inter-destination media synchronization is achieving that content is played out synchronously on terminals of two or more users watching the same content, compensating for delay difference caused by transport, coding and other. The following functional elements are involved in inter-destination media synchronization. • SC: Synchronization Client: - Mapping 1: SC in User Equipment (UE), supports both SIP and RTCP signalling - Mapping 2: SC in Transport Processing Functions, supports only RTCP signalling • MSAS: Media Synchronization Application Server: - Session-oriented part for SIP signalling, typically co-located with the Sevice Control Function (SCF) - Media-oriented part for RTCP signalling, typically separate from the session-oriented part and closer to the media streams • SC': Synchronization Client prime: - Option for functional entities that modify and/or re-originate media streams, like transcoders If SIP is supported (mapping 1) then the SC may initiate a synchronization session by including the "a=rtcp-xr:grp- sync,sync-group=<SyncGroupId>" SDP attribute in the SIP message. The SyncGroupId identifies the group of SCs involved in inter-destination media synchronization, which is similar to the ConferenceId in a conference call. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 218 The session-oriented part of the MSAS responds to the SC, providing the IP address and port number of the media- oriented part of the MSAS and providing or confirming the SyncGroupId. There are several variations to the SIP signalling, depending whether inter-destination media synchronization is initiated together with session initiation or later in the session, and on the SIP/RTSP signalling method used. RTCP signalling SC, SC' and MSAS uses the RTCP XR specified in clause W.1. The Synchronization Packet Sender Type (SPST) indentifies the role of the packet sender for this specific eXtended Report. • From SC to MSAS: synchronization status information, such as arrival time information (SPST=1) • From MSAS to SC: delay infromation in the form of synchronization settings instructions (SPST=2) • From SC' to MSAS: synchronization correlation information: - related to the SC' input (SPST=3) - related to an SC' output (SPST=4) RTCP signalling is used between SC and MSAS, and from SC' to MSAS, using the RTCP XR specified in clause W.1. The Synchronization Packet Sender Type (SPST) indentifies the role of the packet sender for this specific eXtended Report. The Media Stream Correlation Identifier identifier is used to correlate synchronized media streams. For SC it corresponds to the SyncGroupId. For SC' is it used to correlate the input and output(s) for a specific media stream. Together, arrival time infotmation such as the Packet Received NTP timestamp, Packet Received RTP timestamp and the Packet Presented NTP timestamp indicate at what wall-clock time an RTP packet passed or should pass a specific point in an SC or SC'. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 219 Annex X (normative): XML Schema for Content Switch <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uep="urn:org:etsi:ngn:params:xml:ns:iptvcontentswitch" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="IPTVContentSwitch"> <xs:complexType> <xs:sequence> <xs:element name="SwitchedContentItem" type="tSwitchedContentItem" maxOccurs="unbounded" /> </xs:sequence> <xs:attribute name="content-id" type="xs:string" use="required" /> </xs:complexType> </xs:element> <xs:complexType name="tSwitchedContentItem"> <xs:sequence> <xs:element name="ContentItemID" type="xs:string" minOccurs="1"/> <xs:element name="ContentItemName" type="xs:string" minOccurs="1"/> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 183 063 V3.6.1 (2014-08) 220 Annex Y (normative): Support for an Application profile for SIP User Agents This annex defines the normative text for a new application profile for a SIP User agent in addition to the 3 existing profiles currently defined in the SIP Config framework. Y.1 Introduction SIP User Agents require profile data to function properly. A mechanism to obtain profile data is specified by the Framework for SIP User Agent Profile Delivery I-D ietf-sipping-config-framework [63]. The framework separates profile data into three categories, termed profile types, local-network, device and user. Each profile type deals with a specific data set, e.g. the device profile type is used to obtain device-specific configuration. The framework also allows for future extensions to support additional profile types. The present document specifies one such extension to support an additional profile type, application. This can be used by user agents for requesting profile data for one or more applications that they support. Y.2 Motivation The motivation for an independent application profile type can be demonstrated using the scenario described in figure Y.1. The scenario considers a device (not shown) that supports three applications (X, Y, Z). It also considers two users (A, B). Applications X and Y are user-specific, i.e. restricted to known end-users, where as Application Z can be used by any user (e.g. Weather Information). ------- ------- -------- | App X | | App Y | | App Z | ------- ------- -------- | | | | | | | <any user> | | | ------ ------ |User A| |User B| ------ ------ Figure Y.1: Motivation for application profile type Each application needs specific profile data to function. For instance, an application such as Video on Demand (VoD) would require VoD server information, codecs for rendering, minimum bandwidth requirements etc. It may also have requirements specific to users, such as rating and cost restrictions (parental controls). Further, the presence of an application does not always mean that it is enabled. For example, a Service Provider may disable VoD for certain subscription levels. Profile data related to such applications, especially those that are unrelated to specific users, would need to be retrieved for successful operation. This profile data may be retrieved during device boot-up if it is configured to do so, e.g. via the device profile. The profile data can also be retrieved dynamically, e.g. when the application is enabled. Such profile data does not qualify under any existing profile types specified by the SIP UA configuration framework, viz., local-network, device and user. The only exception is application profile data that is specific to users, which can be provided via the user profile type. Thus the need for an additional profile type specific to applications. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 221 Y.3 Overview Y.3.1 Profile Type Definition The present document specifies a new profile type for use with the SIP UA configuration framework. The name of the profile type is 'application'. The present document also defines an additional event header parameter for use with the application profile type. This parameter is termed "appids". Y.3.2 Parameter 'appids' The "appids" parameter describes the application profiles being requested. Its value is an identifier for the application, or a comma-separated list of such identifiers. Each application identifier is a unique value defined by the application specification, along with the profile content, and is in the form of a URI (RFC 4395 [66]), preferably a URN (RFC 3406 [67]). This parameter value SHOULD be provided in the SUBSCRIBE request for the 'application' profile- type only, along with the other three parameters (vendor, model and version) specified in I-D. ietf-sipping-config- framework [63]. This parameter is useful to the PDS to affect the profile provided. Behavior when the "appids" parameter is omitted is currently undefined and treated as an error. Future standards action may specify this behavior. In the following ABNF defining the syntax, EQUAL and DQUOTE are defined in RFC 3261 [62]: appids = "appids=" list-of-app-ids list-of-app-ids = DQUOTE app-id *("," app-id) DQUOTE app-id = 1*(subset-print-chars) subset-print-chars= %x21 /%x23-25 / %x27-29 / %x2D-3C / %x3E-7E ;All printable characters except ", =, &, *, + ;comma or white-space characters. The "appids" parameter appears in the Event header of the NOTIFY request to specify the actual application the NOTIFY belongs to. In the initial NOTIFY following a SUBSCRIBE, the appids parameter SHOULD list all applications obtained in the subscription, which may be a subset of the applications listed in the SUBSCRIBE. The only case in which the "appids" parameter MAY be omitted from the initial NOTIFY is when only one application was listed in the SUBSCRIBE. If the SUBSCRIBE included an "appids" parameter, the "appids" parameter of the initial NOTIFY SHALL NOT list applications not present in the SUBSCRIBE. If the parameter contains a list of applications, the order in the appids parameter SHALL be the same as followed in the body (see below). Subsequent NOTIFY requests on a single application subscription MAY omit the "appids", since the application context is implied by the subscription dialog. Y.3.3 Summary of Event Header The following are example Event headers which may occur in SUBSCRIBE requests. The examples are not intended to show complete SUBSCRIBE requests. Event: ua-profile;profile-type=application; vendor="vendor.example.com";model="Z100";version="1.2.3" Event: ua-profile;profile-type=application; vendor="vendor.example.com";model="Z100";version="1.2.3"; appids="myapplication" Event: ua-profile;profile-type=application; vendor="vendor.example.com";model="Z100";version="1.2.3"; appids="myapplication1,myapplication2,myapplication3" The following are example Event headers which may occur in NOTIFY requests. These example headers are not intended to be complete NOTIFY requests. Event: ua-profile;profile-type=application Event: ua-profile;profile-type=application;appids="myapplication1" Event: ua-profile;profile-type=application; appids="myapplication2,myapplication3" ETSI ETSI TS 183 063 V3.6.1 (2014-08) 222 The table shows the use of Event header parameters in SUBSCRIBE requests for the application profile type: profile-type || application =========================== appids || s vendor || o model || o version || o effective-by || m - mandatory s - SHOULD be provided o - optional The table shows the use of Event header parameters in NOTIFY requests for the application profile type: profile-type || application =========================== appids || s vendor || model || version || effective-by || o Y.3.4 SUBSCRIBE Bodies The present document defines an enhancement to the I-D.ietf-sipping-config-framework [63] by specifying a use for the SUBSCRIBE request body. If the appids parameter contains a single application identifier, the SUBSCRIBE message body MAY contain a single body part appropriate for the application. If the appids parameter contains a list of applications, the body of the SUBSCRIBE MAY contain a "multipart/mixed" content-type, with appropriate body parts for each of the applications for which the UA is subscribing. The body parts SHALL be in the same order in which they are listed in the "appids" parameter, and if any body parts are present, all applications shall have a corresponding part, even if empty. If present in the SUBSCRIBE request, the body SHALL be used by the application-specific PDS to tailor the NOTIFY responses to the subscribing UA for each of the applications listed. The meaning and form of the SUBSCRIBE body is specified by each application. NOTE: An alternative to requiring all applications to have body parts if any do, and to using "empty" parts where a body part is not needed, is to employ Content-Description to name the appid to which the part corresponds. Y.3.5 NOTIFY Bodies The NOTIFY message body contains a content type specific to the requested application (this type shall be listed in the Accept header of the SUBSCRIBE). If the subscription is for multiple applications, the initial NOTIFY message body will contain a "multipart/mixed" content-type, and the ordering of the body-parts corresponds to the ordering of the "appids" application values. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 223 Y.4 Example Usage SUBSCRIBE sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB @example.com SIP/2.0 Event: ua-profile;profile-type=application;appids="sampleapplication" From: sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB @example.com;tag=1234 To: sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB@example.com Call-ID: 3573853342923422@192.0.2.44 CSeq: 2131 SUBSCRIBE Contact: sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB @example.com ;+sip.instance="<urn:uuid:00000000-0000-0000-0000-123456789AB0>" Via: SIP/2.0/TCP 192.0.2.41; branch=z9hG4bK6d6d35b6e2a203104d97211a3d18f57a Accept: message/external-body, application/x-z100-device-profile Content-Length: 0 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 224 Annex Z (normative): SDP attributes for IMS-based IPTV Z.0 General RFC 2327 [68] generically defines SDP attributes as follows: attribute-fields = *("a=" attribute CRLF) attribute = (att-field ":" att-value) | att-field This annex specifies several IPTV attributes as special cases of this ABNF syntax. Z.1 SDP attributes for Personalized Service Composition Z.1.1 SDP attribute for PSC identifier The SDP attribute a=PSCid is used to signal that a particular SIP session is part of a PSC. The use of this attribute is specified in clauses 5.1.11 and 5.3.10. The Augmented Backus-Naur Form [61] specification of this SDP attribute is as follows: psc-attribute-field = "a=" psc-attribute CRLF psc-attribute = "PSCid" ":" PSCid PSCid = *(%x21-7E); Zero or more of any printable character, except for "space". The following is an example of the SDP attribute for PSC identifier: • a=PSCid:MyPersonalisedServiceComposite12345<>[[[-+!@#$%^&*() NOTE: As specified in ABNF above, the attribute parameter of a=PSCid is case-sensitive. So "a=PSCid:case" is different from "a=PSCid:CASE". Z.2 SDP attributes for BC Z.2.1 SDP attributes for BC Service The SDP attribute a=bc_service is used to signal the BCServiceId (channel).The use of this attribute is specified in clauses 5.1.3 and 5.3.1. The Augmented Backus-Naur Form [61] specification of this SDP attribute is as follows: bc-service-attribute-field = "a=" bc-service-attribute CRLF bc-service-attribute = "bc_service" ":" BCServiceId BCServiceId = *16(ALPHA / DIGIT / "-"); Zero up to 16 letters, digits or dashes. The following is an example of the SDP attribute for BC service identifier. • a=bc_service:CCTV-5-Sports ETSI ETSI TS 183 063 V3.6.1 (2014-08) 225 Z.2.2 SDP attributes for BC Service Package The format of the a=bc_service_package attribute shall be the following: bc-service-package-attribute-field = "a=" bc-service-package-attribute CRLF bc-service-package-attribute = "bc_service_package" ":" BCPackage BCPackage = BCPackageId *1("[" mult-list "]" ) ; 0 or 1 mult_list BCPackageId = *16(ALPHA / DIGIT / "-"); Zero up to 16 letters, digits or dashes. mult-list = "mult_list:" source-unit *("/" source-unit) ; 1 or more source-unit source-unit = "[" 0*1("src_list:" source-addresses) "]" multicast-addresses "[" BCServiceId "]" ; one BCService Id, one or more multicast addresses, and optionally one or more source addresses source-addresses = IPaddresses ; source addresses should be unicast IP addresses multicast-addresses = IPaddresses ; these should be multicast IP addresses IPaddresses = (IPaddress / IPaddress-range) *("," (IPaddress / IPaddress-range)) IPaddress-range = IPaddress "-" IPaddress ; lowest and highest value of the IP address range IPaddress = IPv4address / IPv6address BCServiceId is defined in clause Z.2.1 (ABNF notation). BCPackageId is the service package ID string. IPv4 address and IPv6 address are specified in RFC 3261 [62], clause 25. NOTE: An essential correction to the ABNF of IPv6address is proposed in [11]. Implementers are advised to follow that guideline. The following are examples of the SDP attribute for BC service package: a=bc_service_package:P25-News-Sports a=bc_service_package:P25-News-Sports[mult_list:[]225.10.3.0[CCTV-5-Sports]] a=bc_service_package:P25-News-Sports[mult_list:[src_list:192.168.10.1]225.10.3.0[CCTV-5-Sports]] a=bc_service_package:P25-News-Sports[mult_list:[src_list:192.168.10.1-192.168.10.255]225.10.3.0- 225.10.4.255,FF02::2-FF02::8[CCTV-5- Sports]/[src_list:192.168.11.1,2001:cdba::3257:9652]FF02::10[CCTV-9- News]/[src_list:192.168.11.2]FF02::13[CCTV-8-News]/[]FF02::14[CCTV-6-Sports]] As seen in this notation the multi_list parameter can contain one or more source_unit parameters with multicast addresses that can be separated with either "," or "-". When they are separated with "-" it means that it is a range of addresses. In addition there can optionally be a list of source addresses within the source unit parameter which is applicable for all the multicast addresses within the source unit parameter. Z.2.3 SDP attributes for BC Program The SDP attribute a=bc_program is used to signal the BC program ID. The use of this attribute is specified in clauses 5.1.3 and 5.3.1. The Augmented Backus-Naur Form [61] specification of this SDP attribute is as follows: bc-program-field = "a=" bc-program-attribute CRLF bc-program-attribute = "bc_program" ":" BCprogramId BCprogramId = *16(ALPHA / DIGIT / "-"); Zero up to 16 letters, digits or dashes. The following is an example of the SDP attribute for BC program identifier. • a=bc_program:USA-Movie-Superman ETSI ETSI TS 183 063 V3.6.1 (2014-08) 226 Annex ZA (normative): Definition of Info Packages This annex defines the Info packages required in support of IPTV. ZA.1 Playlist Info Package The Playlist Info Package is used to send a list of network-owned content to any application that requires it using SIP INFO requests. The content is transparent to the end user in the sense that the user cannot perform any trick-mode operations on any content in the playlist. ZA.1.1 Overall General This clause contains the information required for the IANA registration of an Info Package. ZA.1.2 Overall Description Playlist are normally sent by a network-owned control server to a streaming server during an established session with the streaming server. The playlist includes a list of content allowing the streaming server to stream the content to an end-user according to the indicated time per content. The Playlist Info Package is used to transport the necessary information regarding the content to be streamed to the end-user. The Playlist Info Package is used to transfer a single list at any time. As such, only one list is transported in a single SIP INFO request. The list can include multiple contents. The Playlist Info Package is defined for any multimedia application that incorporates content streaming. Any application, where sending a playlist using the SIP INFO method is required, can use the Playlist Info Package. ZA.1.3 Applicability The Info Package mechanism for transporting a list of content has been chosen since this is a service that some networks may offer, and as such it is optional. The mechanism also allows the list of content to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog. This is especially important since the playlist is only pertinent to the sessioZA. ZA.1.4 Info Package Name The name of the content bookmark Info Package is: Playlist. ZA.1.5 Info Package Parameters No parameters are defined for the Playlist Info Package. ZA.1.6 SIP Option Tags No SIP option tags are defined for the Playlist Info Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 227 ZA.1.7 INFO Message Body Parts ZA.1.7.1 General The playlist sent as part of the message body of the SIP INFO request. This clause defines the information and syntax associated with the message body part used for transporting the play list. ZA.1.7.2 SIP Content-Type header field value The value of the SIP Content-Type header field associated with the Playlist Info Package message body is: application/vnd.etsi.playlist+xml. ZA.1.7.3 SIP Content-Disposition header field value The value of the SIP Content-Disposition header field associated with the Playlist Info Package message body is: Info- Package. ZA.1.7.4 Message body syntax The syntax of the Playlist Info Package message body is based on the rules defined in clause 5.3.9.1. ZA.1.8 Info Package Usage Restrictions No usage restrictions are defined for the Playlist Info Package. ZA.1.9 Rate of INFO Requests No maximum rate or minimum rate is defined for sending INFO requests associated with the Playlist Info Package. When Playlist requests are generated, the package does not provide a feedback mechanism to indicate to the sender that the rate of Playlist generation is too slow or fast. However applications in the network can control the rate of generation from users if they so desire. ZA.1.10 Info Package Security Considerations No additional security mechanism is defined for the Playlist Info Package. The security of the Playlist Info Package is based on the generic security mechanism provided for the underlying SIP signalling. ZA.1.11 Implementation Details and Examples Examples of the Playlist Info Package usage can be found in clause 5.3.9. ZA.2 Restricted-Trickplay-Policies Info Package The Restricted-Trickplay-Policies Info Package is used to send to a streaming server or an end-user streaming application a list of policies regarding trickplay restrictions on a streamed content that a user cannot perform using SIP INFO requests. ZA.2.1 Overall General This clause contains the information required for the IANA registration of an Info Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 228 ZA.2.2 Overall Description Restricted-Trickplay-Policies Playlist is normally sent by a control server to a streaming server or an end-user streaming application during an established session with the streaming server. This allows the server to enforce polices in regard trick plays that could not be performed over some segment of the content while the content is being streamed. This is useful if certain content segments such as ads should not be skipped as an example. The Restricted-Trickplay-Policies Info Package is used to transport the necessary information regarding those policies. The Restricted-Trickplay-Policies Info Package is used to transfer a single list at any time. As such, only one list is transported in a single SIP INFO request. The list can include multiple policies. The Restricted-Trickplay-Policies Info Package is defined for any multimedia application that incorporates content streaming and that wishes to impose restrictions on trickplays while streaming the content. Any application, where sending restricted trickplay policies using the SIP INFO method is required, can use the Restricted-Trickplay-Policies Info Package. ZA.2.3 Applicability The Info Package mechanism for transporting a list of Restricted trickplay policies has been chosen since this is a service that some networks may offer, and as such it is optional. The mechanism also allows the list of policies to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog. This is especially important since the policies are only pertinent to the session and the content streamed thereiZA. ZA.2.4 Info Package Name The name of the Info Package is: Restricted-Trickplay-Policies. ZA.2.5 Info Package Parameters No parameters are defined for the Restricted-Trickplay-Policies Info Package. ZA.2.6 SIP Option Tags No SIP option tags are defined for the Restricted-Trickplay-Policies Info Package. ZA.2.7 INFO Message Body Parts ZA.2.7.1 General The trickplay restricted policies are sent as part of the message body of the SIP INFO request. This clause defines the information and syntax associated with the message body part used for transporting the policies. ZA.2.7.2 SIP Content-Type header field value The value of the SIP Content-Type header field associated with the Restricted-Trickplay-Policies Info Package message body is: "application/vnd.etsi.iptvrestrictedtrickplay+xml". ZA.2.7.3 SIP Content-Disposition header field value The value of the SIP Content-Disposition header field associated with the Restricted-Trickplay-Policies Info Package message body is: Info-Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 229 ZA.2.7.4 Message body syntax The syntax of the Restricted-Trickplay-Policies Info Package message body is based on the rules defined in clause 5.3.7. ZA.2.8 Info Package Usage Restrictions No usage restrictions are defined for the Restricted-Trickplay-Policies Info Package. ZA.2.9 Rate of INFO Requests No maximum rate or minimum rate is defined for sending INFO requests associated with the Restricted-Trickplay- Policies Info Package. ZA.2.10 Info Package Security Considerations No additional security mechanism is defined for the Restricted-Trickplay-Policies Info Package. The security of the Restricted-Trickplay-Policies Info Package is based on the generic security mechanism provided for the underlying SIP signalling. ZA.2.11 Implementation Details and Examples Examples of the Restricted-Trickplay-Policies Info Package usage can be found in clauses 5.3.7 and 5.4.6. ZA.3 IPTV-Content-Marker Info Package The IPTV-Content-Marker Info Package is used to send a content bookmark to any application that requires it using SIP INFO requests. ZA.3.1 Overall General This clause contains the information required for the IANA registration of an Info Package. ZA.3.2 Overall Description IPTV Content Markers are normally sent by a user while watching content when a user desires to store information regarding a position in time in the streamed content that he wants to locate later when viewing the same content. The bookmarked position allows the user to start viewing from the bookmarked positioZA. The IPTV-Content-Marker Info Package is used to transport the necessary information regarding that point in time for storage in the network. Information regarding the stored content bookmark can be later retrieved by the user. The IPTV-Content-Marker Info Package is used to transfer a single content bookmark at any time. As such, only one content bookmark is transported in a single SIP INFO request. The IPTV-Content-Marker Info Package is defined for any multimedia application that incorporates content streaming. Any application, where sending content bookmark information using the SIP INFO method is required, can use the IPTV-Content-Marker Info Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 230 ZA.3.3 Applicability The Info Package mechanism for transporting content bookmarks has been chosen since this is a service that some networks may offer, and as such it is optional. Also networks that offer the service may impose a limit on the number of content bookmarks per subscriber to be stored in the network. As such, the network would restrict users who have exceeded their quota from sending any more bookmarks to it. Finally, the mechanism also allows content bookmarks to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog. ZA.3.4 Info Package Name The name of the content bookmark Info Package is: IPTV-Content-Marker. ZA.3.5 Info Package Parameters No parameters are defined for the IPTV-Content-Marker Info Package. ZA.3.6 SIP Option Tags No SIP option tags are defined for the IPTV-Content-Marker Info Package. ZA.3.7 INFO Message Body Parts ZA.3.7.1 General The Content bookmarks are sent as part of the message body of the SIP INFO request. This clause defines the information and syntax associated with the message body part used for transporting the content bookmarks. ZA.3.7.2 SIP Content-Type header field value The value of the SIP Content-Type header field associated with the IPTV-Content-Marker Info Package message body is: "application/vnd.etsi.iptvcontentmarker+xml". ZA.3.7.3 SIP Content-Disposition header field value The value of the SIP Content-Disposition header field associated with the IPTV-Content-Marker Info Package message body is: Info-Package. ZA.3.7.4 Message body syntax The syntax of the IPTV-Content-Marker Info Package message body is based on the rules defined in clauses 5.1.14 and 5.3.13. ZA.3.8 Info Package Usage Restrictions No usage restrictions are defined for the IPTV-Content-Marker Info Package. ZA.3.9 Rate of INFO Requests No maximum rate or minimum rate is defined for sending INFO requests associated with the IPTV-Content-Marker Info Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 231 When IPTV-Content-Marker requests are generated by users, the package does not provide a feedback mechanism to indicate to the sender that the rate of IPTV-Content-Marker generation is too slow or fast. However applications in the network can control the rate of generation from users if they so desire. ZA.3.10 Info Package Security Considerations No additional security mechanism is defined for the IPTV-Content-Marker Info Package. The security of the IPTV-Content-Marker Info Package is based on the generic security mechanism provided for the underlying SIP signalling. ZA.3.11 Implementation Details and Examples Examples of the IPTV-Content-Marker Info Package usage can be found in clause 5.1.14. ZA.4 Event-Notification Info Package The Event-Notification Info Package is used to send to an application unsolicited application events that the applications is required to act on using SIP INFO requests. ZA.4.1 Overall General This clause contains the information required for the IANA registration of an Info Package. ZA.4.2 Overall Description Notifications about events are normally sent when an action is required by an application such as inserting an ad to a user who has paused a streamed content. In these cases, the reason for the event is signalled in the event itself so the application knows what it needs to do. The Event-Notification Info Package is used to transfer a single event at any time. As such, only one event is transported in a single SIP INFO request. The Event-Notification Info Package is defined for any multimedia application that incorporates content streaming. Any application, where sending events using the SIP INFO method is required, can use the Event-Notification Info Package. ZA.4.3 Applicability The Info Package mechanism for transporting application events has been chosen since this is a service that not all applications may support, and as such it is optional. Finally, the mechanism also allows application events to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog. ZA.4.4 Info Package Name The name of the event notification Info Package is: Event-Notification. ZA.4.5 Info Package Parameters No parameters are defined for the Event-Notification Info Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 232 ZA.4.6 SIP Option Tags No SIP option tags are defined for the Event-Notification Info Package. ZA.4.7 INFO Message Body Parts ZA.4.7.1 General Notification events are sent as part of the message body of the SIP INFO request. This clause defines the information and syntax associated with the message body part used for transporting the notification events. ZA.4.7.2 SIP Content-Type header field value The value of the SIP Content-Type header field associated with the Event-Notification Info Package message body is: " application/vnd.etsi.iptvnotification+xml ". ZA.4.7.3 SIP Content-Disposition header field value The value of the SIP Content-Disposition header field associated with the Event-Notification Info Package message body is: Info-Package. ZA.4.7.4 Message body syntax The syntax of the Event-Notification Info Package message body is based on the rules defined in clause 5.1.13. ZA.4.8 Info Package Usage Restrictions No usage restrictions are defined for the Event-Notification Info Package. ZA.4.9 Rate of INFO Requests No maximum rate or minimum rate is defined for sending INFO requests associated with the Event-Notification Info Package. Given that these events are typically generated by network servers, the network can control the rate itself. ZA.4.10 Info Package Security Considerations No additional security mechanism is defined for the Event-Notification Info Package. The security of the Event-Notification Info Package is based on the generic security mechanism provided for the underlying SIP signalling. ZA.4.11 Implementation Details and Examples Examples of the Event-Notification Info Package usage can be found in clause 5.1.13. ZA.5 CoD-Playlist Info Package The CoD-Playlist Info Package is used to send to a streaming server a list of content held by the server using SIP INFO requests. This allows the server to sequentially stream the list of content to an end user. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 233 ZA.5.1 Overall General This clause contains the information required for the IANA registration of an Info Package. ZA.5.2 Overall Description CoD-Playlist is normally sent by a user to a streaming server once a session is established with the server. The CoD playlist includes a list of content allowing the streaming server to stream the content to an end-user sequentially. The user can equally switch streaming between the different contents in the playlist. CoD play lists are typically created and updated by the end-user. The CoD-Playlist Info Package is used to transfer a single list at any time. As such, only one list is transported in a single SIP INFO request. The list can include multiple contents. The CoD-Playlist Info Package is defined for any multimedia application that incorporates content streaming. Any application, where sending a playlist using the SIP INFO method is required, can use the Playlist Info Package. ZA.5.3 Applicability The Info Package mechanism for transporting the CoD list of content has been chosen since this is a service that some networks may offer, and as such it is optional. The mechanism also allows the list of content to be sent inside an existing dialog, using the same signalling path as other SIP messages within the dialog, rather than having to establish a separate dialog. This is especially important since the playlist is only pertinent to the session ZA. ZA.5.4 Info Package Name The name of the content bookmark Info Package is: CoD-Playlist. ZA.5.5 Info Package Parameters No parameters are defined for the CoD-Playlist Info Package. ZA.5.6 SIP Option Tags No SIP option tags are defined for the CoD-Playlist Info Package. ZA.5.7 INFO Message Body Parts ZA.5.7.1 General The CoD playlist is sent as part of the message body of the SIP INFO request. This clause defines the information and syntax associated with the message body part used for transporting the CoD-Playlist. ZA.5.7.2 SIP Content-Type header field value The value of the SIP Content-Type header field associated with the CoD-Playlist Info Package message body is: "application/vnd.etsi.iptvcontentswitch+xml". ZA.5.7.3 SIP Content-Disposition header field value The value of the SIP Content-Disposition header field associated with the CoD-Playlist Info Package message body is: Info-Package. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 234 ZA.5.7.4 Message body syntax The syntax of the CoD-Playlist Info Package message body is based on the rules defined in clause 5.3.15.2. ZA.5.8 Info Package Usage Restrictions No usage restrictions are defined for the CoD-Playlist Info Package. ZA.5.9 Rate of INFO Requests No maximum rate or minimum rate is defined for sending INFO requests associated with the CoD-Playlist Info Package. ZA.5.10 Info Package Security Considerations No additional security mechanism is defined for the CoD-Playlist Info Package. The security of the CoD-Playlist Info Package is based on the generic security mechanism provided for the underlying SIP signalling. ZA.5.11 Implementation Details and Examples Examples of the CoD-Playlist Info Package usage can be found in clause 5.3.9. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 235 Annex ZZ (informative): Change history Date WG Doc. CR CRRev CAT Title/Comment Current Version New Version 19-05-09 20bTD115r1 001 D Outline for IPTV Stage3 Procedures 2.4.1 3.0.0 11-06-09 21WTD129r1 002 D WI3204_Editorial_Corrections 3.0.0 3.0.1 11-06-09 21WTD210r5 003 B CPVR Service procedures 3.0.0 3.0.1 11-06-09 21WTD211r2 004 B WI3204_PPV_Service 3.0.0 3.0.1 11-06-09 21WTD212r3 005 B WI3204_Procedures_of_UGC_Service 3.0.0 3.0.1 CRs001 to 005 TB approved 3.0.1 3.1.0 31-08-09 21bTD112r1 006 B Restricted Trick Play service procedures 3.1.0 3.1.1 31-08-09 21bTD103r2 007 B SCF Initiate Sessions 3.1.0 3.1.1 31-08-09 21bTD114r2 008 B Procedures_for_Service_Initiation_by_Remote UE 3.1.0 3.1.1 31-08-09 21bTD109r3 009 B Playlist Procedures 3.1.0 3.1.1 31-08-09 21bTD110r5 010 B Notification service 3.1.0 3.1.1 31-08-09 21bTD104r1 011 B Personalized Service Composition 3.1.0 3.1.1 31-08-09 21bTD115r6 012 B Procedure_for_Retrieving_User's_IPTV_Service_ Access 3.1.0 3.1.1 31-08-09 21bTD099r4 013 B Applicability_of_Synchronization 3.1.0 3.1.1 31-08-09 21bTD113r6 014 B Protocol_Implementation_for_PCh_Service 3.1.0 3.1.1 31-08-09 21bTD196r4 015 B Content Inserton At UE Side 3.1.0 3.1.1 31-08-09 21bTD154r5 016 B Procedures for IPTV Content Marker 3.1.0 3.1.1 31-08-09 21bTD111r3 017 B Ad_Service_Procedures-TISPAN_Option 3.1.0 3.1.1 01-10-09 22WTD196r1 018 A XML Corrections 3.1.1 3.1.2 01-10-09 22WTD040r1 019 B Procedures for UE watching 3.1.1 3.1.2 01-10-09 22WTD077r1 020 B XML Sheama definition for PCh Procedures 3.1.1 3.1.2 01-10-09 22WTD074r3 021 B Procedures_for_CPVR_Recording_Session 3.1.1 3.1.2 01-10-09 22WTD136r3 022 B Introduction of Instance Identifier 3.1.1 3.1.2 01-10-09 22WTD038r2 023 B RTCP_for_Synchronization 3.1.1 3.1.2 01-10-09 22WTD036r4 024 B Synchronization_Example_Signalling_Flows 3.1.1 3.1.2 01-10-09 22WTD037r3 025 B Synchronization_Session_Setup 3.1.1 3.1.2 01-10-09 22WTD150r2 026 B Introduction of TV Anytime Phase 2 as SSF technology 3.1.1 3.1.2 01-10-09 22WTD041r3 027 B Presence_for_Service_State_Data 3.1.1 3.1.2 01-10-09 22WTD076r4 028 B Content Switch within the COD playlist 3.1.1 3.1.2 01-10-09 22WTD078r3 029 B XML_Schema_Definition_for_UGC_Procedures 3.1.1 3.1.2 01-10-09 22WTD151r2 030 B Playlist proceduires 3.1.1 3.1.2 01-10-09 22WTD069r4 031 B Improvement on the XML schema for IPTV notification service 3.1.1 3.1.2 01-10-09 22WTD138r5 032 B UE Notification Procedures 3.1.1 3.1.2 01-10-09 22WTD137r2 033 B Mandating ICSI for IPTV 3.1.1 3.1.2 01-10-09 22WTD070r4 034 B Content Insertion at MF Side 3.1.1 3.1.2 01-10-09 22WTD152r2 035 B IPTV Content Marker Procedures 3.1.1 3.1.2 01-10-09 22WTD183r3 036 C Move TAI procedures 3.1.1 3.1.2 CRs 006 to 036 TB approved at TISPAN#22 3.1.2 3.2.0 11-11-09 22bTD074r1 037 D Editorial modifications 3.2.0 3.2.1 11-11-09 22bTD068r1 038 B Content Recommendation 3.2.0 3.2.1 11-11-09 22bTD150r1 039 F Conplience to SIP drafting Rules 3.2.0 3.2.1 11-11-09 22bTD069r1 040 C Improve the PCh Schema 3.2.0 3.2.1 11-11-09 22bTD089r3 041 B Control of Content Reporting 3.2.0 3.2.1 11-11-09 22bTD073r4 042 B UE initiated Content Download 3.2.0 3.2.1 11-11-09 22bTD072r2 043 B TAI at MF Side 3.2.0 3.2.1 11-11-09 22bTD051r1 044 F Correction_Sync_for_RTSP_Method_2 3.2.0 3.2.1 11-11-09 22bTD047r1 045 B Synchronisation_Clients_in_the_Transport_Netwo rk 3.2.0 3.2.1 11-11-09 22bTD048r1 046 B Direct_Synchronisation_between_UEs 3.2.0 3.2.1 11-11-09 22bTD050r1 047 B RTCP_XR_Block_Type_for_Synchronization 3.2.0 3.2.1 11-11-09 22bTD071r5 048 B Resolve_Editors_Note_for_Content_Switch 3.2.0 3.2.1 11-11-09 22bTD136r2 049 B Completion of TV Anytime Phase 2 parts 3.2.0 3.2.1 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 236 Date WG Doc. CR CRRev CAT Title/Comment Current Version New Version 11-11-09 22bTD187r4 050 B Procedure for Preview Service 3.2.0 3.2.1 12-25-09 23WTD056r1 051 B Direct Synchronization between UEs 3.2.1 3.2.2 12-25-09 23WTD057r1 052 B Synchronization clients for Transcoders 3.2.1 3.2.2 12-25-09 23WTD058r1 053 B Annex W RTCP Block Type 3.2.1 3.2.2 12-25-09 23WTD073r1 054 D Delete ther Editor's Notes for UGC Upload 3.2.1 3.2.2 12-25-09 23WTD079r1 055 B Resolving Editor's notes for PPV 3.2.1 3.2.2 12-25-09 23WTD082r1 056 B Resolving Editor's notes for Content switch 3.2.1 3.2.2 12-25-09 23WTD083r1 057 B Remove Annex ZZZ 3.2.1 3.2.2 12-25-09 23WTD140r1 058 B XML Scheme for the IPTV Profile 3.2.1 3.2.2 12-25-09 23WTD078r1 059 B EN_handling for Preview 3.2.1 3.2.2 12-25-09 23WTD077r4 060 B EN Handling for PCh 3.2.1 3.2.2 12-25-09 23WTD072r3 061 B Binding_Request_and_Response_for_UGC_Decl aration 3.2.1 3.2.2 12-25-09 23WTD074r2 062 B Disposal of Editor's Notes of Remote Service Initiation 3.2.1 3.2.2 12-25-09 23WTD075r3 063 B Disposal of Editor's Notes for UGC service 3.2.1 3.2.2 12-25-09 23WTD080r2 064 B Resolving Editor's Notes for presence 3.2.1 3.2.2 12-25-09 23WTD081r2 065 B Resolving Editor's Notes for Content Download 3.2.1 3.2.2 12-25-09 23WTD076r4 066 B EN_Handling for Ad 3.2.1 3.2.2 CRs 037 to 066 TB approved at TISPAN#23 3.2.2 3.3.0 02-17-10 TISPAN03(10) 0012r1 067 B Removal of editor's notes on Sync 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0014r1 068 B Synchronization scalability 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0015r1 069 B Distribution_of_Synchronisation_Client_Functional ities 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0023r2 070 B Clarification_and_Resolve_Editor's_Note_for_CP VR_Service 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0030r1 071 B PCh_Name_Change 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0031r4 072 B PCh_Overlap Handling 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0032r3 073 B PCh_Initialization 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0033r2 074 B Playlist handling 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0034r3 075 B Restricted Trick Play 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0037r4 076 B Access Control in Content Marker procedure 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0047r3 077 B IPTV Security 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0048r2 078 B Ss' Reference Point 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0049r2 079 B Signalling Flows 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0017r1 080 B Content_Insertion_at_the_UE 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0025r2 081 B Session_Transfer_Push_Mode 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0016r1 082 B Personalized_Service_Composition_for_Content_ Insertion 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0026r2 083 B Content_Insertion_MFside 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0027r1 084 B Content_Insertion_UEside 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0028r1 085 B Content_Insertion_Overloading_Invite 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0038r4 086 B Some Modifications about IPTV Content Marker 3.3.0 3.3.1 02-17-10 TISPAN03(10) 0013r3 087 B Clarification_on_Optionality_of_Functionalities 3.3.0 3.3.1 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 237 Date WG Doc. CR CRRev CAT Title/Comment Current Version New Version 04-27-10 TISPAN03(10) 0084r2 088 C WI-03204 Changes to the Output draft at version .3.1 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0085r3 089 B WI-03204 Example of session Transfer 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0087r1 090 B WI-03204 Inconsistencies in Content Switch Specifications 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0088r2 091 B WI-03204 Inconsistencies in Playlist Specifications 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0089r2 092 B WI-03204 PCh declaration 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0090r2 093 B WI-03204 Removal of Editor's note 5.1.4.2A 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0091r1 094 B WI-03204 Removal of Editor's note 5.3.12.2 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0092r2 095 B WI-03204 Removal of Editor's note 5.4.9.1.2 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0093r1 096 B WI-03204 SIP Instance Correction 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0094r1 097 B WI-03204 Support for GRUU 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0095r1 098 B WI-03204 Support For GRUU In Session Transfer Service 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0096r3 099 B WI-03204 Support For t=line in Network Time Shift 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0097r2 100 B WI-03204 using SIP Options in SCF initiated Session 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0100r1 101 C WI-03204 Resolution of Editor's notes 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0101r1 102 D WI-03204 Removal of SDES references 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0102r4 103 F WI-03204 Clarification of Content Insertion at UE 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0103r1 104 F WI-03204 review of TS 183 063 Draft Synchronization CR 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0140r1 105 F WI-03204 Non synchronization CR 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0104r1 106 C WI-03204 Definition of SDP Attribute Parameter for Sync 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0130r1 107 A WI-03204: Addressing Editor's Note 42 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0116r1 108 D WI-03204 Inter UE Session Transfer 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0117r1 109 C WI-03204 Content Marker Service 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0118r1 110 F WI-03204 BC Bookmark 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0125r2 111 F WI-03204 UE Profile (XML modifications) 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0126r1 112 B WI-03204 UE Profile (Content Protection) 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0099r3 113 F WI-03204_Improve_TAI_Clauses 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0113r3 114 B WI-03204 Bandwidth reservation for progressive download 3.3.1 3.3.2 04-27-10 TISPAN03(10) 0128r2 115 B WI-03204 FLUTE for multicast download 3.3.1 3.3.2 CRs 067 to 0115 TB approved at TISPAN#24 3.3.2 3.4.0 06-09-10 TISPAN03(10) 0190r1 116 F WI3204 tCodDeliveryStatus parameter in the Annex K 3.4.0 3.4.1 06-09-10 TISPAN03(10) 0191r1 117 F RTSP Playback Control parameters 3.4.0 3.4.1 06-09-10 TISPAN03(10) 0193r2 118 B WI 3204 - Inclusion of Compliance to SIP INFO framework 3.4.0 3.4.1 06-09-10 TISPAN03(10) 0197r1 119 B Enhancement to Notification Service 3.4.0 3.4.1 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 238 Date WG Doc. CR CRRev CAT Title/Comment Current Version New Version 06-09-10 TISPAN03(10) 0198r4 120 B Enhancements to RTSP ANNOUNCE For Media Events 3.4.0 3.4.1 06-09-10 TISPAN03(10) 0195r2 121 B Support For Content Switch 3.4.0 3.4.1 09-15-10 TISPAN03(10) 0211r2 122 F Rapporteur changes 3.4.1 3.4.2 09-15-10 TISPAN03(10) 0236r1 123 A New Normative Annex to replace draft- channabasappa-sipping-app-profile-type-03 3.4.1 3.4.2 09-15-10 TISPAN03(10) 0214r2 124 D IANA_specification_of_SDP_attributes 3.4.1 3.4.2 09-15-10 TISPAN03(10) 0235r1 125 B Info Packages 3.4.1 3.4.2 09-15-10 TISPAN03(10) 0237r1 126 B Generic Handling of Play lists, Cod Content lists and Personalized Channel 3.4.1 3.4.2 Some editorial refinements by Rapporteur 3.4.2 3.4.3 10-28-10 TISPAN03(10) 0246r2 127 D IANA Reference Corrections 3.4.3 3.4.4 10-28-10 TISPAN03(10) 0254r2 128 C XML_Corrections 3.4.3 3.4.4 10-28-10 TISPAN03(10) 0274r1 129 A Reference to Sipping config. v18 3.4.3 3.4.4 12-14- 2010 TISPAN03(10) 0 287r1 130 A Annex_Z_SDP_Correction 3.4.4 3.4.5 Publication 3.4.5 3.5.1 Make figure W.1 visible 3.5.1 3.5.2 23-06- 2014 NTECH(12)01 _015r1 131 E addition of an IETF reference for Annex W 3.5.2 3.5.3 Publication 3.5.3 3.6.1 ETSI ETSI TS 183 063 V3.6.1 (2014-08) 239 History Document history V2.1.0 June 2008 Publication V2.4.1 May 2009 Publication V2.4.2 June 2009 Publication V2.8.1 February 2011 Publication V3.5.1 February 2011 Publication V3.5.2 March 2011 Publication V3.6.1 August 2014 Publication
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
1 Scope
|
The present document specifies the stage three protocol description of the signalling interworking between ISDN DSS1 protocol and SIP based on the concatenation of ETSI TS 129 163 [1], ETSI TS 124 229 [5] with ETSI EN 300 899-1 [2]. The concatenation method describes only the SIP/ISDN parameter mapping without ISUP procedures. In addition direct inter-working not supported by this concatenation of these existing inter-working documents will be described.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
2 References
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 129 163 (V15.8.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 version 15.8.0 Release 15)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/129100_129199/129163/15.08.00_60/ts_129163v150800p.pdf. [2] ETSI EN 300 899-1 (V1.1.2): "Integrated Services Digital Network (ISDN);Signalling System No.7; Interworking between ISDN User Part (ISUP) version 2 and Digital Subscriber Signalling System No. One (DSS1); Part 1: Protocol specification [ITU-T Recommendation Q.699, modified]". [3] Void. [4] Void. [5] ETSI TS 124 229 (V15.8.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 15.8.0 Release 15)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/124200_124299/124229/15.08.00_60/ts_124229v150800p.pdf. [6] ETSI TS 124 607 (V15.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.607 version 15.0.0 Release 15)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/124600_124699/124607/15.00.00_60/ts_124607v150000p.pdf. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 9 [7] ETSI TS 124 608 (V15.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.608 version 15.0.0 Release 15)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/124600_124699/124608/15.00.00_60/ts_124608v150000p.pdf. [8] ETSI TS 124 604 (V15.1.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 version 15.1.0 Release 15)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/124600_124699/124604/15.01.00_60/ts_124604v150100p.pdf. [9] ETSI TS 124 605 (V14.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605 version 14.0.0 Release 14)". NOTE: Available at https://www.etsi.org/deliver/etsi_ts/124600_124699/124605/14.00.00_60/ts_124605v140000p.pdf. [10] ETSI TS 124 083 (V14.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 (3GPP TS 24.083 version 14.0.0 Release 14)". NOTE: Available https://www.etsi.org/deliver/etsi_ts/124000_124099/124083/14.00.00_60/ts_124083v140000p.pdf. [11] ETSI EN 300 052-1: "Integrated Services Digital Network (ISDN); Multiple Subscriber Number (MSN) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [12] ETSI EN 300 055-1: "Integrated Services Digital Network (ISDN); Terminal Portability (TP) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [13] ETSI EN 300 058-1: "Integrated Services Digital Network (ISDN); Call Waiting (CW) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [14] ETSI EN 300 061-1: "Integrated Services Digital Network (ISDN); Subaddressing (SUB) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [15] ETSI EN 300 064-1: "Integrated Services Digital Network (ISDN); Direct Dialling In (DDI) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [16] ETSI EN 300 092-1: "Integrated Services Digital Network (ISDN); Calling Line Identification Presentation (CLIP) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [17] ETSI EN 300 093-1: "Integrated Services Digital Network (ISDN); Calling Line Identification Restriction (CLIR) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [18] ETSI EN 300 097-1: "Integrated Services Digital Network (ISDN); Connected Line Identification Presentation (COLP) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". ETSI ETSI TS 183 036 V3.7.1 (2021-02) 10 [19] ETSI EN 300 098-1: "Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [20] ETSI EN 300 130-1: "Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [21] ETSI EN 300 138-1: "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [22] ETSI EN 300 141-1: "Integrated Services Digital Network (ISDN); Call Hold (HOLD) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [23] ETSI EN 300 185-1: "Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [24] ETSI EN 300 188-1: "Integrated Services Digital Network (ISDN); Three-Party (3PTY) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [25] ETSI EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [26] ETSI TS 183 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification". [27] Void. [28] Void. [29] ETSI EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. One (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]". [30] Void. [31] ETSI TS 183 047: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN IMS Supplementary Services; Advice Of Charge (AOC)". [32] ETSI TS 183 028: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Common Basic Communication procedures; Protocol specification". [33] Void. [34] ETSI EN 300 207-1: "Integrated Services Digital Network (ISDN); Diversion supplementary services; Digital Subscriber Signalling System No. One (DSS1); Part 1: Protocol specification". [35] ETSI EN 300 369-1: "Integrated Services Digital Network (ISDN); Explicit Call Transfer (ECT) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [36] ETSI TS 183 029: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification". [37] ETSI EN 300 182-1: "Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". ETSI ETSI TS 183 036 V3.7.1 (2021-02) 11 [38] ETSI EN 300 286-1: "Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [39] ETSI EN 300 359-1: "Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [40] ETSI EN 301 065-1: "Integrated Services Digital Network (ISDN); Completion of Calls on No Reply (CCNR) supplementary service; Digital Subscriber Signalling System No. One (DSS1) protocol; Part 1: Protocol specification". [41] Void. [42] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Stage 3 specification". [43] ETSI EN 301 798 (V1.1.1): "Services and Protocols for Advanced Networks (SPAN); Anonymous Call Rejection (ACR) Supplementary Service; Service description". [44] IETF RFC 4575 (2006): "A Session Initiation Protocol (SIP) Event Package for Conference State". [45] IETF RFC 7044: "An Extension to the Session Initiation Protocol (SIP) for Request History Information". [46] ETSI TS 183 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol Specification". [47] IETF RFC 3966: "The tel URI for Telephone Numbers". [48] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". [49] ETSI TS 183 023: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services". [50] IETF RFC 4916: "Connected Identity in the Session Initiation Protocol (SIP)". [51] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call". [52] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". [53] IETF RFC 3261: "SIP: Session Initiation Protocol". [54] Recommendation ITU-T Q.931: "ISDN user-network interface layer 3 specification for basic call control". [55] Recommendation ITU-T Q.939: "Typical DSS 1 service indicator codings for ISDN telecommunications services". [56] Recommendation ITU-T T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". [57] ETSI EN 300 745-1 (V1.2.4): "Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification". [58] ETSI TS 183 015: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN) NGN Signalling Control Protocol Communication Waiting (CW) PSTN/ISDN simulation services". ETSI ETSI TS 183 036 V3.7.1 (2021-02) 12 [59] ETSI TS 124 642: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.642 Release 8)". [60] Recommendation ITU-T G.711: "Pulse code modulation (PCM) of voice frequencies". [61] Recommendation ITU-T Q.850: "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". [62] ETSI TS 124 654 (V15.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification (3GPP TS 24.654 version 15.0.0 Release 15)". [63] IETF RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)".
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 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] draft-johnston-sipping-cc-uui-02: "Transporting User to User Information for Call Centers using SIP". [i.2] Recommendation ITU-T Q.763: "Signalling System No. 7 - ISDN User Part formats and codes". [i.3] Recommendation ITU-T H.221: "Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices". [i.4] Recommendation ITU-T G.725: "System aspects for the use of the 7 kHz audio codec within 64 kbit/s". [i.5] Recommendation ITU-T G.722: "7 kHz audio-coding within 64 kbit/s".. [i.6] Recommendation ITU-T E.164 (2010-11): "The international public telecommunication numbering plan". [i.7] Recommendation ITU-T E.163: "Numbering plan for the international telephone service". NOTE: Former E.163/Q.11 bis (1984). The content of this Recommendation was incorporated in ITU-T E.164 (1991).
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
3 Definition of terms, symbols and abbreviations
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
3.1 Terms
|
For the purposes of the present document, the following terms apply: en bloc receiving: procedure, used in call establishment of an incoming call, to enable the network to send called party number digits to the user in a single message NOTE: See ETSI EN 300 403-1 [29]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 13 en bloc sending: procedure, used in call establishment of an outgoing call, to enable the user to send called party number digits to the network in a single message NOTE: See ETSI EN 300 403-1 [29]. incoming AGCF/VGW: physical entity, which can be combined with a SIP UNI or NNI, terminates incoming calls using SIP protocol and originates outgoing calls using the DSS1 protocol outgoing AGCF/VGW: physical entity, which can be combined with an ISDN access device, terminates incoming calls using DSS1 and originates outgoing calls using the SIP protocol overlap receiving: procedure, used in call establishment of an incoming call, to enable the network to send called party number digits to the user in successive messages, as and when they are made available from the remote network NOTE: See ETSI EN 300 403-1 [29]. overlap sending: procedure, used in call establishment of an outgoing call, to enable the user to send called party number digits to the network in successive messages, as and when they are made available by the user NOTE: See ETSI EN 300 403-1 [29]. SIP Phone 3,1 KHz: native SIP endpoint that supports the G.711 [60] codec NOTE: Such an endpoint may inter-work with an ISDN user in the IMS/PSTN for the 3,1 KHz bearer service due to both endpoints commonly supporting the G.711 [60] codec. SIP Phone 7 KHz: native SIP endpoint that supports the G.722 codec NOTE 1: However, such an endpoint may not inter-work with an |ISDN user in the IMS/PSTN for the 7 KHz bearer service as the VGW/AGCF/MGCF advertises the CLEARMODE codec (which enables a H.221 [i.3] structure to be carried transparently - as described in Recommendation ITU-T G.725 [i.4]). NOTE 2: It is assumed that the CLEARMODE codec is not understood by the SIP endpoint. user: DSS1 protocol entity at the user side of the user-network interface NOTE: See ETSI EN 300 403-1 [29].
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
3.2 Symbols
|
Void.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement ACR Anonymous Call Rejection AFI Authority and Format Identifier AGCF Access Gateway Control Function AGW Access GateWay AOC Advice Of Charge AOC-D Advice Of Charge During the call AOC-E Advice Of Charge at the End of the call AOC-S Advice Of Charge at call Set-up time AS Application Server ATP Access Transport ATS advance telephony server BC Bearer Capability information element BCD Binary Coded Decimal BCI Backward Call Indicator BRI Basic Rate Interface BS Busy Subscriber ETSI ETSI TS 183 036 V3.7.1 (2021-02) 14 CCBS Call Completion to Busy Subscriber CCNR Call Completion on No Reply CD Call Deflection CDIV Communication Diverting CFB Call Forwarding Busy CFNR Call Forwarding on No Reply CFU Call Forwarding Unconditional CLI Calling Line Identification CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction COLP Connected Line identification Presentation COLR Connected Line identification Restriction CONF supplementary service Conference CSCF Call Session Control Function CUG Closed User Group CW Call Waiting DDI Direct Dialling In DISC Disconnect DSS Digital Subscriber System DSS1 Digital Subscriber Signalling System No. one ECT Explicit Communication Transfer FCI Forward Call Indicator HLC High Layer Compatibility information element HTTP HyperText Transfer Protocol ID IDentification IE Information Element IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network ISUP ISDN User Part IWF InterWorking Function LLC Low Layer Capability LN Local Number MCID Malicious Communication IDentification MGCF Media Gateway Control Function MIME Multipurpose Internet Mail Extensions MRFC Multimedia Resource Function Controller MSN Multiple Subscriber Number MWI Message Waiting Indication NDC National Destination Code NGN Next Generation Network NPI Network Protcol Indicator NR Not Reply NSAP Network Service Access Point OIP Originating Identification Presentation OIR Originating Identification Restriction PBX Private Branch Exchange PCMA Puls-Code-Modulation A law PCMU Puls-Code-Modulation µ law PES PSTN/ISDN Emulation Subsystem PI Progress Indicator PRI Primary Rate Interface PROC Proceeding PSTN Public Switched Telephone Network PT Pay load Type ROSE Remote Operations Service Element S-CSCF Server-Call Session Control Function SDP Session Description Protocol SIP Session Initiation Protocol SN Subscriber Number SUB SUBaddressing TDM Time Division Multiplex ETSI ETSI TS 183 036 V3.7.1 (2021-02) 15 TIP Terminating Identification Presentation TIR Terminating Identification Restriction TON Type Of Number TP Test Purpose UE User Equipment URI Universal Resource Identifier UUS User to User Service VGW Voice over IP GateWay XCAP eXtensible Markup Language (XML) Configuration Access Protocol XML eXtensible Markup Language
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
4 General
|
The present document describes the requirements for implementing commonly deployed Integrated Service Data Network (ISDN) basic call and supplementary services using the IP Multimedia Subsystem (IMS) and IMS-based PSTN/ISDN Emulation Subsystem (PES) architecture: • ISDN terminals are connected to Voice over IP GateWay (VGW) or access gateways Access Gateway Control Function (AGCF) using Basic Rate Interface (BRI) or Primary Rate Interface (PRI) interfaces. The protocol running on the interfaces between these gateways and the PES is the Session Initiation Protocol (SIP). The actual service logic resides in the Application Server and is outside the scope of the present document. The present document focuses on the interactions between the InterWorking Function (IWF) [42]. Full support of supplementary services may be realized by exchanging service information between peer SIP signalling entities via SIP signalling. The Digital Subscriber Signalling System No. one (DSS1) information necessary to support each individual service is specified by the corresponding ETSI or ITU-T supplementary service specification; see table 4-1. For the management of several supplementary services (e.g. activation or deactivation of a service), two possibilities exist. The usage of the Ut interface allows the transport of the content of the DSS1 Facility in the PSTN XML instances as specified in the relevant simulation service to the PSTN/ISDN simulation services Extensible Markup Language (XML) Configuration Access Protocol (XCAP) server to manipulate the service. In addition, the usage of an empty INVITE to carry service code sequences is also applicable to manipulate the supplementary service. The applicability is a network provider option. The management of supplementary services in the PSTN/ISDN Emulation Subsystem (PES) is out of scope of the present document. In case of the interworking for IMS simulation the mapping of PSTN XML Attachment parameters (ProgressIndicator HighLayerCapability, LowLayerCapability, BearerCapability, Display; SendingComplete) and additional P-Early media header are a network provider option, in the IMS based PES they are mandatory. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 16 Table 4-1: Supplementary Service References Supplementary Service ETSI Reference Calling Line Identification Presentation (CLIP) [16] Calling Line Identification Restriction (CLIR) [17] Connected Line Identification Presentation (COLP) [18] Connected Line Identification Restriction (COLR) [19] Terminal Portability (TP) [12] User-to-User Signalling (UUS) [38] Closed User Group (CUG) [21], [62] Subaddressing (SUB) [14] Malicious Call Identification (MCID) [20] Conference Call (CONF) [23] Explicit Call Transfer (ECT) [35] Call Forwarding Busy (CFB) [34] Call Forwarding No Reply (CFNR) [34] Call Forwarding Unconditional (CFU) [34] Call Deflection (CD) [34] Call Hold (HOLD) [22] Call Waiting (CW) [13] Completion of Calls to Busy Subscriber (CCBS) [39] Three-Party (3PTY) [24] Completion of Calls on No Reply (CCNR) [40] Anonymous Communication Rejection (ACR) [43] Multiple Subscriber Numbering (MSN) [11] Direct Dialling In (DDI) [15] Advice of Charge (AOC) [37] Message Waiting Indication (MWI) [57]
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5 Interworking for IMS simulation/emulation services
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1 Basic Call
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1 Actions at the Outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.1 Sending of the Initial INVITE
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.1.0 Interworking of DSS1 SETUP or INFO into SIP INVITE request
|
After initiating the normal incoming call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the originating VGW/AGCF shall send the initial INVITE. As a network option, the originating VGW/AGCF may send INVITE requests without determining the end of address signalling. The end of address signalling shall be determined by the earlier of the following criteria: a) by receipt of a "#" character as a sending complete indication or sending complete information element; b) optional by receipt of the maximum number of digits used in the national numbering plan; or c) optional by analysis of the called party number to indicate that a sufficient number of digits has been received to route the call to the called party. Table 5.1.1.1.0-1: Mapping of sending complete info element SETUP/INFO→ INVITE/XXX→ Information element PSTN XML attachment sending complete sendingCompleteIndication ETSI ETSI TS 183 036 V3.7.1 (2021-02) 17
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.1.1 En-bloc sending according to ETSI EN 300 403-1, clause 5.1.1
|
If en-bloc sending is used, the SETUP message contains the complete called number information. The called party number information is included in the called party number information element possibly completed by the called party subaddress information element. The network shall send a CALL PROCEEDING message to the user. This acknowledges the SETUP message and indicates that the call is being processed and that no further address information is expected. The AGCF/VGW can contain a configurable digit map which is used to analyse the called party information element contents received in the called party number information element. Among other purposes, this digit map can be used to identify the required number of digits to be entered for a particular digit sequence for a particular service. The procedures for digit maps are described within ETSI TS 183 043 [42], clause 7.3.1.3.1.1. Even in the absence of a digit map, it is appropriate for the AGCF/VGW to collect dialled digits. The AGCF/VGW shall contain a configurable parameter indicating the minimum number of digits expected in the sequence of called party number information elements before a Request-URI is constructed and an INVITE request sent. The minimum number could be zero. If this option does not apply, the VGW has to assume overlap sending. If en-bloc sending is used, the SETUP message may contain the sending complete indication (IE the sending complete information element) (see ETSI EN 300 403-1 [29]). It is mandatory for the network to recognize the sending complete information element.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.1.2 Bearer capability mapping
|
The "information transfer capability" code point of the bearer capability information element in the SETUP message shall be mapped to the SDP in SIP according to table 5.1.1.1.2-1. Table 5.1.1.1.2-1: Coding of the BC received SETUP→ INVITE→ Bearer capability information element Coding of SDP media description lines from BC/HLC to SIP Information transfer capability Speech See table 5.1.1.1.4-2 3,1 kHz audio See table 5.1.1.1.4-2 Unrestricted digital inf. W/tone/ann See table 5.1.1.1.4-2 unrestricted digital information See table 5.1.1.1.4-2 In addition, the whole bearer capability information element, as received in the SETUP message, shall be mapped to the PSTN XML bearer capability body in SIP, according to table 5.1.1.1.2-2. If two BC's are received then: • the BC 2 shall be mapped to the first SDP entry of the SIP INIVITE as indicated in table 5.1.1.1.4-2; and • the BC 1 shall be mapped to the second SDP entry of the SIP INVITE as indicated in table 5.1.1.1.4-2; and • both selected codecs shall appear in one m line; and • the AGCF/VGW shall store the BC values. This is needed for the fall back mechanism as described within clause 5.1.1.2.2. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 18 Table 5.1.1.1.2-2: Mapping of Bearer capability to PSTN XML BearerCapability SETUP→ INVITE→ Content PSTN XML attachment BearerCapability One BC received: BC BearerCapability mapped from the BC Information element (see note 2) Two BC received (see note 1): BC 1 (speech or 3,1 kHz audio) BC 2 (unrestricted digital information with tones and announcements) BearerCapability 1 mapped from the BC 1 Information element (see note 2) BearerCapability 2 mapped from the BC 2 Information element (see note 2) NOTE 1: BC 1 is the bearer capability information element received in first position in the SETUP message, BC 2 in the second position. Bearer capability information elements shall be received in ascending order of priority as described in clause 5.11.1.1/Recommendation ITU-T Q.931 [54]. NOTE 2: Octet 1 (information element identifier) and 2 (length) of the bearer capability information element are not included. 5.1.1.1.3 Mapping of Progress indicator/High Layer Compatibility/Low Layer Compatibility IE A progress indicator IE, high layer compatibility IE, or low layer compatibility IE, if received in a SETUP message, shall be mapped to the PSTN XML attachment in SIP, according to table 5.1.1.1.3-1. Table 5.1.1.1.3-1: Mapping of the Progress indicator/High Layer Compatibility/Low Layer Compatibility IE SETUP→ INVITE→ Content PSTN XML Attachment Progress indicator ProgressIndicator High layer compatibility HighLayerCapability Low layer compatibility LowLayerCapability Table 5.1.1.1.3-2: Mapping of the High Layer Compatibility SETUP→ INVITE→ Content PSTN XML One HLC received: HLC HighLayerCapability HLC Two HLC received (see note 1): HLC 1 HLC 2 HighLayerCapability (content of HLC 1) (see note 2) HighLayerCapability (content of HLC 2) (see note 2) NOTE 1: HLC 1 Is the high layer compatibility information element received in first position in the SETUP message, HLC 2 in second position. High layer compatibility information elements shall be received in ascending order of priority as described in clause 5.12.1.1/Recommendation ITU-T Q.931 [54]. NOTE 2: Octets 1 (information element identifier) and 2 (length) of the high layer compatibility information element are not included. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 19 Table 5.1.1.1.3-3: Coding of the progress indicator information element SETUP→ INVITE→ Progress indicator information element PSTN XML attachment No. Value of PI (see note 1) PSTN XML with ProgressIndicator No. (Value of PI) PSTN XML with ProgressIndicator No. 6 (see note 2) PSTN XML with ProgressIndicator No. 6 (see note 2) NOTE 1: Except value: No. 2 - Indicates that the destination user is not ISDN; No. 8 - "in-band information or an appropriate pattern is now available". NOTE 2: The ISDN access indicator - "originating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 6 (see annex E). The calling and called party subaddress information shall be mapped to SIP as described in clause 5.2.8.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.1.4 Request URI/To header field
|
Table 5.1.1.1.4-1: Mapping DSS1 called party number to SIP Request-URI and To header field SETUP INVITE Called party Number Request-URI and To header field Type of number Unknown Dialled strings E. 164 Number format LN (local number) Option a) sip: dialled digits@homehostportion (see note 2) Option b) sip: dialled digits; phone-context=<xxxxxx >@homehostportion; user=xxxx (see notes 1 and 2) Option c) sip: dialled digits @homehostportion; user=xxxx (see note 2) E. 164 Number format Prefix+NDC+SN (national number) E. 164 Number format Prefix + CC+NDC+SN (international number) Subscriber number Option a) sip:subscribernumber@homehostportion (see note 2) Option b) sip: subscribernumber; phone-context=<xxxxxx>@homehostportion; user=xxxx (see notes 1 and 2) option c) tel: subscribernumber;phone-context= <xxxxxx> (see notes 1 and 2) Network specific number Option a) sip: network-specific-number@homehostportion (see note 2) Option b) sip: network-specific-number;phone- context=<xxxxxx>@homehostportion;user=xxxx (see notes 1 and 2) Abbreviated number Option a) sip: dialled digits@homehostportion (see note 2) Option b) sip: dialled digits; phone-context=<xxxxxxx>@homehostportion; user=xxxx (see notes 1 and 2) ETSI ETSI TS 183 036 V3.7.1 (2021-02) 20 SETUP INVITE Called party Number Request-URI and To header field Type of number National number Option a) sip: national number@homehostportion (see note 2) Option b) sip: national number; phone-context=< xxxxxx>@homehostportion; user=xxxx (see notes 1 and 2) Option c) tel: national number;phone-context=<xxxxxx> (see notes 1 and 2) International number Option a) sip: "+" dialled digits@homehostportion; user= phone (see note 2) Option b) tel: "+" dialled digits (see note 2) NOTE 1: The combination of digits and phone-context parameter shall globally unique in the network as defined in IETF RFC 3966 [47]. NOTE 2: The provision of DDI is described in clause 6.1 of [15]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 21 Table 5.1.1.1.4-2: Coding of SDP media description lines from BC/HLC to SIP BC IE (normative) HLC IE in (Optional) m= line b= line a= line Information Transport Capability User Information Layer 1 Protocol Indicator High Layer Characteristics Identification <media> <transport> <fmt-list> <modifier>: <bandwidth -value> rtpmap:<dynamic-PT> <encoding name>/<clock rate>/encoding parameters> "Speech" "G.711 μ-law" Ignore Audio RTP/AVP 0 (and possibly 8) (see note 1) AS:64 rtpmap:0 PCMU/8000 (and possibly rtpmap:8 PCMA/8000) (see note 1) "Speech" "G.711 μ-law" Ignore Audio RTP/AVP Dynamic PT (and possibly a second Dynamic PT) (see note 1) AS:64 rtpmap:<dynamic-PT> PCMU/8000 (and possibly rtpmap:<dynamic- PT> PCMA/8000) (see note 1) "Speech" "G.711 A-law" Ignore Audio RTP/AVP 8 AS:64 rtpmap:8 PCMA/8000 "Speech" "G.711 A-law" Ignore Audio RTP/AVP Dynamic PT AS:64 rtpmap:<dynamic-PT> PCMA/8000 "3,1 kHz audio" "G.711 μ-law" Ignore Audio RTP/AVP 0 (and possibly 8) (see note 1) AS:64 rtpmap:0 PCMU/8000 (and possibly rtpmap:8 PCMA/8000) (see note 1) "3,1 kHz audio" "G.711 A-law" Ignore Audio RTP/AVP 8 AS:64 rtpmap:8 PCMA/8000 "3,1 kHz audio" "G.711 A-law" "Facsimile Group 2/3" Image Udptl t38 [56] AS:64 Based on Recommendation ITU-T T.38 [56] "3,1 kHz audio" "G.711 A-law" "Facsimile Group 2/3" Image Tcptl t38 [56] AS:64 Based on Recommendation ITU-T T.38 [56] isup_usi mapped from BC IE (see note 4) "3,1 kHz audio" "G.711 μ-law" "Facsimile Group 2/3" Image Udptl t38 [56] AS:64 Based on Recommendation ITU-T T.38 [56] isup_usi mapped from BC IE (see note 4) "3,1 kHz audio" "G.711 μ-law" "Facsimile Group 2/3" Image Tcptl t38 [56] AS:64 Based on Recommendation ITU-T T.38 [56] "Unrestricted digital inf. W/tone/ann." (see notes 4 and 5) N/A Ignore Audio RTP/AVP Dynamic PT AS:64 rtpmap:<dynamic-PT> CLEARMODE/8000 "Unrestricted digital information" N/A Ignore Audio RTP/AVP Dynamic PT AS:64 rtpmap:<dynamic-PT> CLEARMODE/8000 NOTE 1: Both PCMA and PCMU could be appear in the SDP. NOTE 2: CLEARMODE is specified in IETF RFC 4040 [51]. NOTE 3: The mapping of the "Information Transport Capability" to the proper codec is explained in annex B. NOTE 4: In case of receiving two BC elements both shall be mapped into codecs within the same m line. The fallback possibility is described within clause 5.1.1.2.2. NOTE 5: After the CLEARMODE codec, an additional speech codec G.711 should be offered in the same m line. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 22
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.2 Receipt of a Provisional Response 18x
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.2.0 General statement to provisional responses
|
The SDP answer is described in annex B.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.2.1 180 Ringing response
|
5.1.1.2.1.0 Basic procedure Depending on the following three cases, the AGCF/VGW shall send an ALERTING message across the user-network interface to the calling user, as described in table 5.1.1.2.1.0-1. The reception of the first 180 Ringing response without a P-Early-Media header (authorizing early media); or the reception of the first 180 Ringing with a P-Early-Media header (authorizing early media). 180 Ringing ALERTING Ring tone AGCF/VGW Figure 5.1.1.2.1.0-1: Sending of ALERTING (Receipt of first 180 Ringing without authorization of early media) NOTE 1: The ringing tone is sent only for voice services. In the event of the P-Early-Media header not being present in the 180 Ringing and no media flow has been received, the AGCF/VGW shall send an ALERTING message with a Progress Indicator set to 8 (in-band information or appropriate pattern now available) with the local generated media flow for BC = speech or BC = 3,1 kHz. 180 Ringing P-Early-Media ALERTING with PI#8 AGCF/VGW Ring tone Figure 5.1.1.2.1.0-2: Sending of ALERTING (Receipt of first 180 Ringing that includes authorization of early media) NOTE 2: Based on local knowledge that the call is transited to a PSTN network, the AGCF/VGW can make a decision not to generate the awaiting answer indication when receiving the 180 Ringing message without a P-Early-Media header. Once all the following sub-conditions have been met: 1) the reception of the first 183 Session Progress that includes a P-Early-Media header authorizing early media; 2) the SDP offer/answer procedures are completed; and 3) SDP preconditions are not used, or applicable SDP preconditions have been met. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 23 The support of the reception of the P-Early-Media header is mandatory for the AGCF/VGW. If the AGCF/VGW receives a 18x response with a P-Early-media header that changes the authorization of early media: • if the header authorizes early media and if the AGCF/VGW is sending the awaiting answer indication, the AGCF/VGW shall terminate the sending of the awaiting answer indication; and • if the header removes authorization of early media and if the AGCF/VGW has received the 180 Ringing response, the AGCF/VGW shall initiate the sending of the awaiting answer indication. In the event of the P-Early-Media header not being present in the 18x message and a media flow being received, such a media flow would ideally not be authorized. However, under these circumstances, a VGW may, as a network option, forward the received media flow and send an ALERTING, CALL PROCEEDING or PROGRESS message with a Progress Indicator set to 8 (In-band information or appropriate pattern now available). NOTE 3: This behaviour enables managing the case when the remote entity generating early media does not support the P-Early-Media header. Table 5.1.1.2.1.0-1: Message sent to the DSS 1 upon receipt of first 180 ←Message sent to the DSS 1 ←180 Ringing ALERTING Progress indicator information element No. 1 (see note 1) (Call is not end-to-end ISDN: further progress information may be available in-band) (see note 4) (see note 5) No PSTN XML ProgressIndicator No. 8 (see note 1) (In-band information or appropriate pattern now available) P-Early-Media header (see note 3) Number of Value of PI (see notes 2 and 4) PSTN XML with Progress indicator No. (Value of PI) and PSTN XML ProgressIndicator No. 7 (see note 2) Number of Value of PI (see note 4) PSTN XML with Progress indicator No. (Value of PI) PSTN XML with Progress indicator No. 7 (see note 2) NOTE 1: The progress indicator is only sent if the BC received in the SETUP message is coded "speech", "3,1 kHz audio" or "unrestricted digital information with tones and announcements". NOTE 2: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7 and is not sent to the access see annex E. NOTE 3: The PSTN XML ProgressIndicator No. 8 may also be present, in which case only one PI=8 is signalled to DSS1. NOTE 4: The mapping of the PSTN XML contents in the 180 message is only relevant if the information received in the message is different compared to earlier received information in the 18x message received prior to this message [2]. NOTE 5: Progress Indicator PI#1, shall be sent only if, there was no Progress Indicator PI#7 previously received. In case a Progress Indicator PI#7 was previously received then no Progress Indicator PI#1 shall be sent in the case when no PSTN XML ProgressIndicator was received. NOTE 6: In case of call diversion with the receiving of 181, the AGCF/VGW shall clear the previous status of the received PI#7 which was previously received (see note 5). In case the user has subscribed the subscriber option "Calling user is notified of diversion" set to NO, the AGCF/VGW and the calling user will not be informed in case of CFNR to a SIP user with a Progress Indicator No. 1 in the proceeding PROGRESS (Call is not end-to-end ISDN: further progress information may be available in-band). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 24 Table 5.1.1.2.1.0-2: Message sent to the DSS 1 upon receipt of subsequent 180 ←Message sent to the DSS 1 ←180 Ringing PROGRESS (see note 1) Progress indicator information element No. 1 (see notes 7 and 8) (Call is not end-to-end ISDN: further progress information may be available in-band) No PSTN XML ProgressIndicator No. 8 (In-band information or appropriate pattern now available) P-Early-Media header (see note 5) No. Value of PI (see note 3) No. 4 (see notes 4 and 7) (Call has returned to the ISDN) PSTN XML with Progress indicator Number. (Value of PI) and PSTN XML ProgressIndicator No. 7 (see note 3) No. Value of PI (see notes 6 and 7) PSTN XML with Progress indicator Number (Value of PI) No. 4 (see note 4) (Call has returned to the ISDN) PSTN XML with Progress indicator No. 7 (see note 3) NOTE 1: CALL PROCEEDING is sent if not sent previously - else PROGRESS. NOTE 2: The progress indicator is only sent if the BC received in the SETUP message is coded "speech", "3,1 kHz audio" or "unrestricted digital information with tones and announcements". NOTE 3: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7 and is not sent to the access see annex E. NOTE 4: This value is sent if PI=1 or PI=2 was signalled before. The Progress Indicator PI#4 shall be sent only in the case when no Progress Indicator PI#7 (in PSTN XML with Progress indicator) was previously received in one of the previously received messages. NOTE 5: The PSTN XML ProgressIndicator No. 8 may also be present, in which case only one PI=8 is signalled to DSS1. NOTE 6: Possible values are the Values 1 ("call is not end-end ISDN") or 2 ("destination address is not ISDN"). NOTE 7: The mapping of the PSTN XML contents in the 180 message is only relevant if the information received in the message is different compared to earlier received information in the 18x message received prior to this message [2]. NOTE 8: Progress Indicator PI#1, shall be sent only if, there was no Progress Indicator PI#7 previously received. In case a Progress Indicator PI#7 was previously received then no PI#1 shall be sent in the case when no PSTN XML ProgressIndicator was received. NOTE 9: In case of call diversion with the receiving of 181, the AGCF/VGW shall clear the previous status of the received PI#7 which was previously received (see note 8). In case the user has subscribed the subscriber option "Calling user is notified of diversion" set to NO, the AGCF/VGW and the calling user will be not be informed in case of CFNR to a SIP user with a Progress Indicator No. 1 in the proceeding PROGRESS (Call is not end-to-end ISDN: further progress information may be available in-band). 5.1.1.2.1.1 Progress indicator If the Progress indicator information elements are present in the PSTN XML attachment of the SIP Provisional Response, they shall be transferred in the DSS1 message sent to the calling user. In addition, progress indicator information elements are created by the originating AGCF/VGW according to tables 5.1.1.2.1.0-1 and 5.1.1.2.1.0-2. In case of fall-back to an alternative bearer capability or high layer compatibility, according to ETSI EN 300 403-1 [29], clauses 5.11 and 5.12, a progress indicator No. 5 (interworking has occurred and has resulted in a telecommunication service change) shall be sent by the ACGF/VGW, as described in tables 5.1.1.3-1 and 5.1.1.3-2. Every message sent to the DSS1 user (ALERTING, CALL PROCEEDING or PROGRESS) may contain two progress indicator information elements. When more than two progress indicator information elements are to be sent, the subsequent progress indicator information elements are sent in a PROGRESS message. 5.1.1.2.1.2 High layer compatibility If a high layer compatibility information element is present in the PSTN XML attachment of the SIP Provisional Response, the mapping to the HLC IE is described in table 5.1.1.2.1.2-1. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 25 Table 5.1.1.2.1.2-1: Sending of HLC fall-back information ←Message sent to DSS 1 ALERTING ←180 RINGING Content PSTN XML attachment HLC HighLayerCompatibility NOTE: The HighLayerCompatibility information in the PSTN XML attachment of the SIP body shall be mapped, if present, to the HLC IE (ETSI EN 300 403-1 [29], clause 4.5.17, table 4-23/Recommendation ITU-T Q.931 [54]). 5.1.1.2.1.3 Handling of fall-back information a) Bearer capability selection procedure According to ETSI EN 300 403-1 [29], clause 5.11, the mapping shall be done as described in table 5.1.1.2.1.3-1. Table 5.1.1.2.1.3-1: Sending of BC fall-back information ←Message sent to DSS 1 ALERTING ←180 RINGING PSTN XML attachment See note 1 BearerCapability (speech or 3,1 kHz audio) (see note 2) NOTE 1: The AGCF/VGW stores the PSTN XML Bearer Capability element for this dialog. NOTE 2: The received BearerCapability information should contain a Speech or 3,1 kHz BC. If a high layer compatibility information element is present in the PSTN XML attachment of the 180 Ringing, and if no progress indicator No. 1 (call is not end-to-end ISDN) or No. 2 (destination address is non-ISDN) has to be sent, table 5.1.1.2.1.3-1 is applicable. b) High layer compatibility selection procedure According to ETSI EN 300 403-1 [29], clause 5.12, the mapping shall be done as described in table 5.1.1.2.1.3-2. Table 5.1.1.2.1.3-2: Sending of HLC fall-back information ←Message sent to DSS 1 ALERTING ←180 RINGING PSTN XML attachment See note HighLayerCapability NOTE: The AGCF/GW stores the received PSTN XML attachment for this dialog. c) SDP selection procedure When an SDP answer was received indicating no support of the 7 kHz call setup (CLEARMODE codec not the first codec in the m line), the fall-back shall not apply as the call may not yet have reached its final destination (e.g. CFNR occurring). Table 5.1.1.2.1.3-3: No CLEARMODE support in the SDP ←Message sent to DSS 1 ALERTING ←180 RINGING SDP CLEARMODE not the first codec on the codec list ETSI ETSI TS 183 036 V3.7.1 (2021-02) 26
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.2.2 Receipt of the 183 (Session Progress) response
|
5.1.1.2.2.0 General description Once all the following sub-conditions have been met: • if the AGCF/VGW has received the first 183 Session Progress that includes a P-Early-Media header (indicating authorization of early media); and • SDP preconditions are not used or applicable SDP preconditions have been met. The AGCF/VGW shall send a CALL PROCEEDING or PROGRESS message according to table 5.1.1.2.2.3-2 to the calling user, as described in table 5.1.1.2.2.3-2. 183 Progress P-Early-Media CALL PROC/PROGRESS in-band information available appropriate announcement O-AGCF/VGW Figure 5.1.1.2.2.0-1: Sending of Call Proceeding (Receipt of first 183 that includes authorization of early media) In the event of the P-Early-Media header not being present in the 18x message and a media flow being received, such a media flow would ideally not be authorized. However, under these circumstances, a VGW may, as a network option, forward the received media flow and send an ALERTING, CALL PROCEEDING or PROGRESS message with a Progress Indicator set to 8 (In-band information or appropriate pattern now available). NOTE: This behaviour enables managing the case when the remote entity generating early media does not support the P-Early-Media header. 5.1.1.2.2.1 Progress indicator Table 5.1.1.2.2.1-1: Message sent to the DSS 1 interface upon receipt of 183 (Session Progress) response ←Message sent to the DSS 1 ←183 Session Progress CALL PROCEEDING when not been sent before (see note 1) Progress Indicator IE: Progress description No. 8 (see note 3) (In-band information or appropriate pattern now available) P-Early-Media header (see note 7) Progress Indicator IE: Progress description No. Value of PI (see notes 5, 8 and 9) PSTN XML with Progress indicator (Value of PI) and ProgressIndicator No. 7 (see note 5) PSTN XML with Progress indicator (Value of PI) (see notes 8 and 9) PSTN XML with Progress description No. Value of PI PSTN XML ProgressIndicator No. 7 (see note 5) ETSI ETSI TS 183 036 V3.7.1 (2021-02) 27 ←Message sent to the DSS 1 ←183 Session Progress PROGRESS if a progress indicator information element is contained in 183 (see note 2) Progress description No. 1 (Call is not end-to-end ISDN: further progress information may be available in-band) (see notes 9 and 10) No PSTN XML ProgressIndicator Progress Indicator IE: Progress description No. 8 (see note 3) (In-band information or appropriate pattern now available P-Early-Media header (see note 7) Progress Indicator IE: Progress description No. Value of PI (see notes 5, 8 and 9) No. 4 (see note 6) (Call has returned to the ISDN) PSTN XML with Progress indicator (Value of PI) and PSTN XML ProgressIndicator No. 7 (see note 5) PSTN XML with Progress indicator (Value of PI) (see notes 8 and 9) PSTN XML with Progress Indicator IE: Progress description Number Value of PI No. 4 (see note 6) (Call has returned to the ISDN) PSTN XML ProgressIndicator No. 7 (see note 5) NOTE 1: The receipt from the network of a 183 Session Progress is interpreted by the network as a sending complete indication, in the case where the network could not determine it before. NOTE 2: The sending of a progress indicator information element is described above. NOTE 3: The progress indicator is only sent if the BC received in the SETUP message is coded speech, 3,1 kHz audio. NOTE 4: If a PSTN XML attachment HLC is received, it shall be mapped to the HLC IE. NOTE 5: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7 and is not sent to the access. NOTE 6: This value is sent if PI=1 or PI=2 was signalled immediately before. The Progress Indicator PI#4 shall be sent only in the case when no Progress Indicator PI#7 (in PSTN XML with Progress indicator) was previously received in one of the previously received messages. NOTE 7: The PSTN XML ProgressIndicator No. 8 may also be present, in which case only one PI=8 is signalled to DSS1. NOTE 8: Possible values are the Values 1 ("call is not end-end ISDN") or 2 ("destination address is not ISDN") NOTE 9: The mapping of the PSTN XML contents in the 183 message is only relevant if the information received in the message is different compared to earlier received information in the 18x message received prior to this message [2]. NOTE 10: Progress Indicator PI#1, shall be sent only if, there was no Progress Indicator PI#7 previously received. In case a Progress Indicator PI#7 was previously received then no PI#1 shall be sent in the case when no PSTN XML ProgressIndicator was received. This note is not applicable in case of call forwarding. If more than two progress indicator information elements are to be sent, the subsequent progress indicator information elements shall be sent in a PROGRESS message. 5.1.1.2.2.2 High layer compatibility If a high layer compatibility information element is present in the PSTN XML attachment of the 183 Session Progress, see handling of fall-back information in clause 5.1.1.2.2.3. 5.1.1.2.2.3 Handling of fall-back information a) Bearer capability selection procedure According to ETSI EN 300 403-1 [29], clause 5.11, the mapping shall be done as described in table 5.1.1.2.2.3-1. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 28 Table 5.1.1.2.2.3-1: Sending of BC fall-back information ←Message sent to DSS 1 ←183 Session Progress CALL PROCEEDING or PROGRESS PSTN XML attachment See note 1 BearerCapability (speech or 3,1 kHz audio) (see note 2) NOTE 1: The AGCF/VGW stores the received PSTN XML for this dialog. NOTE 2: The received BearerCapability information should contain a Speech or 3,1 kHz BC. If a high layer compatibility information element is present in the PSTN XML attachment of the 183 Session Progress, and if no progress indicator No. 1 (call is not end-to-end ISDN) or No. 2 (destination address is non-ISDN) has to be sent, table 5.1.1.2.1.3-1 is applicable. b) High layer compatibility selection procedure According to ETSI EN 300 403-1 [29], clause 5.12, the mapping shall be done as described in table 5.1.1.2.1.3-2. Table 5.1.1.2.2.3-2: Sending of HLC fall-back information ←Message sent to DSS 1 ←183 Session Progress ← CALL PROCEEDING or PROGRESS PSTN XML attachment See note HighLayerCapability Progress indicator No. 5 NOTE: The AGCF/VGW stores the received PSTN XML for this dialog. c) SDP selection procedure When an SDP answer was received indicating no support of the 7 kHz call setup (no CLEARMODE codec in the m line), the fall-back shall not apply as the call may not yet have reached its final destination (e.g. application of an indication). Table 5.1.1.2.2.3-3: Sending of fall-back information no support in the SDP ←Message sent to DSS 1 ←183 Session Progress ←CALL PROCEEDING or PROGRESS SDP Progress Indicator No. 8 (see note) CLEARMODE not the first codec on the codec list NOTE: The AGCF/VGW may send the Progress Indicator No. 8 also in a PROGRESS message to the user.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.3 Receipt of the 200 OK INVITE
|
Upon receipt of a 200 OK INVITE and the 200 OK INVITE does not contain the from-change tag in the supported header, the AGCF/VGW shall send a CONNECT message across the user-network interface to the calling user. If the from-change tag in the supported header is contained in the 200 OK INVITE, the applicable procedures are described in clause 5.2.2.2. The SDP answer is described in annex B. The CONNECT message is coded as follows. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 29 Table 5.1.1.3-1: Sending criteria of the progress indicator information elements created by the VGW/AGCF ←CONNECT ←200 OK Progress indicator information element Progress description No. 1 (see note 2) (Call is not end-to-end ISDN: further progress information may be available in-band) (see notes 5 and 6) No PSTN XML ProgressIndicator Progress description No. Value of PI Progress description No. 4 (see note 3) (Call has returned to the ISDN) (see notes 4 and 5) PSTN XML with Progress indicator No (Value of PI) and PSTN XML ProgressIndicator No. 7 (see note 1) Progress description No. Value of PI (see note 4) (see note 5) PSTN XML with Progress indicator No (Value of PI) Progress description No. 4 (see note 3) (Call has returned to the ISDN) PSTN XML ProgressIndicator No. 7 (see note 1) NOTE 1: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7 and is not sent to the access see annex E. NOTE 2: This value is sent if PI=1 not previously sent or PI=4 was signalled immediately previously. NOTE 3: This value is sent if PI=1 or PI=2 was signalled immediately before. The Progress Indicator PI#4 shall be sent only in the case when no Progress Indicator PI#7 (in PSTN XML with Progress indicator) was previously received in one of the previously received messages. NOTE 4: Values 1 ("call is not end-end ISDN") or 2 ("destination address is not ISDN") and value 5 ("interworking has occurred and has resulted in a telecommunications service change NOTE 5: The mapping of the PSTN XML contents in the 200 OK message is only relevant if the information received in the message is different compared to earlier received information in the 18x message received prior to this message [2]. NOTE 6: Progress Indicator PI#1, shall be sent only if, there was no Progress Indicator PI#7 previously received. In case a Progress Indicator PI#7 was previously received then no PI#1 shall be sent in the case when no PSTN XML ProgressIndicator was received. This note is not applicable in case of call forwarding. NOTE: The PES AS assures that the correct PI and their combination is provided to the AGCF/VGW. The CONNECT message sent to the access may contain two progress indicator information elements. When more than two progress indicator information elements are to be sent, the subsequent progress indicator information elements shall be sent in a PROGRESS message. High layer compatibility If a high layer compatibility information element is present in the PSTN XML attachment of the 200 OK INVITE, see handling of fall-back information at the end of this clause. Low layer compatibility The low layer compatibility possibly present in the PSTN XML attachment of the 200 OK INVITE is passed on unchanged. History-Info header See clause 5.2. User-user See clause 5.2. P-Asserted-Identity See clause 5.2. Connected subaddress See clause 5.2. Handling of fall-back information According to ETSI EN 300 403-1 [29], clause 5.11, the mapping shall be done as described in table 5.1.1.3-2. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 30 Table 5.1.1.3-2: Sending of BC fall-back information ←CONNECT (see note 1) ←200 OK INVITE PSTN XML attachment SDP m line BC derived from received BearerCapability (Unrestricted digital information with tones and announcements) BearerCapability (unrestricted digital information with tones and announcements) (see note 2) The first stated codec has to be consistent with the PSTN XML BearerCapability BC derived from received BearerCapability (speech or 3,1 kHz audio) Progress Indicator No. 5 BearerCapability (speech or 3,1 kHz audio) (see note 2) The first stated codec has to be consistent with the PSTN XML BearerCapability B C (speech or 3,1 kHz audio) Progress Indicator No. 5 No PSTN XML attachment The SDP answer has precedence (see note 3) NOTE 1: If fall-back allowed was indicated in the SETUP message, and fall-back occurs at the destination, or fall-back does not occur, the AGCF/VGW shall include in the CONNECT message the BC IE of the resultant bearer service. NOTE 2: If the SDP answer is not consistent with PSTN XML BearerCapability element, the call is released by the AGCF/VGW. NOTE 3: The SDP answer shall indicate G.711 not CLEARMODE - if not then the AGCF/VGW releases the call. NOTE 4: The PSTN XML and SDP may be contained in the 200 OK or else stored from a 18X message in the same dialog. According to ETSI EN 300 403-1 [29], clause 5.12, the mapping shall be done as described in table 5.1.1.3-3. Table 5.1.1.3-3: Sending of HLC fall-back information ←CONNECT ←200 OK INVITE Content PSTN XML attachment HLC HighLayerCapability Progress indicator No. 5 ProgressIndicator No. 5 NOTE 1: If procedures of BC fall-back and HLC fall-back both require the sending of the progress indicator No. 5, only one progress indicator No. 5 is sent. NOTE 2: The PSTN XML may be contained in the 200 OK or else stored from a 18X message in the same dialog.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.4 Receipt of (BYE or Final Response)
|
Table 5.1.1.4-1: Receipt (BYE or Final Response) ←DISCONNECT ←BYE/3xx/4xx/5xx/6xx Cause information element Reason header Cause value No. X (see notes 1 and 2) cause value No. X Progress indicator No. 8 (see note 3) (In-band information or appropriate pattern now available) NOTE 1: If the cause value received in the Release message (BYE or Final Response) is unknown in DSS 1, the unspecified cause value of the class is sent. NOTE 2: Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values; see clause 5.2. NOTE 3: The progress indicator is only sent if the BC received in the SETUP message is coded speech, 3,1 kHz audio. NOTE 4: The location is coded '1010' network beyond interworking point. NOTE 5: The Progress Indicator may also be sent in a PROGRESS message. NOTE 6: If the 3xx response is not filtered by the AS, it can be received by the AGCF/VGW. The handling of the other parameters is described in clause 5.2. The receipt of the release message (BYE or Final Response) during the user suspend/resume procedure is described in clause 5.2. NOTE: For providing tones/announcements in the disconnect indication state (ETSI EN 300 403-1 [29]), three possibilities are applicable: 1) Provision of tones/announcements by the AGCF autonomously. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 31 2) Provision of tones/announcements under the control of the AS, for which the impact on the AGCF/VGW is the receipt of either a reINVITE or REFER. 3) The AGCF/VGW has a pre-configured URI of the MRFC and establishes a session for providing the tones/announcements. The session to the MRFC is terminated with a BYE when a RELEASE message is sent or received from/to the DSS1 user. If a reason header is included in a 4XX, 5XX, 6XX final response, then the cause value of the reason header shall be mapped to the DSS1 Cause value sub-field in the DISCONNECT message. Otherwise coding of the cause parameter value in the DISCONNECT message is derived from the SIP Status code received according to table 5.1.1.4-2. The Cause Values are defined in ETSI endorsement of Recommendation ITU-T Q.850 [61]. Table 5.1.1.4-2: 3xx/4xx/5xx/6xx Received on SIP side of O-AGCF/VGW ←DISCONNECT (cause value) ←3xx/4xx/5xx/6xx SIP final responses 127 (interworking unspecified) 400 Bad Request 127 (interworking unspecified) 401 Unauthorized 127 (interworking unspecified) 402 Payment Required 127 (interworking unspecified) 403 Forbidden 1 (Unallocated number) 404 Not Found 127 (interworking unspecified) 405 Method Not Allowed 127 (interworking unspecified) 406 Not Acceptable 127 (interworking unspecified) 407 Proxy authentication required 127 (interworking unspecified) 408 Request Timeout 22 (Number changed) 410 Gone 127 (interworking unspecified) 413 Request Entity too long 127 (interworking unspecified) 414 Request-URI too long 127 (interworking unspecified) 415 Unsupported Media type 127 (interworking unspecified) 416 Unsupported URI scheme 127 (interworking unspecified) 420 Bad Extension 127 (interworking unspecified) 421 Extension required 127 (interworking unspecified) 423 Interval Too Brief 24 (call rejected due to ACR supplementary service) 433 Anonymity Disallowed 20 Subscriber absent 480 Temporarily Unavailable 127 (interworking unspecified) 481 Call/Transaction does not exist 127 (interworking unspecified) 482 Loop detected 127 (interworking unspecified) 483 Too many hops 28 (Invalid Number format) 484 Address Incomplete 127 (interworking unspecified) 485 Ambiguous 17 (User busy) 486 Busy Here 127 (Interworking unspecified) or not interworked (see note 1) 487 Request terminated 127 (interworking unspecified) 488 Not acceptable here 127 (interworking unspecified) 493 Undecipherable 127 (interworking unspecified) 500 Server Internal error 127 (interworking unspecified) 501 Not implemented 127 (interworking unspecified) 502 Bad Gateway 127 (interworking unspecified) 503 Service Unavailable 127 (interworking unspecified) 504 Server timeout 127 (interworking unspecified) 505 Version not supported 127 (interworking unspecified) 513 Message too large 127 (interworking unspecified) 580 Precondition failure 17 (User busy) 600 Busy Everywhere 21 (Call rejected) 603 Decline 1 (unallocated number) 604 Does not exist anywhere 127 (interworking unspecified) 606 Not acceptable NOTE 1: No interworking if the O-AGCF previously issued a CANCEL request for the INVITE. NOTE 2: The 4xx/5xx/6xx SIP responses that are not covered in this table are not interworked (i.e. mapped to cause 127). NOTE 3: The 3xx responses are not interworked (i.e. mapped to cause 127). ETSI ETSI TS 183 036 V3.7.1 (2021-02) 32
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.5 Sending of (BYE or CANCEL)
|
Table 5.1.1.5-1: Call clearing from the user DISCONNECT, RELEASE RELEASE COMPLETE→ BYE/CANCEL→ Cause information element Reason header Cause value No. X cause value No. X (see notes 1 and 2) NOTE 1: If the cause value received in the DSS 1 message is unknown in ISUP, the unspecified cause value of the class is sent. NOTE 2: Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values; see clause 5.2.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.1.6 Use of Overlap signalling (Optional)
|
If overlap signalling is supported between the AGCF/VGW and the originating PES Application Server the overlap signalling method used, either the multiples INVITES method or the IN-Dialog method as described within annexes G and H is dependent on national or network operator option.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2 Actions at the Incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.1 Sending of the SETUP message
|
On reception of a SIP INVITE, the AGCF/VGW shall send a SETUP message. An AGCF/VGW shall support both incoming INVITE requests containing SIP preconditions and 100rel extensions in the SIP Supported or Require headers, and INVITE requests not containing these extensions. If the SDP in the received INVITE request contains preconditions not met, the AGCF/VGW shall delay sending the SETUP until the SIP preconditions are met. The AGCF/VGW shall reject an INVITE request for a session only containing unsupported media types by sending a status code 488 (unsupported media type). If several media streams are contained in a single INVITE request, the AGCF/VGW shall select one of the supported media streams, reserve the codec(s) for that media stream, and reject the other media streams and unselected codecs in the SDP answer, as detailed in IETF RFC 3264 [52]. If supported audio media stream(s) and supported non-audio media stream(s) are contained in a single INVITE request, an audio stream should be selected. The AGCF/VGW shall include a to tag in the first backward non-100 provisional response, in order to establish an early dialog as described in IETF RFC 3261 [53]. The information elements carried in the PSTN XML attachment of the INVITE are taken into account whatever the order of receipt, except when two bearer capability and/or two high layer compatibility information elements are received: the order of these two information elements shall be treated according to ETSI EN 300 403-1 [29], see table 5.1.2.1-1. Only the information elements involved in the interworking are described hereafter. The information elements used for the supplementary services are described in clause 5.2. For the case a PSTN XML SendingCompleteIndicator is received in an INVITE, a sending complete information element is contained in the SETUP and INFO, timer T304 is not started. Bearer capability NOTE: The message side and direction has been changed to be in-line with the usual mapping as in ETSI EN 300 899-1 [2] ISUP-DSS1. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 33 Table 5.1.2.1-1: Coding of the Bearer Capability information element (BC) INVITE→ SETUP→ Content Bearer capability information element PSTN XML BearerCapability BC information is taken from PSTN XML BearerCapability PSTN XML BearerCapability 1 Speech, or 3,1 kHz audio PSTN XML BearerCapability 2 Unrestricted digital information with tones and announcements First BC information is derived from first PSTN XML BearerCapability (see note 1) Second BC information is derived taken from second PSTN XML BearerCapability (see note 1) No PSTN XML BearerCapability See table 5.1.2.1-2 NOTE 1: BC 1 is the bearer capability information element sent in first position in the SETUP message, BC 2 in second position. Bearer capability information elements shall be sent in ascending order of priority as described in clause 5.11.2.1/Recommendation ITU-T Q.931 [54]. NOTE 2: Basic coding of the Bearer Capability IE. If the INVITE does not contain SDP information but a bearer capability information in the PSTN XML body is present, this is an error and the call shall be rejected with the status code 606. If the INVITE message does not contain any bearer information (neither bearer info in SDP nor in PSTN XML body), the AGCF/VGW may postpone the sending of the SETUP message. The AGCF/VGW may send an SDP offer including a media description, the content of which is determined using local policy within a 183 (Session Progress) response message. The SETUP message shall then be sent when the AGCF/VGW has received sufficient information to create the BC/HLC, else the call shall be cleared with status code 606. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 34 Table 5.1.2.1-2: Coding of from SDP: SIP to DSS1 m= line b= line (see note 4) a= line BC IE (normative) (see note 1) HLC parameter (optional) <media> <transport> <fmt-list> <modifier>:<bandwi dth-value> (see note 5) Rtpmap:<dynamic-PT> <encoding name>/<clock rate>/encoding parameters> Information Transport Capability User Information Layer 1 Protocol Indicator High Layer Characteristics Identification Audio RTP/AVP 0 N/A or up to 64 kbit/s N/A "3,1 kHz audio" "G.711 A-law" (see note 3) Audio RTP/AVP 0 N/A or up to 64 kbit/s N/A "3,1 kHz audio" "G.711 μ-law" (see note 3) Audio RTP/AVP Dynamic PT N/A or up to 64 kbit/s rtpmap:<dynamic-PT> PCMU/8000 "3,1 kHz audio" "G.711 A-law" (see note 3) Audio RTP/AVP Dynamic PT N/A or up to 64 kbit/s rtpmap:<dynamic-PT> PCMU/8000 "3,1 kHz audio" "G.711 μ-law" (see note 3) Audio RTP/AVP 8 N/A or up to 64 kbit/s N/A "3,1 kHz audio" "G.711 A-law" (see note 3) Audio RTP/AVP 8 N/A or up to 64 kbit/s N/A "3,1 kHz audio" "G.711 μ-law" (see note 3) Audio RTP/AVP Dynamic PT N/A or up to 64 kbit/s rtpmap:<dynamic-PT> PCMA/8000 "3,1 kHz audio" "G.711 A-law" (see note 3) Audio RTP/AVP Dynamic PT N/A or up to 64 kbit/s rtpmap:<dynamic-PT> PCMA/8000 "3,1 kHz audio" "G.711 μ-law" (see note 3) Audio RTP/AVP Dynamic PT, AS: 64 kbit/s rtpmap:<dynamic-PT> CLEARMODE/8000 "Unrestricted digital inf. W/tone/ann." (see notes 6 and 7) Mapped from the PSTN XML attachment Mapped from the PSTN XML attachment Audio RTP/AVP Dynamic PT AS: 64 kbit/s Rtpmap:<dynamic-PT> CLEARMODE/8000 (see note 2) "Unrestricted digital information" Mapped from the PSTN XML attachment Image Udptl t38 [56] N/A or up to 64 kbit/s Based on Recommendation ITU-T T.38 [56] "3,1 kHz audio" "G.711 A-law" "Facsimile Group 2/3" Image Tcptl t38 [56] N/A or up to 64 kbit/s Based on Recommendation ITU-T T.38 [56] "3,1 kHz audio" "G.711 A-law" "Facsimile Group 2/3" Image Udptl t38 [56] N/A or up to 64 kbit/s Based on Recommendation ITU-T T.38 [56] "3,1 kHz audio" "G.711 μ-law" "Facsimile Group 2/3" Image Tcptl t38 [56] N/A or up to 64 kbit/s Based on Recommendation ITU-T T.38 [56] "3,1 kHz audio" "G.711 μ-law" "Facsimile Group 2/3" NOTE 1: In this table the codec G.711 is used only as an example. Other codecs are possible. NOTE 2: CLEARMODE is specified in IETF RFC 4040 [51]. NOTE 3: HLC is normally absent in this case. It is possible for HLC to be present with the value "Telephony", although clause 6.3.1/Recommendation ITU-T Q.939 [55] indicates that this would normally be accompanied by a value of "Speech" for the Information Transfer Capability element. NOTE 4: If the b=line indicates a bandwidth greater than 64 kbit/s then the call may use compression techniques or reject the call with a 415 response indicating that only one media stream of 64 kbit/s is supported. NOTE 5: <bandwidth value> for <modifier> of AS is in units of kbit/s. NOTE 6: The mapping of the "Information Transport Capability" to the proper codec is explained in annex B. NOTE 7: The value "Unrestricted digital inf. w/tones/ann" should only be used if the Clearmode codec appears together with speech codecs in the same m line. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 35 Progress indicator Table 5.1.2.1-3: Coding of the progress indicator information element INVITE→ SETUP→ Progress indicator information element PSTN XML attachment ProgressIndicator No. (Value of PI) and PSTN XML and ProgressIndicator No. 6 (see note 2) Progress indicator No. Value of PI (see note 1) ProgressIndicator No. 6 (see note 2) No PSTN XML Progress indicator No. 1 NOTE 1: Except value No. 6 which is not defined in ETSI EN 300 403-1 [29]. NOTE 2: The ISDN access indicator - "originating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 6 and is not sent to the access, see annex E. Low layer compatibility If the low layer compatibility information element is present in the PSTN XML attachment, LowLayerCompatibility of the INVITE, it is converted into the LLC in the SETUP message. High layer compatibility If the high layer compatibility information element is present in the PSTN XML attachment, HighLayerCompatibility of the INVITE, it is converted into the HLC in the SETUP message. If two high layer compatibility information elements are received in the PSTN XML attachment, HighLayerCompatibility of the INVITE, they are converted into the HLC in the same order in the SETUP message (the meaning of HLC order is described in clause 5.12.3.2/Recommendation ITU-T Q.931 [54]). Calling party number See clause 5.2. Calling party subaddress See clause 5.2. Called party subaddress See clause 5.2. User-user See clause 5.2. Table 5.1.2.1-4: Mapping SIP Request-URI to DSS1 called party number INVITE SETUP Request-URI Called Party Number E164 Address (format "+"CC+NDC+SN) (e.g. as User info in SIP URI with user= phone, or as tel URI) Type of number (see note) National number NDC+SN International number "+"CC+NDC+SN Subscriber number SN NOTE: The DDI procedures for interworking with private ISDN are described in clause 10.2 of [15]. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 36
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.2 Sending of the 18x from the destination VGW/AGCF
|
Table 5.1.2.2-1: Interworking of CALL PROCEEDING/PROGRESS ←Message on the SIP ←Message sent to the DSS 1 183 Session Progress CALL PROCEEDING/PROGRESS Progress indicator information element PSTN XML with ProgressIndicator Value of PI and PSTN XML ProgressIndicator No. 7 (see note 2) Number Value of PI PSTN XML ProgressIndicator No. 7 (see note 2) NOTE 1: The P-Early-Media header is only sent if the BearerCapability received in the INVITE message is coded speech, 3,1 kHz audio. NOTE 2: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML ProgressIndicator No. 7, see annex E. The SDP answer is described in annex B. If en bloc sending is used on the DSS 1 side, the SETUP message shall contain all the information required by the called user to process the call. If overlap sending is used, and if the SETUP message has already been sent and the SETUP ACKNOWLEDGE message received, an INFORMATION message is sent upon receipt of each subsequent INVITE message. The following cases are possible trigger conditions of sending the 18x message: a) The destination VGW/AGCF has determined independently of access indications that the complete called party number has been received, a 183 Session Progress is sent. b) Overlap receiving is used on the DSS 1 side and a CALL PROCEEDING is received, a 183 Session Progress is sent. c) En bloc receiving is used on the DSS 1 side and a Progress indicator information element is received in a CALL PROCEEDING message or in a PROGRESS message, a 183 session progress is sent. 183 Session Progress should be not sent if the value No. 8, in-band information or an appropriate pattern is now available, or No. 3 originating address is non-ISDN is received. d) The first ALERTING message is received, a 180 ringing is sent. e) It has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination VGW/AGCF, a 183 session progress is sent. On speech or 3,1 kHz calls, the awaiting answer indication (e.g. ring tone) is sent to the calling party upon receipt of the first ALERTING message. Table 5.1.2.2-2: Interworking of ALERTING ←180 Ringing ←ALERTING Progress indicator information element PSTN XML with progress indicator value of PI and PSTN XML progressIndicator No. 7 (see note 2) Number Value of PI P-Early-Media header PSTN XML with progress indicator 8 (see note 1) PSTN XML progressIndicator No. 7 (see note 2) NOTE 1: The P-Early-Media header is only sent if the BearerCapability received in the INVITE message is coded "speech", "3,1 kHz audio". NOTE 2: The ISDN access indicator - "Terminating access ISDN" is transported in the IMS as PSTN XML progress indicator No. 7, see annex E. The SDP answer is described in annex B. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 37 If the 180 Ringing has already been sent the following cases are possible trigger conditions of sending the 183 Session Progress: a) It has been determined, in case of call failure, that a special in-band tone or announcement has to be returned to the calling party from the destination VGW/AGCF. b) It has been determined that an in-band tone or announcement has to be returned to the calling party from the destination VGW/AGCF. Table 5.1.2.2-3: Contents of 183 Session Progress message if a 180 Ringing has already been sent ←Message on the SIP 183 Session Progress P-Early-Media header PSTN XML with Progress indicator 8 (see note 1) NOTE 1: The P-Early-Media header is only sent if the PSTN XML BearerCapability received in the INVITE message is coded speech, 3,1 kHz audio. NOTE 2: This ensures that the originating side receives an indication that the terminating access is ISDN. MANDATORY PARAMETERS None. OPTIONAL PARAMETERS The P-Early-Media header authorization of early media if it has been determined, that an in-band tone or announcement has to be returned to the calling party from the destination gateway. NOTE: Tones and announcements can as well be provided by the MRFC. PSTN XML attachment HLC, LLC, Progress indicator, etc. This extension carries the progress indicator information element possibly received from the called user (except the value No. 8). It may carry other information element as well: see clause 5.2 and tables 5.1.2.2-4 and 5.1.2.2-5. History-Info header See clause 5.2. Handling of fall-back information (only applicable at T reference point) When the terminating gateway has knowledge that the fall-back capability was requested in the Initial INVITE, and if no progress indicator No. 1 or No. 2 have been received from the DSS 1 side, tables 5.1.2.2-4 and 5.1.2.2-5 are applicable. Table 5.1.2.2-4: Handling of BC fall-back information ←18x ←Message received from the access PSTN XML attachment Content BearerCapability derived from received DSS1 BC (speech or 3,1 kHz audio) ProgressIndicator No. 5 BC low (speech or 3,1 kHz audio) p.i. No. 5 ETSI ETSI TS 183 036 V3.7.1 (2021-02) 38 The SDP answer is described in annex B. Table 5.1.2.2-5: Handling of HLC fall-back information ←18x ←Message received from the access PSTN XML attachment Content HighLayerCompatibility ProgressIndicator No. 5 HLC Progress indicator No. 5 The SDP answer is described in annex B.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.3 Sending of the 200 OK INVITE
|
Upon receipt of the CONNECT message, the destination AGCF/VGW shall: • stop the sending of the awaiting answer indication (if any); • send the 200 OK INVITE to the preceding entity. NOTE: Tones and announcements can as well be provided by the MRFC. The 200 OK INVITE is coded as follows: OPTIONAL PARAMETERS P-Asserted-Identity See clause 5.2. A second identity is also delivered in a changed from header in an UPDATE request, in detail described in clause 5.2.2. PSTN XML attachment Table 5.1.2.3-1: Contents of the PSTN XML attachment ← 200 OK INVITE ←CONNECT PSTN XML attachment Information elements ProgressIndicator No (Value of PI) and ProgressIndicator No. 7 (see annex E) Progress indicator No. Value of PI LowLayerCompatibility and ProgressIndicator No. 7 (see annex E) Low layer compatibility High layer compatibility and ProgressIndicator No. 7 (see annex E) High layer compatibility Bearer Capability and ProgressIndicator No. 7 (see annex E) Bearer Capability ProgressIndicator No. 7 (see annex E) It may carry other information elements as well: see clause 5.2 and tables 5.1.2.3-2 to 5.1.2.3-5. The SDP answer is described in annex B. Handling of fall-back information When the terminating AGCF/VGW has knowledge that the fall-back capability was requested in the initial INVITE, and if no progress indicator No. 1 or No. 2 has been received from the DSS 1 side, tables 5.1.2.3-2 to 5.1.2.3-5 are applicable. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 39 Coincident S and T reference point Table 5.1.2.3-2: Handling of BC fall-back information Coincident S and T reference point ←200 OK INVITE ←CONNECT PSTN XML attachment Content BearerCapability (unrestricted digital information with tones and announcements) BC (unrestricted digital information with tones and announcements) BearerCapability (speech or 3,1 kHz audio) BC (speech or 3,1 kHz audio) BearerCapability received in the PSTN XML attachment of the received INVITE request (speech or 3,1 kHz audio) No BC The SDP answer is described in annex B. Table 5.1.2.3-3: Handling of HLC fall-back information Coincident S and T reference point ←200 OK INVITE ←CONNECT PSTN XML attachment Content HighLayerCompatibility HLC HighLayerCompatibility received in first position in the PSTN XML attachment of the INVITE request No HLC The SDP answer is described in annex B. T reference point Table 5.1.2.3-4: Handling of BC fall-back information T reference point ← 200 OK INVITE ←CONNECT PSTN XML attachment Content BearerCapability (unrestricted digital information with tones and announcements) BC (unrestricted digital information with tones and announcements) BearerCapability (speech or 3,1 kHz audio) BC (speech or 3,1 kHz audio) BearerCapability (speech or 3,1 kHz audio) ProgressIndicator No. 5 BC (speech or 3,1 kHz audio) p.i. No. 5 BearerCapability received in the PSTN XML attachment of the INVITE request (speech or 3,1 kHz audio) ProgressIndicator No. 5 No BC (see note) NOTE: In this case, the fall-back information coded in the PSTN XML attachment is not repeated if already sent in a previous backward message. The SDP answer is described in annex B. Table 5.1.2.3-5: Handling of HLC fall-back information T reference point ←200 OK INVITE ←CONNECT PSTN XML attachment Content HighLayerCompatibility HLC HighLayerCompatibility ProgressIndicator No. 5 HLC Progress indicator No. 5 No HighLayerCompatibility No HLC The SDP answer is described in annex B. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 40
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.4 Receipt of BYE/CANCEL
|
Table 5.1.2.4-1: Receipt of BYE/CANCEL BYE/CANCEL→ DISCONNECT → Reason header Cause information element Cause No. X Cause value No. X (see notes 1 and 2) NOTE 1: If the Reason value received in the Release message (BYE/CANCEL) is unknown in DSS 1, the unspecified cause value of the class is sent. NOTE 2: Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values: see clause 5.2. NOTE 3: The location is coded '1010' network beyond interworking point. The handling of the other parameters is described in clause 5.2.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.5 Sending of BYE/4xx/5xx
|
If a DISCONNECT, RELEASE or RELEASE COMPLETE message is received and a final response (i.e. 200 OK (INVITE)) has already been sent, the I-AGCF/VGW shall send a BYE message. "The Cause value sub-field received in the DISCONNECT, RELEASE or RELEASE COMPLETE message shall be mapped to the cause value of the Reason header of the BYE message". If the DISCONNECT, RELEASE or RELEASE COMPLETE message is received and the final response (i.e. 200 OK (INVITE)) has not already been sent, the I-AGCF/VGW shall send a Status-Code 4xx (Client Error) or 5xx (Server Error) response. The Status code to be sent is determined by examining the Cause code value received in the DISCONNECT, RELEASE or RELEASE COMPLETE message. Table 5.1.2.5-2 specifies the mapping of the cause code values to SIP response status codes. Cause code values not appearing in the table shall have the same mapping as the appropriate class defaults according to the ETSI endorsement of Recommendation ITU-T Q.850 [61]. Table 5.1.2.5-1: Call clearing during call establishment ←BYE/4xx/5xx ←DISCONNECT RELEASE RELEASE COMPLETE (see note 1) Reason header Cause information element Cause No. X (see note 2) Cause value No. X NOTE 1: In case of coincident S and T reference point, clause 5.2.5.3/Recommendation ITU-T Q.931 [54] describes how these messages are taken into account when they are received during call establishment. NOTE 2: If the cause value received in the DSS 1 message is unknown in ISUP, the unspecified cause value of the class is sent. NOTE 3: Some supplementary services, such as CUG or UUS supplementary services, require the mapping of some cause values: see clause 5.2. The handling of the other parameters possibly present in the Release message BYE or 4xx/5xx is described in clause 5.2. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 41 Table 5.1.2.5-2: Receipt of DISCONNECT, RELEASE or RELEASE COMPLETE message ←SIP final response ←DISCONNECT, RELEASE, RELEASE COMPLETE Status code Cause value 404 Not Found Cause value No. 1 (unallocated (unassigned) number) 500 Server Internal error Cause value No. 2 (no route to network) 500 Server Internal error Cause value No. 3 (no route to destination) 500 Server Internal error Cause value No. 4 (Send special information tone) 404 Not Found Cause value No. 5 (Misdialled trunk prefix) 486 Busy Here Cause value No. 17 (user busy) 480 Temporarily unavailable Cause value No. 18 (no user responding) 480 Temporarily unavailable Cause value No. 19 (no answer from the user) 480 Temporarily unavailable Cause value No. 20 (subscriber absent) 603 Decline Cause value No. 21 (call rejected), Location = 000/user (U) 480Temporarily unavailable Cause value No. 21 (call rejected) , Location <> 000/user (U) 410 Gone Cause value No. 22 (number changed) 433 Anonymity Disallowed Cause value No. 24 (call rejected due to ACR supplementary service) 480 Temporarily unavailable Cause value No. 25 (Exchange routing error) 502 Bad Gateway Cause value No. 27 (destination out of order) 484 Address Incomplete Cause value No. 28 invalid number format (address incomplete) 500 Server Internal error Cause value No. 29 (facility rejected) 480 Temporarily unavailable Cause value No. 31 (normal unspecified) (class default) (see note) 486 Busy here if CCBS-T-Available invoke component is present) else 480 Temporarily unavailable Cause value in the Class 010 (resource unavailable, cause value No. 34) 500 Server Internal error Cause value in the Class 010 (resource unavailable, cause value No.'s 38, 41, 42, 43, 44 & 47) (47 is class default) 500 Server Internal error Cause value No. 50 (requested facility no subscribed) 500 Server Internal error Cause value No. 57 (bearer capability not authorized) 500 Server Internal error Cause value No. 58 (bearer capability not presently) 500 Server Internal error Cause value No. 63 (service option not available, unspecified) (class default) 500 Server Internal error Cause value in the Class 100 (service or option not implemented, cause value No.'s. 65, 70 and 79) 79 is class default 500 Server Internal error Cause value No. 88 (incompatible destination) 404 Not Found Cause value No. 91 (invalid transit network selection) 500 Server Internal error Cause value No. 95 (invalid message) (class default) 500 Server Internal error Cause value No. 97 (Message type non-existent or not implemented) 500 Server Internal error Cause value No. 99 (information element/parameter non-existent or not implemented)) 480 Temporarily unavailable Cause value No. 102 (recovery on timer expiry) 500 Server Internal error Cause value No. 110 (Message with unrecognized Parameter, discarded) 500 Server Internal error Cause value No. 111 (protocol error, unspecified) (class default) 480 Temporarily unavailable Cause value No. 127 (interworking unspecified) (class default) NOTE: Class 1 and class 2 have the same default value.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.1.2.6 Sending of the DSS1 INFO (Optional)
|
If overlap signalling is supported between the AGCF/VGW and the terminating PES Application Server the overlap signalling method used, either the Multiples INVITES method or the IN-Dialog method as described within annexes D and E is dependent on national or network operator option. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 42
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2 Supplementary services
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.0 General statement to supplementary service interworking
|
This clause discusses the impact of supplementary services on the AGCF/VGW. Table 5.2.0-1 lists the supplementary services covered and the corresponding references to the PES simulation service specifications. Table 5.2.0-1: PES Simulation Supplementary Services Supplementary Service Reference Communication Hold (HOLD) [10] Connected Line Identification Presentation (COLP) & Connected Line Identification Restriction (COLR) [7] Calling Line Identification Presentation (CLIP) & Calling Line Identification Restriction (CLIR) [6] Conference Call (CONF) [9] Communication Diversion Services (CDIV) [8] Malicious Call Identification (MCID) [46] Explicit Call Transfer (ECT) [36] Subaddressing (SUB) - Closed User Group (CUG) [62] User-to-User Signalling (UUS) - Communication Waiting (CW) [58] Terminal Portability (TP) Three Party (3PTY) [9] Completion of Communications to Busy Subscriber (CCBS) & Completion of Communications by No Reply (CCNR) [59] Advice of Charge (AOC) [31] Message Waiting Indication (MWI) [26]
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1 Communication Hold (HOLD)
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.1 Actions at the Incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.1.1 Notification received from the network
|
Table 5.2.1.1.1-1: HOLD notification INVITE/UPDATE→ NOTIFY→ SDP: a=sendonly/inactive Notification indicator information element Notification description sendonly/inactive 111 1001 Remote hold sendreceive 111 1010 Remote retrieval
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.1.2 Invocation at coincident S and T reference point
|
Table 5.2.1.1.2-1: HOLD invocation ←INVITE/UPDATE ←Message received from the DSS 1 SDP: a=sendonly/inactive sendonly/inactive HOLD sendreceive RETRIEVE ETSI ETSI TS 183 036 V3.7.1 (2021-02) 43
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.1.3 Notification received at T reference point
|
A HOLD notification may be received at T reference point in the active phase of the call. Table: 5.2.1.1.3-1: Receipt of a HOLD notification from a private network ←INVITE/UPDATE ←NOTIFY SDP: a=sendonly/inactive Notification indicator information element Notification description sendonly/inactive 111 1001 Remote hold sendreceive 111 1010 Remote retrieval
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.2 Actions at the outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.2.1 Notification received from the network
|
Table 5.2.1.2.1-1: Receipt of HOLD notification from the network ←NOTIFY ←INVITE/UPDATE Notification indicator information element SDP: a=sendonly/inactive Notification description 111 1001 Remote hold sendonly/inactive 111 1010 Remote retrieval sendreceive
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.2.2 Invocation at coincident S and T reference point
|
Table 5.2.1.2.2-1: HOLD invocation INVITE/UPDATE→ Message received from the DSS 1 → SDP: a=sendonly/inactive HOLD sendonly/inactive RETRIEVE sendreceive
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.1.2.3 Notification received at T reference point
|
A HOLD notification may be received at T reference point in the active phase of the call. Table 5.2.1.2.3-1: Receipt of a HOLD notification from a private network NOTIFY→ INVITE/UPDATE→ Notification indicator information element SDP: a=sendonly/inactive Notification description 111 1001 Remote hold sendonly/inactive 111 1010 Remote retrieval sendreceive ETSI ETSI TS 183 036 V3.7.1 (2021-02) 44 5.2.2 Connected Line Identification Presentation (COLP)/Connected Line Identification Restriction (COLR)
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.1 Actions at the incoming AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.1.0 General statement to TIP
|
If the Initial INVITE is received and the Supported header contains the "from-change" tag, then the P-Asserted-Identity in the 200 OK INVITE or UPDATE request and the changed From header in the UPDATE are sent as described in tables 5.2.2.1.1-1 and 5.2.2.1.1-2.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.1.1 Connected Line Identification Presentation (COLP)
|
The AGCF/VGW shall sent first a 200 OK INVITE including an option tag "from-change" and after then an UPDATE request as shown in table 5.2.2.1.1-1 according the rules of IETF RFC 4916 [50]. 200 OK and UPDATE is sent on the Mw interface Table 5.2.2.1.1-1: Connected number interworking applies at Mw interface ←200 OK INVITE ←CONNECT ←UPDATE Connected number IE Numbering plan identification Type of number No "from-change" tag in the supported header P-Asserted-Identity containing the value saved from the P-Called- Party-ID header that was received in the INVITE request. No UPDATE No or invalid (see note 1) connected number information element No "from-change" tag in the supported header No UPDATE ISDN/telephony numbering plan unknown or Unknown P-Asserted-Identity with a value, including the display name if previously stored during registration representing the terminating user indicated in the connected number. Address digits No "from-change" tag in the supported header No UPDATE ISDN/telephony numbering plan Subscriber number or Unknown P-Asserted-Identity with a value, including the display name if previously stored during registration representing the terminating user indicated in the connected number. Address digits "from-change" tag in the supported header ISDN/telephony numbering plan National number or Unknown P-Asserted-Identity with a value, including the display name if previously stored during registration representing the terminating user indicated in the connected number. Userinfo of the changed From header derived from the Address digits in the format: sip: local-number-digits = Address digits; phone- context=xxxxxx@hostportion; user=phone (see note 2). Address digits ETSI ETSI TS 183 036 V3.7.1 (2021-02) 45 ←200 OK INVITE ←CONNECT ←UPDATE Connected number IE Numbering plan identification Type of number "from-change" tag in the supported header ISDN/telephony numbering plan international number or unknown P-Asserted-Identity with a value, including the display name if previously stored during registration representing the terminating user indicated in the connected number. Userinfo of the changed From header derived from the Address digits in the format: sip: global -number-digits = Address digits@hostportion; user=phone. Address digits NOTE 1: Validity conditions of the connected number information element are defined in clause 5.5.2.3/Recommendation ITU-T Q.931 [54]. NOTE 2: The combination of dialled digits and phone-context parameter shall globally unique in the network as defined in IETF RFC 3966 [47]. If the "from-change" tag in the Supported header in the Initial INVITE is not received, then no UPDATE is sent. A P-Asserted-Identity header with the value saved from the P-Called-Party-ID header that was received in the request is contained in the 200 OK (INVITE). Connected subaddress If provided, the connected subaddress is transported in the changed From header field of the UPDATE request. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 46 200 OK and UPDATE is sent on the Gm interface Table 5.2.2.1.1-2: Connected number interworking applies at Gm interface ←200 OK INVITE ←CONNECT ←UPDATE Connected number IE Numbering plan identification Type of number No "from-change" tag in the supported header No UPDATE No or invalid (see note 1) connected number information element No "from-change" tag in the supported header No UPDATE ISDN/telephony numbering plan unknown or Unknown Address digits No "from-change" tag in the supported header No UPDATE ISDN/telephony numbering plan Subscriber number or Unknown Address digits ISDN/telephony numbering plan National number or Unknown Userinfo of the changed From header derived from the Address digits in the format: sip: local-number-digits = Address digits; phone- context=xxxxxx@hostportion; user=phone (see note 2) Address digits "from-change" tag in the supported header ISDN/telephony numbering plan international number or unknown Userinfo of the changed From header derived from the Address digits in the format: sip: global -number-digits = Address digits @hostportion; user=phone Address digits NOTE 1: Validity conditions of the connected number information element are defined in clause 5.5.2.3/Recommendation ITU-T Q.931 [54]. NOTE 2: The combination of dialled digits and phone-context parameter shall globally unique in the network as defined in IETF RFC 3966 [47]. Connected subaddress If provided, the connected subaddress is transported in the changed From header field of the UPDATE request.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.1.2 Connected Line Identification Restriction (COLR)
|
Table 5.2.2.1.2-1: Coding of the Privacy header field ←200 OK INVITE ←CONNECT Privacy header field Connected number information element Presentation indicator "id", "header", "user" Presentation restricted No Privacy header Absent "none" Presentation allowed ETSI ETSI TS 183 036 V3.7.1 (2021-02) 47
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.2 Actions at the outgoing AGCF/VGW
| |
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.2.1 Connected Line Identification Presentation (COLP)
|
NOTE: Depending on national regulations, some networks may define categories of subscribers that have the ability to override the presentation restriction and have the connected party's ISDN number, and subaddress information (if any) presented (e.g. the police). The ability to override the presentation restriction and the protocol to support such a service is a national matter. The option tag "from-change" is added to the supported header in the initial INVITE. Only one connected number information element is sent in the CONNECT message. If a 200 OK final response including the option tag "from-change" is received then TTIR1 shall be started if P-Asserted-Identify value is in the format of a tel URI or sip URI and no Privacy (including Privacy value of none) is present. In this case the interworking as described in tables 5.2.2.2.1-1 and 5.2.2.2.1-3 applies. The 200 OK INVITE to a CONNECT shall be held up till the UPDATE containing the changed From and To information is received and timer TTIR1 is running ELSE the 200 OK INVITE shall be mapped immediately as described within tables 5.2.2.2.1-1 and 5.2.2.2.1-2. At expiry of TTIR1 the 200 OK INVITE shall be mapped as described in table 5.2.2.2.1-2. If no P-Asserted-Identity header was received and no Privacy "id" or "header" was received in the 200 OK final response this is assumed as the originating user has not subscribed the COLP service. If several responses contain a P-Asserted-Identity header field, only the latest received P-Asserted-Identity header should be used for a Connected number sent in a CONNECT message to the calling user. Table 5.2.2.2.1-1: COLP information sent to the calling user ←CONNECT ←200 OK INVITE COLP information sent to the calling user P-Asserted-Identity Privacy header Supported header Connected number IE (see table 5.2.2.2.1-2) Userinfo in the format of a tel URI No Privacy present or Priv. value none No "from-change" Connected number IE (see table 5.2.2.2.1-3) Userinfo in the format of a tel URI No Privacy present or Priv. value none "from-change" Connected number IE Type of number Unknown Numbering plan Unknown Presentation ind. Presentation restricted Screening ind. Network provided Number digits No digit Not present id or header Value non- significant No Connected number IE No P-Asserted-Identity header field no Privacy present Value non- significant If the P-Asserted-Identity header is received at the AGCF/VGW it is assumed that the originating user subscribes the COLP supplementary service. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 48 Table 5.2.2.2.1-2: Coding of the connected number information element according to the P-Asserted-Identity header field ←CONNECT ←200 OK INVITE Connected number IE P-Asserted-Identity Type of number (see note) National number International number userinfo sip: local-number-digits; phone-context=nat @hostportion; user=phone sip: global-number-digits@hostportion; user=phone Numbering plan identification ISDN/Telephony numbering plan Presentation indicator Presentation allowed Screening indicator Network provided Number digits derived from the userinfo. In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number NOTE: As a network option, the type of number may be coded unknown when a prefix is added to the number. Table 5.2.2.2.1-3: Coding of the connected number information element according to the changed From header ←CONNECT ←UPDATE Connected number IE From header Type of number (see note) National number International number userinfo sip: local-number-digits; phone-context=nat @hostportion; user=phone sip: global-number-digits@hostportion; user=phone Numbering plan identification ISDN/Telephony numbering plan Presentation indicator Presentation allowed Screening indicator User provided, not verified Number digits derived from the userinfo. In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number NOTE: As a network option, the type of number may be coded unknown when a prefix is added to the number. Connected subaddress Table 5.2.2.2.1-4: Sending of the connected subaddress ←CONNECT ←UPDATE Content Changed From isub parameter Privacy header Connected subaddress information element Connected subaddress address string absent or not "id" No connected subaddress information element Connected subaddress address string "id" or "header" or No connected number parameter NOTE: As a national option, the presentation restriction indication received in the connected number parameter can be overridden for specific calling access' categories. In such a case, the same actions are taken as if presentation allowed was received. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 49
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.2.2.2 Connected line identification restriction (COLR)
|
See table 5.2.2.2.1-1. 5.2.3 Calling line Identification Presentation (CLIP)/Calling line Identification Restriction (CLIR)
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.3.1 Actions at the incoming AGCF/VGW
|
Table 5.2.3.1-1: Mapping of SIP From/P-Asserted-Identity/ Privacy header fields to CLI parameters INVITE→ SETUP→ P-Asserted-Identity From header Privacy Coding of the calling party number information element Absent Value not significant (see note) No Privacy header No Calling number IE Absent "Anonymous" <sip:anonymous@anonymo us.invalid> "Id" or "Header" or "user" See table 5.2.3.1-3 Absent "Unavailable" <"sip:unavailable@unknown .invalid> No Privacy header or the header has other values than "Id" or "Header" or "user" See table 5.2.3.1-2 User portion is in the format of a tel URI User portion is not in the format of a tel URI No Privacy header or the header has other values than "Id" or "Header" or "user" See table 5.2.3.1-4 User portion is in the format of a tel URI User portion is not in the format of a tel URI "Id" or "Header" or "user" See table 5.2.3.1-3 The user portion of the P-Asserted-Identity and the user portion of the From header are in the format of a tel URI and the user portion of the P-Asserted-Identity is not equal to the user portion of the From header No Privacy header or the header has other values than "Id" or "Header" or "user" The calling party number information element is repeated. As specified in ETSI EN 300 899-1 [2] clause 3.1.2.3 and ETSI EN 300 092-1 [16], clause B.2.1, the first calling party number IE is sent encoded according to table 5.2.3.1-5 and the second according to table 5.2.3.1-4 The user portion of the P-Asserted-Identity and the user portion of the From header are in the format of a tel URI and the user portion of the P-Asserted-Identity is equal to the user portion of the From header No Privacy header or the header has other values than "Id" or "Header" or "user" See table 5.2.3.1-4 User portion is in the format of a tel URI User portion is in the format of a tel URI "Id" or "Header" or "user" See table 5.2.3.1-3 NOTE: The Application Server may as a network option set the contents of the From header to a default non-significant value which is different from the values in the list below: From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag= xxxxxxx. From: "Unavailable" <"sip:unavailable@unknown.invalid>;tag= xxxxxxx. If no P-Asserted-Identity header is received at the AGCF/VGW it is assumed that the terminating user does not subscribe the CLIP supplementary service. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 50 Table 5.2.3.1-2: Calling party number not presented due to interworking to the called user Calling party number IE Type of number Unknown Numbering plan identification Unknown Presentation indicator Not available due to interworking Screening indicator Network provided Number digits No digits Table 5.2.3.1-3: Calling party number not presented due to presentation restriction to the called user Calling party number IE Type of number Unknown Numbering plan identification Unknown Presentation indicator Presentation restricted Screening indicator Network provided Number digits No digits Table 5.2.3.1-4: Coding of the calling party number information element according to the P-Asserted-Identity header field INVITE→ SETUP→ P-Asserted-Identity header Calling party number IE sip: local-number-digits; phone-context=nat @hostportion; user=phone Type of number (see note 1) National number sip: global-number-digits@hostportion; user=phone Type of number (see note 1) International number Numbering plan identification ISDN/Telephony numbering plan Presentation indicator Presentation allowed If the userinfo of the From header field is equal to the userinfo in the P-Asserted-Identity (see note 2) Screening indicator User provided, verified and passed If the userinfo of the From header field is not equal to the userinfo in the and P-Asserted-Identity (see note 2) Screening indicator Network provided Number digits are derived from user portion. In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number" NOTE 1: As a network option, the type of number may be coded unknown when a prefix is added to the number. NOTE 2: ETSI TS 129 163 [1], as a network option, the AGCF may support "Calling number verification using signature verification and attestation information" feature as described in IETF RFC 8224 [63] and ETSI TS 124 229 [5]. If the AGCF received a "verstat" tel URI parameter (defined in ETSI TS 124 229 [5], clause 7.2A.20) in the P-Asserted-Identity header filed the AGCF may map the "verstat" tel URI parameter to the Screening Indicator field as follows: - the value "No-TN-Validation" to the value "user provided, not verified"; - the value "TN-Validation-Passed" to the value "user provided, verified and passed"; and - the value "TN-Validation-Failed" to the value "user provided, verified and failed". ETSI ETSI TS 183 036 V3.7.1 (2021-02) 51 Table 5.2.3.1-5: Coding of the calling party number information element according to the From header field INVITE→ SETUP→ From header field Calling party number IE sip: local-number-digits; phone-context=nat @hostportion; user=phone Type of number (see note) National number sip: global-number-digits @hostportion; user=phone Type of number (see note) International number Numbering plan identification ISDN/Telephony numbering plan Presentation indicator Presentation allowed Screening indicator User provided, not verified Number digits are derived from user portion. In case for global number and the country code is the same as the AGCF/VGW or line is located, the country code is removed from the number of the Type of number is set to "national number" NOTE: As a network option, the type of number may be coded unknown when a prefix is added to the number.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.3.2 Actions at the outgoing AGCF/VGW
|
Actions at the Gm interface Table 5.2.3.2-1: Mapping CLI parameters to SIP header fields - Gm interface SETUP→ INVITE→ Presentation Restriction Indicator P-Preferred-Identity header field From header field: Privacy header field Privacy value Presentation restricted Addr-spec is derived from Calling Party Number parameter Address Signals (see note 1) Addr-spec is derived from Calling Party Number parameter Address Signals or (see note 2) "anonymous@anonymous.invalid" Y "id" and "header" and "user" Presentation restricted (see note 3) Default registered public identity associated with calling party is used "unavailable@unknown.invalid" Y "id" and "header" and "user" Absent Default registered public identity associated with calling party is used "unavailable@unknown.invalid" N/Y (see note 2) If present: "id" and "header" and "user" Allowed Addr-spec is derived from Calling Party Number parameter Address Signals (see note 1) Addr-spec is derived from Calling Party Number parameter Address Signals (see note 1) Y "none" NOTE 1: Mapping CLI parameters to SIP header fields see table 5.2.3.2-3. NOTE 2: As network option. NOTE 3: Calling party number available but number digits are not included. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 52 Actions at the Mw interface Table 5.2.3.2-2: Mapping CLI parameters to SIP header fields - Mw interface SETUP→ INVITE→ Presentation Restriction Indicator P-Asserted-Identity header field From header field Privacy header field Privacy value Presentation restricted Addr-spec: calling party number address signal is matched with one of the public user identities else if no matched the default public user identity is used Addr-spec is derived from Calling Party Number parameter Address Signals or (see note 2) "anonymous@anonymous.invalid" Y "id" and "header" and "user" Presentation restricted (see note 3) Addr-spec is the default public user identity "unavailable@unknown.invalid" Y "id" and "header" and "user" Absent Addr-spec is the default public user identity "unavailable@unknown.invalid" N/Y (see note 2) If present: "id" and "header" and "user" Allowed Addr-spec: calling party number address signal is matched with one of the public user identities else if no matched the default public user identity is used (see note 1) Addr-spec is derived from Calling Party Number parameter Address Signals (see note 1) Y "none" NOTE 1: Mapping CLI parameters to SIP header fields see table 5.2.3.2-3. NOTE 2: As network option. NOTE 3: Calling party number available but number digits are not included. Table 5.2.3.2-3: Mapping CLI parameters to SIP header fields at the Gm interface SETUP→ INVITE→ Calling party number IE From Header Field P-Preferred-Identity Type of number Numbering plan identification No or invalid (see note 1) calling party number information element See table 5.2.3.2-1 See table 5.2.3.2-1 National number ISDN/telephony numbering plan or Unknown See note 3 The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 2) An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. (see note 4) International number The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone (see note 4) ETSI ETSI TS 183 036 V3.7.1 (2021-02) 53 SETUP→ INVITE→ Calling party number IE From Header Field P-Preferred-Identity Type of number Numbering plan identification Subscriber The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 2) An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. (see note 4) Unknown The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 2) An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. (see note 4) NOTE 1: Validity conditions of the calling party number information element are defined in clause 3.5.2.2.1/Recommendation ITU-T Q.931 [54]. NOTE 2: The combination of dialled digits and phone-context parameter shall be globally unique in the network as defined in IETF RFC 3966 [47]. NOTE 3: If the calling party number information element is received with a coding of the numbering plan identifier field other than "ISDN/telephony numbering plan (Recommendation ITU-T E.164 [i.6] and Recommendation ITU-T E.163 [i.7])" or "unknown", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 4: The DDI supplementary service shall be provided after prior arrangement with the network provider. If this option is used, the proper operation of the DDI supplementary service may require a bilateral agreement between the public network and the private network on the starting point of partial numbers in relation to the full ISDN number and configuration within the private network [15]. To ensure the transport of the DDI as part of the calling party number to the called user, the VGW should evaluate the type of number (TON) and depending on the result compare received numbers with one of the registered public user identities. If the full ISDN number or the partial numbers (e.g. NDC+SN+DDI; SN+DDI; DDI) matches with the default registered public identity (the full ISDN number), the DDI and the default registered public identity will be used in the P-Preferred-Identity. If they is no match, only the default registered public identity shall be used. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 54 Table 5.2.3.2-4: Mapping CLI parameters to SIP header fields at the Gm interface if special arrangement applies (network option) SETUP→ INVITE→ Calling party number IE From Header Field P-Preferred-Identity Type of number Numbering plan identification No or invalid (see note 1) calling party number information element See table 5.2.3.2-1 See table 5.2.3.2-1 National number ISDN/telephony numbering plan or Unknown See note 3 The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 2) An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. See note 5 International number The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone An attempt is made to match the address string of the calling party number IE to one of the calling party's registered public identities. If no match is determined, a default registered public identity is used. The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone See note 5 Subscriber See note 4 "unavailable@unknown.invalid" The default registered public identity shall be used. See note 5 Unknown See note 4 "unavailable@unknown.invalid" The default registered public identity shall be used. See note 5 NOTE 1: Validity conditions of the calling party number information element are defined in clause 3.5.2.2.1/Recommendation ITU-T Q.931 [54]. NOTE 2: The combination of dialled digits and phone-context parameter shall be globally unique in the network as defined in IETF RFC 3966 [47]. NOTE 3: If the calling party number information element is received with a coding of the numbering plan identifier field other than "ISDN/telephony numbering plan (Recommendation ITU-T E.164 [i.6] and Recommendation ITU-T E.163 [i.7])" or "unknown", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 4: If a special arrangement applies and If the calling party number information element is received with the coding of the type of number field other than "national number" or "international number", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 5: The DDI supplementary service shall be provided after prior arrangement with the network provider. If this option is used, the proper operation of the DDI supplementary service may require a bilateral agreement between the public network and the private network on the starting point of partial numbers in relation to the full ISDN number and configuration within the private network [15]. To ensure the transport of the DDI as part of the calling party number to the called user, the VGW should evaluate the type of number (TON) and depending on the result compare received numbers with one of the registered public user identities. If the full ISDN number or the partial numbers (e.g. NDC+SN+DDI; SN+DDI; DDI) matches with the default registered public identity (the full ISDN number), the DDI and the default registered public identity will be used in the P-Preferred-Identity. If they is no match, only the default registered public identity shall be used. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 55 Table 5.2.3.2-5: Mapping CLI parameters to SIP header fields at the Mw interface SETUP→ INVITE→ Calling party number IE From Header Field P-Asserted-Identity Type of number Numbering plan identification No or invalid (see note 1) calling party number information element See table 5.2.3.2-2 See table 5.2.3.2-2 National number ISDN/telephony numbering plan or Unknown See note 4 The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 3) See note 2 See note 5 International number The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone See note 2 See note 5 Subscriber The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone-context=xxxxxx @hostportion; user=phone (see note 3) See note 2 See note 5 Unknown The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 3) See note 2 See note 5 NOTE 1: Validity conditions of the calling party number information element are defined in clause 3.5.2.2.1/Recommendation ITU-T Q.931 [54]. NOTE 2: When the AGCF receives a SETUP with a Calling party number that matches one of the registered public user identities, the AGCF will insert this public user identity in the P-Asserted-Identity as a result of applying the procedures defined for a UE and the P-CSCF. When the AGCF receives a SETUP with a Calling party number that does not match one of the registered public user identities, or the SETUP does not contain a Calling party number, the AGCF will insert the registered public user identity in the P-Asserted-Identity header. NOTE 3: The combination of dialled digits and phone-context parameter shall be globally unique in the network as defined in IETF RFC 3966 [47]. NOTE 4: If the calling party number information element is received with a coding of the numbering plan identifier field other than "ISDN/telephony numbering plan (Recommendation ITU-T E.164 [i.6] and Recommendation ITU-T E.163 [i.7])" or "unknown", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 5: The DDI supplementary service shall be provided after prior arrangement with the network provider. If this option is used, the proper operation of the DDI supplementary service may require a bilateral agreement between the public network and the private network on the starting point of partial numbers in relation to the full ISDN number and configuration within the private network [15]. To ensure the transport of the DDI as part of the calling party number to the called user, the AGCF should evaluate the type of number (TON) and depending on the result compare received numbers with one of the registered public user identities. If the full ISDN number or the partial numbers (e.g. NDC+SN+DDI; SN+DDI; DDI) matches with the default registered public identity (the full ISDN number), the DDI and the default registered public identity will be used in the P-Asserted-Identity. If they is no match, only the default registered public identity shall be used. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 56 Table 5.2.3.2-6: Mapping CLI parameters to SIP header fields at the Mw interface if special arrangement applies (network option) SETUP→ INVITE→ Calling party number IE From Header Field P-Asserted-Identity Type of number Numbering plan identification No or invalid (see note 1) calling party number information element See table 5.2.3.2-2 See table 5.2.3.2-2 National number ISDN/telephony numbering plan or Unknown See note 4 The userinfo is derived from the address string of the calling party number IE sip: local-number-digits; phone- context=xxxxxx@hostportion; user=phone (see note 3) See note 2 See note 6 International number The userinfo is derived from the address string of the calling party number IE sip: global-number-digits @hostportion; user=phone See note 2 See note 6 Subscriber See note 5 "unavailable@unknown.invalid" The default registered public identity shall be used. See note 6 Unknown See note 5 "unavailable@unknown.invalid" The default registered public identity shall be used. See note 6 NOTE 1: Validity conditions of the calling party number information element are defined in clause 3.5.2.2.1/Recommendation ITU-T Q.931 [54]. NOTE 2: When the AGCF receives a SETUP with a Calling party number that matches one of the registered public user identities, the AGCF will insert this public user identity in the P-Asserted-Identity as a result of applying the procedures defined for a UE and the P-CSCF. When the AGCF receives a SETUP with a Calling party number that does not match one of the registered public user identities, or the SETUP does not contain a Calling party number, the AGCF will insert the registered public user identity in the P-Asserted-Identity header. NOTE 3: The combination of dialled digits and phone-context parameter shall be globally unique in the network as defined in IETF RFC 3966 [47]. NOTE 4: If the calling party number information element is received with a coding of the numbering plan identifier field other than "ISDN/telephony numbering plan (Recommendation ITU-T E.164 [i.6] and Recommendation ITU-T E.163 [i.7])" or "unknown", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 5: If a special arrangement applies and If the calling party number information element is received with the coding of the type of number field other than "national number" or "international number", then the network shall discard the calling party number information element and process the call as if that information element was not received. NOTE 6: The DDI supplementary service shall be provided after prior arrangement with the network provider. If this option is used, the proper operation of the DDI supplementary service may require a bilateral agreement between the public network and the private network on the starting point of partial numbers in relation to the full ISDN number and configuration within the private network [15]. To ensure the transport of the DDI as part of the calling party number to the called user, the AGCF should evaluate the type of number (TON) and depending on the result compare received numbers with one of the registered public user identities. If the full ISDN number or the partial numbers (e.g. NDC+SN+DDI; SN+DDI; DDI) matches with the default registered public identity (the full ISDN number), the DDI and the default registered public identity will be used in the P-Asserted-Identity. If they is no match, only the default registered public identity shall be used.
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.4 Conference calling (CONF)
|
This service is for further study. ETSI ETSI TS 183 036 V3.7.1 (2021-02) 57
|
f51d9e0ffee2862bfeb29fc49a01bf46
|
183 036
|
5.2.5 Communication Diversion Services (CDIV)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.