Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.246  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.4…   4.4.3…   5…   6…   7…   8…   8.3…   8.4   8.5…   8.6…   8.7   8.8…   8.9…   8.10…   8.11…   8.16…   9…   C   D…   E…

 

8.6  MBMS De-Registration ProcedureWord‑p. 49

8.6.0  Common MBMS De-Registration procedureWord‑p. 49

The MBMS De-Registration is the procedure by which a downstream node informs an upstream node that it does not need to receive signalling, session attributes and data for a particular MBMS bearer service anymore and therefore would like to be removed from the corresponding distribution tree.
The MBMS De-registration procedure is initiated:
  • By the SGSN or GGSN when the last MBMS UE Context for a particular MBMS bearer service is deleted from the node and the "list of downstream nodes" parameter in the corresponding MBMS Bearer Context is empty;
  • By the SGSN or GGSN when the last node registered in the "list of downstream nodes" de-registers from an MBMS bearer service for which there is no corresponding MBMS UE Context; or
  • By the DRNC that registered at an SGSN when it deletes the associated MBMS Service Context.
Copy of original 3GPP image for 3GPP TS 23.246, Fig. 11: MBMS De-Registration Procedure
Figure 11: MBMS De-Registration Procedure
(⇒ copy of original 3GPP image)
Up
  1. When the DRNC that is registered at an SGSN no longer hosts any UE interested in that MBMS bearer service, the DRNC requests the de-registration from the MBMS bearer service to its parent SGSN. As an implementation option, the DRNC may decide not to de-register from the MBMS bearer service immediately when these conditions are met, e.g. in order to avoid unnecessary signalling in the case where the RNC would again need the same MBMS bearer service shortly after. The SGSN removes the identifier of the RNC from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending an MBMS De-Registration Response message to the RNC. If an Iu bearer plane had been established between the DRNC and the SGSN for this MBMS bearer service, the Iu bearer plane is released. If the RNC is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376, RFC 3810 and RFC 4604.
  2. When the "list of downstream nodes" of a particular MBMS Bearer Context in the SGSN becomes empty and the SGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the SGSN sends an MBMS De-Registration Request (IP multicast address, APN) message to its upstream GGSN associated with the MBMS Bearer Context.
    The GGSN removes the identifier of the SGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending an MBMS De-Registration Response message to the SGSN. If a bearer plane had been established between the SGSN and the GGSN for this MBMS bearer service, the bearer plane is released.
  3. When the "list of downstream nodes" of a particular MBMS Bearer Context in the GGSN becomes empty and the GGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the GGSN sends a De-Registration Request (IP multicast address, APN) message to the BM-SC. Proxy and Transport function If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released.
    The BM-SC removes the identifier of the GGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending a De-Registration Response message to the GGSN.
Up

8.6.1  BM-SC initiated MBMS De-Registration ProcedureWord‑p. 50

This MBMS De-Registration Procedure is initiated by BM-SC when the specific MBMS bearer service is terminated. This procedure tears down the distribution tree for the delivery of session attributes and MBMS data. This procedure results in releasing of all MBMS Bearer Contexts and associated MBMS UE Contexts in the nodes along the distribution tree.
Copy of original 3GPP image for 3GPP TS 23.246, Fig. 12: BM-SC initiated MBMS De-Registration Procedure
Up
Step 1.
The BM-SC sends a De-Registration Request message to all GGSNs contained in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context to indicate the session is terminated and any related MBMS bearer resources shall be released.
The GGSN returns a De-Registration Response message to the BM-SC. The BM-SC releases all MBMS UE Contexts and the corresponding MBMS Bearer context.
Step 2.
The GGSN sends an MBMS De-Registration Request message to all SGSNs contained in the "list of downstream nodes" parameter. of the corresponding MBMS Bearer Context. The SGSN returns an MBMS De-registration Response message to the GGSN and releases all bearer resources if the state attribute of the MBMS Bearer Context is 'Active'. The GGSN releases all MBMS UE Contexts and the affected MBMS Bearer Context. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released.
Step 3.
The SGSN sends an MBMS De-Registration Request message to all BSCs/RNCs connected with this SGSN. The BSC/RNC returns an MBMS De-Registration Response message to the SGSN, and releases all bearer resources if the state attribute of the MBMS Service Context is 'Active'. If the BSC/RNC is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376, RFC 3810 and RFC 4604. The SGSN releases all MBMS UE Contexts and the affected MBMS Bearer Context. If a bearer plane had been established between the SGSN and the GGSN for this MBMS bearer service, the bearer plane is released.
Step 4.
The BSC/RNC releases the affected radio resources, all MBMS UE Contexts and the MBMS Service Context. The detailed procedures are specified in TS 25.346 and TS 43.246. RAN may notify the UEs that the MBMS Bearer service has being terminated, so that the UE can locally deactivate its MBMS UE context, detailed procedures are specified in TS 25.346 and TS 43.246.
Up

Up   Top   ToC