WO2006076865A1 - Procede de desactivation du service de diffusion multidiffusion multimedias - Google Patents

Procede de desactivation du service de diffusion multidiffusion multimedias Download PDF

Info

Publication number
WO2006076865A1
WO2006076865A1 PCT/CN2006/000099 CN2006000099W WO2006076865A1 WO 2006076865 A1 WO2006076865 A1 WO 2006076865A1 CN 2006000099 W CN2006000099 W CN 2006000099W WO 2006076865 A1 WO2006076865 A1 WO 2006076865A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms
context
sgsn
indication
ggsn
Prior art date
Application number
PCT/CN2006/000099
Other languages
English (en)
French (fr)
Inventor
Hai Zhang
Chang Duan
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to DE602006006966T priority Critical patent/DE602006006966D1/de
Priority to AT06705520T priority patent/ATE432598T1/de
Priority to EP06705520A priority patent/EP1821465B1/en
Publication of WO2006076865A1 publication Critical patent/WO2006076865A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to a multimedia multicast broadcast technology, and more particularly to a method for implementing activation of a multimedia multicast broadcast service. Background of the invention
  • the third generation mobile communication can provide higher data rate services than the second generation mobile communication, thereby supporting multiple business forms, such as: video telephone, picture download, high speed browsing Internet network And other services.
  • one type of service is characterized by: The service can be sent to users who subscribe to the service in the wireless network at the same time, for example: weather forecast, news clips, sports competition highlights, and the like.
  • the third generation of mobile communications introduced the concept of broadcast/multicast.
  • the upstream node always sends a data to the intermediate node; after receiving the data, the intermediate node receives the data according to the downstream node.
  • the number of nodes expecting to receive data copies the data and distributes the data to the downstream nodes that are expected to receive the data.
  • each branch of the multicast/broadcast service data transmission tree has only one piece of data for transmission, occupying one transmission resource, and the same is true for the data transmission of the root node and its downstream nodes.
  • the difference between the multicast service and the broadcast service is only that:
  • the multicast service only sends corresponding information to users who subscribe to certain information, and the broadcast service sends information to all users in the wireless network.
  • the multicast/broadcast service provides the same information to a large number of users at the same time, which can greatly save network resources.
  • a wireless network entity supporting broadcast/multicast services is a broadcast/multicast service.
  • the server (BM-SC) 201 the BM-SC 201 is connected to the TPF gateway GPRS support node (GGSN) 202 through a Gmb interface or a Gi interface, one The BM-SC 201 can be connected to multiple TPF GGSNs 202; the TPF GGSN 202 is connected to a Serving GPRS Support Node (SGSN) 203 via a Gn7Gp interface, and one GGSN 202 can be connected to multiple SGSNs 203; the SGSN 203 can pass The Iu interface is connected to a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) 204, and then the UTRAN 204 is connected to a User Equipment (UE) 206 via a Uu interface, and the SG
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System
  • UE User Equipment
  • GSM Global System
  • GERAN Enhanced Radio Access Network
  • the GGSN and the SGSN belong to nodes in the core network (CN) in the wireless network.
  • BM-SC provides functions for the provision and transmission of MBMS user services, and exists for MBMS user services.
  • the BM-SC can be used as an access point for MBMS content transmission, authorization and initiation of MBMS bearer services in PLMN, and can be used to schedule and transmit MBMS transmissions.
  • the BM-SC is a functional entity, as shown in Figure 3, consisting of four sub-sections: membership functions, session and send functions, proxy and transport functions, and business announcement functions.
  • the BM-SC membership function provides authorization for the user to request activation of the MBMS service, may have registration information of the MBMS service user, and may also generate charging information of the MBMS service user;
  • the membership function is a function of the MBMS bearer service layer, but It can provide functions of the user service layer, such as: membership function management, key management, etc. In this case, there is a Gi interface.
  • the BM-SC session and send function can schedule MBMS session transmissions.
  • the BM-SC proxy and transport function is a proxy server for Gmb interface point signaling transmission between the GGSN and other BM-SC sub-function entities, such as: BM-SC membership function and BM-SC session and send function.
  • BM-SC proxy and transport functions can also handle the routing of different information interactions, which are transparent to the GGSN.
  • the BM-SC service announcement function provides service announcements for multicast and broadcast MBMS user services.
  • the MBMS multicast service activation process registers the user in the network, so that the user can receive data of a specific multicast MBMS bearer service.
  • Activation is a signaling process between the UE and the network.
  • the user establishes an MBMS UE context for each user that activates the multicast MBMS bearer service in the UE, the SGSN, the GGSN, the BM-SC, and the BSC/RNC, and establishes the MBMS UE context to be similar to the normal PDP context establishment.
  • the MBMS multicast service deactivation process the user leaves an MBMS multicast service, and the user's MBMS UE context is deleted.
  • the MBMS UE context contains specific information of a particular MBMS bearer that the UE has joined.
  • the MBMS UE context is saved as part of the UE's Mobility Management (MM) context; in the GGSN, the MBMS UE context is saved separately.
  • MM Mobility Management
  • Each MBMS joined by the UE carries an MBMS UE context.
  • the MBMS UE context includes: IP multicast address, APN, in-use GGSN address, in-use SGSN address, TMGI, Linked NSAPI, and IMSI.
  • the IP multicast address is used to identify the MBMS bearer that the UE has joined;
  • the APN is the access point name that the IP multicast address has been defined;
  • the TMGI is the temporary mobile group identifier assigned to the MBMS bearer;
  • the Linked NSAPI is the UE.
  • NSAPI carrying the PDP context of IGMP/MLD signaling;
  • IMSI is the user identifier;
  • TI is the event identifier;
  • MBMS NSAPI is used to identify an MBMS UE context.
  • IP multicast address IP multicast address identifies a UE X X X X Iu - X X has joined the MBMS bearer Gb-none
  • the IP multicast address has been set X X X X Iu - X X
  • the GGSN address is used in the current context X
  • Linked NSAPI is hosted by the UE to carry IGMP MLD X X
  • (1) indicates that in the UE and the SGSN, the IMSI is valid in the MM context, the MM context includes the MBMS UE context; (2) indicates that in the RC, the IMSI is valid in the UE context, and the UE context includes the MBMS UE context; (3) The existence of IMSI is not based on MBMS.
  • Step 401 The UE sends an IGMP Leave message, an IGMP Leave message, or an MLD Leave message to the GGSN through a default PDP context, leaving an IP multicast address. Identify the specific multicast service.
  • the UE sends an IGMP Join message to the GGSN1.
  • the IPv6 protocol is used, the UE adds a message to the MLD. In this process, the IPv4 protocol is adopted. In this process, the GGSN corresponding to the default PDP context is GGSN1.
  • Step 402 The GGSN1 sends a Leave Indication message containing the IP multicast address, the APN, and the IMSI to the BM-SC proxy and the transport function, indicating that the UE is ready to leave the multicast service identified by the IP multicast address, the leave indication message.
  • the leave indication message was forwarded to the BM-SC member's greedy function.
  • Step 403 Upon receiving the leave indication message, the BM-SC membership function verifies that the IP multicast address corresponds to a valid MBMS service, and sends a UE delete request message with an IP multicast address, APN, and IMSI.
  • the GGSNL APN to which the Request gives the leave indication is to be consistent with that provided during the service activation process.
  • the BM-SC membership function may also trigger the MBMS UE context deactivation by sending a UE Delete Request message directly to GGSN1.
  • Step 404 Upon receiving the UE deletion request message or the GGSN1's own reason, the GGSN1 sends an MBMS UE context deactivation request message MBMS UE Context Deactivation Request containing the IP multicast address, the APN and the IMSI to the SGSN.
  • the IP Multicast Address, APN and IMSI together identify an MBMS UE context that needs to be deleted by the SGSN.
  • This step The APN in the message is the APN received in step 403.
  • the SGSN sends an MBMS UE context deactivation response message MBMS UE Context Deactivation Response to GGSN1, in response to which it receives the MBMS UE context deactivation request.
  • Step 405 The SGSN receives the MBMS UE context deactivation request message, or the SGSN's own reason.
  • the SGSN sends a Deactivate MBMS Context Request message containing the TI to the UE.
  • the TI identifies the MBMS UE that needs to be deleted by the UE. Context.
  • Step 406 The UE deletes the MBMS UE context, and sends a Deactivate MBMS Context Response message containing the TI to the SGSN.
  • Step 407 If the UE is in a Packet Domain Mobility Management (PMM) connection state and has been linked with the RAN, the SGSN sends an MBMS UE delink request MBMS UE De-Linking Request to the RNC, where the request includes an IP multicast address, APN. , TMGI.
  • the RAN deletes the MBMS UE context and sends an MBMS UE with TMGI to link the MBMS UE De-Linking Response to the SGSN.
  • PMM Packet Domain Mobility Management
  • Step 408 If the UE is currently allocated dedicated radio resources for transmitting MBMS data, the RAN releases the radio resource; if the shared radio resource is currently allocated for transmitting MBMS data, the RAN may decide to transfer the remaining UEs to For special resources, this step is optional.
  • Step 409 If the reason for deactivating the MBMS Context Accept message or the SGSN itself is received, the SGSN sends a Delete MBMS Context Request message containing MBMS_NSAPI Delete MBMS Context Request to the GGSN2 having the MBMS UE context.
  • the GGSN that actually provides the required MBMS service is GGSN2, and GGSN1 and GGSN2 may be the same GGSN, or may be different from GGSN1 in step 401 that receives the IGMP Leave Request.
  • Step 410 The GGSN2 deletes the MBMS UE context, and sends a Deactivation Indication message to the BM-SC to confirm that the MBMS UE context is successfully deactivated.
  • the BM-SC deletes the MBMS UE context and sends a confirmation message to the GGSN Deactivation Confirmatior Step 411: If no user in the GGSN2 receives the MBMS multicast service, and the "downstream node list" of the corresponding MBMS bearer context is empty, the GGSN2 sends an MBMS deregistration request message to the BM-SC proxy and the transport function.
  • the BM-SC proxy and transport function feeds back an MBMS Deregistration Response message MBMS Deregistration Response, and deletes the identity of GGSN2 in its own MBMS bearer context from the "downstream node list" parameter. This step is optional.
  • Step 412 The GGSN2 sends a Delete MBMS Context Response message to the SGSN to confirm that the MBMS UE context is deactivated.
  • the SGSN deletes the MBMS. UE context.
  • Step 413 If no user in the SGSN receives the MBMS multicast service, and the "downstream node list" of the corresponding MBMS bearer context is empty, the SGSN sends an MBMS Deregistration Request message to the GGSN2. GGSN2 feeds back an MBMS to register the response message Deregistration Response, and deletes the identity of the SGSN in its own BMS bearer context from the "downstream node list" parameter.
  • the MBMS service deactivation process deletes the MBMS UE context in the UE, the SGSN, and the GGSN, and the MBMS service deactivation process can be triggered by the UE, the SGSN, the BM-SC, and the GGSN.
  • the UE triggered deactivation process begins in step 401; the BM-SC triggered deactivation process begins in step 403; the GGSN triggered deactivation process begins in step 404; the SGSN triggered deactivation process begins in steps 405 and 409; MBMS UE De-linking is performed at step 407.
  • the SGSN routing area update refers only to the SGSN routing area update when the new SGSN does not support the MBMS service.
  • the .MBMS UE context of each MBMS service is associated with a certain PDP context through the associated NSAPI, if it is associated with a certain MBMS UE context on the PDP
  • the following is deactivated by the UE, SGSN or GGSN, which also triggers the SGSN to trigger the deactivation process.
  • the SGSN will perform the MBMS deactivation process from steps 405 and 409.
  • the UE performs the GPRS de-attachment, the SGSN routing area update, or the UE deletes the default PDP context, so that all the corresponding MBMS UE contexts need to be deactivated on the network side and the terminal side. Since the user may apply for dozens of MBMS bearer services, when the deactivation process needs to be performed, according to the existing processing procedure, the steps 405 to 413 are repeatedly performed to complete the correspondence corresponding to all the MBMS services. The deletion of the MBMS UE context. Obviously, the entire process flow is redundant, which not only reduces efficiency, but also increases equipment complexity. In particular, performing so many repetitive signaling on the air interface significantly reduces the utilization of wireless resources. Summary of the invention
  • the main purpose of the present invention is to provide a method for deactivating a multimedia multicast broadcast service, which can complete the deletion of the context of the related MBMS UE in a simple process, which not only reduces the complexity of the device, but also greatly improves the wireless. Utilization of the interface.
  • a method for implementing deactivation of a multimedia multicast broadcast service comprising:
  • the BM-SC determines that the relevant MBMS UE context needs to be deleted according to the detachment indication, and then deletes the relevant MBMS UE context; and the GGSN returns to the SGSN.
  • the SGSN that received the response message deletes the associated MBMS UE context.
  • the response message carries a detach indication.
  • the method specifically includes:
  • the SGSN sends a delete MBMS context request carrying the detachment indication to the GGSN, and the GGSN that receives the request determines that the relevant MBMS UE context needs to be deleted according to the detachment indication, and then deletes the related MBMS UE context, and sends the MME-SC to the BM-SC.
  • Sending a deactivation indication carrying a detachment indication After receiving the deactivation indication with the detachment indication, the BM-SC determines that the relevant MBMS UE context needs to be deleted according to the detachment indication, deletes the related MBMS UE context, and sends a deactivation confirmation message to the GGSN;
  • the GGSN After receiving the deactivation confirmation, the GGSN returns a delete MBMS context response to the SGSN, and after receiving the SGSN, deletes its own related MBMS UE context.
  • the method further includes: the SGSN sending a delinking request carrying the detachment indication to the RAN, and the RAN receiving the delinking request determines, according to the detaching indication, that the related MBMS UE needs to be deleted.
  • the context deletes its own associated MBMS UE context and returns a de-link response to the SGSN.
  • the de-linking response returned by the RAN to the SGSN carries a detachment indication.
  • the method further includes: the SGSN sending, to the UE, a deactivated MBMS Context Request carrying the detachment indication, where the UE receiving the request determines, according to the detachment indication, that the related MBMS needs to be deleted.
  • the UE context deletes its own associated MBMS UE context and returns a deactivated MBMS Context Response to the SGSN.
  • the deactivated MBMS context response returned by the UE to the SGSN carries a detach indication.
  • all MBMS UE contexts corresponding to different MBMS services activated by the UE are associated with the same PDP context, and the MBMS UE context related to the deletion is: All MBMS UE contexts of the UE are deleted.
  • the MBMS UE context corresponding to the different MBMS services activated by the UE is associated with a different PDP context
  • the MBMS UE context related to the deletion is: deleting all the UEs associated with the currently deactivated PDP context.
  • MBMS UE context is: deleting all the UEs associated with the currently deactivated PDP context.
  • the detachment indication includes one or more identifiers of the MBMS UE context to be deleted, and the BM-SC, the GGSN, and the SGSN delete the related MBMS UE contexts as: BM-SC, GGSN, SGSN Delete the MBMS UE context specified by the detach indication in itself.
  • the BM-SC and the GGSN that receive the detachment indication may delete all MBMS UE contexts related to the UE.
  • the RAN that receives the detachment instruction, The UE deletes all its associated MBMS UE contexts.
  • the detachment indication carries an identifier indicating that all MBMS UE contexts related to the specified UE are deleted; and the BM-SC, GGSN, and SGSN that have received the detachment indication delete all MBMS UEs related to the UE. Context.
  • the method further comprises: receiving, by the RAN, the detachment indication, the UE deleting all related MBMS UE contexts.
  • the method further includes: the UE automatically deleting the locally saved related MBMS UE context; or: after receiving the detach request from the SGSN, the UE deletes the locally saved related MBMS UE context; or the UE is receiving After the deactivated PDP context accept message from the SGSN, the locally saved related MBMS UE context is deleted; or the UE deletes the locally saved related MBMS UE context after receiving the deactivated PDP context request from the SGSN.
  • the UE automatically deletes the locally saved MBMS UE context associated with the currently deactivated PDP context; or, after receiving the detach request from the SGSN, the UE deletes the locally saved and currently deleted The MBMS UE context associated with the activated PDP context; or, after receiving the deactivated PDP context accept message from the SGSN, the UE deletes the locally saved MBMS UE context associated with the currently deactivated PDP context; or After receiving the deactivated PDP context request from the SGSN, the UE deletes the locally saved MBMS UE context associated with the currently deactivated PDP context.
  • the detach indication is an identifier indicating that the related MBMS UE context needs to be deleted, or an identifier indicating whether the related MBMS UE context needs to be deleted by using different values.
  • the MBMS UE context corresponding to the different MBMS services activated by the UE is associated with different PDP contexts, and the detach indication is an identifier of one or more MBMS UE contexts to be deleted.
  • the identifier of the MBMS UE context is: the MBMS service corresponding to the MBMS UE context is stored in the Linked NSAPI in the RAN, the SGSN, the GGSN, and the BM-SC during the activation process.
  • the deleting the MBMS UE Context Request message is sent by the SGSN to the GGSN when the GPRS detach procedure is performed, or the SGSN routing area update procedure of the new SGSN does not support the MBMS service triggers the multimedia multicast broadcast service deactivation process.
  • the de-linking request is sent by the SGSN to the GPRS de-attachment process, or the SGSN routing area update process in which the new SGSN does not support the MBMS service, or the PDP context deactivation process triggers the multimedia multicast broadcast service deactivation process.
  • RAN the GPRS de-attachment process
  • the PDP context deactivation process triggers the multimedia multicast broadcast service deactivation process.
  • the deactivated MBMS Context Request is sent by the SGSN to the UE when the PDP context deactivation process triggers the multimedia multicast broadcast service deactivation process.
  • the SGSN selects an appropriate timing to trigger the deactivation process, and notifies the relevant network entity to perform the operation of deleting all relevant MBMS UE contexts by carrying the detachment indication, in the relevant step.
  • the related MBMS UE contexts to be deleted can be deleted by only one message, thereby avoiding the process redundancy caused by repeating the same steps when a certain UE applies for multiple MBMS bearer services, thus not only reducing the process.
  • the complexity increases efficiency; reduces the load on core network devices and improves the utilization of wireless resources.
  • the present invention provides multiple implementations for different situations, not only for a wide range of applications, but also for flexibility, convenience, and billing.
  • FIG. 1 is a schematic diagram of a transmission principle of a multicast service
  • FIG. 2 is a schematic structural diagram of a wireless network supporting broadcast/multicast services
  • Figure 3 is a structural diagram of the functional entities of the BM-SC
  • FIG. 5 is a flowchart of an implementation of an embodiment of the present invention.
  • FIG. 7 is a flowchart of an implementation of another embodiment of the present invention. Mode for carrying out the invention
  • the core idea of the present invention is: In the GPRS de-attachment process or the PDP context deactivation process, the SGSN selects an appropriate timing, triggers a deactivation process, and notifies the relevant network entity to perform deletion of the relevant MBMS UE context by carrying a detachment indication. operating.
  • the detachment indication may be only an identifier, for example, a single bit is set, and the identifier has two different usage modes: one is, if the indication is carried, the related MBMS UE context needs to be deleted, if not, It means that the related MBMS UE context does not need to be deleted.
  • the other is that the detachment indication is always carried in the interaction message of each network entity, and different values are used to indicate whether the relevant MBMS UE context needs to be deleted, for example: Indicates that deletion is not required, and 1 means that deletion is required; or true means deletion is required, false means no deletion is required.
  • the detachment indication may also be a message carrying one or more MBMS UE context identifiers to be deleted, for example:
  • the deactivated MBMS UE context message may be used as a detachment indication.
  • the detach indication may also be a message carrying an indication indicating that all MBMS UE contexts associated with the designated UE are deleted.
  • the detachment indication is an identifier
  • the following uses the first usage mode, that is, whether the detachment indication is carried out to indicate whether the MBMS UE context needs to be deleted.
  • the appropriate timing can be divided into three cases:
  • the SGSN may be as shown in FIG.
  • the deactivation process is started, or the deactivation process is started from step 409, and the related MBMS UE context of the UE in the UE, the SGSN, and the GGSN is deleted.
  • the detach indication is a message carrying an MBMS UE context identifier
  • the deleted related MBMS UE context is one, or more, or all of the identifiers specified.
  • an identifier dedicated to indicating that all relevant MBMS UE contexts are deleted may be used, and the identifier is carried in the detachment indication message. 2
  • the SGSN In the case of RDP context deactivation, if the PDP context associated with the MBMS UE context by the associated NSAPI is deactivated by the UE, SGSN or GGSN, the SGSN also performs the deactivation procedure starting from step 407 or step 409 shown in FIG. , delete the associated MBMS UE context associated with the deactivated PDP context.
  • the detach indication is a message carrying an MBMS UE context identifier
  • the deleted related MBMS UE context is one, or more, or all of the identifiers specified.
  • an identifier dedicated to indicating that all relevant MBMS UE contexts are deleted may be used, and the identifier is carried in the detachment indication message.
  • the SGSN may also perform deactivation from step 405 shown in FIG. Flow, deleting the associated MBMS UE context associated with the deactivated PDP context.
  • the detach indication is a message carrying the MBMS UE context identifier
  • the associated MBMS UE context deleted is one, or more, or all of the identifiers specified.
  • an identifier specifically for indicating deletion of all relevant MBMS UE contexts may be used, and the identifier is carried in the detachment indication message.
  • each entity such as BM-SC, GGSN, SGSN, RAN, UE, deletes all MBMS UE contexts related to the specified UE, and all the processes and situations described are also applicable to the case of deleting the specified MBMS UE context. .
  • the specific deactivation process is also divided into three types:
  • the SGSN When the SGSN starts the deactivation process from step 407, the SGSN carries the detachment indication in the MBMS UE delink request MBMS UE De-Linking Request sent to the RAN, and the RAN deletes all relevant MBMS UEs of the corresponding UEs in the SGSN.
  • the SGSN sends a delete MBMS context request carrying the detach indication to the GGSN, and the GGSN deletes all related MBMS UE contexts of the corresponding UE in the GGSN;
  • the GGSN sends a deactivation indication carrying the detachment indication to the BM-SC, and the BM-SC deletes all related MBMS UE contexts of the corresponding UEs in the BMSN.
  • the GGSN returns a carry and detach indication to the SGSN.
  • the MBMS Context Response is deleted, and the SGSN deletes all relevant MBMS UE Contexts of the corresponding UEs in the UE.
  • the SGSN When the SGSN starts the deactivation process from step 409, the SGSN carries the detachment indication in the Delete MBMS Context Request sent to the GGSN, and the GGSN deletes all relevant MBMS UE contexts of the corresponding UEs in the GGSN; In step 410, the GGSN sends a deactivation indication carrying the detachment indication to the BM-SC, and the BM-SC deletes all relevant MBMS UE contexts of the corresponding UEs in the BM-SC; in the subsequent step 412, the GGSN returns the bearer to the SGSN. From the indicated deletion MBMS context response, the SGSN deletes all relevant MBMS UE contexts of the corresponding UEs in itself.
  • step 405 when the SGSN starts the deactivation process from step 405, the SGSN carries the detachment indication in the Deactivate MBMS Context Request sent to the UE, and the UE deletes all relevant MBMS UE contexts of the corresponding UEs in the UE;
  • steps in case a) are exactly the same according to 407, 409 ⁇ 410, 412 and their corresponding processing.
  • the UE needs to delete the relevant MBMS locally in the GPRS detach procedure or the SGSN routing area update.
  • UE context Specifically: if it is a terminal initiated GPRS detach procedure or an SGSN routing area update process, the terminal automatically deletes the locally saved MBMS UE context; if it is a network initiated GPRS detach procedure or an SGSN routing area update process, the terminal receives the After the SGSN's detach request message, the locally saved MBMS UE context is deleted.
  • the specific GPRS detachment process or the SGSN routing area update process is a standard procedure specified by the 3GPP. For reference, the 3GPP 23.060 specification is not described here.
  • the UE since the PDP context associated with the MBMS UE context of a certain UE is deactivated, the UE has to delete the corresponding MBMS UE context locally. Specifically: if it is a terminal-triggered PDP context deactivation process, the UE receives the deactivated PDP context acceptance sent by the SGSN to the UE. After the message, the locally saved MBMS UE context is deleted. If the SGSN or the GGSN triggers the PDP context deactivation process, the UE deletes the locally saved MBMS UE context after receiving the Deactivate PDP Context Request message from the SGSN.
  • the specific PDP context deletion process is a standard procedure specified by the 3GPP, and may be referred to the 3GPP 23.060 specification, and details are not described herein again.
  • Association One is that all MBMS UE contexts corresponding to different MBMS services activated by the UE are associated with the same PDP context as the default PDP context; the other is that all MBMS UE contexts corresponding to different MBMS services activated by the UE are used.
  • Associated with different PDP contexts in the case of PDP context deactivation, in the former case, deleting all relevant MBMS UE contexts is to delete all MBMS UE contexts of the UE; and in the latter case, deleting all relevant MBMS UE contexts. All MBMS UE contexts associated with the currently deactivated PDP context of the UE are deleted.
  • all MBMS UE contexts activated by UE1 are associated with a default PDP context; UE, SGSN or GGSN triggers a GPRS detach procedure for UE1, and is saved in the SGSN at this time.
  • the state of the UE1 is the PMM connection, that is, the UE1 is in the PMM connection state, and has been linked with the RAN.
  • the SGS starts the MBMS service deactivation process from step 407 shown in FIG. 4, and performs the deletion operation of all the MBMS UE contexts. As shown in Figure 5, the following steps are specifically included:
  • Step 507 The SGSN sends an MBMS UE to link the request to the RNC in the RAN, where The request carries the IP multicast address, APN, and TMGI. Moreover, since the GPRS detach procedure is triggered, all MBMS UE contexts corresponding to UE1 in the RAN should be deleted. Therefore, the MBMS UE de-link request also carries the detachment. Indicates that all MBMS UE contexts associated with UE1 are to be deleted.
  • the RA After receiving the MBMS UE delinking request with the detach indication, the RA deletes all MBMS UE contexts related to UE1, and sends an MBMS UE delinking response to the SGSN, where the response carries at least TMGI, and the response may be Carry the detachment instructions, or you can not carry them.
  • Step 508 It is identical to the processing of step 408 in the existing deactivation process.
  • Step 509 The SGS sends a Delete MBMS Context Request message containing the MBMS-NSAPI to the GGSN having the MBMS UE Context, which may be different from the GGSN receiving the IGMP Leave Request. Since the GPRS detach procedure is triggered, the GPRS detach procedure deactivates the PDP context of the UE1, so all the MBMS UE contexts associated with the deactivated PDP context need to be deleted. Therefore, the delete MBMS context request also carries the teardown. Departure instructions.
  • Step 510 After receiving the delete MBMS context request with the detach indication, the GGSN deletes all MBMS UE contexts related to UE1, and sends a deactivation indication message to the BM-SC to confirm that the MBMS UE context is successfully activated.
  • the deactivation indication carries a detachment indication.
  • the BM-SC After receiving the deactivation indication message with the detachment indication, the BM-SC deletes all MBMS UE contexts related to UE1, and sends a deactivation confirmation message to the GGSN, and the BM-SC replies with the deactivation confirmation message.
  • the detachment instruction may or may not be carried.
  • Step 511 It is identical to the processing of step 411 in the existing deactivation process.
  • Step 512 The GGSN sends a delete MBMS Context Response message to the SGSN, and confirms that all the MBMS UE contexts of the UE1 are deleted.
  • the response message may carry the detachment indication or may not be carried.
  • the SGSN After receiving the MBMS Context Response, the SGSN deletes all MBMS UE contexts associated with UE1.
  • Step 513 It is identical to the processing of step 413 in the existing deactivation process.
  • the terminal if the terminal initiates the GPRS detach procedure, the terminal automatically deletes the locally saved MBMS UE context; if it is a network initiated GPRS detach procedure, the terminal deletes the local after receiving the detach request message from the SGSN.
  • the saved MBMS UE context if it initiates the GPRS detach procedure, the terminal automatically deletes the locally saved MBMS UE context; if it is a network initiated GPRS detach procedure, the terminal deletes the local after receiving the detach request message from the SGSN.
  • the saved MBMS UE context if it initiates the GPRS detach procedure, the terminal automatically deletes the locally saved MBMS UE context; if it is a network initiated GPRS detach procedure, the terminal deletes the local after receiving the detach request message from the SGSN.
  • the saved MBMS UE context if it
  • Embodiment 2 Compared with the prior art, this embodiment is equivalent to performing the deactivation process from the original step bare 407, omitting steps 405 and 406, and each step of the correlation will be related to all MBMS UE contexts related to UE1 by one message. All deleted, greatly reducing the complexity of processing and improving processing efficiency.
  • Embodiment 2 is equivalent to performing the deactivation process from the original step bare 407, omitting steps 405 and 406, and each step of the correlation will be related to all MBMS UE contexts related to UE1 by one message. All deleted, greatly reducing the complexity of processing and improving processing efficiency.
  • Embodiment 2 is equivalent to performing the deactivation process from the original step bare 407, omitting steps 405 and 406, and each step of the correlation will be related to all MBMS UE contexts related to UE1 by one message. All deleted, greatly reducing the complexity of processing and improving processing efficiency.
  • Embodiment 2 is equivalent to performing the deactivation process
  • UE1 is still taken as an example, and all MBMS UE contexts activated by UE1 are associated with a default PDP context; UE, SGSN or GGSN triggers a GPRS detach procedure for UE1, and UE1 is in a PMM connection state, and Linked to the RAN, and the RAN deletes all Radio Access Bearers (RABs) of UE1 in the process of performing GPRS detachment. Therefore, the RAN has automatically deleted all MBMS UE contexts related to UE1, and then the SGSN Step 409 shown in FIG. 4 starts the MBMS service deactivation process, and performs the deletion operation of all MBMS UE contexts. As shown in FIG. 6, the following steps are specifically included:
  • Steps 609 to 613 The processing and description of steps 509 to 513 in the first embodiment are completely the same.
  • the terminal if it is a GPRS detach procedure initiated by the terminal, the terminal automatically deletes the locally saved MBMS UE context; if it is a network initiated GPRS detach procedure, after receiving the detach request message from the SGSN, the terminal Delete the locally saved MBMS UE context.
  • this embodiment is equivalent to performing the deactivation process from the original step 409, and steps 405 to 408 are also omitted, and each of the related steps will all the MBMS UE contexts related to UE1 by one message. Deleted, greatly reducing the complexity of processing and improving processing efficiency.
  • the SGSN also starts the MBMS service deactivation process from step 409 shown in FIG. 4 because the UE1 is in the PMM idle state. That is, it is carried out in accordance with the processing flow of this embodiment.
  • the old SGSN when the UE initiates the SGSN routing area update process, if the new SGSN does not support the MBMS service, the old SGSN also triggers the MBMS service deactivation process to delete all relevant MBMS UE contexts of the corresponding UE.
  • the MBMS service deactivation procedure initiated by the SGSN is the same as the MBMS service deactivation procedure triggered by the GPRS detachment. That is to say, the deactivation process described in the first embodiment and the second embodiment is also applicable to the case where the new SGSN does not support the MBMS service deactivation triggered by the MBMS service when the SGSN routing area is updated.
  • Embodiment 3 Embodiment 3:
  • UE1 is still used as an example, and all MBMS UE contexts activated by UE1 are associated with a default PDP context.
  • the default PDP context is deactivated by the UE, the SGSN, or the GGSN.
  • the UE1 is in the PMM connection state.
  • the SGSN since the RAN does not know the relationship between the deactivated PDP context and the MBMS UE context for the PDP context deactivation process, therefore, the SGSN must start the MBMS service from step 407 shown in FIG. Deactivation process, delete all MBMS UE contexts. Referring to FIG. 5, the following steps are specifically included:
  • Step 11 The SGSN sends an MBMS UE delink request to the RC, where the request carries an IP multicast address, APN, TMGI; and, since the deactivation of the PDP context associated with the MBMS UE context is triggered, the corresponding UE1 in the RAN All MBMS UE contexts should be deleted. Therefore, the MBMS UE delinking request also carries a detach indication indicating that all MBMS UE contexts related to UE1 are to be deleted.
  • the RAN After receiving the MBMS UE delinking request with the detachment indication, the RAN deletes all the MBMS UE contexts related to the UE1, and returns an MBMS UE delinking response message to the SGSN, where the response message may carry the detachment indication, or may Do not carry.
  • Steps 12 to 17 The processing and description of steps 508 to 513 in the first embodiment are identical.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • UE1 is still taken as an example, and all MBMS UE contexts activated by UE1 are related to A default PDP context association, the default PDP context is deactivated by the UE, SGSN or GGSN, and the SGSN performs the MBMS deactivation procedure starting from step 405 shown in FIG. As shown in FIG. 7, the following steps are specifically included:
  • Step 705 The SGSN sends a deactivated MBMS Context Request message containing the TI to the UE, where the TI identifies the MBMS UE context that needs to be deleted by the UE. Since the PDP context associated with the MBMS UE context is deactivated, the deactivated MBMS Context Request also carries a detach indication indicating that all MBMS UE Contexts associated with the deactivated PDP context are to be deleted.
  • Step 706 After receiving the deactivated MBMS Context Request carrying the detach indication, the UE deletes all MBMS UE contexts, and sends a deactivated MBMS Context Response message containing the TI and the detach indication to the SGSN.
  • the response message may carry the detachment indication or may not be carried.
  • Steps 707 to 713 The processing and description of steps 507 to 513 in the first embodiment are completely the same.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the UE1 is used as an example, and the MBMS UE context activated by the UE1 is associated with a different PDP context.
  • the deletion and the deactivated PDP context need to be performed.
  • the associated MBMS UE context, the MBMS UE context not associated with the deactivated PDP context does not have to be deleted.
  • UE1 is in the PMM connection state and has been linked with the RAN.
  • the SGSN starts the MBMS service deactivation process from step 407 shown in FIG. 4, and performs the deletion operation of the related MBMS UE context.
  • the UE since a certain PDP context associated with the MBMS UE context is deactivated, the UE needs to locally delete the corresponding MBMS UE context. Specifically, if it is a terminal-triggered PDP context deactivation process, after receiving the deactivate PDP context accept message sent by the SGSN to the UE, the UE deletes the locally saved MBMS UE context associated with the deactivated PDP context and associated with the Linked_NSAPI. If it is the PDP context deactivation process triggered by the SGSN or the GGSN, after receiving the deactivate PDP context request message, the UE deletes the locally saved MBMS UE context associated with the deactivated PDP context and associated with the Linked-NSAM. Specific PDP The context deletion process is a standard procedure specified by the 3GPP, and may be referred to the 3GPP 23.060 specification, and details are not described herein again.
  • processing steps in this embodiment are similar to the first embodiment, and specifically include the following steps:
  • Step 21 The SGSN sends an MBMS UE delinking request to the RNC, where the request carries an IP multicast address, APN, and TMGL. Since the PDP context associated with the MBMS UE context is deactivated, the SGSN may send multiple MBMS UEs. The identity of the context is included in an MBMS UE delink request. In this way, the RAN will delete the MBMS UE context associated with the deactivated PDP context corresponding to UE1 according to the identifier of the MBMS UE context, and send an MBMS UE to link the response to the SGSN, where the response message carries the TMGI.
  • the method for identifying a plurality of MBMS UE contexts may be a combination of multiple IP multicast addresses, APNs, TMGIs; or a Linked NSAPI, that is, a PDP context recorded in the SGSN and bound to all of these MBMS UE contexts.
  • NSAPI if this is the method, the SGSN needs to send the NSAPI of the PDP context bound to these MBMS UE contexts to the RAN when the MGSN performs the MBMS UE linking mechanism, and the RAN saves the NSAPI as the Linked NSAPI to the MBMS UE context in the RAN.
  • the specific link mechanism may refer to the 3GPP 23.246 specification, and details are not described herein again.
  • Step 22 It is identical to the processing of step 408 in the existing deactivation process.
  • Step 23 The SGSN sends a Delete MBMS Context Request message containing the MBMS-NSAPI to the GGSN that has the MBMS UE context, which may be different from the IGMP received.
  • the PDP context is deleted.
  • multiple MBMS UE contexts associated with the PDP context may be deleted. Therefore, the identifiers of multiple MBMS UE contexts associated with the PDP context are included in the deleted MBMS context request sent by the SGSN to the GGSN. In the message.
  • the method for identifying multiple MBMS UE contexts may be multiple MBMS NSAPIs; or may be a Linked NSAPI, that is, an NSAPI recorded in the SGSN and bound to all of these MBMS UE contexts, if this is the method, SGSN in MBMS multicast service
  • the NSAPI of the PDP context bound to the MBMS UE context is sent to the GGSN as a Linked NSAPI.
  • the GGSN saves the NSAPI in its own related MBMS UE context.
  • the specific service activation procedure can refer to the 3GPP 23.246 specification. This will not be repeated here.
  • Step 24 After receiving the delete MBMS context request that includes the MBMS UE context identifier associated with the deactivated PDP context, the GGSN deletes the association between the UE1 and the deactivated PDP context according to the MBMS UE context identifier information carried in the deleted MBMS context request.
  • the MBMS UE context ; and sends a deactivation indication message to the BM-SC to confirm that the MBMS UE context is successfully deactivated, and the deactivation indication carries the identifier of all MBMS UE contexts associated with the deactivated PDP.
  • the BM-SC After receiving the deactivation indication message of the MBMS UE context identifier associated with the deactivated PDP context, the BM-SC deletes the MBMS associated with the deactivated PDP context of the UE1 according to the MBMS UE context identifier information carried in the deactivation indication. The UE context and send a deactivation confirmation message to the GGSN.
  • the method for identifying multiple MBMS UE contexts may be multiple TMGIs; or a Linked NSAPI, that is, the NSAPI of the PDP contexts recorded in the SGSN and bound to all of these MBMS UE contexts, if this is the method, the GGSN
  • the NSAPI of the PDP context bound to the MBMS UE context is saved as the Linked NSAPI in the MBMS UE context of the BM-SC.
  • the specific service activation procedure can refer to the 3GPP 23.246 specification. Narration.
  • Step 25 It is identical to the processing of step 411 in the existing deactivation process.
  • Step 26 The GGSN sends a Delete MBMS Context Response message to the SGSN to confirm that the relevant MBMS UE context is deleted. After receiving the SGSN, the SGSN deletes the MBMS UE context of the UE1 associated with the deactivated PDP context. .
  • Step 27 It is identical to the processing of step 413 in the existing deactivation process.
  • the UE1 is used as an example, and the MBMS UE context activated by the UE1 is associated with a different PDP context.
  • the deletion and the deactivated PDP context need to be performed.
  • the associated MBMS UE context, the MBMS UE context not associated with the deactivated PDP context does not have to be deleted.
  • the SGSN performs the MBMS service deactivation process from step 705 shown in FIG. 7, and performs the deletion operation of the related MBMS UE context.
  • UE1 does not delete the MBMS UE context locally, and the SGSN carries the TI and the detach indication in the deactivated MBMS Context Request message of step 705 shown in FIG.
  • the UE1 After receiving the deactivated MBMS Context Request message carrying the detachment indication, the UE1 finds a corresponding MBMS UE context according to the TI, and then finds the Linked NSAPI saved in the MBMS context, and then deletes all the MBMS UEs in the UE1 that have saved the Linked NSAPI. Context.
  • the detachment indication may be carried, or not carried.
  • the detachment indication carried in step 705 and step 706 is an indication identifier
  • the detachment indication carried in step 707 and subsequent steps 707 is a plurality of identifiers to delete the MBMS UE context.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Description

