CN101227307A - Equipment, system and method for processing multimedia broadcast multicast business - Google Patents
Equipment, system and method for processing multimedia broadcast multicast business Download PDFInfo
- Publication number
- CN101227307A CN101227307A CNA2007100010234A CN200710001023A CN101227307A CN 101227307 A CN101227307 A CN 101227307A CN A2007100010234 A CNA2007100010234 A CN A2007100010234A CN 200710001023 A CN200710001023 A CN 200710001023A CN 101227307 A CN101227307 A CN 101227307A
- Authority
- CN
- China
- Prior art keywords
- mbms
- user terminal
- node
- network side
- request
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000012545 processing Methods 0.000 title claims abstract description 41
- 230000008569 process Effects 0.000 claims abstract description 18
- 230000003213 activating effect Effects 0.000 claims description 6
- 238000003672 processing method Methods 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 230000011664 signaling Effects 0.000 abstract description 4
- RASFMBBIZLUCME-UHFFFAOYSA-N methyl 2-amino-3-[(2-amino-3-methoxycarbonylphenyl)methyl]benzoate Chemical compound COC(=O)C1=CC=CC(CC=2C(=C(C(=O)OC)C=CC=2)N)=C1N RASFMBBIZLUCME-UHFFFAOYSA-N 0.000 abstract 2
- 238000001994 activation Methods 0.000 description 29
- 238000013475 authorization Methods 0.000 description 29
- 230000004913 activation Effects 0.000 description 28
- 230000004044 response Effects 0.000 description 28
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for processing multi-medium broadcast multicast services, which comprises following steps: receiving an MBMA service request which is sent by a user terminal by a network side and processing the MBMS service request of the user terminal according to MBMS carrying capacity parameters of the user terminal, which are pre-obtained by the network side. The invention also provides a system and equipment for processing the multi-medium broadcast multicast services. When the network side equipment receives the MBMA service request which is sent by the user terminal, the invention directly calls the MBMS carrying capacity parameters of the user terminal, which are stored before and process according to the request of the parameters to the user terminal, the transmission of the MBMS carrying capacity parameters of the user terminal does not need in every service, and thereby signaling load can be effectively reduced and network resources can be saved.
Description
Technical Field
The present invention relates to the field of network technologies, and in particular, to a method, a system, and a device for processing a multimedia broadcast multicast service.
Background
UMTS (Universal Mobile telecommunications System) is a third Generation wireless communication network technology standard defined by the 3GPP (3rd Generation Partnership Project) organization. The UMTS network consists of a core network and an access network, the core network includes a circuit domain and a packet domain, and the circuit domain provides services based on circuit switching, such as voice services; while the packet domain provides packet-switched based services, such as Internet access. A terminal used by a mobile User is a UE (User Equipment). In a UMTS network, MBMS (Multimedia Broadcast/Multicast Service) is provided, and its bearer Service architecture is shown in fig. 1.
In the MBMS bearer Service architecture, a Content Provider (CP) provides Multicast Service data to a Broadcast-Multicast Service center (BM-SC); the broadcast multicast service center has functions of service announcement, member management, session transmission, proxy transmission, security, and the like, and is an IP (Internet Protocol) multicast service source of the UE. GGSN (gateway GPRS Support Node ) is the entry point of IP multicast service, GGSN and BM-SC are connected through Gmb and Gi interface, wherein Gmb interface completes the signaling interaction between GGSN and BM-SC, and is the boundary of network side of MBMS bearer service; the Gi interface transmits IP multicast service data and the like. The SGSN (serving GSN, serving GPRS support node) performs MBMS bearer service control functions for each individual UE and provides MBMS transmissions to the radio access network. The Radio Access Network includes a UTRAN (UMTS Terrestrial Radio Access Network)/GERAN (GSM EDGE Radio Access Network), and is responsible for transmitting MBMS data to a designated MBMS service domain. And the UE is responsible for activating/deactivating the MBMS bearer service to receive the multicast service, etc.
The MBMS is divided into a broadcast service and a multicast service, and the present invention is mainly directed to the multicast service, but can also be applied to the broadcast service. The multicast service includes several procedures such as Subscription (Subscription), service announcement (service notification), service activation (Joining)/exit (Leaving), Session start/stop (Session stop), MBMS notification (MBMS notification), data transmission (Datatransfer), and so on.
In the current 3G network system, the MBMS service processing procedure is shown in fig. 2, and includes the following steps:
and step s101, establishing a general PDP (Packet data protocol) context among the UE, the SGSN and the GGSN.
Step s102, the UE sends an IGMP (Internet Group management Protocol) or MLD (Multicast Listener Discovery) join message in the PDP context, indicating that the UE requests to receive a specific Multicast MBMS bearer service indicated by an IP Multicast address, where the IGMP join message is used in IPv4(Internet Protocol version 4, version 4 Internet Protocol), and the MLD join message is used in IPv6(IP version 6, version 6 IP).
Step s103 a-step s103b, the GGSN sends an MBMS authorization Request (MBMS authorization Request) to the BM-SC seeking authorization information including path information, i.e. additional MBMS path information, for activating the UE to receive data. The authorization decision providing the membership function in the MBMS authorization Response (MBMS authorization Response) is used together with an APN (Access point network) to generate an MBMS UE context based on the intra-BM-SC subscription data. If the MBMS grant response indicates that the UE does not have permission to receive MBMS data, the procedure is terminated and no further messages are exchanged.
Step s104 a-step s104b, the GGSN sends an MBMS notification request to the SGSN, where the request includes an IP multicast address, an APN, and an NSAPI (Network Service Access point identifier) for connection. The connected NSAPI is set to the NSAPI of the PDP context that is used to receive the join request. The IP multicast address is the request content of the UE at the time of the join request, and the APN may be different from the APN in the default activated PDP context. In any case, the APN can be decomposed into one GGSN, which is different from the GGSN that receives the IGMP/MLD join request. The MBMS activation timer is started when the GGSN does not receive the feedback. SGSN sends MBMS inform response message to GGSN, and feeds back the reason whether MBMS context is activated. If the unsuccessful operation message is fed back, the GGSN should not send the MBMS notification request message any more, and terminates the procedure.
Step s105, the SGSN sends a Request MBMS context Activation (Request MBMS context Activation) message to the UE, where the message includes an IP multicast address, an APN, an NSAPI and a TI (Terminal Interface) for connection, and requests the UE to activate an MBMS UE context. The connected NSAPI allows the UE to associate the MBMS UE context with the PDP context that sent the IGMP/MLD join message. TI is selected by the SGSN and contains a value that is not used by any other active PDP context and the MBMS UE context of the UE.
Step s106, the UE generates an MBMS UE Context and sends an Activate MBMS Context Request (Activate MBMS Context Request) message to the SGSN, where the message includes an IP multicast address, an APN, an MBMS _ NSAPI, an MBMS bearer capability, and the like. The IP multicast address indicates the MBMS multicast service which the UE wants to join or activate; the APN may indicate a particular GGSN; the MBMS bearer capability indicates a maximum QoS (Quality of Service) that the UE can handle; the MBMS _ NSAPI is selected by the UE and contains a value that is not used by any other active PDP context and the MBMS UE context of the UE. If the SGSN has the MBMS bearing context information of the MBMS bearing service, the SGSN shall check the MBMS bearing capability of the UE. If the SGSN determines that the MBMS bearer capability of the UE is less than the required MBMS bearer capability, the SGSN shall reject the request for MBMS context activation and give appropriate reasons.
Step s107 a-step s107 b. if the MBMS UE context is not established, the SGSN sends an MBMS Notification Reject Request (MBMS Notification Request) message to the GGSN with a reason indicating the reason why the MBMS UE context is not established. Then, the GGSN returns an MBMS notification reject response to the SGSN, prevents further transmission of the MBMS notification request message, and terminates the procedure.
Step s108, performing security functions, such as authentication of the UE.
Step s109, in the a/Gb mode, if BSS (Broadband Switching System) route is activated, the SGSN shall send a Trace (Invoke Trace) message to the BSS in the RAN, where the message includes a route reference, a route type, a trigger Id, and an OMC (Operation & Management Center) identifier, where the route reference and the route type are copied from the route information of the HLR (Home Location Register) or the OMC.
Step s110, the SGSN generates an MBMS UE Context and sends a Create MBMS Context Request (Create MBMS Context Request) message to the GGSN, where the message includes a multicast address, an APN, an MBMS _ NSAPI, an IMSI (International Mobile Subscriber Identity), an MSISDN (Mobile Station International ISDN Number), an RAI (Routing Area Identity), an IMEI-SV, a RAT type, a MS (Mobile Station) time zone, a CGI (Common Gateway Interface, universal Gateway Interface)/SAI (Service Area Identity), a route reference, a route type, a trigger Id, an OMC Identity, and additional route MBMS information. If GGSN route is activated, SGSN shall contain route reference, route type, trigger Id and OMC identification; if the BM-SC route is activated, the SGSN shall contain additional MBMS route information. The SGSN should copy the route reference, route type and OMC identification from the route information received from the HLR or OMC. The inclusion of CGI/SAI should be done according to the specific details of 15.1.1a in TS 23.060.
Step s111 a-step s111b, the GGSN sends an MBMS authorization Request (MBMS authorization Request) message to find an authorization to activate the UE, where the message includes IMSI, MSISDN, RAI, IMEI-SV, RAT (Radio Access Technology) type, MS time zone, CGI/SAI, and additional MBMS route information. The GGSN should also contain additional MBMS routing information if the BM-SC route is activated. If the CGI/SAI is valid, it is also included. The Authorization decision is provided in an MBMS Authorization Response (MBMS Authorization Response) message. The BM-SC generates one MBMS UE context.
Step s112 a-step s112 b. if the GGSN does not have the MBMS bearer context information of the MBMS bearer service, the GGSN sends an MBMS registration request to the BM-SC. If the MBMS bearer service does not allocate a TMGI, the BM-SC allocates a new TMGI. The TMGI transmits the MBMS registration response message to the GGSN and the SGSN, and further notifies an Activate MBMS ContexttAccept message to the UE. BM-SC responds an MBMS register response message containing MBMS bearing context information for the MBMS bearing service, and adds the GGSN ID into the Downstream node List (List of Downflow Nodes) parameter of MBMS bearing context.
Step s113, the GGSN generates an MBMS UE Context and sends a Create MBMS Context Response (Create MBMS Context Response) message to the SGSN.
Step s114 a-step s114 b. if the SGSN does not have the MBMS bearer context information of the MBMS bearer service, the SGSN sends an MBMS registration request (MBMS registration request) message to the GGSN. The GGSN sends an MBMS Registration Response (MBMS Registration Response) message including MBMS bearer context information of the MBMS bearer service, and adds the identifier of the SGSN to a downstream node list parameter of the MBMS bearer context.
Step s115, if there is at least one PS RAB (Packet Switched Radio access bearer) established on the UE, the SGSN provides the MBMS UE context to the Iu mode RAN (Radio access network).
Step s116, in Iu mode, if the route is activated, SGSN shall send a trace message to RAN, the message including route reference, route type, trigger Id and OMC identification; and the route reference, route type and OMC identification are copied from the route information received from the HLR or OMC.
Step s117, the SGSN sends an Activate MBMS context Accept (Activate MBMS context Accept) message to the UE, where the message includes the TMGI and the MBMS bearer capability. The MBMS bearer capability indicates the maximum QoS used by the MBMS bearer service, which the UE considers when the MBMS bearer service is active. If it is not possible to detect the MBMS bearer capability of the UE in step s106, the MBMS bearer capability of the UE should be detected at this time. If the SGSN determines that the MBMS bearing capacity of the UE is lower than the requested MBMS bearing capacity, the SGSN sends an activation rejection request of the MBMS context and informs a proper reason to start the deactivation of the established MBMS UE context.
The problem existing in the prior art is that, in the above-mentioned service activation process step s106, the UE carries its own MBMS bearer capability in an activation MBMS Context Request (activation MBMS Context Request) sent to the SGSN, the SGSN compares the MBMS bearer capability of the UE with the MBMS bearer capability required by the service, if the MBMS bearer capability of the UE is lower than the MBMS bearer capability required by the service, the SGSN rejects the Request, and proceeds to step s117 to send an activation MBMS Context reception (activation MBMS Context Accept) message to the UE, where the activation Context reception message carries a cause value of activation failure.
However, the MBMS bearer capability is a physical characteristic of the UE, and the probability of change is relatively low, so if the UE needs to report the MBMS bearer capability to the network for verification every time the MBMS service is activated, redundant fields of the message will be added, and network resources will be wasted.
Disclosure of Invention
The problem to be solved by the present invention is to provide a method for processing an MBMS service, so as to reduce the signaling load when a network side processes an MBMS service of a user terminal in the prior art, thereby saving network resources.
In order to achieve the above object, an embodiment of the present invention provides a method for processing an MBMS service, including the following steps:
a network side receives an MBMS service request sent by a user terminal;
and the network side processes the MBMS service request of the user terminal according to the pre-acquired MBMS bearing capacity parameter of the user terminal.
Another embodiment of the present invention further provides a system for processing an MBMS service, including at least one user terminal and a network side device, wherein,
the user terminal sends an MBMS service request to the network side equipment;
and the network side equipment processes the MBMS service request of the user terminal according to the pre-acquired MBMS bearing capacity parameter of the user terminal and sends a processing result.
Another embodiment of the present invention further provides an apparatus for processing an MBMS service, including a first node and a second node,
the first node stores the MBMS bearing capacity parameter of the user terminal, processes the MBMS service request of the user terminal according to the MBMS bearing capacity parameter of the user terminal and sends a processing result to the user terminal or the second node;
and the second node sends the MBMS notification request of the user terminal to the first node and receives the processing result sent by the first node.
Still another embodiment of the present invention provides a user terminal of an MBMS service, which includes a registration module, and adds its MBMS bearer capability parameter in a registration request to send to the network side device.
Compared with the prior art, the embodiment of the invention has the following advantages:
when receiving an MBMS service request sent by a user terminal, the network side equipment directly calls the MBMS bearing capacity parameter of the user terminal which is stored before, and processes the request of the user terminal according to the parameter without transmitting the MBMS bearing capacity parameter of the user terminal in each service, thereby effectively reducing signaling load and saving network resources.
Drawings
Fig. 1 is a schematic diagram of an MBMS bearer service architecture in the prior art;
fig. 2 is a schematic diagram of a multicast bearer service activation flow in the prior art;
fig. 3 is a flowchart of a network device receiving and storing MBMS bearer capability parameters of a user terminal in a first embodiment of the present invention;
FIG. 4 is a flow chart of a processing method of a UMTS/GPRS network user equipment MBMS service in a second embodiment of the invention;
FIG. 5 is a flow chart of a processing method of a UMTS/GPRS network user equipment MBMS service in a third embodiment of the present invention;
fig. 6 is a flowchart of a method for processing MBMS service of a system architecture evolution network user equipment in a fourth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a system for processing an MBMS service in a fifth embodiment of the present invention.
Detailed Description
The invention is further described with reference to the following figures and specific embodiments.
When a user terminal UE is attached to a network, reporting the MBMS bearing capacity of the UE to the network; the network is saved for use during the subsequent MBMS service. In a specific implementation manner, the UE may add an IE (Information Element) to a registration request message such as an attach request, an RAU request, and the like: supported MBMS bearer capabilities to inform the MBMS bearer capabilities Supported by the UE on the network. In a specific implementation, the IE may be incorporated as another entry in other IEs, such as an MS radio access capability information element, or an MS network capability information element. After receiving the attach request of the UE, the network may store the MBMS bearer capability supported by the UE in a UE communication context, such as a mobility management context. The above process can be applied to networks supporting MBMS services, such as UMTS/GPRS networks, system architecture evolution networks, and the like.
The first embodiment of the present invention takes a UMTS/GPRS network as an example, and in the registration process of the UE, a specific implementation process is shown in fig. 3, which includes the following steps:
step s201, the UE initiates an attach procedure, and sends an attach request message to the SGSN, where the attach request message includes parameters such as IMSI or P-TMSI (Packet Temporary Mobile Subscriber identity), old RAI, and attach type, and further includes MBMS bearer capability parameters supported by the UE.
Step s202, the SGSN initiates an authentication procedure for the UE.
Step s203a and step s203b, if the activated PDP context of the UE exists on the SGSN, initiating a PDP context deletion procedure to the GGSN, and the GGSN deletes the PDP context that was originally activated by the UE according to parameters such as TEID (Tunnel Identifier) and confirms to the SGSN.
Step s204, SGSN initiates location updating to HLR for registration.
Step s205a and step s205b, the HLR inserts subscription data to the SGSN, which acknowledges.
Step s206, the HLR sends an update location confirmation to the SGSN.
Step s207, SGSN replies an attachment acceptance message to UE, the message has parameters such as P-TMSI, etc., and the MBMS bearing capacity supported by UE is saved; the parameters are stored in the UE context establishing process after being received by the SGSN, and are irrelevant to the specific steps.
Step s208, the UE replies an attach complete message to the SGSN.
After the UE bearer capability is saved in the network, the second embodiment of the present invention takes the UMTS/GPRS network as an example, and the improved MBMS service processing procedure is shown in fig. 4, which includes the following steps:
step s301, a general PDP context is established among the UE, the SGSN and the GGSN.
Step s302, the UE sends an IGMP or MLD join message in the default PDP context to indicate that the UE requests to receive a specific multicast MBMS bearer service indicated by one IP multicast address.
Step s303 a-step s303b, the GGSN sends an MBMS authorization Request (MBMS authorization Request) to the BM-SC to seek authorization information including path information, i.e. additional MBMS path information, for activating the UE to receive data. The authorization decision providing the member function in an MBMS authorization Response (MBMS authorization Response) is used together with the APN for generating the MBMS UE context based on the intra-BM-SC subscription data. If the MBMS grant response indicates that the UE does not have permission to receive MBMS data, the procedure is terminated and no further messages are exchanged.
Step s304a to step s304b, the GGSN sends an MBMS notification request to the SGSN, the request including the IP multicast address, APN and attached NSAPI. SGSN sends MBMS notification feedback information to GGSN, and feeds back the reason whether MBMS context is activated. If there is MBMS bearing context information of the MBMS bearing service on the SGSN, the MBMS bearing capability of the UE is checked. If the SGSN determines that the MBMS bearing capacity of the UE is smaller than the required MBMS bearing capacity, the replied MBMS notification response message has a failure reason value. If the unsuccessful operation message is fed back, the GGSN should not send the MBMS notification request message any more, and terminates the procedure. Otherwise, the multicast bearer service activation is performed according to the steps described in step s205 to step s217, and the description is not repeated here.
The third embodiment of the present invention takes UMTS/GPRS network as an example, and an improved MBMS service processing flow is shown in fig. 5, which includes the following steps:
step s401, a general PDP context is established among the UE, the SGSN and the GGSN.
Step s402, the UE sends an IGMP or MLD join message on the default PDP context requesting to receive the specific multicast MBMS bearer service indicated by one IP multicast address.
Step s403a to step s403b, where the GGSN transmits the MBMS authorization request to the BM-SC and receives the authorization response from the BM-SC, are the same as step s303a to step s303b in the second embodiment, and will not be described repeatedly herein.
Step s404a to step s404b, the GGSN sends an MBMS notification request to the SGSN, the request including the IP multicast address, APN and connected NSAPI. SGSN sends MBMS inform response message to GGSN, and feeds back the reason whether MBMS context is activated. If the unsuccessful operation message is fed back, the GGSN should not send the MBMS notification request message any more, and terminates the procedure.
Step s405, if there is the MBMS bearer context information of the MBMS bearer service on the SGSN, checking the MBMS bearer capability of the UE. If the SGSN determines that the MBMS bearing capacity of the UE is smaller than the required MBMS bearing capacity, the request for MBMS context activation is not initiated any more, and step s406 is performed; otherwise, the multicast bearer service activation is performed according to the steps described in step s205 to step s217, and the description is not repeated here.
Step s406 a-step s406 b. if the MBMS UE context is not established, the SGSN sends an MBMS Notification Reject Request (MBMS Notification Request) message to the GGSN with a reason indicating the reason why the MBMS UE context is not established. Then, the GGSN returns an MBMS notification reject response to the SGSN, prevents further transmission of the MBMS notification request message, and terminates the procedure.
In the above two methods, the check of the MBMS bearer capability supported by the UE is one of two options, that is, as described in the second embodiment, the SGSN immediately determines the MBMS bearer capability supported by the UE after receiving the MBMS notification request sent by the GGSN, and replies a failure to the GGSN in the MBMS request response message when the MBMS bearer capability does not meet the requirement; or as described in the third embodiment, before sending the message requesting the MBMS context activation to the UE, the SGSN determines the MBMS bearer capability supported by the UE, and sends the MBMS notification rejection request message to the GGSN if the MBMS bearer capability is not satisfied.
For the case that the UE actively initiates the MBMS service activation request message, that is, when the SGSN does not execute step s105 to request the UE to activate the MBMS service, the SGSN may also check the MBMS bearer capability of the UE in step s106 by using the MBMS bearer context information of the MBMS bearer service: UE generates a MBMS UE context and sends a request message for activating the MBMS context to SGSN, and the SGSN checks the MBMS bearing capacity of the UE. If the SGSN determines that the MBMS bearer capability of the UE is less than the required MBMS bearer capability, the request for MBMS context activation should be rejected and appropriate reasons given.
Before the network device does not store the MBMS bearer capability of the UE, the MBMS bearer capability of the UE cannot be checked according to the methods described in the second and third embodiments, in this case, according to the processing method in the prior art, after registering in step s112a to step s112b or step s114a to step s114b, the MBMS bearer capability of the UE is checked by the SGSN using the MBMS bearer context information of the MBMS bearer service in step s 117: the SGSN sends an Activate MBMS Context Accept message (TMGI, MBMS bearer capability) to the UE. If the SGSN determines that the MBMS bearing capacity of the UE is lower than the requested MBMS bearing capacity, the SGSN rejects the request for the activation of the MBMS context and informs the appropriate reason to deactivate the established MBMS UE context.
In a fourth embodiment of the present invention, taking a system architecture evolution network as an example, an improved MBMS service processing flow is shown in fig. 6, and includes the following steps:
step s501, UE registers to the network, establishes a default IP bearer, or activates a session Management related context for MBMS service, and stores the context in MME (Mobility Management Entity) and/or SAE (System Architecture evolution) gateway.
Step s502, the UE sends a multicast join message, such as an IPv4IGMP join message or an IPv6MLD join message, with a specific IP multicast address, indicating that it is ready to receive a specific multicast MBMS bearer service, on a default IP bearer or an activated session management related context.
Step s503, SAE gateway sends MBMS authorization request message to broadcast multicast service center to obtain authorization for UE to receive data, BM-SC returns authorization response with authorization result and MBMS service APN. If it is indicated in the MBMS authorization response that the UE is not authorized to receive MBMS data, the entire process flow ends with no further message exchange. This step is optional if the MME or SAE gateway holds the IP multicast address and the configuration policy of the broadcast multicast service center, etc.
Step s504, the SAE gateway sends an MBMS notification request to the MME, and the MBMS notification request has parameters such as IP multicast address. The MME sends an MBMS Notification response to the SAE gateway with a cause value indicating whether MBMS UE context activation will be handled. If the MME has the MBMS bearing context information of the MBMS bearing service, the MME shall check the MBMS bearing capacity supported by the UE. And if the MME determines that the MBMS bearing capacity of the UE is smaller than the required MBMS bearing capacity, returning a proper failure reason value in the MBMS notification response.
Step s505, the MME sends a message requesting MBMS UE context activation to the UE, requesting the UE to activate MBMS UE context, with parameters such as IP multicast address, MBMS service APN, etc.
Step s506, after receiving the request message of MME, or the UE knows the APN information of MBMS service and can initiate actively, creating an MBMS UE context, and sending a request message for activating MBMS UE context to MME, with parameters such as IP multicast address, MBMS service APN, etc. For the request message initiated by the UE actively, if the MME has the MBMS bearer context information of the MBMS bearer service, the MME shall check the MBMS bearer capability supported by the UE. If the MME determines that the MBMS bearer capability of the UE is less than the required MBMS bearer capability, the request for MBMS context activation should be rejected, and step s611 is proceeded to, and a suitable reason is given.
Step s507, MME creates MBMS UE context, and sends MBMS authorization request message to BM-SC to obtain authorization to UE; with parameters such as IMSI. BM-SC authorizes UE, creates MBMS UE context, and replies authorization response to MME. In this context information about the selected SAE gateway should be kept for addressing the SAE gateway at the start of the session.
Step s508, if the MME has not created the MBMS bearer context of the MBMS bearer service, sending an MBMS registration request message to the BM-SC. If a TMGI (Temporary Mobile Group Identity) needs to be allocated for the MBMS bearer service, the BM-SC allocates a new TMGI. BM-SC replies MBMS register response message with MBMS load context information of MBMS load service to MME, and adds the MME relative mark to BM-SC up-and-down stream node list parameter. And after receiving the response, the MME creates the MBMS bearing context of the MBMS bearing service.
Step s509, if at this time at least one packet domain radio access bearer is established for the UE, the MME provides the MBMS UE context to the radio access network entity.
Step s510, the MME sends an activate MBMS context accept message to the UE, with TMGI parameters, etc. If failure occurs in the above process, for example, authorization failure, the MME rejects the MBMS context activation request, returns an appropriate cause value, and the MME initiates a deactivation process to deactivate the established MBMS UE context.
Step s511, after receiving the MBMS context activation acceptance message, the UE replies an MBMS context activation completion message to the MME to perform confirmation. If the MME cannot check the MBMS bearer capability of the UE in step s504 or s506, the MME shall here check the MBMS bearer capability supported by the UE. If the MME determines that the MBMS bearer capability of the UE is less than the required MBMS bearer capability, the request for MBMS context activation should be rejected and appropriate reasons given.
In a fifth embodiment of the present invention, a structure of a system for processing an MBMS service is shown in fig. 7, and includes a plurality of user terminals 10 and a network device 20. Wherein,
the user terminal 10 comprises a registration module 101, which adds the MBMS bearer capability parameter of itself in a registration request to be sent to the first node 20 of the network device.
The network device 20 further includes a first node 21 and a second node 22, where the first node 21 stores MBMS bearer capability parameters sent by each user terminal, and determines whether a user terminal can meet a required MBMS bearer capability according to the MBMS bearer capability parameters of the user terminal; the second node 22 receives the judgment result sent by the first node 21, and activates or rejects the MBMS bearer service activation of the user terminal 10 according to the judgment result.
Specifically, the first node 21 further includes a storage module 211 and a processing module 212;
the storage module 211 receives and stores the MBMS bearer capability parameter sent by the user terminal during registration; the processing module 212 determines whether a certain ue can satisfy the required MBMS bearer capability according to the MBMS bearer capability parameter of the ue stored in the storage module, and sends the determination result to the second node 22 or the ue 10.
The invention is suitable for networks supporting MBMS services, such as a UMTS/GPRS network, a system architecture evolution network and the like, wherein when the invention is applied to the UMTS/GPRS network, a first node and a second node are respectively an SGSN and a GGSN; when the method is applied to a system architecture evolution network, the first node and the second node are respectively an MME and an SAE gateway.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (12)
1. A processing method of multimedia broadcast multicast service MBMS service is characterized by comprising the following steps:
a network side receives an MBMS service request sent by a user terminal;
and the network side processes the MBMS service request of the user terminal according to the pre-acquired MBMS bearing capacity parameter of the user terminal.
2. The method for processing the MBMS service of claim 1, wherein the method for the network side to obtain the MBMS bearer capability parameter in advance comprises: and when the user terminal is registered, the MBMS bearing capacity parameter is added in a registration request and is sent to the network side.
3. The MBMS service processing method of claim 2, wherein the network side stores the MBMS bearer capability parameter of the user terminal in the registration request in a communication context of the user terminal.
4. The method for processing the MBMS service of claim 1, wherein the step of the network side processing the MBMS service request of the user terminal further comprises:
a second node of the network side sends an MBMS notification request to a first node;
and the first node of the network side judges whether the user terminal can meet the MBMS bearing capacity required by the service according to the MBMS bearing capacity parameter of the user terminal acquired in advance, and sends a failure message to the second node of the network side when the user terminal cannot meet the MBMS bearing capacity.
5. The method for processing the MBMS service of claim 1, wherein the step of the network side processing the MBMS service request of the user terminal further comprises:
the user terminal sends a request message for activating the MBMS context to a first node of the network side;
and the first node at the network side judges whether the user terminal can meet the MBMS bearing capacity required by the service according to the MBMS bearing capacity parameter of the user terminal acquired in advance, and sends a rejection message to the user terminal when the user terminal cannot meet the MBMS bearing capacity.
6. The method for processing the MBMS service according to claim 4 or 5, wherein when the network is a universal radio system UMTS or a general packet radio service GPRS network, the first node and the second node at the network side are a serving GPRS support node SGSN and a gateway GPRS support node GGSN, respectively; when the network is a system architecture evolution network, the first node and the second node at the network side are respectively a mobility management entity MME and a system architecture evolution SAE gateway.
7. A processing system of MBMS service comprises at least one user terminal and network side equipment,
the user terminal sends an MBMS service request to the network side equipment;
and the network side equipment processes the MBMS service request of the user terminal according to the pre-acquired MBMS bearing capacity parameter of the user terminal and sends a processing result.
8. The MBMS service processing system of claim 7, wherein the network side device includes a first node and a second node;
the first node stores the MBMS bearing capacity parameter of the user terminal, processes the MBMS service request of the user terminal according to the MBMS bearing capacity parameter of the user terminal and sends a processing result to the user terminal or the second node;
and the second node sends the MBMS notification request of the user terminal to the first node and receives the processing result sent by the first node.
9. The MBMS service processing system of claim 7, wherein the ue includes a registration module, which adds its MBMS bearer capability parameter to a registration request and sends the registration request to the network side device.
10. An MBMS service processing device, comprising a first node and a second node,
the first node stores the MBMS bearing capacity parameter of the user terminal, processes the MBMS service request of the user terminal according to the MBMS bearing capacity parameter of the user terminal and sends a processing result to the user terminal or the second node;
and the second node sends the MBMS notification request of the user terminal to the first node and receives the processing result sent by the first node.
11. The MBMS service processing apparatus of claim 10, wherein the first node includes a storage module and a processing module;
the storage module receives and stores the MBMS bearing capacity parameter sent by the user terminal during registration;
and the processing module processes the MBMS service request of the user terminal according to the MBMS bearing capacity parameter of the user terminal stored by the storage module and sends a processing result.
12. A user terminal of MBMS service is characterized in that the user terminal comprises a registration module, and the registration module adds the MBMS bearing capacity parameter of the user terminal into a registration request and sends the registration request to network side equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007100010234A CN101227307A (en) | 2007-01-19 | 2007-01-19 | Equipment, system and method for processing multimedia broadcast multicast business |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007100010234A CN101227307A (en) | 2007-01-19 | 2007-01-19 | Equipment, system and method for processing multimedia broadcast multicast business |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101227307A true CN101227307A (en) | 2008-07-23 |
Family
ID=39859076
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007100010234A Pending CN101227307A (en) | 2007-01-19 | 2007-01-19 | Equipment, system and method for processing multimedia broadcast multicast business |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101227307A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101784010A (en) * | 2009-01-16 | 2010-07-21 | 上海贝尔股份有限公司 | Method and device for assisting in establishing fixed network multicasting return path for mobile multicasting service |
| CN102149189A (en) * | 2010-02-10 | 2011-08-10 | 中兴通讯股份有限公司 | Registration method, device and system of voice over long term evolution (LTE) via generic access (VOLGA) |
| CN102986186A (en) * | 2011-06-23 | 2013-03-20 | 华为技术有限公司 | Method for terminal network element registration, terminal network element and router |
| WO2017054544A1 (en) * | 2015-09-30 | 2017-04-06 | 华为技术有限公司 | Enhanced multimedia broadcast multicast service (embms) implementation method and apparatus |
| CN107005816A (en) * | 2015-01-13 | 2017-08-01 | 华为技术有限公司 | A kind of processing method and processing device of group service |
-
2007
- 2007-01-19 CN CNA2007100010234A patent/CN101227307A/en active Pending
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101784010A (en) * | 2009-01-16 | 2010-07-21 | 上海贝尔股份有限公司 | Method and device for assisting in establishing fixed network multicasting return path for mobile multicasting service |
| US8982883B2 (en) | 2009-01-16 | 2015-03-17 | Alcatel Lucent | Method and apparatus for aiding the establishment of the multicast backhaul in the fixed network for mobile multicast service |
| CN102149189A (en) * | 2010-02-10 | 2011-08-10 | 中兴通讯股份有限公司 | Registration method, device and system of voice over long term evolution (LTE) via generic access (VOLGA) |
| CN102986186A (en) * | 2011-06-23 | 2013-03-20 | 华为技术有限公司 | Method for terminal network element registration, terminal network element and router |
| CN102986186B (en) * | 2011-06-23 | 2015-05-27 | 华为技术有限公司 | Method for terminal network element registration, terminal network element and router |
| CN107005816A (en) * | 2015-01-13 | 2017-08-01 | 华为技术有限公司 | A kind of processing method and processing device of group service |
| WO2017054544A1 (en) * | 2015-09-30 | 2017-04-06 | 华为技术有限公司 | Enhanced multimedia broadcast multicast service (embms) implementation method and apparatus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8165053B2 (en) | Method for supporting MBMS service transmission in LTE system | |
| US10455489B2 (en) | Method for supporting PDN GW selection | |
| EP1796405B1 (en) | Method and apparatus of service identifying and routing in multimedia broadcast/multicast service system | |
| EP2040493B1 (en) | Apparatus and method for supporting mobility of wireless terminal in wireless communication network | |
| US7450534B2 (en) | Temporary mobile group identifier generation and distribution method | |
| US7546108B2 (en) | Method for supporting backward compatibility of MBMS | |
| US8842593B2 (en) | Method for activating multimedia broadcast/multicast service | |
| US8582503B2 (en) | Method for indicating the bearer management of a serving gateway | |
| US20070014291A1 (en) | Method for multimedia broadcast/multicast service registration | |
| US20060166653A1 (en) | Multicast transmission in a cellular network | |
| US9144105B2 (en) | Deactivation method of multimedia broadcast multicast service and related device | |
| EP1987693B1 (en) | Handling multiple point-to-multipoint services | |
| US7277706B2 (en) | Provision of service contexts in a communication system | |
| WO2009094916A1 (en) | A control method, system, and device for circuit domain fallback | |
| KR20040067975A (en) | System and method for supporting multimedia broadcast/multicast service in non tracking area | |
| US20070133565A1 (en) | Content packet transmission control method in mobile communication network supporting multimedia broadcast/multicast service | |
| JP2004528783A (en) | Method, network device, and terminal device for controlling context activation | |
| CN101227307A (en) | Equipment, system and method for processing multimedia broadcast multicast business | |
| CN102395110B (en) | Method for supporting MBMS service transmission in LTE system | |
| US20100142430A1 (en) | Multimedia data service apparatus of mobile communication system supporting multicast and multicast service activation and deactivation methods for multimedia data service | |
| KR100690439B1 (en) | Method for simplification of the service activation or deactivation in mbms system | |
| WO2004034655A1 (en) | A method of establishing and deleting mbms service in sgsn and ggsn | |
| CN101232701B (en) | Equipment and method for activating broadcast multicast business | |
| WO2008046264A1 (en) | Method of accessing multicast service for roaming user in mobile communication system | |
| CN101232639A (en) | Device and method for activating multimedia broadcast / multicast business |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20080723 |