hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a95505b1e252f195bf707ee85ccce821 | 183 025 | 5.3 H.248 Service State | One of the key descriptors of Terminations in the present document is the ServiceStates property within the Termination State Descriptor: Possible values: InService The termination is in-service and functioning normally. OutOfService The termination is out-of-service and not available for traffic. Test The termination is undergoing testing. The MG/MGC may report changes to the service state via the Service Change Command to its peer. Changes to the service state can occur due to faults (MG only) or interaction with management commands (MG/MGC). In the latter case, the H248 Service State is assumed to reflect the overall/resulting availability status of the termination based on the administrative (i.e. the state of the resource as required by the management interface) and operational (i.e. the state of the resource based whether it is working correctly or not) states. Note that the transition into the TEST state has no impact on Service Change procedures. Service change procedures are impacted only in the transition from TEST to OUT OF SERVICE states (see table F2/H248.1 of [i.5]). |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 6 Management Primitives | As stated previously, specific management systems, architectures and protocols are outside the scope of the present document. Rather, the present document considers only a high level set of primitives which directly result in the triggering of H.248 signalling. The following management primitives are defined in the present document: • Create Resource: This command creates a resource. A resource is typically created prior to it being enabled. This command has no impact on H.248 signalling and is included only for completeness. • Enable Resource: The resource moves from an OOS to an IS state (assuming that there is no problem with any related physical state) and is now available for traffic. • Disable Resource (Graceful): The resource is no longer available to new calls/connections. However, all existing calls are permitted to terminate naturally at which point the resource moves into the OOS state. If there are still remaining calls on the resource after a period of time, the operator may invoke the Disable Resource (Immediate) primitive. • Disable Resource (Immediate): Any existing calls/connections are force released, at which point the resource moves into the OOS state. • Delete Resource: This command deletes a resource. A resource would be disabled prior to it being deleted. This command has no impact on H.248 signalling and is included only for completeness. These management primitives (in general) are applicable at both the MG and MGC. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 7 Failure/Recovery Scenarios | Certain failure scenarios also result in the triggering of H.248 signalling. The present document defines the following set of such scenarios: • Nodal failure and recovery of a MG/MGC. This can be due to hardware or software faults. • Termination failure and recovery. Examples of this are termination failure/recovery on the MG (e.g. DSP failure, interface failure such as loss of synchronization on an E1, etc.). • User plane failure. Examples of this would be detection of loss of RTP media. The MG would inform the MGC of such failure and the MGC may force release the call. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 13 • MG-MGC signalling link (control association) failure/recovery. The detection of a signalling link failure results in H.248 signalling to restore the link. On restoring the link, the MG and MGC may have become out of step and thus additional H.248 audits are necessary to ensure the re-synchronization of each end. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 8 Redundancy Scenarios | The H.248 non call related procedures are also impacted by the redundancy architectures chosen at a MG/MGC. Examples of such scenarios are: • MGC Hand-Off. This functionality enables a MGC to terminate an existing control association and establish a new control association to an alternative MGC. This procedure can be applied to load share or due to maintenance action. • MGC Triggered MG Re-direct. This functionality enables a MGC to redirect an attempted registration to an alternative MGC. • MG Failover. This functionality enables a MG to inform a MGC that a secondary MG is taking over an existing control association. It should be noted that processor redundancy can be achieved within a functional node thus being invisible to the H.248 protocol peer or additionally within the functional node but between logical entities within that node and thus using H.248 procedures but using the same nodal address. The scope of the present document does not extend to inter-nodal protocol solutions to support other such redundancy scenarios. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 9 General Use Cases | The following use cases and their interaction with the H.248 non-call related procedures are considered in the present document. Configuration Management: • Enable MG. • Enable MGC. • Disable MG (Graceful). • Disable MG (Immediate). • Disable MGC. • Enable Termination. • Disable Termination (Graceful). • Disable Termination (Immediate). • Change of MG Resources. Fault Management - Failure and recovery: • MG failure and recovery. • MG termination failure and recovery. • MGC failure and recovery. • User plane failure. • MGC-MG signalling link failure and recovery. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 14 Performance Management: • MG Overload. • MGC Overload. Node Redundancy: • MGC Handoff. • MGC MG Triggered Redirect. • MG Failover. 10 Interaction Between Use Cases and Non-Call Related H.248 Procedures This clause contains high level functional descriptions of the non call-related H.248 procedures in relation to the Use Cases. There may be multiple procedures relating to one general use case. Clause 11 contains the detailed contents of each of the cited procedures. The procedure names are denoted by the use of UPPER CASE letters. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.1 Enable MG | This management primitive is applicable to both the MGC and MG. It is recommended that this primitive is initially sent to the MGC and subsequently to the MG. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.1.1 Enable MG (at MGC) | This use case is triggered by management action that results in a MG being enabled at the MGC. There are no H.248 procedures associated with this action. The MGC simply awaits a registration from the MG (see clause 10.1.2). |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.1.2 Enable MG (at MG) | This use case is triggered by management action that results in a MG being brought into service. The MG will have been provisioned with the identity/address of one or more MGC(s). The H.248 procedures are dependent on whether the MG undergoes a cold or warm boot and are as follows: MG Cold Boot 1) The MG registers with one of its (pre-provisioned) MGCs using the MG REGISTRATION (COLD BOOT) procedure. This step enables the H.248 protocol version to be negotiated as well as the support of any H.248 profiles. 2) In the event of there being no response to the registration request, the MG follows the procedures of clause 11.5 of [i.5]. 3) On completion of the initial registration procedure, the MGC assumes that all physical terminations are in the NULL context and there are no existing ephemeral terminations. Thus no context/termination related audits are required to be performed. 4) The MGC may optionally perform a PACKAGES AUDIT procedure in order to determine the MG support of any optional packages in a mutually supported profile. 5) The MGC may optionally audit ROOT properties (in any mandatory and optional packages) via the AUDIT ROOT PROPERTIES procedure. 6) The MGC may optionally set properties and events (in any mandatory and optional packages) in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 15 7) The MG may optionally inform the MGC of the state of its physical terminations via a MG TERMINATION AVAILABLE/MG TERMINATION UNAVAILABLE procedure. 8) The MGC may optionally Audit the state of the physical terminations if it cannot be assumed that the state is in-service or out-of-service via the AUDIT TERMINATION STATE procedure. 9) The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits by one of the two procedures above. MG Initial Registration Ack MG Initial Registration MGC MG Packages Audit Packages Audit Ack Set ROOT Term Events/Properties Set ROOT Term Events/Properties Ack (optional) (optional) MG Termination (Un)Available MG Termination (Un)Available Ack (optional) (optional) Audit Termination State Audit Termination State Ack (optional) Audit ROOT Properties Audit ROOT Properties Ack Figure 2: MG Cold Boot Procedures MG Warm Boot 1) The MG registers with one of its (pre-provisioned) MGCs using the MG RESTORATION procedure This step enables the H.248 protocol version to be negotiated as well as the support of any H.248 profiles. 2) In the event of there being no response to the registration request, the MG follows the procedures of clause 11.5 of [i.5]. 3) On completion of the re-registration procedure, the MGC does not assume that all physical terminations are in the NULL context and there may be existing ephemeral terminations. 4) The MGC may optionally perform a PACKAGES AUDIT procedure in order to determine the MG support of any optional packages in a mutually supported profile. This step is recommended if the related service change reason indicates that the capabilities/packages of the MG have changed. 5) The MGC may optionally audit ROOT properties (in any mandatory and optional packages) via the AUDIT ROOT PROPERTIES procedure. 6) The MGC may optionally set properties and events (in any mandatory and optional packages) in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. 7) The MGC may optionally perform a CONTEXT AUDIT procedure to determine/check the active contexts and connected terminations on the MG. 8) The MG may optionally inform the MGC of the state of its terminations via a MG TERMINATION AVAILABLE/MG TERMINATION UNAVAILABLE procedure. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 16 9) The MGC may optionally Audit the state of its terminations if it cannot be assumed that the state is in-service or out-of-service via the AUDIT TERMINATION STATE procedure. 10) The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits by one of the two procedures above. MG Restoration Ack MG Restoration MGC MG Packages Audit Packages Audit Ack Set ROOT Term Events/Properties Set ROOT Term Events/Properties Ack (optional) (optional) MG Termination (Un)Available MG Termination (Un)Available Ack (if state changes have occurred) Audit Termination State Audit Termination State Ack Context Audit Context Audit Ack (optional) Audit ROOT Properties Ack Audit ROOT Properties (optional) (optional) Figure 3: MG Warm Boot Procedures |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.2 Enable MGC | This management primitive is applicable only to the MGC and results in a MGC being brought into service. The MGC will optionally have been provisioned with the H.248 mid and possibly the transport address of the H.248 control association of its MGs. The following H.248 procedures are performed: 1) The MGC may optionally check on the availability of its MGs via the CHECK MG AVAILABILITY procedure. This is only possible if the MGC is aware of the pre-provisioned IP address of the MG and UDP transport is used. 2) If the MG is available, the MGC may optionally request the MG to register via the MGC INITIATED SERVICE RESTORATION procedure which causes the MG to initiate the MG RE-REGISTRATION (RESTART) procedure. 3) If the MG is available, the MGC may optionally audit ROOT properties in the MG via the AUDIT ROOT PROPERTIES procedure. 4) If an MG is available, the MGC may optionally set properties and events in the MG on ROOT level via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. 5) If an MG is available, the MGC may optionally perform a CONTEXT AUDIT procedure to determine the active contexts and connected terminations on the MG. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 17 6) If an MG is available, the MGC may optionally clean up hanging contexts/terminations via a WILDCARDED SUBTRACT. 7) If an MG is available, the MGC may optionally check on the service state of the physical terminations on the MG service via the AUDIT TERMINATION STATE procedure. 8) The MGC should not deblock associated circuits toward peer nodes before it has determined the true service state of the MG's circuits. Check MG Availability MGC MG Check MG Availability Ack Set ROOT Term Events/Properties Set ROOT Term Events/Properties Ack (optional) (optional) (optional) Audit Termination State Wildcarded Subtract Ack Context Audit Context Audit Ack (optional) MGC Initiated Service Restoration MGC Initiated Service Restoration Ack MG Ordered Re-Register MG Ordered Re-Register Ack (optional) (optional) Wildcarded Subtract Audit Termination State Ack (optional) Audit ROOT Properties Audit ROOT Properties Ack (optional) Figure 4: Enable MGC Procedures |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.3 Disable MG (Graceful) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service gracefully. It is recommended that the network management system performs a Disable MG (Graceful) command to the MGC. The one scenario where a Disable MG (Graceful) command to the MG makes sense is for an Access Gateway in order to inhibit new calls being initiated toward the MGC during the graceful period, and even in this case a MGC would be able to reject any originating calls appropriately. In addition, the management primitive typically has no equivalent of the H.248 ServiceChangeDelay - rather the acceptable period during which all affected calls/connections ought to be removed is determined by the operator. Therefore when mapping into H.248, a default value for the ServiceChangeDelay period would need to be applied. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.3.1 Disable MG (Graceful) (at MGC) | On receipt of this primitive, the MGC performs the following actions: 1) The MGC inhibits any new calls/connections to the MG and allows existing calls/connections to expire naturally/normally. 2) In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related procedures (e.g. reject the call attempt and connect a failure indication). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 18 3) When all calls have been released, the management system is informed. Optionally, the MGC may also place the MG out of service via the MGC INITIATED SERVICE CANCELLATION procedure. MGC MG (optional) MGC INITIATED SERVICE CANCELLATION I di t A k MGC INITIATED SERVICE CANCELLATION ACK I di t A k Figure 5: MGC INITIATED SERVICE CANCELLATION Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.3.2 Disable MG (Graceful) (at MG) | The following H.248 procedures are applied: 1) The MG informs the MGC via the MG SERVICE CANCELLATION (GRACEFUL) procedure. This procedure enables the MG to specify a timer (the ServiceChangeDelay) during which it is anticipated that all existing calls/connections on that MG will expire normally. 2) If applicable, the MG may prevent new originating calls being offered to the MGC. 3) The MGC inhibits any new calls/connections to the MG and allows existing calls/connections to expire naturally/normally. 4) At the end of the ServiceChangeDelay period, any remaining connections are left hanging on the MG. 5) At the end of the ServiceChangeDelay period, the MGC force releases any remaining calls that have not expired naturally (but does not signal to the MG since the control association is now assumed to be down). MG Service Cancellation (Graceful) MGC MG MG Service Cancellation (Graceful) Ack (expiry of graceful timer) Figure 6: MG SERVICE CANCELLATION (GRACEFUL) Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.4 Disable MG (Immediate) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service immediately. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.4.1 Disable MG (Immediate) (at MGC) | On receipt of this primitive, the MGC performs the following actions: 1) The MGC inhibits any new calls/connections to the MG and force releases existing calls/connections. 2) In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related procedures (e.g. reject the call attempt and connect a failure indication). 3) When all calls have been released, the management system is informed. Optionally, the MGC may also place the MG out of service via the MGC INITIATED SERVICE CANCELLATION procedure (see figure 5). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 19 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.4.2 Disable MG (Immediate) (at MG) | The following H.248 procedures are performed: 1) The MG informs the MGC via the MG SERVICE CANCELLATION (IMMEDIATE) procedure. 2) The MG responds to the management system. Note that existing connections are still hanging on the MG. 3) On receipt of the MG SERVICE CANCELLATION (IMMEDIATE) message, the MGC force releases any calls/connections associated with that MG. However, the connections cannot be removed on the MG due to the control association being down. Since connections may be left hanging, it is recommended that the DISABLE MG (Immediate) primitive is applied firstly at the MGC and then at the MG. MGC MG MG Service Cancellation ( Immediate) MG Service Cancellation (Immediate) Ack Figure 7: MG SERVICE CANCELLATION (Immediate) Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.5 Disable MGC | This primitive is sent to a MGC and results in a MGC being taken out of service. Prior to the MGC being disabled, it is recommended that the MGC inform its dependent MGs to move their control associations to an alternative MGC via the MGC HANDOFF procedure (clause 10.18) or that all dependent MGs are disabled prior to disabling the MGC (clause 10.4). |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.6 Enable Termination | This management primitive is applicable to both the MGC and MG. It is recommended that this primitive is initially sent to the MGC and subsequently to the MG. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.6.1 Enable Termination (at MGC) | The following H.248 procedures are performed: 1) The MGC may: a) Optionally assume that the corresponding termination is in-service on the MG, in which case the MGC attempts to use the termination and will receive an error code if the termination is not available at the MG end. On receipt of any such error code, the MGC desists from using the termination until such time as the procedures in clause 10.6.2 are completed. b) Optionally assume that the corresponding termination is out of service and await the completion of the procedures in clause 10.6.2. c) Optionally audit the service state of the termination via the AUDIT TERMINATION STATE procedure. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 20 MGC MG Audit Termination State Audit Termination State Ack Figure 8: Audit Termination State Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.6.2 Enable Termination (at MG) | The following H.248 procedures are performed: 1) The MG informs the MGC via the MG TERMINATION AVAILABLE procedure. If a successful response is obtained the termination is now in-service at both the MG and MGC. If a negative response/error descriptor with error code #511 "Temporarily Busy" (defined in ITU-T Recommendation H.248.8 [i.13]) indicating a temporary busy condition in the MGC is received, the MG periodically repeats the MG TERMINATION AVAILABLE procedure until a successful response is received. If multiple repetitions are needed, the repetition rate shall be continuously decreased over time. The minimum inter-transmit time under such conditions shall be 100 ms. NOTE: In case the MG termination procedure is to be repeated and if the corresponding MG termination has undergone a Service State change in the meantime, only the latest Service State is reported. This may imply a change of the procedure to be applied (e.g. MG TERMINATION UNAVAILABLE). MGC MG MG Termination Available MG termination Available Ack Figure 9: MG Termination Available Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.7 Disable Termination (Graceful) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a termination being taken out of service gracefully. It is recommended that the network management system performs a Disable Termination (Graceful) command to the MGC. The one scenario where a Disable Termination (Graceful) command to the MG makes sense is for an Access Gateway in order to inhibit new calls being initiated toward the MGC during the graceful period - and even in this case a MGC would be able to reject any originating calls appropriately. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.7.1 Disable Termination (Graceful) (at MGC) | The following actions are performed: 1) The MGC prevents any new calls/connections being offered to the affected termination. 2) If there are any current calls/connections on the termination, the MGC allows them to expire normally/naturally. 3) When all calls are released, the MGC informs the management system. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 21 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.7.2 Disable Termination (Graceful) (at MG) | The following actions are performed: 1) The MG informs the MGC via the MG TERMINATION OOS GRACEFUL procedure. This procedure enables the MG to specify a timer (the ServiceChangeDelay) during which it is anticipated that all existing calls/connections on that MG termination will expire normally. On receipt of this message, the MGC now inhibits any new calls/connections to the specified MG termination and allows existing calls/connections to expire naturally/normally. NOTE 1: The use of delay means that the network management has lost control of when the calls will be forced- released, in many cases the operator would control this and depending on number of calls still active may chose to defer the maintenance action. 2) If a successful response is obtained at the end of the ServiceChangeDelay period, the MG places the termination in the out of service state. If a negative response/error descriptor with error code #511 "Temporarily Busy" (defined in ITU-T Recommendation H.248.8 [i.13]) indicating a temporary busy condition in the MGC is received, the MG periodically repeats the MG TERMINATION OOS GRACEFUL procedure until a successful response is received. Furthermore the MG may adapt the ServiceChangeDelay timer accordingly. If multiple repetitions are needed, the repetition rate shall be continuously decreased over time. The minimum inter-transmit time under such conditions shall be 100 ms. NOTE 2: In case the MG termination procedure is to be repeated and if the corresponding MG termination has undergone a Service State change in the meantime, only the latest Service State is reported. This may imply a change of the procedure to be applied (e.g. MG TERMINATION AVAILABLE). 3) Additionally, at the end of the ServiceChangeDelay period, the MGC force releases any remaining calls that have not expired naturally and subtracts the terminations on the MG since the control association is still up. MG Termination OOS Graceful MGC MG MG Termination OOS Graceful Ack (expiry of graceful timer) Figure 10: MG Termination OOS Graceful Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.8 Disable Termination (Immediate) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a termination being taken out of service immediately. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.8.1 Disable Termination (Immediate) (at MGC) | The following H.248 procedures are performed: 1) The MGC force releases all affected calls/connections, subtracting appropriate terminations on the MG. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 22 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.8.2 Disable Termination (Immediate) (at MG) | This use case is triggered by management action that results in a MG termination being taken out of service immediately. The following H.248 procedures are performed: 1) The MG informs the MGC via the MG TERMINATION UNAVAILABLE procedure. If a successful response is obtained the termination is now out-of-service at both the MG and MGC. If a negative response/error descriptor with error code #511 "Temporarily Busy" (defined in ITU-T Recommendation H.248.8 [i.13]) indicating a temporary busy condition in the MGC is received, the MG periodically repeats the MG TERMINATION UNAVAILABLE procedure until a successful response is received. If multiple repetitions are needed, the repetition rate shall be continuously decreased over time. The minimum inter-transmit time under such conditions shall be 100 ms. NOTE: In case the MG termination procedure is to be repeated and if the corresponding MG termination has undergone a Service State change in the meantime, only the latest Service State is reported. This may imply a change of the procedure to be applied (e.g. MG TERMINATION AVAILABLE). 2) The MGC now force releases all affected calls/connections including subtracting appropriate terminations on the MG. MGC MG MG Termination Unavailable MG Termination Unavailable Ack Figure 11: MG Termination Unavailable Procedure |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 10.9 MG Failure and Recovery | This use case is triggered by a hardware/software failure on the MG. The following H.248 procedures are performed: 1) If possible, the MG informs the MGC via the MG SERVICE CANCELLATION (IMMEDIATE) procedure. The MGC force releases all affected calls. 2) On recovering, the MG restarts and informs the MGC. The procedures of clause 10.1.2 are applicable. MG Service Cancellation ( Immediate) MGC MG MG Service Cancellation (Immediate) Ack (MG recovery) See 10.1.2 Figure 12: MG Failure and Recovery Procedures ETSI ETSI TS 183 025 V2.5.1 (2009-04) 23 10.10 MG Termination Failure and Recovery This use case is triggered by a hardware/software failure on the MG termination (e.g. loss of synchronization on an E1). The following H.248 procedures are performed: 1) The MG informs the MGC via the MG TERMINATION UNAVAILABLE procedure. The MGC force releases any affected calls (and subtracts related terminations on the MG). 2) On the fault being cleared, the MG informs the MGC via the MG TERMINATION AVAILABLE procedure. MG Termination Unavailable MGC MG MG Termination Unavailable Ack (recovery of termination) MG Termination Available MG Termination Available Ack Figure 13: MG Termination Failure and Recovery Procedures 10.11 MGC Failure and Recovery This use case is triggered by a hardware/software failure on the MGC. The following H.248 procedures are performed: 1) During the outage, the procedures associated with the MG detecting the loss of the control association are applicable (see clause 10.13). 2) When the MGC recovers, the procedures of clause 10.2 are applicable. 10.12 User Plane Failure 10.12.1 Failure affecting a Single Termination This use case is triggered by the MG detecting loss of application data (e.g. RTP) on an ephemeral termination. The following H.248 procedures are performed: 1) During the establishment of the connection, the MGC is assumed to have armed the MG to report an appropriate ObservedEvent which would be associated with user plane failure. There are a number of events that could be used for this purpose (e.g. nt/netfail, nt/qalert (see clause E.11 of [i.5]), g/cause (see clause E.1 of [i.5], adid/ipstop (see [i.10]) etc.). 2) The MG detects loss of user plane data on one or more streams and notifies the MGC via the USER PLANE FAILURE procedure. The MG should avoid sending an avalanche of notifications where loss of user plane data is detected simultaneously across multiple ephemeral terminations. 3) On being informed of user plane failure, the MGC would typically remove the affected stream(s) and/or force release the affected call and subtract the related terminations. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 24 MGC MG User Plane Failure User Plane Failure Ack Figure 14: MG User Plane Failure Procedure 10.12.2 Failure affecting Multiple Terminations The events of previous clause may be applied as in this scenario as well. The major difference is the fact, that in this scenario the failure affects multiple ephemeral terminations in parallel. This may lead to a burst arrival of correspondent event notifications at the MGC. Alternative failure reporting could be based on the use of ServiceChange with appropriate wildcarding. 10.13 MGC-MG Control Association Failure and Recovery The general framework for "MGC-MG control association monitoring" is defined in clause 11.6 of [i.5]. If UDP transport is used to convey the H.248 signalling, then the control association is indirectly monitored via the Inactivity Package (see [i.7]). In this case, it is assumed that the MGC has previously initiated the inactivity timer on the MG via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure (see clause 10.1). This approach is based on the MGC being polled by the MG. An unsuccessful event notification can be the result of either a failure in the MGC entity, or a failure of the IP transport. If SCTP transport is used, then the SCTP association is monitored via SCTP procedures (which are out of scope of the present document) and the H.248 application layer is informed by the SCTP layer when the SCTP association goes down/comes up. The following H.248 procedures are performed: 1) For UDP transport, the MGC should endeavour to send at least one message to the MG during the period of the inactivity timer. If there are no call related messages, the MGC may use the CHECK MG AVAILABILITY procedure. If this procedure fails, the MGC periodically re-attempts the procedure to check if the control association is once more OK. 2) For UDP transport, on expiry of the inactivity timer, if the MG has received a message (including an acknowledgment) from the MGC during the inactivity timer period, then the MG resets the inactivity timer. 3) For UDP transport, on expiry of the inactivity timer, if the MG has not received a message (including an acknowledgment) from the MGC during the inactivity timer period, then the MG initiates the ROOT EVENT NOTIFICATION procedure to notify the MGC of the expired inactivity timer. 4) For UDP transport, if the ROOT EVENT NOTIFICATION procedure is successfully acknowledged, then the MG resets the inactivity timer. 5) For UDP transport, if no acknowledgement is received, then the control association is deemed to be down after normal H.248 retransmissions have occurred. 6) For UDP transport, the MG now attempts to re-establish the lost control association via the MG LOST COMMUNICATION (DISCONNECTED) procedure. If no acknowledgement is received (and H.248 retransmissions have occurred), then the MG attempts to establish an alternative control association via the MG LOST COMMUNICATION (FAILOVER) procedure. 7) For SCTP transport, on being informed by the SCTP layer that the SCTP association is now up, the MG re-establishes the H.248 control association via the MG LOST COMMUNICATION (DISCONNECTED) or MG LOST COMMUNICATION (FAILOVER) procedure (dependent on whether the new SCTP association is to the same MGC or different MGC as previously). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 25 8) When the control association is re-established, the MGC may optionally re-synchronize its data with the MG via the AUDIT ROOT PROPERTIES, CONTEXT AUDIT and AUDIT TERMINATION STATE procedures. 9) When the control association is re-established, the MG informs the MGC of the state of its terminations via the MG TERMINATION AVAILABLE/MG TERMINTION UNAVAILABLE procedure if any changes occurred which it was unable to report during the signalling link outage. 10) When the control association is re-established, commands that were buffered during the outage period may be sent. | Check MG Availability Ack Check MG Availability MGC1 MG ROOT Event Notification (inactivity timer) MG Lost Communication (Disconnected) ROOT Event Notification (inactivity timer) UDP transport (inactivity timer running) (timer expiry & reset) | (timer expiry) MG Lost Communication (Failover) Context Audit Context Audit Ack (start inactivity timer) Optional Audit Termination State Audit Termination State Ack If state changes occurred during outage MG Termination (Un)Available MG termination (Un)Available Ack Optional MG Lost Communication (Disconnected) | | MG Lost Communication (Failover) Ack A k MGC2 Audit ROOT Properties Audit ROOT Properties Ack Optional Figure 15: Control Association Failure and Recovery Procedures (UDP) ETSI ETSI TS 183 025 V2.5.1 (2009-04) 26 WC – I’ve ad | MGC MG MG Lost Communication (Disconnected / Failover ) MG Lost Communication (Disconnected / Failover) Ack A k STCP Transport (SCTP association failure) | (SCTP association OK) Context Audit Context Audit Ack Optional Audit Termination State Audit Termination State Ack Optional MG Termination (Un)Available MG termination (Un)Available Ack If state changes occurred during outage Optional Audit ROOT Properties Audit ROOT Properties Ack Figure 16: Control Association Failure and Recovery Procedures (SCTP) 10.14 MG Overload This use case is triggered by the MG entering an overloaded state. It is assumed that that MGC has previously armed the MG for notification of overload via the SET ROOT TERMINATION EVENTS/PROPERTIES procedure. Examples of packages for such notification would be the MG Overload Control Package (see [i.8]) or the MG Resource Handling Package (see [i.6]). The following H.248 procedures are performed: 1) The MG is then pushed into an overload state by excessive call related activity. 2) The MG informs the MGC of its overload condition via the ROOT EVENT NOTIFICATION procedure. If this notification is based on [i.8], then such a notification is triggered by the receipt of a new ADD request on the MG - else the notification may be sent autonomously. 3) On receipt of this notification, the MGC takes appropriate action to reduce the load offered to the MG. MGC MG ROOT Event Notification (MG overload) ROOT Event Notification Ack Figure 17: MG Overload Notification Procedure ETSI ETSI TS 183 025 V2.5.1 (2009-04) 27 10.15 MGC Overload This procedure is applicable only where the MGC is controlling MGs that are capable of generating traffic (e.g. an AGW). The following H.248 procedures are performed: 1) The MGC is pushed into an overload state by excessive call related activity. 2) The MGC informs its dependent MGs of its overload condition via the MGC OVERLOAD NOTIFICATION procedure. A suitable package for this notification would be [i.9]. 3) On receipt of this notification, the MG takes appropriate action to reduce the load offered to the MGC (see [i.9]). MGC MG MGC Overload Notification MGC Overload Notification Ack Figure 18: MGC Overload Procedure 10.16 MGC Hand-Off This use case is triggered by management action that results in the MGC moving an existing control association to an alternative MGC address (e.g. when a single-homed IP host MGC entity provides multiple IP ports for the IP transport connection; or when the MGC entity is realized as multi-homed IP host, i.e. provides multiple IP interfaces. The former "hand-off to an alternative address" relates then to an IP port redirection, the later to an IP interface redirection). This could be done as a load balancing exercise or as a pre-condition to taking a MGC out of service. The following H.248 procedures are performed: 1) The MGC requests its MGs to move an existing control association to a specified alternative MGC address via the MGC HANDOFF procedure. On receipt of this message, the MG then forms a new control association to the specified alternate MGC address via the MG RE-REGISTRATION (HANDOFF) procedure. MGC Hand-Off MGC (initial address) MG MGC Hand-Off Ack MG Re-Registration (Handoff) MG Re-Registration (Handoff) Ack MGC (alternative address) Figure 19: Hand-Off Procedures ETSI ETSI TS 183 025 V2.5.1 (2009-04) 28 10.17 MGC Triggered MG Redirect This use case is triggered by an MGC rejecting a registration request from an MG and providing an alternative MGC address in the response. This relates to a redirection of the IP port or the entire IP interface (see clause 10.16). This could be done as a load balancing exercise. The following H.248 procedures are performed: 1) The MGC on receipt of a registration request, provides an alternative MGC identity/address in the registration response. This is shown in the MG REGISTRATION REDIRECT procedure. The MG subsequently repeats the original registration request to the alternate MGC. MGC MG MG Registration MG Registration (Redirect) Ack Figure 20: MG Registration Redirect Procedure 10.18 MG Failover This use case is triggered by management action that results in the MG swapping over from a primary/worker MG to a secondary/standby MG. This swap over can either be initiated by the Primary MG or the Secondary MG. The following H.248 procedures are performed: Primary MG Initiated 1) The Primary MG is about to go out of service and wishes to relinquish processing to a Secondary MG. The Primary MG firstly informs the MGC that it is about to go out of service via the MG REDUNDANT TAKEOVER (PRIMARY) procedure. On completion of this procedure, the control association to the MGC is terminated. 2) The Secondary MG then registers with the MGC using the procedures in clause 10.1.2 (Warm Boot). MGC MG (secondary) MG Redundant Takeover (Primary) MG Redundant Takeover (Primary) Ack MG (primary) Warm Boot procedures Figure 21: MG REDUNDANT TAKEOVER (PRIMARY) Procedure Secondary MG Initiated 1) In this case, the Secondary MG initiates the swap over (e.g. by detecting the failure of the Primary MG) via the MG REDUNDANT TAKEOVER (SECONDARY) procedure. 2) On completion of this procedure, the control association is now established between the MGC and Secondary MG. The procedures in clause 10.1.2 (Cold/Warm Boot) from bullet 3 onwards are then are then applicable. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 29 MGC MG (secondary) W MG Redundant Takeover (Secondary) MG Redundant Takeover (Secondary) Ack Figure 22: MG REDUNDANT TAKEOVER (SECONDARY) Procedure 10.19 Change of MG Resources This use case is triggered by management action that results in a change to MG resources on an In-Service MG such that the applied change does not result in a Service Change message, but does require the MGC to be notified of the applied change via a H248 NOTIFY message. The MGC has previously armed the necessary event via the SET ROOT EVENTS/PROPERTIES procedure (see clause 10.1). 1) The MG's resources are changed via Management Configuration and the MG has been previously armed to inform the MGC of the related change. 2) The MG informs the MGC of the change in its resources via the ROOT EVENT NOTIFICATION procedure. ROOT Event Notification MGC MG W ROOT Event Notification Ack Figure 23: Change to MG Resources Procedure ETSI ETSI TS 183 025 V2.5.1 (2009-04) 30 11 Non-Call Related H.248 Procedures and their Contents Table 1 lists the procedures described in this clause. Table 1 Procedure Clause MG REGISTRATION (COLD BOOT) (see note) 11.1 MG Restoration (see note) 11.2 Packages Audit 11.3 Context Audit 11.4 MG Termination Available 11.5 MG Termination Unavailable 11.6 Audit Termination State 11.7 Set ROOT Termination Events/Properties 11.8 MGC INITIATED SERVICE RESTORATION 11.9 Check MG Availability 11.10 MG SERVICE CANCELLATION (GRACEFUL) 11.11 MG SERVICE CANCELLATION (IMMEDIATE) 11.12 MGC Hand-Off 11.13 MG RE-REGISTRATION (HANDOFF) (see note) 11.14 MG Termination OOS Graceful 11.15 MGC Overload Notification 11.16 MG Registration Redirect (see note) 11.17 User Plane Failure 11.18 ROOT EVENT NOTIFICATION 11.19 MG LOST COMMUNICATION (DISCONNECTED) 11.20 MG LOST COMMUNICATION (FAILOVER) 11.21 MG REDUNDANT TAKEOVER (PRIMARY) 11.22 MG RE-REGISTRATION (RESTART) 11.23 Wildcarded Subtract 11.24 MG REDUNDANT TAKEOVER (SECONDARY) 11.25 MGC INITIATED SERVICE CANCELLATION 11.26 Void 11.27 Audit ROOT Properties 11.28 NOTE: These procedures are initiated using H.248 version 1 and may be used to negotiate a higher protocol version. All other procedures are initiated using the negotiated protocol version. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 31 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.1 MG Registration (Cold Boot) | Table 2 shows the contents of the MG REGISTRATION (COLD BOOT) and MG REGISTRATION (COLD BOOT) Ack command/response pair. Table 2: MG Registration (Cold Boot) and MG Registration (Cold Boot) Ack Command/Response Initiated Information element name Information element required Information element description MG Registration (Cold Boot) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to RESTART. Reason M This information element indicates the reason for the command. This is set to 901 - "Cold Boot". Service Change Profile O Indicates the name of a supported H.248 profile. Protocol Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Registration (Cold Boot) Ack MGC Context M As received. Command M As received. Termination M As received. Protocol Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 32 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.2 MG Restoration | Table 3 shows the contents of the MG Restoration and MG Restoration Ack command/response pair. Table 3: MG Restoration and MG Restoration Ack Command/Response Initiated Information element name Information element required Information element description MG Restoration MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to RESTART. Reason M This information element indicates the reason for service change. This is set to 900 ("Service Restored") or 902 ("Warm Boot") or 916 ("Packages Change" ) or 917 ("Capabilities Change") or 918 "Cancel Graceful"). Service Change Profile O Indicates the name of a supported H.248 profile. Protocol Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Restoration Ack MGC Context M As received. Command M As received. Termination M As received. Protocol Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.3 Packages Audit | This procedure is typically performed against the ROOT termination, in which case the MG returns all supported packages. It is also possible for the MGC to request a packages audit against other than the ROOT termination (e.g. a circuit termination) in which case the MG returns the sub-set of the packages that are applicable to the termination type. However, it is recommended that a packages audit be performed on the ROOT termination since the MGC can be expected to know how the returned set of packages ought to be used in relation to its different termination types. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 33 Table 4 shows the contents of the Packages Audit and Packages Audit Ack command/response pair. Table 4: Packages Audit and Packages Audit Ack Command/Response Initiated Information element name Information element required Information element description Packages Audit MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Audit packages M This is the Audit Descriptor requesting "Packages". Packages Audit Ack MG Context M As received. Command M As received Termination M As received. Package List M The list of supported packages. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.4 Context Audit | This procedure is invoked by the MGC to check/determine the list of active contexts and related terminations on the MG. There are a number of variations to this audit dependent on the amount of information available to the MGC prior to the audit (e.g. context identity known or termination naming scheme known etc.). A MGC may choose to use one or a combination of these variations dependent on its specific audit requirements. Tables 5 to 8 shows the contents of the various Context Audit and Context Audit Ack command/response pair. Table 5: Context Audit and Context Audit Ack (termination id known) Command/Response Initiated Information element name Information element required Information element description Context Audit MGC Context M This information element indicates the H.248 context for the command. Set to ALL or NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination identity known by the MGC (e.g. aln/4). Audit Information O This is the Audit Descriptor requesting the appropriate information to be returned (e.g. "Media"). Context Audit Ack (see note) MG Context M The specific context with which the termination is currently associated. Command M As received. Termination M As received. Audited Information O The information requested. NOTE: In the event of a termination/context mismatch, then an error 435 would be returned. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 34 Table 6: Context Audit and Context Audit Ack (context known) Command/Response Initiated Information element name Information element required Information element description Context Audit MGC Context M This information element indicates the H.248 context for the command. Set to a specific (non NULL) value. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination identity or a wildcarded to ALL. Audit Information O This is the Audit Descriptor requesting the appropriate information to be returned (e.g. "Media"). Context Audit Ack MG Context M As received (see note). Command M As received. Termination(s) M As received (if a specific termination in the request), else a list of termination identities (if wildcarded in the request). Audited Information O The information requested (per termination). NOTE: In the event of the context not being known at the MG, an error 435 would be returned. Table 7: Context Audit and Context Audit Ack (termination id partly known) Command/Response Initiated Information element name Information element required Information element description Context Audit MGC Context M This information element indicates the H.248 context for the command. Set to ALL or NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to a partially wildcarded termination, e.g. ephemeral/5/*. Audit Information O This is the Audit Descriptor requesting the appropriate information to be returned. Context Audit Ack MG Context M One or more active contexts associated with the wildcarded termination identity (see note). Command M As received. Termination(s) M For each returned context, one or more matching terminations. Audited Information O The information requested. (per termination). NOTE: In the event of there a mismatch between the wildcarded termination and specified context, an error 431 would be returned. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 35 Table 8: Context Audit and Context Audit Ack (context list) Command/Response Initiated Information element name Information element required Information element description Context Audit MGC Context M This information element indicates the H.248 context for the command. Set to ALL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Context Audit Ack MG Context M One or more active contexts present on the MG. Command M Set to AUDIT VALUE. Termination(s) M For each returned context, the ROOT termination is returned. NOTE: In the event of there being a mismatch between the wildcarded termination and specified context, an error 431 would be returned. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.5 MG Termination Available | Table 9 shows the contents of the MG Termination Available and MG Termination Available Ack command/response pair. Table 9: MG Termination Available and MG Termination Available Ack Command/Response Initiated Information element name Information element required Information element description MG Termination Available MG Context M This information element indicates the H.248 context for the command. Set to NULL or specific. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination identity or a partially wildcarded identity (e.g. an E1). Method M This information element indicates the method for the command. This is set to RESTART. Reason M This information element indicates the reason for the command. This is set to 900 - "Service Restored". MG Termination Available Ack MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 36 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.6 MG Termination Unavailable | Table 10 shows the contents of the MG Termination Unavailable and MG Termination Unavailable Ack command/response pair. Table 10: MG Termination Unavailable and MG Termination Unavailable Ack Command/Response Initiated Information element name Information element required Information element description MG Termination Unavailable MG Context M This information element indicates the H.248 context for the command. Set to NULL, ALL or specific. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination identity or a partially wildcarded identity (e.g. an E1). Method M This information element indicates the method for the command. This is set to FORCED. Reason M This information element indicates the reason for the command. This is set to 904 ("Termination Malfunction") or 905 ("Termination Taken OOS") or 906 ("Loss of Lower Layer Connectivity"), or 907 ("Transmission Failure") or 910 ("Media Capability Failure") or 912 ("Mux Capability Failure") or 913 ("Signal Capability Failure") or 914 ("Event Capability Failure" or 915 ("State Loss"). MG Termination Unavailable Ack MGC Context M As received. Command M As received Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 37 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.7 Audit Termination State | Table 11 shows the contents of Audit Termination State and Audit Termination State Ack command/response pair. Table 11: Audit Termination State and Audit Termination State Ack Command/Response Initiated Information element name Information element required Information element description Audit Termination State MGC Context M This information element indicates the H.248 context for the command. Set to ALL or specific or NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination identity or a partially wildcarded identity (e.g. an E1). Audit Service State M This is the Audit Descriptor requesting the Service State in the Termination State Descriptor. Audit Termination State Ack MG Context M The specific/NULL context with which the termination is currently associated (see note). Command M As received Termination M As received. Service State M The Service State in the Termination State Descriptor. NOTE: If the termination does not match the specified context, then a 430 (wildcarded termination) or 435 (specific termination) error is returned. |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.8 Set ROOT Termination Events/Properties | Table 12 shows the contents of Set ROOT Termination Events/Properties and Set ROOT Termination Events/Properties Ack command/response pair. Table 12: Set ROOT Termination Events/Properties and Set ROOT Termination Events/Properties Ack Command/Response Initiated Information element name Information element required Information element description Set ROOT Termination Events/Properties MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to MODIFY. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. ROOT Properties O These are the ROOT level properties - e.g. "Normal MGC Execution Time". ROOT Events O These are the ROOT level events - e.g. notification of expiry of inactivity timer, notification of overload etc. Set ROOT Termination Events/Properties Ack MG Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 38 |
a95505b1e252f195bf707ee85ccce821 | 183 025 | 11.9 MGC Initiated Service Restoration | Table 13 shows the contents of the MGC Initiated Service Restoration and MGC Initiated Service Restoration Ack command/response pair. Table 13: MGC Initiated Service Restoration and MGC Initiated Service Restoration Ack Command/Response Initiated Information element name Information element required Information element description MGC Initiated Service Restoration MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to RESTART. Reason M This information element indicates the reason for the command. This is set to 900 ("Service Restored") or 901 ("Cold Boot"). MGC Initiated Service Restoration Ack MG Context M As received. Command M As received. Termination M As received. 11.10 Check MG Availability Table 14 shows the contents of the Check MG Availability and Check MG Availability Ack command/response pair. Table 14: Check MG Availability and Check MG Availability Ack Command/Response Initiated Information element name Information element required Information element description Check MG Availability MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Check MG Availability Ack MG Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 39 11.11 MG Service Cancellation (Graceful) Table 15 shows the contents of the MG Initial OOS Graceful and MG Service Cancellation (Graceful) Ack command/response pair. Table 15: MG Service Cancellation (Graceful) and MG Service Cancellation (Graceful) Ack Command/Response Initiated Information element name Information element required Information element description MG Service Cancellation (Graceful) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to GRACEFUL. Reason M This information element indicates the reason for the command. This is set to 908 - "MG Impending Failure" or 905 - "Termination OOS". Service Change Delay O Indicates the period before which the MG will go out of service. MG Service Cancellation (Graceful) Ack MGC Context M As received. Command M As received. Termination M As received. 11.12 MG Service Cancellation (Immediate) Table 16 shows the contents of the MG Service Cancellation (Immediate) and MG Service Cancellation (immediate) Ack command/response pair. Table 16: MG Service Cancellation (Immediate) and MG Service Cancellation (Immediate) Ack Command/Response Initiated Information element name Information element required Information element description MG Service Cancellation (Immediate) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to FORCED. Reason M This information element indicates the reason for the command. This is set to 908 - "MG Impending Failure" or 905 - "Termination Taken OOS". MG Service Cancellation (Immediate) Ack MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 40 11.13 MGC Hand-Off Table 17 shows the contents of the MGC Hand-Off and MGC Hand-Off Ack command/response pair. Table 17: MGC Hand-Off and MGC Hand-Off Ack Command/Response Initiated Information element name Information element required Information element description MGC Hand-Off MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to HANDOFF. Reason M This information element indicates the reason for the command. This is set to 903 - "MGC Directed Change". Alternate MGC Id M This is the alternate MGC Identity (see note) to which the control association should be moved. MG Hand-Off Ack MG Context M As received. Command M As received. Termination M As received. NOTE: The ServiceChangeMgcID parameter is of type Message Identifier (MID, see clause 8.3/H.248.1 [i.5]), the parameter format represents thus either an address (IP version 4 or 6 domain address; broadband MTP3 address) or a name (IP domain name or a generic device name). In both cases the parameter is used for an unambiguous identification of an MGC entity (i.e. a primary or secondary MGC). Names require firstly a resolution into a routable address. The name-to-address resolution by the MG requires a local or remote DNS query request in case of the domain format, or a local mapping table in case of the device format. Each name resolution is related to the "pre-configured list of MGC entities" in the MG see clause 11.5/H.248.1 [i.5]). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 41 11.14 MG Re-Registration (Handoff) Table 18 shows the contents of the MG Re-Registration (Handoff) and MG Re-Registration (Handoff) Ack command/response pair. Table 18: MG Re-Registration (Handoff) and MGC Re-Registration (Handoff) Ack Command/Response Initiated Information element name Information element required Information element description MG Re-Registration (Handoff) Request MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to HANDOFF. Reason M This information element indicates the reason for the command. This is set to 903 - "MGC Directed Change". Service Change Profile O Indicates the name of a supported H.248 profile. Protocol Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Re-Registration (Handoff) Ack MGC Context M As received. Command M As received. Termination M As received. Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. Protocol Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 42 11.15 MG Termination OOS Graceful Table 19 shows the contents of the MG Termination OOS Graceful and MG Termination OOS Graceful Ack command/response pair. Table 19: MG Termination OOS Graceful and MG Termination OOS Graceful Ack Command/Response Initiated Information element name Information element required Information element description MG Termination OOS Graceful MG Context M This information element indicates the H.248 context for the command. Set to ALL, NULL or SPECIFIC (dependent on whether the termination identity is partially wildcarded or not). Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to a specific termination or a partially wildcarded identity (e.g. an E1). Method M This information element indicates the method for the command. This is set to GRACEFUL. Reason M This information element indicates the reason for the command. This is set to 905 - "Termination OOS". Service Change Delay M Indicates the period before which the MG will go out of service. MG Termination OOS Graceful Ack MGC Context M As received. Command M As received. Termination M As received. 11.16 MGC Overload Notification Table 20 shows the contents of MGC Overload Notification and MGC Overload Notification Ack command/response pair. Table 20: MGC Overload Notification and MGC Overload Notification Ack Command/Response Initiated Information element name Information element required Information element description MGC Overload Notification MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to MODIFY. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Overload Notification M This information element indicates that the MGC is in overload. MGC Overload Notification Ack MG Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 43 11.17 MG Registration Redirect Table 21 shows the contents of the MG Registration and MG Registration (Redirect) Ack command/response pair. Table 21: MG Registration Redirect Command/Response Initiated Information element name Information element required Information element description MG Registration MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to RESTART or DISCONNECTED or HANDOFF or FAILOVER. Reason M This information element indicates the reason for the command. This is set dependent on the METHOD. Service Change Profile O Indicates the name of a supported H.248 profile. Protocol Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Registration (Redirect) Ack MGC Context M As received. Command M As received. Termination M As received. Protocol Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. Alternate MGC Id M This element enables the MGC to inform the MG that it should redirect its Service Change to an alternative address (see note). The MG will now repeat the MG REGISTRATION (COLD BOOT) procedure to this alternate address. NOTE: See also note in table 17. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 44 11.18 User Plane Failure Table 22 shows the contents of User Plane Failure and User Plane Failure Ack command/response pair. Table 22: User Plane Failure and User Plane Failure Ack Command/Response Initiated Information element name Information element required Information element description User Plane Failure MG Context M This information element indicates the H.248 context for the command. Set to a specific value. Command M This is the H.248 Command. Set to NOTIFY. Termination M This information element indicates the H.248 termination for the command. This is set to a specific ephemeral termination identity. User Plane Failure M This information element indicates that a failure in the user plane has been detected (e.g. nt/netfail, g/cause etc.). User Plane Failure Ack MGC Context M As received. Command M As received. Termination M As received. 11.19 Root Event Notification Table 23 shows the contents of the Root Event Notification and Root Event Notification Ack command/response pair. Table 23: Root Event Notification and Root Event Notification Ack Command/Response Initiated Information element name Information element required Information element description Root Event Notification MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to NOTIFY. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. ROOT events M This information element indicates the detected ROOT event (e.g. expiry of inactivity timer, MG Overload Notification or change to IP Realm Availability). Root Event Notification ACK MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 45 11.20 MG Lost Communication (Disconnected) Table 24 shows the contents of the MG Lost Communication (Disconnected) and MG Lost Communication (Disconnected) Ack command/response pair. Table 24: MG Lost Communication (Disconnected) and MG Lost Communication (Disconnected) Ack Command/Response Initiated Information element name Information element required Information element description MG Lost Communication (Disconnected) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to DISCONNECTED. Reason M This information element indicates the reason for the command. This is set to 900 "Service Restored". MG Lost Communication (Disconnected) Ack MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 46 11.21 MG Lost Communication (Failover) The MG attempts to establish a new control association using its list of pre-provisioned MGC identities. The MG cycles though its list until a successful response is received. This procedure may be part of a MGC failover procedure, e.g. the MG is initiating a changeover from the original primary MGC to a next secondary MGC. Table 25 shows the contents of the MGC Failover -Establish New Control Association and MGC Failover -Establish new Control Association Ack command/response pair. Table 25: MG Lost Communication (Failover) and MG Lost Communication (Failover) Ack Command/Response Initiated Information element name Information element required Information element description MG Lost Communication (Failover) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to FAILOVER. Reason M This information element indicates the reason for the command. This is set to 909 - "MGC Impending Failure". Service Change Profile O Indicates the name of a supported H.248 profile. Protocol Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Lost Communication (Failover) Ack MGC Context M As received. Command M As received. Termination M As received. Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. Protocol Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 47 11.22 MG Redundant Takeover (Primary) Table 26 shows the contents of the MG Redundant Takeover (Primary) and MG Redundant Takeover (Primary) Ack command/response pair. Table 26: MG Redundant Takeover (Primary) and MG Redundant Takeover (Primary) Ack Command/Response Initiated Information element name Information element required Information element description MG Redundant Takeover (Primary) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to FAILOVER. Reason M This information element indicates the reason for the command. This is set to 908 - "MG Impending Failure". MG Redundant Takeover (Primary) Ack MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 48 11.23 MG Re-Registration (Restart) Table 27 shows the contents of the MG Re-Registration (Restart) and MG Re-Registration (Restart) Ack command/response pair. Table 27: MG Re-Registration (Restart) and MG Re-Registration (Restart) Ack Command/Response Initiated Information element name Information element required Information element description MG Re-Registration (Restart) MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to RESTART. Reason M This information element indicates the reason for the command. This is set to the value received from the MGC during the MGC INITIATED SERVICE RESTORATION procedure - see clause 11.9. Service Change Profile O Indicates the name of a supported H.248 profile. Service Change Version O Indicates the highest H.248 version supported by the MG - if other than 1. MG Re-Registration (Restart) Ack MG Context M As received. Command M As received. Termination M As received. Service Change Profile O This information element indicates the profile (name and version) supported by the MGC if different from that proposed by the MG. Service Change Version O If the highest protocol version supported by the MGC is lower than that proposed by the MG, this parameter must be included. If the highest protocol version supported by the MGC is equal to that proposed by the MG, this parameter may be included. Note that if the protocol version supported by the MGC is greater than that proposed by the MG, the command is rejected with an error response 406 ("Version Not Supported"). ETSI ETSI TS 183 025 V2.5.1 (2009-04) 49 11.24 Wildcarded Subtract Table 28 shows the contents of the Wildcarded Subtract and Wildcarded Subtract Ack command/response pair. Table 28: Wildcarded Subtract and Wildcarded Subtract Ack Command/Response Initiated Information element name Information element required Information element description Wildcarded Subtract MGC Context M This information element indicates the H.248 context for the command. Set to ALL. Command M This is the H.248 Command. Set to SUBTRACT or W-SUBTRACT. Termination M This information element indicates the H.248 termination for the command. This is set to ALL or a partially wildcarded identity (e.g. ip/2/*). Wildcarded Subtract Ack MG Context M As received (if W prefix used), else a list of specific context IDs. Command M As received. Termination M As received (if W prefix used), else a list of specific IDs. 11.25 MG Redundant Takeover (Secondary) Table 29 shows the contents of the MG Redundant Takeover (Secondary) and MG Redundant Takeover (Secondary) Ack command/response pair. Table 29: MG Redundant Takeover (Secondary) and MG Redundant Takeover (Secondary) Ack Command/Response Initiated Information element name Information element required Information element description MG Redundant Takeover (Secondary) MG Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to FAILOVER. Reason M This information element indicates the reason for the command. This is set to 919 - "Warm Failover" or 920 - "Cold Failover". MG Redundant Takeover (Secondary) Ack MGC Context M As received. Command M As received. Termination M As received. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 50 11.26 MGC Initiated Service Cancellation Table 30 shows the contents of the MGC Initiated Service Cancellation and MGC Initiated Service Cancellation Ack command/response pair. Table 30: MGC Initiated Service Cancellation and MGC Initiated Service Cancellation Ack Command/Response Initiated Information element name Information element required Information element description MGC Initiated Service Cancellation MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to SERVICE CHANGE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Method M This information element indicates the method for the command. This is set to FORCED. Reason M This information element indicates the reason for the command. This is set to 905 - "Termination taken out of service". MGC Initiated Service Cancellation Ack MG Context M As received. Command M As received. Termination M As received. 11.27 Void 11.28 Audit ROOT Properties This procedure is performed against the ROOT termination to enable the MGC to determine the values of any ROOT termination properties on the MG. Table 31 shows the contents of the Audit ROOT Properties and Audit ROOT Properties Ack command/response pair. Table 31: Audit ROOT Properties and Audit ROOT Properties Ack Command/Response Initiated Information element name Information element required Information element description Audit ROOT Properties MGC Context M This information element indicates the H.248 context for the command. Set to NULL. Command M This is the H.248 Command. Set to AUDIT VALUE. Termination M This information element indicates the H.248 termination for the command. This is set to ROOT. Audit Properties M This is the list of ROOT properties required to be audited by the MGC. Audit ROOT Properties Ack MG Context M As received. Command M As received. Termination M As received. Root Properties M The returned list of ROOT property values as requested by the MGC. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 51 Annex A (informative): Stage 3 Non-Call Related H.248 Procedures and their Contents This annex provides exemplar stage 3 H248 message equivalents of the procedures in clause 11. A.1 MG Registration (Cold Boot) The MG sends SERVICE CHANGE command as in table A.1. Table A.1: MG Registration (Cold Boot) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = RESTART SC Reason = 901 If applicable: H248 Profile Identity H248 Protocol Version The MGC responds as in table A.2. Table A.2: MG Registration (Cold Boot) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If applicable:- H248 Profile Identity H248 Protocol Version An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason='901', Profile=ProfileName/1, Version=2}}}} Reply=1002{Context=-{ServiceChange = ROOT }} A.2 MG Restoration The MG sends SERVICE CHANGE command as in table A.3. Table A.3: MG Restoration Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = RESTART SC Reason = 900,902, 916, 917 or 918 If applicable:- H248 Profile Identity H248 Protocol Version ETSI ETSI TS 183 025 V2.5.1 (2009-04) 52 The MGC responds as in table A.4. Table A.4: MG Restoration Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If applicable:- H248 Profile Identity H248 Protocol Version An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason='900', Profile=ProfileName/1, Version=2}}}} Reply=1002{Context=-{ServiceChange = ROOT }} A.3 Packages Audit The MGC sends an AUDIT VALUE request command as in table A.5. Table A.5: Packages Audit Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT Audit Packages The MG responds as in table A.6. Table A.6: Packages Audit Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT Packages List An example message exchange would be: Transaction=1002{Context=- { AuditValue=ROOT{ Audit{Packages}}}} Reply=1002{Context=-{AuditValue = ROOT {Packages { g-2,root-2, nt-1, xdd-1…….etc.}}}} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 53 A.4 Context Audit A number of different context audits are possible, dependent on what information is already known and what information is required to be returned in the audit response. The MGC audits the MG by sending an AUDIT VALUE request to the MG. The required information is returned in the response. Table A.7: Context Audit Request (Termination Id known) Address Information Control information Bearer information Transaction ID = x Context ID = * OR - Termination ID = specific If required Required Audit Info Table A.8: Context Audit Request Ack (Termination Id known) Address Information Control information Bearer information Transaction ID = x Context ID = specific OR - Termination ID = specific If requested:- Audit Info An example message exchange would be: Transaction=1002{Context=* { AuditValue=aln/4{ Audit{}}}} Reply=1002{Context=12{AuditValue = aln/4}} Table A.9: Context Audit Request (Context Id known) Address Information Control information Bearer information Transaction ID = x Context ID = specific Termination ID = * OR specific If required Required Audit Info Table A.10: Context Audit Request Ack (Context Id known) Address Information Control information Bearer information Transaction ID = x Context ID = specific Termination ID = specific If requested:- Audit Info An example message exchange would be: Transaction=1002{Context=12 { AuditValue=*{ Audit{}}}} Reply=1002{Context=12{AuditValue = aln/4, AuditValue=ephemeral/23}} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 54 Table A.11: Context Audit Request (Termination Id partially wildcarded) Address Information Control information Bearer information Transaction ID = x Context ID = * Termination ID = Partially Wildcarded If required Required Audit Info Table A.12: Context Audit Request Ack (Termination Id partially wildcarded) Address Information Control information Bearer information Transaction ID = x Context ID = specific (list) Termination ID = specific (list) If requested:- Audit Info An example message exchange would be: Transaction=1002{Context=* { O-AuditValue=tdm/e1_3/*{ Audit{ }}}} Reply=1002{Context=12{AuditValue = tdm/e1_3/4}, Context=15{AuditValue=tdm/e1_3/12}, Context=23{AuditValue=tdm/e1_3/21}} Table A.13: Context Audit Request (to obtain context list) Address Information Control information Bearer information Transaction ID = x Context ID = * Termination ID = ROOT Table A.14: Context Audit Request Ack (to obtain context list) Address Information Control information Bearer information Transaction ID = x Context ID = specific (list) Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=* { W-AuditValue=ROOT{ Audit{ }}}} Reply=1002{Context=10{AuditValue = ROOT}, Context=24{AuditValue=ROOT}, Context=45{AuditValue=ROOT}} A.5 MG Termination Available The MG sends SERVICE CHANGE command as in table A.5.1. Table A.15: MG Termination Available Request Address Information Control information Bearer information Transaction ID = x Context ID = - OR specific Termination ID = Specific or Partially Wildcarded SC Method = RESTART SC Reason = 900 ETSI ETSI TS 183 025 V2.5.1 (2009-04) 55 The MGC responds as in table A.16. Table A.16: MG Termination Available Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = Specific or Partially Wildcarded An example message exchange would be: Transaction=1002{Context=- { ServiceChange=aln/1{ Services{Method=Restart, Reason='900'}}}} Reply=1002{Context=-{ServiceChange = aln/1}} A.6 MG Termination Unavailable The MG sends SERVICE CHANGE command as in table A.17. Table A.17: MG Termination Available Request Address Information Control information Bearer information Transaction ID = x Context ID = - OR * OR specific Termination ID = Specific or Partially Wildcarded SC Method = FORCED SC Reason = 904-907, 910, 912-915 The MGC responds as in table A.18. Table A.18: MG Termination Available Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = Specific or Partially Wildcarded An example message exchange would be: Transaction=1002{Context=- { ServiceChange=aln/1{ Services{Method=Forced, Reason='905'}}}} Reply=1002{Context=-{ServiceChange = aln/1}} A.7 Audit Termination State The MGC sends an AUDIT VALUE command as in table A.19. Table A.19: Audit Termination State Request Address Information Control information Bearer information Transaction ID = x Context ID = - OR * OR specific Termination ID = Specific or Partially Wildcarded Audit Service State ETSI ETSI TS 183 025 V2.5.1 (2009-04) 56 The MG responds as in table A.20. Table A.20: MG Termination Available Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - OR specific Termination ID = Specific or Partially Wildcarded Service State An example message exchange would be: Transaction=1002{Context=- { AuditValue=aln/1{ Audit{Media{TerminationState{ServiceState}}}}}} Reply=1002{Context=-{AuditValue = aln/1{ServiceState=InService}}} A.8 Set ROOT Termination Events/Properties The MGC sends a MODIFY request command as in table A.21. Table A.21: Set ROOT Events/Properties Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If required: Set Inactivity Timer Request Overload Notification The MG responds as in table A.22. Table A.22: Set ROOT Events/Properties Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { Modify=ROOT{ Events{it/ito{mit=30000}, ocp/mg_overload}}}} Reply=1002{Context=-{Modify = ROOT}} A.9 MGC Initiated Service Restoration The MGC sends SERVICE CHANGE command as in table A.23. Table A.23: MGC Initiated Service Restoration Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = RESTART SC Reason = 900 or 901 ETSI ETSI TS 183 025 V2.5.1 (2009-04) 57 The MG responds as in table A.24. Table A.24: MGC Initiated Service Restoration Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason='901'}}}} Reply=1002{Context=-{ServiceChange = ROOT}}} A.10 Check MG Availability The MGC sends an AUDIT VALUE command as in table A.25. Table A.25: Audit Termination State Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT The MG responds as in table A.26. Table A.26: MG Termination Available Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { AuditValue=ROOT{ Audit{}}}} Reply=1002{Context=-{AuditValue = ROOT}} A.11 MG Service Cancellation (Graceful) The MG sends SERVICE CHANGE command as in table A.27. Table A.27: MG Service Cancellation (Graceful) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = GRACEFUL SC Reason = 905, 908 Service Change Delay ETSI ETSI TS 183 025 V2.5.1 (2009-04) 58 The MGC responds as in table A.28. Table A.28: MG Service Cancellation (Graceful) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Graceful, Reason='908', Delay=600}}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.12 MG Service Cancellation (Immediate) The MG sends SERVICE CHANGE command as in table A.29. Table A.29: MG Service Cancellation (Immediate) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = FORCED SC Reason = 905, 908 The MGC responds as in table A.30. Table A.30: MG Service Cancellation (Immediate) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Forced, Reason='905'}}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.13 MGC Hand-Off The MGC sends SERVICE CHANGE command as in table A.31. Table A.31: MGC Hand-Off Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = HANDOFF SC Reason = 903 SC MGCId = Alternate MGCId ETSI ETSI TS 183 025 V2.5.1 (2009-04) 59 The MG responds as in table A.32. Table A.32: MGC Hand-Off Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be (see note): Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Handoff, Reason='903', MgcIdToTry=1.2.3.4}}}} Reply=1002{Context=-{ServiceChange = ROOT}} NOTE: The ServiceChangeMgcID parameter is of type "IP version 4 address". The parameter value provides a port-less IP address, i.e. the well-known port (2944 for text, 2945 for binary encoding) is used at the redirected IP interface. A.14 MG Re-Registration (Handoff) The MG sends SERVICE CHANGE command as in table A.33. Table A.33: MG Re-Registration (Handoff) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = HANDOFF SC Reason = 903 If applicable:- H248 Profile Identity H248 Protocol Version The MGC responds as in table A.34. Table A.34: MG Re-Registration (Handoff) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If applicable:- H248 Profile Identity H248 Protocol Version An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Handoff, Reason='903', Profile=ProfileName/1, Version=2}}}} Reply=1002{Context=-{ServiceChange = ROOT }} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 60 A.15 MG termination OOS (Graceful) The MG sends SERVICE CHANGE command as in table A.35. Table A.35: MG Termination OOS Graceful Request Address Information Control information Bearer information Transaction ID = x Context ID = * OR specific OR - Termination ID = specific OR Partially Wildcarded SC Method = GRACEFUL SC Reason = 908 Service Change Delay The MGC responds as in table A.36. Table A.36: MG Termination OOS Graceful Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = * OR specific OR - Termination ID = Specific OR partially wildcarded An example message exchange would be: Transaction=1002{Context=34{ ServiceChange=aln/16{ Services{Method=Graceful, Reason='908', Delay=600}}}} Reply=1002{Context=34{ServiceChange = aln/16}} A.16 MGC Overload Notification The MGC sends a MODIFY request command as in table A.37. Table A.37: MGC Overload Notification Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT Overload Notification The MG responds as in table A.38. Table A.38: MGC Overload Notification Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { Modify=ROOT{ Media{TerminationState{etsi_nr=1.34}}}}} Reply=1002{Context=-{Modify = ROOT }} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 61 A.17 MG Registration Redirect The MG sends SERVICE CHANGE command as in table A.39. Table A.39: MG Registration Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = RESTART or DISCONNECTED or HANDOFF or FAILOVER SC Reason = 901 or others If applicable:- H248 Profile Identity H248 Protocol Version The MGC responds as in table A.40. Table A.40: Registration Redirect Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT Alternate MGC Address (see note) If applicable:- H248 Profile Identity H248 Protocol Version NOTE: See also note in table 11.13-1. An example message exchange would be (see note): Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason='901', Profile=ProfileName/1, Version=2}}}} Reply=1002{Context=-{ServiceChange = ROOT {Services { MGCIdToTry=1.2.3.4}}}} NOTE: The ServiceChangeMgcID parameter is of type "IP version 4 address". The parameter value provides a port-less IP address, i.e. the well-known port (2944 for text, 2945 for binary encoding) is used at the redirected IP interface. A.18 User Plane Failure During call related procedures, the MGC has previously armed for the nt/netfail event. If so, and user plane failure is detected by the MG, then the MG sends a NOTIFY request command as in table A.41. Table A.41: User Plane Failure Address Information Control information Bearer information Transaction ID = x Context ID = specific Termination ID = specific Network Failure ETSI ETSI TS 183 025 V2.5.1 (2009-04) 62 The MGC responds as in table A.42. Table A.42: User Plane Failure Ack Address Information Control information Bearer information Transaction ID = x Context ID = specific Termination ID = specific An example message exchange would be: Transaction=1002{Context=1 { Notify=ephemeral/2{ ObservedEvents{nt/netfail{stream=1}}}}} Reply=1002{Context=1 {Notify = ephemeral/2}} A.19 Root Event Notification The MG sends a NOTIFY request command as in table A.43. Table A.43: Root Event Notification Address Information Control information Bearer information Transaction ID = x Context ID= - Termination ID = ROOT Notified ROOT Event The MGC responds as in table A.44. Table A.44: Root Event Notification Request ACK Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be : Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{it/ito}}}} OR Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{ocp/mg_overload}}}} OR Transaction=1002{Context=- { Notify=ROOT{ ObservedEvents{ipra/arc{nar=[“1”,”5”]}}}}} Reply=1002{Context=-{Notify = ROOT }} A.20 MG Lost Communication (Disconnected) The MG sends a SERVICE CHANGE command as in table A.45. Table A.45: MG Lost Communication (Disconnected) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = DISCONNECTED SC Reason = 900 ETSI ETSI TS 183 025 V2.5.1 (2009-04) 63 The MGC responds as in table A.46. Table A.46: MG Lost Communication (Disconnected) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Disconnected, Reason='900'}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.21 MG Lost Communication (Failover) The MG sends SERVICE CHANGE command as in table A.47. Table A.47: MG Lost Communication (Failover) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = FAILOVER SC Reason = 909 If applicable:- H248 Profile Identity H248 Protocol Version The MGC responds as in table A.48. Table A.48: MG Lost Communication (Failover) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If applicable:- H248 Profile Identity H248 Protocol Version Alternate MGC Address (see note) NOTE: See also note in table 17. An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Failover, Reason='909', Profile=ProfileName/1, Version=2}}}} Reply=1002{Context=-{ServiceChange = ROOT }} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 64 A.22 MG Redundant Takeover (Primary) The MG sends SERVICE CHANGE command as in table A.49. Table A.49: MG Redundant Takeover (Primary) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = FAILOVER SC Reason = 908 The MGC responds as in table A.50. Table A.50: MG Redundant Takeover (Primary) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Failover, Reason='908'}}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.23 MG Re-Registration (Restart) The MG sends SERVICE CHANGE command as in table A.51. Table A.51: MG Re-Registration (Restart) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = RESTART SC Reason = 900 or 901 If applicable:- H248 Profile Identity H248 Protocol Version The MGC responds as in table A.52. Table A.52: MG Re-Registration (Restart) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT If applicable:- H248 Profile Identity H248 Protocol Version ETSI ETSI TS 183 025 V2.5.1 (2009-04) 65 An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Restart, Reason="901", Profile=ProfileName/1, Version=2 }}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.24 Wildcarded Subtract The MGC sends a SUBTRACT or W-SUBTRACTcommand as in table A.53. Table A.53: Wildcarded Subtract Address Information Control information Bearer information Transaction ID = x Context ID = * Termination ID = * OR partially wildcarded The MG responds as in table A.54. Table A.54: Wildcarded Subtract Ack Address Information Control information Bearer information Transaction ID = x Context ID = * Termination ID = * OR partially wildcarded An example message exchange would be: Transaction=1002{Context=* { W-Subtract=*{ Audit{}}}} Reply=1002{Context=*{Subtract= *}} A.25 MG Redundant Takeover (Secondary) The MG sends SERVICE CHANGE command as in table A.55. Table A.55: MG Redundant Takeover (Secondary) Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = FAILOVER SC Reason = 919, 920 The MGC responds as in table A.56. Table A.56: MG Redundant Takeover (Secondary) Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT ETSI ETSI TS 183 025 V2.5.1 (2009-04) 66 An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Failover, Reason='919'}}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.26 MGC Initiated Service Cancellation The MGC sends a SERVICE CHANGE command as in table A.57. Table A.57: MGC Initiated Service Cancellation Request Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT SC Method = FORCED SC Reason = 905 The MG responds as in table A.58. Table A.58: MGC Initiated Service Cancellation Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT An example message exchange would be: Transaction=1002{Context=- { ServiceChange=ROOT{ Services{Method=Forced, Reason='905'}}}} Reply=1002{Context=-{ServiceChange = ROOT}} A.27 Void A.28 Audit ROOT Properties The MGC sends an AUDIT VALUE request command as in table A.59. Table A.59: Audit ROOT Properties Request Address Information Control information Bearer information Transaction ID = x Context ID= - Termination ID = ROOT Audit ROOT Properties The MG responds as in table A.60. Table A.60: Audit ROOT Properties Request Ack Address Information Control information Bearer information Transaction ID = x Context ID = - Termination ID = ROOT ROOT Properties ETSI ETSI TS 183 025 V2.5.1 (2009-04) 67 An example message exchange would be: Transaction=1002{Context=- { AuditValue=ROOT{ Audit{Media{TerminationState{root/*}}}}}} Reply=1002{Context=-{AuditValue = ROOT { Media{TerminationState {root/maxNumberOContexts=1000, root/maxTerminationsPerContext=2, root/normalMGExecutionTime=2, root/normalMGCExecutionTime=2, root/MGProvisionalResponseTimerValue=5, root/MGCProvisionalResponseTimerValue=5, root/MGCOriginatedPendingLimit=10, root/MGOriginatedPendingLimit=10}}}}} ETSI ETSI TS 183 025 V2.5.1 (2009-04) 68 Annex B (informative): Relation of the H.248 ServiceStates Property Model with Management Models This annex provides an example for mapping H.248 ServiceStates to a management state model and vice versa. B.1 Introduction The majority of H.248 procedures are independent of the management plane, i.e. "interactionless" procedures. However some procedures should consider potential interaction aspects between control plane (here H.248) and management plane. Such interactions might be loosely coupled like in case of provisioning or pre-provisioning activities, but there are also some more tightly coupled interactions, particularly in the area of the ServiceChange Command. For instance, certain actions, which are resulting in H.248 or management state changes, may result in correspondent state changes in the management or H.248 model respectively. B.2 Scope The scope of the present document is only on the H.248 ServiceStates Property state model. The H.248 ServiceChange Command model (see annex F ITU-T Recommendation H.248.1 [i.5]) is not considered. The indicated management technologies and correspondent management state models are just examples. There are many other possibilities in mapping the H.248 ServiceStates Property on dedicated management state models. From that perspective, the present document may assist to correlate such management state models with the H.248 ServiceStates Property. The present document provides an example mapping between the H.248 ServiceStates Property states and management plane state models according ITU-T Recommendation X.731 [i.12] and RFC 4268 [i.11]. Other management plane models could be used as well for correlation with the H.248 ServiceStates Property states. For such models the documented mapping could be used as guideline. B.3 Mapping between Models B.3.1 Example Management Models It is proposed to consider the management models from ITU-T Recommendation X.731 [i.12] and RFC 4268 [i.11] as example. One reason for a management model using ITU-T and IETF technologies is related to the origins of H.248 in these two standardization development organizations (SDO). Another motivation is the fact that RFC 4268 [i.11] refers explicitly to ITU-T Recommendation X.731 [i.12] and provides already an aligned management model (on top level). Management models are typically distinguishing three different basic state models, which are related to the three primary factors that are affecting the management state of a managed object with regard to its corresponding resources' availability: operability, administration and usage. The correspondent three basic management state models could be combined. The correlation with the H.248 ServiceStates Property with a single basic management state model (from RFC 4268 [i.11]), i.e. the operational state model, administrative state model or usage state model, may be used as starting point, but is typically not sufficient, e.g. when considering interactions between H.248 procedures and management procedures. For this reason is a combined management state model proposed, based on the combination of operational and administrative states, see table B. 1. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 69 Table B.1: Basic Model Relations Relation of H.248 ServiceStates Property Model with Management Models Control State Model ITU-T Recommendation H.248 Management State Models ITU-T Recommendation X.731 [i.12] / RFC 4268 [i.11] ServiceStates Property ↔ Operational State Administrative State Usage State In-Service ↔ Enabled Unlocked ⎯ Out-of-Service ↔ Disabled Unlocked ⎯ Out-of-Service ↔ Enabled Locked ⎯ Out-of-Service ↔ Disabled Locked ⎯ See note 1 ↔ Enabled Shutting Down ⎯ Test ↔ See note 2 See note 2 ⎯ NOTE 1: There is no explicit state modelled. "Test" is rather indicated via status attributes, which are used to qualify operational, administrative or usage states. Relevant in case of test might be the availability status attribute "in test", or the control status attributes "subject to test" or "reserved for test". NOTE 2: There is no explicit state modelled concerning H.248 ServiceStates Property. There might be a transient state in the H.248 ServiceChange Command model, but this is out of scope here. Other mapping schemes are principally possible. B.4 Interaction Aspects Purpose of this clause is to illustrate principle interaction between management use cases and H.248 procedures. Only a few examples are shown. A comprehensive list of all potential interaction aspects is out of scope of the present document. B.4.1 Effect of H.248 Actions on Management Models Some ServiceChange procedures may affect the H.248 ServiceStates Property. For instance, the ServiceStates Property of a physical Termination could be changed from In-Service to Out-of-Service with a ServiceChangeMethod of "Forced" or "Graceful" and ServiceChangeReason #905 ("Termination taken out of service"), see clause F.3.10.2 of [i.5]. Such a ServiceStates Property change may lead to a state transition in the management model from {enabled, unlocked} to {disabled, unlocked} when using the sample mapping of clause 3.2. That means that the operational state would change. Such a state change in the management model would be visible for the management system, but would not lead to a notification of the management system because the operational state is read-only in nature (see clause 7.1.1 of ITU-T Recommendation X.731 [i.12]). B.4.2 Effect of Management Model State Transition on H.248 Model Only management actions in the areas of configuration management and/or fault management may principally have an interaction with the H.248 ServiceStates Property. B.4.2.1 Configuration management The management action is triggering an H.248 ServiceChange procedure. The management action may lead to a state transition in the management model, and also to a correspondent change of the H.248 ServiceStates Property. See also clause 10. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 70 B.4.2.2 Fault management There are not any effects here because the flow of information is typically from the managed entity towards the management systems (see also next clause). B.4.3 Effect of failures in H.248 entities on State Transition in Management Model and H.248 Model Such a failure scenario in an H.248 entity itself is triggering. See also clause 10. 1) an H.248 ServiceChange procedure; and also 2) a notification (e.g. alarm) of the management system. There may be correspondent state transitions in the management model and the H.248 ServiceStates Property model. ETSI ETSI TS 183 025 V2.5.1 (2009-04) 71 Annex C (informative): Change history Change history Date WG Doc. CR Rev CAT Title / Comment Curren t Versio n New Version 01-07-08 18WTD229r1 012 F Editorial changes and corrections 2.2.0 2.2.1 01-07-08 18WTD230r1 013 F Changes to Disable Termination procedure 2.2.0 2.2.1 07-08 TB approval of CRs 012 and 013 2.2.1 2.3.0 23-09-08 18bTD160r1 014 F Addition of new procedure for MG Resources Change 2.3.0 2.3.1 14-11-08 TB approval of CR 014 2.3.1 2.4.0 23-02-09 20WTD108r1 015 F Clarification to clause 10.2 2.4.0 2.4.1 23-02-09 20WTD109r1 016 F Clarification to clause 10.13 2.4.0 2.4.1 Publication 2.4.1 2.5.1 ETSI ETSI TS 183 025 V2.5.1 (2009-04) 72 History Document history V2.0.0 July 2007 Publication as TR 183 025 V2.0.0 V2.2.0 June 2008 Publication as TR 183 025 V2.2.0 V2.5.1 April 2009 Publication |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 1 Scope | The present document specifies the architecture and functions of an IPTV system that makes use of the NGN IMS architecture and its features, implementing the requirements defined in TS 181 014 [14] and TS 181 016 [15]. The present document has taken IPTV solutions defined by other organizations (such as DVB, ATIS IIF, etc.) into account. It is based on an IMS based architecture and where appropriate the aforementioned solutions are referenced. By relying on common components the resulting architecture can coexist with other TISPAN NGN services. NOTE: As the use of IPTV services may release personal data the provider of IPTV services is expected to comply with relevant privacy protection principles as specified for Identity Management in the NGN in TS 187 016 [19]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI TS 182 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.506 Release 8, modified]". [3] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [4] ETSI TS 133 220: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) (3GPP TS 33.220)". [5] ETSI TS 187 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [6] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [7] ITU-T Recommendation P.10/G.100: "Vocabulary for performance and quality of service " - New Appendix I - Definition of Quality of Experience (QoE). [8] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". ETSI ETSI TS 182 027 V3.5.1 (2011-03) 12 [9] ETSI TS 183 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification". [10] ETSI TS 182 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.141 and OMA-AD-Presence-SIMPLE-V1-0]". [11] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [12] Void. [13] ETSI ES 283 030: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence-SIMPLE-V1-0, modified]". [14] ETSI TS 181 014: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Requirements for network transport capabilities to support IPTV services". [15] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [16] ETSI TS 122 340: "Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS) messaging; Stage 1 (3GPP TS 22.340 version 7.0.0 Release 7)". [17] ETSI TS 123 237: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 (3GPP TS 23.237 Release 9)". [18] ETSI TS 124 237: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 (3GPP TS 24.237 Release 9)". [19] ETSI TS 187 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Identity Protection (Protection Profile)". [20] Void. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] DSL Forum Technical Report TR-126: "Triple-play Services Quality of Experience (QoE) Requirements". [i.2] Void. [i.3] ETSI ES 282 010: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Charging management [Endorsement of 3GPP TS 32.240 Release 7, 3GPP TS 32.260 Release 7, 3GPP TS 32.297 Release 7, 3GPP TS 32.298 Release 7 and 3GPP TS 32.299 Release 7, modified]". [i.4] ETSI TR 182 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data". [i.5] ETSI ES 204 915 (all parts): "Open Service Access (OSA); Application Programming Interface (API); (Parlay 6)". [i.6] ETSI ES 202 504 (all parts): " Open Service Access (OSA); Parlay X Web Services; (Parlay X 3)". ETSI ETSI TS 182 027 V3.5.1 (2011-03) 13 [i.7] ETSI TS 129 198 (all parts): "Universal Mobile Telecommunications System (UMTS); LTE; Open Service Access (OSA) Application Programming Interface (API) (3GPP TS 29.198 Release 7)". [i.8] ETSI TS 123 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 Release 8)". [i.9] ETSI TS 123 218: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) session handling; IM call model; Stage 2 (3GPP TS 23.218 Release 8)". [i.10] 3GPP TR 23.810: "Technical Specification Group Services and System Aspects; Study on Architecture Impacts of Service Brokering; (Release 8)". [i.11] Toshiro Nunome; Shuji Tasaka, "An Application-Level QoS Comparison of Inter-Destination Synchronization Schemes for Continuous Media Multicasting", IEICE transactions on communications, ISSN 0916-8516, Vol. 87 (2004), No. 10, pp. 3057-3067 (11). [i.12] SCTE-130 part 1: "Advertising Systems Overview". [i.13] SCTE-130 part 2: "Core Data Elements". [i.14] SCTE-130 part 3: "Ad Management Service interface". [i.15] OMA MobAd 1.0 RD: "Mobile Advertising Requirements". [i.16] OMA MobAd 1.0 AD: "Mobile Advertising Architecture". [i.17] Void. [i.18] ITU-T Recommendation J.181: "Digital program insertion cueing message for cable television systems". [i.19] ETSI TS 129 199 (all parts): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Open Service Access (OSA); Parlay X web services; (3GPP TS 29.199 version 8.1.0 Release 8)". [i.20] ETSI TS 126 234: "Universal Mobile Telecommunications System (UMTS); LTE; Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs (3GPP TS 26.234 Release 8)". |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3 Definitions and abbreviations | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: content control: procedure for controlling content delivery NOTE: e.g. starting content delivery, playback of content (such as pause, fast and slow playback, reverse playback. rewinding, jumping forwards or backwards), stopping content delivery), and content management (e.g. digital rights management, program scheduling management, delivery management. content delivery: procedure for delivering multimedia contents content Provider: entity that owns or is licensed to sell content or content assets content protection: protection of content or content assets during its entire lifetime NOTE: The content provider defines the lifetime that the protection is required for. Inter-destination Media Synchronization (IDMS): feature for exchanging arrival time and delay information, resulting in substantial synchronisation of the media outputs of two or more UEs, as presented to their users ETSI ETSI TS 182 027 V3.5.1 (2011-03) 14 IPTV Service Access History (SAH): collection of a user's service states and service actions as well as other information NOTE: Examples include accessed service types, watched content and time of watching. IPTV content identifier: superclass of the identifiers that identify content in specific IPTV services IPTV Service Action Data (SAD): persistent record of actions that a user has made; for use in access to IPTV services NOTE: Examples include BC bookmarks, available CoD, PVR items and UGC items. IPTV service state: snapshot of the information related to an ongoing IPTV service NOTE: Examples include the current BC program ID, the ID of current CoD content, the state of PVR recordings, the media state of services and invoked trick play events, commercial breaks in services and combinations of these. IPTV Service State Data (SSD): information about IPTV service state and service actions NOTE 1: This information may be held in network elements that constitute the IPTV solution or external applications. NOTE 2: The relationship between SSD, SAD and SAH is as follows: SSD is information about the present meant for immediate use, e.g. inserting a targeted advertisement or performing an action on an incoming phone call. SAD is information meant for future service access, e.g. a user setting and later retrieving a BC bookmark to see (again) the bookmarked content. SAH is information meant for user preference extraction and sharing services, e.g. for service personalization, targeting, and sharing consumption history among authorized users. IPTV Service protection: managing authorized access to the IPTV-service; the protection of IPTV-content (e.g. files or streams) and IPTV-service information during delivery which may include content already protected and meta data that the service provider adds to the content NOTE: The IPTV service may be composed of the content to be transfered and other data and service components. Service protection addresses protecting this composition while in transit and regulates authorized access to the service. Additionally it addresses ensuring the service availability, as defined in the service level agreements. IPTV service type identifier: identifies type of IPTV services media stream identifier: identifier carried in a unicast or multicast media stream that identifies that specific media stream offset: value indicating the elapsed time between the beginning of content and the current reading position of the reading cursor in that same streamed content park TV: feature that would enable a user (on a UE) make an impulsive request to record ongoing BC service/programme from a particular point in time NOTE: This recording point is also referred to as a bookmark. park and pickup TV: feature that would enable a user (on a UE) to Park TV and subsequently Pickup TV pickup TV: feature that would enable a user (on a UE) retrieve or request BC service/programme that was recorded and bookmarked via an impulsive record request NOTE: The IPTV content can be retrieved from the bookmarked location or recording point on same or different UE at a later point in time. programme: entry in the Electronic Programme Guide ETSI ETSI TS 182 027 V3.5.1 (2011-03) 15 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADM Ad Management Service ADS Ad Decision Service AS Application Server BC BroadCast CIS Content Information Service CM Content marker CoD Content on Demand C-PVR Client Personal Video Recorder CR Content Recommendation CRS Content Recommendation Service CSF Content Security Functions ECF Elementary Control Function EF Elementary Functions EFF Elementary Forwarding Function EPG Electronic Programme Guide GAA Generic Authentication Architecture GBA Generic Bootstrapping Architecture HD High Definition ICM Incoming Call Management IDMS Inter-Destination Media Synchronization IGMP Internet Group Management Protocol IMPU IMS Public User Identity IMS IP Multimedia Subsystem IPTV IP Television MCF Media Control Function MCN Media Channel Negotiation MDF Media Delivery Function MF Media Function MSAS Media Synchronization Application Server NASS Network Attachment SubSystem NGN Next Generation Network N-PVR Network-Personal Video Recorder PC Parental controlled POIS Placement Opportunity Information Service PSC Personalized Service Composition PVR Personal Video Recorder QoE Quality of Experience QoS Quality Of Service RACS Resource and Admission Control Subsystem SAD Service Action Data SAH Service Access History SC Synchronization Client SCF Service Control Function SCIM Service Capability Interaction Manager SCS Service Capability Server SD Standard Definition SDF Service Discovery Function SIP Session Initiation Protocol SIS Subscriber Information Service SKMF Service Key Management elementary Functions SLF Subscription Locator Function SMF Service Membership elementary Functions SPF Service Protection elementary Functions SSC Shared Service Control SSD Service State Data SSF Service Selection Function TAI Targeted Advertisement Insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 16 TPF Transport Processing Functions UE User Equipment UGC User Generated Content UPSF User Profile Server Function URI Uniform Resource Identifier XDMS XML Document Management Server |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 4 High-level overview | User Equipment Application Functions & IPTV Service Functions Core IMS User Profiles Manage- ment Functions Content Provider Functions Media Delivery, Distribution & Storage Transport Control Functions Transport Processing Functions Transport Functions Figure 1: High level functional architecture for IMS-based IPTV NOTE 1: The specification of management functions and content provider functions is considered out of scope of the present document. User equipment UE: The IPTV enabled UE terminates the IPTV control and media signals, and displays the corresponding information to the user. The UE interaction with the user allows selection of programme, content, and service descriptions, such as content guides for broadcast and VoD services. Application functions and IPTV service functions Enables operation of or provides IPTV services. This includes IPTV Service Supporting Functions. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 17 IPTV Service Supporting Function: The IPTV Service Supporting Function defined here are those common functions which could support or be used by other IPTV service or applications. NOTE 2: Examples of IPTV service supporting functions may be Service Discovery and Selection functions. User Profiles User Profiles includes user data that are involved in providing IPTV services. Core IMS It provides functionality for authentication, authorization, and signalling for the setup of the service provisioning and content delivery. It routes signalling messages to the appropriate application server or triggers the applications based on settings maintained in the UPSF. For resource reservation and admission control this function interacts with the RACS. Transport Functions Transport Control: contains functions from RACS and NASS. It provides policy control, resource reservation and admission control as well as IP address provisioning, network level user authentication and access network configuration as defined in TISPAN. Transport Processing Functions (TPF): represents network access links and IP core. The IP core is in charge of data transmission with quality of service support. Media Delivery, Distribution and Storage The Media Delivery, Distribution and storage function receives and stores live feeds and media streams coming into the IPTV System from Content Providers. It is mainly in charge of media processing, delivery, storing, trans-coding and relaying. This function performs all these tasks along with the control of - or feedback to the IPTV Service and Control. Content protection may also be performed here or already protected content could be delivered over these functionalities. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5 Overview of functional entities | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1 Functional architecture for IPTV services | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.1 Functional architecture overview | The overall functional architecture for IPTV service is shown in figure 2. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 18 Figure 2: Functional architecture for IPTV services NOTE 1: Only Xc and Xd are explicitly shown as traversing the Transport Processing Functions. For the sake of simplicity other reference points are only shown as end to end. In figure 2, the IPTV Service Control Functions, the IPTV Media Functions, the Service Selection Function (SSF) and the Service Discovery Function (SDF) fit in the context of TISPAN NGN Functional Architecture Release 2 [1]. NOTE 2: To support the regionalized delivery of content and metadata in accordance with applicable regulations, at least one of the service layer entities involved in the IPTV service should query the UE location from the NASS and enforce the regionalization. As stated in [2], the IMS architecture shall be based on the principle that the service control for Home subscribed services for a roaming subscriber is in the Home network. This principle shall be applied also in case the IPTV solution supports roaming. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.2 IPTV services | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.2.0 Compliance | An IPTV solution is compliant to the present document if the following points are fulfilled. • All mandatory services and features are implemented as specified in the present document. • If an optional service or feature is implemented, then it is implemented as specified in the present document. • If an optional service or feature is implemented, and the present document specifies multiple options, then it is implemented according to at least one or those options. Transport Control Functions Core IMS Transport Processing Functions IPTV Media Functions 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 Sh ISC Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions SDF SSF Ss’ IPTV Service Control Functions (SCF) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 19 The IMS based IPTV architecture in this release should be fully backward compatible with architecture and services specified in previous release. NOTE: Any backwards compatibility issues need to be explicitly mentioned. 5.1.2.1 General IPTV services execution involves three functions: a service control function (SCF), a media control function (MCF) and a media delivery function (MDF). An SCF may host the logic of one or more of the following services as defined in TS 181 016 [15]: The following table 1 provide list of services and feature supported by TISPAN IMS based IPTV architecture (selection based on [1] and procedures described in TISPAN): NOTE: In certain cases, TS 181 016 [15] provides insufficient guidance with respect to the mandatory/optional nature of services. If a service has been specified as "mandatory" within the Service Layer Requirements specification but the corresponding requirements have not been clearly mandated, the service has been specified as "Optional" or "Mandatory/Optional" (with appropriate qualifying Note) within table 1. Table 1: IPTV services and features supported by TISPAN IMS based IPTV subsystem NGN IPTV Service and Feature TISPAN R2 Service Layer Requirements to Integrate NGN Services and IPTV TISPAN R2 IPTV Architecture; IPTV functions supported by the IMS subsystem TISPAN R3 Service Layer Requirements to Integrate NGN Services and IPTV TISPAN R3 IPTV Architecture; IPTV functions supported by the IMS subsystem Specification TS 181 016 [15] Release 2 TS 182 027 Release 2 TS 181 016 [15] Release 3 TS 182 027 Release 3 Linear/ Broadcast TV M M M M Linear/ Broadcast TV with Trick Play M O M O Time Shifted TV O O O O Content on Demand (CoD) M M M M Push CoD NA NA O O Network PVR M M/O (see note 2) M M/O (see note 2) Client PVR NA NA O O (See NOTE 2) Audio M O M O Pay-Per-View NA NA M O Interactive TV NA NA M O Service discovery M M M M Service Information (EPG) M M M M Parental Control M M/O (see note 3) M M/O (see note 3) User Profiling and Personalization O O O O Communications and Messaging NA NA O O Notifications NA NA O O IPTV Presence O O O O Interaction between users NA N/A O O Interaction with NGN services O O O O Advertising M M (see note 4) M M (see note 4) Targeted Advertising NA NA O O User Generated Content NA NA M O Internationalization O O O O Content recommendation NA NA O O Games NA NA O O Picture NA NA O O Bookmarks NA NA O O Personalized channel NA NA O O Personalized Service Composition NA NA O O ETSI ETSI TS 182 027 V3.5.1 (2011-03) 20 NGN IPTV Service and Feature TISPAN R2 Service Layer Requirements to Integrate NGN Services and IPTV TISPAN R2 IPTV Architecture; IPTV functions supported by the IMS subsystem TISPAN R3 Service Layer Requirements to Integrate NGN Services and IPTV TISPAN R3 IPTV Architecture; IPTV functions supported by the IMS subsystem Service Portability NA NA O O Service Continuation between IPTV UEs NA NA O O Service Continuation fixed-mobile NA NA O O Remote Control of IPTV services NA NA O O Emergency Information. NA NA O O Interaction with 3rd Party application (e.g. Parlay) NA NA O O Service synchronization NA NA O O Incoming call management NA NA O O NOTE 1: M - Mandatory, O- Optional, NA - not available or not specified (out of scope in release) in architecture NOTE 2: It is recommended that at least one type of PVR is supported by the IPTV system. NOTE 3: Mandating this feature is subject to local regulatory policies. NOTE 4: Advertising refers to traditional broadcast based advertising services which impose no new requirements on IMS based IPTV subsystem. The service request/response messages between the UE and the SCF are transferred via the Core IMS. Media Control messages are exchanged between the UE and the MCF via the Xc reference point. Media Data is exchanged between UE and MDF via the Xd reference point. For UGC services, media may also be exchanged or streamed between users provided that the control of this media exchange or these media streams lies with the UGC function. For CR services, the SCF exchanges service request/response messages with the UE directly over the Ut or via the IMS Core as appropriate. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.3 Functional entities | Refer to clause 5.1.5. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.3A Generic Capabilities | IPTV Generic IPTV Capabilities: 1. service discovery and selection 2. service control 3. service interaction 4. media control 5. media delivery 6. content protection 7. content management and distribution 8. interactions with other NGN services ETSI ETSI TS 182 027 V3.5.1 (2011-03) 21 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.4 Elementary Functions (EF) | General: 1. network attachment 2. registration 3. resource Management 4. charging information IPTV elementary functions: Service related elementary functions 5. service discovery 6. service authorization 7. service selection 8. service initiation 9. service control 10. service information handling (e.g. metadata) 11. service configuration Session related elementary functions 12. session initiation 13. session modification 14. session termination Service Protection related elementary functions 15. service key triggering function Multimedia delivery and control related elementary functions 16. multicast based media delivery (media streaming) 17. unicast based media delivery (media streaming) 18. content download/upload (offline content transfer) 19. control of multicast based media streaming 20. control of unicast based media streaming) 21. control of content transfer by download/upload 22. content ingestion (receiving content) 23. content recording(capture of live content) 24. content storage 25. content adaptation (e.g. transcoding, mix, substitute, personalize) Content management related elementary functions 26. content acquisition 27. content validation ETSI ETSI TS 182 027 V3.5.1 (2011-03) 22 28. content distribution Content protection related elementary functions 29. content licencing 30. content key management 31. content encryption NOTE: Content protection solutions are not standardised by TISPAN but a framework allowing for implementation of multiple solutions is provided by the TISPAN architecture. User data management related elementary functions 32. User profile/data management 33. Accounting/right control IPTV Common elementary functions: 34. Status/state (changes) detection/reporting 35. Common notification 36. Messaging 37. Presence Reporting 38. Inter-destination Media synchronization |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.4.1 Content Security Functions (CSF) | Content security elementary functions are described in clause 10.2. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5 Functional Entities | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.1 Service Discovery and Selection Functions (SDF and SSF) | The Service Discovery Function (SDF) and Service Selection Function (SSF) are functions which provide information necessary to the UE to select an IPTV service. Tasks of the SDF: • Generates and/or provides the service attachment information. • Provides personalized service discovery. The service attachment information consists of SSF addresses in the form of URIs and/or ip-addresses. Tasks of the SSF: • Provides the service selection information, e.g. a list of available services that the UE can then browse and select. The SSF may optionally generate this service selection information. It may also retrieve and forward the service selection information. - Provides personalized service selection information and/or information needed to personalize the service selection. This must be delivered via unicast mode. (See note 1 regarding multicast options.) - Provides non-personalized service selection data. This can be delivered via multicast or unicast mode. • Optionally provides service selection presentation information. This presentation information may be personalized when it is delivered over unicast mode. Optionally receives selection request from UE, e.g. an N-PVR content capture request as described in clause 8.5. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 23 NOTE 1: The way the service selection information might be personalized when it is delivered via multicast mode is out of scope for this release. However, specified below is a non exhaustive list of high-level options to achieve such personalization: Using the SDF: when processing a request from a particular user/UE, the SDF could redirect the user/UE to specific multicast addresses/SSFs corresponding to the category to which the user belongs. This would imply that users/UEs are classified into specific categories. Using the SCF: UE could fetch IPTV user profile information in the form of BC Service ID listings from the SCF. This may be encoded as XML document(s) via the Ut reference point using XCAP-like mechanism or as HTML document with possibly embedded scripts to filter this service selection data. This IPTV user profile information may then be used to locally filter the service selection data that was previously delivered via multicast mode. NOTE 2: EPG is defined in TS 181 016 [15]. For each IPTV service, the following data is provided: • An identifier associated to the IPTV service: this identifier is used by service control functions and media functions to identify the requested content when processing service initiation requests. In case of a CoD service, the identifier identifies exactly one content item. In case of a BC service, the BC identifier, which is the Service Package Id related to BC profile defined in clause 7.3, identifies a set of channels among which the user can switch. • Optionally the set of network parameters that may be required by the UE to activate a service (e.g. the extra information that may be needed by the UE to establish content delivery channels and content control channels). • User readable data related to the IPTV service. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.2 IPTV Service Control Functions (SCF) | Tasks of SCF: • Service authorization during session initiation and session modification, which includes checking IPTV users' profiles in order to allow or deny access to the service. • Credit limit and credit control (using the on-line charging systems ES 282 010 [i.3]). In addition, the SCF performs the following tasks depending on type of service supported • Select the relevant IPTV media functions (see clause 5.2). • Send relevant notifications to the MF, e.g. for content recommendation service. • For Push CoD Services, initiate media content (e.g. recorded BC program, CoD content) download to UE. • 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). • Communicate with an external advertising sub-system in order to make ad-selection and ad-placement decisions if one exists (see annexes E and F). • For SCF-managed TAI, send ad insertion indication to MF or UE. • Instruct the UE to perform trick play commands, e.g. pause a TV channel, CoD or N-PVR stream. • Initiate BC and/or CoD session to UE for immediate consumption. • Generate playlist information and communicate it to the MF. • For Content Recommendation Services, detect CRS event and generate CRS information for specific user or user group, based on user profile (e.g. user preference). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 24 • Detect an event, based on some criteria, trigger relevant internal service logic and send a notification to the UE or other applications associated with the specific user. • Optionally, for PVR service, initiate the recording of content, e.g. for C-PVR service, initiates a notification request to UE to start recording. • For restricted trick play, acquire restriction policy and transmit to relevant MF. • Detecting IPTV service state information. • Optionally, aggregating (i.e. collecting and storing) requested IPTV service state information. The SCF is a SIP Application Server (AS). An IPTV SCF belonging to an IMS network managed by another provider shall not have direct access to user profile data in the UPSF via the Sh reference point; it may however have access to user profile data by other means (e.g. Rg reference point to GUP), depending on the NGN operator's implementation and capabilities. The SCF may use the IPTV profile in order to customize the user experience. For instance, the list of subscribed BC TV Services could be used to filter the information sent to the UE. The User Equipment communicates with the IPTV Service Control Functions via the Core IMS for the purpose of session management, and may be using the Ut reference point for the purpose of service profile configuration. In the latter case, an authentication proxy may sit between the User Equipment and the SCF. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.3 IPTV Media Control and Delivery Functions (MCF and MDF) | IPTV Media Functions are in charge of controlling and delivering the media flows to the UE. They are split into Media Control Functions (MCF) and Media Delivery Functions (MDF). Tasks of Media Control Function (MCF): • Handling media flow control of MDF. • May manage the media processing of MDF. • Monitoring the status of MDF. • Managing interaction with the UE (e.g trick mode commands). • Handling interaction with the IPTV service control function SCF. • Keeping an accurate view on status and content distribution related to the different MDFs that it controls. • Detecting IPTV service state information. • Reporting IPTV service state information to SCF when requested. • Selecting an MDF, in the case an MCF controls multiple MDFs different criteria, may be applicable (as described e.g. for CoD in clause 5.2). • Selecting MF, return the selection result to SCF and Redirect sessions to the selected MF (e.g. in case the requested content is not available on this MF or for load balancing among MFs). • Generate charging information, e.g. for end-user charging based on the viewed content. • 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. • In case of live User Generated Content consumption (TS 181 016 [15], clause A.13), there is a direct relationship on the media delivery and media control levels between downstreaming and upstreaming UGC sessions, which both terminate at the MCF. The MCF ensures that session descriptions of the downstreaming and upstreaming UGC sessions match. UE's subscribed to the particular Live UGC are notified when this Live UGC starts. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 25 Tasks of MDF: • Handling media flows delivery (for delivering multimedia services to user). • Status reporting to MCF (e.g. reporting on established IPTV media streams). • Store of media (e.g. CoD assets) and may also store some service information stored with media for IPTV services. • In particular, it may be used for storage for the most frequently accessed content or user specific content (e.g. recording PVR, Time-shift TV, BC service with Trick mode, user generated content) if the same tasks are not performed by UE. • May additionally process, encode or transcode (if required) media to different required media formats (e.g. TV resolution depending on terminals capabilities or user preferences). • May perform content protection functionalities (e.g. content encryption). • May support content ingestion of IPTV media. NOTE 1: Ingested content can either be processed, encoded or transcoded in an MDF, or it can arrive in a suitable media format for delivery to UE, thus avoiding transcoding. • MDF may act as source for multicast streams of IPTV services e.g. BC or UGC media streams. • For UGC services, receiving content from UE through an upstreaming/upload media channel. • May collect QoE reports (e.g. from UE using Xd). • For Push CoD Services, handling content download (download CoD content to UE or record BC live stream and then download to UE). • Perform ad insertion during IPTV content playback, i.e. deliver ad content to the UE during the ad insertion time, either exclusively or in parallel with the IPTV content. • 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. • For personalized stream composition, the MDF may support alternative streams for use with an existing broadcast channel or CoD item, e.g. alternative video, audio or subtitle tracks. NOTE 2: To enhance QoE evaluation quality, QoE reports may additionally be collected from other sources than the UE. However, this is beyond the scope of the present document. To support QoE, the UE may send QoE reports via Xd concerning the quality of the IPTV Media Data received. Each IPTV Service Control Function uses the ISC reference point to communicate with the NGN Core IMS. As stated in TS 182 006 [2], an Application Server may originate requests to a destination without involving the S-CSCF. This capability should be used in case the SCF is to communicate with the media function without involving the core-IMS. Each corresponding IPTV Media Function communicates with the UE over Xc and Xd for Media Control and Media Delivery. For each service, the corresponding Media Control entities communicate with the UE on the Xc reference point and control the appropriate Media Data Delivery entities which send the Media Data to the UE on the Xd reference point. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 26 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.4 UPSF | The UPSF holds the IMS user profile and possibly IPTV specific profile data (see clause 7). It communicates with IPTV Service Control Functions at the Sh reference points and with the Core IMS at the Cx reference point as defined in ES 282 007 [11]. When multiple instances of a UPSF exist, the Core IMS and the IPTV Service Control Functions may use the services of a Subscription Locator Function (SLF) to fetch the address of the UPSF. The SLF communicates with IPTV Service Control Functions at the Dh reference points and with the Core IMS at the Dx reference point as defined in ES 282 007 [11]. For the sake of simplicity the SLF and associated reference points are not shown on figure 2. NOTE: The IMS principle procedures, such as security, authentication process, are also considered to be applied to this IPTV functional architecture and the procedures, unless explicitly stated otherwise. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.5 Transport processing functions | IPTV services make use of generic transport processing functions defined in ES 282 001 [1]. 5.2 Interactions between Service Control function and Media Functions The relationship between Service Control Function (SCF) and Media Function (MF), composed of Media Control Function and Media Delivery Function, is shown in figure 3. Figure 3: Relationship between Service Control Function and Media Functions When an MF is involved in a session (e.g. CoD) the specific MF for this particular session will be determined during the session initiation and resource allocation procedure. This determination may be based on the following criteria: • Location of the UE. • Status information of all the available media functions (e.g. online or offline, media processing capability, available resources in the different -MF holding the same contents, etc.). • Load of the different MF holding the same contents. • Content identity of the requested content; It is recommended that the structure of the content identifiers be designed so as to facilitate this selection, without requiring parsing the full identifier. The selection process relies on elementary functions that can be hosted in an SCF and/or an MCF. In the latter case the MCF may act as a redirect server to redirect sessions to another MCF. And in some cases, the selection task of SCF -SCF MCF MDF MDF CoD -MCF MF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 27 and/or MCF may become very simple. For e.g. if a Request-URI for service/content identifier corresponds to just one MCF, then SCF and/or MCF may just transfer the session to the unique MCF. NOTE 1: The location of the selection process in a separate entity is out of scope for this release. NOTE 2: Admission control procedures for use of transport resources at the CoD-MF side are out of scope for this release. The SCF shall contact the MCF during the session initiation and resource allocation phase. The SCF may contact several MCFs before its determination. TheSCF contacts the MCF via the Core IMS as shown in figure 4. Figure 4: Reference points between SCF and MCF When the MCF is contacted, it shall respond with the parameters offer for the session corresponding to the content required by the UE. The MCF controls one or several MDFs. Tasks of the MCF are the following: • Select an MDF. • Control the media stream resources in the MDFs. • Interpret information coming from the SCF and control the MDFs accordingly. • Generate of CDRs. Selection of the MDF by the MCF uses similar criteria to the selection of a MCF by a SCF. And in some cases, the selection task of MCF may become very simple. For e.g. if a Request-URI for service/content identifier corresponds to just one MDF, then MCF may just transfer the session to the unique MDF. After the MCF has selected a MDF for service, it may communicate with the MDF. If the MDF is not functional for some reason, the MCF may detect this exception, for example, by a local response timeout, and select another MDF with the requested content. If there is no other MDF with the requested content under the MCF's control, it should redirect the service request to another MCF or return an appropriate error message to the SCF. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.3 Void | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4 Inter-destination media synchronization | Inter-destination media synchronization is an optional generic capability, aimed at servicing requiring this capability, see TS 181 016 [15], clause A.9.6 for examples. The Media Synchronization Application Server (MSAS) and Synchronization Client (SC) are functions that provide inter-destination media synchronization. These functions are used for synchronization sensitive services for which IPTV delays and delay differences may spoil the quality of experience. The functional entities and reference point of the synchronization mechanism are shown in figure 4A. SCF CORE-IMS MCF ISC y2 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 28 Media Synchronization Application Server (MSAS) Sync Synchronization Client (SC) Figure 4A: Functional entities and reference points for inter-destination media synchronization |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.1 Functional entities MSAS and SC | The inter-destination media synchronization (IDMS) mechanism uses the concept of synchronization sessions. Each synchronization session involves a Media Synchronization Application Server (MSAS) and multiple Synchronization Clients (SC). A synchronization session is used for the inter-destination synchronization of IPTV content (a BC channel, CoD, UGC, etc.) by exchanging synchronization status information (i.e. arrival time information) and delay information in the form of synchronization settings instructions. • Synchronization status information: timing information on media reception at each SC. • Synchronization settings instruction: instruction how much an SC should delay themedia stream . Tasks of the SC: • Setting up and accepting synchronization sessions with/from the MSAS. • Sending synchronization status information to the MSAS. • Receiving delay information in the form of synchronization settings instructions from the MSAS. • Delaying (buffering) a media stream according to the received synchronization settings instruction. Tasks of the MSAS: • Session-oriented tasks: - Setting up and accepting synchronization sessions with/from SCs. • Media-oriented tasks: - Collecting synchronization status information from SCs. - Calculating delay information and the derived synchronization settings instructions for the SCs. - Distributing synchronization settings instructions to SCs. The MSAS function may be decomposed in session-oriented functions and media-oriented functions. NOTE: Examples of algorithms to calculate the synchronization settings instructions from collected synchronization status information may be found in [i.11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.2 Mapping onto the IPTV architecture | The synchronization architecture can be mapped onto the IPTV architecture in the following ways. Mapping 1: SC in UE • The session-oriented part of the MSAS is an elementary function of the SCF. For synchronisation using a direct communication channel between multiple UEs, the MSAS is co-located with the SC in a UE. • The SC is an elementary function of the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 29 • The Sync reference point is tunnelled over the Gm and ISC reference points. • Each synchronization session is associated with an IPTV session. Mapping 2: SC in Transport • The MSAS is an elementary function of the SCF or a stand-alone Application Server. • The SC is an elementary function of the Transport Functions. NOTE 1: Mapping 1 is aimed at small-scale deployments of services that require media synchronization and only a limited number of UEs uses media synchronization. It reuses existing IPTV sessions. Mapping 2 is aimed at large-scale deployment of media synchronization. NOTE 2: In mapping 2, the SC is an adjunct function that may be co-resident with any of the appropriate elements in the transport layer. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.3 Modification and re-origination of media streams | In addition to inter-destination media synchronization, additional synchronisation measures are needed in case a media stream is modified or re-originated during transport. Examples of these are transcoding, HD-to-SD conversion and user-generated comments to a live broadcast. In such cases, additional media-stream-modifying Synchronisation Clients (SC') are placed at the functional entities where media streams are modified, see figure 4B. The Sync' reference point is used to exchange convey synchronization status correlation information between from the media-stream-modifying SC' and to the MSAS on the synchronicity relationship between incoming and outgoing media streams. • Synchronization correlation information: timing information on the synchronicity relationship between incoming and outgoing media streams at an SC'. Figure 4B: Media synchronization in case of media stream modification SC MSAS Media stream origination (e.g. MF or EFF) Media stream modification (e.g. transcoder at MF or re-origination at UE) SC' Media stream destination (e.g. UE or TFP) SC Sync Sync' Media stream M Media stream M' ETSI ETSI TS 182 027 V3.5.1 (2011-03) 30 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5 IPTV Service State | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5.1 General | IPTV service states is defined as a snapshot of the information related to an ongoing IPTV service, see clause 3.1. Examples include the current BC program ID, the ID of current CoD content, the state of PVR recordings, the media state of services and invoked trick play events, commercial breaks in services and combinations of these. Maintaining the IPTV service state can provide information about ongoing services towards the user and network elements, can support service interaction and the creation of combined services by associating service states and reacting on state transitions. IPTV service state is used in several procedures, among which are: targeted ad-insertion (see clause 8.14), shared service control (see clause 8.21) and event-handling involving the SCF (see clause 9.4). IPTV service state can be detected by SCF, MF and/or UE, aggregated by the SCF and is maintained in the IPTV Service State Data (see clause 7.7). IPTV Service State Data can be updated using the procedures in clause 8.26. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5.2 Relationship between IPTV Service State and IPTV presence | Generally, a hierarchical relation exists between the internal service states of Functional Elements, the IPTV Service State information and Presence information; the internal service state information can be aggregated in IPTV Service State, and IPTV Service State data can be used to update Presence. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6 Reference points | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.1 UE - SSF (Xa) | This reference point between UE and SSF is used by the UE to make appropriate service selections. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.2 UE - IPTV Service Control Functions (Ut) | This reference point between UE and IPTV Service Control Functions is used by the UE for the purpose of service profile configuration. Use of the Ut reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.3 UE - Core IMS (Gm) | Use of the Gm reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.4 UE - Media Control Functions (Xc) | This Xc reference point (for media control) is a logical end-to-end reference point between the UE and the IPTV Media Control Function that is used to exchange media control messages for controlling the IPTV Media flow. NOTE: Transport related reference points are used to carry media control messages over underlaying transport segment (defined in ES 282 001 [1]) and as shown below in figure 5 depending on the location of the MCF. The Dj reference point between the UE and the access network, the Di reference point between the access network and the core network, and possibly the Ds or Iz reference point between the core network and the Media Control Function if the MCF is located after the Core Network. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 31 Access Network Di Ds or Iz Dj Xc UE MCF Core Network Transport Processing Figure 5: Decomposition of the Xc reference point when the MCF is after the core network |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.5 UE - Media Delivery Functions (Xd) | This Xd reference point (for media delivery) is a logical end-to-end reference point between the UE and the IPTV Media Delivery Function that is used to deliver media data. NOTE: Transport related reference points are used to carry media delivery data over underlaying transport segment (defined in ES 282 001 [1]) and as shown below in figure 6 depending on the location of the MDF. The Dj reference point between the UE and the access network, the Di reference point between the access network and the core network, and possibly the Ds or Iz reference point between the core network and the Media Delivery Function if the MDF is located after the Core Network. Access Network Di Ds or Iz Dj Xd UE MDF Core Network Transport Processing Figure 6: Decomposition of the Xd reference point If the IPTV system architecture supports QoS and/or QoE [7] and [i.1], this reference point may carry QoS and/or QoE reports from the UE to the MDF. These reports relate to the quality of the IPTV Media Data that the UE receives. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.6 IPTV Service Control Functions (SCF) - UPSF (Sh) | Use of the Sh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.7 Core IMS - UPSF (Cx) | Use of the Cx reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.8 Core IMS - IPTV Service Control Functions (ISC) | Use of the ISC reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.9 Core IMS - IPTV Media Functions (y2) | This reference point between S-CSCF and IPTV Media Control Function (MCF) carries IPTV Service Control Signalling originating from the IPTV Service Control Function (SCF) to control the MCF. In case the CSCF and the Media Control Function are in different administrative domains, signalling flows go through an IBCF. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 32 NOTE: As stated in TS 182 006 [2], an Application Server may originate requests to a destination without involving the S-CSCF. This capability should be used in case the SCF is to communicate with the media function without involving the core-IMS, thus omitting y2. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.10 Core IMS - SDF (ISC) | Use of the ISC reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.11 SDF - UPSF (Sh) | Use of the Sh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.12 Void | Void. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.13 Application Functions - NASS (e2) | Use of the e2 reference point conforms to ES 282 007 [11] and ES 282 004 [3]. NOTE: Application Function entities associated to IPTV services such as core IMS and SCF may query the UE location from the CLF in order to fulfil their tasks. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.14 Core IMS - RACS (Gq') | Use of the Gq' reference point conforms to ES 282 007 [11] and ES 282 003 [8]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.15 NASS - RACS (e4) | Use of the e4 reference point conforms to ES 282 003 [8] and ES 282 004 [3]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.16 IPTV Service Control Functions - SLF (Dh) | Use of the Dh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.17 Core IMS - SLF (Dx) | Use of the Dx reference point conforms to ES 282 007 [11]. 6.18 IPTV Media Control Function - IPTV Media Delivery Function (Xp) This Xp reference point between the Media Control Function (MCF) and Media Delivery Function is used to control media delivery sessions to support media delivery session setup when content is distributed across one and more media delivery functions. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.19 MSAS-SC reference point (Sync) | This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream-synchronizing Synchronization Client (SC). It is used to set up synchronization sessions and to exchange synchronization status information and synchronization settings instructions with functional entities in the network where media streams are mutually synchronized. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 33 The Sync reference point is decomposed as follows: • Synchronization session initiation • Synchronization status information and settings instruction exchange The session-oriented part of the Sync reference point is a logical reference point in Mapping 1 from clause 5.4.2, where the synchronization session initiation signalling is tunnelled over the Gm and ISC reference points. It may also use the Xc reference point. The media-oriented part of the Sync reference point uses the Xd reference points. If the SC is co-located with the MSAS, then the exchange of synchronization status information and synchronization settings instructions is internal to the functional entity in which they reside. Specification of this internal Sync reference point is out of scope. NOTE: An example of co-located SC+MSAS functionality is when UEs exchange synchronization status information and synchronization settings instructions via a direct communication channel. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.20 MSAS-SC' reference point (Sync') | This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream-modifying Synchronization Client (SC'). It is used to set up synchronization sessions and to exchange synchronization status information with functional entities in the network where to-be-synchronized media streams are modified. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.21 SSF-SCF reference point (Ss') | The Ss' optional reference point between IPTV SCF and SSF is used to exchange required service information and/or service provider information(e.g. service provider details, UGC specific information, etc. NOTE 1: Since SSF is not designed for content metadata maintenance/management. How the content metadata is managed in the IPTV architecture and whether there should be required for metadata management any extension of SSF functionality or new functional entity or can be handle by IPTV management is out scope of the present document, which may be considered in future release. NOTE 2: The optional Ss' reference point is not standardised in the current release. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7 User data | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.1 Classification of information | Five categories of user data are involved in providing IPTV services: 1. IMS-profile: This category includes all information required to establish IMS sessions and access IPTV services hosted in Application Servers, as described in TR 182 005 [i.4]. 2. Communication Services profile: This category encompasses all information associated to communication services (e.g. PSTN/ISDN simulation services, presence services, messaging services…) as defined in relevant ETSI TISPAN standards (e.g. TS 183 004 [9]). This type of information is required in support of combinational services (e.g. Caller Id on TV Screen). 3. IPTV user profile: This category encompasses all information required to operate an IPTV service. This includes all the user settings regarding: - Global settings (Language preference, etc.). - Broadcast settings. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 34 - List of subscribed BC service packages. A BC service package is a set of elementary BC TV services, along with a description. These BC services have the same authorization and charging policy. A BC IPTV service is for instance a multicast channel, interactive channel, mosaic that a user may subscribe to. NOTE: The Broadcast settings only provide a reference to service package and/or associated services that a given IPTV user has subscribed to and is not meant to be a complete description of the service package and/or service. The complete service package and/or service description is available in an associated IPTV Service Profile definition (e.g. described with metadata). If the list of elementary IPTV services associated with a given service package are not explicitly listed in the IPTV user profile, then it implies that the IPTV user has implicitly subscribed to all of the IPTV services within that service package. - IPTV User profile information may be used for providing a listing of recommended content to the user based on the user's profile settings - Content on demand settings (Parental control level, etc.). - PVR settings (PVR preferences network/local, PVR user restrictions, PVR storage limit). - UE Settings which includes information related to the capabilities of the UE(s) that an IPTV user is associated with. An IPTV user may be associated with one or more UE(s) and every UE is uniquely identified with a unique UE Identifier (UE ID). The UE capabilities associated with an IPTV user profile may be used for customization of IPTV service selection data that is provided by the SSF to the IPTV user (based on capabilities of the UE that the IPTV user is currently associated with). For instance, an IPTV user on a SD-only device would not be provided with information related to HD services. - The UE settings is not intended to cover all information related to the UE and currently holds only the UE capabilities attribute since this information may be used by the SSF for personalized service selection. Note that detailed information about the UE may be located elsewhere and can be referenced by the IPTV user profile using the UE ID parameter. - The "user actions recordable" parameter indicates whether user actions can be recorded by the network as part of the IPTV service action data, see clause 7.3.1.5. - Further details are provided in clause 7.3. 4. IPTV service action data: see clause 7.4. 5. IPTV Service State Data: see clause 7.7. The relationships between the IMS profile and the dedicated IPTV user data categories are as follows: - IPTV user profile: This profile is associated with an IMS Public user Identity (IMPU). This would enable for instance enforcement of parental control on a per-user basis independent of the device they are using. - IPTV service action data: This profile is associated with an IMS Public user Identity (IMPU). This would enable for instance "follow me TV/video" kind of scenarios wherein users can resume the viewing of content on any device that they are authorized to use. - IPTV Service State Data: This information is associated with an IMS Public user Identity (IMPU). This would enable (IPTV, non-IPTV and blended) services that interact with IPTV service state, for example incoming call management (clause 9.2) and shared service control (clause 8.21). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2 Location and access to user data | The user data is located in UPSF or in more functions/locations as described in clause 7.2.1. When all user data is stored in the UPSF only, as transparent data associated to Application Server functions then this approach is referred to as the consolidated approach. If user data is stored at multiple locations and distributed across several functions (e.g. application servers, stand-alone severs associated with one or more AS) then this approach is referred to as federated approach. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 35 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.1 Data management functions | IMS-profile information is managed by the UPSF. Communication Services profile information may be managed by dedicated database functions, the Application Server functions hosting the communication services, or by the UPSF as transparent data (repository function) associated to these Application Server functions. In the first and second case the Application Server function or the stand-alone server may exhibit the behaviour of an XDMS. IPTV user profile information should be located in the following locations: • Application Server functions hosting the IPTV applications. • In a stand-alone server associated with one or more Application Server functions. • In the UPSF as transparent data associated to these Application Server functions. The first and second options are recommended for data to be accessed by 3rd party application server functions. In the first and second case the Application Server function or the stand-alone server may exhibit the behaviour of an XDMS. IPTV service action data as well as content markers data need to be persistent across IPTV sessions, and should be located in the network. They may be located in one of the following locations: • The Application Server functions hosting the IPTV applications. • A stand-alone server associated with one or more Application Server functions. • In the UPSF as transparent data associated to these Application Server functions. In the first and second case the Application Server function or the stand-alone server may exhibit the behaviour of an XDMS. IPTV service state data relate to ongoing IPTV session(s). The information may be stored in one of the following locations: • The Application Server functions hosting the IPTV applications. • A stand-alone server associated with one or more Application Server functions. • In the UPSF as transparent data associated to these Application Server functions. In the first and second case the Application Server function or the stand-alone server may exhibit the behaviour of an XDMS. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.2 Access from other application servers | User data stored in the UPSF can be accessed by Application Servers at the Sh reference point. Direct access to user data stored in Application Servers is outside the scope of the present document. However, part of these data may be indirectly exposed through Web Services and/or SIP Event packages. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.3 Access from User Equipment (UE) | A subset of IPTV user-profile information may be accessed from the User Equipment at the Ut reference point. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.4 Access from the SSF | For the purpose of personalized service selection, the SSF may need to access user data. In the case when such user data is stored in the UPSF, it can be accessed by the SSF at the Sh reference point when the SSF is in the same domain. On the contrary, when such user data is stored in the AS or in a stand alone server associated with one or more application servers or if the SSF in not in the same domain as the UPSF, the user data can be accessed by the SSF using an reference point that is out of scope for this release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 36 The SSF may also request notification of IPTV user data updates. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3 IPTV user profile structure | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1 IPTV user profile structure | An IPTV user profile comprises: • zero, one or more instances of the UE object class comprising UE capabilities attribute and associated UE ID; • at least one instance of a Broadcast (BC) or a Content on Demand (CoD) object class (see figure 7); • zero or one instance of the Global settings object class; • zero or one instance of the Personal Video Recorder (PVR) object class; • zero, one or multiple instances of Personalized Channel profile (PCh Profile) object class; • zero or one instance of the Content Recommendation settings (CR) object class; • zero or one instance of the Incoming Call Management settings (ICM) object class. A Broadcast profile comprises one or more BC Service package descriptions. A PCh profile comprises one or more PCh itemlist descriptions, which contain the mapping of each PCh content item to the world clockthe individual PCh IDs as well as the expiry time of each PCh list. Each BC service package comprises zero or more BC TV Services descriptions. Each PCh list comprises one or more PCh items descriptions. Each BC TV service includes a quality definition level (e.g. standard or high definition or other defined quality level). Delivered quality level depends on this quality definition level as well as UE capabilities, available codecs and/or bandwidth limitations. NOTE: When there is no service description for a given BC service package, it would imply that the IPTV user has access to all of the BC services within that given BC service package. The complete service package and/or service description is available in an associated IPTV Service Profile definition (e.g. described with metadata). The ServicePackageId attribute associated with the service package and/or the ServiceId attribute associated with the service refers to appropriate descriptions in an associated IPTV Service Profile definition (e.g. described with metadata) and hence, can be used to fetch detailed information about the particular service package and associated services. A CoD profile includes a parental control level (ParentalControlLevel) attribute. A BC profile includes a parental control level (ParentalControlLevel) attribute. An PVR profile contains PVR rules for the user. A Global Setting profile includes zero or one Parental Control description, which contains attributes related to parental control. The CR Settings includes a CR notification attributes. The ICM Settings includes ICMrule attributes. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 37 Figure 7: IPTV user profile data model This data model assumes that each IPTV user is allocated at least an IMS Public User Identity and an IPTV user profile is associated with this IMS Public User Identity. Multiple IPTV users may share the same IMS subscription. The IPTV user identity (i.e. the IMS Public User Identity) selected when making an outgoing request is asserted by the UE using means outside the scope of the present document (e.g. using a local pin code). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.1 BC service package | A service package is a group of one or more BC service. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.2 BC service | A service relates to a particular TV channel and associated quality definition (e.g. SD or HD). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.3 UE | Contains the UE's Id and its capabilities. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.4 Global settings: language preference | This attribute defines which default language the user would like to use. For instance, this could be the default language for the GUI that is displayed on the UE, and/or the default language used for subtitles. BC Service Package Id: String Description: String BC Service package Profile Id: String IPTV Profile ParentalControlLevel: enumerated IPTVContentMarkerAuth orizedViewUser: String IPTVContentMarkerSour ceUser: String CoD Profile UEId: String UE Capabilities: String FFS UE Language preference : enumerated Users action recordable: boolean BC Profile 0..1 0..1 0..n 0..1 1..n PVR preference: enumarated: N-PVR storage limit PVR Profile 0..1 BC TV Service Id: String Quality Definition: enumerated BC TV Service 0..n Global Settings PC-CostLimit: string PC-TotalCostLimit: string PC-ClassificationRestriction: enumerated PC-TimePeriodRestriction: time PC-TotalPlayTimeLimit: string dynamic PC-activation: boolean PC-Contact: string PC-AdminUser:string 0..1 IPTVContentMarker AuthorizedViewUser: String IPTVContentMarkerS ourceUser: String AuthorizedControlUs er: String ParentalControlLevel:enum erated IPTVContentMarkerAuthori zedViewUser: String IPTVContentMarkerSource User: String PCh List PChId: string PCh Item PChItemServiceType:enumerated PChItemContentId: string PChItemStartTime: timestamp PChItemEndTime: timestamp PChItemOffset: timestamp 1..n 1..n 0..n 0..1 PCh Profile (TBD) 0..1 CR Settings CR notifications: enumerated UGC storage limit AuthorizedControlUser: String UGC Profiler 0..1 ICM Settings ICMrules: enumerated 0..1 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 38 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.