一种实现多媒体组播广播业务去激活的方法 技术领域
本发明涉及多媒体组播广播技术， 尤指一种实现多媒体组播广播业务去 激活的方法。 发明背景
随着第三代移动通信技术的发展， 第三代移动通信可以提供比第二代移 动通信更高数据速率的服务， 从而支持多种业务形式， 比如： 视频电话、 图 片下载、 高速浏览 Internet网絡等服务。 其中， 有一类业务的特点是： 该业务 可以同时给无线网络中订阅了该业务的用户进行发送， 比如说： 天气预报、 新闻短片、 体育比赛集锦等等。 利用这些业务同时发送的特点， 第三代移动 通信引入了广播 /组播的概念。
参见图 1 所示， 对于一个中间节点而言， 无论其下游包含多少个期待接 收数据的节点， 其上游节点总是向该中间节点发送一份数据； 该中间节点收 到数据后， 根据其下游期待接收数据的节点数量复制该数据， 并向其下游各 期待接收该数据的节点分发该数据。 这样， 組播 /广播业务数据传输树的每一 条分支都只有一份数据进行传输 , 占用一份传输资源, 根节点与其下游节点 的数据传输也是如此。 组播业务和广播业务的区别点仅在于： 组播业务只向 订阅了某些信息的用户发送相应信息， 广播业务则向无线网络中的所有用户 发送信息。 由以上描述可见， 通过组播 /广播业务同时向大量用户提供相同信 息， 能够极大地节省网络资源。
图 2为支持广播 /组播业务的无线网絡结构示意图， 如图 2所示， 现有第 三代合作伙伴计划 （3GPP ) 中， 支持广播 /组播业务的无线网络实体为广播 / 组播业务服务器（ BM-SC ) 201 , BM-SC 201通过 Gmb接口或 Gi接口与 TPF 关口 GPRS支持节点（GGSN, Gateway GPRS Support Node ) 202相连， 一个 BM-SC 201可与多个 TPF GGSN 202相连； TPF GGSN 202通过 Gn7Gp接口 与服务 GPRS支持节点 （ SGSN, Serving GPRS Support Node ) 203相连， 一 个 GGSN 202可与多个 SGSN 203相连； SGSN 203可通过 Iu接口与通用移动 通信系统（UMTS ) 陆地无线接入网 （UTRAN ) 204相连， 然后 UTRAN 204 通过 Uu接口与用户终端 （UE ) 206相连， SGSN 203也可通过 Iu/Gb接口与 余球移动通信系统（ GSM )增强无线接入网（ GERAN ) 205相连，然后 GERAN 205通过 Um接口与 UE 207相连。 其中， GGSN和 SGSN属于无线网络中核 心网 （CN ) 内的节点。
BM-SC作为广播组播业务中心为 MBMS用户业务的提供和发送提供功 能，为 MBMS用户业务而存在。 BM-SC可以作为一个在 PLMN中用于 MBMS 内容传输、 授权和发起 MBMS承载业务的接入点， 并且可以用于调度和发送 MBMS传输。
BM-SC是一个功能实体， 如图 3所示， 包含四个子部分： 成员资格功能、 会话和发送功能、 代理和传输功能、 业务宣告功能。 其中， BM-SC成员资格 功能提供用户请求激活 MBMS业务的授权， 可能拥有 MBMS业务用户的注 册信息，还可能产生 MBMS业务用户的计费信息；成员资格功能是一个 MBMS 承载业务层的功能， 但是可以提供用户业务层的功能， 例如： 成员资格功能 管理， 密钥管理等， 这种情况下， 存在 Gi接口。 BM-SC会话和发送功能能够 调度 MBMS会话发送。 BM-SC代理和传输功能是一个代理服务器，用于 GGSN 和其它 BM-SC子功能实体之间的 Gmb接口点信令传输， 例如： BM-SC成员 资格功能和 BM-SC会话和发送功能。 此外， 当 BM-SC为多个物理网络元素 服务时， BM-SC代理和传输功能也能处理， 路由不同信息的交互， 对 GGSN 是透明的。 BM-SC业务宣告功能能为组播和广播 MBMS用户业务提供业务宣 告。
MBMS组播业务激活过程将用户在网络中注册， 使该用户可以接收一个 特定组播 MBMS承载业务的数据。 激活是 UE与网络之间的信令过程， 该过 程为每个激活了组播 MBMS承载业务的用户在 UE、 SGSN、 GGSN、 BM-SC 以及 BSC/RNC建立 MBMS UE上下文， 建立 MBMS UE上下文与普通 PDP 上下文建立相似。 在 MBMS组播业务去激活过程中， 用户离开一个 MBMS 组播业务， 用户的 MBMS UE上下文将被删除。
MBMS UE上下文包含 UE已经加入的一个特定 MBMS承载的特定信息。 在 UE和 SGSN, MBMS UE上下文作为 UE的移动性管理（MM )上下文的 一部分保存； 在 GGSN， MBMS UE上下文单独保存。 UE加入的每个 MBMS 承载有一个 MBMS UE上下文。
参见表一所示， MBMS UE上下文有包括： IP组播地址、 APN、在用 GGSN 地址、 在用 SGSN地址、 TMGI、 Linked NSAPI和 IMSI等。 其中， IP组播地 址用于标识一个 UE已经加入的 MBMS承载； APN为该 IP组播地址已经被 定义的接入点名称； TMGI为分配给 MBMS承载的临时移动组标识； Linked NSAPI为由 UE承载 IGMP/MLD信令的 PDP上下文的 NSAPI; IMSI为用户 标识； TI为事件标识； MBMS NSAPI用于标识一个 MBMS UE上下文。
参数 定义 UE SGSN GGSN RNC BSC BM-SC
IP组播地址 IP組播地址标识一个 UE X X X X Iu - X X 已经加入的 MBMS承载 Gb-none
APN 该 IP组播地址已经被定 X X X X Iu - X X 义的接入点名称 Gb-none 在用 GGSN地址 当前上下文使用的 X
GGSN的地址
在用 SGSN地址 X
TMGI 分配给 MBMS承载的临 X X X Iu - X
时移动组标识 Gb-none
Linked NSAPI 由 UE去承载 IGMP MLD X X
信令的 PDP 上下文的
NSAPI
Figure imgf000006_0001
表一中， （1)表示在 UE和 SGSN中， IMSI在 MM上下文中有效， MM上 下文包含 MBMS UE上下文； （2)表示在 R C中， IMSI在 UE上下文中有效， UE上下文包含 MBMS UE上下文； （ 3 ) IMSI的存在不基于 MBMS。
现有技术中正常的 MBMS业务去激活过程如图 4所示， 包括以下步骤： 步骤 401： UE通过默认的 PDP上下文给 GGSN发送 IGMP离开消息 IGMP Leave或 MLD离开消息， 离开一个由 IP组播地址标识的特定的组播业务。
这里，如果采用 IPv4协议，则 UE向 GGSN1发 IGMP加入消息 IGMP Join; 如果釆用 IPv6协议， 则 UE向 MLD加入消息， 本流程中是采用 IPv4协议。 本流程中， 与默认 PDP上下文对应的 GGSN为 GGSN1。
步骤 402: GGSN1给 BM-SC代理和传输功能发送一个含有 IP組播地址、 APN和 IMSI的离开指示消息 Leave Indication, 指示 UE准备离开由该 IP组 播地址标识的组播业务， 该离开指示消息被转发到 BM-SC成员貪格功能。
步骤 403: —旦收到离开指示消息， BM-SC成员资格功能验证了该 IP组 播地址对应一个有效的 MBMS业务， 则发送一个含有 IP组播地址、 APN和 IMSI的 UE删除请求消息 UE Removal Request给产生离开指示的 GGSNL APN要与业务激活过程中提供的一致。 BM-SC成员资格功能也可能通过直接 给 GGSN1发送一个 UE删除请求消息， 触发 MBMS UE上下文去激活。
步驟 404: GGSN1一旦收到 UE删除请求消息或者 GGSN1 自己的原因， GGSN1给 SGSN发送一个含有 IP组播地址、 APN和 IMSI的 MBMS UE上下 文去激活请求消息 MBMS UE Context Deactivation Request。 IP组播地址、 APN 和 IMSI—起标识了一个需要被 SGSN删除的 MBMS UE上下文。其中， 本步 骤消息中的 APN为步骤 403收到的 APN。 SGSN给 GGSN1发送一个 MBMS UE上下文去激活响应消息 MBMS UE Context Deactivation Response , 回应其 收到了 MBMS UE上下文去激活请求。
步骤 405: SGSN—旦收到 MBMS UE上下文去激活请求消息，或者 SGSN 自己的原因， SGSN发送一个含有 TI 的去激活 MBMS 上下文请求消息 Deactivate MBMS Context Request给 UE， TI标识需要被 UE删除的 MBMS UE 上下文。
步骤 406: UE删除 MBMS UE上下文， 并且给 SGSN发送一个含有 TI 的去激活 MBMS上下文接受消息 Deactivate MBMS Context Response。
步骤 407: 如果 UE处于分组域移动性管理（PMM )连接状态， 并且已 与 RAN链接， SGSN发送一个 MBMS UE去链接请求 MBMS UE De-Linking Request给 RNC，该请求中含有 IP組播地址、 APN、 TMGI。 RAN删除 MBMS UE 上下文， 并且发送含有 TMGI 的 MBMS UE 去链接响应 MBMS UE De-Linking Response给 SGSN。
步骤 408: 如果当前为该 UE分配了专用的无线资源用于传输 MBMS数 据，则 RAN释放该无线资源； 如果当前分配了共享无线资源用于传输 MBMS 数据， 则 RAN可能决定将剩余的 UEs转移到专用资源当中去， 本步骤可选。
步骤 409: 如果收到了去激活 MBMS上下文接受消息或者 SGSN自己的 原因， SGSN发送一个含有 MBMS_NSAPI 的删除 MBMS 上下文请求消息 Delete MBMS Context Request给拥有 MBMS UE上下文的 GGSN2。 这里， 实 际提供所需 MBMS业务的 GGSN为 GGSN2, GGSN1和 GGSN2可以是同一 个 GGSN, 也可能不同于步骤 401中收到 IGMP离开请求的 GGSN1。
步骤 410: GGSN2删除 MBMS UE上下文， 给 BM-SC发送一个去激活 指示消息 Deactivation Indication确认成功去激活了 MBMS UE上下文。 BM-SC 收到去激活指示消息后， 删除 MBMS UE上下文， 并给 GGSN发送一个确认 消息 Deactivation Confirmatior 步骤 411 : 如果 GGSN2 中无用户接收该 MBMS组播业务， 且对应的 MBMS承载上下文的 "下行流节点列表" 为空， 则 GGSN2给 BM-SC代理和 传输功能发送一个 MBMS去注册请求消息 MBMS Deregistration Request, BM-SC 代理和传输功能反馈一个 MBMS 去注册响应消息 MBMS Deregistration Response, 并将自身 MBMS承载上下文中 GGSN2的标识从"下 行流节点列表"参数中删除。 本步骤可选。
步驟 412: GGSN2给 SGSN发送一个删除 MBMS上下文响应消息 Delete MBMS Context Response，确认去激活了 MBMS UE上下文。 SGSN删除 MBMS. UE上下文。
步骤 413:如果 SGSN中无用户接收该 MBMS组播业务，且对应的 MBMS 承载上下文的 "下行流节点列表" 为空， SGSN给 GGSN2发送一个 MBMS 去注册请求消息 Deregistration Request。 GGSN2反馈一个 MBMS去注册响应 消息 Deregistration Response, 并将自身 BMS承载上下文中该 SGSN的标识 从"下行流节点列表''参数中删除。
从上述步骤可以看出， MBMS业务去激活过程将 UE、 SGSN, GGSN中 的 MBMS UE上下文删除， MBMS业务去激活过程可以由 UE、SGSN、BM-SC、 GGSN触发。 UE触发的去激活过程开始于步骤 401; BM-SC触发的去激活过 程开始于步骤 403; GGSN触发的去激活过程开始于步骤 404; SGSN触发的 去激活过程开始于步骤 405和 409; MBMS UE De-linking在步骤 407执行。
GPRS去附着（Detach )或 SGSN路由区更新时，相应 UE在 UE、 SGSN, GGSN中的所有 MBMS UE上下文将被删除，也就是说， GPRS去附着流程或 SGSN路由区更新流程会引发 SGSN触发去激活流程， 具体的， SGSN从步骤 409开始执行去激活过程。这里， SGSN路由区更新仅指新 SGSN不支持 MBMS 业务时的 SGSN路由区更新情况。
由于每个 MBMS业务的 .MBMS UE上下文都会通过关联的 NSAPI与某 个 PDP上下文相关联， 因此，如果与某个 MBMS UE上下文相关联的 PDP上 下文被 UE、 SGSN或 GGSN去激活， 同样会引发 SGSN触发去激活流程， 具 体的， SGSN将从步骤 405和步驟 409开始执行 MBMS去激活过程。
现有规范中， 会出现因为 UE执行 GPRS去附着、 SGSN路由区更新或 UE删除了默认的 PDP上下文， 从而导致所有相应 MBMS UE上下文都需要 在网络侧、 终端侧进行去激活的过程。 由于用户可能申请数十个 MBMS承载 业务， 那么， 在发生所述需要执行去激活流程的情况时， 按照现有处理过程， 将重复执行数十次步骤 405~413才能完成对所有 MBMS业务对应的 MBMS UE上下文的删除工作。 显然， 整个处理流程冗余， 不仅降低了效率， 而且增 加了设备复杂性。 尤其在空中接口执行如此多重复信令， 明显降低了无线资 源利用率。 发明内容
有鉴于此， 本发明的主要目的在于提供一种实现多媒体组播广播业务去 激活的方法， 能通过简单流程一次完成对相关 MBMS UE上下文的删除， 不 仅降低了设备复杂度， 而且大大提高了无线接口的利用率。
为达到上述目的， 本发明的技术方案是这样实现的：
一种实现多媒体组播广播业务去激活的方法， 该方法包括：
收到携带有拆离指示的删除 MBMS UE上下文请求消息的 GGSN、： BM-SC 根据拆离指示确定需要删除相关 MBMS UE 上下文， 则各自删除相关的 MBMS UE上下文； 并且， 所述 GGSN向 SGSN返回响应消息， 收到响应消 息的 SGSN删除相关的 MBMS UE上下文。 其中， 所述响应消息中携带有拆 离指示。
该方法具体包括：
a. SGSN向 GGSN发送携带有拆离指示的删除 MBMS上下文请求， 收到 所述请求的 GGSN根据拆离指示确定需要删除相关 MBMS UE上下文， 则删 除自身相关的 MBMS UE上下文，并向 BM-SC发送携带有拆离指示的去激活 指示； b. BM-SC收到携带有拆离指示的去激活指示后， 根据拆离指示确定需要 删除相关 MBMS UE上下文， 则删除自身相关的 MBMS UE上下文， 并给 GGSN发送去激活确认消息；
c GGSN收到去激活确认后，向 SGSN返回删除 MBMS上下文响应， SGSN 收到后， 删除自身相关的 MBMS UE上下文。
上述方案中， SGSN向 GGSN发送删除 MBMS UE上下文的请求之前， 进一步包括： SGSN向 RAN发送携带有拆离指示的去链接请求， 收到去链接 请求的 RAN根据拆离指示确定需要删除相关 MBMS UE上下文，则删除自身 相关的 MBMS UE上下文，并向 SGSN返回去链接响应。其中， RAN向 SGSN 返回的去链接响应中携带有拆离指示。
上述方案中， SGSN向 RAN发送去链接请求之前， 进一步包括： SGSN 向所述 UE发送携带有拆离指示的去激活 MBMS上下文请求， 收到请求的所 述 UE根据拆离指示确定需要删除相关 MBMS UE上下文， 则删除自身相关 的 MBMS UE上下文， 并向 SGSN返回去激活 MBMS上下文响应。 其中， 所 述 UE向 SGSN返回的去激活 MBMS上下文响应中携带有拆离指示。
上述方案中， 所述 UE激活的对应不同 MBMS业务的所有 MBMS UE上 下文与同一个 PDP上下文关联， 则所述删除相关的 MBMS UE上下文为： 将 所述 UE的所有 MBMS UE上下文全部删除。
上述方案中， 所述 UE激活的对应不同 MBMS业务的 MBMS UE上下文 与不同的 PDP上下文关联， 则所述删除相关的 MBMS UE上下文为： 删除所 述 UE的所有与当前被去激活的 PDP上下文关联的 MBMS UE上下文。
上迷方案中， 所述拆离指示包括一个或一个以上要删除的 MBMS UE上 下文的标识， 则所述 BM-SC、 GGSN、 SGSN删除自身相关的 MBMS UE上 下文为： BM-SC、 GGSN、 SGSN删除自身中拆离指示指定的 MBMS UE上下 文。 其中， 收到拆离指示的所述 BM-SC、 GGSN, SGSN可以删除自身所有与 所述 UE相关的 MBMS UE上下文。 进一步的， 收到拆离指示的所述 RAN、 UE删除自身所有相关的 MBMS UE上下文。
所述拆离指示中携带有用于表示删除所有与指定 UE相关的 MBMS UE 上下文的标识； 则收到拆离指示的所述 BM-SC、 GGSN、 SGSN删除自身所有 与所述 UE相关的 MBMS UE上下文。 相应的， 该方法进一步包括： 收到拆 离指示的 RAN、 UE删除自身所有相关的 MBMS UE上下文。
该方法进一步包括： 所述 UE 自动删除本地保存的相关 MBMS UE上下 文； 或者， 所述 UE在收到来自 SGSN的去附着请求后， 删除本地保存的相关 MBMS UE上下文； 或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文 接受消息后， 删除本地保存的相关 MBMS UE上下文； 或者， 所述 UE在收 到来自 SGSN的去激活 PDP上下文请求后， 删除本地保存的相关 MBMS UE 上下文。
上述方案中， 所述 UE 自动删除本地保存的与当前被去激活的 PDP上下 文关联的 MBMS UE上下文； 或者， 所述 UE在收到来自 SGSN的去附着请 求后， 删除本地保存的与当前被去激活的 PDP上下文关联的 MBMS UE上下 文； 或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文接受消息后， 删 除本地保存的与当前被去激活的 PDP上下文关联的 MBMS UE上下文；或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文请求后， 删除本地保存的与 当前被去激活的 PDP上下文关联的 MBMS UE上下文。
上述方案中， 所述拆离指示为一个表示需要删除相关 MBMS UE上下文 的标识； 或为一个通过不同取值表示是否需要删除相关 MBMS UE上下文的 标识。
上述方案中， 所述 UE激活的对应不同 MBMS业务的 MBMS UE上下文 与不同的 PDP上下文关联， 所述拆离指示为一个或一个以上要删除的 MBMS UE上下文的标识。 其中， 所述 MBMS UE上下文的标识为： 所述 MBMS UE 上下文对应的 MBMS业务在激活过程中 ,保存于 RAN、 SGSN, GGSN、 BM-SC 中的 Linked NSAPI。 上述方案中， 所述删除 MBMS UE上下文请求消息在 GPRS去附着流程、 或新 SGSN不支持 MBMS业务的 SGSN路由区更新流程触发多媒体组播广播 业务去激活流程时， 由 SGSN发送给 GGSN。
上述方案中， 所述去链接请求在 GPRS去附着流程、 或新 SGSN不支持 MBMS业务的 SGSN路由区更新流程、或 PDP上下文去激活流程触发多媒体 组播广播业务去激活流程时， 由 SGSN发送给 RAN。
上述方案中，所述去激活 MBMS上下文请求在 PDP上下文去激活流程触 发多媒体组播广播业务去激活流程时， 由 SGSN发送给 UE。
本发明所提供的实现多媒体组播广播业务去激活的方法， 由于 SGSN选 择适当的时机触发去激活流程， 并通过携带拆离指示通知相关网络实体执行 删除全部相关 MBMS UE上下文的操作， 在相关步骤中， 仅仅通过一条消息 就可以将要删除的相关 MBMS UE上下文全部删除， 从而避免了当某个 UE 申请多个 MBMS承载业务时， 重复执行相同步骤而导致的流程冗余， 如此， 不仅降低了流程的复杂性， 提高了效率； 减少了核心网络设备的负荷， 提高 了无线资源的利用率。
另外， 本发明针对不同的情况提供多种实现方式， 不仅适用范围广， 而 且实现灵活、 方便、 筒单。 附图简要说明
图 1为组播业务的传输原理示意图；
图 2为支持广播 /组播业务的无线网络结构示意图；
图 3为 BM-SC功能实体的组成结构图；
图 4为现有技术中 MBMS业务去激活的处理流程图；
图 5为本发明一实施例的实现流程图；
图 6为本发明另一实施例的实现流程图；
图 7为本发明又一实施例的实现流程图。 实施本发明的方式
本发明的核心思想是： 在 GPRS去附着过程中或 PDP上下文去激活过程 中， SGSN要选择适当的时机， 触发去激活流程， 并通过携带拆离指示通知相 关网络实体执行删除相关 MBMS UE上下文的操作。
其中， 拆离指示可以仅仅是一个标识， 比如设置一个单独的比特， 该标 识有两种不同的使用方式： 一种是， 如果携带该指示， 表示需要删除相关的 MBMS UE上下文， 如果不携带， 表示不需要删除相关的 MBMS UE上下文； 另一种是， 拆离指示一直都携带于各网络实体的交互消息中， 通过取不同的 值来表示是否需要删除相关的 MBMS UE上下文， 比如： 取 0表示不需要删 除， 取 1表示需要删除； 或者， true表示需要删除， false表示不需要删除等。
拆离指示也可以是携带有一个或多个要删除的 MBMS UE上下文标识的 消息， 比如： 可以将去激活 MBMS UE上下文消息作为拆离指示。 拆离指示 还可以是携带一个指示删除所有与指定 UE相关的 MBMS UE上下文的标识 的消息。
当拆离指示为一个标识时， 下文均以第一种使用方式即是否携带拆离指 示表示是否需要删除 MBMS UE上下文为例。
这里， 所述适当时机可分为三种情况：
① 对于 GPRS去附着或新 SGSN不支持 MBMS业务的 SGSN路由区更 新的情况， 如果 UE、 SGSN或 GGSN触发了针对 UE的 GPRS去附着流程或 SGSN路由区更新流程， SGSN可以从图 4所示的步骤 407开始执行去激活流 程， 或是从步骤 409开始执行去激活流程， 删除某 UE在 UE、 SGSN, GGSN 中相关的 MBMS UE上下文。 这里， 如果拆离指示为携带 MBMS UE上下文 标识的消息， 则删除的相关 MBMS UE上下文是标识指定的一个、 或多个、 或全部。 当然， 如果删除某 UE所有相关的 MBMS UE上下文， 也可以采用 一个专门用于表示删除全部相关 MBMS UE上下文的标识， 将该标识携带于 拆离指示消息中。 ② 对于 RDP上下文去激活的情况， 如果通过关联 NSAPI与 MBMS UE 上下文相关联的 PDP上下文被 UE、 SGSN或 GGSN去激活， 则 SGSN也是 从图 4所示的步驟 407或步骤 409开始执行去激活流程，删除与被去激活 PDP 上下文相关联的相关 MBMS UE上下文。 这里， 如果拆离指示为携带 MBMS UE上下文标识的消息， 则删除的相关 MBMS UE上下文是标识指定的一个、 或多个、 或全部。 当然， 如果删除某 UE所有相关的 MBMS UE上下文， 也 可以采用一个专门用于表示删除全部相关 MBMS UE上下文的标识， 将该标 识携带于拆离指示消息中。
③ 当通过关联 NSAPI与 MBMS UE上下文相关联的 PDP上下文被 UE、 SGS 或 GGSN去激活时， 为了确保 UE侧删除相应的 MBMS UE上下文， SGSN也可以从图 4所示的步骤 405开始执行去激活流程， 删除与被去激活 PDP 上下文相关联的相关 MBMS UE 上下文。 这里， 如果拆离指示为携带 MBMS UE上下文标识的消息， 则删除的相关 MBMS UE上下文是标识指定 的一个、 或多个、 或全部。 当然， 如果删除某 UE所有相关的 MBMS UE上 下文， 也可以采用一个专门用于表示删除全部相关 MBMS UE上下文的标识， 将该标识携带于拆离指示消息中。
下文的描述均以各实体如 BM-SC、 GGSN> SGSN、 RAN、 UE删除自身 所有与指定 UE相关的 MBMS UE上下文为例， 所描述的所有流程及情况同 样适用于删除指定 MBMS UE上下文的情况。
对应上述 SGSN发起去激活的三种时机， 具体去激活处理流程也分为三 种：
a ) 当 SGSN从步骤 407开始执行去激活流程时， SGSN将拆离指示携带 于发送给 RAN的 MBMS UE去链接请求 MBMS UE De-Linking Request中， RAN将删除自身中相应 UE所有相关的 MBMS UE上下文； 相应的， 在后续 的步骤 409中， SGSN会向 GGSN发送携带拆离指示的删除 MBMS上下文请 求， GGSN删除自身中相应 UE所有相关的 MBMS UE上下文；在后续的步骤 410中， GGSN会向 BM-SC发送携带拆离指示的去激活指示， BM-SC删除自 身中相应 UE所有相关的 MBMS UE上下文；在后续的步驟 412中， GGSN会 向 SGSN返回携带拆离指示的删除 MBMS上下文响应， SGSN删除自身中相 应 UE所有相关的 MBMS UE上下文。
b ) 当 SGSN从步骤 409开始执行去激活流程时， SGSN将拆离指示携带 于发送给 GGSN的删除 MBMS上下文请求 Delete MBMS Context Request中， GGSN删除自身中相应 UE所有相关的 MBMS UE上下文；在后续的步骤 410 中， GGSN会向 BM-SC发送携带拆离指示的去激活指示， BM-SC删除自身 中相应 UE所有相关的 MBMS UE上下文；在后续的步骤 412中， GGSN会向 SGSN返回携带拆离指示的删除 MBMS上下文响应， SGSN删除自身中相应 UE所有相关的 MBMS UE上下文。
c ) 当 SGSN从步骤 405开始执行去激活流程时， SGSN将拆离指示携带 于发送给 UE的去激活 MBMS上下文请求 Deactivate MBMS Context Request 中， UE删除自身中相应 UE所有相关的 MBMS UE上下文；在后续的步骤中 , 与情况 a ) 中步據 407、 409^ 410、 412及其相应处理完全相同。
至于删除 UE上的 MBMS UE上下文， 有两种情况需要分别考虑： 第一种， 由于 GPRS去附着或 SGSN路由区更新， UE在 GPRS去附着过 程或 SGSN路由区更新中， 要在本地删除相关 MBMS UE上下文。 具体为： 如果是终端发起的 GPRS去附着过程或 SGSN路由区更新过程， 终端自动删 除本地保存的 MBMS UE上下文； 如果是网絡发起的 GPRS去附着过程或 SGSN路由区更新过程，终端在收到来自 SGSN的去附着请求消息后，删除本 地保存的 MBMS UE上下文。 具体 GPRS去附着流程或 SGSN路由区更新过 程为 3GPP规定的标准流程， 可参考 3GPP 23.060规范， 在此不再赘述。
第二种， 由于某 UE与 MBMS UE上下文关联的 PDP上下文被去激活， 该 UE要在本地删除对应的 MBMS UE上下文。 具体为： 如果是终端触发的 PDP上下文去激活过程， UE在收到 SGSN发给 UE的去激活 PDP上下文接受 消息之后， 删除本地保存的 MBMS UE上下文； 如果是 SGSN或者 GGSN触 发的 PDP上下文去激活过程， UE收到来自 SGSN的去激活 PDP上下文请求 消息后，删除本地保存的 MBMS UE上下文。具体 PDP上下文删除过程为 3GPP 规定的标准流程， 可参考 3GPP 23.060规范， 在此不再赘述。 联关系： 一种是， 该 UE激活的对应不同 MBMS业务的所有 MBMS UE上下 文与同一个 PDP上下文如默认的 PDP上下文关联； 另一种是， 该 UE激活的 对应不同 MBMS业务的所有 MBMS UE上下文与不同的 PDP上下文关联。 那么， 在 PDP 上下文去激活的情况下， 对于前一种情况， 删除所有相关的 MBMS UE上下文就是将该 UE的所有 MBMS UE上下文全部删除；而对于后 一种情况， 删除所有相关的 MBMS UE上下文是只删除该 UE的所有与当前 去激活 PDP上下文相关联的 MBMS UE上下文。
基于上述三种去激活流程发起时机及其相应处理， 以及 MBMS UE上下 文与 PDP上下文的两种关联关系， 下面结合附图和具体实施例详细说明本发 明中多媒体组播广播业务去激活方法的实现流程。 其中， 实施例一至实施例 四实现的前提是： 所有被 UE激活的 MBMS UE上下文都与一个默认的 PDP 上下文关联； 实施例五和实施例六实现的前提是： 被 UE激活的 MBMS UE 上下文与不同的 PDP上下文关联。 实施例一：
本实施例中 , 以 UE1为例， 所有被 UE1激活的 MBMS UE上下文都与一 个默认的 PDP上下文关联； UE、 SGSN或 GGSN触发了针对 UE1的 GPRS 去附着过程， 且此时保存于 SGSN中的 UE1的状态为 PMM连接， 即 UE1处 于 PMM连接状态， 并已与 RAN链接， 则 SGS 从图 4所示步骤 407开始执 行 MBMS业务去激活过程， 进行全部 MBMS UE上下文的删除操作。 如图 5 所示， 具体包括以下步骤：
步驟 507: SGSN发送一个 MBMS UE去链接请求给 RAN中的 RNC， 该 请求中携带有 IP组播地址、 APN、 TMGI; 并且， 由于触发了 GPRS去附着 过程， RAN中对应 UE1的所有 MBMS UE上下文应该被删除，因此，该 MBMS UE去链接请求中还携带有拆离指示， 表示要删除所有与 UE1相关的 MBMS UE上下文。
RA 收到带有拆离指示的 MBMS UE去链接请求后， 删除自身所有与 UE1相关的 MBMS UE上下文，并且发送一个 MBMS UE去链接响应给 SGSN, 该响应中至少携带有 TMGI, 该响应中可以携带拆离指示， 也可以不携带。
步骤 508: 与现有去激活流程中步驟 408的处理完全相同。
步骤 509: SGS 发送一个含有 MBMS一 NSAPI的删除 MBMS上下文请 求消息给拥有 MBMS UE上下文的 GGSN, 该 GGSN可能不同于收到 IGMP 离开请求的 GGSN。 由于触发了 GPRS去附着过程， GPRS去附着过程将 UE1 的 PDP上下文去激活，所以需要将与去激活的 PDP上下文关联的所有 MBMS UE上下文删除， 因此， 所述删除 MBMS上下文请求中还携带有拆离指示。
步骤 510: GGSN收到带有拆离指示的删除 MBMS上下文请求后， 删除 自身所有与 UE1相关的 MBMS UE上下文， 并给 BM-SC发送一个去激活指 示消息确认成功去激活了 MBMS UE上下文， 该去激活指示中携带有拆离指 示。 BM-SC收到带有拆离指示的去激活指示消息后， 删除自身所有与 UE1相 关的 MBMS UE上下文， 并给 GGSN发送一个去激活确认消息， BM-SC回复 的去激活确认消息中可以携带拆离指示， 也可以不携带。
步骤 511: 与现有去激活流程中步骤 411的处理完全相同。
步骤 512: GGSN给 SGSN发送一个删除 MBMS上下文响应消息， 确认 删除了 UE1的所有 MBMS UE上下文， 该响应消息中可以携带拆离指示， 也 可以不携带。
SGSN 收到删除 MBMS 上下文响应后， 删除自身所有与 UE1 相关的 MBMS UE上下文。
步骤 513: 与现有去激活流程中步骤 413的处理完全相同。 本实施例中， 如果是终端发起的 GPRS去附着过程， 终端自动删除本地 保存的 MBMS UE上下文； 如果是网络发起的 GPRS去附着过程， 终端在收 到来自 SGSN的去附着请求消息后， 删除本地保存的 MBMS UE上下文。
本实施例与现有技术相比， 相当于从原步裸 407开始执行去激活流程， 省略了步驟 405和 406, 并且， 相关的每个步骤通过一条消息就将与 UE1相 关的所有 MBMS UE上下文全部删除了， 大大降低了处理的复杂度， 提高了 处理效率。 实施例二：
本实施例中， 仍以 UE1为例， 所有被 UE1激活的 MBMS UE上下文都与 一个默认的 PDP上下文关联； UE、 SGSN或 GGSN触发了针对 UE1的 GPRS 去附着过程， UE1处于 PMM连接状态， 并已与 RAN链接， 且 RAN在执行 GPRS去附着的过程中，删除了 UE1所有的无线接入承载（RAB )，因此， RAN 已自动将自身与 UE1相关的所有 MBMS UE上下文全部删除， 则 SGSN从图 4所示步骤 409开始执行 MBMS业务去激活过程， 进行全部 MBMS UE上下 文的删除操作。 如图 6所示， 具体包括以下步驟：
步骤 609〜613： 与实施例一中步骤 509~513的处理和描述完全相同。
同样， 本实施例中， 如果是终端发起的 GPRS去附着过程， 终端自动删 除本地保存的 MBMS UE上下文； 如果是网络发起的 GPRS去附着过程， 终 端在收到来自 SGSN的去附着请求消息后， 删除本地保存的 MBMS UE上下 文。
本实施例与现有技术相比， 相当于从原步骤 409开始执行去激活流程， 也省略了步骤 405〜408, 且相关的每个步骤通过一条消息就将与 UE1相关的 所有 MBMS UE上下文全部删除了， 大大降低了处理的复杂度， 提高了处理 效率。
如果 UE1处于 PMM空闲状态，由于不需要去链接，所以， UE1处于 PMM 空闲状态时， SGSN也从图 4所示步骤 409开始执行 MBMS业务去激活过程， 即： 按本实施例的处理流程进行。
在实际应用中， 当 UE发起 SGSN路由区更新流程时， 如果新 SGSN不 支持 MBMS业务， 则旧 SGSN也要触发 MBMS业务去激活过程， 删除相应 UE所有相关的 MBMS UE上下文， 这种情况下， SGSN发起的 MBMS业务 去激活流程与 GPRS去附着触发的 MBMS业务去激活过程相同。 也就是说， 实施例一和实施例二所描述的去激活处理流程， 也同样适用于 SGSN路由区 更新时新 SGSN不支持 MBMS业务所触发的 MBMS业务去激活的情况。 实施例三：
本实施例中， 仍以 UE1为例， 所有被 UE1激活的 MBMS UE上下文都与 一个默认的 PDP上下文关联， 该默认的 PDP上下文被 UE、 SGSN或 GGSN 去激活； 此时 UE1处于 PMM连接状态， 并已与 RAN链接， 由于对于 PDP 上下文去激活过程而言， RAN不知道该被去激活的 PDP上下文与 MBMS UE 上下文之间的关系， 因此， SGSN必须从图 4所示步驟 407开始执行 MBMS 业务去激活过程， 进行全部 MBMS UE上下文的删除操作。 参照图 5所示， 具体包括以下步骤：
步骤 11: SGSN发送一个 MBMS UE去链接请求给 R C, 该请求中携带 有 IP组播地址、 APN、 TMGI; 并且， 由于触发了与 MBMS UE上下文相关 联的 PDP上下文的去激活， RAN中对应 UE1的所有 MBMS UE上下文应该 被删除， 因此， 该 MBMS UE去链接请求中还携带有拆离指示， 表示要删除 所有与 UE1相关的 MBMS UE上下文。
RAN收到带有拆离指示的 MBMS UE去链接请求后， 删除自身所有与 UE1相关的 MBMS UE上下文，并给 SGSN返回 MBMS UE去链接响应消息， 该响应消息中可以携带拆离指示， 也可以不携带。
步骤 12〜： 17: 与实施例一中步骤 508〜513的处理和描述完全相同。
实施例四：
本实施例中， 仍以 UE1为例， 所有被 UE1激活的 MBMS UE上下文都与 一个默认的 PDP上下文关联， 该默认的 PDP上下文被 UE、 SGSN或 GGSN 去激活， SGSN从图 4所示步骤 405开始执行 MBMS去激活过程。 如图 7所 示， 具体包括以下步骤：
步骤 705: SGSN发送一个含有 TI的去激活 MBMS上下文请求消息给 UE, 其中， TI标识需要被 UE删除的 MBMS UE上下文。 由于与 MBMS UE 上下文关联的 PDP上下文被去激活， 因此，该去激活 MBMS上下文请求中还 携带有拆离指示， 表示要删除所有与被去激活 PDP上下文关联的 MBMS UE 上下文。
步骤 706: UE收到携带拆离指示的去激活 MBMS上下文请求后，删除自 身所有 MBMS UE上下文， 并给 SGSN发送一个含有 TI和拆离指示的去激活 MBMS上下文响应消息。 该响应消息中可以携带拆离指示， 也可以不携带。
步驟 707〜713： 与实施例一中步骤 507~513的处理和描述完全相同。
实施例五：
本实施例中， 以 UE1为例， 被 UE1激活的 MBMS UE上下文与不同的 PDP上下文关联， 某个 PDP上下文被 UE、 SGSN或 GGSN去激活后， 需要 执行的是删除与该被去激活 PDP上下文关联的 MBMS UE上下文， 不与该被 去激活 PDP上下文关联的 MBMS UE上下文不必删除。 此时 UE1处于 PMM 连接状态， 并已与 RAN链接， SGSN从图 4所示步骤 407开始执行 MBMS 业务去激活过程， 进行相关 MBMS UE上下文的删除操作。
本实施例中，由于某个与 MBMS UE上下文关联的 PDP上下文被去激活， 该 UE要在本地删除对应的 MBMS UE上下文。 具体为： 如果是终端触发的 PDP上下文去激活过程， UE在收到 SGSN发给 UE的去激活 PDP上下文接受 消息之后， 删除本地保存的、 与被去激活 PDP上下文以 Linked_NSAPI进行 关联的 MBMS UE上下文；如果是 SGSN或者 GGSN触发的 PDP上下文去激 活过程， UE收到去激活 PDP上下文请求消息后， 删除本地保存的、 与被去 激活 PDP上下文以 Linked—NSAM进行关联的 MBMS UE上下文。 具体 PDP 上下文删除过程为 3GPP规定的标准流程， 可参考 3GPP 23.060规范， 在此不 再赘述。
本实施例的处理步骤与实施例一类似， 具体包括以下步骤：
步骤 21: SGSN发送一个 MBMS UE去链接请求给 RNC, 该请求中携带 有 IP组播地址、 APN、 TMGL 由于与 MBMS UE上下文关联的 PDP上下文 被去激活， 这时， SGSN 可以将多个 MBMS UE 上下文的标识包括在一个 MBMS UE去链接请求中。 这样， RAN将按照 MBMS UE上下文的标识， 删' 除与 UE1对应的、 与去激活 PDP上下文关联的 MBMS UE上下文， 并且发送 一个 MBMS UE去链接响应给 SGSN, 该响应消息中携带有 TMGI。
这里 ,标识多个 MBMS UE上下文的方法可以是多个 IP组播地址、 APN、 TMGI的组合； 也可以是一个 Linked NSAPI, 即 SGSN中记录的、 与所有这 些 MBMS UE上下文绑定的 PDP上下文的 NSAPI, 如果是这种方法， SGSN 在执行 MBMS UE链接机制时 , 需要将与这些 MBMS UE上下文绑定的 PDP 上下文的 NSAPI发送给 RAN, RAN把该 NSAPI作为 Linked NSAPI保存到 RAN中的 MBMS UE上下文中， 具体链接机制可参考 3GPP 23.246规范， 在 此不再赘述。
步骤 22: 与现有去激活流程中步骤 408的处理完全相同。
步骤 23: SGSN发送一个含有 MBMS一 NSAPI的删除 MBMS上下文请求 消息给拥有 MBMS UE上下文的 GGSN, 该 GGSN可能不同于收到 IGMP离
PDP上下文删除， 这时可以将与该 PDP上下文关联的多个 MBMS UE上下文 删除， 因此， SGSN发送给 GGSN的删除 MBMS上下文请求中将与该 PDP 上下文关联的多个 MBMS UE上下文的标识包括在一条消息中。
这里， 标识多个 MBMS UE上下文的方法可以是多个 MBMS NSAPI; 也 可以是一个 Linked NSAPI, 即 SGSN中记录的、 与所有这些 MBMS UE上下 文绑定的 PDP上下文的 NSAPI, 如果是这种方法， SGSN在 MBMS组播业务 激活过程时， 需要将与这些 MBMS UE上下文绑定的 PDP上下文的 NSAPI 作为 Linked NSAPI发送给 GGSN, GGSN将该 NSAPI保存在自身相关的 MBMS UE上下文中， 具体业务激活流程可参考 3GPP 23.246规范， 在此不再 赘述。
步骤 24: GGSN收到含有与去激活 PDP上下文关联的 MBMS UE上下文 标识的删除 MBMS 上下文请求后， 根据删除 MBMS 上下文请求中携带的 MBMS UE上下文标识信息， 删除自身 UE1的与该去激活 PDP上下文关联的 MBMS UE上下文； 并给 BM-SC发送一个去激活指示消息确认成功去激活了 MBMS UE上下文， 该去激活指示中携带有与去激活 PDP上下 关联的所有 MBMS UE上下文的标识。
BM-SC收到含有与去激活 PDP上下文关联的 MBMS UE上下文标识的去 激活指示消息后， 根据去激活指示中携带的 MBMS UE上下文标识信息， 删 除自身 UE1的与该去激活 PDP上下文关联的 MBMS UE上下文，并给 GGSN 发送一个去激活确认消息。
这里，标识多个 MBMS UE上下文的方法可以是多个 TMGI;也可以是一 个 Linked NSAPI, 即 SGSN中记录的、 与所有这些 MBMS UE上下文绑定的 PDP上下文的 NSAPI， 如果是这种方法， GGSN在 MBMS组播业务激活过程 时， 需要将这些 MBMS UE上下文绑定的 PDP上下文的 NSAPI作为 Linked NSAPI保存到 BM-SC的 MBMS UE上下文中，具体业务激活流程可参考 3GPP 23.246规范， 在此不再赘述。
步骤 25: 与现有去激活流程中步骤 411的处理完全相同。
步驟 26: GGSN给 SGSN发送一个删除 MBMS上下文响应消息，确认删 除了相关的 MBMS UE上下文， SGSN收到后， 删除自身 UE1的与该去激活 PDP上下文关联的 MBMS UE上下文。 .
步驟 27: 与现有去激活流程中步骤 413的处理完全相同。
本实施例中， 多个要删除 MBMS UE上下文的标识就作为拆离指示。 实施例六：
本实施例中， 以 UE1为例， 被 UE1激活的 MBMS UE上下文与不同的 PDP上下文关联， 某个 PDP上下文被 UE、 SGSN或 GGSN去激活后， 需要 执行的是删除与该被去激活 PDP上下文关联的 MBMS UE上下文， 不与该被 去激活 PDP上下文关联的 MBMS UE上下文不必删除。 与实施例四类似， SGSN从图 7所示步骤 705开始执行 MBMS业务去激活过程，进行相关 MBMS UE上下文的删除操作。
本实施例中， UE1不在本地删除 MBMS UE上下文， SGSN在图 7所示 的步骤 705的去激活 MBMS上下文请求消息中， 携带 TI和拆离指示。
UE1收到携带拆离指示的去激活 MBMS上下文请求消息后， 根据 TI找 到对应的一个 MBMS UE上下文， 然后找到该 MBMS上下文保存的 Linked NSAPI,然后，删除 UE1中所有保存了该 Linked NSAPI的 MBMS UE上下文。
同样，在 UE1返回去激活 MBMS上下文响应的步骤中，可以携带拆离指 示， 或不携带。
其它处理流程与实施例四的描述完全相同。
本实施例中， 步驟 705和步驟 706中所携带的拆离指示为一个指示标识， 步骤 707 以及步骤 707 以后的步驟中所携带的拆离指示就为多个要删除 MBMS UE上下文的标识。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保护 范围。

