hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.24 Role of BGF in IPTV
|
In certain IPTV scenarios there is a need to bypass the BGF for scalability reasons. For example, the BGF could be bypassed when using MPEG2-TS directly over UDP transport, as well as, for RTP(RTCP) transmission when there is no RTCP towards the network. It shall be possible to bypass the BGF. Its use is a local decision taken by the network provider during the IPTV session setup based on the session information provided.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.25 Procedures for service initiation by remote UE
|
The service initiation by remote UE can be used by one remote UE to activate the target UE to start-up the IPTV service, for example, it can be used to remote start-up UGC, CoD or BC services. Figure 39M depicts the typical steps for service initiated by Remote UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 136 Figure 39M: Service initiation by Remote UE 1A) The Remote UE sends a remote service start-up request through the Core IMS to the SCF. The request carries the necessary parameters indicating the service identified by the IPTV service type identifier (see clause I.2), e.g. BC service or UGC service, IPTV content identifier (see clause I.1) when appropriate, user identifier of Target UE which start-up the service and user identifier of the remote UE. 1B) The SCF performs service authorization as described in clause 5.1, if the Remote UE is allowed to perform remote start-up operation of the service, the SCF forwards the remote service start-up request through the core IMS to the Target UE. And the user of Target UE may deny the request even if the SCF authorized. NOTE 1: The SCF authorizes the remote UE by checking the user profile of the Target UE. 1C) The Target UE sends a remote service start-up response through the Core IMS to the SCF. 1D) The SCF forwards remote service start-up response through the Core IMS to the Remote UE. NOTE 2: The remote service start-up request in steps 1A-1D may directly sent to the target UE if SCF does not need to perform authorization. 2) The Target UE initiates the service indicated in the remote start-up request, e.g. BC or CoD session initiation following the procedures of clauses 8.3.1.1 or 8.4.1.1. CORE IMS SCF MF 2). Service initiation procedures Target UE Remote UE 1A. Remote service start-up Request 1A. Remote service start-up Request 1D. Remote service start-up Response 1D. Remote service start-up Response 1B. Remote service start-up Request 1B. Remote service start-up Request 1C. Remote service start-up Response 1C. Remote service start-up Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 137 8.26 Signalling flows for IPTV service state data updates/requests IPTV service state data may be updated by MF as described in clause 8.26.1. Furthermore, IPTV service state data requests may be initiated by the SCF as described in clause 8.26.2. The procedures are limited to data within the SSD model and which the SCF cannot derive directly from ongoing traffic and events.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.26.1 IPTV service state data updated by MF
|
The procedure described in figure 39N is used to update IPTV service state data by the MF. The SSD may need to be updated for example when a user pauses a streaming or terminates the session. Figure 39N: IPTV service state data updated by MF MF is triggered by an event, e.g. by detecting a pause or and end of a session and decides to send changes of SSD to the SCF. 1) MF sends an SSD update request to save the current SSD. This request may also include a indicator to inform the SCF of the reason for the SSD update. 2) The IMS core forwards this request to the SCF. 3) The SCF updates the SSD. 4) The SCF confirms the SSD update. 5) The IMS core forwards the response to the MF. 8.26.2 IPTV service state data update requested by the SCF This procedure allows the SCF to acquire an update of the current service state from the MF during an ongoing session. Figure 39O provides an overview of the information flow for an SSD update request by the SCF. This procedure can occur at any time during ongoing IPTV services (CoD/N-PVR/, etc.). (1) SSD update Request (3) Save SSD update SCF Core IMS MF Event triggering the SSD update (2) SSD update Request (4) SSD update Response (5) SSD update Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 138 Figure 39O: SCF IPTV service state data Request Procedure 1) The SCF sends an SSD request to the MF, via the IMS core, to request the service state during an ongoing IPTV service. 2) The IMS core forwards this request to the appropriate MF for the IPTV service. 3) The MF acquires the requested information. 4) The MF returns to core IMS the requested information in an SSD response. 5) The IMS core forwards the response to the SCF, which updates the SSD accordingly. 9 Interactions between IPTV services and other TISPAN services Several approaches can be employed for realizing the interaction between IPTV services and other TISPAN services. This clause describes approaches that are considered within the TISPAN architecture, e.g. where application servers interact directly through Core IMS. Two other approaches involving 3GPP SCIM and OSA/Parlay methods are described in annex C.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.1 Presence and IPTV
|
IPTV services may be combined with the presence service capability. This clause describes the mechanisms that apply when IPTV services are combined with the presence service capability. These mechanisms may also be used for other purposes then publishing user presence information. For example they may be used to gather statistics about BC TV Service or user behaviour information.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.1.1 Presence architecture and functional description
|
The architecture and functional description of the presence service capability when used in relation to the IPTV services conform to TS 182 008 [10]. SCF Core IMS MF (1) IPTV SSD Request (3) MF fetches the information (2) IPTV SSD Request (4) IPTV SSD Response (5) IPTV SSD Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 139
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.1.2 Presence attributes for IPTV
|
The Presence attributes defined in TS 182 008 [10] apply. In addition, the following specific IPTV attributes shall be supported: • BC service activated; • CoD service activated; • PVR service activated. If the IPTV presence attribute "channel currently accessed" is supported, then the machine-readable part of the identification of the channel shall be globally unique. The term globally unique here means that there is no ambiguity in the identification of the channel if presentity and watcher (for terminology, see in TS 182 008 [10]) are with different network operators and/or in different countries. The following specific IPTV attributes may also be supported: • IPTV service activated; • IPTV service type identifier (see clause I.2) should be used to identify which service(s) are activated: - UGC service activated; - PCoD service activated; - TAI service activated; - PCh service activated; - SSC service activated; - PSC service activated. • IPTV content identifier (see clause I.1) should be used to identify which content(s) are currently accessed/watched: - BC TV Service currently accessed; - programme currently watched, when available; - content currently accessed. • current service state (e.g. paused, playing, in trick play mode). • IPTV service access history. It is up to user's decision to include specific IPTV attributes in presence document. Note that if a service relies on user's presence information, but the user has decided not to publish this information, the user may not be able to utilize the service. When the "BC service activated" attribute is included in a presence document, the attributes "BC TV Service currently accessed" and "programme currently watched" may also be included, depending on user preferences. These attributes shall not be present in a document if the "BC service activated" attribute is not present. When the "CoD service activated" or the "PVR service activated" attribute is included in a presence document, the attribute "content currently accessed" may also be included depending on user preferences. This attribute shall not be present if the "CoD service activated" or the "PVR service activated attribute" is not present. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 140
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.1.3 SIP related procedure
|
The SIP related procedures defined in ES 283 030 [13] apply. The publication of CoD related presence information happens: • after completion of CoD session initiation procedure; • after completion of CoD session termination procedure. The publication of BC related presence information happens: • after completion of BC session initiation procedure; • after completion of the BC session termination procedure; • optionally, when the UE successfully subscribes to a particular multicast channel (i.e. channel hopping). In order to cope with overload possibly caused by numerous channel-hopping, it shall be possible to define a timer to limit the number of publications. This timer is started and reinitialised after each channel change. Publication shall only be sent when the timer elapses. NOTE: Preventing overload caused by numerous IPTV service access entries, is possible by defining a timer or ceiling to limit the number of publications. The publication of UGC related presence information happens: • after completion of UGC creation session initiation procedure; • after completion of UGC creation session termination procedure; • after completion of UGC watching session initiation procedure; • after completion of UGC watching session termination procedure. The publication of PCoD related presence information happens: • after completion of PCoD session initiation procedure; • after completion of PCoD session termination procedure. The publication of PCh related presence information happens: • after completion of PCh session initiation procedure; • after completion of PCh session termination procedure. The publication of TAI related presence information happens: • after completion of TAI session initiation procedure; • after completion of TAI session termination procedure.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.2 Incoming call management
|
The combination of basic IPTV services (e.g. Broadcast, CoD and N-PVR) with telephony allows a user to have increased control over incoming calls when watching TV. This clause describes an approach, where the IPTV SCF decides based on incoming call state, IPTV service state and user profile settings how to handle the call. Approaches using only standard IMS telephony mechanisms to inform IPTV UE of incoming calls are described in [2]. Also, if the user is registered with the same IMPU on the UE (Phone) and UE (IPTV ) normal IMS forking procedures (as described in [2], clause 4.2.7) apply. The following procedure only applies if the user is registered with different IMPUs on the aforementioned UEs or when forking results in the IPTV SCF being involved. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 141
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.2.1 Procedure for incoming call management
|
Figure 39P shows a signalling flows for incoming call management. Figure 39P: Signalling flows for incoming call management NOTE 1: "Incoming call" indicates an incoming call that may come from different sources such as a telephony AS, an originating network, or a UE. 1) An incoming call is received by the Core IMS. 2) The Core IMS forwards the session initiation request to SCF. 3) The SCF retrieves user profiles and IPTV service and call state. 4) Optionally, the SCF notifies the user and ask what to do with the incoming call, based on IPTV service and call state, if this is indicated in the user profile (see clause 9.2.2). In case of no answer from the user on the IPTV UE B1 after a timeout, SCF may perform any of the actions in step 5. 5) Optionally, the SCF performs one or more actions. For example, these actions are performed based on - the IPTV service and call state; - and/or the answer of the user if step 4 is performed and an answer from the UE has been received by the SCF; - and/or indications in the user profile (e.g. pause on incoming call using network-controlled trick play from clause 8.16 or redirect the call to voicemail). 6) Telephony session establishment: based on the outcome of the previous steps the SCF handles the incoming call (e.g. accept, reject the call or forward to another AS). CORE IMS SCF Incoming call 1. Session Initiation Request 4. UE notification and selection (clause 9.2.2 / 9.2.3) 2. Session Initiation Request 3. User profile check and state handling 6. Telephony session establishment 5. SCF-Controlled action 7. UE notification UE B2 (Phone) UE B1 (IPTV) User B User A ETSI ETSI TS 182 027 V3.5.1 (2011-03) 142 7) Optionally, the SCF notifies the user on its UE B1 (IPTV ) about the incoming call (e.g. "caller id" presentation on the TV) and/or optionally, about the action that has been performed during step 4 on behalf of the user. NOTE 2: The order of the steps 4-7 may change. Steps 4, 5 and 7 are optional. For example, an incoming call notification that requires user action is covered on step 4; an incoming call notification that only present the incoming call (e.g. "caller id") is covered by step 7. 9.2.2 Incoming call accepted on a phone device Figure 39Q shows a signalling flow for an incoming call accepted by user. Figure 39Q: Signalling flows for an incoming call accepted by user 1) The SCF sends a notification to UE B1 (IPTV) with a message about incoming call from user A (using notification procedures using signalling path as described in clause 8.11.1.1). 2) User B may select from multiple options how to handle incoming call, for example: - Accept on TV; the TV signal is paused and phone is ringing. Steps 1-3 from previous clause §9.2.1 UE B1 (IPTV) CORE IMS SCF UE B2 (Phone) Incoming call Network 1. Notification about incoming call 2. Selection of option for handling call 3. Selection response for handling call 4. Session Initiation Request to UE Phone 5. Session Initiation Request to UE Phone User A User B 10. Session established 9. Session Initiation Response 8. Session Initiation Response 7. Session Initiation Response 6. Session Initiation Response Pick up ETSI ETSI TS 182 027 V3.5.1 (2011-03) 143 - Accept on phone; the call is forwarded to user B's UE B2 (Phone). According to his user profile and service and call states, the TV can either be paused or can continue. - Route to mailbox; if user B does not answer the call or based on his user profile, the call is forwarded to his voicemail box. - Refuse; user B does not answer the call. 3) Based on the user decision in step 2, UE B1 (IPTV) sends to SCF response how to handle the incoming call 4) - 5) The SCF forwards the session initiation request to UE B2 (Phone) via Core IMS in B2BUA mode (The SCF stays in the call path). 6) - 7) UE B2 (Phone) sends a session initiation response to the originating network via the SCF (in B2BUA mode). 8) - 9) SCF sends the session initiation response to the originating network via the Core IMS. 10) Telephone session established.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.3 Message and IPTV
|
9.3.1 Messaging procedures Messaging procedure is used for several purposes: where messages are sent between users or between system and users. Following procedures may be primarily used for immediate messaging described in TS 181 016 [15] in section in clause 6.2.3 to provide services specified in TS 122 340 [16] together with IPTV services. Several additional specific use cases described in TS 181 016 [15] (e.g. in clause in annex A) require integration of existing messaging systems (in this case IMS based messaging) with IPTV service logic to provide blended IPTV and messaging service (e.g. messaging during BC service or chat discussion related to content or related to used IPTV service, etc.). Figure 40 depicts the typical steps that occur when the UE wants to send message from one user to one or more other users using signalling path. Figure 40: messaging procedure using signalling path 1) UE sends a message request via IMS core to SCF using signalling path for IMS messaging mechanisms [2]. Message contains message itself (supporting different media content types as in [16]) and also parameters which identify related IPTV service blended with this messaging procedure. 1. Message request send via core IMS CORE IMS SCF 1..n UEs 3. Message forwarded via core IMS to 1..n UEs UE 2. Validating request, evaluate destination address based on service logic, generate message and presentation rules ETSI ETSI TS 182 027 V3.5.1 (2011-03) 144 2) SCF evaluates appropriate destination UEs for delivery message to specified group of users (as users interaction related with IPTV services) based on service logic (and other conditions e.g. user profile or messaging rules) specified for required IPTV service. SCF may also modify/generate messages (original message may be included together with additional IPTV related information e.g. watched channel, form of presentation of message, etc.). 3) SCF sends message (original/modified) via IMS core using IMS messaging framework [2] to one or more UEs. NOTE : In this example the messaging service function is not explicitly shown for brevity. IMS messages may traverse the messaging service function, and are under service provider control. Furthermore, while figure 40 shows the SCF in the path of the IMS message, this is an option and need not be the case for all IMS messages originating/terminating from/to an IPTV end user. The SCF would typically be in the signaling path of an IMS message if the message is addressed explicitly to it, or if it has to perform some special procedure on the message. 9.3.2 Procedures for deliver messages of BC service using media path This clause describes mechanisms of deliver messages that are associated with a BC service using media path. These mechanisms may be used for some purposes. For example they may be used to participate in a comment service associated with a BC program; one user can send his comment to the SCF using IMS immediate message services, then the SCF and the MF deliver the comments to all users who subscribed to the comment service associated with the BC service. Figure 41 depicts the typical steps that occur when one user sends IMS immediate messages to SCF, and SCF and MF deliver the message to users who subscribed to the message services associated with the BC service. NOTE 1: The parameters for joining the multicast group, i.e. multicast address, need to be available to UE before it receives the messages delivered using media path. Figure 41: Deliver messages of BC service using media path 1) UE joins a BC service and the messages multicast group associated with the BC service, e.g. comment services of a BC service. 2) UE initiates an IMS immediate message request carrying the message, which is specified in the IMS stage 2 specification [2]. The immediate message is routed by Core IMS to the SCF in charge of the delivery of messages associated with the BC service. (2) Send IMS Message to SCF UE Core IMS SCF MF (1) UE joins a BC service and the message group associated with the BC service (3) Notification procedures using media path (in clause 8.11.1.2) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 145 3) The SCF detects which BC service is associated with the IMS immediate message e.g. by the destination of the immediate message, and sends the IMS immediate message to the selected MF. The MF transfers the IMS immediate message to the multicast group associated with the BC service. The procedures use mechanisms of delivering notification using media path specified in clause 8.11.1.2, and the notification request from SCF to the selected MF at least contains parameters of BC service ID and the message. NOTE 2: Existing mechanisms of IMS could be used for the SCF to distinguish IMS immediate message from normal IMS message, e.g. by checking the content type of the message body.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
9.4 Event Handling involving the SCF
|
Event handling by the SCF takes place if the SCF receives events from several sources. The events can include requests from the UE, new content arrival notification, presence updates, trick play reports from MF, channel change reports from UE, events from other NGN application servers, external applications and so on. Usage of this procedure occurs in several cases under clause 8. SCF involvement is required depending on the event and the user profile configuration. Examples include incoming call management involving multiple UE's (e.g. pause on incoming call), emergency warning and alerting systems, or parental control. In such cases the SCF needs to correlate the event with the right UE and apply service logic to determine the applicable action to the UE and/or MF. Figure 42: Event handling involving the SCF 1) The SCF receives an incoming event which requires handling. NOTE 1: It is up to the IPTV Service Provider, on behalf of the user and/or based on the service requirements, to decide when to route an incoming event to the SCF a or send it directly to the UE. 2) The SCF correlates the incoming event with the designated user/group of users and/or UE's, performs authentication and detects the ongoing IPTV service status. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. NOTE 2: The SCF can decide which (if any) further actions to perform, e.g. based on user preferences and detected service state. 3) The SCF performs an action towards the UE and or MF, e.g. it can send a notification to the UE or instruct the UE to send a trick play command/change the channel. UE Core IMS SCF 3 SCF action towards UE and/or MF 2 Event handling MF 1 Incoming event triggering the handling ETSI ETSI TS 182 027 V3.5.1 (2011-03) 146
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
10 Security
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
10.1 Authentication
|
Authentication procedures for the Ut reference point conforms to TS 187 003 [5].
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
10.2 Content Protection
|
The locations and related reference points of the following elementary functions are defined in TS 187 003 [5]. They are reproduced below for information. 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 licencing, 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: 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).
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
10.3 Service Protection
|
The locations and related reference points of the following sets of elementary functions are defined in TS 187 003 [5]. The function groups are reproduced below for information. 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 protection the following sets of elementary 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 SCF, 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. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 147
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
11 Charging
|
IMS charging principles apply as defined in ES 282 010 [i.3]. TISPAN IMS-based IPTV shall use the generic IMS charging model using the standardized Rf reference point for offline- and Ro reference point for online charging. NOTE: Further IPTV service-specific charging may be required in addition to the generic IMS charging but is out of scope for the present document in this release.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
12 Management
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
12.1 Management requirements
|
For each IPTV service, several entities require to be provisioned with necessary network parameters (e.g. multicast addresses for multicast services, source of original content, etc.) and to associate specific content or service with these network parameters. These entities are: • the SSF, as it needs to provide the UE with the content identifier associated to an IPTV service and possibly with a set of network parameters (control and/or content channel descriptions) necessary to initiate an IPTV session; • the MFs, as they need to associate a content identifier with multicast or unicast streams to be delivered to the UE; • the SCF, as it may also need to provide the UE with network parameters in response to service initiation requests, in configurations where the SSF does not provide this information beforehand. Consistent information has to be provisioned on these entities.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
12.2 Content management
|
Content management functionalities are responsible for managing acquisition of content and service information (e.g. metadata) from content and its metadata sources of content provider, controlling validation and/or processing/adaptation to the required format and also to provide management functionalities for supporting distribution of the prepared content to the media delivery function and distribution of content among different media delivery functions. 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. Content management functionalities can consist of the following groups of elementary functions: • Content acquisition - responsible for content management functionalities needed to acquire, aggregate and import content/metadata from multiple external sources of content providers. • Content validation/adaptation - after acquisition it could be necessary to manage content/metadata format validation and verification as well as to define a relation between content and its metadata. Management can also control media or metadata adaptation and/or processing (e.g. transcoding, packaging, scheduling, resolution conversion, editing, etc.) to the required type of media files or streams. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 148 • Content distribution Control - management functionalities for control the distribution of content and its metadata from content providers when content acquisition/ content validation/adaptation were performed to appropriate functional entity (e.g. media files storage in MDF). This function handles the whole lifecycle of the content and provide management support for its distribution to media delivery distributed architecture (e.g. uploads on video streamers, moving according to management criteria such as popularity, regionalization, un-referenced content, MDF resources and so on). Additionally, this function can control the content distribution among MDFs (e.g. delete content in some MDFs, moving content from one MDF to other MDFs) according to some criteria such as content popularity.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
13 Support of Metadata
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
13.1 Introduction
|
IPTV Metadata enriches the service experience of the IPTV Services a user has access to. IPTV Metadata may originate from the User, the NGN Service Provider, the Application Provider or the Content Provider. The Metadata should be processed, filtered and enriched by involved IPTV solution entities in order to improve the user experience. NOTE 1: Processing, Filtering and Enriching Metadata may be based on techniques like personal preferences, additional subscribed-to services and other means and are out of scope of the present document. NOTE 2: How user originated Metadata is injected into the IPTV solution is out of scope of the present document. NOTE 3: Content metadata may be delivered along with the content in real time (from MDF). In this case metadata might differ from the metadata already stored in the SSF and therefore SSF can require update them with relevant metadata from MDF. Also, IPTV CRS might be a service requiring the SCF to access actualised metadata. Generally, if UE or other entity needed most updated metadata it is requesting them from SSF (SSF is responsible acquire most updated metadata). NOTE 4: The mechanisms and handling of all possible cases for synchronization of metadata cross multiple IPTV Fes, are not provided in the current specification. The access to Metadata may be considered as a service in itself which shall be protected by appropriate service authorization means before the Metadata is delivered to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
13.2 SSF support
|
IPTV Metadata may be delivered outside of an IPTV service session by the SSF. Xa shall be used for the Metadata delivery.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
13.3 SCF/MF support
|
IPTV Metadata may be delivered as part of a normal IPTV service session or inside an IPTV service session dedicated to Metadata delivery. In the first case, the Metadata is sent in addition to Media as part of the IPTV session. In either case the Metadata capabilities are negotiated during session setup or session modification between UE and SCF. The Metadata itself is delivered via the MDF through unicast or multicast via Xd. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 149
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
14 Support of Mobility Capabilities
|
To support the mobility capabilities of IPTV services, the UE shall support roaming in the Visited Network. When the UE is located in the Visited Network, it can access the IPTV services in its own home network. Sometimes when the IPTV Service Provider servers both home network and visited network, the MF can server both visited network and home network. Annex H give interconnection examples to support of mobility capabilities.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
15 Emergency alert
|
The IPTV solution shall enable deliver emergency alerting based on different aspects (e.g. type of emergency situation, priority, and locality). TISPAN IMS based IPTV subsystems may in practice also require secure mechanisms to acquire, verify and inject the appropriate content (alert message or emergency live transmission) after ensuring that it comes from an authorized source. The emergency alerts will only achieve their purpose if they are immediately delivered to UE (interruption of actually watched content may be required) when they alert the public promptly, accurately and efficiently and then correctly decoded and rendered on the user equipment. Following examples of procedures may be used for delivery of emergency alert to UE (other existing delivery mechanisms are also possible): • using notification procedures to deliver message (notification procedures as in clause 8.11.1.1) with confirmation of delivery; • using notification procedures using multicast media path as described in clause 8.11.1.2 (for stream insertion or replacement of actually watched content) or to deliver live emergency transmission via multicast (e.g. using SCF-initiated BC session initiation). NOTE: Emergency alert capability can be subject to local or regional regulation. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 150 Annex A (informative): Integration of non-SIP-AS Service Discovery Function in IMS based IPTV A.1 Introduction Clause 5 defines Service Discovery and Selection (SD and S) as a two step process consisting of Service Discovery and Service Selection. While clause 5 focuses on discovering services by an SIP based SDF entity, the Service Selection uses non-SIP mechanisms. This annex describes using non-SIP SDF to reuse standard non-SIP Service Discovery technologies such as DVB-IP Service Discovery as specified in TS 102 034 [6]. A.2 Architecture Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions CoD-MCF CoD-MDF BC-MCF BC-MDF N-PVR-MCF N-PVR-MDF IPTV Service Control Functions CoD-SCF BC-SCF N-PVR-SCF Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions IPTV Media Delivery Functions Sh Ut y2 SDF Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions Xa’ Figure A.1: Functional architecture for IPTV services integrating non-SIP SDF A.2.1 Functional entities Figure A.1 depicts the IMS based IPTV architecture based on figure A.2 using a non-SIP AS SDF for Service Discovery. All entities are defined in clause 5. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 151 A.2.2 Reference points Figure A.1 depicts the IMS based IPTV architecture based on figure A.2 using a non-SIP AS SDF for Service Discovery. All shown reference points are defined in clause 6 except Xa' which is described in the following clause. A.2.2.1 UE - SDF (Xa') This reference point delivers Service Discovery Information, i.e. SSF addresses in the form of URIs and/or ip-address, from the SDF to the UE. Both Unicast and Multicast delivery of this information is possible. The use of Xa' conforms to TS 102 034 [6] clause 5.2.5, where the term "HNED" is to be replaced by "UE" and where "Location(s)" carries the SSF address(es). A.2.3 Procedures A.2.3.1 IPTV service attachment and selection Figure A.2 defines steps 3 and 4 of figure 9 in case the SDF is not SIP-AS based. Figure A.2: IPTV service attachment and selection 1) The UE requests the SDF it was assigned. This assignment may have occurred during the network attachment phase, during offline provisioning or by other means. 2) The SDF determines the proper SSF (or SSFs). It is for further study how the SDF may take into account the UE's capabilities, the user's profile and/or the location of the UE (Personalized Service Discovery). 3) Configuration information that includes the SSF address(es) is (are) routed back to the UE. 4) The UE requests the SSF to get the selection data. 5) The SSF delivers the requested data to the UE. NOTE: If a non-SIP AS SDF is used for IPTV service attachment, no IMS registration prior to step 1) of figure A.2 is required. Therefore, step 2 of figure 9 (IMS registration) can occur in parallel to, before or after the procedure described in figure A.2. UE SDF SSF (2) SSF Election (1) attachToIPTV (3) Service Config Info ( Elected SSF address,...) (4) request selection data (5) retrieve selection data (EPG, CoD catalog, …) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 152 Annex B (normative): Policies for Shared Service Control B.1 SSC room policies An SSC Policy is associated with an SSC room, identified by the RoomId attribute. A user in an SSC room has an SSC Privilege containing the allowed actions by that user. Additionally, SSC room privileges can be allocated to service logic for performing room administration tasks. Note that this annex does not describe an SSC room data model, nor does it describe implementation of the SSC room itself. Figure B.1 shows a generic data model for an SSC Policy. Figure B.1: Data model for SSC Policy • Room Administration actions: - AddUser: boolean indicating whether the user is allowed to add other users to the SSC room. Adding users to the room is done by extending the list of allowed users associated to the room, that is exchanged during SSC room creation (step 1A of clause 8.21.2). - NotifyUser: boolean indicating whether the user is allowed to send notifications to other users of the SSC room. If a user is allowed to send notifications related to the SSC room, the messaging procedures from clause 8.11 apply. - InitiateRoom: boolean indicating whether the user is allowed to initiate a service in the SSC room (clause 8.21.3, step 3). If the SSC room has been created by another user, this user may or may not be allowed to do that. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 153 - DeleteRoom: boolean indicating whether the user is allowed to delete the SSC room. SSC room deletion is performed according to clause 8.21.5. - GiveFloor: boolean indicating whether the user is allowed to give the floor to another user in the room. Typically, a chairman has this right. Specific procedures for floor control are out of scope of this release. - TakeFloor: boolean indicating whether the user is allowed to take floor control. Typically, a presenter has this right. Specific procedures for floor control are out of scope of this release. - SendMessage: boolean indicating whether the user is allowed to send messages to other users of the SSC room. If a user is allowed to send messages related to the SSC room, the messaging procedures from clause 9.3. apply. - IsAdmin: boolean indicating whether the user has administrator rights. - IsInitiator: boolean indicating whether the user has initiated this SSC room, and has associated rights. - ArbitrateConflict: boolean indicating whether the user has right to arbitrate a conflict. An example of such conflict is different users wanting to watch different BC channels. NOTE: Different approaches for the arbitration of conflicts exist, but are not describing further here. • ContentControl actions: Describes actions that can be performed in relation to content services. In case of a shared BC service, the content is a channel. In case of a shared CoD service, the content is a CoD item and so on: - AddContent: boolean indicating whether the user is allowed to add the content to the SSC room. - ChangeContent: boolean indicating whether the user is allowed to change the content being watched in the SSC room. - RemoveContent: boolean indicating whether the user is allowed to remove content from the SSC room. - BlockContent: boolean indicating whether the user is allowed to block content from being watched in the SSC room. Parental control may be a reason to block content. - TrickplayControl: PlayContent: boolean indicating whether the user is allowed to play content. PauseContent: boolean indicating whether the user is allowed to pause content. RewindContent: boolean indicating whether the user is allowed to rewind content. RestartContent: boolean indicating whether the user is allowed to restart content. FastForwardContent: boolean indicating whether the user is allowed to fast forward content. StopContent: boolean indicating whether the user is allowed to stop content in the SSC room. The SSC policy, or part of it, may be performed at the UE or at the MF. This would prevent the user from sending administration and/or content control actions that are is not allowed to. Policy distribution towards the UE is not described in the present document. Tight floor control follows strict rules on the actions that users may perform in relation to the service state of the SSC room. This may require a more detailed floor control policy that sets those rules. It could describe the use of timers and master allocation through e.g. tokens. Such policy is not described in the present document. Loose floor control allows any user to perform administration and/or content control actions without first taking the floor. This can result in control conflicts. An example is when two users are simultaneously trying to switch to different BC channels. Such conflicts should be automatically resolved by the network, so that the service state of the SSC room and the associated UE's remain aligned. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 154 Annex C (informative): Architectures for Interactions between IPTV services and other TISPAN services This Annex contains examples of architectures that can enable the interaction between IPTV services and other TISPAN services. The examples of architectures given refer to existing work and serve to clarify how service interaction can achieved by using this existing work. For these architectures, it is assumed that service interaction requires a dedicated Application Server that may explicitly implement the blended service functionality (e.g. pausing the TV on incoming call, or watching apart together). Such an AS can be seen as an external application with respect to the TISPAN IPTV architecture. C.1 Interaction based on an OSA/Parlay/Parlay X SCS This approach is based an OSA/Parlay/Parlay X Service Capability Server (SCS), that provisions standardized interfaces and APIs to external and third party application servers. The use of such an SCS is described in ES 204 915 [i.5], ES 202 504 [i.6], TS 129 198 [i.7] and TS 129 199 [i.19]. C.1.1 Service Capability Server (SCS) The OSA SCS acts as a secure gateway between the underlying network and the application with the OSA architecture. It is responsible for providing specific service abilities to third party applications. An SCS further serves to make an abstraction of the functionality offered by the network, in effect offering the service capability features of the underlying network to the third party applications. C.1.2 Architecture Figure C.1 shows a simplified version of the IMS-based IPTV architecture from figure 2 in clause 5.1.1, with interfaces to an SCS and subsequent external applications. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 155 Figure C.1: Interaction between TISPAN IMS-based IPTV architecture and an OSA/Parlay/Parlay X SCS C.2 Interaction based on a 3GPP SCIM This approach is based on a Service Capability Interaction Manager (SCIM), that allows for service association and dynamic service triggering. The use of such an SCIM is described in TS 123 002 [i.8], TS 123 218 [i.9] and 3GPP TR 23.810 [i.10]. C.2.1 Service Capability Interaction Manager (SCIM) The Service Capability Interaction Manager (SCIM)is a function that manages the interaction between IPTV services and other NGN services, by e.g. associating the IPTV services with other NGN services and dynamic triggering the services in the ongoing session based on the information about the relational session or user's status. C.2.2 Architecture Figure C.2 shows a simplified version of the IMS-based IPTV architecture from figure 2 in clause 5.1.1, with interfaces to an SCIM and subsequent external applications. Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc ExternalApplications(OSA AS) OSA/ Parlay/Parlay X Gateway (SCS) e.g. CORBA/SOAP OSA/Parla API Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc ExternalApplications(OSA AS) OSA/Parlay/Parlay X Gateway (SCS) e.g. CORBA/SOAP OSA/Parlay API ETSI ETSI TS 182 027 V3.5.1 (2011-03) 156 Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc External Applications (SIP AS) 3GPP SCIM ISC ISC ISC Figure C.2: Interaction between TISPAN IMS-based IPTV architecture and a 3GPP SCIM ETSI ETSI TS 182 027 V3.5.1 (2011-03) 157 Annex D (informative): Mapping of elementary functions D.1 Mapping of elementary functions to generic capabilities Mapping of elementary functions in table D.1 show which elementary function (listed in clause 5.1.4) are applicable to generic capabilities (described in clause 5.1.3A). Table D.1: Mapping of elementary functions to generic capabilities Elementary function Discover and select content Service control Service interact Media control Deliver media Content protection Content mng. and distribution Service Protection Service interaction 1 network attachment X 2 registration X 3 resource management X 4 charging information X X 5 service discovery X 6 service authorization X X X 7 service selection X X X 8 service initiation X X 9 service control X X X 10 service information handling X X X X 11 service configuration X 12 session initiation X X X 13 session modification X X X 14 session termination X X X 15 multicast based media delivery X 16 unicast based media delivery X 17 content download/upload X 18 control of multicast streaming X X 19 control of unicast streaming X X 20 control of download/ upload 21 content ingestion/receiving X X 22 content recording X 23 content storage X 24 content adaptation X 25 content acquisition X 26 content validation X 27 content distribution X 28 content licencing X 29 key management X X 30 content encryption X 31 user profile/data mng. X X ETSI ETSI TS 182 027 V3.5.1 (2011-03) 158 Elementary function Discover and select content Service control Service interact Media control Deliver media Content protection Content mng. and distribution Service Protection Service interaction 32 accounting/right control X X X 33 status/state (changes) detection/reporting X X X X 34 common notification X X X 35 messaging X X 36 presence X X 37 inter-destination media synchronization X X X D.2 Mapping of elementary functions to functional entities Mapping of elementary functions in table D.2 show which elementary function (listed in clause 5.1.4) are applicable to functional entities (described in clause 5.1.3). Table D.2: Mapping of elementary functions to functional entities Elementary function UE SSF SDF Core IMS SCF UPSF MCF MDF 1 network attachment X X 2 registration X X X 3 resource management X 4 charging information X X X 5 service discovery X 6 service authorization X X X 7 service selection X X 8 service initiation X X 9 service control X X X 10 service information handling X X 11 service configuration X X X 12 session initiation X X X 13 session modification X X X 14 session termination X X 15 multicast based media delivery X 16 unicast based media delivery X X 17 content download/ upload X X 18 control of multicast streaming X X 19 control of unicast streaming X X 20 control of download/ upload X X 21 content ingestion/receiving X X 22 content recording X X 23 content storage X X 24 content adaptation X 25 content acquisition 26 content validation 27 content distribution 28 content licencing 29 key management 30 content encryption X 31 user profile/data mng. X X X ETSI ETSI TS 182 027 V3.5.1 (2011-03) 159 Elementary function UE SSF SDF Core IMS SCF UPSF MCF MDF 32 accounting/right control X X X 33 status/state (changes) detection/reporting X X X X 34 common notification X X 35 messaging X X 36 presence X X 37 inter-destination media synchronization X X D.3 Mapping of elementary functions to IPTV services Mapping of elementary functions in table D.3 show which elementary function (listed in clause 5.1.4) are applicable for described IPTV services (described in TS 181 016 [15]). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 160 Table D.3: Mapping of elementary functions to IPTV services Elementary function BC CoD N-PVR C-PVR BCwTP UGC Push CoD Ad. CRS Notif. Msg Presen ce 1 network attachment x x x x x x x x x x x x 2 registration x x x x x x x x x x x x 3 resource management x x x x x x x 4 charging information x x x x x 5 service discovery x x x 6 service authorization x x x x x x x x x x x x 7 service selection x x x x x x 8 service initiation x x x x x x x x x x x x 9 service control x x x x x x x x x x x x 10 service information handling x x 11 service configuration x x x x x x x x x x x x 12 session initiation x x x x 13 session modification x x x x x x 14 session termination x x x x x x x x x 15 multicast based media delivery x x x x 16 unicast based media delivery x x x x x x 17 content download/ upload x x x 18 control of multicast streaming x x x x x x x 19 control of unicast streaming x x x x x x x 20 control of download/ upload x x x x x x x 21 content ingestion/receiving x x x x x x x 22 content recording x x x 23 content storage x x x x x 24 content adaptation x x x 25 content acquisition x x x x x x 26 content validation x x x x x 27 content distribution x x x x x x 28 content licencing x x x x x 29 key management x x x x x 30 content encryption x x x x x 31 user profile/data mng. x x x 32 accounting/right control x x x x x x x x x 33 status/state (changes) detection/reporting x x x x x x x x x 34 common notification x x x 35 messaging x x 36 presence x x 37 inter-destination media synchronization x x x x x ETSI ETSI TS 182 027 V3.5.1 (2011-03) 161 Annex E (informative): Implementation Examples for Targeted Advertising Annex E describes implemtation examples for the following options: • Advertising performed exclusively by TISPAN IPTV entities. Also referred to an "Internal Advertising" option. • Advertising performed by an external system based on SCTE, [i.12], [i.13] and [i.14]. Also referred to as an "SCTE-130 based External Advertising" option. • Advertising performed by an external system based on OMA. Also referred to as an "OMA MobAd based External Advertising" option. E.1 Internal Advertising Architecture Option This clause specifies the entities involved in the TISPAN-IPTV specific advertising architecture, the procecures and the interfaces involved between the TISPAN entities. E.1.1 Void E.1.2 Advertising architecture Refer to clause 5.1.1. E.1.3 Reference points Refer to clause 6. E.1.4 Procedures for targeted ad insertion (TAI) In internal option, the Ad Server described in clause 8.14 is instantiated to a logical SCF that is in charge of Ad service which is responsible for IPTV service status detection, ad content selection and subsequent ad service control. NOTE: In specialized implementation, the SCF in charge of Ad service (i.e. SCF2) can be co-located with the SCF in charge of BC, CoD or other IPTV services (i.e. SCF1). E.1.4.1 Signalling flows for TAI at UE side When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions may exist on the UE during the ad insertion time. Figure E.1 depicts the typical steps when UE is informed of targeted ad insertion indication. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 162 Figure E.1: signalling flows for UE performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and the related IPTV content is delivered to the UE. 2) The SCF2 detects the ongoing IPTV service state (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events, etc.) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) SCF2 selects targeted ad content for the user, which can be inserted to the specific content. The user profile (e.g. shopping habits, user preference) is used to help locating of appropriate ad content targeted to specific user or user group. 4) SCF2 sends UE the notification of ad insertion information, using procedures specified in clause 8.11.1. The ad insertion information includes the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. 5) UE initiates the session initiation or modification procedure for ad content acquisition and the selected ad content is delivered to the UE. During this step the procedures described in clauses 8.3.1 and 8.3.2 for BC session or 8.4.1 and 8.4.2 for CoD session applies, with SCF2 responsible for the Ad service control and MF responsible for Ad content control and delivery. NOTE: The session modification is only possible when the same SCF handles CoD and Ad sessions. 6) The UE performs the ad insertion, i.e. renders the ad content exclusively or in parallel with the ongoing IPTV content (e.g. in PiP). 7) When the ad insertion times up, the session for ad content is released as procedures described in clauses 8.3.3 or 8.4.3, and UE resumes the rendering of the IPTV content. E.1.4.2 Signalling flows for TAI at MF side When the ad insertion takes place at MF, the MF is informed of the ad insertion information from the SCF2 and performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure E.2 depicts the typical steps when MF is informed of the ad insertion information. UE Core IMS SCF1 SCF2 MF 1 Session initiation (clause 8) 2 IPTV service status detection 3 Ad content selection 5 Session initiation/modification for ad content (8.3.1/8.3.2/8.4.1/8.4.2) 6 Ad insertion 7 Session Release for ad content (8.3.3/8.4.3) 4 Notification for ad insertion (8.11.1) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 163 Figure E.2 signalling flows for MF performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and the related IPTV content is delivered to the UE. 2) The SCF2 detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) SCF2 selects targeted ad content for the user, which can be inserted to the specific IPTV content. The user profile (e.g. shopping habits, user preference, etc.) is used to help locating of appropriate ad content targeted to specific user. 4) SCF2 sends the ad insertion information to the MF which is responsible for IPTV content delivery and control. The information includes the selected ad content identifier(s) insertion time (begin time and/or length), and other information needed for ad insertion. Playlist information may be used as ad insertion information. NOTE: In the case of co-located entities, step 2 to 4 can be combined in step 1. 5) MF acquires the selected ad content and performs ad insertion, i.e. the selected ad content is delivered separately from the IPTV content or it is inserted as part of ongoing IPTV content. The MF may perform transcoding if the codec of ad content is not supported by the UE. The MF may perform session modification if needed (e.g; the ad content uses different network parameters, the stream is delivered separately, etc.). It is up to SCF preference/policy on how out-of-band insertion indicators work with the in-band insertion indicators, e.g. the in-band insertion indicator has precedence over the out-of-band indicator when both are present. 6) The ad content is provided to the UE during the ad insertion time. UE Core IMS SCF1 SCF2 2 IPTV service status detection 3 Ad content selection MF 1 Session initiation (clause 8) 4 Ad insertion indication 6. Ad content provision 5 Ad insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 164 E.2 SCTE-130 Based External Advertising Architecture Option This clause specifies the entities defined by SCTE-130, complete architecture for advertising, the procedures and necessary interfaces between TISPAN and SCTE-130 entities. E.2.1 SCTE-130 Definitions SCTE-130 has defined the following advertising entities in [i.12]: • Ad Decision Service (ADS): The Ad Decision Service determines how advertising content is combined with non-advertising (i.e. entertainment) content assets. The decisions made by an ADS may be straightforward (i.e. specific ad content placed at a specific time in a specific asset) or arbitrarily complex (based on subscriber data, advertising zone, etc.). • Ad Management Service (ADM): The Ad Management Service defines messages in support of ad insertion activities. The primary consumer of these messages is an ADS. The message interfaces exposed by an ADM allow for both preconfigured ad decisions as well as real-time fulfillment models. ADM detection of a placement opportunity is outside the scope of the specification. However, the ADM may be a service consumer of a POIS and/or a CIS in order to obtain such information. • Content Information Service (CIS): The Content Information Service manages metadata describing all the assets (both advertising assets and non-advertising assets) available to the other SCTE 130 logical services. The CIS provides query and notification interfaces to the other logical services. • Placement Opportunity Information Service (POIS): The Placement Opportunity Information Service (POIS) holds, maintains, or retains descriptions of placement opportunities. • Subscriber Information Service (SIS): The Subscriber Information Service manages the per-subscriber information relevant to ad placement decisions. The SIS provides mechanisms surrounding privacy issues. E.2.2 SCTE-130 based Advertising Architecture Figure E.3 shows the interfaces between the SCTE-130 advertising specific entities and the TISPAN IPTV architecture. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 165 Figure E.3: Interaction between TISPAN IMS-based IPTV architecture and SCTE-130 advert entities The SCF entity can be interconnected with the Ad Decision service by the ADx reference point to request for placement decision. POIS is an external entity. SIS may be either covered by SCF, by SCF and UPSF, or by a complete external entity. The MF entity can be interconnected with the Ad Decision service by the ADy reference point to request placement decisions. The UE entity can be interconnected with the Ad Decision Service by the ADz reference point to request placement decisions. A deployment can have SCF,MF and/or the UE contact Ad Decision Service and perform ad insertion depending on the type of placement opportinuties that are detected by that particular entity. The option of where the ADM functions exist is a deployment choice that is not mandated by SCTE-130. Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions IPTV Service Control Functions (SCF) Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions (MCF) IPTV Media Delivery Functions (MDF) Sh Ut y2 SDF Sh ISC Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions ADx ADy ADS POIS SIS ADM CIS SIS SIS ADM External SCTE-130 Advertising Sub-system ADz ADM ETSI ETSI TS 182 027 V3.5.1 (2011-03) 166 E.2.3 Reference points E.2.3.1 IPTV Service Control Functions (SCF) - SCTE-130 External Ad system (ADx) This reference point is used to exchange advertising related messages between SCF and an SCTE-130 external Advertising sub-system. ADx reference point sends and receives messages from/to the ADS, POIS and SIS entities and the TISPAN IPTV SCF and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The use of ADx between SCF and ADS conforms to SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the SCF and ADS and that is declared during the discovery and registration phases. E.2.3.2 IPTV Media Function (MF) - SCTE-130 External Ad system (ADy) This reference point is used to exchange advertising related messages between MF and an SCTE-130 external Advertising sub-system. ADy reference point should be used to send and receive messages from/to the ADS,POIS and SIS entites and the TISPAN IPTV MF and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The MF entity is interconnected with the Ad Decision service by the ADy reference point to made ad-selection and ad-placement requests for broadcast services. The use of ADy between MF and ADS conforms to SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the ADS and MF and that is declared during the discovery and registration phases. E.2.3.3 IPTV User Equipment (UE) - SCTE-130 External Ad system (ADz) This reference point is used to exchange advertising related messages between UE and an SCTE-130 external Advertising sub-system. ADz reference point should be used to send and receive messages from/to the ADS, POIS entities and the TISPAN UE and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The UE entity is interconnected with the Ad Decision service by the ADz reference point to made ad-selection and ad-placement requests. The use of ADz between UE and ADS conforms to a relevant subset of SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the ADS and UE and that is declared during the discovery and registration phases. E.2.4 Procedures for Targeted Ad Insertion (TAI) Several deployment scenarios are supported by SCTE-130. The call flows below depicts specific example scenarios in which either the MF or the UE is involved in service state detection. Other deployment scenarios can have the SCF only being involved or the MF, UE and /or SCF being involved, where each entity handle different events. NOTE: Due to the stateful nature on the service channel established by the registration messages as described in SCTE 130-3 [i.14], deployments should consider the scalability and load on the ADS while supporting this option. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 167 E.2.4.1 Signalling flows for UE performing TAI E.2.4.1.1 UE detects service state Figure E.4: Signalling flows for UE performing TAI(Case: UE detects service state) 1) In the discovery step, the AD server becomes aware of the existence of the ADM. This can be through manually configuration, or by dynamically subscribing to an entity that can report to the AD server that a UE is online. 2) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the UE. These actions of the external ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 3) Based on the current advertising campaign, the ad server (ADS) registers with a particular ADM, in this case the UE, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 4) An IPTV session is established between UE and SCF as described in clause 8, e.g. CoD session in clause 8.4.1.1, etc. and some IPTV content is delivered to the UE. 5) The service state of on-going IPTV session is detected on the UE (e.g. the current CoD content id, the BC channel Id, the trick-play events, etc.). 10. Placement Status notification/ Response UE SCF MF Ad Server 4. Session initiation (clause 8.3.1.1, 8.4.1.1, …) 8. Ad insertion 5. IPTV service state detection Core IMS 2. List ADM services 3. ADS Registration 6. Placement Opportunity Request/ Placement Decision Response 7. Session initiation/modification for fetching Ad content 9. Session termination/modification for Ad content 1 Discovery ETSI ETSI TS 182 027 V3.5.1 (2011-03) 168 6) The UE initiates a placement request to the Ad server and sends it the list of placement opportunities and other targeting information (service state of on-going session, user information, etc.) that allows the Ad Server to select the appropriate target ads. The Ad server responds with relevant placement/ad insertion information that can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. 7) In order to retrieve the ads, the UE may perform session modification procedure in case the MF for the target ads is the same MF from which the streaming of the actual content occurs. Alternatively, the UE may also initiate a separate session to MF that includes the target ad content. During this step the procedures described in clause 8.4.2 for CoD session applies. NOTE: Other means such as off-line mechanisms can be also used to deliver the target ads to the UE, which are out of scope of the present document. 8) The UE performs the ad insertion, i.e. renders the ad content embedded within the actual content or in parallel with the ongoing IPTV content (e.g. in PiP). 9) When the ad insertion time is up, the session for ad content is released, if one has been created, and UE resumes the rendering of the IPTV content. 10) A placement status message exchange takes place between the UE and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 169 E.2.4.1.2 MF detects service state Figure E.5: Signalling flows for UE performing TAI Note that the discovery procedure is not shown here: 1) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the MF. These actions of the external ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 2) Based on the current advertising campaign, the ad server (ADS) registers with a particular ADM, in this case the MF, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 3) An IPTV session is established between UE and SCF as described in clause 8, e.g. CoD session in clause 8.4.1.1 etc., and some IPTV content is delivered to the UE. 4) The service state of on-going IPTV session is detected on the MF (e.g. the commercial break of the program, the current CoD content id, the trick-play events, etc.). 5) The MF initiates a placement request/response exchange that allows the Ad Server to select the appropriate target ads which can be inserted in the currently streamed content. The ad insertion information can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. 10. Placement Status notification 5. Placement Request/Response 2. Registration 1. List ADM services UE Core IMS SCF Ad Server MF 3. Session initiation (clause 8) 4. IPTV service status detection 8. Session initiation/modification for ad content (8.3/8.4) 6a. Notification of ad insertion decision 6b. Notification for ad insertion (8.11.1) 7. AD 9. Session Release for ad content (8.3/8.4) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 170 6) The notification procedures specified in clause 8.11.1 are applied to deliver the ad insertion information to the UE. The ad insertion information can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. Other means for conveying the same information are also possible. 7) In order to retrieve the ads, the UE may perform session modification procedure in case the MF for the target ads is the same MF from which the streaming of the actual content occurs. Alternatively, the UE may also initiate a separate session to MF that includes the target ad content. During this step the procedures described in clause 8.4.2 for CoD session applies. NOTE: Other means such as off-line mechanisms can be also used to deliver the target ads to the UE, which are out of scope of the present document. 8) The UE performs the ad insertion, i.e. renders the ad content embedded within the actual content or in parallel with the ongoing IPTV content (e.g. in PiP). 9) When the ad insertion time is up, the session for ad content is released, if one has been created, and UE resumes the rendering of the IPTV content. 10) A placement status message exchange takes place between the MF and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 171 E.2.4.2 Signalling flows for MF performing TAI E.2.4.2.1 MF detects service state Figure E.6: Signalling flows for MF performing TAI Note that the discovery procedure is not shown here: 1) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the MF. These actions of the ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 2) Based on the current advertising campaign, the ADS registers with a particular ADM, in this case the MF, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 3) An IPTV session is established between UE and SCF (CoD) as described in clause 8, e.g. CoD session in clause 8.4.1.1, etc., and some IPTV content is delivered to the UE. 4) The service state of on-going IPTV session is detected on the MF (e.g. the commercial break of the program, the current CoD content id, the trick-play events, etc.). 2. Registration 1. List ADM services 5. Placement Request/Response 8. Placement Status notification UE Core IMS SCF Ad Server MF 3. Session initiation (clause 8) 6. Session initiation/modification for ad content (8.4) 7. Session Release for ad content (8.4) 4. IPTV service status detection ETSI ETSI TS 182 027 V3.5.1 (2011-03) 172 5) The MF initiates a placement/request response exchange that allows the Ad Server to select the appropriate target ads which can be inserted in the currently streamed content. The ad insertion information can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion.The means by which the MF acquires the ad content is outside scope. 6) The MF performs the ad insertion, i.e. insert the ad content to the on-going IPTV content or replace the default ad content. The MF may perform transcoding or initiate session modification if the network parameters (e.g. codec or bandwidth) of ad content are not supported by the UE. Optionally, the ad content may be delivered to the UE via a new session. 7) When the ad insertion time is up, the session for ad content is released, if one has been created, as procedures described in clause 8.4, and UE resumes the rendering of the IPTV content. 8) A placement status message exchange takes place between the MF and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. E.3 OMA MobAd Based External Architecture Option This clause specifies the OMA MobAd (Mobile Advertising) entities, complete architecture for advertising, the procedures and necessary interfaces between TISPAN and OMA MobAd entities [i.15] and [i.16]. E.3.1 OMA MobAd Definitions Ad Server: Network resident functions specified by the MobAd Enabler [i.16]. Ad Engine: Device resident functions specified by the MobAd Enabler [i.16]. Ad App: An application running on the Device which interacts with the Ad Engine in order to present Ad(s) to the user. SP App: An Ad enabled network Application that is executing within the Service Provider environment (e.g. MMSC or SP-portal) and interacts with the MobAd Enabler for providing Ads as part of its service (e.g. requesting Ads, providing metrics data). SP App is not one of the MobAd Enabler Entities on the Network, but an external actor which interacts with them. Contextualisation: Tailoring and matching an advertising campaign to User's Context. In practical terms, this can include statically or dynamically associating a given User context (e.g.: "around Marble Arch in London, after 6pm, if using a streaming-capable Device"), to a varying degree of detail, with an advertising campaign. The above can imply using any data known and/or assumed about the User Context, e.g. location, device capabilities, etc. Personalisation: Tailoring and matching an advertising campaign to a set of User(s)' characteristics, such as demographics, tastes, preferences, etc. In practical terms, this can include statically or dynamically allocating a group of users which are to be participants in a given campaign, based on targeting criteria associated with a campaign. It can imply using static and dynamic data known and/or assumed about the User, which may be distributed in e.g.: User Profile, subscriber profiles, preferences and similar. This process can be self-improving throughout the campaign. NOTE: In this annex OMA's usage of the term "interface" is followed for consistency, this may differs from the use in other TISPAN's specification. Figure E.7 shows the OMA MobAd 1.0 architecture [i.16]. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 173 Figure E.7: OMA MobAd Architecture Diagram OMA MobAd 1.0 has defined the following advertising entities in [i.16]: • Ad Server: The Ad Server is a MobAd enabler component resident in the network (outside the device) that performs actions grouped in the following high-level functions: - Ad selection function: select the most appropriate Ad(s)/Ad Campaign(s) primarily using: Contextualisation and Personalisation information, Ad Metadata and applicable MobAd Rules. - Ad delivery function: the delivery of Ad(s)/Ad Campaigns can be done via Pull, Push or Broadcast. - Ad Metrics handling function: collect and process Ad Metrics data. - User/service data management function: manage user's Personalisation and Contextualisation data, MobAd Rules, user groups, Ad Channels, etc. • Ad Engine: The Ad Engine (see clause E.4.1 Definitions) is a MobAd Enabler component resident on the device that performs actions grouped in the following high-level functions: - Ad acquisition and delivery function: the acquiring of Ad(s)/Ad Campaigns can be done via Pull, Push or Broadcast. - Ad selection function: select Ads from the cache. - Ad metrics handling function: augment Ad Metrics data received from Ad Apps and report it to the Ad Server. - User/service/device data handling function: gather and process user's Personalisation and Contextualisation data, monitor and process device static and/or dynamic status (e.g. device resource threshold) and apply MobAd Rules. • SP App (SP Application): The SP App is an external entity that requests and receives Ad(s)/Ad Campaign(s) from Ad Server, and embeds them in content that is provided to the user. SP App records Ad Metrics data related to the Ad(s) and reports Ad Metrics data to the Ad Server. Ad Server Ad Engine Ad App SP App MobAd-3 MobAd-2 MobAd-1 Delv-1 Legend: Mandatory Interface Optional Interface MobAd components Entities external to MobAd MobAd Enabler ETSI ETSI TS 182 027 V3.5.1 (2011-03) 174 • Ad App (Ad Application): The Ad App is an external entity running on the device that requests and receives Ad(s) from Ad Engine, and presents them to the user. Ad App also report Ad Metrics data to the Ad Engine. The interfaces defined in OMA MobAd 1.0 are: • MobAd-1 is an interface exposed by the Ad Engine to the Ad App. The Ad App uses this interface to request and obtain Ads and their associated Ads identifiers from the Ad Engine, as well as to report Ad Metrics data to the Ad Engine, accompanied by the associated Ads identifiers. • MobAd-2 is an interface exposed by the Ad Server to the SP App. The SP App uses this interface to request and obtain Ad(s), reference(s) to Ad(s), associated Ad(s) identifiers and possibly additional information (to be determined in the TS stage), as well as to report Ad Metrics data, accompanied by the associated Ad(s) identifier(s). • MobAd-3 is an interface exposed by the Ad Server to the Ad Engine. The Ad Engine uses this interface to request and obtain Ad(s), reference(s) to Ad(s), their associated Ad(s) identifier(s) and Ad Metadata from the Ad Server, as well as to report Ad Metrics data to the Ad Server, accompanied by the associated Ad(s) identifier(s). • Delv-1 is an optional interface exposed by the Ad Engine. The Ad Engine receives Ad(s) and/or Ad Metadata over this interface from the Ad Server via underlying push and/or broadcast delivery mechanisms. The Ad Server uses this interface to push either Ad(s) or notification that Ad(s) are available for retrieval. The Ad Server may also use this interface to provide service notification to the Ad Engine. E.3.2 OMA MobAd based Advertising Architecture Figure E.8 shows the interfaces between the OMA MobAd advertising specific entities and the TISPAN IPTV architecture. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 175 Figure E.8: Interaction between TISPAN IMS-based IPTV architecture and OMA MobAd entities The SCF/MCF entities can be considered as SP App in MobAd and are interconnected with the Ad Server by the MobAd-2 interface to request for placement decision. The UE is interconnected with the Ad Server by the MobAd-3 interface to request Ad in case of Ad pulling. E.3.3 Reference Points E.3.3.1 IPTV SCF/MCF - MobAd External Ad system (MobAd-2) This interface is used to exchange advertising related messages between SCF/MCF and a MobAd external Advertising sub-system. MobAd-2 interface should be used to exchange messages between the Ad Server and the TISPAN IPTV SCF/MCF. The use of MobAd-2 interface between SCF/MCF and Ad Server conforms to OMA MobAd AD [i.16]. Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions IPTV Service Control Functions (SCF) Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions (MCF) IPTV Media Delivery Functions (MDF) Sh Ut y2 SDF Sh ISC Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions MobAd-2 External OMA MobAd Advertising Sub-system MobAd-2 MobAd-3 Ad Engine SP App SP App Ad App Ad Server ETSI ETSI TS 182 027 V3.5.1 (2011-03) 176 E.3.3.2 IPTV UE - MobAd External Ad system (MobAd-3) This interface is used to exchange advertising related messages between UE and a MobAd external Advertising sub-system. MobAd-3 interface should be used to for the UE to request Ad from the Ad Server. The use of MobAd-3 interface between UE and Ad Server conforms to OMA MobAd AD [i.16]. E.3.4 Procedures for Targeted Ad Insertion (TAI) In OMA MobAd option, the Ad Server described in clause 8.14 is instantiated to the Ad Server (defined in OMA MobAd AD [i.16]) that is in charge of Ad service which is responsible for ad content selection and subsequent ad service control. The SCF and MF are instantiated to the SP App (defined in OMA MobAd AD [i.16]) which is a Service Provider Application system for ad request and ad response. E.3.4.1 Signalling Flows for TAI at UE side When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions may exist on the UE during the ad insertion time. Alternatively, the UE can request ad from Ad Server directly using the MobAd-3 interface, which is specified in OMA MobAd AD [i.16]. UE can have the ad content stored locally for the ad insertion at the UE side. And also, the Ad Server can send appropriate ads to the MCF or MF beforehand to facilitate the ad request from UE. These can be done by offline means and out of scope of the present document. Figure E.9 depicts the typical steps when UE is informed of targeted ad insertion indication. Figure E.9: signalling flows for UE performing TAI 1) Some IPTV session is established between UE and SCF as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and some IPTV content is delivered to the UE. UE Core IMS SCF Ad Server MF 1 Session initiation (clause 8) 2 IPTV service status detection 3b Ad content selection 5 Session initiation/modification for ad content (8.3.1/8.3.2/8.4.1/8.4.2) 7 Session Release for ad content (8.3.3/8.4.3) 4 Notification for ad insertion (8.11.1) 3a OMA MobAd Ad Request 3c OMA MobAd Ad Response 3d Send information to MF 6 Ad insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 177 2) The SCF detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events, etc.) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) The SCF sends a OMA MobAd Ad Request message to the target Ad Server for the user. The Ad Server acquires the contextualisation and personalisation data relavant to the user and selects the appropriate target ads. The ads on the Ad Server can be stored locally or come from external entities. The selected ads can be inserted in the currently streamed content. The Ad Server sends the OMA MobAd Ad Response message including the selected target ads information to the SCF. In step 3d, the SCF sends the target ad information and the ad insertion indication back to a selected MF. 4) SCF sends UE the notification of ad insertion indication, using procedures specified in clause 8.11.1. The ad insertion indication includes the selected ad content identifier, the user id, insertion time (begin time and/or length), and other information needed for ad insertion. 5) UE initiates the session initiation or modification procedure for ad content acquisition and the selected ad content is delivered to the UE. During this step the procedures described in clauses 8.3.1 and 8.3.2 for BC session or 8.4.1 and 8.4.2 for CoD session applies, with Ad Server responsible for the Ad service control and MF responsible for Ad content control and delivery. 6) The UE performs the ad insertion, i.e. renders the ad content exclusively or in parallel with the ongoing IPTV content (e.g. in PiP). 7) When the ad insertion times up, the session for ad content is released as procedures described in clauses 8.3.3 or 8.4.3, and UE resumes the rendering of the IPTV content. E.3.4.2 Signalling flows for TAI at MF side When the ad insertion takes place at MF, the MF is informed of the ad insertion indication from the SCF and performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure E.10 depicts the typical steps when MF is informed of the ad insertion indication. Figure E.10: signalling flows for MF performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and some IPTV content is delivered to the UE. UE Core IMS SCF 2 IPTV service status detection MF 1 Session initiation (clause 8) 5 Ad content provision 4 Ad insertion Ad Server 3a OMA MobAd Ad Request 3c OMA MobAd Ad Response 7. Ad content provision ETSI ETSI TS 182 027 V3.5.1 (2011-03) 178 2) The SCF detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) The SCF sends an OMA MobAd Ad rRequest message to the target Ad Server for the user. The Ad Server acquires the contextualisation and personalisation data relavant to the user and selects the appropriate target ads. The ads on the Ad Server can be stored locally or come from external entities. The selected ads can be inserted in the currently streamed content. The Ad Server sends the OMA MobAd Ad Response message including the selected target ad information to the SCF. In step 3d, the SCF sends the target ads informaion and the ad insertion indication back to a selected MF. 4) MF acquires and stores the selected ad content, and performs ad insertion, i.e. the selected ad content is delivered separately from the IPTV content or it is inserted as part of ongoing IPTV content. 5) The ad content is provided to the UE during the ad insertion time. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 179 Annex F (informative): Mapping between TISPAN entities and external architectures Clause F.1 describes a mapping of the functional entities defined by others Advertising standards with the TISPAN IPTV functional entities. F.1 Mapping between TISPAN entities and SCTE-130 entities This clause describes a mapping of the functional entities defined by SCTE with the TISPAN IPTV functional entities. Placement Opportunity Information Service (POIS) and Ad Decision Service (ADS) are considered out of scope of TISPAN architecture because placement opportunities providing and Advert placement decision are not defined as TISPAN entities tasks. Link between ADS and ADM is considered as a reference point in scope of TISPAN. Other modules can be mapped with current TISPAN entities as they cover TISPAN entities tasks. In table F.1, is presented entities defined in the SCTE-130 [i.12] to [i.14], their roles and concerned TISPAN entities. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 180 Table F.1 SCTE-130 entity name Role TISPAN Entity concerned TISPAN entity task covered POIS Provides placement opportunities Out of scope (external entity) - SIS Manage subscriber information relevant for Ad SCF/UPSF/External entity SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). CIS Manage assets metadata SCF SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). ADM Provides placement opportunities based on POIS and CIS information Defines messages for Ad insertion Activities SCF (for TAI) and MCF (for Broadcast) SCF tasks from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). Send ad insertion indication to MF. MCF tasks from clause 5.1.5.3: Handle ad insertion control of MDF, i.e. control the fetching of the ad content and synchronization between ad content and IPTV content, including accounting for delay or drift in broadcast TV schedules. ADS Decide ad placement relative to content based on ADM placement opportunities Out of scope (external entity) - ETSI ETSI TS 182 027 V3.5.1 (2011-03) 181 F.2 Mapping between TISPAN Entities and OMA MobAd Entities TISPAN entities can use the interfaces exposed by Ad Server and Ad Engine for advertising purposes. Modules can be mapped with current TISPAN entities as they cover TISPAN entities tasks. Table F.2 shows the presented entities defined in the OMA MobAd, their roles and concerned TISPAN entities. Table F.2 OMA MobAd entity name Role TISPAN Entity concerned TISPAN entity task covered Ad Server Ad selection, Ad delivery, Ad Metrics data handling, data management Out of scope Use the interface exposed by Ad Server Ad Engine Ad selection, Ad acquisition and delivery, Ad Metrics data handling, data managment UE UE task from 8.14: When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. SP App Request and receive Ad, insert Ads to the content, report Ad Metrics data SCF/MF SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). MDF task from clause 5.1.5.3: Recognize appropriate in-band /out-of-band Ad insertion indicators (eg-cue messages as defined in ITU-T Recommendation J.181 [i.18]), when present. These Ad insertion indicators define positions within the IPTV content where advertisement content can be inserted /replaced. This task may be done by coordination with an external advertising sub-system. Ad App Request and receive Ad, report Ad Metrics data UE UE task from clause 8.14: When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 182 Annex G (informative): Ad placement options This annex presents examples for implemented of Ad placement by existing mechanism from other SDOs. G.1 IPTV Ad placement: SCTE-130 option In SCTE-130 [i.14], four types of ad insertion opportunities exists: • Pre-roll (a placement opportunity preceding an entertainment asset). • Post-roll (a placement opportunity following the play out of an entertainment asset). • Interstitial (a placement opportunity occurring during the play out of an entertainment asset). • Pause (placement opportunity as a result of a subscriber pressing the pause button). They can be separated in two options: predetermined placement opportunities (Pre/Post roll and Interstitial) and unexpected placement opportunities (Pause). The predetermined option should be used for the following types of stored contents: BC, COD, N-PVR and UGC contents. The unexpected option could be used for all sorts of stored contents: BC with trick mode, COD, N-PVR, UGC, timeshift. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 183 Annex H (informative): Interconnection Models to support of Mobility Capabilities TISPAN IMS based IPTV can recognize at least the following basic scenarios for roaming and interconnection to home network (not need support all of them): a) pure data access remotely to IPTV SP/content provider; b) IMS interconnect to home IPTV provider (described in clause H.1); c) visited - home network roaming between IPTV providers (served only from home network); d) visited - home network roaming between IPTV providers (served from home and/or visited network). Scenario A: IMS based IPTV user accessing via remote data access to home IPTV SP Because the UE accessing home IPTV SP from remote network without IMS, the user uses some remote data IP connection (e.g. VPN or secure remote access) to connect UE to his home network. Over this connection can be transferred all media and signaling to the subscriber directly from his Home Network. Because such a connection should going over any IP network (also best effort) also without resource reservation mechanisms, no QoS can be really ensured. NOTE 1: This scenario is out of scope of the current release. Scenario B: IMS based IPTV roaming with visiting IMS provider without IMS based IPTV solution This scenario is the simplest one with using core IMS. User will use IPTV services provided from IPTV functional elements from his Home Network. The IMS elements of visited network perform just IMS roaming via network attachment and registration in visited network and forward all other request to home network and its IMS IPTV SP (e.g. registration, service discovery/selection, service initiation/modification/termination). Service selection information and media are delivered from Home network over interconnection. The quality of the IPTV service for the end customer should be same as in home network (when interconnection and visited network assure enough resources and QoS), but no reuse of local media delivery resources for the provider is possible (because in visited network have no IMS based IPTV platform). NOTE 2: This scenario is described in clause H.1. Scenario C: IMS based IPTV roaming with visiting IPTV Service Provider with TISPAN IMS-IPTV solution (only home served) Additionally to the previous scenario the following one expects the IMS based IPTV platform is available in Visited Network, however all content and services are delivered only from Home Network. This solution expect that delivery of the content, metadata and service discovery, selection and service initiation, modification and termination will be done from home network. Also it could be required from Home Network IMS based IPTV solution to provide transcoding and content adaptation to adapt media to parameters required for entering the Visited Network (or this could be done in edge of visited network). Scenario D: IMS based IPTV roaming with visiting IPTV Service Provider with IMS-IPTV solution (home and/or partially visited IPTV platform served) If there is an IPTV solution in Visited Network, possibly having similar content for CoD, BC, PVR service, it is useful and more efficient to use this local resources in visited network as deliver all content over interconnection. The content which is available in Visited Network is not needed to be transferred over an interconnection network and allocate interconnection bandwidth/resources. For this purpose both providers should agree on the same identification of content, sharing service discovery and selection information, content security, billing clearing, and for sure about all parameters required for roaming agreements (e.g. QoS, Service Level Agreement). Other IPTV services or content not available in offer of visited IMS IPTV SP are provided as in previous scenario by home network and by user home IPTV service provider. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 184 H.1 Interconnection model using IMS roaming to home IMS IPTV Figure H.1 illustrates the model of interconnection with the Visited Network within Core IMS involved. UE can request IPTV services in the Home Network by connecting to the Visited Network. Core IMS in the Visited Network can request resources from the RACS in the Visited Network through the interface Gq'. Core IMS in the Home Network can request resources from the RACS in the Home Network through the interface Gq'. UE can attach to the Visited Network through the interface e1 so that the NASS in the Visited Network can assign IP address for the UE and discovery the address of P-CSCF in the Visited Network. Core IMS in the Visited Network can transfer the IPTV service request from the UE through the interface Ic to the Core IMS in the Home Network through the connection of their own IBCF(Intermediate Breakout Control Function). UE can connect the SSF to select IPTV services through the interface Xa which is already defined. UE can connect to the IPTV SCF to configure parameters through the interface Ut which is already defined. Core IMS in both network connect to their own UPSF to get user profiles through their own interface Cx. Figure H.1 H.2 Signalling flows The clauses below explain the signalling flows of UE start-up procedures and CoD procedures when the UE is located in the Visited Network. In Broadcast procedures, N-PVR and other services, they are similar as CoD procedures. NOTE: Following procedure are indicative to show one possible way how should IMS roaming be handle between home and visited network. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 185 H.2.1 UE start-up procedures Figure H.2 1) Network Attachment In this step the UE attaches to the network. The procedures for network attachment are defined in ES 282 004 [3]. This step includes IP configuration, P-CSCF address discovery of Visited Network, etc. 2) IMS Registration in Visited Network In this step, the UE performs regular IMS Registration as defined in TS 182 006 [2]. 3) P-CSCF within Core IMS in Visited Network submits the registration request to the I-CSCF within the Core IMS in the Home Network. In this step, the UE performs regular IMS Registration as defined in TS 123 002 [i.8]. 4) Core IMS in the Visited Network return parameters (e.g. P-CSCF address of Home Network) to the UE. 5) The step is the same as step 3 to 4 in figure 9 of clause 8.2. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 186 H.2.2 CoD procedures Figure H.3 1) The UE initiates a dialogue to the CoD service and submit the request to the Core IMS in the Visited Network, similar to steps 3 to 5 in clause 8.4.1.1.1. 2) Core IMS in the Visited Network forwards the request to the Core IMS in the Home Network. 3) The session initiation request is routed by the Core IMS in the Home Network up to the SCF. 4) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to access the content, the SCF forwards the session initiation request to the selected MF. 5) Signalling procedures for establishment of a content control channel and optionally content delivery channels take place between the UE and the MF (see similar clause 8.4.1.2.1). 6 to 8) The steps are the same as step 7 to 10 not including step 8 of clause 8.4.1.1.1. 9) The Core IMS in the Home Network forwards this confirmation to the Core IMS in the Visited Network. 10) The P-CSCF within the Core IMS in the Visited Network interacts with the RACS in the Visited Network to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 11) The P-CSCF in the Visited Network forwards the dialogue confirmation to the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 187 After this point, UE may use the content control channel to request content to be streamed and the actual content will then be delivered to the UE. The content control channel will also be used to carry UE requests for controlling the streams, e.g. "pause", "fast forward", etc. NOTE: Resources reserve/commit between Core IMS and RACS in the home network is optional when selected MF in the visited network servers the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 188 Annex I (informative): IPTV Identifiers This annex provides an overview of generic IPTV identifiers used in the present document. I.1 IPTV content identifiers Table I.1 provides an overview over IPTV content identifiers. Table I.1: IPTV content identifiers IPTV Service IPTV content identifier Clause(s) Identifies … BC BCServiceId 7.4.1 … a BC channel BC ProgrammeId 7.4.1 … a BC programme CoD CoDId 7.4.1 … CoD PVR PVRContentId 7.4.1 …PVR content UGC UGC content id 8.9.2 … UGC Ad ad content id 8.14.1 … an advertisement clip PCh PCh id 8.10 … a personalized channel NOTE: In case of BC, the IPTV content identifier contains the BCServiceId, the ProgrammeId or both. Table I.2: Use of IPTV content identifiers by other IPTV services Other IPTV service/feature Clause(s) IPTV content identifier is used to identify content that is … BC N/A (only BC content) CoD N/A (only CoD content) PVR 7.1 … used by the UE to activate a PVR session related to the PVR content Time shift N/A … time-shifted Preview 8.7 … previewed Parental controlled - … parentally controlled UGC N/A (only UGC content) PCh 8.10 … concatenated into a personalised channel CR 8.13 … recommended by the CR service Ad 8.14.1.1 … subjected to ad insertion Sync 8.15 … synchronised Trick-play 8.16 8.20 … controlled through network-controlled trick play Push CoD N/A (only CoD content) Content upload/download 8.18 8.19 … up/downloaded SSC 8.21 … controlled together with other users PSC 8.22 … used to build a personalised service composition Content marker 7.5.2.5 8.23 … marked Remote UE 8.25 … remotely intiated and controlled Presence 9.1 … being watched, as published to other users and/or IPTV services ETSI ETSI TS 182 027 V3.5.1 (2011-03) 189 I.2 IPTV service type identifier Table I.3 provides an overview over IPTV service types that are identified by an IPTV service type identifier. Table I.3: IPTV service type identifiers IPTV Service Type Broadcast (BC) Broadcast with trick play Content on Demand (CoD) Personal Video Recorder (PVR) Network Personal Video Recorder (N-PVR) Consumer Personal Video Recorder (C-PVR) Time shift Preview Parental controlled (PC) User Generated Content (UGC) Personalised Channel (PCh) Content Recommendation (CR) Targeted Advertisement Insertion (TAI) Push Content on Demand Content upload/download Shared Service Control (SSC) Personalised Service Composition (PSC) Content marker (CM) Remote UE ETSI ETSI TS 182 027 V3.5.1 (2011-03) 190 Annex J (informative): Bibliography ETSI TS 126 237: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) based Packet Switch Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) User Service; Protocols (3GPP TS 26.237 Release 8)". ETSI ETSI TS 182 027 V3.5.1 (2011-03) 191 Annex K (informative): Change history Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 30-05-08 17bTD256r1 001 A Fixing Figure 34 in TS 182 027 for Release 3. Corresponds to 17bTD260 3.0.0 3.0.1 30-05-08 17bTD255r2 002 1 D 16 Editor's notes on Release 3, Guidance to contributors 3.0.0 3.0.1 06-06-08 17bTD195r3 003 1 B Notification procedures 3.0.0 3.0.1 02-07-08 18WTD074r2 004 F Corrections in step numbering 3.0.1 3.0.2 02-07-08 18WTD052r4 005 1 B WI2070 User generated content in IPTV architecture 3.0.1 3.0.2 02-07-08 18WTD070r3 006 B Modification of content distribution related description in clause 12 3.0.1 3.0.2 02-07-08 18WTD086r2 007 D Proposal for ToC of TS182 027 on value added services 3.0.1 3.0.2 02-07-08 18WTD138r3 008 B Service Control function for IPTV content recommendation service 3.0.1 3.0.2 02-07-08 18WTD139r2 009 B Include procedures for IPTV recommendation service 3.0.1 3.0.2 02-07-08 18WTD140r1 010 D Clarification of notification service 3.0.1 3.0.2 02-07-08 18WTD181r1 011 B Network-initiated CoD session 3.0.1 3.0.2 02-07-08 18WTD071r6 012 B Support Push CoD service in IMS-based IPTV Architecture 3.0.1 3.0.2 02-07-08 18WTD082r4 013 C Reselection of MDF 3.0.1 3.0.2 02-07-08 18WTD083r7 014 C Notification using media path 3.0.1 3.0.2 02-07-08 18WTD085r2 015 B Advertising functions in IPTV architecture 3.0.1 3.0.2 02-07-08 18WTD084r3 016 B User Profile for Parent Control 3.0.1 3.0.2 01-10-08 18bTD288r1 017 D WI2070 ToC Drafting: Changes to clauses 5 and 8 3.0.2 3.0.3 01-10-08 18bTD194r1 018 B Session Transfer procedure 3.0.2 3.0.3 01-10-08 18bTD257r1 019 A WI2070, adding references to stage 1 3.0.2 3.0.3 01-10-08 18bTD143r2 020 B Sharing Bookmarks Between Multiple IPTV Users 3.0.2 3.0.3 01-10-08 18bTD170r3 021 D Generic SCF and MF 3.0.2 3.0.3 01-10-08 18bTD169r2 022 D "CoD-based" UGC procedures 3.0.2 3.0.3 01-10-08 18bTD085r2 023 B UGC Functions in IPTV Architecture 3.0.2 3.0.3 01-10-08 18bTD080r3 024 B IPTV Advertising Service Procedures 3.0.2 3.0.3 01-10-08 18bTD076r2 025 B Procedure of CoD content preview 3.0.2 3.0.3 01-10-08 18bTD079r3 026 1 B Personalized Channel Functions 3.0.2 3.0.3 01-10-08 18bTD128r3 027 B Architectures for NGN Service Blending 3.0.2 3.0.3 01-10-08 18bTD131r3 028 B WI2070 Synchronization Architecture 3.0.2 3.0.3 01-10-08 18bTD196r2 029 A Correction of inconsistency of IPTV presence timer definition between stage 2 and 3 3.0.2 3.0.3 01-10-08 18bTD091r5 030 C Clarification of Push CoD service 3.0.2 3.0.3 01-10-08 18bTD224r4 031 B WI2070 messaging 3.0.2 3.0.3 01-10-08 18bTD130r3 032 B Network-controlled Trick Play 3.0.2 3.0.3 01-10-08 18bTD081r4 033 B Deliver Messages Associated with a BC Service Using Media Path 3.0.2 3.0.3 01-10-08 18bTD094r6 034 B Clarification of Network initiated service 3.0.2 3.0.3 01-10-08 18bTD095r4 035 B Procedures of Network initiated BC service 3.0.2 3.0.3 06-11-08 19WTD047r1 036 D Typo Correction Fig C1 3.0.2 3.0.4 06-11-08 19WTD192r2 037 B IPTV Elementary functions 3.0.2 3.0.4 06-11-08 19WTD179r1 038 B Addition of playlist generation task for SCF 3.0.2 3.0.4 06-11-08 19WTD093r2 039 B Functions and Procedures for CRS 3.0.2 3.0.4 06-11-08 19WTD175r2 040 F Cleaning up references [2] and [12] 3.0.2 3.0.4 06-11-08 19WTD140r2 041 F Advertising Procedures- Name Update 3.0.2 3.0.4 06-11-08 19WTD143r3 042 B Advertising Procedures- MCF Role 3.0.2 3.0.4 12-11-08 19WTD091r2 043 B Capability of SCF on event detection 3.0.2 3.0.4 12-11-08 19WTD092r3 044 B PVR procedures 3.0.2 3.0.4 12-11-08 19WTD094r3 045 B Procedures for PPV Service 3.0.2 3.0.4 12-11-08 19WTD050r2 046 B User Generated Content Session Coordination 3.0.2 3.0.4 12-11-08 19WTD051r2 047 B User Generated Content Procedures Coordination note 3.0.2 3.0.4 12-11-08 19WTD095r2 048 B Uploading of UGC Content Description 3.0.2 3.0.4 12-11-08 19WTD144r3 049 C Traditional Broadcast Advertising Procedures 3.0.2 3.0.4 12-11-08 19WTD111r2 050 F COD offset use 3.0.2 3.0.4 12-11-08 19WTD177r3 051 B IPTV Bookmark data model 3.0.2 3.0.4 12-11-08 19WTD142r7 052 C Advertising Procedures- MDF Role 3.0.2 3.0.4 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 192 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 12-11-08 19WTD149r1 053 F Alignment of terminology for the IMS-based IPTV procedures 3.0.2 3.0.4 14-11-08 CRs 17 to 53 TB approved at TISPAN#19 and clean-up by ETSI Secretariat 3.0.4 3.1.0 05-12-08 19bTD169r2 054 D WI2070 editorial fixes 3.1.0 3.1.2 05-12-08 19bTD164r1 055 A Deleting informative reference to IPTV stage 1 3.1.0 3.1.2 05-12-08 19bTD054r1 056 F Editorial change 3.1.0 3.1.2 05-12-08 19bTD117r1 057 B Personalized Stream Composition 3.1.0 3.1.2 05-12-08 19bTD184r2 058 C Targeted ad insertion clarification 3.1.0 3.1.2 05-12-08 19bTD125r4 059 B IPTV Service Access History Data Model 3.1.0 3.1.2 05-12-08 19bTD112r2 060 C Clarification of notification procedures 3.1.0 3.1.2 05-12-08 19bTD131r1 061 B Elementary functions mapping 3.1.0 3.1.2 05-12-08 19bTD180r1 062 A Multiple services packages in BC session initiation 3.1.0 3.1.2 05-12-08 19bTD185r1 063 F Clarification on User Profile configuration 3.1.0 3.1.2 05-12-08 19bTD086r3 064 B Modification of targeted advertising flows for CoD services 3.1.0 3.1.2 05-12-08 19bTD153r2 065 F Signalling flow at MF side 3.1.0 3.1.2 05-12-08 19bTD113r2 066 B Event Handling-Involving SCF 3.1.0 3.1.2 05-12-08 19bTD114r2 067 B IPTV Status Detection 3.1.0 3.1.2 05-12-08 19bTD059r3 068 B PCh Specific Information 3.1.0 3.1.2 05-12-08 19bTD087r3 069 B Addition of Signalling flows of playlist generation by SCF and playlist acquisition by MF from SCF 3.1.0 3.1.2 05-12-08 19bTD128r5 070 B Push CoD service procedures 3.1.0 3.1.2 05-12-08 19bTD182r1 071 F Obsolete use of BC MCF/SCF 3.1.0 3.1.2 05-12-08 19bTD218r2 072 D Editor notes for open issues 3.1.0 3.1.2 05-12-08 19bTD055r3 073 B Add Signalling Flows for CoD service action data update 3.1.0 3.1.2 05-12-08 19bTD061r3 074 B Generic Content Upload/Download Procedures 3.1.0 3.1.2 05-12-08 19bTD056r4 075 B Procedures for Restricted Trick Play 3.1.0 3.1.2 05-12-08 19bTD152r5 076 B Advert alignment SCTE 3.1.0 3.1.2 05-12-08 19bTD154r3 077 F Content recommendation attributes in user profile 3.1.0 3.1.2 05-12-08 19bTD130r4 078 B IPTV roaming in IMS-based IPTV Architecture 3.1.0 3.1.2 05-12-08 19bTD183r4 079 B Shared content procedures 3.1.0 3.1.2 05-12-08 19bTD212r5 080 C PPV- Adding required step to call flows in clause 8.3.8 3.1.0 3.1.2 05-12-08 19bTD181r2 081 C Alternative solution for PPV 3.1.0 3.1.2 05-12-08 19bTD193r4 082 D Clarification of CoD Session Transfer 3.1.0 3.1.2 05-12-08 19bTD129r7 083 C Modification of UGC procedures 3.1.0 3.1.2 05-12-08 19bTD060r3 084 B Personalized Channel Procedures 3.1.0 3.1.2 30-01-09 19tTD197r1 085 D Editor's note on relationship between Xc and BC tasks 3.1.2 3.1.3 30-01-09 19tTD078r3 086 C Clarification of UGC Creation Procedure 3.1.2 3.1.3 30-01-09 19tTD079r2 087 C Clarification of UGC Watching Procedure 3.1.2 3.1.3 30-01-09 19tTD080r4 088 B Procedure for Personal Service Composition 3.1.2 3.1.3 30-01-09 19tTD081r2 089 C Synchronization of Shared Content 3.1.2 3.1.3 30-01-09 19tTD082r2 090 B Synchronization Procedures 3.1.2 3.1.3 30-01-09 19tTD147r1 091 C Playlist parameters 3.1.2 3.1.3 30-01-09 19tTD202r2 092 D Cleanup of IPTV Bookmark Terminology 3.1.2 3.1.3 30-01-09 19tTD149r3 093 B Shared Service Control procedure 3.1.2 3.1.3 30-01-09 19tTD183r2 094 F Modification on procedures for shared content 3.1.2 3.1.3 30-01-09 19tTD101r1 095 F Modifications to Flows and Assumptions in Session Transfer 3.1.2 3.1.3 30-01-09 19tTD107r2 096 B Signalling Flows for IPTV Favourites procedures 3.1.2 3.1.3 30-01-09 19tTD185r3 097 B Reuse Media Channel for CoD Services 3.1.2 3.1.3 03-03-09 20WTD224r1 099 F Correcting figure 7 3.1.3 3.1.4 03-03-09 20WTD093r1 100 C Alignment of UGC watching with CoD procedures 3.1.3 3.1.4 03-03-09 20WTD223r1 102 D IPTV Content Marker cleanup 3.1.3 3.1.4 03-03-09 20WTD197r2 103 B Metadata exchange with SSF 3.1.3 3.1.4 03-03-09 20WTD072r1 104 B Support for Bypassing BGF in IPTV Flows 3.1.3 3.1.4 03-03-09 20WTD087r3 105 C PVR Content Update Procedure 3.1.3 3.1.4 03-03-09 20WTD125r2 106 F Resolve Editor's Notes for PVR service 3.1.3 3.1.4 03-03-09 20WTD076r2 107 B Unclear specification for notification on the media stream in conjunction with BC service 3.1.3 3.1.4 03-03-09 20WTD092r2 108 C IPTV service status 3.1.3 3.1.4 03-03-09 20WTD126r2 109 D Amendments on Advertising Related Clauses 3.1.3 3.1.4 03-03-09 20WTD122r4 110 B Preview Procedures for BC Service 3.1.3 3.1.4 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 193 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 03-03-09 20WTD288r3 111 B Add Procedures for Service Initiation by Remote UE 3.1.3 3.1.4 03-03-09 20WTD123r4 112 B Add Procedure for UGC Creation Session Initiated by Remote UE 3.1.3 3.1.4 03-03-09 20WTD128r3 113 B Delete Editor's Note: UGC Creation Procedures 3.1.3 3.1.4 03-03-09 20WTD074r2 114 B Incomplete specification on Personalized Channel service 3.1.3 3.1.4 03-03-09 20WTD127r6 115 B Content related Content Marker Retrieving Procedure 3.1.3 3.1.4 03-03-09 20WTD073r3 116 B Unclear Messaging Procedures 3.1.3 3.1.4 03-03-09 20WTD130r3 117 B PPV User Profile Definition 3.1.3 3.1.4 03-03-09 20WTD086r3 118 C SSC procedures clarifications 3.1.3 3.1.4 10-03-09 CRs 54 to 118 (except 98) TB approved at TISPAN#20 3.1.4 3.2.0 25-03-09 20bTD207r1 119 D Fixing figure 8B 3.2.0 3.2.1 25-03-09 20bTD120r1 120 B Clarification on UGC Creation Session 3.2.0 3.2.1 25-03-09 20bTD119r1 121 F Delete Push CoD procedures in Annex B 3.2.0 3.2.1 25-03-09 20bTD230r2 122 B Procedures for Shared Service Control 3.2.0 3.2.1 25-03-09 20bTD280r1 123 B IPTV interconnection types 3.2.0 3.2.1 25-03-09 20bTD065r2 124 F Correction on PVR Off-line Capture Request Procedures 3.2.0 3.2.1 25-03-09 20bTD067r2 125 B C-PVR User Profile Definition 3.2.0 3.2.1 25-03-09 20bTD244r3 126 B IPTV_SCF-initiated UGC Watching 3.2.0 3.2.1 25-03-09 20bTD061r4 127 B Personalized Channel Service Procedure 3.2.0 3.2.1 25-03-09 20bTD062r2 128 B Clarification on Notification through Media Path 3.2.0 3.2.1 25-03-09 20bTD241r2 129 B Synchronisation with SC in Transport 3.2.0 3.2.1 25-03-09 20bTD246r2 130 B Synchronization and Transcoding 3.2.0 3.2.1 25-03-09 20bTD323r1 131 B Note on Synchronisation 3.2.0 3.2.1 25-03-09 20bTD334r1 132 B Proposal for revised Annex E 3.2.0 3.2.1 25-03-09 20bTD273r3 133 B OMA MobAd Advertising Architecture Option 3.2.0 3.2.1 25-03-09 20bTD066r4 134 B C-PVR SAD data model definition 3.2.0 3.2.1 25-03-09 20bTD063r4 135 B Publication of UGC Content Description 3.2.0 3.2.1 25-03-09 20bTD069r2 136 B Push CoD procedure resues SCF initiated unicast content download procedure 3.2.0 3.2.1 25-03-09 20bTD064r3 137 B Clarification on UE-initiated Unicast Content Upload/Download 3.2.0 3.2.1 25-03-09 20bTD068r3 138 D Message Transfer on Media Path 3.2.0 3.2.1 25-03-09 20bTD239r4 139 B IPTV Service Identifier 3.2.0 3.2.1 25-03-09 20bTD026r8 140 B Alignment of Session Transfer Call Flows with stage 1 3.2.0 3.2.1 25-03-09 20bTD109r4 142 B Usage of presence for IPTV services 3.2.0 3.2.1 25-03-09 20bTD112r4 143 B integration with 3GPP PSS or MBMS 3.2.0 3.2.1 06-04-09 20bTD028r7 141 B Modifications to Targeted Advertisement section 8.14 and Annex F 3.2.0 3.2.2 07-05-09 WG2-07-060r1 144 B TAI Procedures using OMA MobAd 3.2.2 3.2.3 07-05-09 WG2-07-026r1 145 A Clarification on playlist for content distributed over multiple MF 3.2.2 3.2.3 07-05-09 WG2-07-027r2 146 B Data model for playlist 3.2.2 3.2.3 07-05-09 WG2-07-021r1 147 B Synchronisation Tasks 3.2.2 3.2.3 07-05-09 WG2-07-032r1 148 C SCF-MF interaction 3.2.2 3.2.3 07-05-09 WG2-07-033r1 149 C UGC removal 3.2.2 3.2.3 07-05-09 WG2-07-030r1 150 C Content markers clarification 3.2.2 3.2.3 07-05-09 WG2-07-058r1 151 F Correction on PVR Impulsive Capture Request Procedures 3.2.2 3.2.3 07-05-09 WG2-07-049r1 152 B Update of annex D 3.2.2 3.2.3 07-05-09 WG2-07-061r2 153 F CoD Preview Procedure 3.2.2 3.2.3 07-05-09 WG2-07-013r4 154 B IPTV service state revisited 3.2.2 3.2.3 07-05-09 WG2-07-056r3 155 F Correction on PVR SAD model 3.2.2 3.2.3 07-05-09 WG2-07-057r3 156 B Add PVR Type attribute to IPTV SAD structure 3.2.2 3.2.3 07-05-09 WG2-07-011r1 157 D Editorial Cleanup 3.2.2 3.2.3 07-05-09 WG2-07-068r1 158 D Editorial fixes on SAD and CR history 3.2.2 3.2.3 07-05-09 WG2-07-051r4 159 F Correction on Generic TAI Procedures 3.2.2 3.2.3 07-05-09 WG2-07-052r4 160 B IPTV Ad Service Procedures 3.2.2 3.2.3 07-05-09 WG2-07-019r2 161 B Pre-selection of User Generated Content 3.2.2 3.2.3 07-05-09 WG2-070-035r3 162 B Network initiated content marking 3.2.2 3.2.3 07-05-09 WG2-070-036r1 163 B Optional support for UE sending offset to the network in Session transfer 3.2.2 3.2.3 07-05-09 WG2-07-029r4 164 B Modification of N-PVR capture procedures 3.2.2 3.2.3 07-05-09 WG2-07-023r2 165 B Personalised Service Composition 3.2.2 3.2.3 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 194 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 07-05-09 WG2-07-010r2 166 B IPTV Content Identifier 3.2.2 3.2.3 07-05-09 WG2-07-017r2 167 B Resolving SSC issues 3.2.2 3.2.3 07-05-09 WG2-07-028r4 168 B Modification of mappings with IMS based IPTV 3.2.2 3.2.3 07-05-09 WG2-07-031r4 169 C Parental control clarifications 3.2.2 3.2.3 07-05-09 WG2-07-047r3 170 B IPTV services R2/R3, M/O 3.2.2 3.2.3 07-05-09 WG2-07-048r2 171 B Emergency alert 3.2.2 3.2.3 07-05-09 WG2-07-054r3 172 B UE-utilized PCh 3.2.2 3.2.3 07-05-09 WG2-07-055r2 173 B CRS Data Model and Procedure 3.2.2 3.2.3 07-05-09 WG2-07-072r5 174 B SSF-SCF Reference Point 3.2.2 3.2.3 07-05-09 WG2-07-059r3 175 B UGC Specific Information 3.2.2 3.2.3 07-05-09 WG2-07-034r5 176 B Incoming call management 3.2.2 3.2.3 07-05-09 WG2-07-014r4 177 B MAD and SAD 3.2.2 3.2.3 18-06-09 21WTD207r2 178 D Editors Note For Service Access History 3.2.5 3.2.6 18-06-09 21WTD144r4 179 B SCTE 130TAI arch and references 3.2.5 3.2.6 18-06-09 21WTD153r2 180 B SCTE 130TAI procedures 3.2.5 3.2.6 18-06-09 21WTD122r2 181 F Editors Notes on User Generated Content 3.2.5 3.2.6 18-06-09 21WTD123r1 182 B Editors Note on Service State 3.2.5 3.2.6 18-06-09 21WTD124r2 183 B Editors Note on N-PVR and Unicast 3.2.5 3.2.6 18-06-09 21WTD125r2 184 B Editors Note on SCF Event Handling 3.2.5 3.2.6 18-06-09 21WTD126r2 185 B Editors Note Content Ingres and Transcoding 3.2.5 3.2.6 18-06-09 21WTD127r3 186 B Definition Service Action Data 3.2.5 3.2.6 18-06-09 21WTD128r4 187 B Clarification of Mandatory and Optional 3.2.5 3.2.6 18-06-09 21WTD130r3 188 B Synchronisation Identifier 3.2.5 3.2.6 18-06-09 21WTD133r2 189 B IPTV Service State Data correction 3.2.5 3.2.6 18-06-09 21WTD134r2 190 B IPTV Service State Data usage 3.2.5 3.2.6 18-06-09 21WTD135r4 191 C IPTV Shared Service Control Policies 3.2.5 3.2.6 18-06-09 21WTD136r3 192 C Incoming Call Management 3.2.5 3.2.6 18-06-09 21WTD083r4 193 D SIP related Procedure Editor note removal 3.2.5 3.2.6 19-06-09 21WTD155r3 194 B Editor notes in Session Transfer 3.2.5 3.2.6 19-06-09 21WTD208r4 195 D Usage Of PCh Control Message 3.2.5 3.2.6 19-06-09 21WTD233r1 196 D List of Services 3.2.5 3.2.6 19-06-09 21WTD265r2 197 C IPTV Charging 3.2.5 3.2.6 19-06-09 21WTD266r2 198 C Note access to user data 3.2.5 3.2.6 19-06-09 21WTD283r1 199 F Correction on C-PVR SAD Data Model 3.2.5 3.2.6 19-06-09 21WTD050r4 200 B IPTV Security 3.2.5 3.2.6 19-06-09 21WTD143r3 201 B General TAI UE based 3.2.5 3.2.6 19-06-09 21WTD154r2 202 B Editor notes in TAI generic procedure 3.2.5 3.2.6 19-06-09 21WTD253r2 203 D Issue 3 editors note on privacy issues 3.2.5 3.2.6 19-06-09 21WTD236r1 204 D Deletion of Annex ZZY 3.2.5 3.2.6 19-06-09 21WTD303r1 205 C Note metadata synchronization 3.2.5 3.2.6 19-06-09 21WTD309r1 206 C Resolving SSC editor notes 3.2.5 3.2.6 19-06-09 21WTD311r1 207 C Resolving Presence editor notes 3.2.5 3.2.6 18-06-09 21WTD232r2 209 D Editor's notes cleanup 3.2.5 3.2.6 18-06-09 21WTD183r3 210 F Mandatory versus optional services 3.2.5 3.2.6 CRs 119 to 207 and 209, 210 approved at TISPAN#21 3.2.6 3.3.0 26-08-09 21bTD070r1 211 F Figure 21 Call Flow Correction 3.3.0 3.3.1 26-08-09 21bTD145r1 212 F CoD Call Flow Description Correction 3.3.0 3.3.1 01-10-09 22WTD035r2 213 B Synchronisation Clients in the Transport networks 3.3.1 3.3.3 01-10-09 22WTD210r3 214 C IMS IPTV Draft 3.3.1 3.3.3 Publication 3.3.3 3.3.4 Input draft 3.3.4 3.4.0 05-02-10 02(10)0008r3 215 C Functional_Modification_of_Sync_Architecture 3.4.0 3.4.1 14-04-10 02(10)0042r1 216 C Editorial_Corrections 3.4.0 3.4.1 15-09-10 02(10)157r1 217 D Term consistency on service discovery information 3.4.1 3.4.2 update of CR numbers and work item reference 3.4.2 3.4.3 publication 3.4.3 3.5.1 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 195 History Document history V2.0.0 February 2008 Publication V2.4.1 July 2009 Publication V3.4.1 January 2010 Publication V3.5.1 March 2011 Publication
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
1 Scope
|
The present document defines a profile of the Gateway Control Protocol (H.248.1) to be used for controlling Border Gateway Functions (BGF), as defined in ES 282 003 [3].
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T Recommendation H.248.1 (2005): "Gateway control protocol: Version 3" including its Amendment 1 (2008) "Corrections and clarifications". [2] Void. [3] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [4] ITU-T Recommendation H.248.45 (2006): "Gateway control protocol: MGC information package". [5] ITU-T Recommendation H.460.18 (2005): "Traversal of H.323 signalling across network address translators and firewalls". [6] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". [7] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". [8] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations". [9] ITU-T Recommendation H.248.37 (2008): "Gateway control protocol: IP NAPT traversal package". [10] ITU-T Recommendation H.248.54 (2007): "Gateway control protocol: MPLS support package". [11] ITU-T Recommendation H.248.56 (2007): "Gateway control protocol: Packages for virtual private network support". Inclusive Corrigendum 1 (2009) "VLAN package clarifications". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 10 [12] ITU-T Recommendation H.248.40 (2007): "Gateway Control Protocol: Application Data Inactivity Detection Package". [13] ITU-T Recommendation H.248.14 (2009): "Gateway control protocol: Inactivity timer package". [14] ITU-T Recommendation Q.3303.2 (2007): "Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw Interface): H.248 Alternative". [15] ITU-T Recommendation H.248.11 (2002): "Gateway control protocol: Media gateway overload control package". Inclusive Corrigendum 1 (2008) "Clarifying MG-overload event relationship with ADD commands". [16] ITU-T Recommendation H.248.41 (2006): "Gateway control protocol: IP domain connection package" including its Amendment 1 (2008) "IP Realm Availability Package". [17] ITU-T Recommendation H.248.52 (2008): "Gateway control protocol: QoS Support packages" including its Amendment 1 (2009) "Clarifications and updates to the differentiated services package". [18] ITU-T Recommendation H.248.43 (2008): "Gateway control protocol: Packages for gate management and gate control". [19] ITU-T Recommendation H.248.53 (2009): "Gateway control protocol: Traffic management packages". [20] Void. [21] Void. [22] ETSI ES 283 018 (V1.1.4): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". [23] ITU-T Recommendation H.248.49 (2007): "Gateway control protocol: Session description protocol RFC and capabilities packages". [24] ITU-T Recommendation H.248.36 (2005): "Gateway control protocol: Hanging Termination Detection package". [25] ITU-T Recommendation H.248.47 (2008): "Gateway control protocol: Statistic conditional reporting package". [26] Void. [27] Void. [28] IETF RFC 4566: "SDP: Session Description Protocol". [29] IETF RFC 1123: "Requirements for Internet Hosts - Application and Support". [30] ITU-T Recommendation H.248.8: "Gateway control protocol: Error code and service change reason description". [31] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". [32] ETSI ES 283 018 (V2.7.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 11 [33] ITU-T H.Imp248.1 Version 2 (2008): "Implementors' Guide for Recommendation H.248.1 Version 2 (Media Gateway Control Protocol) and its Corrigendum 1 (03/2004)". NOTE: Available at: http://www.itu.int/rec/T-REC-H.Imp248.1-200805-I/en. [34] ITU-T Recommendation H.248.58 (2008): "Gateway control protocol: Packages for application level H.248 statistics". [35] Void. [36] IETF RFC 4975 (2007): "The Message Session Relay Protocol (MSRP)". [37] ETSI TS 187 003 (V1.7.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [38] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control".
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 102 333: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Gate control protocol". [i.2] ETSI TS 183 025: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction". [i.3] IETF RFC 2327: "SDP: Session Description Protocol". [i.4] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [i.5] ITU-T Recommendation V.152: "Procedures for supporting voice-band data over IP networks". Inclusive Corrigendum 1 (09/2005) and Corrigendum 2 (05/2006). [i.6] IETF RFC 4301: "Security Architecture for the Internet Protocol". [i.7] ITU-T Recommendation H.248.18: "Gateway control protocol: Package for support of multiple profiles". [i.8] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [i.9] IEEE 802.3: "Ethernet Working Group". [i.10] ITU-T Recommendation Y.1221 (2002): "Traffic control and congestion control in IP based networks". Inclusive a) Amendment 1 (2004): 'Extensions to transfer capabilities', b) Amendment 2 (11/2005): 'Further extension to transfer capabilities ', c) Amendment 3 (10/2007): "New Appendix IV - Example methods for determining token-bucket parameters". [i.11] ITU-T Recommendation Y.1541 (2006): "Network performance objectives for IP-based services". [i.12] ETSI TS 181 005: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements". [i.13] Void. [i.14] Void. [i.15] Void. [i.16] Void. [i.17] Void. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 12 [i.18] ETSI TR 183 068 (V0.0.4): "Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Guidelines on using Ia H.248 profile for control of Border Gateway Functions (BGF); Border Gateway Guidelines". [i.19] ITU-T Recommendation H.248.57 (2008): "Gateway Control Protocol: RTP Control Protocol Package". [i.20] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". [i.21] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)". [i.22] ETSI TR 183 025: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction".
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
3 Definitions and abbreviations
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: address: term used for "network address" (a.k.a. IP address) Border Gateway Function (BGF): packet-to-packet gateway for user plane media traffic NOTE 1: The BGF performs both policy enforcement functions and NA(P)T functions under the control of the SPDF. NOTE 2: A Border Gateway Function (BGF) provides the interface between two IP-transport domains. It may reside at the boundary between an access network and a core network or between two core networks, as defined in ES 282 001 [i.4]. The BGF has the "H.248 MG" role in the scope of this Profile. gate: represents a transport plane function enabling or disabling the unidirectional forwarding of IP packets under specified conditions (e.g. QoS) NOTE: See TS 102 333 [i.1]. IP-to-IP interworking modes: available SDP information elements and values in the signalled SDP "media description" (mainly "m=" and "a=" lines) by the SPDF (MGC), may be used to categorize following interworking modes from BGF (MG) perspective (see also annex G in [i.18]): (1) "Media-agnostic": - the "m=" line values of media type (<media>) and media format (<fmt>) are not allowing to conclude for the BGF (MG) on the transported "media" information; (2) "Media-aware": - the "m=" line values of media type (<media>), transport protocol (<proto>) and media format (<fmt>) are unambiguously defining the entire protocol stack of the H.248 IP termination, i.e. the BGF (MG) knows transported "media" information and the underlying transport protocol type; (3) "Transport protocol-agnostic" (or briefly "transport-agnostic"): - the BGF (MG) may not conclude from signalled SDP information elements on the transported IP payload information (see note); (4) "Transport protocol-aware" (or briefly "transport-aware"): - the value of the IP protocol field is indicated by the signalled SDP information elements, e.g. by the "m=" line value of the transport protocol (<proto>) field. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 13 NOTE: The BGF (MG) could principally derive the used transport protocol by analyzing the protocol field (http://www.iana.org/assignments/protocol-numbers) in the IP header, but such a function is beyond H.248. The BGF (MG) is still transport protocol-agnostic from H.248 point of view. pinhole: configuration of two associated H.248 IP Terminations within the same H.248 Context, which allows/prohibits unidirectional forwarding of IP packets under specified conditions NOTE 1: A pinhole may also be referred to as a "gate". NOTE 2: E.g. address tuple. NOTE 3: See ITU-T Recommendation H.248.37 [9]. NOTE 4: See annex A in TR 183 068 [i.18]. NOTE 5: It has to be noted that there is also a different definition for "pinhole", which is used in the context of H.323 systems (see ITU-T Recommendation H.460.18 [5]). The difference is the fact that the "H.248 pinhole" and "gate" are unidirectional, whereas the "H.323 pinhole" is bidirectional. port: term used for "transport port" (a.k.a. L4 port) Resource and Admission Control Subsystem (RACS): provides admission control and gate control functionalities NOTE: Including the control of NAPT and priority marking. Service Policy Decision Function (SPDF): logical policy decision element for Service Based Policy control (SBP) NOTE: The SPDF makes policy decisions using policy rules for Service Based Policy control (SBP). The SPDF has the "H.248 MGC" role in the scope of this Profile. transcoding: translation from one type of encoded media format to another different media format EXAMPLE 1: G.711 A-law to μ-law or vice versa. EXAMPLE 2: G.711 to G.726-40K. EXAMPLE 3: G.729 to AMR with 4.75 rate. EXAMPLE 4: G.711 to a broadband codec that operates at 256 kbps, etc. NOTE 1: The definition of "transcoding" is according to clause 3.10/ITU-T Recommendation V.152 [i.5]. NOTE 2: Transcoding belongs to the category of "media aware" IP-to-IP interworking (see above). transport address: combination of an Address and a Port
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AC Admission Control AF Application Function B2BIH Back-to-Back IP Host (mode) B2BRE Back-to-Back RTP Endsystem (mode) BGF Border Gateway Function BGW Border GateWay C-BGF Core-BGF CBR Constant BitRate CNAME Canonical End-Point Identifier CoAC Context Admission Control DA Destination Address DP Destination Port DSCP Differentiated Services Code Point GCP Gate Control Protocol ETSI ETSI TS 183 018 V3.5.2 (2010-01) 14 HR High Resolution (Report) HW HardWare IBCF Interconnect Border Control Function I-BGF Interconnect-BGF ICMP Internet Control Message Protocol IMS IP Multimedia Subsystem IP Internet Protocol IPR IP Router (mode) IPsec IP Security (RFC 4301 [i.6]) LD Local Descriptor (H.248 protocol element) Local Destination (H.248 naming convention) LS Local Source (H.248 naming convention) MG Media Gateway MGC Media Gateway Controller MID Message IDentifier (H.248) MP Measuring Points MPLS Multi Protocol Label Switching NA Not Applicable NAPT Network Address and Port Translation NAPT-PT NAPT and Protocol Translation NAT Network Address Translation NGN Next Generation Network PCI Protocol Control Information PHB Per-Hop Behaviour QoS Quality of Service RACS Resource and Admission Control Subsystem RD Remote Descriptor (H.248 protocol element) Remote Destination (H.248 naming convention) RFC Request For Comments (IETF) RP Reporting Points RS Remote Source (H.248 naming convention) RTCP RTP Control Protocol RTP Real-time Transport Protocol RTSP Real Time Streaming Protocol SA Source Address SAF Source Address Filtering SAM Source Address Mask SBP Service Based Policy control SCTP Stream Control Transport Protocol SDES Source Description SDP Session Description Protocol SIP Session Initiation Protocol SP Source Port SPDF Service Policy Decision Function SPF Source Port Filtering SPR (Remote) Source Port SPRR (Remote) Source Port Range SRTP Secure Real-time Transport Protocol SSRC Synchronization Source (Identifier StAC Stream Admission Control TCP Transmission Control Protocol THF Topology Hiding Function THIG Topology Hiding Interconnection Gateway TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking Tman Traffic Management UDP User Datagram Protocol VBR Variable BitRate VLAN Virtual LAN VPN Virtual Private Network XR eXtension Reports ETSI ETSI TS 183 018 V3.5.2 (2010-01) 15
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
4 Applicability
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
4.1 Architecture
|
The present document defines an H.248 Profile for the reference point between the Service Policy Decision Function (SPDF) and the Border Gateway Function (BGF), known as the Ia reference point. The SPDF interacts with the BGF to request services. This reference point is used for communication between the SPDF and a Core Border Gateway Function (C-BGF) and between the SPDF and an Interconnect Border Gateway Function (I-BGF). Specific requirements for this reference point are described in ES 282 003 [3]. Figure 1 illustrates the architecture assumed in the present document. SPDF IP Transport Network (Core) IP Transport Network (Access/Core) Scope of the present document BGF AF Figure 1: Reference architecture The names 'BGF' and 'SPDF' are terminology of the RACS functional architecture (stage 2). The SPDF role in this protocol (stage 3) specification is provided by the H.248 MGC entity and the BGF role by the H.248 MG entity. The associated stage 2 and stage 3 names are used synonymously in this H.248 profile specification.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
4.2 Border Gateway Guidelines
|
Guidelines for usage and implementation of border gateways are described in [i.18].
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5 Profile description
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.1 Profile identification
|
Table 1: Profile identification Profile name: ETSI_BGF Version: 3 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 16
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.2 Summary
|
This profile supports the control of the following functionality in IP-to-IP Media Gateways: • opening and closing gates (i.e. packets filtering depending on "IP address/port"); • allocation and translation of IP addresses and port numbers (NAPT): - IP realm/domain indication (via H.248.41 amendment 1); - RTCP handling; • interworking between IPv4 and IPv6 networks (NAPT-PT); • topology hiding; • hosted NAT traversal; • packet marking for outgoing traffic; • resource allocation and bandwidth reservation: - one and two-stage BGF resource reservation; • policing of incoming traffic; • QoS and usage metering: - conditional statistics reporting; • transcoding; • detection of inactive bearer connections; • specific call-independent procedures: - detection of hanging H.248 terminations; and • BGF overload control (at H.248 interface).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.3 Gateway Control Protocol Version
|
ITU-T Recommendation H.248.1 [1] Version 3. NOTE: Version 3 of the H.248 protocol is needed, due to the possible usage of stream statistics.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.4 Connection model
|
Table 2: Connection model Maximum number of contexts: Provisioned Maximum number of terminations per context: 2 Allowed terminations type combinations: (IP,IP) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 17
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.5 Context attributes
|
Table 3: Context attributes Context attribute Supported Values supported Topology No Not Applicable Priority Indicator Yes 0 to15 Emergency Indicator Yes ON/OFF IEPS Indicator No Not Applicable ContextAttribute Descriptor No Not Applicable ContextIdList Parameter No Not Applicable AND/OR Context Attribute No Not Applicable
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6 Terminations
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6.1 Termination names
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6.1.1 IP Termination
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6.1.1.1 Overview and prose specification
|
The Termination ID structure shall follow the guidelines of H.248 and shall be based on four fields: • "ip/<group>/<interface>/<id>". The individual fields are described and defined in table 4. Table 4: IP Termination Fields Name Description Values CHOOSE Wildcard ALL Wildcard ip "ip" is a fixed prefix identifying the termination. "ip" No No group Group of Interface and Id. Integer (0 to 65 535) (see note 6) No Yes interface Logical or physical interface to a network to/from which the termination will be sending/receiving media. (See notes 1 and 2). String of max 51 alphanumeric characters Yes (see note 5) Yes id Termination specific identifier (See note 3). Non-zero 32 bit integer Yes (see note 4) Yes NOTE 1: A specific <Interface> may be used together with different groups. NOTE 2: The generic field <Interface> may relate specifically to an "IP interface", "protocol layer 2 interface" or others. NOTE 3: The combination of Interface and Id is unique. NOTE 4: In version 1 of this profile, there was a tacit assumption that the MGC used a CHOOSE wildcard in an ADD request command. In this version, the MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". See also clause 5.6.1.1.1.3. NOTE 5: The MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". NOTE 6: The actual used range of Group ID is fully under MGC control. NOTE: The SPDF has the ability to choose the address space in which the BGF will allocate an IP address for the termination by using the ipdc/realm property defined in the H.248.41 IP domain connection package. H.248 wildcarding may be applied on IP Termination Identifiers. Wildcarding is limited according the two columns on the right hand side. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 18 5.6.1.1.1.1 Combined usage of fields Group and Interface There are two potential relationships between <group> and <interface> within the TerminationID structure: • strictly hierarchical: a single "interface" is completely associated to a dedicated "group". EXAMPLE 1: May be driven for instance by hardware architecture or addressing schemes with the goal of minimizing ServiceChange command load by using wildcards such as ip/<group>/* for potential HW failures that may lead to issuing a single ServiceChange command rather than multiple ServiceChange commands. • partially hierarchical: an "interface" is distributed over multiple "groups". EXAMPLE 2: A logical partition concept may be driven for instance for selective auditing with the goal of minimizing the AuditReply to be of a manageable size by having the MGC allocate an adequate number of terminations within a <group>. Therefore Audits could be paced for example: ip/1/*, ip/2/*, .., ip/n/*. ip/<group>/<interface>/<id> IP Group ID Interface IP Groups ID Interface (A) Strict hierarchical structure (B) Partial hierarchical structure Figure 2: Group/Interface relationships for the structure of terminationIDs Potential use cases The following examples depict the advantages that each group/interface relationship may facilitate. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 19 Table 5: Examples of Group/interface relationship in ServiceChange Semantic of Termination Name ServiceChange Command (e.g. due to a HW Failure) Strictly hierarchical Upon a HW failure the command issued is (by MG): ServiceChange=ip/1/*{Services{ Method=Forced, Reason="906" }}}, ...a single wildcarded command is possible (facilitated by a strict hierarchical relationship). Partially hierarchical Upon a HW failure the command issued is (by MG): ServiceChange=ip/*/1/*{Services{ Method=Forced, Reason="906" }}}, ServiceChange=ip/*/2/*{Services{ Method=Forced, Reason="906" }}}, … ServiceChange=ip/*/x/*{Services{ Method=Forced, Reason="906" }}} ...a single wildcarded command is not always possible when not using a strict hierarchical relationship. Table 5a: Examples of Termination ID usage in AuditValue Usage of Termination ID structure AuditValue Command (e.g. Requesting a list of Context IDs present in the MG where n and N are number of contexts in the AuditValue Replie-s and n<<N) Neither group nor interface levels specified in request The command (from MGC): Context=*{AuditValue=Root{Audit{}}} Returns: Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}}, Context=2{AuditValue=ip/1/21/201{},AuditValue=ip/1/22/202{}}, Context=3{AuditValue=ip/1/31/301{},AuditValue=ip/1/32/302{}}, … Context=N{AuditValue=ip/256/11/504{},AuditValue=ip/256/12/534{}} … this could potentially return very large AuditValue Replies. Group level specified in request The command (by MGC): Context=*{AuditValue=ip/1/*{Audit{}}} Returns: Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}}, … Context=n{AuditValue=ip/1/51/121{},AuditValue=ip/1/52/122{}} … and this command would be repeated for each group. (facilitated by loose hierarchical relationship). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 20 5.6.1.1.1.2 Optimization of call-independent procedures The CHOOSE wildcard for "Interface" is introduced by this version of the profile. The MGC may optimize (see note 1) call-independent procedures, e.g. based on the AuditValue command, by fully controlling the value allocation for field Group. NOTE 1: "Optimization" could e.g. mean a load shaping function concerning H.248 processing load. The MG may optimize (see note 2) call-independent procedures, e.g. based on the ServiceChange command, via full control over the value allocation for field Interface. NOTE 2: "Optimization" may allow single wildcarded commands, see discussion in table 5. 5.6.1.1.1.3 Field "Id": Usage of wildcard CHOOSE or not The CHOOSE wildcard for "Id" must be applied in the ADD.request command. It is the MGs responsibility for managing the value range of this logical resource.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6.1.1.2 Syntactical Specification
|
5.6.1.1.2.1 ABNF Grammar for H.248 Text Encoding Mode ABNF (RFC 5234 [6]) is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in annex B.2 of ITU-T Recommendation H.248.1 [1]. ABNF coding: pathNAME = EphToken SLASH EPHsystem EphToken = "ip" ; prefix EPHsystem = WildcardALL / WildcardALL SLASH Interface / Group SLASH WildcardALL / Group SLASH (Interface / WildcardCHOOSE) SLASH (Identifier / WildcardALL / WildcardCHOOSE) Group = %d0-65535 ; data type: INT16 Interface = 1*51ALPHANUM Identifier = %d1-4294967295 ; data type: INT32 ALPHANUM = ALPHA / DIGIT WildcardCHOOSE = "$" WildcardALL = "*"
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.6.2 Multiplexed terminations
|
Table 6: Multiplexed terminations MultiplexTerminations Supported? No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7 Descriptors
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.1 TerminationState descriptor
|
Table 7: ServiceState property ServiceState property used: No NOTE: All H.248 Terminations have a ServiceState property according to H.248.1, but explicit usage of the TerminationState Descriptor ServiceState property is not required by this Profile. ServiceState changes can still occur, however, and be indicated in ServiceChange Commands (i.e. this means that the value of the ServiceState property may be implicitly changed by ServiceChange procedures). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 21 Table 8: EventBufferControl property EventBufferControl property used: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.2 Stream descriptor
|
Table 9: Stream descriptor Maximum number of streams per termination type: IP 5 Table 10: Stream configuration Stream Configuration: ALL configurations are allowed
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.2.1 LocalControl descriptor
|
Table 11: LocalControl descriptor If not generic list appropriate termination and stream types Termination Type Stream Type ReserveGroup used: No ReserveValue used: No Table 12: Termination type Termination Type Stream Type Allowed StreamMode Values IP RTP/AVP SendOnly, RecvOnly, SendRecv, Inactive tcp SendRecv, Inactive udptl SendRecv, Inactive udp SendOnly, RecvOnly, SendRecv, Inactive NOTE: Other stream types are for further study.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.3 Events descriptor
|
Table 13: Events descriptor Events settable on termination types and stream types Yes If yes Event ID Termination Type Stream Type See clause 5.14.2.1 • g/cause ALL except ROOT ANY See clause 5.14.2.3 • nt/netfail • nt/qualert ALL except ROOT ANY See clause 5.14.2.11 • it/ito only ROOT Not applicable See clause 5.14.2.14 • adid/ipstop ALL except ROOT ANY See clause 5.14.2.16 • ocp/mg_overload only ROOT Not applicable See clause 5.14.2.17 • hangterm/thb ALL except ROOT Not applicable See clause 5.14.2.18 • scr/cr ALL except ROOT Not applicable See clause 5.14.2.1 • ipra/arc only ROOT Not applicable ETSI ETSI TS 183 018 V3.5.2 (2010-01) 22 Table 14: EventBuffer control EventBuffer Control used: No Table 15: KeepActive KeepActive used on events: No Table 16: Embedded events and signals Embedded events in an Events Descriptor: No Embedded signals in an Events Descriptor: No Table 17: Regulated embedded events Regulated Embedded events are triggered on: None Table 18: ResetEventsDescriptor ResetEventsDescriptor used with events: None Table 19: NotifyImmediate, NotifyRegulated and NeverNotify NotifyImmediate: ALL events NotifyRegulated: None NeverNotify: None
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.4 EventBuffer descriptor
|
Table 20: EventBuffer descriptor EventBuffer Descriptor used: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.5 Signals descriptor
|
Table 21: Signals descriptor Signals settable dependant on termination or streams types Yes If yes Signal ID Termination Type Stream Type / ID ipnapt/* ALL except ROOT ANY Table 22: Signals lists Signals Lists supported: No Table 23: Signals type and duration Signal type and duration supported: No ETSI ETSI TS 183 018 V3.5.2 (2010-01) 23 Table 24: Signals direction Signal Direction supported: No Table 25: NotifyCompletion and RequestID NotifyCompletion supported: No RequestID Parameter Supported: No Table 26: Simultaneously played signals Signals played simultaneously: No Table 27: KeepActive KeepActive used on signals: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.6 DigitMap descriptor
|
Table 28: DigitMap descriptor DigitMaps supported: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.7 Statistics descriptor
|
Table 29: Statistics Descriptor Statistics supported on: Stream Table 30: Statistics Reported On Subtract Statistics reported on Subtract: Yes If yes Statistic IDs reported: ALL (See clause 5.14 for details)
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.8 ObservedEvents descriptor
|
Table 31: ObservedEvents descriptor Event detection time supported: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.9 Topology descriptor
|
Table 32: Topology descriptor Allowed triples: Not Applicable ETSI ETSI TS 183 018 V3.5.2 (2010-01) 24
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.7.10 Error descriptor
|
Table 33: Error Codes sent by MGC Supported H.248.8 [30] Error Codes: ALL Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported Table 34: Error Codes sent by MG Supported H.248.8 [30] Error Codes: ALL with exception of #514 "Media Gateway cannot send the specified announcement" #518 "Event buffer full" #519 "Out of space to store digit map" #520 "Digit Map undefined in the MG" #522 "Functionality Requested in Topology Triple Not Supported" Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8 Command API
|
Table 35 shows in which direction commands are sent, which terminations they can be associated with, and which wildcard options are supported for the specific command. Table 35: Commands and terminations Command Sent By Used on Termination Type Wildcard Support IP ROOT W- O- Add SPDF Yes No No No AuditCapabilities - - - - - AuditValue SPDF Yes Yes No Yes Modify SPDF Yes Yes No No Move - - - - - Notify BGF Yes Yes No No ServiceChange BGF Yes Yes No No Subtract SPDF Yes No Yes No Table 35 shows for which termination types a specific descriptor can be applied, and tables 36 and 37 show with which commands and replies the descriptor can be used respectively. Table 36: Descriptors and requests Descriptor type (see note 1) Termination type Root IP Audit Yes Yes Error Events Yes Yes Local Yes LocalControl Yes Media Yes (see note 2) Yes ObservedEvents Yes Yes Packages Yes ServiceChange Yes Yes Signals Yes Statistics Yes Stream Yes TerminationState Yes (see note 2) NOTE 1: Only H.248 descriptors supported within this H.248 profile specification are shown. NOTE 2: E.g. Base Root package properties. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 25 Table 37: Descriptors and replies Descriptor type (see note 1) Termination type Root IP Audit Error Yes Yes Events Yes Yes Local LocalControl (see note 2) Yes Media Yes Yes ObservedEvents Packages Yes Remote ServiceChange Yes Yes Signals (see note 3) Statistics Yes Stream Yes TerminationState Yes NOTE 1: Only H.248 descriptors supported within this H.248 profile specification are shown. NOTE 2: According to section 5.8.5, auditing of mgcinfo/db H.248 property in LocalControl is required. NOTE 3: According to section 5.8.5, auditing of H.248 signals descriptors is not required. It is seen that an Error Descriptor may be returned in any command reply and thus the Error Descriptor is not included in any subsequent command reply tables.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.1 Add
|
Table 38: Descriptors used by Add Request Descriptors used by Add request: Media (Stream(LocalControl, Statistics, Local, Remote)), Event, Signals NOTE: Statistics are enabled as default. The MGC may explicitly request or suppress statistics generation for individual streams by inclusion of the Statistics descriptor in the Add request command (see section 7.1.15, ITU-T Rec. H.248.1 [1]). Table 39: Descriptors used by Add Reply Descriptors used by Add reply: Media (Stream (Local))
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.2 Modify
|
Table 40: Descriptors used by Modify Request Descriptors used by Modify request: Media (TerminationState, Stream (LocalControl, Statistics, Local, Remote)), Audit (Media (Stream (Statistics)), Signals, Event Table 41: Descriptors used by Modify Reply Descriptors used by Modify reply: Media (Stream(Local, Statistics)) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 26
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.3 Subtract
|
Table 42: Descriptors used by Subtract Request Descriptors used by Subtract request: Audit() OR NONE NOTE: This profile version supports reporting of statistics on all streams or none of the streams. Reporting and disabling of statistics from a subset of the streams in case of multiple streams is not supported by this profile version. Termination level statistics are not supported. Table 43: Descriptors used by Subtract Reply Descriptors used by Subtract reply: Media(Stream(Statistics)) OR NONE
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.4 Move
|
Table 44: Descriptors used by Move Command Move command used: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.5 AuditValue
|
Table 45: AuditValue Audited Properties: Media(TerminationState) (see note 1) Media(Stream(LocalControl)) (see note 2) Audited Statistics: ALL Audited Signals: None Audited Events: None Packages Audit possible: Yes NOTE 1: These are the root/*, seg/* and ipra/* properties. NOTE 2: This is the mgcinfo/db property.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.6 AuditCapabilities
|
Table 46: Descriptors used by AuditCapabilities Command AuditCapabilities command used: No
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.7 Notify
|
Table 47: Descriptors used by Notify Request Descriptors used by Notify Request: ObservedEvents Table 47a: Descriptors used by Notify Reply Descriptors used by Notify Reply: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 27
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.8 ServiceChange
|
Table 48: ServiceChangeMethods and ServiceChangeReasons sent by MGC Service Change Methods Supported ServiceChange Reasons supported Restart 900, 901 Handoff 903 Table 49: ServiceChangeMethods and ServiceChangeReasons sent by MG Service Change Methods Supported ServiceChange Reasons supported Disconnected 900 Forced 904, 905, 906, 915 Restart 900, 901, 902 Graceful 905, 908 Failover 909 Handoff 903 Table 50: ServiceChangeAddress ServiceChangeAddress used: No Table 51: ServiceChangeDelay ServiceChangeDelay used: Yes If yes Valid time period: Provisioned Table 52: ServiceChange Incomplete Flag ServiceChange Incomplete Flag used: No Table 53: ServiceChangeVersion Version used in ServiceChangeVersion: 3 Table 54: Profile Negotiation Profile negotiation as per H.248.18 [i.7]: No Table 54a: ServiceChangeMGCId ServiceChangeMGCId used: Yes
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.8.9 Manipulating and auditing context attributes
|
Table 55: Context Attributes Manipulation and Auditing Context Attributes Manipulated: Emergency, Priority Context Attributes Audited: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 28
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.9 Generic command syntax and encoding
|
Table 56: Command Encoding Supported Encodings: Text (see notes 1 and 2) NOTE 1: The receiver shall be capable of receiving both Short Token Notation and Long Token Notation on an H.248 control association. NOTE 2: The transmitter may select between long and short token forms per H.248 control association.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.10 Transactions
|
Table 57: Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Replies per message: 1 Table 58: Maximum number of Commands per Transaction Request Maximum number of commands per Transaction request: 2 Table 59: Maximum number of Commands per Transaction Reply Maximum number of commands per Transaction reply: 2 Table 60: Optional Commands Commands able to be marked "Optional": AuditValue Table 61: Wildcarded Commands Commands able to be marked "Wildcarded": Subtract Table 62: Transaction Timer Transaction Timer: Value normalMGExecutionTime Provisioned, changeable with Base Root Package (see clause 5.14.2) normalMGCExecutionTime Provisioned, changeable with Base Root Package (see clause 5.14.2) MGOriginatedPendingLimit Provisioned, changeable with Base Root Package (see clause 5.14.2) MGCOriginatedPendingLimit Provisioned, changeable with Base Root Package (see clause 5.14.2) MGProvisionalResponseTimerValue Provisioned, changeable with Base Root Package (see clause 5.14.2) MGCProvisionalResponseTimerValue Provisioned, changeable with Base Root Package (see clause 5.14.2) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 29
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.11 Messages
|
It is recommended that MGC and MG names are in the form of fully qualified domain names. For example the domain name of the MGC may be of the form mgc1.whatever.net and the name of the MG may be of the form mg1.whatever.net. The fully qualified domain name will be used by the MGC and MG as part of the "Message Identifier" in the H.248 messages which identifies the originator of the message.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.12 Transport
|
Table 63: Transport Supported Transports: SCTP (Recommended) UDP (Optional) Table 64: Segmentation Segmentation Supported: SCTP: Inherent in Transport UDP: Optional (dependent on support of Segmentation Package, see clause 5.14.2.12) Table 65: Control Association Control Association Monitoring Supported: Monitoring mechanism is dependent on used H.248 transport (see above table 63): SCTP: inherent capability of SCTP. UDP: H.248.14 (MG-driven monitoring). Empty AuditValue on ROOT (MGC-driven monitoring).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.13 Security
|
Table 66: Security Supported Security: None
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14 Packages
|
This clause includes details of the mandatory and optional H.248 packages that are included in this profile. The meaning of mandatory and optional packages and their properties, signals, events, and statistics is defined in ITU-T Recommendation H.248 Sub-series Implementers' Guide [33]. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 30
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.1 Overview
|
Table 67: Mandatory Packages Mandatory Packages Package Name Package ID Version Generic (ITU-T Rec. H.248.1 [1], annex E.1) g 2 Base root (ITU-T Rec. H.248.1 [1], annex E.2) root 2 Network (ITU-T Rec. H.248.1 [1], annex E.11) nt 1 Diffserv (ITU-T Rec. H.248.52 [17]) ds 2 Gate management (ITU-T Rec. H.248.43 [18], Appendix 1) gm 1 Traffic management (ITU-T Rec. H.248.53 [19]) tman 1 IP NAPT traversal (ITU-T Rec. H.248.37 [9]) ipnapt 1 IP Domain Connection (ITU-T Rec. H.248.41 [16]) ipdc 1 Table 68: Optional Packages Optional Packages Package Name Package ID Version Support dependent on MPLS (ITU-T Rec. H.248.54 [10]) mpls 1 Support of MPLS label stacks - i.e. Label Switched Paths terminated by the MG and related to the H.248 termination. VLAN (ITU-T Rec. H.248.56 [11]) vlan 1 Support of VLAN tags and/or Ethernet priorities. MGC Information (ITU-T Rec. H.248.45 [4]) mgcinfo 1 Support of MGC related recovery. Inactivity Timer (ITU-T Rec. H.248.14 [13]) it 1 Only applicable for UDP transport. Segmentation (ITU-T Rec. H.248.1 [1], annex E.14) seg 1 Applicable for UDP transport where sufficiently large messages are required to be supported. RTP (ITU-T Rec. H.248.1 [1], annex E.12) rtp 1 Support of usage metering and statistics reporting. Particular package capabilities are only applicable for "media-aware" bearer connections. Application Data Inactivity Detection ITU-T Rec. H.248.40 [12]) adid 1 MGC requires to be explicitly informed of a cessation of an application data flow. Media Gateway Overload Control (ITU-T Rec. H.248.11 [15]) ocp 1 Support of message throttling, based on rate limitation, from MGC towards MG. Hanging Termination Detection (ITU-T Rec. H.248.36 [24]) hangterm 1 Support of Hanging Termination Detection. Statistics Conditional Reporting (ITU-T Rec. H.248.47 Revision 1 [25]) scr 2 Support of real time reporting of specific statistics based on a particular condition. This package may be supported as an operator option. Gate management (ITU-T Rec. H.248.43 [18]) gm 2 Support of filtering based on source port range. IP realm availability (ITU-T Rec. H.248.41 Amendment 1) [16] ipra 1 Support of a mechanism allowing the MGC to discover the IP realms that are available at the MG at a certain time and on a mechanism allowing the MG to inform the MGC about change of availability of realms. RTP Application Data Package (H.248.58 [34]) rtpad 1 Support of usage metering and statistics reporting. Scope on traffic-volume based measurement of RTP application data (i.e. the media stream). Latch Statistics (ITU-T Rec. H.248.37 Revision 1 [9]) lstat 1 Complements the IP NAPT Traversal package to enable the recording of discarded packets due to implicit filtering by the latching function. Traffic Policing Statistics (ITU-T Rec. H.248.53 Revision 1 [19]) tmanr 2 Complements the Traffic Management package, allowing the recording of the number of packets and octets that did not conform to the traffic parameters, and the number of packets that were dropped due to such violations. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 31
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2 Package usage information
| |
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.1 Generic (g)
|
Table 69: Generic package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Cause (g/cause) M ADD, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value None ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value General cause (Generalcause) M ALL Not Applicable Failure cause (Failurecause) M ALL Not Applicable Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 32
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.2 Base root (root)
|
Table 70: Base root package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MaxNrOfContexts (root/maxNumberOfContexts) O AUDITVALUE ALL YES MaxTerminationsPerContext (root/maxTerminationPerContext) O AUDITVALUE ALL YES normalMGExecutionTime (root/normalMGExecutionTime) O MODIFY, AUDITVALUE ALL YES normalMGCExecutionTime (root/normalMGCExecutionTime) O MODIFY, AUDITVALUE ALL YES MGProvisionalResponseTimer Value (root/MGProvisionalResponse TimerValue) O MODIFY, AUDITVALUE ALL YES MGCProvisionalResponseTimer Value (root/MGCProvisionalResponse TimerValue) O MODIFY, AUDITVALUE ALL YES MGCOriginatedPendingLimit (root/MGCOriginatedPending Limit) O MODIFY, AUDITVALUE ALL YES MGOriginatedPendingLimit (root/MGOriginatedPendingLimit) O MODIFY, AUDITVALUE ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 33
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.3 Network (nt)
|
Table 71: Network package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Maximum jitter buffer (nt/jit) O ADD, MODIFY ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Network failure (nt/netfail) O ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value None - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Cause (cs) O For further studies. For further studies (see note) Quality alert (nt/qualert) O ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Threshold (th) O ALL Not Applicable ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Threshold (th) O ALL Not Applicable Statistics Mandatory/Optional Used in command Supported Values Duration (nt/dur) O ADD, SUBTRACT, MODIFY, AUDITVALUE ALL Octets sent (nt/os) M ADD, SUBTRACT ALL O MODIFY, AUDITVALUE ALL Octets received (nt/or) M ADD, SUBTRACT ALL O MODIFY, AUDITVALUE ALL Error Codes Mandatory/Optional None NOTE: This event may be overloaded in order to address multiple failure causes (see ITU-T Rec. H.248.1 [1] Version 3, section E.11.5.1.2). An unambiguous distinction on MGC and MG side implies mutually agreed cause codepoints. This is a provisioning activity. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 34
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.4 Differentiated Services (ds)
|
Table 72: Differentiated Services package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Differentiated Services Code Point (ds/dscp) M ADD, MODIFY ALL Yes Tagging Behaviour (ds/tb) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 35
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.5 Gate Management (gm)
|
Table 73: Gate Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Remote Source Address Filtering (gm/saf) M ADD, MODIFY ALL Not Applicable (see note 1) Remote Source Address Mask (gm/sam) O ADD, MODIFY ALL Not Applicable Remote Source Port Filtering (gm/spf) M ADD, MODIFY ALL Not Applicable (see note 1) Remote Source Port (gm/spr) O ADD, MODIFY ALL Not Applicable Remote Source Port Range (gm/sprr) (see note 3) O ADD, MODIFY ALL Not Applicable Explicit Source Address Setting (gm/esas) O ADD, MODIFY ALL See note 1 Local Source Address (gm/lsa) O ADD, MODIFY ALL Not Applicable Explicit Source Port Setting (gm/esps) O ADD, MODIFY ALL See note 1 Local Source Port (gm/lsp) O ADD, MODIFY ALL Not Applicable RTP Specific Behaviour (gm/rsb) (see note 4) M ADD, MODIFY ALL OFF (see note 2) Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None - - Event Parameters Mandatory/ Optional Supported Values Provisioned Value - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values Discarded Packets gm/dp O ADD, MODIFY, SUBTRACT, AUDITVALUE ALL Error Codes Mandatory/Optional None NOTE 1: Default value is 'OFF' in gm/1 (see ITU- Rec. H.248.43 [18]). NOTE 2: Default value must be provisioned in gm/1 (see ITU- Rec. H.248.43 [18]). The provisioned value in this profile shall be OFF. NOTE 3: This property is defined in gm/2 while all other properties exist in gm/1. NOTE 4: The gm/rsb property is identical to the rtcph/rsb property (see Figure II.1 in H.248.43) and defined by ITU-T Rec. H.248.57 [i.19]. The rtcph package defines rsb property semantics for the SDP attribute according RFC 3605 [31] (see in particular clause 6.6.1.4.1 in H.248.57). There are following package usage details for this profile specification: the SDP attribute "a=rtcp:" may be used in the H.248 RD and shall be not used in the H.248 LD (see clauses 5.16 and 5.17.1.7 for more information). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 36
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.6 Traffic management (tman)
|
Table 74: Traffic Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value tman/pol M ADD, MODIFY ALL Yes tman/pdr M ADD, MODIFY ALL Not Applicable tman/dvt M ADD, MODIFY ALL Yes tman/sdr M ADD, MODIFY ALL Not Applicable tman/mbs M ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.7 IP NAPT Traversal (ipnapt)
|
Table 75: IP NAPT Traversal Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value Latching (ipnapt/latch) M ADD, MODIFY Not Applicable Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value NAPT Traversal Processing (napt) M ALL Not Applicable Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 37
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.8 MPLS (mpls)
|
Table 76: MPLS Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value mpls/stack M ADD, MODIFY ALL Not Applicable (see note) Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None NOTE: "Not applicable" means that in case the mpls/stack property is absent, the MG shall not apply any MPLS label to the given termination/stream.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.9 VLAN (vlan)
|
Table 77: VLAN Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value VLAN tags (vlan/tags) O ADD, MODIFY ALL (see note) Yes Ethernet priority (vlan/pri) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None NOTE: "ALL" means: • value range "0 to 4 095" of property VLAN tags used for VLAN tagging; • value "4 096" of property VLAN tags defines the semantic for "no VLAN tagging". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 38
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.10 MGC Information (mgcinfo)
|
Table 78: MGC Information Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value ALL M ADD, MODIFY, AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.11 Inactivity Timer (it)
|
Table 79: Inactivity Timer Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Inactivity Timeout (it/ito) M MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Maximum Inactivity Time (mit) O ALL Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 39
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.12 Segmentation (seg)
|
Table 80: Segmentation Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MGSegmentation TimerValue (seg/ MGSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGCSegmentation TimerValue (seg/ MGCSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGMaxPDUSize (seg/ MGMaxPDUSize) M AUDITVALUE, MODIFY ALL YES MGCMaxPDUSize (seg/ MGCMaxPDUSize) M AUDITVALUE, MODIFY ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional 459 M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 40
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.13 RTP (rtp)
|
Table 81: RTP Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None Statistics Mandatory/Optional Used in command Supported Values Packets Sent (rtp/ps) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Packets Received (rtp/pr) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Packet Loss (rtp/pl) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Jitter (rtp/jit) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Delay (rtp/delay) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Octets sent (rtp/os) (see note 1) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Octets received (rtp/or) (see note 2) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Error Codes Mandatory/Optional None - NOTE 1: Inherited statistic from nt package. Value of rtp/os must be identical to nt/os (see clause E.12.5.2, ITU-T Rec. H.248.1 [1]). NOTE 2: Inherited statistic from nt package. Value of rtp/or must be identical to nt/or (see clause E.12.5.2, ITU-T Rec. H.248.1 [1]).
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.14 Application Data Inactivity Detection (adid)
|
Table 82: Application Data Inactivity Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command IP Flow Stop Detection (adid/ipstop) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Detection Time (dt) O ALL Yes Direction (dir) O ALL Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 41
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.15 IP Domain Connection (ipdc)
|
Table 83: IP domain connection package Properties Mandatory/Optional Used in command Supported Values Provisioned Value IP Realm Identifier (iIpdc/realm) M ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None - - Event Parameters Mandatory/Optional Supported Values Provisioned Value - - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional No - NOTE: The ITU-T Rec. H.248.41 [16] package definition does not specify a length limit for the ipdc/realm string. The maximum length is given by RFC 1123 [29] in case of a domain name format used for the property. If it is not a domain name format, then the maximum size should be up to 255. In case the MGC uses an ipdc/realm property exceeding the above defined length limitation, the MG shall reply with an error descriptor using error code #410: "Incorrect identifier".
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.16 Media Gateway Overload Control (ocp)
|
Table 84: Media Gateway Overload Control Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command MG_Overload (ocp/mg_overload) (see note) M MODIFY, NOTIFY (see note) Event Parameters Mandatory/Optional Supported Values Provisioned Value None - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - NOTE: When the MG is overloaded, overload Events may be sent either only following the first ADD.request which creates a new Context, or following all ADD.request commands (see ITU-T Rec. H.248.11 [15] Corrigendum 1). These two options result in different normalisations of the overload event rate as an indicator of the level of MG overload (see clause 5.17.2.3). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 42
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.17 Hanging Termination Detection (hangterm)
|
Table 85: Hanging Termination Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Termination Heartbeat (hangterm/thb) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Timerx (timerx) O 0,1 up Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional No -
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.18 Statistic Conditional Reporting (scr)
|
Table 86: Statistic Conditional Reporting Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Conditional Reporting, (scr/cr) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values: Provisioned Value Statistic Identifier (si) M ALL YES Duration (dur) O ALL YES Period (per) O ALL YES Maximum (max) O ALL YES Minimum (min) O ALL YES Normal (nor) O ALL YES Request timestamp (rt) O ALL YES Value Type (typ) O ALL YES Target Value (val) O ALL YES Deviation (dev) O ALL YES Compliance (com) O ALL YES Direction (dir) O ALL YES ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistic Identifier (si) M ALL - Value (val) M ALL - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 018 V3.5.2 (2010-01) 43
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.19 IP Realm Availability (ipra)
|
Table 86a: IP Realm Availability Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Available Realms, (ipra/ar) M AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Available Realms Changed, (ipra/arc) M MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values: Provisioned Value - - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Newly Available Realms (nar) O (see note) ALL Not applicable Newly Unavailable Realms (nur) O (see note) ALL Not applicable Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - NOTE: Although the ObservedEvent Parameters ipr/nar and ipra/nur are optional as such, at least one parameter must be included in a ipra/arc notification command.
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.20 RTP Application Data (rtpad)
|
Table 86b: RTP Application Data Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: RTP payload octets sent, (rtpad/payloados) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY RTP payload octets received, (rtpad/payloador) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Error Codes Mandatory/Optional None - ETSI ETSI TS 183 018 V3.5.2 (2010-01) 44
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.21 Latch Statistics (lstat)
|
Table 86c: Latch Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: Discarded packets, (lstat/dp) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Error Codes Mandatory/Optional None -
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.22 Void
|
Table 86d: Void
|
1e3c7e6a783f798e804b24eccd66846f
|
183 018
|
5.14.2.23 Traffic Policing Statistics (tmanr)
|
Table 86e: Traffic Policing Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: Discarded packets, (tmanr/dp) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Peak-rate violating packets, (tmanr/pvp) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Peak-rate violating octets, (tmanr/pvo) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Sustained-rate violating packets, (tmanr/svp) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Sustained-rate violating octets, (tmanr/svo) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY ETSI ETSI TS 183 018 V3.5.2 (2010-01) 45 Error Codes Mandatory/Optional None - NOTE: The statistic tmanr/dp is mandatory because independent of the applied policing mechanism. The other four statistics are optional because dependent on peak- or sustained-rate policing. 5.15 Mandatory support of SDP and annex C information elements Elements listed as mandatory shall be supported by MGC and MG but does not have to be present in all commands containing SDP. Details of which elements are included in each command are provided in clause 5.18. Table 87: Supported SDP Information Elements SDP Information Element Mandatory/optional Description Protocol version "v=" line Mandatory The value must always be equal to zero: v=0 Connection "c=" line Mandatory The network type must always be "IN". The address type value must be "IP4" or "IP6". The connection address value may be underspecified with CHOOSE wildcard ("$"). Media "m=" line Mandatory There are four fields (or SDP values) <media>, <port>, <proto> and <fmt> in the "m=" line (see RFC 4566 [28]; note 3). The "m=" line may be omitted from SDP (see note 6). Media type <media> Mandatory if "m=" line included "Media-type agnostic" mode: "-" may be used for the media value (see also clause G.2.2 of [i.18]). In case MG is media agnostic and MGC specifies any other media type than "-", the MG shall reject the command with error code 515. "Media-type aware" mode: The media value shall be specified in case of media-aware interworking (see note 2). In case MG is media aware but does not support the requested media type the MG shall reject the command with error code 515. Transport port <port> Mandatory if "m=" line included L4-port aware mode: The port value may be underspecified with CHOOSE wildcard ("$"). L4-port agnostic mode: Not supported. Transport protocol <proto> Mandatory if "m=" line included "Transport-protocol agnostic" mode: "-" may be used for the proto value. "Transport-protocol aware" mode: udp Allow only L4 protocol = UDP (see note 8). tcp or TCP Allow only L4 protocol = TCP µ (see note 9). TCP/MSRP Message service using RFC 4975 [36]. RTP/AVP RTP profile according RFC 3551 [38] Allow only L4 protocol = UDP (see note 1). udptl Allow only L4 protocol = UDP. - No transport protocol specific behaviour is required by the MG. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 46 SDP Information Element Mandatory/optional Description Mode misalignments: In case MG is transport aware (i.e. "transport-protocol aware" and "L4-port aware") but does not support the requested transport protocol the MG shall reject the command with error code 449. In case MG is transport agnostic and MGC specifies any other transport protocol than "-", the MG shall reject the command with error code 449. If MG supports both transport protocol agnostic and transport protocol aware behaviours, then it shall accept "-" or a valid value in the transport protocol field. A transport protocol aware MG may not support transport agnostic behaviour and may reject a request with a transport protocol value"-", with error code 449 (see also clause G.3 of [i.18]). Media format <fmt> Mandatory if "m=" line included. "Media format aware" mode: Various values may be used for media-format aware interworking (e.g. transcoding; see clause 5.17.1.14) (see note 2). In case MG is media-format aware but does not support the requested media format the MG shall reject the command with error code 449. "Media format agnostic" mode: "-" may be used for the format list value. Mode misalignments: In case MG is media format aware but does not support the requested format list value the MG shall reject the command with error code 449. In case MG is media format agnostic and MGC specifies any other media format than "-", the MG shall reject the command with error code 449. If MG supports both media format agnostic and media format aware behaviours, then it shall accept "-" or a valid value in the format list value field. A media format aware MG may not support media format agnostic behaviour and may reject a request with a media format list value"-", with error code 449 (see also clause G.3 of [i.18]). Bandwidth "b=" line Mandatory MUST not be used without a "m=" line. The modifier value must always be "AS". This implies that the bandwidth-value represents the ""maximum bandwidth" (see clause 5.8 in RFC 4566 [28]). The bandwidth-value relates therefore to the peak bitrate (see note 7). The bandwidth-value value defines the IP layer bandwidth for the specific H.248 Stream (see notes 4 and 5). For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the bandwidth value will include the bandwidth used by RTP and RTCP together. NOTE 1: Even if the transport value is RTP, the "RTP Specific Behaviour" property of the Gate Management package (gm) shall be used to indicate whether RTCP resource reservation is also requested. NOTE 2: For Ia profile versions 2 and higher RFC 4566 [28] shall be used as basis. RFC 4566 [28] enables "-" as a valid character (Ia profile version 1 uses RFC 2327 [i.3], which does not allow the "-" in place of media type, transport and media format fields. However in the scope of Ia profile version 1 this was considered as an admitted SDP extension). NOTE 3: RFC 4566 [28] obsoleted RFC 2327 [i.3], but the ABNF grammar did slightly change for the "m=" line: a) RFC 2327 [i.3]: m=<media> <port> <transport> <fmt list>. b) RFC 4566 [28]: m=<media> <port> <proto> <fmt> ... There is a syntactical change for the last two fields, but the semantical meaning is unchanged. See also ITU-T Rec. H.248.49 [23], appendix I "Comparison of SDP variants between RFC 4566 [28] and RFC 2327 [i.3]" and in particular: table I.7/H.248.49 "RFC 4566 [28] versus RFC 2327 [i.3] - SDP specification - "m=" line". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 47 SDP Information Element Mandatory/optional Description NOTE 4: This semantic is consistent for RTP traffic (see clause 6.2 of RFC 3550 [i.8]) and non-RTP traffic (see clause 5.8 of RFC 4566 [28]). NOTE 5: It has to be noted that Ia profile version 1 defines a different semantic (see table 81 in ES 283 018 [22]) defined, which incorporates also layer 2 bitrate. A transformation between both "b=" line usages (in case of IP-over-L2) is not straightforward because the transformation parameters are based on L2-PCI and the IP packet rate. The L2-PCI is typically constant for a dedicated L2 technology (like IP-over-IEEE 802.3 [i.9]), but the packet rate is application-specific. E.g. the IP packet rate is usually unknown at Ia for media-agnostic IP-to-IP interworking. NOTE 6: The "m=" and "b=" lines may be omitted in certain procedures, which are further described in clause 5.17.1.11. NOTE 7: The unit for the bandwidth-value (peak bitrate) is "kbit/s". The unit for the peak data rate (tman/pdr) is "byte/s". The "b=" line is not providing any information about the traffic characteristic, i.e. whether the traffic flow has a Constant BitRate (CBR) or Variable BitRate (VBR). The bandwidth-value is thus independent of the traffic characteristic and relates to the peak bitrate for CBR and VBR traffic (see also clause 5.17.1.5). NOTE 8: Parameter "udp" is introduced by RFC 4566 [28] but not yet registered by IANA (see http://www.iana.org/assignments/sdp-parameters). NOTE 9: Upper case TCP is defined by RFC 4145 [i.21] and registered by IANA. Lower case tcp was introduced by Ia v1 and is allowed for backwards compatibility.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.