hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11 Mode of operation
| |
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.1 General Principles
|
Emulating PSTN/ISDN services using the IMS-based PES architecture described in the present document assumes that the logic of the service to be emulated resides in one or more application servers rather than in the AGCF or in gateways. Emulating most PSTN supplementary services requires that at least one Application Server be inserted in the SIP signalling path. For certain call configurations, this requires that encapsulated ISUP information be sent/received by some of these application servers (TS 183 043 [5]). The logic embedded in the AGCF is either interworking logic (e.g. the AGCF has to know how to convert the information contained in an incoming SIP INVITE into a presentation message of the protocol for display services over analog lines as defined in EN 300 659 [12]) or service independent feature logic. On receipt of an off-hook event from a media gateway at the beginning of a call initiation sequence, the AGCF shall apply dial tone unless not required by a feature associated with that line (e.g. fixed destination call). The AGCF's behaviour on receipt of other line events depends on whether or not the AGCF is capable of implementing the feature logic associated with that line, as an example, on a register recall event notification from a media gateway, the AGCF shall determine whether or not to apply dial tone if the AGCF is capable of implementing feature logic for that line; however, if the AGCF is not aware of the feature logic associated with a line and supports mid-call invocation of supplementary services, then it shall send an indication to the AS that register recall has occurred and wait for an indication back as to whether or not dial tone should be applied. Although some application servers may be dedicated to the provision of PES-specific services, the PES architecture does not restrict the type of applications that a PES-user can access (see figure 7). ETSI ETSI TS 182 012 V2.1.4 (2008-03) 22 IMS-based PES Application Servers Embedding PSTN/ISDN emulation logic Application Servers With other types of logic ISC P-CSCF MG AGCF MGCF SS7/TDM networks VGW Gm Gm P1 P1 Analog access ISDN access Figure 7: Service Access via the PES
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.2 Service Provisioning
| |
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.2.1 Provisioning in the UPSF
|
The service profile of PES users is stored in the UPSF as for any other type of user. Appropriate filter criteria are set to ensure that PES-enabled Application Servers are involved in the processing of calls from/to PES-users. Setting these criteria does not require any specific service point trigger beyond those used in relation to the IMS subsystem ES 282 007 [2].
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.2.2 Provisioning in the AGCF
|
The following IMS parameters are assumed to be available, for every line, in a local data base of the AGCF: - private user identities; - public user identities; - home network domain names; - address of the AS to be used for service configuration management (for use over the Ut reference point); and NOTE: Some of the line parameters mentioned above may be shared across a number of lines (e.g. private user identities are shared by all the lines belonging to an implicitly registered group and home network domain names can be shared across all the lines belonging to the same home IMS-based PES operator). The present document does not mandate a particular data model to be implemented in the AGCF provided that the above information is available and uniquely identifiable by the AGCF on a per-line basis. - (optionally) a temporary public user identity that the line will be implicitly registered against. The use of temporary public user identities in the present document is the same as that described in TS 182 006 [3], i.e. a temporary public user identity is used in the initial registration to register a group of public user identities associated with it. Temporary public user identities shall be, for the present document, provisioned into the AGCF (which contains the functionality of a UE) by means outside the scope of the present document. The allocation of private and public user identities is left to each operator to decide. Two approaches are identified: - One private user identity is assigned to a group of lines/subscribers. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 23 In this scenario, the operator may choose to allocate a temporary public user identity for a group of lines to be implicitly registered against. When available, such temporary public user identity shall be used in the initial registration request. - One private user identity is associated with each line connected to the media gateways controlled by the AGCF. Each private user identity is associated with one home network domain name. The association between a line (represented by a termination identifier on a media gateway) and one or more public user identities is provisioned in the AGCF. The public and private user identities must be known by both the AGCF and the UPSF. It is up to the network operators to ensure that the AGCF and UPSF have consistent information. In addition to the above, each line may be characterized by a line type (e.g. loop calling, PBX, line reversal on answer etc. as described in ETR 150 [13]). The following information may also be provisioned on a per-line basis or on a per media gateway basis: - a default dial-tone; - a default digit-map; and - a default ring cadence. Depending on operator-specific requirements and the features implemented, certain "feature marks" may also be needed in the AGCF on a per-line basis; examples of this include: - Calling Line Identity display to user equipment - this feature mark may be needed in cases where, even if no Calling Line Identity information is signalled to the AGCF, the AGCF needs to instruct to the A-MGW whether to send a "Calling Line Identity unavailable" indication or no indication at all to that line depending on whether or not the user has subscribed to Calling Line Identity presentation services. - Priority line – this feature mark may be required in cases where the AGCF needs to treat calls from or to that line as having priority over other lines controlled by the same AGCF. - Fixed destination call/deferred destination call/ normal line - this feature mark may be required for the AGCF to know whether or not dial tone needs to be applied after off-hook event is detected in the line. In the case of deferred destination call lines, dial tone needs to be applied for a period of time after which dial tone needs to be removed and a call to the fixed destination address (as specified below) be placed. - Fixed destination address - this feature mark is required for the AGCF to know the address it needs to place a call to for lines marked as fixed destination call or deferred destination call lines. - Mid-call Malicious Call Indication - this feature mark may be needed when mid-call Malicious Call Indication is required since, an AGCF that implements service independent feature logic for dealing with mid-call events would autonomously apply dial tone after a register recall event unless this feature mark is activated. The AGCF needs to be made aware of dial tone changes in case some specific supplementary services are activated. For that purpose it subscribes to the appropriate SIP events.
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.3 Registration
|
Registration and deregistration procedures are initiated by Voice over IP gateways (A-VGW and R-VGW) at the Gm reference point on behalf of each line or group of lines it serves. The rest of the procedures are identical in the PES and IMS subsystems. Registration and deregistration procedures are initiated by the AGCF on behalf of each line or group of lines connected to the media gateways it controls, based on the information contained in service change messages received from those media gateways and local configuration information. The rest of the procedures are identical in the PES and IMS subsystems. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 24 A group of lines is represented by a set of public user identities sharing the same private user identity, home domain and, optionally, a temporary public user identity (to be used in the initial registration). One of the public user identities is explicitly registered; note that, if present, the temporary public user identity shall be used for the initial explicit registration. Other public user identities are implicitly registered. The list of implicitly registered identities is returned by the UPSF to the AGCF. It should be noted that creating large registration groups may lead to excessively long signalling messages, any issues associated with this need to be solved by implementation. If the list of registered identities returned by the UPSF does not match the list of public user identities associated with the private user identity, the AGCF should take appropriate management actions outside the scope of the present document.
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
11.4 Service code commands
|
Users of analog terminals usually manage supplementary services using service code commands using the syntax defined in ETS 300 738 [10], clause 6.1.1. The AGCF has the necessary service independent logic to determine whether a special dial tone needs to be delivered after the service prefix. In case dial tone needs to be applied, the AGCF can also determine whether a special dial tone needs to be delivered.
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
12 AGCF behaviour
| |
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
12.1 AGCF components
|
The AGCF can be decomposed into three logical components: • The Media Gateway Controller. • The Feature Manager. • The IMS Agent. Figure 8 provides an overview of the AGCF logical structure. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 25 Session Processing Registration Processing Event Subscription /Notification CLF NASS AGCF SIP stack Gq' R-MGF /A-MGF SPDF RACS P1 Mw e2 Feature Manager IMS Agent MGC IMS Agent IMS Agent MGC H.248 Stack Line-based Configuration data Ut Figure 8: AGCF internal structure
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
12.2 Media Gateway Controller
|
The Media Gateway Controller component performs the following functions: • keep track of the media gateway state (e.g. registration/deregistration); • keep track of the line state (e.g. idle, active, parked, out of service, etc.); • control the connection configuration (media flows topology and directionality) in media gateways; • control the connection of tones and announcements in media gateways; • receive line events and DTMF digits from media gateways; • request media gateways to monitor line events and DTMF digits; • perform basic digit analysis sufficient determine end of dialling to detect emergency calls (see note); • provide line signals to media gateways; • download "Digit Maps" to media gateways; • controls media mapping and transcoding; • controls signal processing features such as echo cancellation in media gateways. NOTE: The full digit analysis procedure required for normal call routing purposes is performed by the S-CSCF and Application Servers. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 26
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
12.3 Feature Manager
|
The Feature Manager is the functional block in AGCF that provides the coordination between the IMS core and the Media Gateways. For that, it holds a call and connection model that associate lines to call states and IMS dialogs. Figure 9 shows a call and connection configuration where an analogue line is connected to two parties, each of these relationships being associated with a call state and a SIP dialogue. SIP Dialogue #1 SIP Dialogue #2 Analogue Line Leg#2 Leg#1 Dialogue/call state Dialogue/call state Figure 9: AGCF Call and Connection model The feature manager component performs the following functions: • Perform mediation of signalling events between Media gateways and S-CSCF in accordance with the connection model of AGCF. • Request the registration of lines to the IMS core. Two possible mechanisms are be supported: - registration/deregistration of individual endpoints or registration/deregistration of the group of lines. • Interacts with Application Servers to retrieve the current dial tone from the subscriber profile. • When the AGCF supports service-independent feature logic for mid-call events, the feature manager shall invokes basic features logic for processing mid call events, based on the call state and connection configuration. • When the AGCF does not support service-independent feature logic for mid-call events, the feature manager shall send an indication to the AS that a certain mid-call event has occurred and wait for an indication back as to what actions should be performed next NOTE: User input leading to mid call events may take various forms (e.g. register-recall, register-recall followed by one or more digits, one or more digits, etc.) depending on the network policies. Signalling procedures in support of the above processing logic is outside the scope of this technical specification but shall be compatible with the constraints of the P1 and Mw reference points. • Perform the mapping between alert information received from SIP signalling and ring patterns. • Subscribe to the state of the lines behind media gateways in order to be informed when an individual line is deregistered (e.g. due to operational action a line may be no longer active). • Manage the subscription for event report request from AS. The notification is delivered to the right AS. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 27
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
12.4 IMS Agent
|
The IMS agent encompasses the functionality of an IMS UE and P-CSCF. It communicates with other IMS entities using the SIP profile described in ES 283 003 [4]. The following functionality is implemented in the IMS agent: • Send/receive messages to/from the IMS entities. The received messages are sent to the Feature Manager that is responsible for processing them in accordance with the actual connection model of the line. • Communicate with an I-CSCF (potentially via an IBCF) in order to address the right S-CSCF in the same or a different operator's network. The identity of I-CSCF can be derived from DNS query. • Interact with the Resource and Admission Control Subsystems (RACS). • Interfaces with the Network Attachment Subsystem (NASS) in order to retrieve information related to the IP- connectivity access session (e.g. physical location of the user equipment), when the media gateway is located in the customer premises (i.e. residential media gateway). The IMS agent is considered a trusted network element and therefore, security is equivalent to other IMS network elements.
|
b708cbb24b9b1d04a3865f5f2ea8c6ab
|
182 012
|
13 Physical scenarios
|
Various physical scenarios can be derived from the functional architecture described in the previous clauses. How this functional architecture maps to physical devices and how many of the functional interfaces remain visible in a network implementation is outside the scope of standardization. Possible implementations range from obvious scenarios with a one to one mapping between functional entities and physical entities, to physical architectures mimicking the hierarchical architecture of legacy networks (i.e. local and transit levels), based on only two types of physical nodes: call servers and media gateways. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 28 Annex A (informative): Areas of discussion and potential open items So far, areas of discussion and potential open items include at least the following: • Registration through the AGCF: - Overlap sending. • Interworking between AGCF and AS: - Clarify what parts of encapsulated ISUP are needed. Alternative solutions to it. - Usage of Ut reference point. • Alignment with 3GPP: - Clarify the usage of encapsulated ISUP information. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 29 History Document history V2.1.4 March 2008 Publication
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
1 Scope
|
The present document specifies network requirements: • to support connection and interoperation of business communication capabilities (either hosted in NGCN or NGN) to the NGN; and • to support connection and interoperation of business communication capabilities to other business communication capabilities (either hosted in NGCN or NGN); and • to support connection and interoperation of business communication capabilities to other business communication capabilities located in or connected to the ISDN and PSTN; and • to support PABX functionality (hosted enterprise services) in an NGN. NOTE 1: Network requirements to support connection of NGCN directly connected to an NGN are specified. NOTE 2: Attachment of legacy PBX functionality to the NGN is not specified in the present document. It is assumed that existing legacy service requirements apply in this case. The present document also specifies network requirements for communication between NGCN capabilities (including user equipment) to other NGCN capabilities of the same enterprise through the NGN (e.g. geographically separated). The present document does not specify NGCN services, nor does it specify network based application services provided to a user of an NGCN.
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
2 References
| |
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the 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. The following referenced documents are necessary for the application of the present document. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void . [9] ETSI TS 122 519: "Universal Mobile Telecommunications System (UMTS); LTE; Business Communication Requirements (3GPP TS 22.519)". ETSI ETSI TS 181 019 V3.0.0 (2015-10) 6
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Void. [i.2] Void.
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
3 Definitions and abbreviations
| |
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TS 122 519 [9] apply.
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TS 122 519 [9] apply.
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
4 Capabilities for the support of IP multimedia services
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
5 PSTN/ISDN emulation service
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
6 Codecs services
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
7 Network attachment requirements
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
8 CPE configuration
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
9 Network management
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
10 Control of processing overload
|
The provisions of the present document are contained in ETSI TS 122 519 [9]. ETSI ETSI TS 181 019 V3.0.0 (2015-10) 7
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
11 IP addressing
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
12 NGN interconnection
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
13 IPTV
|
The provisions of the present document are contained in ETSI TS 122 519 [9].
|
60c334e5a4f7f64c2951525c2e46cc2e
|
181 019
|
14 Transport stratum
|
The provisions of the present document are contained in ETSI TS 122 519 [9]. ETSI ETSI TS 181 019 V3.0.0 (2015-10) 8 Annex A (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 03-09-2015 NTECH(15)12 _005 001 D Alignment with 3GPP TS 22.519 2.0.0 3.0.0 ETSI ETSI TS 181 019 V3.0.0 (2015-10) 9 History Document history V2.0.0 November 2007 Publication V3.0.0 October 2015 Publication
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
1 Scope
|
The present document describes the IPTV functional architecture and functions of an NGN Integrated IPTV system by integrating of IPTV functions into the NGN architecture. For example, interactions and information flows between the IPTV functional entities and other functional entities will be specified. The specification starts from outlining high-level IPTV functional architecture, functional groups and is further developed into the more detailed functional architecture, reference points and operational modes. The architecture is intended to support requirements defined by the respective ETSI TISPAN requirement definitions [1] and allow integration new or existing IPTV solutions (such as those defined by DVB, ATIS IIF, ITU, etc.) within the NGN architecture. The resulting architecture should, should rely as much as possible on common components and integrates, coexist with other TISPAN NGN services. The following areas are covered: • Authentication and authorization. • Content Protection (including DRM). • Capability exchange. • Resource Management. • Policy Management. • Charging. • User Profiles. The architecture focuses on closer integration between IPTV services and NGN networks, migration scenarios from existing solutions (i.e. DVB-IPI, ATIS-IIF) into NGN and common components.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
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.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 181 016 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [2] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [3] ETSI TS 122 240: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Service requirements for 3GPP Generic User Profile (GUP); Stage 1 (3GPP TS 22.240)". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 8 [4] ETSI TS 123 240: "Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Generic User Profile (GUP) requirements; Architecture (Stage 2) (3GPP TS 23.240)". [5] ETSI ES 282 001 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture ". [6] ETSI TS 182 027 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". [7] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)". [8] ETSI ES 282 007 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [9] ETSI ES 282 004 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [10] ETSI ES 282 003 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". [11] ETSI TS 187 003 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [12] ETSI ES 282 010 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Charging management [Endorsement of 3GPP TS 32.240 Release 7, 3GPP TS 32.260 Release 7, 3GPP TS 32.297 Release 7, 3GPP TS 32.298 Release 7 and 3GPP TS 32.299 Release 7, modified]". [13] ETSI TS 132 240: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Charging management; Charging architecture and principles (3GPP TS 32.240)". [14] ETSI TS 183 064 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Dedicated IPTV subsystem stage 3 specification".
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
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] "An application-level QoS comparison of inter-destination synchronization schemes for continuous media multicasting", Toshiro Nunome; Shuji Tasaka, IEICE transactions on communications, ISSN 0916-8516, Vol. 87 (2004), No. 10, pp. 3057-3067 (11). [i.2] ETSI ES 204 915 (all parts): "Open Service Access (OSA); Application Programming Interface (API) (Parlay 6)". [i.3] ETSI ES 202 504 (all parts): "Open Service Access (OSA); Parlay X Web Services; (Parlay X 3)". [i.4] ETSI TR 187 013: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on IPTV security architecture". [i.5] SCTE-130 part 1: "Digital Program Insertion - Advertising Systems Interfaces; Part 1 Advertising Systems Overview". [i.6] SCTE-130 part 2: "Digital Program Insertion - Advertising Systems Interfaces; Part 2: Core Data Elements". [i.7] SCTE-130 part 3: "Digital Program Insertion - Advertising Systems Interfaces; Part 3: Ad Management Service (ADM) Interface". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 9 [i.8] SCTE-35: "Digital Program Insertion Cueing Message for Cable". [i.9] ETSI TS 182 028 (V2.0.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; Dedicated subsystem for IPTV functions". [i.10] ITU-T Recommendation Y.1910: "IPTV functional architecture".
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
3 Definitions and abbreviations
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Inter-Destination Media Synchronization (IDMS): feature for exchanging arrival time and delay information, resulting in substantial synchronisation of the media outputs of two or more UEs, as presented to their users IPTV content identifier: super class of the identifiers that identify content in specific IPTV services media stream identifier: identifier carried in a unicast or multicast media stream that identifies that specific media stream
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ADM Ad Management Service ADS Ad Decision Service ADSS Ad Selection Service A-RACF Access Resource And Admission Control Function AS Application Server ASF Application Server Function BC Broadcast BCG Broadcast Content Guide BPG Broadcast Program Guide BTV Broadcast TV CA Conditional Access CDR Content Data Records CF Customer Facing CFIA Customer Facing IPTV Application CIS Content Information Service CM Content Marking CoD Content on Demand CR Content Recommendation CRS Content and Service Recommendation Service CSCF Call Setup Control Function CSP Content and Service Protection DHCP Dynamic Host Configuration Protocol DNG Delivery Network Gateway DNS Domain Name Server DRM Digital Rights Management EPG Electronic Program Guide FE Functional Entity GUP Generic User Profile HD High Definition ID IDentification IDMS Inter-Destination Media Synchronization IMS IP Multimedia Subsystem IP Internet Protocol ETSI ETSI TS 182 028 V3.5.1 (2011-02) 10 IPTV IP Television IPTVC IPTV Control iTV Interactive TV IUDF IP User Data Function MCF Media Control Function MDF Media Delivery Function MF Media Function MSAS Media Synchronization Application Server NASS Network Attachment SubSystem NAT Network Address Translation nCoD Near CoD NGN Next Generation Network NPT Normal Playout Time nPVR networked Personal Video Recorder PCh Personalized Channel pCoD Push CoD PES PSTN/ISDN Emulation Subsystem POIS Placement Opportunity Information Service PPV Pay Per View PSS Packet-switched Streaming Service PVR Personal Video Recorder QoE Quality of Experience QoS Quality of Service RACS Resource and Admission Control Subsystem RTCP Real Time Control Protocol RTP Real Time Protocol SC Synchronization Client SCF Service Control Function SCP Service & Content Protection SCS Service Capability Server S-CSCF Serving CSCF SCTE Society of Cable Telecommunications Engineers SD Standard Definition SD&S Service Discovery and Selection SDF Service Discovery Function SIS Subscriber Information Service SKMF Service Key Management Functions SMF Service Membership Functions SP Service Provider SPD Service Provider Discovery SPF Service Protection Functions SRV Service Record SSF Service Selection Function TAI Targeted Advertising TPF Transport Processing Function UCG User Created Content UDAF User Data Access Function UDF User Data Function UE User Equipment UGC User Generated Content UPSF User Profile Server Function URL Uniform Resource Locator XDMS XML Document Management Server
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4 NGN IPTV subsystem
|
This clause outlines architectural approach adopted in the present document. The approach is then applied to introduce high level IPTV architecture and functional groups in NGN architecture. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 11
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.1 Concept and Architectural Approach
|
The present document focuses on defining flexible functional architecture, which can: • allow development of new IPTV subsystem in NGN; • integrate existing IPTV subsystem in NGN; • extend both to support other NGN services; as defined in the service level requirements [1]. The support for other NGN services has a wide meaning, e.g. the functional architecture would allow coupling functionality of IPTV subsystem with functionality of PES or IMS subsystem, which in-turn may support some IPTV features as defined in [6]. In order to achieve high level of flexibility, the work is focused on identifying and standardizing functional entities and reference points, which needs to be exposed from IPTV subsystem to the rest of NGN. Internal IPTV functional entities and reference points are identified and described for the completeness of the end to end architecture without intend to standardize them. The architectural approach considers IPTV subsystem as a functional area, which is integrated into NGN via standardized reference points and delivers service level requirements, while allowing internal flexibility and extensions for new service types. The IPTV integrated subsystem is based upon IPTV domains defined in TS 181 016 [1], clause 4.1 IPTV Roles.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.2 High Level Architecture Overview
|
Figure 1 presents high-level NGN IPTV functional overview and location of IPTV capabilities in the TISPAN NGN. The high level overview illustrates principal functional groups for NGN IPTV services. The functional groups map to IPTV roles as defined in clause 4.3. The functional groups are used to derive more detailed functional architecture, however, allocation of functions across operational and organizational boundaries will vary between implementations. End- User Func- tions Application Functions IPTV Service Control Functions Transport Functions IPTV Media Control and Delivery Functions Manage- ment Func- tions Content Provider Func- tions Figure 1: High-level NGN based IPTV functional architecture
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3 Functional groups
|
In the context of the present document functional groups are used to describe several functional entities grouped together according to some condition, e.g. location in the certain functional layer. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 12
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.1 Application Functions
|
Within the present document, the term "Application Functions" includes IPTV and NGN Application Functions. NGN Applications: provides the user with rich multimedia applications distributed across multiple NGN subsystems. For example, session follow up or messaging exchange between fixed and mobile terminals, presentation of incoming calls and phone list management on TV, IPTV or gaming applications based on user presence. NGN applications also provide operators with centralized NGN management interface to multiple subsystems for content management, charging, interactions with IMS services, others. NGN applications may include application functions used across multiple service domains for applications interactions, e.g. IMS and IPTV interactions. NGN applications may include service mediation and coordination functionality. IPTV Applications: customer facing and operator facing. Customer facing IPTV applications provides the server side functions to enable customer facing IPTV applications, expose IPTV services to other NGN application and manage IPTV subsystem. Customer facing IPTV applications provide service provisioning, selection and authorization of IPTV services. Operator facing IPTV applications provide operator control over IPTV subsystem in NGN, content preparation and media management, content licensing, subscriber management, offer creation, user profiles. Server side IPTV applications expose IPTV services to NGN.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.2 IPTV Service Control and Media Delivery Functions
|
Enables operation of IPTV services in NGN. The key functionality of this layer is to provide, but not limited to, media distribution, selection and allocation of media delivery units, IPTV session control and management, interactions with other NGN components for admission control and resource allocation, as well as collecting charging and QoS information.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.3 Transport Functions
|
Transport Control Functions: contains common NGN components RACS and NASS, provides policy control, resource reservation and admission control as well as IP address provisioning, network level user authentication and access network configuration as defined in TISPAN. Transport layer definition includes definition from [5]. Transport Processing Functions: the Transport Process Functions represents network access links and IP core. The IP core is in charge of data transmission with quality of service support.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.4 End User Functions
|
Customer transport: provides connection to one or multiple access networks and one or multiple home network segments. UE: provides user interactions and control over delivery of IPTV and other NGN services. IPTV terminal processes serviced multimedia and presents it in user acceptable format. User interactions may include service discovery, selection and authorization. Multimedia processing may include requesting multimedia asset in supported encoded format, decoding and presenting it to the user in acceptable format, trick mode operators, channel change.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.5 Management Functions
|
The IPTV Management Functions include: Service Fulfilment: the functions required to fulfil the IPTV service to the End-User. Service Assurance: the functions required to assure the IPTV service provided to the End-User. Service Billing: the functions required to ensure proper billing to the end user of delivered IPTV services. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 13
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.3.6 Content Provider Functions
|
The functions provided by the entity that owns or is licensed to sell content or content assets. These are normally the sourcing of content, metadata and usage rights.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
4.4 IPTV services
|
NGN integrated IPTV supports the following IPTV services [1]: • Broadcast TV (with or without trick modes). • Content on Demand (CoD). • Personal Video Recording (cPVR, nPVR). • Pay Per View (PPV). • Interactive TV (iTV). • near CoD (nCoD). • push CoD (pCoD). • User Generated Content (UGC). • Profiling and personalization. • Content Recommendations (CR). • Advertising (Ad) and Targeted Advertising (TAI). • Messaging services. • Notification services. • Personalized channel. • Bookmarks or Content Marking (CM). Table 1A provides list of services and feature supported by NGN integrated architecture. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 14 Table 1A: IPTV services and features supported by NGN integrated IPTV subsystem NGN IPTV Release Service & Feature TISPAN R2 NGN dedicated IPTV subsystem TISPAN R3 NGN integrated IPTV subsystem Specification TS 182 028 R2 [i.9] Present document Linear/ Broadcast TV M M Linear/ Broadcast TV with Trick Play M M Time Shifted TV O O Content on Demand M M Push CoD M M Near COD M M Network PVR M M Client PVR NA O Audio M M Pay-Per-View M M Interactive TV M M Service discovery M M Service Information (EPG) M M Parental Control M M 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 M Targeted Advertising NA O User Generated Content NA O Internationalization O O Content recommendation NA O Games NA O Picture NA O Bookmarks (Content Marking) NA O Personalized channel NA O Personalized Service Composition NA O Service Portability NA O Service Continuation between IPTV UEs NA O Service Continuation fixed-mobile NA O Remote Control of IPTV services NA O Emergency Information NA O Interaction with 3rd Party application (e.g. Parlay) NA O Interaction with Internet Services NA O Service synchronization NA O Incoming call management O O NOTE: M - Mandatory, O- Optional, NA - not available or not specified (out of scope in release) in architecture. 5 NGN Integrated IPTV subsystem functional architecture The context of the IPTV architecture is represented "end to end" for completeness, starting from the UE on the left to the management functions and content providers functions on the right. However, the functions on the right (e.g. management and content provider) are outside the present document. Integrated NGN IPTV functional architecture is presented in figure 2. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 15 Service Layer NGN Applications UE M anagem ent Functions Consumer Transport Transport Layer IPTV Service Control Functions RACS NASS Delivery Network Gateway Transport Processing Functions IPTV Control SD&S Content Provider Functions IPTV Applications Media Delivery Function Ss Tr Sa e4 Gq’ Xp Configuration & Authentication NGN App UDF Ug IPTV Subscriber Management NGN Application IPTV UDF Customer Facing IPTV Applications e2 Ct2 Xc Media Control Function Media Acquisition Media Preparation Functions Ud Xd Charging Media Distribution UE & SCP Intr SCP UE & NGN Apps Intr Intr NGN & CF IPTV Apps IPTV Media Control & Delivery Functions M edia M anagem ent User Data Figure 2: NGN IPTV functional architecture The figure also includes reference points using dotted lines, which are shown for completeness and outside the present document. The two reference point outside the scope of the present document shown for completeness are NGN & Customer facing IPTV application interactions and Configuration and Authentication. The focus of the present document on the functions in the middle, namely IPTV functions in the service layer and in the transport layer for integration into NGN. The functions performed by the service layer are grouped into two levels: • the application functions for provisioning an IPTV service consumption by a given user (e.g. service selection, where "selection" is used in a wide sense, e.g. including the parental control rules, others); • the IPTV service control and delivery functions for the execution of a given instance of an IPTV service during service consumption (e.g. the user can experience and control the delivery of a given media content) and for the selection of Media Control Function and media delivery during the IPTV service establishment. The functions performed in the transport layer apply the principles of TISPAN NGN networks transport layer (see definition in [5]) to enable policy control, resource reservation, admission control, IP address provisioning, network level user authentication. The relationship between media management, media distribution and media preparation functions are presented for the completeness. However, interface definitions are outside the scope of the present document, which is represented by the dotted lines. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 16
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.1 Functional entities
|
The functional groups presented on figure 1 contain the following functional entities used to deliver NGN IPTV services.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.1.1 Core IPTV functions
|
NGN Application FE: application providing functionality across single or multiple subsystem, e.g. messaging exchange between fixed and mobile terminals, presentation of incoming calls and phone list management on TV, IPTV gaming applications based on user presence, NGN applications may include service mediation and coordination capabilities. NGN Integrated IPTV supports two approached to user data location: federated and consolidated, as discussed in details in clause 9.2. In the federated approach user data is located close to application in the following functional entities: • NGN Application User Data FE (NGN App UDF): NGN App user data function is responsible for handling NGN application and user data. NGN App UDF allows integration of application data across NGN applications either using 3GPP data federalization (see [3] and [4]), or known NGN application, e.g. UPSF, or other legacy solution. • IPTV User Data FE (IUDF): IPTV user data function. IPTV user data function is responsible for handling dedicated IPTV user data. IUDF allows integration of user data from IPTV subsystem into NGN either using 3GPP data federalization (see [3] and [4]), or known NGN application, e.g. UPSF, or other legacy solution. To access user data the following functional entity is used: • NGN User Data Access FE (NGN UDAF): The NGN UDAF knows the location and gives access to user data. An instance of it can be either GUP server if data federalization approach is selected, known NGN application, or other legacy solutions. In the consolidated approach user data is located and accessed via NGN UDAF, which is: • User Profile Server FE (UPSF): The User Profile Server Function (UPSF), as defined in ES 282 001 [5], is responsible for hosting a set of user related information, amongst service-level user identification, numbering and addressing information, service-level user security information: access control information for authentication and authorization, service-level user location information at inter-system level, service-level user profile information. Customer Facing IPTV Application FE (CFIA): provides IPTV service provisioning, selection and authorization: • Provide IPTV services offer. • Enable navigation and selection. • Verify access right according to the IPTV user profile, e.g. stored in the UPSF. • Provides authentication and authorization to validate the user's right based on the user profile. • Authorizes the UE to access the IPTV Service Control and Delivery Functions. • Provides to the UE initial entry point to the selected service. • May provide to the UE information on selected IPTV service (e.g. duration, range, etc.). • May access to the NASS in order to request the geographical user localization. For example, to deliver SD&S metadata according to the localization of the user, support user nomadism. • May provide application usage control like CoD credit, CoD already purchase with last play range. Service Discovery and Selection (SD&S): provides description information for discovery of the service list for Live TV and selection of these services or on-demand IPTV services. Particular implementation is outside the scope of the present document, e.g. defined in [2] can be used. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 17 IPTV Control FE (IPTV-C): • Checks if UE has been authorized by the Customer Facing IPTV Application to use IPTV Service Control and Delivery Functions. • Provides selection of the Media Control Function during the IPTV service selection ( optional in case of one to one relationship between IPTV Control entity and Media Control Function entity): - Based on location of the Media Control Function (MCF) entity. - Based on load of the Media Control Function (MCF) entity. - Based on distribution of contents among media delivery entity. - Optionally based on resource admission control between UE and media delivery entity. • May retrieve in NASS the geographical user localization, to select the Media Control Function entity. Media Control Function (MCF): • Handling media flow control of MDF (not applicable for multicast e.g. Linear TV). • Monitoring the status of MDF. • Managing interaction with the UE (e.g. trick mode commands). • Handling interaction with the IPTV control function. • Keeping an accurate view on status and content distribution related to the different MDFs that it controls. • Selecting an MDF, in the case an MCF controls multiple MDFs different criteria, may be applicable as for example as follows: - Load balancing of media delivery entities (MDF). - Based on distribution of contents among media delivery entities. - Optionally location of the UE (may need to access NASS in order to request the geographical user localization, e.g. to select the Media Delivery entity according to the localization of the user and to select nearest MDF). - Optionally based on resource admission control between UE and media delivery entity or availability of content/resources in MDF itself. • May check user authorization to use requested IPTV service. • May generate charging information, e.g. for end-user charging based on the viewed content. • May manage the media processing of MDF. • Controlling advertisement insertion of MDF, e.g. instructing MDF to play the advert, handling synchronization between the advert and IPTV content and synchronization with delay or drift in broadcast TV schedules. • Providing a direct relationship on the media delivery and media control levels between downstreaming and upstreaming UGC sessions for live UGC consumption. In IPTV integrated subsystem MCF acts as UE point of contact for requested delivery of the selected IPTV service. Media Delivery Function (MDF): • Handling media flow delivery (delivering multimedia services to the user). • Status reporting to MCF (e.g. reporting on established IPTV media session). • Storing of media (e.g. CoD assets), may store some service information with media for IPTV services. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 18 • In particular, may be used for storing the most frequently accessed content or user specific content (e.g. recording PVR, Time Shifted TV, Pause TV, user generated content) if the same tasks are not performed by UE. • May additionally process, encode or transcode (if required) media to different required media formats (e.g. TV resolution depending on terminals capabilities or user preferences). • May perform content protection functionalities (e.g. content encryption). • May support content ingestion of IPTV media. • May receive media content from UE, e.g. via upstreaming/upload. • Handling content download to UE (download CoD content to UE or record BC live stream and subsequently download to UE). • Performing advert insertion during IPTV content playback, i.e. deliver advert content to the UE during the advert insertion opportunity. • May support alternative streams for use with an existing broadcast channel or CoD item, e.g. alternative video, audio or subtitle tracks for personalized stream composition. For BC services MDF may act as source for multicast streams of BC media streams.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.1.2 Supporting IPTV functions
|
Media Preparation FE: a group of functions for manipulating, "preparing", content to enable content delivery to the UE. Examples of content preparation are encryption, encoding, keys and access rights generation. Such processes may be executed off-line, being considered as belonging to media content management, or on-line, in real-time, then being part of the IPTV applications or service delivery and control, e.g. DRM processing may be delegated. Service & Content Protection (SCP) functions: e.g. Digital Rights Management (DRM) Function and/or Conditional Access (CA), implements encryption and/or conditional access for instances of multimedia service delivery. Content security elementary functions are defined in clause 7. NOTE 1: NGN dedicated IPTV Release 2 refers to SCP as Digital Rights Management (DRM) function. NOTE 2: SCP may contain more detailed service and content protection elementary functions and used during UE service initiation or service attachment (more detail are in TR 187 013 [i.4]). Media Acquisition Function: belongs to the media preparation functions. Implements media acquisition functionality acquiring the media content from the content providers, may acquire license rights from the content providers to enable media distribution to delivery functions. Media acquisition function can be co-located with media delivery function, e.g. for acquisition of live media streams. Media Distribution FE: implements media distribution functionality, e.g. physical distribution of multimedia assets from centralized location to distributed delivery grid via protocols or life access to broadcast channels. NOTE 3: There are relationships and interfaces between Media preparation FE, Media distribution FE, MCF/MDF functional elements and content management may be used to purpose manage content ingest as described in management clause 8. Charging and Accounting Functions: manage customer charging and service subscriptions. IPTV Subscriber Management FE: manages IPTV subscriber database.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.1.3 Transport functions
|
RACS: TISPAN resource admission and control subsystem. NASS: TISPAN network attachment subsystem. Transport Processing Functions: as defined in clause 4.3. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 19
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.1.4 Customer Transport functions
|
Delivery Network Gateway (DNG): device that is connected to one or multiple access networks and one or multiple home network segments. User equipment function: provides user interactions and control over delivery of IPTV and other NGN services. May include the following elementary functions: • Broadcast-Client Function. • On-Demand Client Function - provide interfaces with on demand headend components and enable end user application. • Audio/Video Decoder Function. • Audio/Video Decryption Function. • Optional support for sub-title function.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2 Reference points
|
This clause describes reference points for NGN integrated IPTV architecture as shown on figure 2. Reference points between the core IPTV functional entities are summarized in table 1. Table 1: Reference points between core IPTV functional entities FE/ Reference point UE IPTV-C CFIA SD&S UPSF IUDF MCF MDF UE --- Ct2 Tr Tr --- --- Xc Xd IPTV-C Ct2 --- Ss --- Sh Ud Sa --- CFIA Tr Ss Sh Ss' --- --- --- --- SD&S Tr --- Ss' --- --- --- --- --- UPSF --- Sh Sh --- --- --- --- --- IUDF --- Ud --- --- --- --- Ud --- MCF Xc Sa --- --- --- Ud --- Xp MDF Xd --- --- --- --- --- Xp --- NOTE: As discussed in clause 5, IPTV functional architecture includes reference points, which are shown for completeness, but are outside the scope for the current release. The considerations for deferring assigning reference points to such interfaces are: functional interactions on the reference points is not used in the current procedures; reference points are optional; reference points are left for further study.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.1 Tr - IPTV transactional
|
Reference point between UE and Application Functions: • Used for UE Authentication and Authorization during initialization. NOTE: UE authentication may also be done directly via e2 reference point. • Used for user Authentication and Authorization for IPTV service during initialization. • Used to provide UE with one or more service offers. • Used to enable navigation and service selection. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 20 • May instantiate IPTV/converged service offers. • Can give access to personalized offers from multiple service domains based upon user profile. • Provides to the UE an initial entry point into the IPTV service level subsystem. • Provides to the UE information on selected IPTV service.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.2 Ct2 - UE facing IPTV control
|
Optional reference point between UE and IPTV Control: • Acts as initial UE point of contact to request delivery of the selected IPTV service. • Returns nominated service (media) delivery control function. • Provides enough information for IPTV Control to check that UE has been authorized (by the Customer Facing IPTV Application) to access the requested resources. NOTE: "Optional reference point" refers to a reference point only required in some of the operational modes: proxy, redirect, coupled or decoupled as defined in clause 6.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.3 Sa - IPTV control and Media Control Function
|
Reference point between IPTV control and Media Control Function: • Used to interact with the Media Control Function (MCF) entity of the IPTV service selected by a user (e.g. provides information to the MCF that the user is authorized to access the selected IPTV service). • Used to notify the IPTV control with information related to the service selected (e.g. the IPTV service cannot deliver the service because of network reasons such as insufficient bandwidth or no media delivery available). NOTE: This interface is not used to make the media delivery (MDF) selection; this is the role of the MCF.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.4 Ss - Service selection
|
Optional Ss - Service selection reference point between Customer facing IPTV applications and IPTV control: • Used to notify the IPTV control entity of the IPTV service selected by the user. • Used to notify the Customer Facing IPTV Application the UE initial entry point to the selected service (Media Control Function). • Used to notify to the Customer facing IPTV Application with information related to the service selected (e.g. the IPTV service cannot be delivered because of network reasons - information from the Sa reference point).
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.5 Xc - UE and IPTV Media Control Function
|
Xc reference point (media control) - logical end-to-end reference point between the UE and the IPTV Media Control Function (MCF): • used to exchange media control messages for controlling of the delivery IPTV Media flows. NOTE: Transport related reference points are used to carry media control messages over underlying transport segment (defined in ES 282 001 [5] and as shown below in figure 3). Depending on the location of the MCF, Xc is decomposed into: the Dj reference point between the UE and the access network, optionally the Di reference point between the access network and the core network, and optionally the Ds or Iz reference point between the core network and the Media Control Function, if the MCF is located behind the Core Network. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 21 Access Network Di Ds or Iz Dj Xc UE MCF Core Network Transport Processing Figure 3: Decomposition of the Xc reference point when the MCF is after the Core Network 5.2.6 Xp - IPTV Media Control Function and IPTV Media Delivery Function • Reference point between Media Control Function (MCF) and Media Delivery Function (MDF): used to control media delivery sessions in order to support setup of a media delivery session. The media content can be distributed among one and more media delivery functions. NOTE: If authorization of the user access to the selected IPTV service is still valid, may be used for transmission of adaptations to session control and/or media control to the previously selected/established media delivery session.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.7 Xd - UE and IPTV Media Delivery Function
|
Xd reference point (media delivery) - logical end-to-end reference point between UE and IPTV Media Delivery Function (MDF): • carries IPTV media data by appropriate means to the UE (delivers content streams). NOTE: Transport related reference points are used to carry media delivery data over underlying transport segment (defined in ES 282 001 [5] and as shown in figure 4). Depending on the location of the MDF, Xc can be decomposed into: the Dj reference point between the UE and the access network, optionally the Di reference point between the access network and the core network, and optionally the Ds or Iz reference point between the core network and the Media Delivery Function if the MDF is located after the Core Network. Access Network Di Ds or Iz Dj Xd UE MDF Core Network Transport Processing Figure 4: Decomposition of the Xd reference point
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.8 e2 - NASS access
|
The e2 reference point is defined in ES 282 007 [8] and ES 282 004 [9].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.9 e4 - NASS and RACS
|
The e4 reference point is defined in ES 282 003 [10] and ES 282 004 [9]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 22
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.10 Gq' - RACS
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.11 Ud - access to IPTV user data
|
In the federated approach: • Used by IPTV application server functions, IPTV subscriber management to access subset of IPTV profiles, which are hosted in IUDF. In the consolidated approach: • User Data implements UPSF functionality. • Used to access user data located in User Data function. The Reference point is between IPTV applications layer ions and UPSF [5]: As an application server function may choose to use the repository function of the UPSF for hosting service-level user data, as transparent data, the interface should comply with Sh reference point used between this AS Function and UPSF. • The use of Sh reference point conforms to ES 282 007 [8]. • The IPTV applications represented on Figure 2, that may use the UPSF repository function are: Customer Facing IPTV Applications, IPTV control, IPTV subscriber management.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.12 Ug - access to NGN user data
|
In the federated approach: • Used by IPTV applications to provision and access federalized data from service level subsystems, e.g. IMS, NGN App UDF, mobile, other profile and non-NGN user data. • Used by converged applications (e.g. communicational features on TV, mobile session handover) to provision and access federalized data from service level subsystems (e.g. IMS, IPTV UDF, mobile, other profile data and non-NGN user data. • Provides common access among application to profile data models and data components that are common across applications. In the consolidated approach: • User Data implements UPSF functionality. • Used to access user data located in User Data function. The Reference point is to access common user data in NGN via UPSF [5]: As an application server function may choose to use the repository function of the UPSF for hosting service-level user data, as transparent data, the interface should comply with Sh reference point used between this AS Function and UPSF. • The use of Sh reference point conforms to ES 282 007 [8]. • The IPTV applications represented on figure 2, that may use the UPSF repository function are: Customer Facing IPTV Applications, IPTV control, IPTV subscriber management.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.2.13 Ss' - access to SD&S data
|
Optional Ss' reference point between Customer facing IPTV applications and SD&S used to retrieve service and optionally service provider information from the SD&S server, e.g. EPG, content metadata, service information updates, service provider details. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 23
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3 Generic IPTV Capabilities
|
This clause describes generic IPTV capabilities - capabilities provided by IPTV functional entities and exposed via interfaces on the high level architecture. The capabilities are used to deliver a variety of IPTV services as defined in the detailed procedures. IPTV Generic IPTV Capabilities: • service discovery and selection; • service control; • service interaction; • media control; • media delivery; • content protection; • content management and distribution; • interactions with other NGN services.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1 Inter-destination media synchronization
|
Inter-destination media synchronization is an optional generic capability, aimed at servicing corresponding service level requirement as defined in clause A.9.6 of [1]. 5.3.1.1 Synchronization architecture The Media Synchronization Application Server (MSAS) and Synchronization Client (SC) are functions that provide inter-destination media synchronization. These functions are used for synchronization sensitive services for which IPTV delays and delay differences may degrade the quality of experience. The functional entities and reference point of the synchronization mechanism are shown in figure 4A. Media Synchronization Application Server (MSAS) Sync Synchronization Client (SC) Figure 4A: Functional entities and reference points for inter-destination media synchronization
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.1.1 Functional entities MSAS and SC
|
The inter-destination media synchronization (IDMS) mechanism uses the concept of synchronization sessions. Each synchronization session involves a Media Synchronization Application Server (MSAS) and multiple Synchronization Clients (SC). A synchronization session is used for the inter-destination synchronization of IPTV content (e.g. BC channel, CoD, UGC) by exchanging synchronization status information (i.e. arrival time information) and delay information in the form of synchronization settings instructions. • Synchronization status information: timing information on media reception at each SC. • Synchronization settings instruction: instruction how much an SC should delay the media stream. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 24 Tasks of the SC: • 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. • Delaying (buffering) a media stream BC channel according to the received synchronization settings instruction. Tasks of the MSAS: • Session-oriented tasks: - Setting up and accepting synchronization sessions with/from SCs. • Media-oriented tasks: - Collecting synchronization status information from SCs. - Calculating delay information and the derived synchronization settings instructions for the SCs. - Distributing synchronization settings instructions to SCs. The MSAS function may be decomposed in session-oriented functions and media-oriented functions. NOTE: Examples of algorithms to calculate the synchronization settings instructions from collected synchronization status information may be found in [i.1].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.1.2 Mapping onto the IPTV architecture
|
The synchronization architecture can be mapped onto the IPTV architecture in the following ways. Mapping 1: SC in UE • The session-oriented part of the MSAS is an elementary function of the IPTV Control. For synchronisation using a direct communication channel between multiple UEs, the MSAS is co-located with the SC. • The SC is an elementary function of the UE. Mapping 2: SC in Transport • The MSAS is an elementary function of the IPTV Control or a stand-alone Application Server. • The SC is an elementary function of the Transport Functions. NOTE 1: Mapping 1 is aimed at small-scale deployments of services that require media synchronization and only a limited number of UEs uses media synchronization. Mapping 2 is aimed at large-scale deployment of media synchronization. NOTE 2: In mapping 2, the SC is an adjunct function that may be co-resident with any of the appropriate elements in the transport layer.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.1.3 Modification and re-origination of media streams
|
In addition to inter-destination media synchronization, additional synchronization measures are needed in case a media stream is modified or re-originated during transport. Examples of these are transcoding, HD-to-SD conversion and user-generated comments to a live broadcast. In such cases, additional media-stream-modifying Synchronization Clients (SC') are placed at the functional entities where media streams are modified, see figure 4B. The Sync' reference point is used to exchange convey synchronization status correlation information between from the media-stream-modifying SC' and to the MSAS on the synchronicity relationship between incoming and outgoing media streams. • Synchronization correlation information: timing information on the synchronicity relationship between incoming and outgoing media streams at an SC'. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 25 Figure 4B: Media synchronization in case of media stream modification
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.2 Synchronization reference points
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.2.1 MSAS-SC reference point (Sync)
|
This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream- synchronizing Synchronization Client (SC). It is used to set up synchronization sessions and to exchange synchronization status information and synchronization settings instructions with functional entities in the network where media streams are mutually synchronized. The Sync reference point is decomposed as follows: • Synchronization session initiation • Synchronization status information and settings instruction exchange The session-oriented part of the Sync reference point is a logical reference point in Mapping 1 from clause 5.3.2, where the synchronization session initiation signalling is tunnelled over the Ct2 reference point. The media-oriented part of the Sync reference point uses the Xd reference points. If the SC is co-located with the MSAS, then the exchange of synchronization status information and synchronization settings instructions is internal to the functional entity in which they reside. Specification of this internal Sync reference point is out of scope. NOTE: An example of co-located SC+MSAS functionality is when UEs exchange synchronization status information and synchronization settings instructions via a direct communication channel.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.3.1.2.2 MSAS-SC' reference point (Sync')
|
This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream-modifying Synchronization Client (SC'). It is used to set up synchronization sessions and to exchange synchronization status information with functional entities in the network where to-be-synchronized media streams are modified. SC MSAS Media stream origination (e.g. MF or EFF) Media stream modification (e.g. transcoder at MF or re-origination at UE) SC' Media stream destination (e.g. UE or TFP) SC Sync Sync' Media stream M Media stream M’ ETSI ETSI TS 182 028 V3.5.1 (2011-02) 26
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
5.4 Elementary functions
|
This clause describes generic IPTV capabilities - capabilities provided by IPTV functional entities and exposed via interfaces on the high level architecture. The capabilities are used to deliver a variety of IPTV services as defined in the detailed procedures. General elementary functions: 1) Network attachment 2) Registration 3) Resource Management 4) Charging information IPTV elementary functions: Service related elementary functions: 5) Service discovery 6) Service authorization 7) Service selection 8) Service initiation 9) Service control 10) Service information handling (e.g. Metadata) 11) Service configuration Session related elementary functions: 12) Session initiation 13) Session modification 14) Session termination Service protection related elementary functions: 15) Service key triggering function Multimedia delivery & control elementary functions 16) Multicast based media delivery (media streaming) 17) Unicast based media delivery (media streaming, both down- and/or upstream) 18) Content download/upload (offline content transfer) 19) Control of multicast based media streaming 20) Control of unicast based media streaming (both down- and/or upstream) 21) Control of content transfer by download/upload 22) Content ingestion (receiving content) 23) Content recording(capture of live content) 24) Content storage 25) Content adaptation (e.g. Transcoding, mix, substitute, personalize) ETSI ETSI TS 182 028 V3.5.1 (2011-02) 27 Content management related elementary functions: 26) Content acquisition 27) Content validation 28) Content distribution Content protection related elementary functions: 29) Content licensing 30) Content key management 31) Content encryption User management elementary functions: 32) User profile/data management 33) Accounting/right control IPTV Common elementary functions: 34) Status/state (changes) detection/reporting 35) Common notification 36) Messaging 37) Presence Reporting 38) Inter-destination Media synchronization
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6 Operational framework
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.1 IPTV delivery modes
|
Integrated IPTV subsystem supports IPTV or NGN service using IP delivery modes: • Unicast: delivery mode where information packets are sent to a single destination. • Multicast: delivery mode of forwarding information packets to a group of destinations. • Combinations and interchanging of both inside a given service. In order to implement service level requirements defined in [1], integrated IPTV subsystem can use IP unicast delivery mode, for example, for Content on Demand service, or IP multicast delivery mode, for example, for broadcast TV service. More complex service scenarios are possible, where IP delivery modes are interchanged inside a single service, for example, to implement broadcast TV with trick modes. Unicast and multicast capabilities are expected from the transport layer. However, if only a subset of delivery capabilities is available, the functional architecture would implement functional capabilities build upon the available subset. For example, if transport layer has unicast capabilities only, the functional architecture implements CoD, nPVR and other services build upon unicast delivery.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.2 Operational modes
|
This clause describes interactions between the UE, the Application functions and the "IPTV Service Control and Media Delivery functions". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 28 There are two aspects of these interactions: • Interactions between the Application functions and the "IPTV Service Control and Media Delivery functions". • Interactions between the UE and the "IPTV Service Control and Media Delivery functions". Concerning the first aspect, there are two possible modes of operations: coupled and decoupled. Coupled: following a request from the UE, the application communicates with the "IPTV Service Control and Media Delivery functions" to allocate and reserve a media delivery function before the content selection is confirmed to the UE. The URL to contact the "IPTV Service Control and Media Delivery functions" is returned to the UE. Decoupled: following a request from the UE, the application returns the URL to contact the "IPTV Service Control and Media Delivery functions" assuming that the "IPTV Service Control and Media Delivery functions" will be able to allocate a media delivery function and associated resources when needed. Concerning the second aspect, there are two possible modes of operation: proxy and redirect. In the redirect mode: a functional entity receives an input request, performs its actions and redirects UE to the next functional entity in sequence. In the proxy mode: a functional entity receives an input request, performs its actions and proxies the request to the next functional entity in sequence. The flows for proxy and redirect modes are defined for one of the functional entities from "IPTV service control and media control functions. IPTV control is defined in redirect mode and MCF is defined in proxy mode. If one of the functional entities work in either of modes it neither mandates no precludes other functional entities to work in the same or alternative modes.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.2.1 Coupled mode
|
Operational flow in the coupled mode is presented on figure 5. UE Customer Facing IPTV Application (AS) IPTV Service Control and Media Delivery functions UPSF/ IUDF RACS NASS 1. Service Initialisation 2. Profile Access 3. Media Delivery Control Allocation 5. Resource Reservation and Admission Control 6. Resource Reservation and Admission Control 7. MDC allocate 8. URL for Media Delivery and MDC to contact 10. Media Delivery Control 9. Media Delivery Request 4. User Location (NASS optional) Figure 5: Operation flow in the coupled mode Main functional steps in the coupled mode: 1) Service Initialization: UE selects and requests service from the application. 2) Profile Access: The application optionally access profile information withers from application data of via data access functions. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 29 3) Media Control Function Allocation: The application request a Media Control Function the UE can contact to requested media. 4) User location: user location can be requested from NASS or from IPTV UDF in order to select the appropriate Media Delivery Function (and Media Control Function). 5) Resources Reservation and Admission Control: IPTV service control and media delivery functions select a MCF and a Media Delivery Function and requests reservation of transport delivery resource (from UE to Media Delivery Function selected). 6) Resources Reservation and Admission Control: transport resources reserved and committed. 7) Media Control Function Allocation: Allocation of the user contact point in order to request media delivery and for interactive Media Control Function. 8) URL for Media Delivery to content Media Control Function functional entity. 9) Media Delivery Request: UE requests interactive media delivery. 10) Media delivery Function: UE controls interactive media delivery.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.2.2 Decoupled mode
|
Operational flow in the decoupled mode is presented on figure 6. UE Customer Facing IPTV Application (AS) IPTV Service Control and Media Delivery functions UPSF/ IUDF RACS NASS 1. Service Initialisation 2. Profile Access 6. Resource Reservation and Admission Control 7. Resource Reservation and Admission Control 8. Media Delivery Allocation 3. URL for Media Delivery 10. Media Delivery Control 4. Media Delivery Request 9. Media Delivery Request 5. User Location (NASS optional) Figure 6: Operation flow in the decoupled mode Main functional steps in the decoupled mode: 1) Service Initialization: UE selects and requests service from the application. 2) Profile Access: The application optionally access profile information withers from application data of via data access functions. 3) URL for Media Delivery. 4) Media Control Function Allocation: Media Delivery Request. UE requests interactive media delivery. 5) User location: user location can be requested from NASS or from IPTV UDF to select the appropriate Media Delivery Function (and Media Control Function). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 30 6) Resources Reservation and Admission Control: IPTV service control functions selects and media delivery functions selects a MCF and a Media delivery entities and requests reservation of transport delivery resources (from UE to Media Delivery Function selected). 7) Resources Reservation and Admission Control: transport resources reserved and committed. 8) Media Control Function Allocation: Allocation of the user contact point in order to request media delivery and for interactive Media Control Function. 9) Media Delivery Request: UE requests interactive media delivery. The UE knows it has to send a second request because request at step 4 has resulted in redirect response as defined in clause 6.2.3. 10) Media Delivery Control: UE controls interactive media delivery.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.2.3 Redirect mode
|
Operational flow of the IPTV control functional entity in the redirect mode is presented on figure 7. The flow represents operational. UE IPTV Service Control and Media Delivery functions UPSF/ IUDF RACS NASS 4. Resource Reservation and Admission Control 5. Resource Reservation and Admission Control 6. REDIRECT TO MDC 1. Media Delivery Request 7. Media Delivery Request 3. User Location (NASS optional) IPTV control MCF MDF 2. Authorisation Verification Figure 7: Operation flow in the redirect mode Main functional steps in the decoupled mode: 1) Media Delivery Request: UE requests interactive media delivery. 2) Authorization Verification: IPTV control optionally verifies user rights to access the service. 3) User Location: user location can be requested from NASS or from IPTV UDF. 4) Resources Reservation and Admission Control: IPTV control selects media delivery function and optionally requests reservation of transport delivery resources. Note: resource reservation can be alternatively performed by the selected MCF. 5) Resources Reservation and Admission Control: transport resources reserved and committed. 6) Redirect to MCF: UE is redirected to MCF for the selected MDF function for interactive media delivery. 7) Media Delivery Request: UE requests interactive media delivery.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.2.4 Proxy mode
|
Operational flow of the MCF control functional entity in the proxy mode is presented on figure 8. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 31 UE IPTV Service Control and Media Delivery functions UPSF/ IUDF RACS NASS 3. Resource Reservation and Admission Control 4. Resource Reservation and Admission Control 6. Media Delivery 1. Media Delivery Request 5. Media Delivery Request IPTV control MDC MD 2. Authorisation Verification Figure 8: Operation flow in the proxy mode 1) Media Delivery Request: UE requests interactive media delivery. 2) Authorization Verification: MCF optionally verifies user rights to access the service. May access to IPTV UDF for this purpose. 3) Resources Reservation and Admission Control: MCF selects media delivery function and optionally requests reservation of transport delivery resources. NOTE: Resource reservation can be alternatively performed by the IPTV control. 4) Resources Reservation and Admission Control: transport resources reserved and committed. 5) Media Delivery Request: Media Control Function command is passed to media delivery. 6) Media Delivery: media is delivered to the UE.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.3 Service initialization
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.3.1 Functional steps for UE start-up
|
Figure 9 presents functional steps of the UE start-up for IPTV subsystem in NGN. UE NASS SD&S 3. IPTV Security Bootstrapping IPTV AS 1. Network Attachment 2. Service discovery 4. Attach to the IPTV Service 5. IPTV Service Configuration SCP Figure 9: UE start-up procedure ETSI ETSI TS 182 028 V3.5.1 (2011-02) 32 1) Network Attachment. In this step, the UE attaches to the network. The UE may be passed data for Service Provider Discovery (SPD) as defined in clause 5.2.1. 2) Service discovery. In this step, the UE discovers service providers and services as discussed in clause 5.2.1. 3) IPTV security bootstrapping. In this step, the UE performs authentication, key management (CSP may be also involved in initial steps of service and content protection). During this procedure IPTV subsystem may register IPTV UE in other service level subsystems on behalf of UE. 4) Attach to the IPTV Service. 5) IPTV Service Configuration. In steps 4 and 5, the UE navigates and selects a service from available service offers. IPTV AS may update IPTV user profile, presence of behalf of IPTV as a part of the SD&S process. The service navigation and selection can be provided in a generic case via different functional entity as presented on figure 10. NOTE: The high level service attachment steps can looks similar for integrated IPTV subsystem and IMS based IPTV approaches, the exact alignment in procedures is out of the scope of the present document.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.3.2 Service discovery and selection
|
This clause defines steps in the service discovery and selection process used by the UE to attach to the network, acquire list of service providers and make service selection from the selected service provider. There is a step preceding SD&S process including setup and initial UE configuration. Figure 10 presents steps in the SD&S process. Step 1. Network Attachment Step 2. Service Provider Discovery Step 3. Service Discovery and Attachment Figure 10: High Level SD&S Process Network Attachment: during this step UE establishes connectivity to an IP-network and obtains network-based service configuration data. For example, the following information may be obtained or established by UE: IP address, network mask, DNS, domain name, others. During this step UE may be passed data for SPD, e.g. a container option sent by DHCP server listing the source IP address of the Service Provider server or list of registered IPTV service provider servers using DNS SRV mechanism in accordance with RFC 2782 [7]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 33 Service Provider Discovery (SPD): during this step UE collects the location (entry points) for discovering service providers and retrieves information about available IPTV Service Providers, learns the location of their one or more Service Discovery (SD) Server. Service Discovery and Attachment: during this step UE acquires information about available IPTV Services from one or more Service Discovery (SD) Servers, navigate, select service from the service offering and attach to the service. The procedure used to activate a particular IPTV service is typically service specific. Authentication is performed at this step. Further decomposition for Service Provider Discovery (SPD) is presented on figure 11. Service Provider Selection Entry Point Discovery Figure 11: Service Provider Discovery (SPD) Steps Entry points discovery: during the step UE determines the entry point(s) for discovering service providers (e.g. bootstrap process). Service provider selection: during this stage UE retries information about available IPTV Service Providers, learns the location of their one or more Service Discovery (SD) Servers and makes a selection of the Service Provider. Different mechanisms are available for Step 2 and Step 3, e.g. those defined in DVB-IP [2] can be used. Regionalized or personalized delivery of the content metadata can be performed by the Customer Facing IPTV applications by accessing user profiles (as described in the clause 8) and accessing user location (as described in clause 5).
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.4 Nomadism
|
In TISPAN Release 2, nomadism can be provided by relying on the functionality provided by the transport control layer (i.e. RACS and NASS). In this scenario, all functions in the integrated IPTV subsystem are located in the user's home domain and therefore, a UE in a visited access network or access point needs to be provided with: • IP connectivity to the user's home service control domain. • A pointer to the Customer Facing IPTV Application in the user's home service control domain (as part of the Service Discovery and Attachment procedures described in clause 6.3.2).
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
6.5 Support of Mobility Capabilities
|
Annex G discusses interconnection models for IPTV UE mobility. NOTE: If the UE supports roaming in the visited network to support mobility of IPTV services. Annex G considers how the UE in the visited network can access IPTV services from the home network. IPTV Service Provider in the home network may select to use MF in the home network to deliver content to UE in both home and visited networks. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 34
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
7 Security
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
7.1 Content Protection
|
For content protection the following elementary functions are used: • Content licensing: This elementary function handles the licenses issuing related functions, including generation and distribution of the licenses to the desired entities. • Key management: This elementary function handles the management of the security keys on behalf of the content usage profiles as defined in the content licensing, including generate and provide the keys and corresponding parameters to the desired entities. • Content encryption: This elementary function handles the content protection related operations, e.g. content encryption and encapsulation operations, etc. These three elementary functions may be flexibly located in existing functional entities or new ones as a whole or in independent parts. NOTE 1: The locations and related reference points of those three elementary functions are defined in TS 187 003 [11]. NOTE 2: Some of these elementary functions may be executed on-line (in real-time) or off-line (in this case could be part of the management). NOTE 3: Additional details and procedures for IPTV service and content protection of these three elementary functions and other IPTV security functions are described in TR 187 013 [14].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
7.2 Service Protection
|
The Service Membership (SMF), Service Key Management (SKMF) and Service Protection (SPF) Functions described in this clause each involve a set of elementary functions required as part of a generic model for service protection. The SMF, SKMF, and SPF do not duplicate, but collaborate and interact with existing elementary functions in order to perform service protection. For service security the following functions are used: • Service Membership elementary Functions (SMF): This set of elementary functions handles the granting and revoking of service access rights to access the IPTV services. Metadata related to the service rights management are maintained by the SMF. NOTE 1: The SMF is handled in an array of existing elementary functions (e.g., service key triggering function) and functional entities. For example, service authorization may be provided by the CFIA or IPTV-C, and meta-data is maintained in the UPSF. • Service Key Management Function (SKMF): This set of elementary functions acts on behalf of the Service Membership Function and as such manages service security keys, including generating and providing keys and corresponding parameters to the desired entities. • Service Protection Function (SPF): This (set of elementary) function(s) handles the service protection related options, e.g. service confidentiality, integrity operations and authorization at the service access point, etc, using the keys generated in SKMF. NOTE 2: The SPF includes group association, e.g. multicast group. NOTE 3: The locations and related reference points of those three elementary functions are defined in TS 187 003 [11]. NOTE 4: Additional details and procedures for IPTV content protection are described in TR 187 013 [i.4]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 35
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
8 Management
|
A number of functional entities used to deliver IPTV and NGN services require time synchronization, e.g. to provide time of day reference. Transport layer should support such reference. Content management functionalities are responsible for managing acquisition of content and service information (e.g. metadata) from sources, controlling validation and/or processing/adaptation to the required format and also to provide management functionalities for supporting distribution of content to the media delivery function. NOTE: Content management is used in the case of offline or online ingest of the content. The online ingest means receiving content directly streamed from the content provider. The offline ingest refers to content files delivered by other means than the online (e.g. such on physical media like DVD, CD, etc.). The content management is used by the IPTV service provider to statically provision the content.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
9 User data
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
9.1 IPTV profiles
|
IPTV related data can be grouped into three types of IPTV profiles (see figure 12): • Content Profile. • Service Profile. • User Profile. IPTV profiles Content Profile Service Profile User Profile Figure 12: NGN IPTV profiles Content Profile: Content profile contains and maintains information about multimedia metadata and multimedia service packaging used for the provisioning of IPTV services. Service Profile User information Offer Information Figure 13: NGN IPTV Service Profile ETSI ETSI TS 182 028 V3.5.1 (2011-02) 36 Service Profile: Service profile refers to data used to the provisioning of the service to the user. It contains and maintains information about service-level user data and service-level offer data (see figure 13): • Service-level user data: as defined in NGN Functional Architecture [5], e.g. user identification, numbering, addressing, user security, location information at inter-system level, other. • Service-level offer data: contains the information for delivery of IPTV services, e.g. EPG/BPG. User profile: User profile refers to user customization and usage metadata. It contains and maintains basic user information, service specific information, e.g. subscription, bookmarks, activities, parental control, etc. and User actions related to service purchase and consumption. • User subscription data - contains information such as language preference, payment preferences, navigation preferences, etc. Service actions data - contains and maintains non static data related to the purchase and consumption of services such as list of CoD already consumed, indexes for currently consumed programs, language selection.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
9.2 User data location
|
NGN Integrated IPTV supports two approached to user data location: federated and consolidated. In the federated approach user data is located close to associated AS functions in IPTV UDF, NGN Apps UDFs. User data associated with applications can be access by the AS functions directly on Ud interfaces. If AS function requires access to subset of user data associated with other AS functions, Ug interface should be used. User Data functional acts as data federation agent providing unified approach and federation of user data profiles. Federated approach is applicable to other data profiles defined in clause 9.1: • content profiles; • service profiles. In the consolidated approach user data is located in a single location: User Data Function and can is accessed on Sh interface. Ud and Ug interfaces, in essence, become the same Sh interface. As discussed above, both IUDF and UPSF may be used for handling the IPTV user data. IPTV profile information (Content, service, user, as defined in clause 8.1) could be optionally located in the IPTV Application server functions (i.e. IUDF) hosting the IPTV applications, or in the UPSF as transparent data associated to the Application Server functions, or in an XDMS associated with the IPTV Application Function. The type of user related information necessary for multi-subsystems service blending belongs to the following list: service-level user identification, numbering and addressing information, service-level user security information: access control information for authentication and authorization, service-level user location information at inter-system level, service-level user profile information. To provide support for converged applications that span across several subsystems of the TISPAN NGN network (e.g. chatting on watched programs, multiple incoming calls management, as listed in TS 181 016 [1]) both federated and consolidated approaches are applicable, and in accordance the location of the user data profile: • Use UPSF as the host for the set of user related information necessary for multi-subsystems service blending. • Use of data federalization (represented by UDAF on figure 2). It is recommended that an NGN (e.g. converged) application, or its corresponding user data functions do not have direct access to IPTV profiles in IUDF (reverse applies respectively). It may however have access to it by other means (e.g. Ug reference point to UDAF, Sh to UPSF for the subpart of IPTV profile that is hosted onto UPSF. If UPSF is used, several entities will need to be consistently provisioned for: • user identification (in UPSF and IUDF); • user authentication (in UPSF and IUDF). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 37 NOTE: Such need for consistent provisioning is to be brought to the attention of WG8.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
10 Charging
|
As illustrated in figure 2, the charging belongs to the management domain. IPTV subsystem collects information related to billing and provides IPTV CDRs (including charging related elements), that can be collected by the billing system for the sake of off-line charging. These CDRs may also be used for other purposes than billing (such as QoS, statistics). NOTE: CDR means Charging Data Record, as defined in TS 132 240 [13] (endorsed by ES 282 010 [12]). It is a formatted collection of information about chargeable event, knowing that, as a minimum, a chargeable event characterizes the resource/ service usage and indicates the identity of the involved end User (s). IPTV subsystem integrates with the charging and accounting components of the management domain for having access to the user account (credit, balance, etc.) in order to allow IPTV user facing applications and optionally media delivery control to perform their role with.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11 Procedures
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.1 Linear TV
|
This clause provides the flows for the BTV IPTV services integrated into the TISPAN NGN architecture and inter-working with the NGN common functions and components. The flows support linear TV in coupled and decoupled mode. Linear TV in coupled and decoupled mode uses RACS in the "push mode". The clause presents generic flows and does not mandate placement of functions. DRM flows are not included. Linear TV procedure for coupled and decoupled mode. 1. Acquisition of SD&S information UE TPF RACS MDF UPSF/ IUDF SD&S and CF IPTV apps 2. 3. 4. Linear TV channels 5. Join channel A 6. 7. Channel A 8. Leave channel A 10. Join channel B 11 12. Channel B 9. Figure 14: NGN IPTV Linear TV procedure for coupled and de-coupled mode 1) UE requests SD&S information from SD&S. SD&S format and request methods are outside the scope of the present document and have been researched in other specifications, e.g. [2], others. 2) SD&S verifies user profiles from IUDF/UPSF. The location of IUDF/UPSF and data model, e.g. centralized or federated is described in clause 9. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 38 3) SD&S replies service offers to UE. 4) MDF outputs BTV multimedia stream, such as regular TV channels or scheduled content, to the TPF connected via MGF. 5) UE requests TPF to join linear TV channel A (BTV multicast stream). 6) Optionally, resource admission control may take place at this stage. For Multicast, this is typically performed by an A-RACF, which can be separately located or collocated with the TPF [10]. 7) Channel A is delivered. 8) UE requests TPF to leave linear TV channel A. 9) If resource admission control was executed in Step 6, resource release procedure shall take place at this stage. 10) UE requests TPF to join linear TV channel B. Optionally, local admission control can check resource availability before granting the request. 11) Optionally, resource admission control may take place at this stage. For Multicast, this is typically performed by an A-RACF, which can be separately located or collocated with the TPF [10]. 12) Channel B is delivered. NGN Linear TV IPTV session is a lasting service agreement and reserved network delivery resources for broadcast multimedia service between UE and TPF, e.g. between and including steps 5) and 8) on figure 14. Typically in the coupled mode UE would access the channel (step 4) immediately after step 3. In the decoupled mode there could be a time delay between step 3 and step 4, e.g. user may be authenticated to access bTV package at the service initialization stage (steps 1-3), but choose to view channel from the package at the later time (step 4). NOTE: This and subsequent flows show separate location of the TPF and RACS, they can be co-located as discussed in [10].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.2 Multimedia Content on Demand (CoD)
|
This clause provides the flows for the CoD IPTV services integrated into the TISPAN NGN architecture and inter-working with the NGN common functions and components. The clause presents generic flows and does not mandate placement of functions. DRM flows are not included. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 39 1. Acquisition of SD&S information 2. NASF MCF RACS IPTV Control UE 3. 4. CoD Service purchase 5. 7. 8. CoD Delivery selection 9. Resource reservation 11. CoD Delivery 13. CoD VCR- control 14. Automatic resource release 10. 6. Authorisation record 12. Authorisation verification UPSF/ IUDF SD&S / CFIA Figure 15: NGN IPTV CoD procedure 1) UE requests SD&S information from SD&S. SD&S format and request methods are outside the scope of the present document and have been researched in other specifications, e.g. [2], others. 2) SD&S verifies user profiles from IUDF/UPSF. The location of IUDF/UPSF and data model, e.g. centralized or federated, is described in clause 9. 3) SD&S replies service offers to UE. 4) User selects a service from the offers. UE requests the selected service from Customer Facing IPTV Applications. 5) Customer Facing IPTV Applications. Optionally creates billing event, e.g. for on-line billing, and sends it to IUDF/UPSF. The location of the billing information and data model are discussed in clause 9. 6) Customer Facing IPTV Applications optionally creates authorization record (play ticket) to authorize content delivery. 7) Customer Facing IPTV Applications replies the location of IPTV control and optionally ticket data to UE. 8) UE requests IPTV control the location of MCF. Optionally ticket data is supplied. 9) IPTV Control selects MCF based upon operator defined criterions and requests RACS to allocate resources between the end-points. Distributed RACS interfaces are allowed. 10) IPTV Controls replies MCF location to UE. 11) UE requests MCF to deliver media using reserved session and associated resources. Optionally ticket data is supplied and the ticket punched. 12) MCF optionally verifies user credentials to request multimode delivery. 13) UE utilizes VCR style control over media to MCF. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 40 14) Automatic resource reservation follows session termination, which can be initiated either by end point UE or MCF, or by an IP network. Although it is not necessary to explicitly tear-down an old reservation, we recommend that during normal operation MCF or IPTV Control send a teardown request to RACS as soon as the session has finished. NGN CoD IPTV session is a lasting service agreement and reserved delivery resources on server and network levels for multimedia on demand service between UE and MDF. Cod flows do not cover NAT explicitly, however, standard IP NAT protocols can be used, see [14].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.2.1 Optimized bandwidth utilization during CoD
|
This clause discusses optimized bandwidth utilization during CoD procedure for UE containing local storage. The MDF, during media delivery initiated by Step 13 on figure 15, may increase the bandwidth of the session to a higher bandwidth once the session has been opened, to permit delivery of data from MDF to the UE at a rate higher than the nominal reserved rate. The excessive content should be saved on the local storage for further consumption. The content "burst" may come with a different network priority or class of service. The UE may optionally provide feedback to the delivery server, e.g. the UE may detect missing data and to request missing packets from the delivery server using a retransmission approach and a RTP/RTCP feedback mechanism specified in clause A.3 [1]. The MDF may increase the bandwidth gradually, waiting for the results of feedback received by the delivery service: the MDF increase the bandwidth gradually until a retransmission request is received, and, once the retransmission request has been received, to reduce the bandwidth gradually until retransmission requests are no longer received. The delivery server may cyclically increase and decrease the bandwidth, in accordance with the retransmission requests. Optimized bandwidth utilization enables more efficient utilization of the network resources and capacity, e.g. since the content can be delivered faster (e.g. at the idle times) and RACS resources to be released earlier (e.g. to meet peek demands). Figure 15A illustrates Optimized bandwidth utilization during CoD. Figure 15A: Optimized bandwidth utilization during CoD 1) CoD session setup as discussed in clause 11.2. During session setup at SD&S stage the UE has been identified as containing local storage and enabled for optimized network utilization mode. 2) Content media flow from MDF to UE. 3) MDF increases delivery bandwidth. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 41 4) Content media flow from MDF to UE. 5) Media loss detected. Request for missing data. 6) MDF requested retransmission of missing data. Steps 3 to 6 can be repeated.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.