Claims

权利要求书
1、 一种实现多媒体组播广播业务去激活的方法， 其特征在于， 该方法包 括：
收到携带有拆离指示的删除 MBMS UE上下文请求消息的 GGSN、BM-SC 根据拆离指示确定需要删除相关 MBMS UE 上下文， 则各自删除相关的 MBMS UE上下文； 并且， 所述 GGSN向 SGSN返回响应消息， 收到响应消 息的 SGSN删除相关的 MBMS UE上下文。
2、 根据权利要求 1所述的方法， 其特征在于， 所述响应消息中携带有拆 离指示。
3、 根据权利要求 1所述的方法， 其特征在于， 该方法具体包括： a. SGSN向 GGSN发送携带有拆离指示的删除 MBMS上下文请求， 收到 所述请求的 GGSN根据拆离指示确定需要删除相关 MBMS UE上下文， 则删 除自身相关的 MBMS UE上下文，并向 BM-SC发送携带有拆离指示的去激活 指示； '
b. BM-SC收到携带有拆离指示的去激活指示后， 根据拆离指示确定需要 删除相关 MBMS UE上下文， 则删除自身相关的 MBMS UE上下文， 并给 GGSN发送去激活确认消息；
c GGS 收到去激活确认后，向 SGSN返回删除 MBMS上下文响应 , SGSN 收到后， 删除自身相关的 MBMS UE上下文。
4、 根据权利要求 3所述的方法， 其特征在于， SGSN向 GGSN发送删除 MBMS UE上下文的请求之前， 进一步包括： SGSN向 RAN发送携带有拆离 指示的去链接请求， 收到去链接请求的 RAN根据拆离指示确定需要删除相关 MBMS UE上下文， 则删除自身相关的 MBMS UE上下文， 并向 SGSN返回 去链接响应。
5、 根据权利要求 4所述的方法， 其特征在于， RAN向 SGSN返回的去 链接响应中携带有拆离指示。
6、 根据权利要求 4所述的方法， 其特征在于， SGSN向 RAN发送去链 接请求之前， 进一步包括： SGSN向所述 UE发送携带有拆离指示的去激活 MBMS 上下文请求， 收到请求的所述 UE根据拆离指示确定需要删除相关 MBMS UE上下文， 则删除自身相关的 MBMS UE上下文， 并向 SGSN返回 去激活 MBMS上下文响应。
7、 根据权利要求 6所述的方法， 其特征在于， 所述 UE向 SGSN返回的 去激活 MBMS上下文响应中携带有拆离指示。
8、 根据权利要求 1至 7任一项所述的方法， 其特征在于， 所述 UE激活 的对应不同 MBMS业务的所有 MBMS UE上下文与同一个 PDP上下文关联， 则所述删除相关的 MBMS UE上下文为： 将所述 UE的所有 MBMS UE上下 文全部删除。
9、 根据权利要求 1至 7任一项所迷的方法， 其特征在于， 所述 UE激活 的对应不同 MBMS业务的 MBMS UE上下文与不同的 PDP上下文关联， 则 所述删除相关的 MBMS UE上下文为： 删除所述 UE的所有与当前被去激活 的 PDP上下文关联的 MBMS HE上下文。
10、 根据权利要求 2至 7任一项所述的方法， 其特征在于， 所述拆离指 示包括一个或一个以上要删除的 MBMS UE上下文的标识， 则所述 BM-SC、 GGSN、 SGSN删除自身相关的 MBMS UE上下文为： BM-SC、 GGSN、 SGSN 删除自身中拆离指示指定的 MBMS UE上下文。
11、 根据权利要求 10 所述的方法， 其特征在于， 收到拆离指示的所述 BM-SC、 GGSN、 SGSN删除自身所有与所述 UE相关的 MBMS UE上下文。
12、 根据权利要求 11所述的方法， 其特征在于， 该方法进一步包括： 收 到拆离指示的 AN、 UE删除自身所有相关的 MBMS UE上下文。
13、 根据权利要求 2至 7任一项所述的方法， 其特征在于， 所述拆离指 示中携带有用于表示删除所有与指定 UE相关的 MBMS UE上下文的标识； 则收到拆离指示的所述 BM-SC、 GGSN、 SGSN删除自身所有与所述 UE相关 的 MBMS UE上下文。
14、 根据权利要求 13所述的方法， 其特征在于， 该方法进一步包括： 收 到拆离指示的 RAN、 UE删除自身所有相关的 MBMS UE上下文。
15、 根据权利要求 1、 3、 4或 6所述的方法， 其特征在于， 该方法进一 步包括： 所述 UE自动删除本地保存的相关 MBMS UE上下文；
或者，所述 UE在收到来自 SGSN的去附着请求后，删除本地保存的相关 MBMS UE上下文；
或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文接受消息后， 删 除本地保存的相关 MBMS UE上下文；
或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文请求后， 删除本 地保存的相关 MBMS UE上下文。
16、根据权利要求 9所述的方法， 其特征在于， 所述 UE自动删除本地保 存的与当前被去激活的 PDP上下文关联的 MBMS UE上下文；
或者，所述 UE在收到来自 SGSN的去附着请求后，删除本地保存的与当 前被去激活的 PDP上下文关联的 MBMS UE上下文；
或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文接受消息后， 删 除本地保存的与当前被去激活的 PDP上下文关联的 MBMS UE上下文；
或者， 所述 UE在收到来自 SGSN的去激活 PDP上下文请求后， 删除本 地保存的与当前被去激活的 PDP上下文关联的 MBMS UE上下文。
17、 根据权利要求 1至 7任一项所述的方法， 其特征在于， 所述拆离指 示为一个表示需要删除相关 MBMS UE上下文的标识； 或为一个通过不同取 值表示是否需要删除相关 MBMS UE上下文的标识。
18、根据权利要求 1至 7任一项所述的方法， 其特征在于， 所述 UE激活 的对应不同 MBMS业务的 MBMS UE上下文与不同的 PDP上下文关联， 所 述拆离指示为一个或一个以上要删除的 MBMS UE上下文的标识。
19、 根据权利要求 18所述的方法， 其特征在于， 所述 MBMS UE上下文 的标识为： 所述] ffiMS UE上下文对应的 MBMS业务在激活过程中， 保存于 RAN, SGSN、 GGSN、 BM-SC中的 Linked NS API。
20、根据权利要求 1或 3所述的方法， 其特征在于， 所述删除 MBMS ΌΈ 上下文请求消息在 GPRS去附着流程、或新 SGSN不支持 MBMS业务的 SGSN 路由区更新流程触发多媒体组播广播业务去激活流程时， 由 SGSN发送给 GGSN。
21、 根据权利要求 4所述的方法， 其特征在于， 所述去链接请求在 GPRS 去附着流程、 或新 SGSN不支持 MBMS业务的 SGSN路由区更新流程、 或 PDP上下文去激活流程触发多媒体组播广播业务去激活流程时， 由 SGSN发 送给 RANo
22、 根据权利要求 6所述的方法， 其特征在于， 所述去激活 MBMS上下 文请求在 PDP上下文去激活流程触发多媒体组播广播业务去激活流程时， 由 SGSN发送给 UE。
PCT/CN2006/000099 2005-01-20 2006-01-20 Procede de desactivation du service de diffusion multidiffusion multimedias WO2006076865A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
DE602006006966T DE602006006966D1 (de) 2005-01-20 2006-01-20 Verfahren zur deaktivierung eines multimedia-broadcast-multicast-dienstes
AT06705520T ATE432598T1 (de) 2005-01-20 2006-01-20 Verfahren zur deaktivierung eines multimedia- broadcast-multicast-dienstes
EP06705520A EP1821465B1 (en) 2005-01-20 2006-01-20 A method for implementing the deactivation of the multimedia broadcast multicast service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2005100025279A CN1327742C (zh) 2005-01-20 2005-01-20 一种实现多媒体组播广播业务去激活的方法
CN200510002527.9 2005-01-20

