hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1 Non IMS capable CNDs
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.2 Non-IP CNDs
|
The non-IP devices include the POTS phone and ISDN devices; these type of devices can be connected to the NGN through the CNG or directly. In any case, the architecture of these devices is out of scope of the present document. The voice services on POTS/ISDN devices can be done in emulation [1], [2] and [3] or simulation mode on NGN. In next clause the impact on customer premises network is analyzed for both modes.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.2.1 Non-IP CNDs connected to the NGN without a CNG
|
In this case the POTS and ISDN device is connected to the MG (Media Gateway) [3] via the Z interface for voice services, as shown in figure 4.1. In case of data services, for ISDN device, the S/T interface is needed. The case of voice services for POTS/ISDN in PES scenario is shown in figure 4.1. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 12 Figure 4.1: Non-IP CNDs connected to the NGN network without a CNG (PES scenario) The case of voice services for POTS/ISDN supported in the Core IMS scenario is shown in figure 4.2. Figure 4.2: Non-IP CNDs connected to the NGN network without a CNG (Core IMS scenario)
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.2.2 Non-IP CNDs connected to the NGN through a CNG
|
In this case, the CNG includes all the CPN functionalities necessary to fulfil a service between the analogue or ISDN phone and the NGN network. The voice services can be based on PES or Core IMS scenario. The details of CNG architecture are specified in TS 185 003 [6]. IMS Core Customer Premises Network POTS Z Gm CNG FXS FXS IMS Core IMS Core Customer Premises Network POTS Z Gm CNG FXS FXS Figure 4.3: Non-IP CNDs connected to the NGN network trough a CNG (Core IMS scenario) IMS Core Customer Premises Network POTS ISDN VGW VGW S/T Z Gm Gm TISPAN PSTN/ISDN Emulation Subsystem Customer Premises Network POTS ISDN AGF S/T Z AGW MGW ETSI ETSI TS 185 006 V2.3.1 (2009-05) 13 TISPAN PSTN/ISDN Emulation Subsystem Customer Premises Network POTS Z a CNG FXS FXS TISPAN PSTN/ISDN Emulation Subsystem Customer Premises Network POTS Z a CNG FXS FXS Figure 4.4: Non-IP devices connected to the NGN network trough a CNG (PES scenario) In order to support the Z interfaces on FXS ports the CNG shall support protocol conversion as defined in TS 185 003 [6].
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.3 IP CNDs
|
These devices are able to get IP connectivity within the CPN, but they are not implementing the RFC 3261 [10] functionalities to manage signalling. This can be a communication device non compliant with RFC 3261 [10], but also devices not specifically devoted to communication services (for example: webcam with HTTP server, general purpose PC, etc.).
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.4 SIP IETF capable CNDs
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.4.1 Non-IMS SIP CND connected to the NGN through a CNG
|
A non-IMS SIP IETF device shall utilize the Gm' reference point (instead of the Gm reference point that is utilized by IMS capable devices) in order to get a service from NGN-IMS. See figure 4.5. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 14 CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P-CCSF CNGCF ARF Gm e3 e1 Customer Network Gateway CNG-User Interface Function (CNG-UIF) e3' e1' Access node Dj CND-SIP UA CND-NAPT Traversal Function (CND-NTF) CND-Communication Services Media Function (CND-CSMF) u CNG-Location Function (CNG-LF) AS Ut Ut au CNG-Attachment Function (CNG-AtF) CND CNG-Plug and Play Function (CNG-PPF) C CND-Local Authentication Function (CND-LAF) CND-Configuration & Management Function (CND-CMF) CND-Attachment Function (CND-AtF) CND-Self Provisioning (CND-SP) Customer Application Customer Application Customer Application Gm' CNG-Authentication Function (CNG-AuF) CNG-Policy Control Function (CNG-PCF) CNG-Configuration & Management Function (CNG-CMF) CNG-AdmissionControlFunction (CNG-ACF) Gm CNG-NAPT and Firewall Function (CNG-NFF) e3 B2BUA CNG- SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e1 SIP/IMS Adapter ISIM UICC CNG-IPTV Functions (CNG-IPTVF) CND-Plug and Play Function (CND-PPF) Figure 4.5: SIP IETF CND connected to the NGN-IMS network through a CNG
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.1.5 Consumer Electronics
|
These types of CNDs are out of scope. The case of CND correlated to IPTV is detailed in TS 185 009 [i.1].
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.2 IMS capable CNDs
|
4.2.1 IMS Customer Network Device connected to the NGN through a CNG In this case, the Customer Network Device includes all the service-related functionalities necessary to fulfil a service between itself and the NGN-IMS network, as shown in figure 4.6. The CNG offers the capabilities to support attachment and transport in case of IMS customer device connected via Wi-Fi/Bluetooth, Ethernet port (wired) or femto cell (for mobile devices). ETSI ETSI TS 185 006 V2.3.1 (2009-05) 15 CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P-CCSF CNGCF ARF Gm e3 e1 Customer Network Gateway CNG-User Interface Function (CNG-UIF) e3' e1' Access node Dj CND-SIP UA CND-NAPT Traversal Function (CND-NTF) CND-Communication Services Media Function (CND-CSMF) u CNG-Location Function (CNG-LF) AS Ut Ut au CNG-Attachment Function (CNG-AtF) CND CNG-Plug and Play Function (CNG-PPF) CND-Plug and Play Function (CND-PPF) C CND-Local Authentication Function (CND-LAF) CND-Configuration & Management Function (CND-CMF) CND-Attachment Function (CND-AtF) CND-Self Provisioning (CND-SP) Customer Application Customer Application Customer Application Gm' CNG-Authentication Function (CNG-AuF) CNG-Policy Control Function (CNG-PCF) CNG-Configuration & Management Function (CNG-CMF) CNG-AdmissionControlFunction (CNG-ACF) Gm CNG-NAPT and Firewall Function (CNG-NFF) e3 B2BUA CNG- SIP proxy B2BUA SIP Proxy Registrar Customer Network Device e1 ISIM UICC UICC ISIM CNG-IPTV Functions (CNG-IPTVF) Gm Figure 4.6: IMS CND connected to the NGN-IMS network through a CNG
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.2.2 Consumer Electronics
|
The definition of consumer electronics architecture is out of scope for the present document. The architecture of CND involved in IPTV services are covered in TS 185 009 [i.1]
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.3 IMS customer network device architecture
|
In the following clause a detailed description of the entities on figure 4.6 is given. 4.3.1 The Customer Network Devices- Network Attachment Subsystem entities (CND-NASS) CND-CMF: Customer Network Device - Configuration and Management Function. The CND-CMF entity shall enable the configuration of CND based on data obtained from the CNGCF. The CNG-CMF (in CNG) should be able particularly to store configuration information dedicated to several CNDs, after sending only one request to the CNGCF. As soon as one CND is connected, the CNG-CMF should be able to deliver configuration parameters to it is CND-CMF. Otherwise the CND-CMF can be directly accessed by the CNGCF without the CNG mediation. The CND-CMF shall manage a mutual authentication between the CNGCF and the CND. The CND-CMF shall enable the CND configuration and firmware upgrade. The CND-CMF shall access the credential keys for authentication (via ISIM or stored parameters received from CNGF, e.g. for HTTP digest). ETSI ETSI TS 185 006 V2.3.1 (2009-05) 16 The CND-CMF should provide, for example, the functionality and interfaces of a DSL Forum Auto Configuration Client [7]. Finally, the CND-CMF should allow device maintenance from the NGN network, through the CNG-CMF, with the opportunity to do diagnostic and performance tests too. Some authentication parameters may be stored in a UICC (containing the ISIM). CND-AtF: Customer Network Device Attachment Function. The CND-AtF entity shall store the private or public IP addresses sent by CNG-AtF or NASS (e.g. a DHCP client). CND-LAF: Customer Network Device - Local Authentication Function. The CND-LAF shall manage local authentication procedure to the CPN environment. For instance, a CND requesting for a CPN Wireless attachment should be authorized by the access point embedded in the CNG. In order to ask for local authentication the CND-LAF interacts with the CNG-AuF. The CNG-AuF can thus be configured by the user for such a case, by using the CNG User Interface Function (CNG-UIF).
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.3.2 The transfer level functions
|
CND-NTF: NAPT Traversal Function The function shall allow the CNG-NFF (in CNG) traversal (as detailed in TR 187 008 [i.3]) and particularly maintain the binding between the SIP UA and the P-CSCF/C-BGF. The CND-NTF should also supply the SIP UA with the mapping made by the CNG on the NGN side so as to fill the SDP field of SIP messages sent by the CND.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
4.3.3 The transport level functions
|
CND-CSMF: Customer Network Device-Communication Services Media Function The CND-CSMF shall terminate the media flows. In some cases the media flows may be encrypted. 4.3.4 The Customer Network Devices - Service-related Functional entities (CND-SF) CND-SIP UA: Customer Network Device SIP UA This block shall implement the Gm reference points on IMS customer devices. This SIP UA shall perform the service authentication and manage signalling flows securely. CND-A: Customer Network Device Client Application At least one CND-A shall be installed on CND to support a service. There can be on or more CND-As depending on the applications installed over CND. It is a client specific for application. This client can implement local application or network services through the use of SIP UA. CND-SC: Customer Network Device Self Configuration This functionality is optional. It implements the Ut reference point; the Ut enables the access to an Application Sever to support the user in configuration updates related to services. CND-PPF: Customer Network Device - Plug and Play Function The CNG-PPF in the CNG may obtain some device information (service discovery, description) and allow their control from the CND-PPF. Particularly, the CNG-PPF entity may allow a communication between many types of Customer Device within the CPN, not only conversational (based UPnP for instance). ETSI ETSI TS 185 006 V2.3.1 (2009-05) 17
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
5 Reference Points
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
5.1 Network attachment reference points
|
e1': The e1' reference point is defined between the CND and the CNG-AtF. The CNG-AtF provides IP addresses (IPv4 or IPv6 format) to the CND through the CND-AtF, it may also send some configuration information for the CND (typically through DHCP options). The CND and CNG shall mutually exchange their hardware identities (e.g. MAC address, DeviceID, etc.) on e1' reference point. The CNG has to know which CNDs are behind itself within CPN and each CND has to know its CNG. This reference point is mandatory if the CNG runs in a routed mode. e3': The e3' reference point is defined between the CND and the CNG-CMF. The CNG-CMF may provide the CND with parameters that are pre-configured in the CNGCF and sent to the CNG through the e3 reference point or, as an alternative, directly defined by the user. The CNG-CMF also configures the CNG, using information received from the CNGCF or supplied by the user himself. The CNG-CMF also configures the CNG, it can also be provided by the CNGCF or the user himself. Finally the CND-CMF should provide information on device status to allow the CNGCF to make some diagnostic and performance tests through the CNG-CMF. To sum up, the e3' reference point support a variety of functionality to manage a collection of user equipment (CNG/CNDs), including the following capabilities: - auto-configuration and service provisioning; - software/firmware management; - status and performance monitoring; - diagnostics. This reference point is recommended as the e3 reference point could also be used. This reference point is recommended as integration of the mandatory e3 interface described below. In order to simplify the management functions on the CNG, the e3 reference point can be implemented directly between CND and CNGCF as specified in ES 282 004 [12]. In this case, the direct reference point between CND and CNG, e3', could be limited to service provisioning functions; this may be required in addition or as an alternative to the corresponding functionalities on the e3 reference point between CND and CNGCF. au: The au reference point is defined between the Customer Network Device and the CNG-AuF. There may be two types of authentication/authorization, according to: CPN pairing (attachment, encryption and security processes (WEP, WPA2 …)) based on specific CPN technologies (e.g. Wife SSID, PLC technology). Access rights for some LAN services like the CNG Configuration (through the CNG-UIF). This reference point is recommended, except if a wireless access point is embedded in the CNG in which case it is mandatory. e1: This reference point is based on TS 183 019 [13]. The e1 reference point is dedicated to the network attachment of the User Equipment. The e1 reference point is mandatory (in coherence with WG2 specifications). ETSI ETSI TS 185 006 V2.3.1 (2009-05) 18 e3: This reference point is based on ES 282 004 [12]: The e3 reference point is defined between the CNG-CMF and the CNGCF and should be extended also between the CNG-CMF and the CND for configuration purposes. Through a remote management protocol it is possible to support a variety of functionalities to manage a collection of user equipment (CNG/Customer Network Devices), including the following capabilities: - auto-configuration and service provisioning; - software/firmware management; - status and performance monitoring; - diagnostics. The e3 implementation between the CNG-CMF and the CNGCF is mandatory (in coherence with WG2 specifications), whereas the e3 implementation between the CNG-CMF and the CND-CMF is recommended, as e3' should be an alternative.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
5.2 Transport level reference points
|
Dj: The Dj reference point is responsible for the exchange of media flows between the User Equipment (CNG or CND) and the C-BGF. This reference point is mandatory. It is based on ES 282 001 [14].
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
5.3 Service layer reference points
|
Gm: The Gm reference point supports the communication between UE and the IMS, e.g. related to registration and session control. Gm between the P-CSCF and the SIP proxy B2BUA is used to support several actions: - send SIP messages to/from the NGN; - call forking at the CNG level. The protocol used for the Gm reference point is SIP. To be noticed that the definition is extracted from ES 282 007 [11]. This reference point is in line with specifications: - ES 283 003 [4]; - TS 182 012 [3]; - TS 131 103 [15]. This reference point is mandatory (in coherence with WG2 specifications). Gm': The Gm' reference point supports the communication between one CND and the CNG, e.g. related to registration and session control. The difference between Gm and Gm' is related to the conformance to the IMS and to the need to go through the B2BUA to support local services. Further details about Gm' possible implementations can be found in TR 185 007 [i.4]. This reference point is recommended (it shall be used in case a SIP B2BUA is implemented inside the CNG). ETSI ETSI TS 185 006 V2.3.1 (2009-05) 19 Ut: The Ut reference point enables the user to manage information related to his services, such a creation and assignment of Public Service Identities, management of authorization policies that are used e.g. by Presence service, conference policy management, etc. This reference point is in line with ES 282 007 [11]. This reference point is optional (in coherence with WG2 specifications, see [11]). u: The u reference point gives the possibility to one or several users authorized (via the CNG-AuF) to have access to the CNG Configuration, through the CNG-UIF. The liaison should be as secure as possible (using HTTPs for instance). This reference point is recommended. C: The C reference point is defined between the CNG-PPF and the CND-PPF. It provides some CND information (service discovery, description) to the CNG and allows its control. Also, a communication between many types of Customer Network Device within the CPN may be established through the C reference point, using UPnP for instance. This reference point is optional.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
6 Authentication issues
|
This clause is related to the authentication method used by customer network devices for registration and authentication on IMS core. The target authentication method is IMS AKA authentication based on ISIM/UICC, but in coherence with TS 187 001 [i.2] there are other two methods to be considered: HTTP Digest and NBA. For that reason in the present document customer network devices, without UICC, that support HTTP Digest and NBA are considered as early deployments. In these case of HTTP Digest or NBA a CND R2 shall be able to provide it is private and public identity in every method that requires authentication (e.g. REGISTER) in order to support shared public identity for multi device use case (shared IMPU). The CND that does not support this feature can be extended through a CNG. In order to clarify the concept of early deployments some schemas are presented.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
6.1 CNG based
|
In case of CNG in the CPN, the CNG can be add the private identity in the Authorization Header ES 283 003 [4], if needed, both for HTTP Digest and NBA authentication method. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 20 CNG CND IMS capable (early deploy) Auth Http Digest NGN REGISTER((IMPU, IMPI, Authorization head. mandatory) CND Non IMS capable SIP IETF CNG REGISTER (local SIP URI) NGN REGISTER (IMPU, IMPI, CNG add Authorization head.) Http Digest Http Digest Http Digest CND Non IMS capable POTS, ISDN, H.323, H.248 CNG NGN 401 Unauthorized (Challenge nonce) R2 CNG SIP Proxy B2BUA 401 Unauthorized (Challenge nonce …) CNG SIP Proxy B2BUA TA REGISTER (IMPU, IMPI, response) 200 OK 200 OK REGISTER (IMPU, IMPI, CNG add Authorization head.) Http Digest 401 Unauthorized (Challenge nonce) REGISTER (IMPU, IMPI, response) 200 OK REGISTER (IMPU, IMPI, response …) 200 OK CNG CND IMS capable (early deploy) Auth Http Digest NGN REGISTER((IMPU, IMPI, Authorization head. mandatory) CND Non IMS capable SIP IETF CNG REGISTER (local SIP URI) NGN REGISTER (IMPU, IMPI, CNG add Authorization head.) Http Digest Http Digest Http Digest CND Non IMS capable POTS, ISDN, H.323, H.248 CNG NGN 401 Unauthorized (Challenge nonce) R2 CNG SIP Proxy B2BUA 401 Unauthorized (Challenge nonce …) CNG SIP Proxy B2BUA TA REGISTER (IMPU, IMPI, response) 200 OK 200 OK REGISTER (IMPU, IMPI, CNG add Authorization head.) Http Digest 401 Unauthorized (Challenge nonce) REGISTER (IMPU, IMPI, response) 200 OK REGISTER (IMPU, IMPI, response …) 200 OK CND IMS capable (NBA) NGN REGISTER (IMPU) R1 CNG REGISTER (IMPU, IMPI, CNG Add Authorization head.) CNG SIP Proxy B2BUA CND IMS capable (Http Digest) NGN REGISTER (IMPU) R1 CNG REGISTER (IMPU, IMPI, CNG Add Authorization head.) CNG SIP Proxy B2BUA 401 Unauthorized (Challenge nonce …..) 200 OK REGISTER (IMPU,IMPI, response) 200 OK CND IMS capable (NBA) NGN REGISTER (IMPU) R1 CNG REGISTER (IMPU, IMPI, CNG Add Authorization head.) CNG SIP Proxy B2BUA CND IMS capable (Http Digest) NGN REGISTER (IMPU) R1 CNG REGISTER (IMPU, IMPI, CNG Add Authorization head.) CNG SIP Proxy B2BUA 401 Unauthorized (Challenge nonce …..) 200 OK REGISTER (IMPU,IMPI, response) 200 OK Figure 6.1: Early Deployments with CNG In table 6.1 the functional block roles are summarized. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 21 Table 6.1: Functional block rules for authentication (CNG based) CND CND => NGN CNG NGN IMS Capable Early deployment R2 (HTTP Digest) CND sends REGISTER with authorization header including IMPI. Transparent. NGN sends 401 unauthorized and challenge the CND. Non IMS Capable SIP IETF (HTTP Digest) CND sends REGISTER without authorization header. The SIP UA (IETF) receives the REGISTER The B2BUA close the session with SIP IETF and open a new session with NGN adding the authorization head with CND's IMPI. NGN sends 401 unauthorized and challenge the CND trough the B2BUA inside the CNG. Non IMS Capable (POTS, ISDN, H323, H248) CND generates local signalling to the Terminal Adapter (TA). The B2BUA opens a new session with NGN adding the authorization head with CNG's IMPI. NGN sends 401 unauthorized and challenge the CND trough the B2BUA inside the CNG. IMS Capable R1 (NBA) CND sends REGISTER without authorization header. The B2BUA can modify the REGISTER to the NGN adding the authorization head with CND's IMPI. The NGN does not challenge the CND because NBA is used. IMS Capable R1 (HTTP Digest) CND sends REGISTER without authorization header. The B2BUA can modify the REGISTER to the NGN adding the authorization head with CND's IMPI. NGN sends 401 unauthorized and challenge the CND.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
6.2 Non CNG based
|
In case of no CNG is in CPN, for non CND R2 and non IMS capable CND it is impossible to add the Authorization Header to the message that requires authorization before the challenge, so these CNDs cannot be supported in shared IMPU use case [5]. Figure 6.2: Early Implementation without CNG in CPN ETSI ETSI TS 185 006 V2.3.1 (2009-05) 22 In table 6.2 the functional block roles are summarized: Table 6.2: Functional block rules for authentication (without CNG) CND CND => NGN NGN IMS Capable R1 (HTTP Digest) CND sends REGISTER without authorization header. NGN should support a mechanism to queries the UPSF (TR 182 005 [i.5]), discover the auth schema to be used, and sends 401 unauthorized to challenge the CND because HTTP Digest is used. Non IMS Capable SIP IEHTTPHTTP Digest) CND sends REGISTER without authorization header. NGN uses some GW to convert SIP IETF in SIP should support a mechanism to queries the UPSF, discover the auth schema to be used, and sends 401 unauthorized to challenge the CND because HTTP Digest is used. IMS Capable R1 (NBA) CND sends REGISTER without authorization header. NGN should support a mechanism to queries the UPSF, discover the auth schema to be used. The NGN does not challenge the CND because NBA is used.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
7 The CND Data Model
|
The CND should support the device data model proposed by DSL Forum, the TR-106 [9] (data model for a generic device). The CND is needed to support the set of parameters defined by DSL Forum in TR-104 [8] (data model for VoIP functionalities).
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8 Information Flows
|
NOTE: Information flows clause is non normative text reported in form of examples, to better understand the relationships between the CPN entities and functionalities.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.1 Attachment Flows
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.1.1 Example of Information Flows on e1'
|
The candidate on e1' is DHCP specified in RFC 2131 [16]. In figure 8.1 the basic information flow is given. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 23 CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack Figure 8.1: Information Flow on e1' In order to mutually exchange the hardware identities between the CND and the CNG, the hardware identity can be defined for example as in TR-069 [7] (DeviceId) and the DHCP Option 125 can be used for the CND-CNG association as specified in TR-069 [7], annex F.
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.2 Configuration and management flows
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.2.1 Example of management reference point selection
|
In this clause an example of a general way to select between e3 and e3' is given. CNG routed mode Figure 8.2 shows the routed mode scenario; the main data exchanges in this flow are the following: (1) The CNG sends on e1 the request for IP address acquiring to the NASS, on the same e1 the NASS replies with the IP address (if the CNG is authorized) and with some configuration data like CNGCF url and something else. If the phase (1) is terminated without errors the CNG is attached to the access network. (2) The CNG sends on e3 the notification for acquiring configuration data like CNG id and credentials for authentication on NGN to the CNGCF. The CNGCF can send CNDs configuration data (if e3' is used on CNG) like identities, credentials and so on. If the phase (2) is terminated without errors the CNG is configured and is certified as trusted for NGN and ready to start the registration procedure on NGN. From that point is possible to attach CNDs on CNG. (3) The CND sends on e1' the request for IP address acquiring to the CNG. More in general the CND send that request on e1'/e1 but in this case the CNG is configured in routed mode and it does not forward the request to the NASS. The CNG replies with an IP private address and with some configuration data, if available, like CNGCF url. If the phase (3) is terminated without errors the CND is attached to the CNG and indirectly to the access network. (4) If the CND supports the e3' then it sends the request for configuration data (for example identities and credentials) to the CNG. The CNG can reply with: the configuration data or not, or with error message. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 24 (5) If the CND supports the e3 then it sends the notification for configuration data to the CNGCF. The CNGCF check if the CND is already configured or not. If not, it sends configuration data. If the CND is configured via e3' then the e3 is used for monitoring, firmware upgrading and so on. If the phase (4)/(5) is terminated without errors the CND is configured and ready to start the registration procedure with NGN. Figure 8.2: Management flow with CNG routed mode CNG bridged mode In case of CNG bridged mode configuration (see figure 8.3), the phase (1) and (2) are not applicable, while the subsequent steps can be summarized in the following way: (3) The CND on e1 sends the request for IP address acquiring to the NASS. The NASS replies with the IP address and with some configuration data like CNGCF url. If the phase (3) is terminated without errors the CND is attached to the network access. (4) The CND sends the notification for configuration data to the CNGCF. The CNGCF replies with the configuration data. If the phase (4) is terminated without errors the CND is ready to start the registration procedure on the NGN. CND CND - CMF CNG CNG - CMF CND CND - CMF CNG CNG - CMF CNGCF NASS e1 (CNGCF url ) CNG Attached e3 CNG config : • only CNG id or • CNG and CND id also e1 ’ (CNGCF url ) e3 ’ If CND supports e 3 ’ then => 1. CNG doesn ’ t support e 3 ’ 2. CNG hasn ’t CND confg data 3. CNG has CND config data If CND supports e3 then => e3 If CND is already configured then nothing to do Else send config data for CND CND Attached (4) (2) (3) (1) (5) CNG Configured CND Configured CND CND - CMF CNG CNG - CMF CND CND - CMF CNG CNG - CMF CNGCF NASS e1 (CNGCF url ) CNG Attached e3 CNG config : • only CNG id or • CNG and CND id also e1 ’ (CNGCF url ) e3 ’ If CND supports e 3 ’ then => 1. CNG does n ’ t support e 3 ’ 2. CNG hasn ’t CND confg data 3. CNG has CND config data If CND supports e3 then => e3 If CND is already configured then nothing to do Else send config data for CND CND Attached (4) (2) (3) (1) (5) CNG Configured CND Configured ETSI ETSI TS 185 006 V2.3.1 (2009-05) 25 CND CND - CMF CNG CNG - CMF CND CND - CMF CNG CNG - CMF CNGCF NASS e1 (CNGCF url) CNG Attached e3 CNG config: • only CNG id e1 (CNGCF url) CND config data e3 CND Attached (2) (3) (1) (4) CND Configured CNG Configured CND CND - CMF CNG CNG - CMF CND CND - CMF CNG CNG - CMF CNGCF NASS e1 (CNGCF url) CNG Attached e3 CNG config: • only CNG id e1 (CNGCF url) CND config data e3 CND Attached (2) (3) (1) (4) CND Configured CNG Configured Figure 8.3: Management flow with CNG in bridged mode
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.2.2 Example of Information Flows on e3'
|
The following information flow is an example of service provisioning functions supported by CNG (see figure 8.4). CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Set Identity) 200 OK (GET Response) CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Set Identity) 200 OK (GET Response) Figure 8.4: Provisioning on e3' With the first HTTP GET (Ask Identity), the CND asks the CNG for the list of available identities (tuples of IMPI, IMPU, etc.), and the CNG answers with the identities list in the HTTP GET Response. Then the CND chooses one identity and, in the second HTTP GET (Set Identity), provides the choice to the CNG, that answers for confirmation in the HTTP Get Response. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 26
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.3 Signalling flows
|
The candidate on Gm' is SIP specified in RFC 3261 [10], the one on Gm is SIP specified in TS 124 229 [17] and ES 283 003 [4].
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.3.1 CND attachment and NGN registration
|
The non-IMS devices considered in this case are devices associated to the VoIP phone number of the CNG. Different kinds of devices (see table 4.1): • Fixed or Wireless SIP phone. • SIP Multi-mode (e.g. dual WI-Fi/3G phone). • SIP soft phone on PC. • Other: play station, STB, etc. These SIP devices have a local SIP identity, as defined as local SIP URI (e.g. device kitchen) or public SIP URI (e.g. John123): • The vendor provides a local SIP identity for all SIP devices. This enables "Plug and play" functionality. User does not need to configure the SIP device. By default, this local identity can be the MAC address. • The user can change the local identity provided by the vendor to another local identity. The user may also be allowed to change the local identity to a public SIP URI. The customer can change this parameterization, and select a specific name or a local phone number for each device. The attachment phase is defined in the following way (see figure 8.5): 1) In case Gm' needs to be used (for local services), the DHCP server of the CNG will return the DHCP option 120 to the CND, standardized to provision CNG SIP proxy IP address or domain-name. This option will contain the IP address of the CNG on the CPN side (ex: 192.168.1.1). 2) The device registers locally to the CNG SIP-IMS proxy. SIP REGISTER message is sent with the local SIP URI of the device. 3) So as to allow the device to communicate through the NGN, the customer can configure the association between the local SIP URI of the device (pre-configured in the device) and the CNG's IMPU, or the device can use its own IMPU (public SIP URI pre-configured in the device) to send the register through the CNG SIP proxy. In those cases only one register has to be sent from the CNG to the NGN for multiple CND IMPUs within the CPN. The authentication is handled directly by the CNG-SIP proxy B2BUA. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 27 Non-IMS IETF SIP CND CNG-B2BUA NGN REGISTER (local SIP URI ) 200 (OK) REGISTER (IMPI,IMPU, Aut_header) 200 OK Adds challenge response 401 (Unauthorized) REGISTER (IMPI,IMPU, response) Adds Authorization header 1 2 3 4 5 7 8 6 Figure 8.5: Non IMS capable device Authentication trough CNG SIP Proxy Other devices shall use their own IMPU (pre-configured in the device) to send the register directly to the NGN proxy through the CNG SIP proxy. It is the case for instance for a nomadic device which is not able to register locally at the CNG level as it does not use the option 120 to know its registrar already provisioned, but use the option 120 to discover the outbound proxy within the CNG. with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP proxy 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP Proxy B2BUA 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) IMS CND with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP proxy 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) with CNG CNG SIP proxy IMS with CNG REGISTER (IMPU) 200 OK 401 (SIP outbound proxy = CNG address) ) SIP- IMS Proxy SIP core network IMS 200 OK REGISTER (IMPU,IMPI,challenge response) SIP- IMS Proxy SIP core network IMS DHCP with option120 CNG CNG SIP Proxy B2BUA 401 200 OK REGISTER (IMPU) REGISTER (IMPU,IMPI,challenge response) IMS CND NOTE: This scenario is not possible in case of IMS device implementing the AKA authentication mechanisms (IPsec tunnel through the CNG). Figure 8.6: IMS capable CND attachment and IMS registration ETSI ETSI TS 185 006 V2.3.1 (2009-05) 28
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.3.2 Outgoing call
|
The non-IMS device is provided with a public SIP URI or a local identity, as it is the case in figure 8.7. INVITE (local SIP URI) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challengeresponse) CND with a local Id (eg device_kitchen) CNG-SIP Proxy B2BUA IMS core network 1xx ACK INVITE (IMPU) RTP/RTCP 1xx 200 OK ACK INVITE (local SIP URI) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challengeresponse) CND with a local Id (eg device_kitchen) CNG-SIP Proxy B2BUA IMS core network 1xx ACK INVITE (IMPU) RTP/RTCP 1xx 200 OK ACK NOTE: The 407 (challenge) is optional. Figure 8.7:Outgoing Call trough CNG SIP Proxy For non-IMS CND, the CNG SIP-SIP proxy can replace the device local IMPU with its own IMPU in the SIP INVITE, in case the CNG IMPU is associated with several CNDs (only one register is sent to the P-CSCF for several devices with the same tel number). Figure 8.8 shows the case of IMS capable device: INVITE (IMPU) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challenge response) SIP "nomadic" terminal SIP-IMS Proxy SIP core network 1xx ACK INVITE (IMPU) RTP/RTCP IMS CND CNG-SIP Proxy B2BUA IMS Core Network 407 (challenge) INVITE (IMPU, IMPI, challenge response 1xx 200 OK ACK Figure 8.8: Outgoing call IMS capable device ETSI ETSI TS 185 006 V2.3.1 (2009-05) 29
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.3.3 Internal Call
|
The CNG SIP- proxy can route local call between 2 devices of the CPN. No NGN resource is used to establish internal call. SIP signalling is not forwarded to core network and media streams are kept on the CPN directly between endpoints. The CNG SIP proxy identifies internal call after the analysis of the called party number. The customer can dial: • Directly the local identity of the device (e.g.: kitchen, dect, John, etc.). • Or a private numbering plan. The commutation table is configurable for instance by the customer by the web server of the CNG (via U reference point). Figure 8.9: Internal Call Use Case ETSI ETSI TS 185 006 V2.3.1 (2009-05) 30 SIP 1 SIP 2 CNG-SIP Proxy B2BUA INVITE (local SIP URI_2) INVITE (local SIP URI_2) 1xx 1xx 200 OK 200 OK ACK ACK RTP/RTCP SIP 1 SIP 2 CNG-SIP Proxy B2BUA INVITE (local SIP URI_2) INVITE (local SIP URI_2) 1xx 1xx 200 OK 200 OK ACK ACK RTP/RTCP Figure 8.10: Internal call Information Flow
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.3.4 Admission Control (CNG-ACF)
|
The CNG-Admission Control Function (CNG-ACF) module calculates the available resources on the access line during the establishment of a new session, possibly limiting the number of sessions in advance, before the direct intervention of the RACS on the NGN side. As it has no means of reading signalling protocols other than unencrypted SIP, the result of this calculation may be wrong for the access line because of an underestimation of the total number of sessions. Still RACS will assure the proper result for the connection admission control over the access line and limit the session setup [i.5]. The module is considered as optional (as Gm' and Gm interfaces related to the SIP proxy). The objective is to guarantee the quality of service for each new session and existing sessions previously established. The B2BUA extracts from SIP message the SDP offer and announced capabilities (codec audio, video, etc.). It asks to CNG-ACF module if announced capabilities are compliant with the available resource. The CNG-ACF module returns 3 responses: • OK: - The resource is available for all announced codecs. - The initial SIP message is forwarded without any change on SDP part. • OK with restriction: - The initial SIP message is modified (incompatible codecs are suppressed from SDP part) and then forwarded. - The session can be established with an acceptable codec for network resource. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 31 • Not OK: - The B2BUA rejects the session establishment. NOTE: The SIP profiles can be different from one side of the B2BUA to another. Make the media flows be direct between the device and the network. CNG CND LAN WAN SIP Codecreference •G711: bitrate = 100Kbps ; cpu=7% •G722: bitrate = 100Kbps ; cpu=7% •G729: bitrate = 45Kps ; cpu = 5% •H263: bitrate = 156Kbps ; cpu=9% SIP Dynamical pointers #bitrate #CPU ACF media CNG SIP Proxy B2BUA CNG CNG CND LAN WAN SIP Codecreference •G711: bitrate = 100Kbps ; cpu=7% •G722: bitrate = 100Kbps ; cpu=7% •G729: bitrate = 45Kps ; cpu = 5% •H263: bitrate = 156Kbps ; cpu=9% SIP Dynamical pointers #bitrate #CPU ACF media CNG SIP Proxy B2BUA CNG Figure 8.11: CNG-Admission Control Function (ACF) L2 Caller CNG SIP Proxy B2BUA Callee SIP messagewith a SDP offer 1. Analysis of L2 available resources 2. Analysis of announced codecs 3. Selection of the codecs compatible with available bitrate If CAC returns that all announced codecsare compatiblewith available bitrate, the SIP messageis forwardedwithoutmodification If no codecis compatiblewith available bitrate, SIP error responseis sent If CAC returns that some codecs are incompatiblewith available bitrate, the SIP- IMS proxy modifies the original SDP bysuppressingthese codecs and forwarded this modifiedSIP message L2 Caller CNG SIP Proxy B2BUA Callee SIP messagewith a SDP offer 1. Analysis of L2 available resources 2. Analysis of announced codecs 3. Selection of the codecs compatible with available bitrate If CAC returns that all announced codecsare compatiblewith available bitrate, the SIP messageis forwardedwithoutmodification If no codecis compatiblewith available bitrate, SIP error responseis sent If CAC returns that some codecs are incompatiblewith available bitrate, the SIP- IMS proxy modifies the original SDP bysuppressingthese codecs and forwarded this modifiedSIP message Figure 8.12: Admission Control Information Flow
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.4 Remote Access information flows
| |
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.4.1 Connection Setup
|
This clause describes one procedure where information of which CNDs are registered in the CNG and therefore accessible via Remote Access, is retrieved by the remote UE. The UE provides an application linking the procedures for Remote Access services. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 32 SIP ACK SIP ACK Remote UE IMS Core Network CNG CND CND (1) SIP INVITE:(Home CNG) SIP INVITE:(Home CNG) CNG – CND Info exchange CNG – CND Info exchange (2) SIP 200 OK SIP 200 OK (3) HTTP GET: Device info request (4) HTTP 200 OK: Device info response (5) SIP BYE (6) SIP INVITE:(( HomeCNG (CND)) SIP INVITE:( HomeCNG (CND)) (7) SIP 200 OK SIP 200 OK Figure 8.13: RA Connection Setup Prerequisite, the CNDs in the CPN have to be registered (e.g. using UPnP or similar procedure) to the CNG before the following take place: 1) The remote access menu initiates SIP INVITE to the users home CNG. The request is granted by the IMS NW and sent to CNG. 2) CNG checks if the request shall be granted. It initiates mapping of addresses and ports and prepares for the remote access procedures by returning SIP 200 OK. 3) Optionally a secure tunnel is then setup between the remote UE and the CNG. 4) HTTP GET carries (e.g. DLNA or similar procedure) requesting CND information including device types and identities to be provided. 5) CNG checks its present CND registrations, DB info (e.g. DLNA or similar) and returns the CND's device type, identity and pointer to CND in HTTP 200 OK. 6) This session is terminated with SIP BYE. 7) The Remote UE now holds the list of available CNDs, their identities and types. The end user chooses the CND of interest and initiates a new session according to the following. 8) SIP INVITE is now sent addressing the CND (in the SDP part). The request is granted by the IMS NW and sent to the CNG. 9) CNG checks if the request shall be granted. It initiates mapping of addresses and ports and prepares for the remote access procedures by returning SIP 200 OK. NOTE: This initiated session will be terminated (SIP BYE) in the end of the sequence. See last part of clauses 8.4.2 and 8.4.3. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 33
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.4.2 Download of content
|
This clause describes the procedure where content is downloaded from a particular CND to the remote UE. The information about which CNDs are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connection setup procedure displayed in clause 8.4.1: 1) The Remote UE points out the CND of interest using the path descriptor received under point 4 in clause 8.4.1. 2) CND sends an acknowledgement back to the Remote UE also indicating where to retrieve additional info. 3) The Remote UE sends a request (e.g. UPnP or similar) to the CND for additional device and service information. 4) CND responds with information about the services supported in the device. 5) The Remote UE browses the directories (e.g. with UPnP or similar procedure) where available content for download are located and makes a choice. 6) CND is responding with information (e.g. UPnP or similar) about the content URL/URI. 7) The Remote UE requests the download of data by addressing the content URL/URI. 8) The particular file is downloaded to the UE. 9) The connection is terminated with SIP BYE tearing down the session initiated by SIP INVITE in RA Connection setup described in clause 8.4.1, point 6. In case of consecutive download requests the first four steps do not need to be repeated if the CND device and service information is cached in the Remote UE. In the following flows (see figure 8.14) the HTTP protocol is shown as an example although other alternative choices could be considered. Remote UE CNG CND (1) HTTP GET (Path Descriptor) (5) HTTP (Content Directory Browse) (7) HTTP GET (URL to content) (9) SIP BYE Connection setup procedure (2) HTTP 200 OK (3)HTTP GET (Device and service info) (4) HTTP 200 OK (8) HTTP 200 OK (Content download) (6) HTTP (Content URL) Figure 8.14: Download of content using HTTP ETSI ETSI TS 185 006 V2.3.1 (2009-05) 34
|
d20cee83487b776a4bad5c032873a036
|
185 006
|
8.4.3 Upload of content
|
This clause describes the procedure where content is uploaded to a particular CND from the remote UE. The information about which CNDs are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connection Setup procedure in clause 8.4.1: 1) The Remote UE points out the CND of interest using the path descriptor received under point 4 in clause 8.4.1. 2) CND sends an acknowledgement back to the Remote UE also indicating where to retrieve additional info. 3) The Remote UE sends a request (e.g. UPnP or similar) to the CND for additional device and service information. 4) CND responds with information about the services supported in the device. 5) The Remote UE browses the directories where content can be uploaded. 6) CND is responding with information about the content directory URL/URI. 7) The user selects the folder where content will be uploaded. An object is created for the pending file. 8) The Object description and URL/URI address is received by Remote UE. 9) The particular file (object) is uploaded to the CND. 10) CND is acknowledging the upload of content. 11) Disconnection is initiated with SIP BYE terminating the session initiated by SIP INVITE in RA Connection setup described in clause 8.4.1, point 6. In case of consecutive upload requests the first four steps do not need to be repeated if the CND device and service information is cached in the Remote UE. In the following flows the HTTP protocol is shown as an example although other alternative choices could be considered. Remote UE CNG CND (1) HTTP GET (Path Descriptor) (5) HTTP (Content Directory Browse) (9) HTTP POST (Content) (11) SIP BYE Connection setup procedure (2) HTTP 200 OK (3) HTTP GET (Device and service info) (4) HTTP 200 OK (10) HTTP 200 OK (6) HTTP (Content URL) (7) HTTP (Create Object) (8) HTTP 200 OK (URL and Object Id) Figure 8.15: Upload of content using HTTP ETSI ETSI TS 185 006 V2.3.1 (2009-05) 35 Annex A (informative): Bibliography • HGI - Home Gateway Technical Requirements. • 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". • ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". ETSI ETSI TS 185 006 V2.3.1 (2009-05) 36 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 28-05-08 17bTD202 001 F ToC and figures Revision 2.0.0 2.0.1 28-05-08 17bTD259 002 2 F Clarification on CNG Admission Control Function 2.0.0 2.0.1 28-05-08 17bTD261 003 1 F Correction to change of local identity 2.0.0 2.0.1 28-05-08 17bTD262 004 1 F Correction CND-PPCF 2.0.0 2.0.1 28-05-08 17bTD263 005 1 F Correction of figure 4.6 2.0.0 2.0.1 02-07-08 18WTD121 006 1 F Correction of the RA setup signalling flows – figure 8.13 2.0.1 2.0.2 11-07-08 All CRs approved at TISPAN#18 2.0.2 2.1.1 25-09-08 18bTD139r2 007 D Clarifications in specification due to comments from HGI 2.1.1 2.1.2 All CRs approved at TISPAN#19 2.1.2 2.2.1 Publication 2.2.1 2.3.1 ETSI ETSI TS 185 006 V2.3.1 (2009-05) 37 History Document history V2.0.0 March 2008 Publication V2.3.1 May 2009 Publication
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
1 Scope
|
The present document describes the Procedures on the Functional Entities and Call Flows for the protocols and their possible enhancements to support IPTV services based on the architecture and stage 2 information flows described in TS 182 027 [2]. The possible enhancements of protocols will define the scope of new or enhanced protocol specifications. Besides, the interaction with other Simulation Service will be considered. NOTE: The present document relies on the architectural framework defined in TS 182 027 [2] for IMS-based IPTV Stage 2 and may need to be updated once the open issues identified in the present document are resolved. The present document is applicable to: • the interface between the User Equipment (UE) and the Call Session Control Function (CSCF); • the interface between the S-CSCF and IPTV Service Control Functions (SCF); • the interface between the S-CSCF and IPTV Service Discovery Functions (SDF); • the interface between the S-CSCF and the Media Control Functions (MCF); • the interface between the User Equipment (UE) and IPTV Service Selection Functions(SSF); • the interface between the User Equipment (UE) and Elementary Control Functions (ECF)/Elementary Forwarding Functions (EFF); • the interface between the User Equipment (UE) and IPTV Service Control Functions (SCF).
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [2] ETSI TS 182 027: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". [3] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [4] ETSI TS 102 471: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Electronic Service Guide (ESG)". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 17 [5] ETSI TS 102 472: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Content Delivery Protocols". [6] OMA-TS-BCAST-ServiceGuide-V1-0: "Open Mobile Alliance: Service Guide for Mobile Broadcast Services". [7] OMA-TS-BCAST-DVB-Adaptation-V1-0: "Open Mobile Alliance: Broadcast Distribution System Adaptation - IPDC over DVB-H". [8] IETF RFC 2326: "Real Time Streaming Protocol (RTSP)". [9] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". [10] ETSI TS 187 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [11] ETSI TS 124 109: "Universal Mobile Telecommunications System (UMTS); LTE; Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details (3GPP TS 24.109 Release 7)". [12] 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". [13] ETSI TS 102 539: "Digital Video Broadcasting (DVB); Carriage of Broadband Content Guide (BCG) information over Internet Protocol (IP)". [14] ETSI TS 133 222: "Universal Mobile Telecommunications System (UMTS); Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) (3GPP TS 33.222 Release 7)". [15] IETF RFC 5874: "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources". [16] ETSI TS 184 009: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Rules covering the use of TV URIs for the Identification of Television Channels". [17] IETF RFC 3925: "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)". [18] IETF RFC 1035: "Domain names - implementation and specification". [19] IETF RFC 1034: "Domain names - concepts and facilities". [20] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [21] ETSI ES 283 030: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence-SIMPLE-V1-0, modified]". [22] Void. [23] OMA-TS-Presence-SIMPLE-V1-0-20060725-A: "Open Mobile Alliance: Presence SIMPLE Specification". [24] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); 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 Release 9)". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 18 [25] IETF RFC 5956: "Forward Error Correction Grouping Semantics in the Session Description Protocol". [26] IETF RFC 5875:"An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package". [27] Void. [28] IETF RFC 3376: "Internet Group Management Protocol, Version 3". [29] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". [30] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1". [31] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)". [32] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". [33] ETSI TS 102 822-3-1: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 1: Phase 1 - Metadata schemas". [34] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream". [35] ETSI TS 102 822-4: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 4: Phase 1 - Content referencing". [36] ETSI ES 283 035: "Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMETER protocol". [37] DSL Forum TR-069 Amendment 2: "CPE WAN Management Protocol v1.1". [38] ETSI TS 183 060: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Subsystem (RACS); Re interface based on the DIAMETER protocol". [39] W3C: "Synchronized Multimedia Integration Language (SMIL 2.1)". [40] IETF RFC 4660: "Functional Description of Event Notification Filtering". [41] IETF RFC 4661: "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering". [42] IETF RFC 4235: "An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)". [43] IETF RFC 5760: "RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback". [44] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [45] IETF RFC 3611: "RTP Control Protocol Extended Reports (RTCP XR)". [46] IETF RFC 5576: "Source-Specific Media Attributes in the Session Description Protocol (SDP)". [47] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". [48] ETSI TS 102 822-6-1: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 6: Delivery of metadata over a bi-directional network; Sub-part 1: Service and transport". [49] ETSI TS 126 234: "Universal Mobile Telecommunications System (UMTS); LTE; Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs (3GPP TS 26.234 Release 9)". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 19 [50] OMA-TS-SIMPLE-IM-V1-0-20100322-C: "Open Mobile Alliance: Instant Messaging using SIMPLE". [51] ETSI TS 126 237: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) based Packet Switch Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) User Service; Protocols (3GPP TS 26.237 Release 9)". [52] IETF RFC 4745: "Common Policy: A Document Format for Expressing Privacy Preferences". [53] IETF RFC 5025: "Presence Authorization Rules". [54] OMA-TS-Presence-SIMPLE-XDM: "Presence XDM Specification". [55] ETSI TS 102 822-3-3: "Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 3: Phase 2 - Extended Metadata schema". [56] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification". [57] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". [58] ETSI TS 124 237: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 (3GPP TS 24.237 Release 9)". [59] IETF RFC 5627: "Obtaining and Using Globally Routable User Agent URIs (GRUU) in the Session Initiation Protocol (SIP)". [60] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN Services and IPTV". [61] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". [62] IETF RFC 3261: "SIP: Session Initiation Protocol". [63] IETF draft-ietf-sipping-config-framework-18: "A Framework for Session Initiation Protocol User Agent Profile Delivery". NOTE: Available at draft-ietf-sipping-config-framework-18. [64] IETF RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)". [65] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace". [66] IETF RFC 4395: "Guidelines and Registration Procedures for New URI Schemes". [67] IETF RFC 3406: "Uniform Resource Names (URN) Namespace Definition Mechanisms". [68] IETF RFC 2327: "SDP: Session Description Protocol". [69] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification". [70] IETF RFC 3891: "The Session Initiation Protocol (SIP) "Replaces" Header". [71] IETF RFC 7272: "Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP)".
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Void. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 20 [i.2] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [i.3] ETSI TS 183 033: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 and 3GPP TS 29.229, Release 9]". [i.4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 Release 7)". [i.5] IEEE 1003.1-2004: "Standard for information technology - portable operating system interface (POSIX). Shell and utilities". [i.6] F. Boronat, J. Lloret, M. García, "Multimedia group and inter-stream synchronization techniques: A comparative study", Elsevier Information Systems 34 (2009), pp. 108-131. [i.7] ETSI TR 187 013: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on IPTV Security Architecture". [i.8] Recommendation ITU-T G.114: "General Recommendations on the transmission quality for an entire international telephone connection, One-way transmission time", May 2003. [i.9] IETF draft: "RTSP 2.0 Asynchronous Notification, draft-stiemerling-rtsp-announce-01". [i.10] IETF draft-stiemerling-rtsp-announce-01: "RTSP 2.0 Asynchronous Notification". [i.11] IETF draft-ietf-sip-ipv6-abnf-fix-05: "Essential correction for IPv6 ABNF and URI comparison in RFC 3261". [i.12] IANA: "RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry". NOTE: http://www.iana.org/assignments/rtcp-xr-block-types/rtcp-xr-block-types.xhtml. [i.13] IANA: "RTP Control Protocol Extended Reports (RTCP XR) Session Description Protocol (SDP) Parameters Registry". NOTE: http://www.iana.org/assignments/rtcp-xr-sdp-parameters/rtcp-xr-sdp-parameters.xhtml. [i.14] ETSI TS 182 028: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN integrated IPTV subsystem Architecture". [i.15] draft-ietf-sipcore-info-events-08. [i.16] IETF RFC 3725: "Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)".
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ABNF Augmented BNF (Backus-Naur Form) ACK ACKnowledge character AP Authentication Proxy AS Application Server AUID Application Unique ID B2BUA Back To Back UA BC BroadCast BCG Broadband Content Guide CCR Credit-Control Request ETSI ETSI TS 183 063 V3.6.1 (2014-08) 21 CNGCF Customer Network Gateway Configuration Function CoD Content on Demand C-PVR Client-side Personal Video Recorder CRS Content Recommendation Service CSCF Call Session Control Function DHCP Dynamic Host Configuration Protocol DNS Domain Name System DVB Digital Video Broadcasting DVBSTP DVB SD&S Transport Protocol ECF/EFF Elementary Control Function/Elementary Forwarding Function EPG Electronic Program Guide ERE Extended Regular Expressions ESG Electronic Service Guide FEC Forward Error Correction GRUU Globally Routable User Agent URIs HTTP Hypertext Transfer Protocol IARI IMS Application Reference Identifier I-CSCF Interrogation - Call Session Control Function ICSI IMS Communication Service Identities ID Identifier IFC Initial Filter Criteria IGMP Internet Group Management Protocol IMS IP Multimedia Subsystem IP Internet Protocol IPTV Internet Protocol TeleVision MCF Media Control Function MDF Media Delivery Function MF Media Function MLD Multicast Listener Discovery MSAS Media Synchronization Application Server NGN Next Generation Network NPT Normal Play Time N-PVR Network-side Personal Video Recorder NTP Network Time Protocol OMA Open Mobile Alliance P-CSCF Proxy - Call Session Control Function PPV Pay Per View PSC Personalized Service Composition PSI Public Service Identity RACS Resource and Admission Control Subsystem RTCP Real Time Control Protocol RTP Real Time Protocol RTSP Real Time Streaming Protocol SAD Service Action Data SAH Service Access History SC Synchronization Client SCF Service Control Function S-CSCF Serving - Call Session Control Function SD Standard Definition SD&S Service Discovery and Selection SDF Service Discovery Function SDP Session Description Protocol SGDD Service Guide Delivery Descriptors SGDU Service Guide Delivery Units SIP Session Initiation Protocol SNTP Simple Network Time Protocol SOAP Simple Object Access Protocol SRV Service Records SSD Service State Data SSF Service Selection Function SSRC Synchronization source TCP Transmission Control Protocol ETSI ETSI TS 183 063 V3.6.1 (2014-08) 22 TLS Transport Layer Security TsTV Time shift TV UA User Agent UDP User Datagram Protocol UE User Equipment UGC User Generated Content UPSF User Profile Server Function URI Uniform Resource Identifier XCAP XML Configuration Access Protocol XDMSXML eXtensible Markup Language Data Management Server XML eXtensible Markup Language
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4 Applicability
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.1 Overview
|
The overall functional architecture for the IMS-based IPTV service conforms to TS 182 027 [2]. This clause provides the list of protocols and related reference points. Figure 4.1: Protocols used in functional architecture for the IMS-based IPTV service ETSI ETSI TS 183 063 V3.6.1 (2014-08) 23 Table 4.1: IMS based IPTV functional entities and protocols used on reference points FE/ Reference point (protocol) UE IMS core UPSF SDF SSF SCF MCF MDF ECF/ EFF UE --- Gm (SIP/SDP) --- via Core IMS (SIP/SDP) Xa (HTTP, DVBSTP, FLUTE) Ut (HTTP), via Core IMS (SIP/SDP) Xc (RTSP) (Note 1) Xd (UDP/RTP /RTCP/ HTTP) (Note 1) Dj, Di IGMP/ MLD IMS core Gm (SIP/SDP) --- Cx (Diameter) ISC (SIP/SDP) --- ISC (SIP/SDP) y2 (SIP/SDP) --- --- UPSF --- Cx (Diameter) --- Sh (Diameter) --- Sh (Diameter) --- --- --- SDF via Core IMS (SIP/SDP) ISC (SIP/SDP) Sh (Diameter) --- --- --- --- --- --- SSF Xa (HTTP, DVBSTP, FLUTE) --- --- --- --- Ss' (not defined) --- --- --- SCF Ut (HTTP), via Core IMS (SIP/SDP) ISC (SIP/SDP) Sh (Diameter) --- Ss' (not defined) --- via Core IMS and y2 (SIP/SDP) --- --- --- MCF Xc (RTSP) (Note 1) y2 (SIP/SDP) --- --- --- via Core IMS and y2 (SIP/SDP) --- Xp (not defined) --- MDF Xd (UDP/RTP/ RTCP/HTT P) (Note 1) --- --- --- --- --- Xp (not defined) --- --- ECF/ EFF Dj, Di IGMP/ MLD --- --- --- --- --- --- --- --- NOTE 1: As described in TS 182 027 [2], clauses 6.4 and 6.5, Xc and Xd are logical reference points that can be decomposed into Dj and possibly Di, Ds or Iz reference points depending on the location of the MCF or MDF, and the HTTP is used for the content download. NOTE 2: Annex H lists compliance requirements for the protocols listed in this table. Usage of the SIP/SDP protocol across the following interfaces is described in clause 5: - interface Gm; - interface ISC; - interface y2. Usage of the HTTP protocol across the following interfaces is described in clause 6: - interface Xa; - interface Ut; - interface Xd. Usage of the RTSP protocol across the following interfaces is described in clause 7: - interface Xc; - interface Di, Dj, Ds or lz. Usage of the UDP/RTP/RTCP protocol across the following interfaces is described in clause 11: - interface Xd; - interface Di, Dj, Ds or Iz. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 24 Usage of the IGMP/MLD protocol across the following interfaces is described in clause 8: - interface Xd; - interface Dj, Di, Ds or Iz. NOTE: Whether usage of multicast protocols (IGMP,MLD) is supported on Xc, Xd interface or how MDF joins multicast streams (e.g. for N-PVR or BC with trick mode services) is out of the scope of the present document. Usage of the DVBSTP protocol across the following interface is described in clause 9: - interface Xa. Usage of the FLUTE protocol across the following interface is described in clause 10: - interface Xa.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2 Functional entities
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.1 User Equipment (UE)
|
The UE is a functional entity that provides the user with access to IPTV services. For time -and synchronization- sensitive services, the UE shall support NTP/SNTP-based network time services as described in clause 8.2 of [3].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.2 Service Control Function (SCF)
|
The SCF is a functional entity that provides IPTV service logic and the functions required to support execution of such logic.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.3 Service Discovery Function (SDF)
|
An SDF is a functional entity that provides service attachment information to the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.4 Service Selection Function (SSF)
|
An SSF is a functional entity that provides service selection information to the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.5 Media Control Function (MCF)
|
The MCF is a functional entity that provides the UE with functions required to control media flows and manages the MDFs under its control.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.6 Media Delivery Function (MDF)
|
The MDF is a functional entity that delivers content data to the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.7 Core-IMS
|
The Core IMS includes a number of functional entities identified in ES 282 007 [1]. For the purpose of supporting IPTV services, the following functional entities of the Core IMS are involved: - the P-CSCF; - the S-CSCF; - the I-CSCF; ETSI ETSI TS 183 063 V3.6.1 (2014-08) 25 - the IBCF in case the P-CSCF and the I/S-CSCF or the CSCF and the MCF are in different administrative domains. The behaviour of these functional entities with regards to SIP and SDP shall conform to ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.8 Inter-destination media synchronization entities
|
Figure 4.2 shows the two functional entities involved in inter-destination media synchronization, i.e. the media synchronization application server (MSAS) and Synchronization Client (SC). Optionally, there is also a Synchronization Client' (SC'). These functional entities are described in clauses 4.2.8.1, 4.2.8.2 and 4.2.8.3, respectively. Figure 4.2: Functional entities and reference points for inter-destination media synchronization As described in TS 182 027 [2], there exist different mappings of the SC and MSAS onto the functional entities depicted in figure 4.1. The mapping of the SC as an elementary function of the UE is aimed at small-scale deployments of services that require media synchronization and only a limited number of UEs that use media synchronization. It reuses existing IPTV sessions. NOTE: Synchronization signalling procedures are initiated by the SC. This means that a UE without SC functionality will not be involved in synchronization signalling. The mapping of the SC as an adjunct function that may be co-resident with any of the appropriate elements of the Transport Processing Function is aimed at large-scale deployment of media synchronization. The process of inter-destination media synchronization involves three basis steps: 1) Synchronization session initiation 2) Synchronization status information and synchronization settings instruction exchange 3) Synchronization session termination Given these steps, the Sync reference point is decomposed as follows: • Synchronization session initiation information is exchanged over the Gm and ISC reference points, using SIP/SDP. Synchronization session initiation information can also be exchanged over the Xc reference point, using RTSP/SDP. • Synchronization status information and delay information in the form of synchronization settings instruction is exchanged over the Xd reference points, using RTCP. Media Synchronization Application Server (MSAS) Synchronization Client’ (SC') Sync’ Synchronization Client (SC) Sync Session-level capabilities Media-level capabilities ETSI ETSI TS 183 063 V3.6.1 (2014-08) 26 • Synchronization session termination is exchanged over the Gm and ISC reference points, using SIP/SDP. Synchronization session termination information can also be exchanged over the Xc reference point, using RTSP/SDP. RTCP reports with synchronization status information or synchronization settings instructions can be sent directly between UEs, if a direct communication channel between UEs already exists. In that case, one UE acts as co-located SC+MSAS as described in clauses 11.3.2 and A.5.2.3. The Sync' reference point is used to report synchronization correlation information on the synchronicity relationship between the incoming media stream (which could be received by some SCs)and the outgoing media stream(s) (which could be received by other SCs) from the SC' to the MSAS. The Sync' reference point uses RTCP.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.8.1 MSAS
|
The MSAS is a functional entity that coordinates session synchronization with SCs and SC' for inter-destination media synchronization purposes. The MSAS session-level capabilities are reflected as independent functional entity or as elementary functions of the SCF, its media-level capabilities are reflected as adjunct functions of other functional entities. For synchronization using a direct communication channel between multiple UEs, the MSAS is co-located with the SC in a UE. Tasks of the MSAS are setting up and accepting synchronization sessions with/from SCs; collecting synchronization status information from SCs; collecting synchronization correlation information from SC's; calculating delay information and derive synchronization settings instructions for the SCs and distributing synchronization settings instructions to SCs.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.8.2 SC
|
The SC is a functional entity that coordinates session synchronization with the MSAS for inter-destination media synchronization purposes. It is an elementary function of the UE or an adjunct function of the Transport Processing Functions. Tasks of the SC are setting up and accepting synchronization sessions with/from the MSAS; sending synchronization status information to the MSAS; receiving delay information in the form of synchronization settings instructions from the MSAS; and delaying (buffering) a media stream according to the received synchronization settings instruction.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.8.3 SC'
|
The SC' is a functional entity that assists session synchronization by the MSAS for inter-destination media synchronization purposes. It is an elementary or adjunct function of functional entities that modify and/or re-originate media streams, e.g. a transcoder or a mixer in an MDF.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.2.9 Service Protection and Content Protection function (SCP)
|
In the IMS based IPTV architecture, the functional entities and elementary functions that are responsible for Service protection and content protection are defined in TS 182 027 [2] clause 10.2 and 10.3, the NGN security architecture TS 187 003 [10], and the IPTV security architecture TR 187 013 [i.7]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 27
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
4.3 Compliance
|
Compliance for the IMS-based IPTV service conforms to table 4.2. Table 4.2: IPTV services and features supported by TISPAN IMS based IPTV subsystem NGN IPTV Service & Feature TISPAN R3 Stage 2 TISPAN R3 Stage 3 Specification TS 182 028 [i.14] Release 3 Present document Linear/ Broadcast TV M M Linear/ Broadcast TV with Trick Play O O Time Shifted TV O O Content on Demand (CoD) M M Push CoD O O Network PVR M/O (See note 2) M/O (See note 2) Client PVR O (See note 2) O (See note 2) Audio O O Pay-Per-View O O Interactive TV O O Service discovery M M Service Information (EPG) M M Parental Control M/O (See note 3) M/O (See note 3) User Profiling & Personalization O O Communications and Messaging O O Notifications O O IPTV Presence O O Interaction between users O O Interaction with NGN services O O Advertising M (See note 4) M (See note 4) Targeted Advertising O O User Generated Content O O Internationalization O O Content recommendation O O Games O O Picture O O Bookmarks O O Personalized channel O O Personalized Service Composition O O Service Portability O O Service Continuation between IPTV UEs O O Service Continuation fixed-mobile O O Remote Control of IPTV services O O Emergency Information. O O Interaction with 3rd Party application (e.g. Parlay) O O Service synchronization O O Incoming call management O O NOTE 1: M - Mandatory, O- Optional, NA - not available or not specified (out of scope in release) in architecture. NOTE 2: It is recommended that at least one type of PVR is supported by the IPTV system. NOTE 3: Mandating this feature is subject to local regulatory policies. NOTE 4: Advertising refers to traditional broadcast based advertising services which impose no new requirements on IMS based IPTV subsystem. Features that are only used by optional services are optional as well. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 28
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5 Procedures using SIP/SDP for IMS-based IPTV
|
Use the SIP/SDP protocol across the following interfaces is described in this clause: • interface Gm; • interface ISC; • interface y2. SIP/SDP capable functional entities are following: • UE. • SCF. • SDF. • MCF. • Core IMS. NOTE: Summary of compliancy requirements and referred specification are listed in clause H.1.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1 User Equipment (UE)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.1 Procedure for IMS registration
|
As specified in TS 182 027 [2], clause 8.2 the UE shall perform IMS registration before launching a service attachment procedure. The behaviour of the UE with regards to IMS registration shall comply with ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.2 Procedure for service attachment
|
If the SDF is known as per annex I the Pull mode as in clause 5.1.2.2 shall be used, else the UE shall be preconfigured to use the public user identity of the user to send a SIP SUBSCRIBE request according to the Pull mode or to expect a SIP MESSAGE request according to Push mode as in clause 5.1.2.1.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.2.1 Push mode
|
Upon receipt of a SIP MESSAGE request from the SDF, the UE shall parse the XML document as described in clause 5.1.2.2.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.2.2 Pull mode
|
Service Attachment, the UE shall generate a SUBSCRIBE request. The behaviour of the UE when processing a SUBSCRIBE request shall conform to ES 283 003 [20], clause 5.1.2A.1. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 29
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.2.2.1 Subscription
|
When the UE intends to retrieve service attachment information from the SDF, it shall generate a SUBSCRIBE request for the "ua-profile" event package defined in annex Y. The contents of the SUBSCRIBE request shall be as follows: • The value of the Request-URI shall be set to one of following: - The PSI of the SDF which is retrieved using SDF Discovery procedures specified in annex I, or - When the SDF identify is not present the public user identity of the IPTV end user. • The From and To header shall be set to the public user identity of the IPTV end user. • The Accept header shall include the content-type identifier that corresponds to the registered MIME type of XML documents representing IPTV profiles: "application/vnd.etsi.iptvdiscovery+xml". • The Event header shall be set to the "ua-profile" event package. • The Event parameters shall be set as follows: - The "profile-type" parameter shall be set to "application". - The "vendor", "model" and "version" parameter values shall be set to values specified by the implementer of the user equipment, as specified in ES 283 003 [20]. - The "appids" parameter shall be set to "urn:org:etsi:ngn:applications:ims-iptv-service-discovery". The UE may include a SIP SUBSCRIBE message body associated with the appid " urn:org:etsi:ngn:applications:ims-iptv-service-discovery ". The message body includes the capabilities of the UE which is sent to the SDF. NOTE: Process of registering the appid is aligned with IETF specification in annex Y. If the SIP SUBSCRIBE contains a message body, the details of the SIP SUBSCRIBE are as follows: • Content Type header shall be set to "application/vnd.etsi.iptvueprofile+xml". • A message body shall be present for conveying UE-specific information as defined in annex P. This includes: - User Equipment ID. - User Equipment Class: Specifies the type of UE. The currently defined types are "STB", "Mobile" and "PC". - UE Capabilities: This defines the set of UE capabilities and could include: Physical resolution of the screen of the rendering device (defined in vertical and horizontal number of pixels). Supported coding formats (defined using the Coding XML element from TV-Anytime (TS 102 822-3-1 [33]), and using the classification schemes from MPEG7 and DVB). Optionally, supported Video Frame Rates (defined as per TS 101 154 [34]) associated with the encoding format. If the UE supports a content protection, it shall include in its UE capabilities, supported Content Protection System associated with the supported protected formats. A Content Protection System is defined via a URN with the DVB CA System ID (16 bit number) as registered in DVB http://www.dvbservices.com/identifiers/ca_system_id). It shall be signalled by prefixing the decimal number format of CA_System_ID with "urn:dvb:casystemid:". For example, the CA_System_ID hexadecimal 0x1234, is encoded as "urn:dvb:casystemid:4660". Note that the decimal number format of CA_System_ID shall not have leading zeroes. A supported protected format shall be signalled by its mime type (i.e. "video/mp2t" for MPEG2-TS). Supported transport protocols (MPEG2TS over UDP, MPEG2TS over RTP, direct RTP). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 30 Upon receipt of a 2xx response to the SUBSCRIBE request, the UE shall store the information for the established dialog and the expiration time as indicated in the Expires header of the received response. The UE shall automatically refresh the subscription, either 600 seconds before the expiration time if the initial subscription was for greater than 1 200 seconds, or when half of the time has expired if the initial subscription was for 1 200 seconds or less. If a SUBSCRIBE request to refresh a subscription fails with a non-481 response, the UE shall still consider the original subscription valid for the duration of the most recently known "Expires" value according to ES 283 003 [20]. Otherwise, the UE shall consider the subscription invalid and start a new initial subscription according to ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.2.2.2 Receiving notifications
|
Upon receipt of a NOTIFY request on the dialog which was generated during subscription, the UE shall look for a message body with a content-type header indicating "application/vnd.etsi.iptvdiscovery+xml ". The IPTV application within the UE shall parse the XML document contained in the message body. The list of parameters which are described in clause 5.2.2.3 shall be used for service selection information retrieval according to clause 6.1.1 in unicast mode and clause 8.1.1 in multicast mode. When parsing the list of parameters the UE shall take the following action: • Information relates to SSF whom the UE has already an entree. - If the "@version" attribute is present and has not the same value or if not present, then the UE performs the following actions: For parameters related to this SSF already present in the UE: the UE shall update these parameters with the new values sent by the SSF. If the Segment@Version has not the same value, the UE shall update service selection information from the SSF before using it. For parameters related to this SSF not present in the UE: the UE shall store the new parameters. - If the "@version" attribute is present and has the same value, the UE shall not update the stored SSF information. • Information relates to an SSF not known by the UE: the UE creates a new entry for this SSF with all indicated parameters. After all elements have been processed, the UE shall return a SIP 200 OK response to the NOTIFY request. Failure to perform subscription refresh does not imply that there is a loss of communication to SSF or SCF. The UE has an option to continue using the lists of parameters from the last NOTIFY. After deregistration, the UE may keep stored information on per user basis. As for subscription refresh, the UE may use the stored information if initial subscription fails after a new registration.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3 Procedure for BC service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.1 UE-initiated session initiation
|
The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon a request for a BC session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE. The Request-URI in the INVITE request shall be the well known PSI (Public Service Identifier) of the BC Service. If the UE supports the SIP INFO framework, as defined in draft-ietf-sipcore-info-events-08 [i.15], the UE shall indicate so by including Recv-Info header in the INVITE with a value set to 'nil'. Note that the inclusion of the Recv-Info header is the indication that the UE supports the SIP INFO framework. If the UE does support the reception of other INFO packages (for other applications), and it wishes to indicate so, it can replace the value nil with the appropriate list of INFO packages. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 31 Note that the draft defines a mechanism for backward compatibility when one end in the SIP dialog supports the SIP INFO framework while the other peer does not support the SIP INFO framework. Clause 9 in the draft details co- existence within a SIP dialog of legacy SIP INFO and SIP INFO based on the SIP INFO framework. An SDP Offer shall be included in the request. The SDP offer shall be done in accordance with the parameters received during UE service selection procedure and with media capabilities and required bandwidth available for the BC session. If the user desires to join a BC service outside of this negotiated set of channels, a session modification is required. The SDP offer at media level shall include the following elements: • The m-line(s) shall be set according to the mapping defined in clause L.2 for the BC service which the UE intends to join first. • The c-line(s) shall be set according to the mapping defined in clause L.2 for the BC service which the UE intends to join first. • An a=bc_service:BCServiceId line to indicate the BC service which the UE intends to join first. • Optionally one or more a=bc_service_package attributes (see below) as defined in annex N. In the first initial offer it shall not contain mult_list and bc_service_id list parameters. If the initiation is the result of a previously denied initiation the UE may restrict the BC services by including mult_list. • If the UE has knowledge of the largest bandwidth of all the BC services included in the session, the b-line shall be included and set to this value. • An a=recvonly line. Additionally, FEC streams may be defined, as described in clause 5.1.3.1.1. When the UE receives any SIP request or response, and if the UE supports the SIP INFO framework, it shall look for the Recv-Info header. If the header is present then the UE shall follow the network request as set in the header, to report/not report the selected channel. If the header is absent, then the UE may optionally report the selected channel outside the SIP INFO framework. The UE shall then examine the media parameters in the received SDP. The UE shall restrict the BC services that it joins according to the a=bc_service_package parameters received from the SCF. If the UE has retrieved the IPTV User profile prior to BC session initiation, it may ignore the a=bc_service_package parameters, if present (see clause 5.3.1.1). If the user desires to join a BC service outside of this negotiated set, a session modification is required. If the UE receives a 488 error code with warning 370 Insufficient Bandwidth the UE may perform a new SIP INVITE with a lower maximum bandwidth for BC service the UE intends to join. This procedure may be repeated. If no agreement can be reached the UE may display a failure message to the user. When the UE receives the SIP final response, the UE shall joins the multicast channel according to the a=bc_service line.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.1.1 Additional SDP lines for FEC streams
|
When the UE decides to connect to FEC stream(s) associated to the original BC stream(s), it shall include additional SDP lines in the SDP offer as follows: • One or more m line(s) for each FEC stream exposed through the SSF: - It shall be set according to the mapping defined in clause L.2. - It shall contain a c-line according to the mapping defined in clause L.2. If the BC content is defined through a single m-line, a grouping line may be included. If the BC content is defined through several m-lines, grouping line(s) shall be included, one for each BC m-line that is associated to a FEC stream. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 32 The grouping line uses the "FEC" semantic as defined in RFC 5956 [25]: • a=group:FEC:<original stream id> <FEC stream id> The present document supports only the DVB-IP AL-FEC Base layer, so there can be only one <FEC stream id> associated to an original stream. - The original stream id shall reflect the value held by the media description of one stream in its a=mid attribute. - The FEC stream id shall reflect the value held by the media description of the DVB-IP AL-FEC Base layer FEC stream (associated to the original stream) in its a=mid attribute. Furthermore, when grouping line is included, there shall be an additional media identification attribute within the m-line of the original stream that is within the grouping: • a=mid:<original stream id>.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.1A SCF-initiated session initiation
|
The UE shall support the procedures specified in ES 283 003 [20] for handling sessions. Upon receipt of SIP INVITE request, and if the UE supports the SIP INFO framework, it shall look for the Recv-Info header. If the header is present then the UE shall follow the network request as set in the header, to report/not report the selected channel. If the header is absent, then the UE may optionally report the selected channel outside the SIP INFO framework. The UE then checks the P-Asserted-Identity header for a well-formed PSI of the BC service, and the SDP parameters to determine that it is a BC session initiation request. In particular: • The UE shall examine the a=bc_service parameter. This parameter contains the BCServiceId (channel) the SCF wants the UE to join. • If present it shall examine the a=bc_service_package attributes and store the attributes. If the UE has retrieved the IPTV User profile prior to BC session initiation, it may ignore the a=bc_service_package parameters. • It shall examine the c-line(s) and extract the IP multicast address to determine that it is a multicast session. • If the UE has a pre-configured maximum bandwidth limitation, it shall examine the b-line parameter and verify if it not exceeds the pre-configured value. If the value is exceeded, the UE shall answer with a 403 error code. The UE shall check the if SDP parameters in the offer are acceptable (e.g., codecs), the UE shall answer with a SIP 200 OK, indicating the SDP answer as follows: • The c-lines and m-lines shall be identical to ones indicated in the SDP offer. • It shall include an a=recvonly attribute. • It shall include a b-line parameter with the same value as in the offer. • If the SDP offer includes one or more a=bc_service_package attribute the UE answer shall include the same attributes. Finally, if the UE supports the SIP INFO framework, and if the SCF indicated, as well, support for the SIP INFO framework as described in the processing above, the UE shall indicate the same support. For that purpose, the UE shall include the Recv-Info header in the SIP 200 OK with a value set to 'nil'. When the UE receives an acknowledgement, the UE shall join the multicast channel according to the multicast address. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 33
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.2 Session modification
|
When there is a need for BC session modification, the UE shall generate a re-INVITE request or an UPDATE request, depending on the dialogue state, as specified in ES 283 003 [20] for an originating UE. The UE shall include SDP offer in session modification request. When the modified session is also a broadcast session the format of the SDP shall be the same as for a session initiation. Upon receipt of a re-INVITE request or an UPDATE request, the UE shall follow the procedures defined in ES 283 003 [20] for an originating UE. When receiving SDP offer, the SDP answer shall reflect the media capabilities and required bandwidth as available for the BC session. The selection of the channels that are above the negotiated bandwidth may require a new session modification in accordance with the behaviour of the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.3 BC service with trick-play mode
|
When supporting BC service with trick play, the BC session can observe two special cases: • The Broadcast session is modified to change from Multicast to unicast flow. This is the case in which the UE activates the trick play mode. • The Broadcast session with trick play mode is modified to return to normal Broadcast TV. This is the case in which the UE deactivates the trick play mode by, e.g. switching channels from a paused channel to another live Broadcast TV channels.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.3.1 Trick-play mode activation
|
Upon activation of trick-play mode, the UE shall perform session modification as described in clause 5.1.3.2. The UE shall include an SDP offer with previously negotiated media descriptions with the port set to zero and two or more additional media descriptions: one for RTSP control and one or more for the unicast streams. The RTSP control media descriptor shall follow ES 283 003 [20]. The SDP offer for media delivery shall be identical to the previous SDP offer done for broadcast in term of codecs and transport protocol. The "t=" line in the SDP offer shall include a reference timestamp for when trick mode was activated. The "t=" line shall be used by the network to calculate the h-offset that is returned in the SDP answer. By including the reference timestamp, the network can provide a more accurate h-offset independent of clock synchronizations issues. If the "t=" line in the SDP offer is set to "0 0" the h-offset shall be calculated based on the timestamp for when the re-INVITE is processed by network. The SDP answer shall include the same value as in the "t=" line as in the SDP offer. If the "t=" line in the SDP answer is set to "0 0" the UE assumes the h-offset was calculated based on network reference timestamp. The UE shall also include the following Service Action Data: • IPTVActionDataCommand shall be set to "SwitchToTM". • SwitchToTM shall be set to "IPTVBcActionData". BCServiceId shall present only if the UE has not informed the SCF of the selected channel prior to this procedure (as defined in clause 5.1.3.5) and set to the value of the current channel. When the UE acknowledges the SIP 200 OK with an ACK message, the UE may start playback (see clause 7).
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.3.2 Trick-play mode deactivation
|
Upon deactivation of trick-play mode, the UE shall perform session modification as described in clause 5.1.3.2. The UE shall include an SDP offer with previously negotiated RTSP and unicast media descriptions with the port set to zero. The SDP corresponding to the broadcast session shall be reactivated (i.e. port not set to zero). The "t=" line in the SDP offer shall be set to "0 0". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 34 The UE shall also include the following Service Action Data: • IPTVActionDataCommand shall be set to "SwitchToBC". • SwitchToBC shall be set to "IPTVBcActionData". • BCServiceId is set to the value of the selected channel. The UE deactivates trick-play mode when it receives an indication from the network that it has caught up with the live BC service. The UE shall go back to normal BC session if it does not receive any delivery data anymore and has not paused playback.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.4 Session termination
|
Upon a request for a BC session termination, the UE shall generate a BYE request as specified in ES 283 003 [20] for an originating UE. Upon receipt of a BYE request the UE shall follow the procedure specified in ES 283 003 [20] for an originating UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.5 Session Information
|
During the procedures for join multicast group (clause 8.1.1) the UE may inform SCF of the selected channel. If both the UE and the SCF support the INFO Framework and the UE was not authorized by the SCF during the session initiation setup to send information of the selected channel, then the UE shall not report the selected channel. If both the UE and the SCF support the INFO Framework and the UE was authorized by the SCF during the session initiation setup to send information of the selected channel, then the UE shall proceed as described below. To that effect, the UE shall reset a delay timer after successfully viewing a new channel using the procedure for joining multicast group (clause 8.1.1). The delay timer is a preconfigured value in the UE with a default value of 10 seconds. When the delay timer expires, the network shall be informed of the currently viewed channel with a SIP INFO message including the appropriate info package. NOTE: A formal definition of the INFO package for reporting the selected BC channel is out scope of the current release. • The SIP INFO message based on the SIP INFO framework draft as defined in draft-ietf-sipcore-info-events-08 [i.15] shall be sent by the UE on the same dialogue as the Broadcast TV session initiation and shall contain an info package that is based on XML file schema that includes the channel change information. The service action data: the matching "BC Bookmarks" object shall be created so that: - IPTVActionDataCommand shall be set to "Notify". - Notify shall be set to "IPTVBcActionData". - BCServiceId is set to the value of the current channel. - ProgrammeId is optionally set to the value of the current programme. • Bookmark is set to the current timestamp if the UE has the knowledge of such timestamp (e.g. through SNTP). If the UE is not aware of such current timestamp, Bookmark is set to a default value: "NOW". The Content-Type header shall be set to "application/vnd.etsi.iptvcommand +xml". The body content of the message is described in annex D. The Content-Type header shall be set to "application/vnd.etsi.iptvcommand +xml". The XML schema is described in annex D. If the UE does not support the INFO Framework, the UE may inform the SCF of the selectd channel. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 35 To that effect, the UE shall reset a delay timer after successfully viewing a new channel using the procedure for joining multicast group (clause 8.1.1). The delay timer is a preconfigured value in the UE with a default value of 10 seconds. When the delay timer expires, the network shall be informed of the currently viewed channel with a SIP INFO message. • The SIP INFO message shall be sent by the UE on the same dialogue as the Broadcast TV. • Session initiation and shall contain an XML schema with the channel change information. The message body carries the service action data: the matching "BC Bookmarks" object shall be created so that: - IPTVActionDataCommand shall be set to "Notify". - Notify shall be set to "IPTVBcActionData". - BCServiceId is set to the value of the current channel. - ProgrammeId is optionally set to the value of the current programme. • Bookmark is set to the current timestamp if the UE has the knowledge of such timestamp (e.g. through SNTP). If the UE is not aware of such current timestamp, Bookmark is set to a default value: "NOW". The Content-Type header shall be set to "application/vnd.etsi.iptvcommand +xml". The body content of the message is described in annex D.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.3.6 Procedure for PPV service
|
5.1.3.6.1 PPV Session initiation The PPV may use session initiation of BC as described in clause 5.1.3.1, with the following differences: The Request-URI in the INVITE request shall be the well known PSI (Public Service Identifier) of the BC Service which the PPV service belongs to. The differences in the SDP offer at media level: • The m-line(s) shall be set according to the mapping defined in clause L.2 for the BC Service which the PPV service belongs to. • The c-line(s) shall be set according to the mapping defined in clause L.2 for the BC Service which the PPV service belongs to. • An a=bc_service:BCServiceId line to indicate the BC service which the PPV service belongs to. • An a=bc_program:BCprogramId line to indicate the BC program which the PPV service is, and shall be set according to the mapping defined in clause L.2.2A. 5.1.3.6.2 PPV Session termination When the PPV program ends or UE wants to terminate the session, the UE shall generate a BYE request as specified in ES 283 003 [20] for an originating UE, which is similar with BC session termination as described in clause 5.1.3.4. Upon receipt of a BYE request, the UE shall follow the procedure specified in ES 283 003 [20] for an originating UE, which is similar with BC session termination as described in clause 5.1.3.4.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4 Procedure for CoD service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.1 Procedure for retrieving missing parameters before session initiation
|
In case of procedure for establishing the content control and content delivery at the same time see clause 5.1.4.2.1. If the UE does not have all transport parameters (RTP or UDP transport for MPEG2TS encapsulation or direct RTP, FEC layers addresses and ports) the UE shall send a SIP OPTIONS message. NOTE: It is an operator choice to provide preconfigured transport parameters values, manual configuration mechanisms, etc., if the transport information is not retrieved from the SSF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 36 The "Request-URI" is related to the CoD session that the user wants to activate. The Request-URI shall be composed of a user and domain part as defined as follows: • The user part contains the content identifier in a free string format, as defined in TS 182 027 [2]. • The domain part is the Service Provider domain name, obtained from SSF. The content identifier shall be retrieved from service selection information (see annex L concerning the mapping between service selection information and SIP/SDP parameters). The TO header shall contain the same URI as in the "Request-URI" parameter. The FROM header shall indicate the public user identity of the user. Upon reception of the SIP 200 OK including SDP, the UE shall initiate COD session as described in clause 5.1.4.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.2 UE-initiated session initiation
|
The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon a request for a COD session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE. The "Request-URI" is related to the CoD session that the user wants to activate. The Request-URI shall be composed of a user and domain part as defined as follows: • The user part contains the content identifier in a free string format, as defined in TS 182 027 [2]. • The domain part is the Service Provider domain name, obtained from SSF. The content identifier shall be retrieved from service selection information (see annex L concerning the mapping between service selection information and SIP/SDP parameters). The TO header shall contain the same URI as in the "Request-URI" parameter. The FROM header shall indicate the public user identity of the user.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.2.1 Procedure for establishing the RTSP content control and content delivery channel
|
5.1.4.2.1.1 UE as SDP offerer An SDP Offer shall be included in the initial INVITE request. The SDP offer shall be done in accordance with media capabilities and policies available for the CoD session and with the parameters received from the SSF during UE service selection procedure (see annex L concerning the mapping between service selection information and SIP/SDP parameters) or from the SIP OPTIONS response. The SDP offer from the UE shall contain a media description for the RTSP content control channel and one for the content delivery channel. SDP session level parameters shall be used as specified in ES 283 003 [20]. The RTSP content control media description shall be carried by TCP and follow ES 283 003 [20]. The SDP parameters for the RTSP content control channel shall be set as follows: • a "m" line for an RTSP stream of format: m=<media> <port> <transport> <fmt>: - The media field shall have a value of "application". - The port field shall be set to a value of 9, which is the discard port. - The transport field shall be set to TCP or TCP/TLS. The former is used when RTSP runs directly on top of TCP and the latter is used when RTSP runs on top of TLS, which in turn runs on top of TCP. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 37 - The fmt parameter shall be included and shall be set to iptv_rtsp (ex. m=application 9 tcp iptv_rtsp). • An "a=setup" attribute shall be present and set to "active" as defined in ES 283 003 [20] (ex. a=setup:active). • An "a= connection" attribute shall be present and set as "new" as defined in ES 283 003 [20] (ex. a=connection:new). • A "c" line shall include the network type with the value set to IN, the address type set to IP4 or IP6 and IP address of the flow of the related RTSP content control (ex. c=IN IP4 <IP_ADDRESS>). NOTE: RTSP over UDP is out of scope of the present document. For each media stream controlled by the RTSP content control channel the SDP offer shall include a content delivery channel media description set as follows: • The "m=" line indicates the type of the media, the transport protocol and the port of the related content delivery channel. It may also include a fmt parameter which shall indicate the format given by the SSF, a subset of them or the format offered by the UE if none is given by the SSF. • The "c=" line shall include the network type with the value set to IN, the address type set to IP4 or IP6 and unicast address of the flow of the related content delivery channel, (ex. c=IN IP4 <IP_ADDRESS>). • The "b=" line shall contain the proposed bandwidth. If the user has fetched the bandwidth required for this particular content delivery channel during service selection procedure, the bandwidth attribute at media level shall be set to this value. Otherwise, this attribute shall be set to a pre-configured value (ex. b=AS:15000). • An "a=" line with a "recvonly" (ex. a=recvonly). Additionally, FEC streams may be defined, as described in clause 5.1.4.2.3. When receiving any SIP response, the UE shall examine the media parameters in the received SDP: the UE shall fetch the RTSP session ID from the "fmtp:iptv_rtsp h-session" attribute if present in the received SDP answer contained in the SIP response. This RTSP session ID shall be used for in RTSP media control messages and the UE shall subsequently use RTSP Method 1 for CoD playback control as described in clause 7.1.1. If fmtp:iptv_rtsp h-offset is specified in the SDP from MCF, the UE may use this as appropriate in subsequent RTSP media control messages. If no "fmtp:iptv_rtsp h-session" parameter was received in the SDP answer, the UE shall use RTSP method 2 for CoD playback control as described in clause 7.1.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.2.2 Procedure for establishing the RTSP channel separately
|
5.1.4.2.2.1 UE as SDP offerer The INVITE request shall contain an SDP offer of media description only for the RTSP channel. The SDP session level parameters shall be used as specified in ES 283 003 [20]. The SDP parameters for the RTSP channel shall be set as follows: • A "m" line for an RTSP stream of format: m=<media> <port> <transport> <fmt>: - The media field shall have a value of "application". - The port field shall be set to a value of 9, which is the discard port. - The transport field shall be set to TCP or TCP/TLS. The former is used when RTSP runs directly on top of TCP and the latter is used when RTSP runs on top of TLS, which in turn runs on top of TCP: ETSI ETSI TS 183 063 V3.6.1 (2014-08) 38 The fmt parameter shall be set to iptv_rtsp. • An "a=setup" attribute shall be present and set to "active" as defined in ES 283 003 [20]. • An "a= connection" attribute shall be present and set as "new" as defined in ES 283 003 [20]. NOTE: RTSP over UDP is out of scope of the present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.2A SCF-initiated session initiation
|
The UE shall support the procedures specified in ES 283 003 [20] for terminating sessions. Upon receipt of SIP INVITE request, the UE shall check the P-Asserted-Identity header for a well known PSI of the CoD service. If the UE does not already have all transport parameters to compose an SDP offer, the UE shall use SIP OPTIONS to retrieve missing parameters (e.g. RTP or UDP transport for MPEG2TS encapsulation or direct RTP, bandwidth, FEC layers addresses and ports). An SDP offer shall be included in the SIP 200 OK. The SDP offer shall be done in accordance with media capabilities and policies available for the CoD session and with the parameters received from the SSF during UE service selection procedure (see annex L concerning the mapping between service selection information and SIP/SDP parameters). The SDP offer from the UE shall contain a media description for: • either the RTSP content control channel as described in clause 5.1.4.2.2; or • for the RTSP content control channel and one for the content delivery channel as described in clause 5.1.4.2.1. SDP session level parameters shall be used as specified in ES 283 003 [20]. When the UE receives the ACK, the UE shall examine the media parameters in the received SDP: the UE shall fetch the RTSP session ID from the "fmtp:iptv_rtsp h-session" attribute if present in the received in the SDP answer contained in the ACK. This RTSP session ID shall be used for in RTSP media control messages and the UE shall subsequently use RTSP Method 1 for CoD playback control as described in clause 7.1.1. If fmtp:iptv_rtsp h-offset is specified in the SDP answer contained in the ACK, the UE may use this as appropriate in subsequent RTSP media control messages. If no "fmtp:iptv_rtsp h-session" parameter was received in the SDP answer, the UE shall use RTSP method 2 for CoD playback control as described in clause 7.1.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.2.3 Additional SDP lines for FEC streams
|
When the UE decides to connect to FEC stream(s) associated to the COD original stream, it shall include additional SDP lines in the SDP offer as follows: • One or more m-line(s) for each FEC stream exposed through the SSF: - It shall be set according to the mapping defined in clause L.3. - It shall contain a c-line according to the mapping defined in clause L.3. If the COD content is defined through a single m-line, a grouping line may be included. If the COD content is defined through several m-lines, grouping line(s) shall be included, one for each COD m-line that is associated to a FEC stream. • a=group:FEC:<original stream id> <FEC stream id> The present document supports only the DVB-IP AL-FEC Base layer, so there can be only one <FEC stream id> associated to an original stream: - The original stream id shall reflect the value held by the media description of one stream in its a=mid attribute. - The FEC stream id shall reflect the value held by the media description of the DVB-IP AL-FEC Base layer FEC stream (associated to the original stream) in its a=mid attribute. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 39 Furthermore, when grouping line is included, there shall be an additional media identification attribute within the m-line of the original stream that is within the grouping: • a=mid:<original stream id>.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.3 Session modification
|
In order to modify the session from the UE side, the UE shall send a re-INVITE or an UPDATE request as specified in ES 283 003 [20] for an originating UE. The UE shall not modify RTSP channel m-line description in the SDP if the media delivery streams controlled by RTSP are not removed (port not set to zero in m-lines) in the SDP. Upon receipt of a re-INVITE request or an UPDATE request, the UE shall modify the session as specified in ES 283 003 [20] if the request is acceptable to the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.3.1 Procedure for establishing the content delivery channel
|
5.1.4.3.1.1 UE as SDP offerer The UE shall send a re-INVITE or an UPDATE request containing SDP offer after acquiring the network parameters via RTSP DESCRIBE as specified in clause 7.1.2.2 in order to establish the content delivery channels. The media descriptions of content delivery channels shall be populated as follows: • Media descriptions acquired by DESCRIBE response are appended after the media description of RTSP channel. • The port number in "m=" line shall be replaced by the real receiving port of the UE. • "a=recvonly" attribute shall be inserted if the attribute is not specified. • Remove "a=" lines specific to RTSP (a=control, a=range, and a=etag). • If "c=" lines are specified in media descriptions, the addresses of "c=" lines shall be replaced by the address of the UE. The SDP parameters for the RTSP channel shall be set to the same parameters as specified in clause 5.1.4.2.2.1 except for the "a=connection" attribution. The attribution shall be set to "existing" as defined in ES 283 003 [20]. The SDP offer shall include one or more media description sets as follows: • The "m=" line indicates the type of the media, the transport protocol and the port on which the UE has to received the flows of the related content delivery channel. It may also include a fmt parameter which shall indicate the format given by the network parameters. • The "c=" line shall include the network type with the value set to IN, the address type set to IP4 or IP6, and unicast address of the flow of the related content delivery channel. These values are given by the network parameters. • The "b=" line shall contain the bandwidth. The bandwidth attribute shall be set to this value given by the network parameters. • An "a=" line with a "recvonly". Additionally, FEC streams may be defined, as described in clause 5.1.4.3.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.3.2 Additional SDP lines for FEC streams
|
When the UE decides to connect to FEC stream(s) associated to the COD original stream, it shall include additional SDP lines in the SDP offer as follows: • One or more m-line(s) for each FEC stream exposed through the SSF: - It shall be set according to the mapping defined in clause L.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 40 - It shall contain a c-line according to the mapping defined in clause L.3. • If the COD content is defined through a single m-line, a grouping line may be included. If the COD content is defined through several m-lines, grouping line(s) shall be included, one for each COD m-line that is associated to a FEC stream. The grouping line uses the "FEC" semantic as defined in RFC 5956 [25]: • a=group:FEC:<original stream id> <FEC stream id>. The present document supports only the DVB-IP AL-FEC Base layer, so there can be only one <FEC stream id> associated to an original stream: - The original stream id shall reflect the value held by the media description of one stream in its a=mid attribute. - The FEC stream id shall reflect the value held by the media description of the DVB-IP AL-FEC Base layer FEC stream (associated to the original stream) in its a=mid attribute. Furthermore, when grouping line is included, there shall be an additional media identification attribute within the m-line of the original stream that is within the grouping: • a=mid:<original stream id>.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.4 Session termination
|
The session termination will differ when using RTSP "Method 1" or RTSP "Method 2" as described in clauses 5.1.4.4.1 and 5.1.4.4.2. The different RTSP methods are described in clause 7 and annex Q.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.4.1 Session termination using RTSP Method 1
|
In order to terminate the session, the UE shall first close the RTSP session that was established during session initiation by closing the underlying TCP connection and then send a BYE request as specified in ES 283 003 [20]. Upon receipt of a BYE request, the UE shall then terminate the session as specified in ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.4.2 Session termination using RTSP Method 2
|
In order to terminate the session, the UE shall send a BYE request as specified in ES 283 003 [20]. The media teardown procedures using RTSP TEARDOWN as described in clause 7.1.2.6 shall be executed before the BYE is sent out. This would ensure that the BYE request does not close the RTSP content control channel ports at transport layer before RTSP TEARDOWN is sent. Upon receipt of a BYE request, the UE shall send a TEARDOWN request to terminate the RTSP session if non-persistent RTSP connection is used or if the TCP connection is open. The UE shall then send a SIP 200 OK response to the BYE request as specified in ES 283 003 [20]. NOTE: The UE may not be able to send TEARDOWN or receive a response for TEARDOWN when the resource in the network for RTSP session has been released when of receiving SIP BYE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.4.5 Procedures for handling COD Service action data
|
When a user requests to stop viewing a CoD with the intention of resuming it later, i.e. to 'park' the CoD stream (bookmark it to allow it be resumed later) and to tear down the session, the UE should send a SIP INFO request to the SCF. The content of that INFO request shall be as follows: • The value of the Request-URI shall be set to the one used in the related session. • From and To headers shall be set to the one defined during the session initiation procedure. • Call-ID shall be set to the same value as that of the CoD session. • CSeq shall be generated by UE following rules defined in ES 283 003 [20] for request within a dialog. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 41 • The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvcommand+xml". • The message body carries the service action data: - IPTVActionDataCommand shall be set to "Notify". - Notify shall be set to "IPTVCodActionData". - The matching "Available CoD" object shall be updated so that CoDDeliveryStatus is set to "Parked" and CoDOffset is set to the current reading cursor of the content. NOTE 1: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-cod+xml" is available in annex K of the present document. When a user is making a request that allows for some type of content insertion, i.e. without tearing down the session, the UE should send a SIP INFO request to the SCF. This may be during the pausing of content, to allow some other content to be played during the pause. The content of that INFO request shall be as follows: • The value of the Request-URI shall be set to the one used in the related session. • From and To headers shall be set to the one defined during the session initiation procedure. • Call-ID shall be set to the same value as that of the CoD session. • CSeq shall be generated by UE following rules defined in ES 283 003 [20] for request within a dialog. • The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvcommand+xml". • The message body carries the service action data: 1) IPTVActionDataCommand shall be set to "Notify". 2) Notify shall be set to "IPTVCodActionData". 3) The matching "Available CoD" object shall be updated so that CoDDeliveryStatus is set to "Paused", the expected duration is set to its value and CoDOffset is set to the current reading cursor of the content. NOTE 2: How to determine expected pause duration is up to the implementor of the UE. NOTE 3: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-cod+xml" is available in annex K of the present document. NOTE 4: Content insertion may still be performed on the UE and/or MF side, regardless of this procedure being used.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.5 Procedure for Service Configuration
|
The UE uses the XCAP to manage the IPTV user profile (see clause 6.1.2). In order to keep the IPTV User Profile data synchronized with the network elements and other terminals that the user might be using, the UE should subscribe from the SCF to changes in the XCAP IPTV documents. NOTE: Changes may result from XCAP manipulation and/or operator's action.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.5.1 Subscription to notification of changes
|
If subscription to notification of changes is used, the UE shall generate a SUBSCRIBE request in accordance with references [26] and [15]. The contents of the SUBSCRIBE request shall be as follows: • The value of the Request-URI shall be set to the IMS public user identity associated to the profile or to a pre-configured value or to a value received from the CNGCF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 42 • The From header shall be set to the IMS public user identity associated to the profile. • The To header shall be set to a URI that identifies the IPTV service provider (e.g. PSI). • The Accept header shall include the following values: - application/xcap-diff+xml. • The Event header shall be set to the "xcap-diff" event package. Upon receipt of a 2xx response to the SUBSCRIBE request, the UE shall store the information for the established dialog and the expiration time as indicated in the Expires header of the received response. The UE shall automatically refresh the subscription, either 600 seconds before the expiration time if the initial subscription was for greater than 1 200 seconds, or when half of the time has expired if the initial subscription was for 1 200 seconds or less. If a SUBSCRIBE request to refresh a subscription fails with a non-481 response, the UE shall still consider the original subscription valid for the duration of the most recently known "Expires" value according to ES 283 003 [20]. Otherwise, the UE shall consider the subscription invalid and start a new initial subscription according to ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.5.2 Processing of notifications
|
Upon receipt of a NOTIFY request on the dialog which was generated during subscription, the UE shall look for a message body with a content-type header indicating "application/xcap-diff+xml" stores its contents for further processing and return a SIP 200 OK response to the NOTIFY request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.6 Procedure for IPTV presence service
|
If presence service is used, the UE shall implement the role of a PUA as specified in ES 283 030 [21]. Publication of IPTV specific information in presence document depends on user-configurable data stored in the user equipment. Depending on the user configuration, the UE may send a SIP PUBLISH request in the following cases: - On receipt of a final SIP 200 OK concerning a BC session initiation procedure. - On receipt of a final SIP 200 OK concerning CoD session initiation procedure. - On receipt of a final SIP 200 OK concerning N-PVR content session initiation procedure. - On receipt of a final SIP 200 OK concerning an IPTV session teardown procedure. During a BC session, the UE may also send a PUBLISH request after having performed a channel-change (i.e. sending IGMP or MLD request for a particular BC service) or after the timer Tcc associated to the channel change has elapsed if this timer is activated as described in annex M. NOTE 1: In order to decrease the data size and reduce the redundancy of IPTV service access history data, it is recommended that UE send the PUBLSIH request based on the user's request or based on local policy, e.g. send service information every 10 minutes or under the user's indication to send out the request, which is out scope of the present document. When activated, the timer Tcc is triggered at every channel-change. The content of the PUBLISH request shall be as follows: - The Request-URI of the To and From headers shall be set to the public user identity of the user. - The Event header shall be set to the "presence" event package. - The content type shall be set to "application/pidf +xml". The presence XML document included in the PUBLISH body shall conform to ES 283 030 [21]. The "Entity" element shall be present and set to the public user identity of the user. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 43 The "Activity" element shall be present and set to "TV". Additional IPTV presence elements are defined in annex E and may be included in the presence documents published by the UE: • The "BCServicePresence" element is part of the "tuple" component according to the presence data model. It is composed of: - "CurrentBCServiceID" element: it indicates the currently activated BC service. - "CurrentBCProgramID" element: it indicates the currently watched program. • The "CoDServicePresence" element is part of the "tuple" component according to the presence data model. It is composed of: - "CurrentCoDContentID" element: it indicates the currently watched CoD content. • The "NPVRServicePresence" element is part of the "tuple" component according to the presence data model. It is composed of: - "CurrentNPVRContentID" element: it indicates the currently watched N-PVR content. • The "ServiceAccessHistoryPresence" element is part of the "tuple" component and the "ServiceAccessHistoryID" element is the 'id' attribute according to the presence data model. It is composed of: - "ServiceType" element: it indicates the service type of the watched IPTV service. - "ReferencedContentID" element: it identifies the associated content in the context of specific ServiceType. - "Rating" element: it indicates the user rating for the referenced content. - "AccessStartTime" element: it indicates the time accessing the IPTV service. - "AccessEndTime" element: it indicates the time when the access of the IPTV service is ended. - "HistoryExpireTime" element: it indicates the expiring time of the IPTV service access history item. • The "ServiceStateDataPresence" element is part of the "tuple" component and the "ServiceStateDataID" element is the 'id' attribute according to the presence data model. It is composed of: - Zero or more "IPTVServiceState" elements, which identify the services that the SSC is composed of. The "IPTVServiceState" element is composed of: "ServiceType" element: it indicates the service type of the watched IPTV service. "ReferencedContentID" element: it identifies the associated content in the context of specific ServiceType. "ServiceState" element: it contains service state information that can be enumerated, e.g. trick play status or - commands. "ServiceStateInformation " element: it contains additional service state information, e.g. state (transition) history. "ServiceStateExpiryTime " element: it indicates the expiry time of the IPTV Service State. The default value of ServiceStateExpiryTime indicates that it expires when the associated ongoing service is terminated. - If the ServiceType element has the value "BC", then the following element is applicable: "TrickPlayActivated" element: it indicates whether BC trickplay is activated. - If the IPTVServiceTypeIdentifier has the value "SSC", then the following elements are applicable: "SSCRoomID" element: it identifies the SSC Room for Shared Service Control. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 44 "IPTVServiceState" element: it identifies the services that the SSC is composed of. The "IPTVServiceState" element is described above. - If the IPTVServiceTypeIdentifier has the value "PSC", then the following elements are applicable: "PSCid" element: it identifies a specific PSC service for Personalized Service Composition. "IPTVServiceState" element(s), which identify the services that the PSC is composed of. The "IPTVServiceState" element is described above. NOTE 2: The data model for SSC - and PSC Service State follows the so-called "composite design pattern". The individual BC and CoD Service States have their own ServiceState and ServiceStateInformation attributes, which are associated in the combined SSC - or PSC Service State. NOTE 3: The collection of Service State Data (from UE, network elements, external applications and/or other) is outside the scope of the present document. NOTE 4: The availability of Service State Data is optional, as indicated in TS 182 027 [2]. In the XML document, each service is described thanks to the "service-description" OMA parameter as specified in OMA-TS-Presence-SIMPLE-V1 [23]. A new "service-id" is defined for this purpose with the following values IPTV-BC, IPTV-CoD, IPTV-NPVR, IPTV-SAH, IPTV-SSD. A "class" parameter can also be added with the value "IPTV". The activation/deactivation of this service is reported thanks to the "status parameter present in the relevant "tuple. An example of the use of this parameter in the XML document is described in annex E. The IPTV presence authorization rules and common policy shall be in conformance with the OMA-TS- Presence_SIMPLE_XDM-V2_0 [54], RFC 5025[53] and RFC 4745[52]. NOTE 5: Additional privacy and regulatory aspects affecting presence management and policy mechanisms are outside the scope of present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.6.1 Subscribing to presence
|
When the UE intends to retrieve one user's IPTV presence, it shall generate a SUBSCRIBE request for the "presence" event package as specified in ES 283 030 [21]. When the UE indicates to retrieve the IPTV service access history attribute or the IPTVServiceStateData attribute of the presence, the SUBSCRIBE request shall contain a message body for defining the SAH or the SSD information as the preferred notification information to be delivered. The contents of the SUBSCRIBE request shall be as follows: • The content Type header shall be set to "application/simple-filter+xml". • A message body shall be present for defining the structure of the filter criteria, and the filter criteria is present as an XML document as follows: 1) The <what> element shall be included, containing one or more <include> elements. 2) The <include> element shall include a <type> attribute with the value of "xpath", and the value of the <include> element shall be set to "/presence/tuple/SAH" or "/presence/tuple/SSD". 3) The <trigger> element may be included, containing one or more <changed> elements. 4) The <changed> element may include <from> and <to> attribute, and the <changed> element may be set to "/pidf:SAH/pidf:AccessStartTime". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 45 Upon receipt of a 2xx response to the SUBSCRIBE request, the UE shall store the information for the established dialog and the expiration time as indicated in the Expires header of the received response. The UE shall automatically refresh the subscription before the expiration time expires according to RFC 3265 [69]. The filter criteria complies to "Functional Description of Event Notification Filtering" [40] and "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering" [41].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.6.2 Receiving presence notifications
|
Upon receipt of a NOTIFY request on the dialog which was generated during subscription, the IPTV application within the UE shall parse the XML document contained in the message body to retrieve and display the presence information.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7 Procedure for PVR Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7.1 Procedures for PVR Service Capture Request
|
The SIP MESSAGE method is used here to achieve what is described in the architectural document (TS 182 027 [2]) as "PVR content capture request". This request may be done in an impulsive way or offline.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7.1.1 Procedures for Impulsive Request
|
This use case is itself divided in two sub-cases: Case 1: The user does not specify any end date and time for the recording. This can be seen as a case of "Park and pickup TV" as described in TS 182 027 [2]: In this case the UE shall send a SIP MESSAGE request to SCF requiring Bookmark setting. The contents of the SIP MESSAGE request shall be as follows: • The Request-URI in the MESSAGE request shall be the well known PSI (Public Service Identifier) of the BC Service. NOTE 1: This is the same value as the Request-URI for BC service session initiation. • From and To headers shall be set to the public identity of the user issuing the MESSAGE message. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. • The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvcommand+xml". • The message body carries the service action data: the matching "BC Bookmarks" object shall be created so that: - IPTVActionDataCommand shall be set to "Record". - Record shall be set to "IPTVBcActionData". - BCServiceId is set to the value of the current channel. - ProgrammeId is optionally set to the value of the current programme. - Bookmark is set to the current timestamp if the UE has the knowledge of such timestamp (e.g. through SNTP). If the UE is not aware of such current timestamp, Bookmark is set to a default value: "NOW" which implies that the content capture is initiated as soon as the N-PVR SCF gets the request. NOTE 2: BookmarkExpiryTime may be updated in two ways. It can be updated according to the user preference pre-set by the user, or according to the service policy defined by the service provider. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 46 Case 2: The user specifies an end date and time for the recording: In this case the UE shall send a MESSAGE request to the SCF. The contents of the SIP MESSAGE request shall be as follows: • The user-part value of the Request-URI shall be set to the BC Service Package ID that the BC service to be recorded belongs to. • From and To headers shall be set to the public identity of the user issuing the MESSAGE message. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. • The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvcommand+xml". • For N-PVR, the message body carries the service action data: the matching "NPVR item" object shall be created so that: - IPTVActionDataCommand shall be set to "Record"; - Record shall be set to "IPTVNpvrActionData"; - NPVRContentId is not set; - BCServiceId is set to the BC Service to be recorded; - RecordStartDate is set to the current timestamp if the UE has the knowledge of such timestamp (e.g. thanks to SNTP). If the UE is not aware of such current timestamp, RecordStartDate should be set to a default value: "NOW" which implies that the content capture is started as soon as the NPVR SCF gets the request; - RecordEndDate is set to the end date/time when the recording should stop and would correspond to what the user has specified. NOTE 3: NPVRContentExpiryTime may be updated in two ways. It can be updated according to the user preference pre-set by the user, or according to the service policy defined by the service provider. • For C-PVR, the message body carries the service action data: the matching "CPVR item" object shall be created so that: - IPTVActionDataCommand shall be set to "Record"; - Record shall be set to "IPTVCpvrActionData"; - CPVRContentId is not set; - TargetUEId shall be set to the public GRUU or SIP instance ID instead of GRUU; - BCServiceId is set to the BC Service to be recorded; - RecordStartDate is set to the current timestamp if the UE has the knowledge of such timestamp (e.g. thanks to SNTP). If the UE is not aware of such current timestamp, RecordStartDate should be set to a default value: "NOW" which implies that the content capture is started as soon as the PVR SCF gets the request; - RecordEndDate is set to the end date/time when the recording should stop and would correspond to what the user has specified. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 47
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7.1.2 Procedures for Offline Request
|
A user may request to record a live programme that has not started yet. In this case the UE shall send a SIP MESSAGE request to the SCF. The content of the SIP MESSAGE request shall be as follows: • The user-part of the Request-URI shall be set to the BC Service Package ID that the BC service belongs to. • From and To headers shall be set to the public identity of the user issuing the MESSAGE message. • CSeq shall be generated by UE. • The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvcommand+xml". • For N-PVR, the message body carries the service action data: the matching "NPVR item" object shall be created so that: - IPTVActionDataCommand shall be set to "Record". - Record shall be set to "IPTVNpvrActionData". - If the recording is requested on a specific entry in the EPG: NPVRContentId is set to the matching ProgrammeId. - If the recording do not match a specific entry in the EPG: NPVRContentId is not set. BCServiceId is set to the BC Service to be recorded. RecordStartDate is set to the date/time when the recording has to start as specified by the user. RecordEndDate is set to the date/time when the recording has to be terminated and is specified by the user. NOTE: NPVRContentExpiryTime may be updated in two ways. It can be updated according to the user preference pre-set by the user, or according to the service policy defined by the service provider. • For C-PVR, the message body carries the service action data: the matching "CPVR item" object shall be created so that: - IPTVActionDataCommand shall be set to "Record"; - Record shall be set to "IPTVCpvrActionData"; - If the recording is requested on a specific entry in the EPG: CPVRContentId can be set to the matching ProgrammeId. - If the recording do not match a specific entry in the EPG: CPVRContentId is not set. TargetUEId shall be set to the public GRUU to the SIP instance ID instead of GRUU. BCServiceId is set to the BC Service to be recorded. RecordStartDate is set to the date/time when the recording has to start as specified by the user. RecordEndDate is set to the date/time when the recording has to be terminated and is specified by the user.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.