6. SIP and SIP/SDP
6.3 Protocols for Service Access and Control Functions
6.3.1
Service Provider discovery
6.3.1.1
Protocol for UNIS-8 and NPI-30
The IPTV Service Provider Discovery FE SHALL generate and/or provide the Service Provider Discovery information. To retrieve Service Provider Discovery information, the OITF SHALL request the IG to send a SUBSCRIBE request which shall be forwarded to the IPTV Service Provider Discovery FE via the ASM FE. See Section
5.3.1.1 Protocol over HNI-IGI for the Managed Model
The OITF MAY include a SIP SUSCRIBE message body associated with the appid
“urn:oipf:application:iptv-SP-discovery”. The message body SHALL include the capabilities of the OITF which are sent to the Service Provider Discovery FE. The details of the SIP SUBSCRIBE are as specified in [TS183063], Section 5.1.2.2.1.
The Content Type header SHALL be set to “application/oipf-iptvueprofile+xml” The UserEquipmentID is a unique global identifier of the device.
The User Equipment Class SHALL take values “TV-OITF”, “STB-OITF”, according to the implementation options in Release 1 Architecture specification [ARCH] Annex D.
When the Service Provider Discovery FE receives a SUBSCRIBE request, it MAY check the user’s IPTV subscription profile and provide a personalized Service Provider Discovery information to the OITF. Filtering may also be
performed if device capabilities are available to the SDF.
If the Service Provider Discovery FE receives a SIP SUBSCRIBE message body from the OITF carrying UE capabilities, the Service Provider Discovery FE shall process the SIP request specified in [TS183063] Section 5.2.2.2 On successful subscription, the Service Provider Discovery FE SHALL generate a 200 OK response. The Service Provider Discovery FE SHALL then send a NOTIFY request to the OITF in accordance with RFC 3265 [SIP-EVNT]. The Service Provider Discovery Information SHALL be delivered in the message body of the SIP NOTIFY which is set as follows:
• Extend the existing “ua-profile” event package for SIP NOTIFY as follows: - The Event header SHALL be set to the “ua-profile” event package. - The “effective-by” parameter for the event header SHALL be set to 0. - The content type SHALL be set to “application/oipf-iptvspdiscovery+xml”. Refer to [TS183063] Section 5.2.2.2.
Note: If the above extension is not accepted by the IETF, then the use of a new method (New Event package) should
When the IPTV Service Provider Discovery FE knows of a change to the Service Discovery, Service Provider or Selection Information, the IPTV Service Provider Discovery FE SHALL inform the OITF of this change by sending a SIP NOTIFY message.
6.3.2
User Registration and Network Authentication
6.3.2.1
User Identity Modelling
Every IMS Subscription SHALL be allocated a single unique default IMS Pubic Identity by the Service Platform Provider. This SHALL be the identity that is registered in the IMS domain when an OITF is turned on.
Every IPTV end-user in an IMS Subscription MAY be associated with an IMS Public User Identity by the Service Platform Provider.
This release complies with option 1 in Annex D.4 in [ARCH].
6.3.2.2
Procedure for User Registration and Authentication in a Managed Model on
UNIS-8
The following SHALL be supported by the IG on the UNIS-8 interface for user registration:
• The IG SHALL support the 3GPP IMS registration procedure as per ETSI ES 283 003 [TISPAN]. This includes handling of user authentication and authorization. This procedure shall be invoked upon receipt of an HTTP POST from the OITF with the REGISTER method.
• The IG SHALL report to the OITF the final outcome of any registration or de-registration.
• The IG SHALL be stateful for all successful registrations until de-registration occurs. The following SHALL be supported by the IG on the UNIS-8 interface for user de-registration:
• The IG SHALL support the 3GPP IMS de-registration procedure as per ETSI ES 283 003 [TISPAN]. This procedure shall be invoked upon receipt of an HTTP POST from the OITF with the REGISTER method. The following SHALL be supported in the IG on UNIS-8 for subscription to the Registration event:
• The IG SHALL support subscription to the registration-state event package as per ETSI ES 283 003 [TISPAN].
• On request from the OITF, the IG SHALL refresh the registration-state event package subscription in accordance with ETSI ES 283 003 [TISPAN].
• The IG SHALL NOT store any registration event related data, but SHALL be stateful of the subscription. The IG SHALL support terminating a subscription to the registration-state event package as per ETSI ES 283 003 [TISPAN].
6.3.3
Notification of Service Profile changes
6.3.3.1 Notification of Service Profile changes Protocol on UNIS-8
6.3.3.1.1
Subscription to Notifications of Service Profile changes
If subscription to notification of changes is requested by the OITF, the IG SHALL send a SUBSCRIBE request to the IPTV Service Profile FE in accordance with IETF draft-ietf-sip-xcapevent-03 [XCAP-EVT] and draft-ietf-simple- xcap-diff-09.txt [XCAP-DFF].
The IG will process the request from the OITF and will generate a SUBSCRIBE request, that SHALL be as specified in [TS183063] Section 5.1.5.1.
Note: For changes that apply to a very large number of subscribers, it is up to Service Provider to set up proper rules in the ‘notifier function’ to make the notification procedure scalable.