Publications (1)

Publication Number Publication Date
WO2006076865A1 true WO2006076865A1 (fr) 2006-07-27

Family

ID=36691987

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/000099 WO2006076865A1 (fr) 2005-01-20 2006-01-20 Procede de desactivation du service de diffusion multidiffusion multimedias

Country Status (5)

Country Link
EP (1) EP1821465B1 (zh)
CN (1) CN1327742C (zh)
AT (1) ATE432598T1 (zh)
DE (1) DE602006006966D1 (zh)
WO (1) WO2006076865A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580346A (zh) * 2011-03-17 2018-01-12 高通股份有限公司 针对多媒体广播多播服务连续性的目标小区选择

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1997008B (zh) * 2006-12-30 2011-01-19 华为技术有限公司 一种解除激活pdp上下文的方法及其装置
CN101232701B (zh) * 2007-01-26 2010-10-27 华为技术有限公司 广播组播业务去激活的方法及设备
CN102695293B (zh) * 2007-06-05 2015-12-02 华为技术有限公司 一种承载删除的方法及系统、服务网关实体
CN101500340B (zh) * 2008-01-28 2012-09-05 华为技术有限公司 一种删除承载的方法、系统及设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1499761A (zh) * 2002-11-05 2004-05-26 北京三星通信技术研究有限公司 核心网和用户设备识别用户设备状态的方法
CN1499765A (zh) * 2002-11-11 2004-05-26 北京三星通信技术研究有限公司 控制无线单元控制器中多媒体广播组播业务上下文的更新方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1489314A (zh) * 2002-10-11 2004-04-14 北京三星通信技术研究有限公司 在sgsn和ggsn中建立和清除mbms业务的方法
CN1549611A (zh) * 2003-05-11 2004-11-24 北京三星通信技术研究有限公司 Mbms业务上下文更新的方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1499761A (zh) * 2002-11-05 2004-05-26 北京三星通信技术研究有限公司 核心网和用户设备识别用户设备状态的方法
CN1499765A (zh) * 2002-11-11 2004-05-26 北京三星通信技术研究有限公司 控制无线单元控制器中多媒体广播组播业务上下文的更新方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580346A (zh) * 2011-03-17 2018-01-12 高通股份有限公司 针对多媒体广播多播服务连续性的目标小区选择
CN107580346B (zh) * 2011-03-17 2021-02-02 高通股份有限公司 针对多媒体广播多播服务连续性的目标小区选择

