CN101384005A - Method for routing region updating using UE of MBMS service in communication system - Google Patents
Method for routing region updating using UE of MBMS service in communication system Download PDFInfo
- Publication number
- CN101384005A CN101384005A CNA2008101687203A CN200810168720A CN101384005A CN 101384005 A CN101384005 A CN 101384005A CN A2008101687203 A CNA2008101687203 A CN A2008101687203A CN 200810168720 A CN200810168720 A CN 200810168720A CN 101384005 A CN101384005 A CN 101384005A
- Authority
- CN
- China
- Prior art keywords
- sgsn
- ggsn
- mbms
- message
- context
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a method for updating a routing region of UE using the MBMS service in a communication system. The UE sends routing region updating request information to a new SGSN; the new SGSN sends SGSN context request information to an old SGSN; the old SGSN sends SGSN context response information to the new SGSN and contains MBMS context; the new SGSN sends updated MBMS context request information to M-GGSN and contains a new SGSN address; the M-GGSN sends updated MBMS context response information to the new SGSN; and the new SGSN sends routing region updating reception to the UE. From the U-GGSN to the signal interaction of Old SGSN and New SGAN as well as from the M-GGSN to the new signal interaction of the Old SGSN and the New SGSN, the invention solves the problems existing in the prior art. After entering a new routing region, the UE can continuously use the MBMS service. The SGSN which does not support the MBMS service can also indirectly provide the MBMS service to the UE. The U-GGSN can provide the MBMS service to the UE by a point-to-point PS way. The invention remains the consistency of the MBMS context in the UE, the SGSN and the GGSN.
Description
Technical field
The present invention relates to the method that a kind of UE that uses the MBMS business in the WCDMA communication system carries out routing region updating.
Background technology
Multimedia broadcasting and multicast service (hereinafter to be referred as MBMS) are that a standardized new business is being carried out in third generation partner plan (hereinafter to be referred as 3GPP).The MBMS business is a kind of business of unidirectional point-to-multipoint, and the maximum characteristics of this business are that it can effectively utilize Radio Resource and Internet resources.
For MBMS better is described, Fig. 1 has described the system configuration of MBMS, Fig. 2 has described the flow process that a UE sets up the MBMS multicast service as an example, Fig. 3 described the flow process that UE in the prior art carries out routing region updating (upgrading hereinafter to be referred as RA), and Fig. 4 has described the flow process that a UE leaves the MBMS multicast service.
As shown in Figure 1, the MBMS network configuration is based on GPRS (hereinafter to be referred as GPRS) core net, and increased new network element.101 broadcasting and multicast service center (hereinafter to be referred as BM-SC) are the professional control centres of MBMS system.102 Gateway GPRS Support Nodes (hereinafter to be referred as GGSN) and 103 Serving GPRS Support Nodes (hereinafter to be referred as SGSN) have constituted the transmission network of MBMS business, for the transmission of data provides route.104 land radio access webs (hereinafter to be referred as RAN) provide Radio Resource for MBMS serves on the interface aloft.105 subscriber equipmenies (hereinafter to be referred as UE) are the terminal equipments that is used for receiving data.106 attaching position registers (hereinafter to be referred as HLR) are preserved and subscriber-related data, and services such as subscription authentication can be provided.107Gn/Gp represents the interface between SGSN and the GGSN.108Gi represents that interface and the interface protocol between BM-SC and the GGSN is Internet group management protocol of the multicast group (hereinafter to be referred as IGMP).109Gmb represents that interface and the interface protocol between BM-SC and the GGSN is exclusively used in transmission MBMS signaling parameter.The professional used Radio Resource of MBMS is not user's special use, but professional thus all users share.
Process description as shown in Figure 2 is as follows:
201 UE initiate to set up the process of PDP Context.After PDP Context is set up successfully, all preserve this PDP Context in UE, SGSN and GGSN, the signaling of having set up the exchanges data territory simultaneously between UE and GGSN connects, and the intermediate equipment that this signaling connects is RAN and SGSN.
202 UE send IGMP to GGSN and add message, and this message arrives GGSN by the signaling connection of setting up in the step 201.This message comprises parameter: IP multicast address, this multicast address can indicate a certain multicast service in a certain MBMS multicast service or the external data network.
203 GGSN and BM-SC carry out Signalling exchange so that UE is carried out authentication.
204 GGSN send the MBMS notification request message to SGSN, and this message comprises parameter: IP multicast address, APN, Linked NSAPI.Wherein IP multicast address and APN indicate the MBMS business, and NSAPI indicates a specific PDP Context, and UE sends IGMP by this PDP Context to add message.In addition, the APN here may be resolved to the different GGSN of another one and get on, and receives in 202 that promptly the GGSN of IGMP message and the GGSN that the MBMS business is provided may be different.
After 205 SGSN receive message in the step 204, send request MBMS context activation message to UE, this message comprises parameter: IP multicast address, APN, Linked NSAPI.This place parameter implication and 204 in identical.
After 206 UE receive message in the step 205, send to SGSN and to activate the MBMS context request message, this message comprises parameter: IP multicast address, APN.The APN here may be resolved to the different GGSN of another one and get on, and receives in 202 that promptly the GGSN of IGMP message and the GGSN that the MBMS business is provided may be different.
207 if desired, carries out ciphering process between UE and the SGSN.
208 SGSN send to GGSN and set up the MBMS context request message, and this message comprises IP multicast address and APN.
209 GGSN carry out Signalling exchange so that MBMS business and UE are carried out authentication with BM-SC after receiving message in the step 208.
210 authentications are passed through, and GGSN sets up the MBMS context for this UE.If GGSN did not set up the MBMS bearer context before, perhaps be to use the UE of this MBMS business to set up the MBMS context for the first time in GGSN, then GGSN sends bearing request message to BM-SC, and this message comprises parameter: IP multicast address, APN.
After BM-SC received the bearing request message of above-mentioned GGSN transmission, if there is not bearer context among the BM-SC, then BM-SC set up bearer context.BM-SC joins parameter in the bearer context: list of downstream nodes (descendant node tabulation) with the sign of GGSN, and BM-SC sends the carrying response message to GGSN then, and this message comprises parameter: IP multicast address, APN, session attribute, state, TMGI.
After 211 GGSN received the message that BM-SC sends in above-mentioned 210, GGSN set up bearer context, and set up the MBMS context acknowledge message to the SGSN transmission.
After 212 SGSN received the message that GGSN sends in above-mentioned 211, SGSN set up the MBMS context for this UE.If SGSN did not set up the MBMS bearer context before, perhaps be to use the UE of this MBMS business to set up the MBMS context for the first time in SGSN, then SGSN sends the MBMS bearing request message to GGSN, and this message comprises parameter: IP multicast address, APN, TEID.After GGSN received the MBMS bearing request message that above-mentioned SGSN sends, GGSN was added to parameter in the bearer context with the sign of SGSN: among the list of downstream nodes (descendant node tabulation).Then, GGSN sends MBMS carrying response message to SGSN, and this message comprises parameter: IP multicast address, APN, session attribute, state, TMGI.
213 SGSN offer RAN with the MBMS context of UE.
214 SGSN send activation MBMS context to UE and accept message, and UE also sets up the MBMS context after receiving message, and activation finishes.
In the described process of above-mentioned Fig. 2, the MBMS context of preserving in SGSN and GGSN after UE activation MBMS business about UE is as shown in table 1:
Table 1
Parameter | Describe |
IP multicast address | Be used to indicate the MBMS carrying, and indicate a MBMS business with APN. |
APN | The access point name indicates a MBMS business with IP multicast address. |
TMGI | Temporary mobile group identity is for the MBMS carrying distributes. |
Linked NSAPI | Sign UE is used to send the PDP of IGMP message |
Context. |
In the described process of above-mentioned Fig. 2, the bearer context of preserving in SGSN and GGSN after UE activation MBMS business about the MBMS business is as shown in table 2:
Table 2
Parameter | Describe |
IP multicast address | Be used to indicate the MBMS carrying, and indicate a MBMS business with APN. |
APN | The access point name indicates a MBMS business with IP multicast address. |
TMGI | Temporary mobile group identity is for the MBMS carrying distributes. |
State | Current contextual state is described: idle or busy.Idle expression conversation procedure does not also begin, and busy expression conversation procedure begins. |
QoS | Service quality for MBMS carrying distribution. |
Li st of Downstream Nodes | All descendant nodes that once required to set up carrying to this node are preserved in descendant node tabulation, this tabulation.MBMS data and MBMS notification message are exactly in the descendant node that is sent out according to this tabulation. |
Number of UEs | Expression has activated the number of the UE of MBMS business. |
Fig. 3 has described the method that UE carries out routing region updating.RA is updated in SGSN and it seems two kinds of different situations: carrying out between the different SGSN and carrying out between identical SGSN.The present invention focuses on the RA renewal process of carrying out between different SGSN, so Fig. 3 has described carry out more news of RA in the prior art between different SGSN.Action of the present invention in addition mainly occurs in core network side, promptly between SGSN and SGSN and SGSN and GGSN, so do not do explanation to reaching the action that relates to RAN among the present invention in the prior art.
301 when UE enters new Routing Area by New SGSN control, and UE sends the RA update inquiry information to New SGSN.This message comprises necessary parameter to be made New SGSN can discern UE and finds the Old SGSN that UE is managed.
302 New SGSN send the SGSN context request message to Old SGSN.This request message is in order to notify Old SGSN that Old SGSN is sent to New SGSN about the context of UE.303 Old SGSN send the SGSN context acknowledge message to New SGSN.This message has comprised the context of preserving among the OldSGSN about this UE.
After 304 New SGSN receive context message, UE is carried out safety inspection.This process need is preserved the participation of the central database HLR of UE log-on message.
305 New SGSN send the SGSN context acknowledgement message to Old SGSN, and expression New SGSN has received context.
After 306 Old SGSN receive affirmation message in the step 305, send the data packet message of hopping to New SGSN, this message comprises the data of temporarily being hung up by Old SGSN because UE moves.
307 New SGSN send to GGSN and upgrade the PDP Context request message.
308 GGSN send to New SGSN and upgrade the PDP Context response message.
309 New SGSN and Old SGSN and HLR carry out the position renewal alternately and insert user data.
310 New SGSN send the RA renewal to UE and accept message, and this message comprises parameter: P-TMSI, P-TMSI signature.
311 UE send the RA renewal to SGSN and finish message, confirm to have received the P-TMSI of distribution, and whole RA renewal process is finished.
Process description as shown in Figure 4 is as follows:
401 when UE wants to leave a certain MBMS multicast service group, if UE is in idle condition (PMM-IDLE), UE initiates the service request process and connects with the signaling of setting up the packet switch domain from UE to GGSN, and this process is existing process, after finishing, UE just can send out upstream data.
402 when UE wants to leave a certain MBMS multicast service group, and UE sends IGMP by the PDP Context of having set up to GGSN and leaves (IGMP Leave) message, the IP multicast address parameter sign that this message comprises UE want the multicast service group left.
403 GGSN and BM-SC carry out Signalling exchange so that BM-SC removes the relevant information of UE.
404 GGSN send deletion MBMS context request message to SGSN, and this message comprises IP multicast address and APN.
405 SGSN send anti-MBMS context request (the Deactivate MBMS ContextRequest) message that activates to UE.
406 UE deletion MBMS context also instead activates the MBMS context to the SGSN transmission and accepts message.
After 407 SGSN received message in the step 406, deletion MBMS context also sent deletion MBMS context acknowledge message to GGSN, and GGSN receives same deletion MBMS context after this message, and so far anti-activation finishes.
In the prior art, when UE carries out routing region updating, because the appearance of MBMS business, should make UE can continue to receive the MBMS business, but because the particularity of MBMS business, be that the MBMS business is a shared service, provide the GGSN of the business of MBMS may be different simultaneously with the GGSN of the PDP Context of preserving UE, the new Routing Area that enters of UE may be by the SGSN control of not supporting the MBMS business in addition, this all makes in the prior art, when UE entered a new Routing Area and this Routing Area by a new SGSN control, network can not well provide the MBMS business to UE.
Summary of the invention
The purpose of this invention is to provide the method that the UE that uses the MBMS business in a kind of communication system carries out routing region updating, make UE after carrying out routing region updating, can continue to use the MBMS business.
For achieving the above object, a kind of method of routing region updating is characterized in that:
" the routing region updating request information is given new SGSN in the UE transmission;
New SGSN sends " SGSN context request " message and gives old SGSN;
Old SGSN sends " the SGSN context is replied " message and gives new SGSN, comprises the MBMS context;
" the update MBMS context request information is given M-GGSN, comprises new SGSN address in new SGSN transmission;
M-GGSN sends " update MBMS context response " message and gives new SGSN;
New SGSN sends " routing region updating acceptance " and gives UE.
The present invention is by the Signalling exchange of new U-GGSN to Old SGSN and New SGSN, and M-GGSN has solved problems of the prior art to the new Signalling exchange of Old SGSN and New SGSN.UE can continue to use the MBMS business after entering new Routing Area.Do not support the SGSN of MBMS business can provide the MBMS business indirectly to UE yet.U-GGSN can use point-to-point PS mode to provide the MBMS business to UE.Kept the contextual consistency of MBMS among UE, SGSN and the GGSN.
Description of drawings
Fig. 1 has described the system configuration of MBMS.
Fig. 2 has described the flow process that a UE sets up the MBMS multicast service as an example.
Fig. 3 has described the flow process that UE carries out routing region updating (hereinafter to be referred as the RA renewal) in the prior art.
Fig. 4 has described the flow process that a UE leaves the MBMS multicast service.
Fig. 5 has described when U-GGSN and M-GGSN are not a GGSN, and UE carries out the flow process of RA renewal process.
Fig. 6 has described the course of action of node Old SGSN in the flow process of above-mentioned Fig. 5.
Fig. 7 has described the course of action of node New SGSN in the flow process of above-mentioned Fig. 5.
Fig. 8 has described the course of action of node U-GGSN in the flow process of above-mentioned Fig. 5.
Fig. 9 has described the course of action of node M-GGSN in the flow process of above-mentioned Fig. 5.
Figure 10 has described when U-GGSN and M-GGSN are a GGSN, and UE carries out the flow process of RA renewal process.
Figure 11 has described the course of action of node Old SGSN in the flow process of above-mentioned Figure 10.
Figure 12 has described the course of action of node New SGSN in the flow process of above-mentioned Figure 10.
Figure 13 has described the course of action of node GGSN in the flow process of above-mentioned Figure 10.
Figure 14 has described the subprocess of setting up the MBMS bearer context of being initiated by SGSN.
Figure 15 has described the subprocess of the deletion MBMS bearer context of being initiated by SGSN
Embodiment
Owing to provide the GGSN of the business of MBMS may be different,, following name arranged among the present invention for GGSN that distinguishes the PDP Context of preserving UE and the contextual GGSN of MBMS that preserves UE with the GGSN of the PDP Context of preserving UE:
◆ U-GGSN: preserve the GGSN of the PDP Context of UE, this GGSN also provides other data service to UE by point-to-point mode
◆ M-GGSN: preserve the contextual GGSN of MBMS of UE, this GGSN provides MBMS business to UE specially, need to prove, if certain UE has been based upon oneself PDP Context among the M-GGSN, U-GGSN and M-GGSN are same GGSN concerning this UE.
◆ Old SGSN: the SGSN of working control UE before UE enters new Routing Area.
◆ New SGSN: the SGSN of working control UE after UE enters new Routing Area
When U-GGSN and M-GGSN were not a GGSN, UE carried out routing region updating (RA renewal) process, comprising:
-UE is to New SGSN, Old SGSN, U-GGSN, the overall flow of M-GGSN.
The node action process of-New SGSN.
The node action process of-Old SGSN.
The node action process of-U-GGSN.
The node action process of-M-GGSN.
When U-GGSN and M-GGSN were a GGSN, UE carried out routing region updating (RA renewal) process, comprising:
-UE is to New SGSN, Old SGSN, U-GGSN, the overall flow of M-GGSN.
The node action process of-New SGSN.
The node action process of-Old SGSN.
The node action process of-U-GGSN.
The node action process of-M-GGSN.
-when U-GGSN and M-GGSN are not a GGSN, the RA renewal process
◆ Fig. 5 has described when U-GGSN and M-GGSN are not a GGSN, and UE carries out the flow process of RA renewal process.
Above-mentioned Fig. 5 501 in, when UE enters a new Routing Area, by the Routing Area sign (RAI) in the broadcast message that contrasts sub-district, current place, UE finds own in a new Routing Area, so UE sends the RA update inquiry information to SGSN, this message comprises parameter: P-TMSI, Old RAI, TMGI, Old P-TMSI Signature or the like.TMGI wherein is the new argument after the introducing MBMS business, is used to distinguish different MBMS business when UE paging receiving information.
Above-mentioned Fig. 5 502 in, after New SGSN receives message, utilize prior art to derive the address of Old SGSN and send the SGSN context request message to Old SGSN by parameter Old RAI or Old P-TMSI.This message comprises parameter: IMSI, Old RAI etc.
Above-mentioned Fig. 5 503 in, after Old SGSN received the SGSN context request message from New SGSN, SGSN was put into MM context, PDP Context and the MBMS context of UE in the SGSN context acknowledge message, sends to New SGSN.The parameter that UE is carried out mobile management and access preserved in the MM context, and PDP Context is preserved the parameter about the data field connection of UE, and MBMS preserves the parameter about the use MBMS business of UE.
Above-mentioned Fig. 5 504 in, after New SGSN received the SGSN context acknowledge message from Old SGSN, New SGSN was by carrying out safety verification and authentication with UE and HLR exchange message to UE.
Above-mentioned Fig. 5 505 in, New SGSN finishes behind the security process and sends the SGSN context acknowledgement message to Old SGSN, its effect is to confirm that to Old SGSN NewSGSN has received contextual information.After Old SGSN receives this acknowledge message, be invalid, and after waiting for the regular hour it deleted that the time of wait is depended on realization with the MM context about UE, PDP Context, the MBMS contextual tagging of oneself preserving.
Above-mentioned Fig. 5 506 in, Old SGSN will not reach the packet that sends to UE and will send to New SGSN by message by GTP tunnel, send to UE by New SGSN after the RA process is finished.
Above-mentioned Fig. 5 507 and 508 in, New SGSN send to upgrade the PDP Context request message to U-GGSN, this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.U-GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to New SGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of U-GGSN, after New SGSN receives this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
Above-mentioned Fig. 5 509 in, this process utilizes prior art to make that by Old SGSN, New SGSN and HLR exchange message the positional information about UE of preserving among the HLR obtains upgrading, delete the UE information of preserving among the Old SGSN simultaneously, send some the permanent subscription information about UE of preserving among the HLR to New SGSN in addition.
Above-mentioned Fig. 5 510 in, U-GGSN sends the MBMS notification request message to New SGSN, this message is in order to tell New SGSN that described UE has activated the MBMS business, this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
Above-mentioned Fig. 5 511 in, after New SGSN received the message of U-GGSN transmission, if NewSGSN supports MBMS, then New SGSN sent MBMS notice response message to U-GGSN, this message comprises parameter: Cause, the Cause parameter comprises some explanations to message itself.If New SGSN does not support MBMS, then New SGSN ignores this message or sends error messages to U-GGSN.
Above-mentioned Fig. 5 512 in, if U-GGSN does not receive the MBMS notice response message in described 511, or U-GGSN receives error message, then U-GGSN sends deletion MBMS context notification request message to Old SGSN, this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly U-GGSN requires the contextual reason of Old SGSN deletion MBMS.
Above-mentioned Fig. 5 513 in, after Old SGSN received the deletion MBMS context notification request message of sending from U-GGSN, Old SGSN sent deletion MBMS context notice response message to U-GGSN, this message comprises parameter: Cause, Cause represents reason.
Above-mentioned Fig. 5 514 in, Old SGSN by above-mentioned Fig. 5 512 in the parameter that comprises in the message received find corresponding M BMS context, and send deletion MBMS context request message to M-GGSN, this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, Teardown Ind represents to delete designator, if Teardown Ind parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
Above-mentioned Fig. 5 515 in, M-GGSN finds corresponding M BMS context that it is deleted according to the message of sending from Old SGSN in 514, and sends deletion MBMS context acknowledge message to Old SGSN, this message comprises parameter: TEID, Cause.After Old SGSN receives deletion MBMS context acknowledge message, if Old SGSN finds that oneself has been not empty about the MBMS context of UE and the Li st of Downstream Nodes parameter in the bearer context among the Old SGSN, promptly do not have descendant node to need to receive the MBMS data again, then Old SGSN initiates the subprocess of deletion MBMS bearer context as shown in figure 15.
Above-mentioned Fig. 5 516 in, if New SGSN supports MBMS, then it is after 511 the action of finishing above-mentioned Fig. 5, New SGSN sends the update MBMS context request message to M-GGSN, this message comprises parameter: New SGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the M-GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the M-GGSN.
Above-mentioned Fig. 5 517 in, when M-GGSN above-mentioned Fig. 5 516 in receive the update MBMS context request message that sends from New SGSN after, M-GGSN is according to receiving that the parameter that comprises in the message finds the MBMS context that will upgrade, and upgrade wherein relevant parameters territory, afterwards, M-GGSN sends the update MBMS context response message to New SGSN, comprises the TEID of parameter: GGSN in sending message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the M-GGSN, and Cause represents reason.After New SGSN received the update MBMS context response message, if New SGSN finds oneself also do not have the MBMS bearer context, then New SGSN initiated the subprocess of setting up the MBMS bearer context as shown in figure 14.
Above-mentioned Fig. 5 518 in, when U-GGSN above-mentioned Fig. 5 510 after do not receive correct response message after, the U-GGSN supposition should provide MBMS business to UE by existing point-to-point mode, so U-GGSN and BM-SC exchange message, its objective is that the multicast service while BM-SC in order to allow U-GGSN add among the BM-SC can carry out authentication to U-GGSN, after 518, U-GGSN adds the multicast service among the BM-SC, just can provide MBMS business to UE by point-to-point mode later.
Above-mentioned Fig. 5 519 in, after 518 successes of above-mentioned Fig. 5, U-GGSN sends the point-to-point PS mode of MBMS notification message to UE, this message comprises parameter: IP multicast address and APN.After UE received this message, UE can select according to specific implementation: suspend contextual use of MBMS or deletion MBMS context.
Above-mentioned Fig. 5 520 in, if New SGSN supports MBMS, above-mentioned Fig. 5 510 after, after New SGSN knows that UE is to use the UE of MBMS, New SGSN the above-mentioned Fig. 5 that receives 503 in the SGSN context acknowledge message in there is no the MBMS context, then New SGSN sends request MBMS context activation message to UE, this message and above-mentioned Fig. 2 205 in the message of SGSN transmission identical.
Above-mentioned Fig. 5 521 in, UE carry out to activate the MBMS context procedures, this process substantially with above-mentioned Fig. 2 in 206 to 214 identical, only in Fig. 5, GGSN has been divided into U-GGSN and M-GGSN.
Above-mentioned Fig. 5 522 in, New SGSN has approved that UE is in the existence of new Routing Area and send RA and upgrade and receive message to UE.This message comprises parameter: P-TMSI, P-TMSISignature.These two parameters are that New SGSN distributes to UE as the identity sign in this RA zone.
Above-mentioned Fig. 5 523 in, UE receive above-mentioned Fig. 5 522 in after the message that sends from New SGSN, UE confirms the P-TMSI and the P-TMSI Signature that distribute in this message, and sends RA and upgrade and finish message to New SGSN, so far, the RA renewal process finishes.
◆ Fig. 6 has described the course of action of node Old SGSN in the flow process of above-mentioned Fig. 5.
502 stages of 601 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 601 stages, Old SGSN receives the SGSN context request message that sends from New SGSN, and all context message about UE that this message request Old SGSN will preserve send to New SGSN.This message comprises parameter: OldP-TMSI, Old RAI, Old P-TMSI Signature.These parameters are in order to allow Old SGSN find corresponding all contextual informations about this UE.
503 stages of 602 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 602 stages, after Old SGSN finds all contextual informations of UE of preservation, send the SGSN context acknowledge message to NewSGSN.This message comprises all contextual informations about UE: the MM context, and PDP Context, if UE has activated the MBMS business, this message also comprises the MBMS context.
505 stages of 603 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 603 stages, Old SGSN receives the SGSN context acknowledgement message that sends from New SGSN, and this message confirms that to Old SGSN New SGSN has received the contextual information of UE.
In 506 stages of 604 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6, in 604 stages, the data that the time-out that Old SGSN will preserve sends to UE send to New SGSN earlier by the data packet message of hopping, and send to UE in due course by New SGSN.
509 stages of 605 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 605 stages, Old SGSN and HLR are mutual, upgrade the contextual information about UE, and the Iu about UE is connected between release and the RAN, according to the difference that realizes, after Old SGSN can be chosen in for 605 stages, deletion again after all contextual informations of deleting UE immediately also can wait a period of time.
606 of above-mentioned Fig. 6 is judgment condition, if the New SGSN in above-mentioned Fig. 5 supports MBMS then Old SGSN entered into for 607 stages, otherwise Old SGSN entered into for 611 stages.
512 stages of 607 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 607 stages, Old SGSN receives the deletion MBMS context notification request message that sends from U-GGSN, and this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly U-GGSN requires the contextual reason of Old SGSN deletion MBMS.The purpose in 607 stages is, if New SGSN does not support MBMS, at this moment should continue to provide MBMS business with point-to-point PS mode to UE, but New SGSN does not support MBMS, so can not carry out alternately to upgrade the MBMS contextual information of preserving among the M-GGSN with M-GGSN, this has just caused the MBMS context of preserving among the M-GGSN incorrect, so require Old SGSN to go to delete the MBMS context of preserving among the M-GGSN alternately with M-GGSN here.
513 stages of 608 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 608 stages, Old SGSN sends deletion MBMS context notice response message to U-GGSN, and this message comprises parameter: Cause, Cause represents reason.
514 stages of 609 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 609 stages, Old SGSN finds corresponding M BMS context by the parameter that comprises in the message of receiving in above-mentioned 607 stages, and sends deletion MBMS context request message to M-GGSN, and this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, Teardown Ind represents to delete designator, if Teardown Ind parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
515 stages of 610 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 6.In 610 stages, Old SGSN receives the deletion MBMS context acknowledge message that sends from M-GGSN, and this message comprises parameter: TEID, Cause.Show that M-GGSN deletes corresponding M BMS context.
611 phase table of above-mentioned Fig. 6 are shown in the release of Old SGSN in Fig. 5 flow process.
◆ Fig. 7 has described the course of action of node New SGSN in the flow process of above-mentioned Fig. 5.
501 stages of 701 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 701 stages, New SGSN receives the RA update inquiry information that sends from UE, and this message comprises parameter: P-TMSI, Old RAI, TMGI, Old P-TMSI Signature or the like.TMGI wherein is the new argument after the introducing MBMS business, when paging UE, is used to make UE to distinguish different MBMS business.
502 stages of 702 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 702 stages, after New SGSN receives the message of above-mentioned 701 stage UE, utilize prior art to derive the address of Old SGSN and send the SGSN context request message to Old SGSN by parameter Old RAI or OldP-TMSI.This message comprises parameter: IMSI, Old RAI etc.
503 stages of 703 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 703 stages, New SGSN receives the SGSN context acknowledge message that sends from Old SGSN, and this message comprises MM context, PDP Context and the MBMS context of UE.New SGSN can preserve MM context, the PDP Context of the UE that receives in the message.If New SGSN supports MBMS, New SGSN also can preserve the MBMS context of UE, otherwise New SGSN abandons the MBMS context, it is not done any processing though perhaps preserve.
504 stages of 704 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 704 stages, New SGSN is by carrying out safety verification and authentication with UE and HLR exchange message to UE.
505 stages of 705 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 705 stages, New SGSN sends the SGSN context acknowledgement message to Old SGSN after finishing security process, and its effect is to confirm that to OldSGSN New SGSN has received all contextual informations about UE.
506 stages of 706 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 706 stages, New SGSN receives the data packet message of hopping that Old SGSN sends, and this message comprises the data that time-out that Old SGSN preserves sends to UE, receive this message after, New SGSN can send to UE with packet in due course.
506 and 507 stages of 707 and 708 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 707 and 708 stages, New SGSN sends to U-GGSN and upgrades the PDP Context request message, and this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.U-GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to NewSGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of U-GGSN, after New SGSN receives this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
509 stages of 709 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 709 stages, utilize prior art to make that by Old SGSN, New SGSN and HLR exchange message the positional information about UE of preserving among the HLR obtains upgrading, delete the UE information of preserving among the Old SGSN simultaneously, send some the permanent subscription information about UE of preserving among the HLR to New SGSN in addition.
510 stages of 710 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 710 stages, New SGSN receives the MBMS notification request message that sends from U-GGSN, and this message is in order to tell New SGSN that described UE has activated the MBMS business, and this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
711 of above-mentioned Fig. 7 is judgment condition, if New SGSN supports MBMS, then New SGSN entered into for 712 stages, otherwise entered into for 721 stages.
511 stages of 712 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 712 stages, because New SGSN supports MBMS, New SGSN sends MBMS notice response message to U-GGSN, and this message comprises parameter: Cause, the Cause parameter comprises some explanations to message itself.
713 of above-mentioned Fig. 7 is judgment condition, if New SGSN comprises the MBMS context in above-mentioned 703 stages from the message that OldSGSN receives, then New SGSN entered into for 714 stages, New SGSN does not comprise the MBMS context in above-mentioned 703 stages from the message that Old SGSN receives else if, and then New SGSN entered into for 719 stages.
516 stages of 714 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 714 stages, New SGSN sends the update MBMS context request message to M-GGSN, and this message comprises parameter: New SGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the M-GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the M-GGSN.
517 stages of 715 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 715 stages, New SGSN receives the update MBMS context response message that sends from M-GGSN, comprises the TEID of parameter: GGSN in this message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the M-GGSN, and Cause represents reason.
522 stages of 716 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 716 stages, New SGSN has approved that UE upgrades reception message to UE at the existence and the transmission RA of new Routing Area.This message comprises parameter: P-TMSI, P-TMSI Signature.These two parameters are that New SGSN distributes to UE as the identity sign in this RA zone.
523 stages of 717 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 717 stages, New SGSN receives from the RA renewal of UE transmission and finishes message that this message is to show that UE confirms newly assigned P-TMSI and P-TMSI Signature.
718 phase table of above-mentioned Fig. 7 are shown in the release of New SGSN in above-mentioned Fig. 5 flow process.
520 stages of 719 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 719 stages, from the SGSN context acknowledge message that Old SGSN sends, there is no the MBMS context owing to what receive in above-mentioned 703 stages, New SGSN sends request MBMS context activation message to UE, this message and above-mentioned Fig. 2 205 in the message of SGSN transmission identical.
521 stages of 720 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 7.In 720 stages, among the action of New SGSN and above-mentioned Fig. 2 in 206 to 214 stages the action of SGSN identical, just in 720, the GGSN that exchanges messages with New SGSN is M-GGSN rather than U-GGSN.
721 stages of above-mentioned Fig. 7 are represented because New SGSN does not support MBMS, after then receiving the message that sends from U-GGSN in above-mentioned 710 stages, New SGSN does not do corresponding or sends error messages to U-GGSN, and error messages comprises parameter: Cause, Cause represents the reason of makeing mistakes.◆ Fig. 8 has described the course of action of node U-GGSN in the flow process of above-mentioned Fig. 5.
507 and 508 stages of 801 and 802 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 801 and 802 stages, U-GGSN receives the renewal PDP Context request message that sends from New SGSN, and this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.U-GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to New SGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of U-GGSN so that after allowing New SGSN receive this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
510 stages of 803 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 803 stages, U-GGSN sends the MBMS notification request message to New SGSN, and this message is in order to tell New SGSN that described UE has activated the MBMS business, and this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
In 511 stages of 804 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8,804 of Fig. 8 is judgment condition simultaneously.If in 804 stages, U-GGSN receives the correct MBMS notice response message that sends from New SGSN, and then U-GGSN entered for 805 stages.If in 804 stages, U-GGSN does not receive that the correct MBMS that sends from New SGSN notifies response message or receives error messages, and then U-GGSN enters the stage 806.
805 releases of expression U-GGSN in Fig. 5 of above-mentioned Fig. 8.
806 of above-mentioned Fig. 8 is judgment condition.If U-GGSN was to use point-to-point PS mode MBMS to be provided business for this UE before 801 stages, then U-GGSN entered for 805 stages.Otherwise U-GGSN entered for 807 stages.
512 stages of 807 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 807 stages, U-GGSN sends deletion MBMS context notification request message to Old SGSN, and this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly U-GGSN requires the contextual reason of OldSGSN deletion MBMS.
513 stages of 808 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 808 stages, U-GGSN receives the deletion MBMS context notice response message that sends from Old SGSN, and this message comprises parameter: Cause, Cause represents reason.
518 stages of 809 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 809 stages, U-GGSN and BM-SC exchange message, U-GGSN adds the multicast service among the BM-SC, and BM-SC carries out authentication to U-GGSN simultaneously.
519 stages of 810 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 8.In 810 stages, U-GGSN sends the point-to-point PS mode of MBMS notification message to UE, and this message comprises parameter: IP multicast address and APN.Its objective is allow UE receive this message after, UE can select according to specific implementation: suspend contextual use of MBMS or deletion MBMS context.
811 releases of expression U-GGSN in above-mentioned Fig. 5 of above-mentioned Fig. 8.
◆ Fig. 9 has described the course of action of node M-GGSN in the flow process of above-mentioned Fig. 5.
901 of above-mentioned Fig. 9 is judgment condition.When the New SGSN among above-mentioned Fig. 5 supported that MBMS is professional, M-GGSN can enter for 902 stages,, otherwise M-GGSN can enter for 906 stages.
902 of above-mentioned Fig. 9 is a judgment condition equally.If when in the SGSN context acknowledge message that the New SGSN among above-mentioned Fig. 5 received in 503 stages the MBMS context being arranged, M-GGSN entered for 903 stages, otherwise M-GGSN entered for 908 stages.
516 stages of 903 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 9.In 903 stages, M-GGSN receives the update MBMS context request message that sends from New SGSN, and this message comprises parameter: NewSGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the M-GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the M-GGSN.
517 stages of 904 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 9.In 904 stages, the parameter that M-GGSN comprised from the update MBMS context request message that New SGSN sends according to above-mentioned 903 stages of receiving, find the MBMS context that will upgrade, and upgrade wherein relevant parameters territory, afterwards, M-GGSN sends the update MBMS context response message to New SGSN, comprises the TEID of parameter: GGSN in sending message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the M-GGSN, and Cause represents reason.
905 releases of expression M-GGSN in Fig. 5 of above-mentioned Fig. 9.
514 stages of 906 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 9.In 906 stages, M-GGSN receives the deletion MBMS context request message that sends from Old SGSN, and this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, Teardown Ind represents to delete designator, if Teardown Ind parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
515 stages of 907 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 9.In 907 stages, M-GGSN finds corresponding M BMS context that it is deleted according to the parameter in the message of receiving in 906, and sends deletion MBMS context acknowledge message to Old SGSN, and this message comprises parameter: TEID, Cause.
521 stages of 908 corresponding above-mentioned Fig. 5 of above-mentioned Fig. 9.In 908 stages, among the action of M-GGSN and above-mentioned Fig. 2 in 208 to 210 stages the action of GGSN identical.
When U-GGSN and M-GGSN are a GGSN, the RA renewal process
◆ Figure 10 has described when U-GGSN and M-GGSN are a GGSN, and UE carries out the flow process of RA renewal process.
Above-mentioned Figure 10 1001 in, when UE enters a new Routing Area, by the Routing Area sign (RAI) in the broadcast message that contrasts sub-district, current place, UE finds own in a new Routing Area, so UE sends the RA update inquiry information to SGSN, this message comprises parameter: P-TMSI, Old RAI, TMGI, Old P-TMSISignature or the like.TMGI wherein is the new argument after the introducing MBMS business, is used to distinguish different MBMS business when UE paging receiving information.
Above-mentioned Figure 10 1002 in, after New SGSN receives message, utilize prior art to derive the address of Old SGSN and send the SGSN context request message to Old SGSN by parameter Old RAI or Old P-TMSI.This message comprises parameter: IMSI, Old RAI etc.
Above-mentioned Figure 10 1003 in, after Old SGSN received the SGSN context request message from New SGSN, SGSN was put into MM context, PDP Context and the MBMS context of UE during message SGSN context replys, and sends to New SGSN.The parameter that UE is carried out mobile management and access preserved in the MM context, and PDP Context is preserved the parameter about the data field connection of UE, and MBMS preserves the parameter about the use MBMS business of UE.
Above-mentioned Figure 10 1004 in, after New SGSN received the SGSN context acknowledge message from Old SGSN, New SGSN was by carrying out safety verification with UE and HLR exchange message to UE.
Above-mentioned Figure 10 1005 in, New SGSN finishes behind the security process and sends the SGSN context acknowledgement message to Old SGSN, its effect is to confirm that to Old SGSN New SGSN has received contextual information.After Old SGSN receives this acknowledge message, be invalid, and after waiting for the regular hour it deleted that the time of wait is depended on realization with the MM context about UE, PDP Context, the MBMS contextual tagging of oneself preserving.
Above-mentioned Figure 10 1006 in, Old SGSN will not reach the packet that sends to UE and will send to New SGSN by message by GTP tunnel, send to UE by New SGSN after the RA process is finished.
Above-mentioned Figure 10 1007 and 1008 in, New SGSN send to upgrade the PDP Context request message to GGSN, this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to New SGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of GGSN, after New SGSN receives this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
Above-mentioned Figure 10 1009 in, this process utilizes prior art to make that by Old SGSN, New SGSN and HLR exchange message the positional information about UE of preserving among the HLR obtains upgrading, delete the UE information of preserving among the Old SGSN simultaneously, send some the permanent subscription information about UE of preserving among the HLR to New SGSN in addition.
Above-mentioned Figure 10 1010 in, GGSN sends the MBMS notification request message to New SGSN, this message is in order to tell New SGSN that described UE has activated the MBMS business, this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
Above-mentioned Figure 10 1011 in, after New SGSN received the message of GGSN transmission, if NewSGSN supports MBMS, then New SGSN sent MBMS notice response message to GGSN, this message comprises parameter: Cause, the Cause parameter comprises some explanations to message itself.If New SGSN does not support MBMS, then New SGSN ignores this message or sends error messages to GGSN.
Above-mentioned Figure 10 1012 in, if GGSN does not receive the MBMS notice response message in described 1011, or GGSN receives error message, then GGSN sends deletion MBMS context notification request message to Old SGSN, this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly GGSN requires the contextual reason of Old SGSN deletion MBMS.
Above-mentioned Figure 10 1013 in, after Old SGSN received the deletion MBMS context notification request message of sending from GGSN, Old SGSN sent deletion MBMS context notice response message to GGSN, this message comprises parameter: Cause, Cause represents reason.
Above-mentioned Figure 10 1014 in, Old SGSN by above-mentioned Figure 10 1012 in the parameter that comprises in the message received find corresponding M BMS context, and send deletion MBMS context request message to GGSN, this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, and TeardownInd represents to delete designator, if the TeardownInd parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
Above-mentioned Figure 10 1015 in, GGSN finds corresponding M BMS context that it is deleted according to the message of sending from Old SGSN in 1014, and sends deletion MBMS context acknowledge message to Old SGSN, this message comprises parameter: TEID, Cause.After Old SGSN receives deletion MBMS context acknowledge message, if Old SGSN finds that oneself has been not empty about the MBMS context of UE and the List of Downstream Nodes parameter in the bearer context among the Old SGSN, promptly do not have descendant node to need to receive the MBMS data again, then Old SGSN initiates the subprocess of deletion MBMS bearer context as shown in figure 15.
Above-mentioned Figure 10 1016 in, if New SGSN supports MBMS, then it is after 1011 the action of finishing above-mentioned Figure 10, New SGSN sends the update MBMS context request message to GGSN, this message comprises parameter: New SGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the GGSN.
Above-mentioned Figure 10 1017 in, when GGSN above-mentioned Figure 10 1016 in receive the update MBMS context request message that sends from New SGSN after, GGSN is according to receiving that the parameter that comprises in the message finds the MBMS context that will upgrade, and upgrade wherein relevant parameters territory, afterwards, GGSN sends the update MBMS context response message to NewSGSN, comprises the TEID of parameter: GGSN in sending message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the GGSN, and Cause represents reason.After New SGSN received the update MBMS context response message, if New SGSN finds oneself also do not have the MBMS bearer context, then New SGSN initiated the subprocess of setting up the MBMS bearer context as shown in figure 14.
Above-mentioned Figure 10 1018 in, when GGSN above-mentioned Figure 10 1010 after do not receive correct response message after, the GGSN supposition should provide MBMS business to UE by existing point-to-point mode, so GGSN and BM-SC exchange message, its objective is that the multicast service while BM-SC in order to allow GGSN add among the BM-SC can carry out authentication to GGSN, after 1018, GGSN adds the multicast service among the BM-SC, just can provide MBMS business to UE by point-to-point mode later.
Above-mentioned Figure 10 1019 in, after 1018 successes of above-mentioned Figure 10, GGSN sends the point-to-point PS mode of MBMS notification message to UE, this message comprises parameter: IP multicast address and APN.After UE received this message, UE can select according to specific implementation: suspend contextual use of MBMS or deletion MBMS context.
Above-mentioned Figure 10 1020 in, if New SGSN supports MBMS, above-mentioned Figure 10 1010 after, after New SGSN knows that UE is to use the UE of MBMS, New SGSN the above-mentioned Figure 10 that receives 1003 in the SGSN context acknowledge message in there is no the MBMS context, then New SGSN sends request MBMS context activation message to UE, this message and above-mentioned Fig. 2 205 in the message of SGSN transmission identical.
Above-mentioned Figure 10 1021 in, UE carry out to activate the MBMS context procedures, 206 to 214 identical among this process and above-mentioned Fig. 2.
Above-mentioned Figure 10 1022 in, New SGSN has approved that UE is in the existence of new Routing Area and send RA and upgrade and receive message to UE.This message comprises parameter: P-TMSI, P-TMSISignature.These two parameters are that New SGSN distributes to UE as the identity sign in this RA zone.
Above-mentioned Figure 10 1023 in, UE receive above-mentioned Figure 10 1022 in after the message that sends from New SGSN, UE confirms the P-TMSI and the P-TMSI Signature that distribute in this message, and sends RA and upgrade and finish message to New SGSN, so far, the RA renewal process finishes.
◆ Figure 11 has described the course of action of node Old SGSN in the flow process of above-mentioned Figure 10.
1002 stages of 1101 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1101 stages, Old SGSN receives the SGSN context request message that sends from New SGSN, and all context message about UE that this message request Old SGSN will preserve send to New SGSN.This message comprises parameter: OldP-TMSI, Old RAI, Old P-TMSI Signature.These parameters are in order to allow 0ld SGSN find corresponding all contextual informations about this UE.
1003 stages of 1102 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1102 stages, after Old SGSN finds all contextual informations of UE of preservation, send the SGSN context acknowledge message to NewSGSN.This message comprises all contextual informations about UE: the MM context, and PDP Context, if UE has activated the MBMS business, this message also comprises the MBMS context.The MBMS context is as shown in table 1.
1005 stages of 1103 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1103 stages, Old SGSN receives the SGSN context acknowledgement message that sends from New SGSN, and this message confirms that to Old SGSN New SGSN has received the contextual information of UE.
In 1006 stages of 1104 corresponding above-mentioned Figure 10 of above-mentioned Figure 11, in 1104 stages, the data that the time-out that Old SGSN will preserve sends to UE send to New SGSN earlier by the data packet message of hopping, and send to UE in due course by New SGSN.
1009 stages of 1105 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1105 stages, Old SGSN and HLR are mutual, upgrade the contextual information about UE, and the Iu about UE is connected between release and the RAN, according to the difference that realizes, after Old SGSN can be chosen in for 1105 stages, deletion again after all contextual informations of deleting UE immediately also can wait a period of time.
1106 of above-mentioned Figure 11 is judgment condition, if the New SGSN in above-mentioned Figure 10 supports MBMS then Old SGSN entered into for 1107 stages, otherwise Old SGSN entered into for 1111 stages.
1012 stages of 1107 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1107 stages, Old SGSN receives the deletion MBMS context notification request message that sends from GGSN, and this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly GGSN requires the contextual reason of OldSGSN deletion MBMS.The purpose in 1107 stages is, if New SGSN does not support MBMS, at this moment should continue to provide MBMS business with point-to-point PS mode to UE, but NewSGSN does not support MBMS, so can not carry out alternately to upgrade the MBMS contextual information of preserving among the GGSN with GGSN, this has just caused the MBMS context of preserving among the GGSN incorrect, so require Old SGSN to go to delete the MBMS context of preserving among the GGSN alternately with GGSN here.
1013 stages of 1108 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1108 stages, Old SGSN sends deletion MBMS context notice response message to GGSN, and this message comprises parameter: Cause, Cause represents reason.
1014 stages of 1109 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1109 stages, Old SGSN finds corresponding M BMS context by the parameter that comprises in the message of receiving in above-mentioned 1107 stages, and sends deletion MBMS context request message to GGSN, and this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, TeardownInd represents to delete designator, if Teardown Ind parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
1015 stages of 1110 corresponding above-mentioned Figure 10 of above-mentioned Figure 11.In 1110 stages, Old SGSN receives the deletion MBMS context acknowledge message that sends from GGSN, and this message comprises parameter: TEID, Cause.Show that GGSN deletes corresponding M BMS context.
1111 phase table of above-mentioned Figure 11 are shown in the release of Old SGSN in Figure 10 flow process.
◆ Figure 12 has described the course of action of node New SGSN in the flow process of above-mentioned Figure 10.
1001 stages of 1201 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1201 stages, New SGSN receives the RA update inquiry information that sends from UE, and this message comprises parameter: P-TMSI, Old RAI, TMGI, Old P-TMSI Signature or the like.TMGI wherein is the new argument after the introducing MBMS business, when paging UE, is used to make UE to distinguish different MBMS business.
1002 stages of 1202 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1202 stages, after New SGSN receives the message of above-mentioned 1201 stage UE, utilize prior art to derive the address of Old SGSN and send the SGSN context request message to Old SGSN by parameter Old RAI or OldP-TMSI.This message comprises parameter: IMSI, Old RAI etc.
1003 stages of 1203 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1203 stages, New SGSN receives the SGSN context acknowledge message that sends from Old SGSN, and this message comprises MM context, PDP Context and the MBMS context of UE.New SGSN can preserve MM context, the PDP Context of the UE that receives in the message.If New SGSN supports MBMS, New SGSN also can preserve the MBMS context of UE, otherwise New SGSN abandons the MBMS context, it is not done any processing though perhaps preserve.
1004 stages of 1204 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1204 stages, New SGSN is by carrying out safety verification and authentication with UE and HLR exchange message to UE.
1005 stages of 1205 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1205 stages, New SGSN sends the SGSN context acknowledgement message to Old SGSN after finishing security process, and its effect is to confirm that to OldSGSN New SGSN has received all contextual informations about UE.
1006 stages of 1206 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1206 stages, New SGSN receives the data packet message of hopping that Old SGSN sends, and this message comprises the data that time-out that Old SGSN preserves sends to UE, receive this message after, New SGSN can send to UE with packet in due course.
1006 and 1007 stages of 1207 and 1208 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1207 and 1208 stages, New SGSN sends to GGSN and upgrades the PDP Context request message, and this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to New SGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of GGSN, after New SGSN receives this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
1009 stages of 1209 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1209 stages, utilize prior art to make that by Old SGSN, New SGSN and HLR exchange message the positional information about UE of preserving among the HLR obtains upgrading, delete the UE information of preserving among the Old SGSN simultaneously, send some the permanent subscription information about UE of preserving among the HLR to New SGSN in addition.
1010 stages of 1210 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1210 stages, New SGSN receives the MBMS notification request message that sends from GGSN, and this message is in order to tell New SGSN that described UE has activated the MBMS business, and this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
1211 of above-mentioned Figure 12 is judgment condition, if New SGSN supports MBMS, then New SGSN entered into for 1212 stages, otherwise entered into for 1221 stages.
1011 stages of 1212 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1212 stages, because New SGSN supports MBMS, New SGSN sends MBMS notice response message to GGSN, and this message comprises parameter: Cause, the Cause parameter comprises some explanations to message itself.
1213 of above-mentioned Figure 12 is judgment condition, if New SGSN comprises the MBMS context in above-mentioned 1203 stages from the message that Old SGSN receives, then New SGSN entered into for 1214 stages, New SGSN does not comprise the MBMS context in above-mentioned 1203 stages from the message that Old SGSN receives else if, and then New SGSN entered into for 1219 stages.
1016 stages of 1214 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1214 stages, New SGSN sends the update MBMS context request message to GGSN, and this message comprises parameter: New SGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the GGSN.
1017 stages of 1215 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1215 stages, New SGSN receives the update MBMS context response message that sends from GGSN, comprises the TEID of parameter: GGSN in this message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the GGSN, and Cause represents reason.
1022 stages of 1216 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1216 stages, New SGSN has approved that UE upgrades reception message to UE at the existence and the transmission RA of new Routing Area.This message comprises parameter: P-TMSI, P-TMSISignature.These two parameters are that New SGSN distributes to UE as the identity sign in this RA zone.
1023 stages of 1217 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1217 stages, New SGSN receives from the RA renewal of UE transmission and finishes message that this message is to show that UE confirms newly assigned P-TMSI and P-TMSI Signature.
1218 phase table of above-mentioned Figure 12 are shown in the release of New SGSN in above-mentioned Figure 10 flow process.
1020 stages of 1219 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1219 stages, from the SGSN context acknowledge message that Old SGSN sends, there is no the MBMS context owing to what receive in above-mentioned 1203 stages, New SGSN sends request MBMS context activation message to UE, this message and above-mentioned Fig. 2 205 in the message of SGSN transmission identical.
1021 stages of 1220 corresponding above-mentioned Figure 10 of above-mentioned Figure 12.In 1220 stages, among the action of New SGSN and above-mentioned Fig. 2 in 206 to 214 stages the action of SGSN identical, just in 1220, the GGSN that exchanges messages with New SGSN is GGSN rather than GGSN.
1221 stages of above-mentioned Figure 12 are represented because New SGSN does not support MBMS, after then receiving the message that sends from GGSN in above-mentioned 1210 stages, New SGSN does not do corresponding or sends error messages to GGSN, and error messages comprises parameter: Cause, Cause represents the reason of makeing mistakes.
◆ Figure 13 has described the course of action of node GGSN in the flow process of above-mentioned Figure 10.
1007 and 1008 stages of 1301 and 1302 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1301 and 1302 stages, U-GGSN receives the renewal PDP Context request message that sends from New SGSN, and this message comprises parameter: New SGSN address, the GTP tunnel address of New SGSN etc.U-GGSN is according to the relevant parameter item in the PDP Context of the preservation of the parameter update oneself in the message of receiving, and to New SGSN transmission renewal PDP Context response message, this message comprises the GTP tunnel address of U-GGSN so that after allowing New SGSN receive this response message, the same relevant parameter item that upgrades in the PDP Context of oneself preserving.
1010 stages of 1303 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1303 stages, U-GGSN sends the MBMS notification request message to New SGSN, and this message is in order to tell New SGSN that described UE has activated the MBMS business, and this message comprises parameter: IP multicast address, APN, NSAPI.Wherein IP multicast address and APN indicate the MBMS business, NSAPI indicates a specific PDP Context, UE sends IGMP by this PDP Context to add message, as shown in Figure 2, the PDP Context of setting up in 201 among the described just Fig. 2 of this specific PDP Context so.
In 1011 stages of 1304 corresponding above-mentioned Figure 10 of above-mentioned Figure 13,1304 of Figure 13 is judgment condition simultaneously.If in 1304 stages, U-GGSN receives the correct MBMS notice response message that sends from New SGSN, and then U-GGSN entered for 1313 stages.If in 1304 stages, U-GGSN does not receive that the correct MBMS that sends from New SGSN notifies response message or receives error messages, and then U-GGSN enters the stage 1305.
1305 of above-mentioned Figure 13 is judgment condition.If U-GGSN was to use point-to-point PS mode MBMS to be provided business for this UE before 1301 stages, then U-GGSN entered for 1316 stages.Otherwise U-GGSN entered for 1306 stages.
1012 stages of 1306 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1306 stages, U-GGSN sends deletion MBMS context notification request message to Old SGSN, and this message comprises parameter: IP multicast address, APN, Linked NSAPI, Cause.IP multicast address and APN indicate a certain MBMS business.Linked NSAPI indicates a certain PDP Context, and this PDP Context is UE is used to send IGMP message when activating the MBMS business a context.Cause represents reason, and promptly U-GGSN requires the contextual reason of OldSGSN deletion MBMS.
1013 stages of 1307 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1307 stages, U-GGSN receives the deletion MBMS context notice response message that sends from Old SGSN, and this message comprises parameter: Cause, Cause represents reason.
1014 stages of 1308 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1308 stages, M-GGSN receives the deletion MBMS context request message that sends from Old SGSN, and this message comprises parameter: TEID, NSAPI, Teardown Ind.TEID and NSAPI indicate the MBMS context that will delete altogether, Teardown Ind represents to delete designator, if Teardown Ind parameter comprised, then this UE of expression deletion all with wait to delete the MBMS context that the MBMS context has identical pdp address.
1015 stages of 1309 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1309 stages, M-GGSN finds corresponding M BMS context that it is deleted according to the parameter in the message of receiving in 1308, and sends deletion MBMS context acknowledge message to Old SGSN, and this message comprises parameter: TEID, Cause.1018 stages of 1310 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1310 stages, U-GGSN and BM-SC exchange message, U-GGSN adds the multicast service among the BM-SC, and BM-SC carries out authentication to U-GGSN simultaneously.
1019 stages of 1311 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1311 stages, U-GGSN sends the point-to-point PS mode of MBMS notification message to UE, and this message comprises parameter: IP multicast address and APN.Its objective is allow UE receive this message after, UE can select according to specific implementation: suspend contextual use of MBMS or deletion MBMS context.
1312 releases of expression GGSN in above-mentioned Figure 10 of above-mentioned Figure 13.
1313 of above-mentioned Figure 13 is a judgment condition equally.If the New in above-mentioned Figure 10
When in the SGSN context acknowledge message that SGSN received in 1003 stages the MBMS context being arranged, M-GGSN entered for 1314 stages, otherwise M-GGSN entered for 1317 stages.
1016 stages of 1314 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1314 stages, M-GGSN receives the update MBMS context request message that sends from New SGSN, and this message comprises parameter: NewSGSN address, data field TEID, NSAPI.The address of New SGSN refers to the pdp address of New SGSN.Control domain TEID in NSAPI and this message header can indicate a MBMS context together.Data field TEID is in order to set up public downlink data tunnel between New SGSN and the M-GGSN, each MBMS business all has a shared downlink data tunnel, at this, during not to the downlink data tunnel of described MBMS business, should comprise data field TEID in this message before between New SGSN and the M-GGSN.
1017 stages of 1315 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1315 stages, the parameter that M-GGSN comprised from the update MBMS context request message that New SGSN sends according to above-mentioned 1314 stages of receiving, find the MBMS context that will upgrade, and upgrade wherein relevant parameters territory, afterwards, M-GGSN sends the update MBMS context response message to New SGSN, comprises the TEID of parameter: GGSN in sending message, Cause.The TEID of GGSN is in order to set up the uplink tunnel between New SGSN and the M-GGSN, and Cause represents reason.
1316 releases of expression GGSN in above-mentioned Figure 10 of above-mentioned Figure 13.
1021 stages of 1317 corresponding above-mentioned Figure 10 of above-mentioned Figure 13.In 1317 stages, among the action of M-GGSN and above-mentioned Fig. 2 in 208 to 210 stages the action of GGSN identical.
◆ Figure 14 has described the subprocess of setting up the MBMS bearer context of being initiated by SGSN
Set up when satisfying the condition of setting up the MBMS bearer context in SGSN, SGSN can initiate to set up the subprocess of MBMS bearer context.Concerning SGSN, satisfy the condition of setting up the MBMS bearer context and comprise:
SGSN successfully set up for certain UE or update MBMS context after, finding oneself does not have the MBMS bearer context, then SGSN initiates to set up the subprocess of MBMS bearer context; Perhaps when the descendant node of SGSN be RNC when SGSN request carrying is set up, SGSN initiates to set up the subprocess of MBMS bearer context.In the present invention, after 516 and 517 of above-mentioned Fig. 5 completed successfully, if New SGSN finds oneself also do not have the MBMS bearer context, then New SGSN initiated to set up the subprocess of MBMS bearer context.In the present invention, after 1016 and 1017 of above-mentioned Figure 10 completed successfully, if New SGSN finds oneself also do not have the MBMS bearer context, then SGSN initiated to set up the subprocess of MBMS bearer context.
Above-mentioned Figure 14 1401 in, when satisfying the condition set up the MBMS bearer context and set up, SGSN sends the MBMS bearing request message to GGSN, this message comprises parameter: IP multicast address, APN, TEID.Its effect of TEID that SGSN distributes is: if session begins, GGSN sends data with this TEID to SGSN.
Above-mentioned Figure 14 1402 in, after GGSN receives the message that SGSN sends in above-mentioned 1401, if the MBMS bearer context has been arranged among the GGSN, then GGSN responds MBMS carrying response message to SGSN, this message comprises parameter: IP multicast address, APN, session attribute (SessionAttributes), TMGI, state (State); If also there is not the MBMS bearer context among the GGSN, then GGSN should require to set up carrying to BM-SC, but this situation and the present invention are irrelevant, so do not do explanation.After SGSN receives this MBMS carrying response message, set up the MBMS bearer context and the parameter of receiving is inserted in this bearer context.Also do not begin if state parameter shows session, then SGSN deletes the TEID that distributes in above-mentioned 1401.
◆ Figure 15 has described the subprocess of the deletion MBMS bearer context of being initiated by SGSN
Set up when the condition that satisfies deletion MBMS bearer context in SGSN, SGSN can initiate to delete the subprocess of MBMS bearer context.Concerning SGSN, the condition that satisfies deletion MBMS bearer context comprises:
SGSN finds that oneself has been not empty about the MBMS context of UE and the List of Downstream Nodes parameter in the bearer context among the SGSN, promptly do not have descendant node to need to receive the MBMS data again, then SGSN initiates the subprocess of deletion MBMS bearer context.In the present invention, after 514 and 515 of above-mentioned Fig. 5 completes successfully, if Old SGSN finds that oneself has been not empty about the MBMS context of UE and the List ofDownstream Nodes parameter in the bearer context among the Old SGSN, promptly do not have descendant node to need to receive the MBMS data again, then Old SGSN initiates the subprocess of deletion MBMS bearer context.In the present invention, after 1014 and 1015 of above-mentioned Figure 10 completes successfully, if Old SGSN finds that oneself has been not empty about the MBMS context of UE and the List of Downstream Nodes parameter in the bearer context among the Old SGSN, promptly do not have descendant node to need to receive the MBMS data again, then Old SGSN initiates the subprocess of deletion MBMS bearer context.
Above-mentioned Figure 15 1501 in, set up when the condition that satisfies deletion MBMS bearer context, SGSN sends MBMS deleting bearing request message to GGSN, this message comprises parameter: IP multicast address, APN.
Above-mentioned Figure 15 1502 in, after GGSN receives the message that SGSN sends in above-mentioned 1501, GGSN deletes the sign of SGSN in the MBMS bearer context of oneself from parameter L ist ofDownstream Nodes, and sends MBMS deleting bearing response message to SGSN.After SGSN receives MBMS deleting bearing response message from GGSN, SGSN deletion MBMS bearer context.
Claims (2)
1. the method for a routing region updating is characterized in that:
" the routing region updating request information is given new SGSN in the UE transmission;
New SGSN sends " SGSN context request " message and gives old SGSN;
Old SGSN sends " the SGSN context is replied " message and gives new SGSN, comprises the MBMS context;
" the update MBMS context request information is given M-GGSN, comprises new SGSN address in new SGSN transmission;
M-GGSN sends " update MBMS context response " message and gives new SGSN;
New SGSN sends " routing region updating acceptance " and gives UE.
2. method according to claim 1 is characterized in that: comprise TEID and NSAPI in the described update MBMS context request, described TEID and NSAPI identify a MBMS context together.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNA031423353A CN1567757A (en) | 2003-06-13 | 2003-06-13 | Method for updating route area using UE of MBMS service in communication system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNA031423353A Division CN1567757A (en) | 2003-06-13 | 2003-06-13 | Method for updating route area using UE of MBMS service in communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101384005A true CN101384005A (en) | 2009-03-11 |
Family
ID=33546192
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNA031423353A Pending CN1567757A (en) | 2003-06-13 | 2003-06-13 | Method for updating route area using UE of MBMS service in communication system |
CNA2008101687203A Pending CN101384005A (en) | 2003-06-13 | 2003-06-13 | Method for routing region updating using UE of MBMS service in communication system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNA031423353A Pending CN1567757A (en) | 2003-06-13 | 2003-06-13 | Method for updating route area using UE of MBMS service in communication system |
Country Status (2)
Country | Link |
---|---|
CN (2) | CN1567757A (en) |
WO (1) | WO2004112328A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102076051A (en) * | 2009-11-20 | 2011-05-25 | 中国移动通信集团广东有限公司 | Method for updating routing areas and SGSN (Serving GPRS (General Packet Radio Service) Support Node) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1697394A (en) * | 2004-05-12 | 2005-11-16 | 华为技术有限公司 | Method for updating routing area in operation of multimedia broadcast/multicast service |
US8428553B2 (en) * | 2005-01-24 | 2013-04-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for protecting a core network |
WO2007025479A1 (en) * | 2005-08-31 | 2007-03-08 | Huawei Technologies Co., Ltd. | A method and communication system for providing multicast service to roaming user |
CN100473216C (en) * | 2006-04-03 | 2009-03-25 | 中兴通讯股份有限公司 | Route renewing method in mobile communication system |
CN101064676B (en) * | 2006-04-29 | 2010-09-22 | 摩托罗拉公司 | Method and system for establishing point-to-multipoint communication environment |
DE602007009215D1 (en) | 2006-05-18 | 2010-10-28 | Huawei Tech Co Ltd | METHOD AND SYSTEM FOR USING A UE IN THE REPLACEMENT MODE WHEN LOGING OUT OF A NETWORK |
EP2081396B1 (en) | 2006-11-03 | 2012-12-12 | Huawei Technologies Co., Ltd. | Mobile communication method and access entity |
CN101267593B (en) * | 2007-03-15 | 2011-04-20 | 华为技术有限公司 | Method and base station for activating multicast and broadcast multimedia service in target cells |
CN101296175B (en) * | 2007-04-25 | 2011-04-20 | 华为技术有限公司 | Method and device for implementing bearing association in multicast broadcasting service |
CN101394577B (en) * | 2007-09-21 | 2012-02-01 | 华为技术有限公司 | Establishing method of multicast broadcast multimedia service user plane transmission path |
CN101594608B (en) * | 2008-05-30 | 2012-08-22 | 华为技术有限公司 | Method for providing security context, mobile management network element and mobile communication system |
CN102821382B (en) | 2008-06-18 | 2015-09-23 | 上海华为技术有限公司 | A kind of device for accessing |
US9066354B2 (en) * | 2008-09-26 | 2015-06-23 | Haipeng Jin | Synchronizing bearer context |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020104801A1 (en) * | 1998-04-06 | 2002-08-08 | Nicolas Voute | Small dense microporous solid support materials, their preparation,and use for purification of large macromolecules and bioparticles |
US20030119452A1 (en) * | 2001-10-19 | 2003-06-26 | Samsung Electronics Co., Ltd. | Apparatus and method for controlling transmission power of downlink data channel in a mobile communication system supporting MBMS |
KR100464351B1 (en) * | 2001-10-20 | 2005-01-03 | 삼성전자주식회사 | Apparatus and method for paging scheme with additional carrie for multimedia broadcasting and multicasting service in w-cdma communication system |
KR100713435B1 (en) * | 2002-05-03 | 2007-05-07 | 삼성전자주식회사 | Apparatus for supporting multi data rate in mobile communication system and method thereof |
-
2003
- 2003-06-13 CN CNA031423353A patent/CN1567757A/en active Pending
- 2003-06-13 CN CNA2008101687203A patent/CN101384005A/en active Pending
-
2004
- 2004-06-12 WO PCT/KR2004/001406 patent/WO2004112328A1/en unknown
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102076051A (en) * | 2009-11-20 | 2011-05-25 | 中国移动通信集团广东有限公司 | Method for updating routing areas and SGSN (Serving GPRS (General Packet Radio Service) Support Node) |
Also Published As
Publication number | Publication date |
---|---|
WO2004112328A1 (en) | 2004-12-23 |
CN1567757A (en) | 2005-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100584449B1 (en) | Method for management service context in order to paging user equipment on idle mode in multimedia broadcast/multicast service | |
US8165053B2 (en) | Method for supporting MBMS service transmission in LTE system | |
US7493108B2 (en) | Provision of a multimedia broadcast/multicast service (MBMS) for a user equipment moving along cells in a cellular mobile communication system | |
KR100827136B1 (en) | Method for signaling connection assignment in a mobile communication system | |
CN1592167B (en) | Method for supporting MBMS backward compatibility | |
US20070014291A1 (en) | Method for multimedia broadcast/multicast service registration | |
WO2008110097A1 (en) | Method and base station for activating multicasting broadcast multimedia service of target community | |
KR20040061705A (en) | Method for transmitting the paging message of multimedia broadcast/multicast service in mobile communication system | |
CN101384005A (en) | Method for routing region updating using UE of MBMS service in communication system | |
CN100502358C (en) | Method for establishing GTP tunnel in multimedia broadcast/multicast service | |
JP2006081173A (en) | Deactivation method of multimedia broadcast multicast service and related device | |
CN102395110B (en) | Method for supporting MBMS service transmission in LTE system | |
WO2004073272A1 (en) | Method for effectively updating mbms service parameters in ggsn, sgsn and rnc | |
CN101742415A (en) | Method for supporting multimedia broadcast/multicast service (MBMS) under shared network architecture | |
CN101112020A (en) | Method and system for transmitting/receiving session non-interest indication information of ue in a multimedia broadcast/multicast service system | |
CN101227307A (en) | Equipment, system and method for processing multimedia broadcast multicast business | |
KR100690439B1 (en) | Method for simplification of the service activation or deactivation in mbms system | |
CN100428860C (en) | Multimedia broadcast/multicast service linking method | |
WO2004034655A1 (en) | A method of establishing and deleting mbms service in sgsn and ggsn | |
CN101102592B (en) | A method for implementing terminal access to multicast service group in mobile communication system | |
CN101232701B (en) | Equipment and method for activating broadcast multicast business | |
KR20050100859A (en) | Method for management service context in order to paging user equipment with cs service in multimedia broadcast/multicast service | |
CN100464530C (en) | Method for announcing group-playing dialogue begin of multimedia broadcasting | |
KR20040096750A (en) | Method for creating/managing service context for multimedia broadcast/multicast service in mobile communication system | |
CN100464591C (en) | Method for realizing multimedia broadcasting/group broadcasting service conversation range control |
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 |
Application publication date: 20090311 |