Also Published As

Publication number Publication date
ATE432598T1 (de) 2009-06-15
EP1821465B1 (en) 2009-05-27
EP1821465A1 (en) 2007-08-22
CN1327742C (zh) 2007-07-18
CN1794859A (zh) 2006-06-28
DE602006006966D1 (de) 2009-07-09
EP1821465A4 (en) 2008-09-10

Similar Documents

Publication Publication Date Title
JP4425307B2 (ja) マルチメディアブロードキャスト／マルチキャストサービスの起動方法
US7400593B2 (en) Method for distinguishing MBMS service request from other service requests
US8325641B2 (en) Method and apparatus for service identifying and routing in multimedia broadcast/multicast service system
EP1802049B1 (en) A method and system for controlling multimedia broadcast/multicast service session
JP4422763B2 (ja) マルチメディアブロードキャスト・マルチキャストサービスの起動方法
WO2005101737A1 (fr) Procede de demarrage de session d'un service de multiplexage de programmes de diffusion multimedia
WO2005069646A1 (fr) Procede d'enregistrement pour service multidestination a diffusion multimedia
WO2008113263A1 (en) Method for supporting multimedia broadcast/multicast service in evolvement of system architecture
WO2008098497A1 (fr) Système de service de diffusion multimedia et procédé de début de session, procédé de fin de session
EP2557819A2 (en) Method for supporting backward compatibility of MBMS
WO2018006279A1 (zh) 业务处理的方法、设备和系统
JP2006081173A (ja) マルチメディアブロードキャストマルチキャストサービスおよび関連デバイスの非アクティブ化方法
WO2005107155A1 (fr) Procede de determination du nombre total d'utilisateur dans un systeme de service de diffusion/multidiffusion (mbms)
WO2006015544A1 (fr) Procede d'etablissement d'une prise en charge dans un service de diffusion/multi-diffusion multimedia
CN102057699A (zh) Mbms的sae应用
WO2005109915A1 (fr) Procede de mise a jour de zone d'acheminement dans mbms
WO2009067866A1 (fr) Procédé et système de réseau pour établir des sessions dans un service de diffusion/multidiffusion multimédia
WO2006076865A1 (fr) Procede de desactivation du service de diffusion multidiffusion multimedias
CN100502570C (zh) 移动通信系统中终端加入组播业务组时获取apn的方法
WO2008025206A1 (fr) Procédé et réseau pour créer le tunnel de plan de contrôle dans le service de multidiffusion du système de communication mobile
JP2007251944A (ja) ポイント・ツー・マルチポイントｍｂｍｓを停止させる方法及び装置
US20100142430A1 (en) Multimedia data service apparatus of mobile communication system supporting multicast and multicast service activation and deactivation methods for multimedia data service
WO2004034655A1 (en) A method of establishing and deleting mbms service in sgsn and ggsn
CN101232701B (zh) 广播组播业务去激活的方法及设备
CN100486353C (zh) 开展组播/广播业务的实现方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2006705520

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2006705520

Country of ref document: EP