The application require on February 9th, 2007 submit that Patent Office of the People's Republic of China, application number are 200710079050.3 to, denomination of invention is the priority of the Chinese patent application of " method and system of mobile terminal to enter from free status to activated status ".
Background technology
In order to guarantee the competitiveness of third generation affiliate tissue (3GPP, 3rd Generation PartnershipProject) system, need carry out evolution to the access technology of existing 3GPP definition.Fig. 1 is evolution system-System Architecture Evolution (SAE of 3GPP, System ArchitectureEvolution) Organization Chart of system, as shown in Figure 1, the core net of SAE system mainly comprises: mobile management entity (MME, Mobility Management Entity), three logic function bodies of user's face anchor point (Inter AS Anchor) between user entity (UPE, User Plane Entity), different access systems.Wherein, the mobile management that MME is responsible for chain of command comprises: user's context and mobile status management, distributing user temporary identity sign, safety function etc., it is corresponding to current conventional wireless communication systems (UMTS, Universal MobileTelecommunication System) internal services GPRS (GPRS, General Packet Radio Service) the control plane part of support node (SGSN, Service GPRS SupportNode); UPE is responsible for initiating paging for downlink data under the idle condition, and IP bearing parameter and the interior routing iinformation of network etc. are preserved in management, and it is corresponding to the datum plane part of current UMTS internal system SGSN; Inter AS Anchor then serves as the user's face anchor point between different access systems.The datum plane part of gateway GRPS support node (GGSN, Gateway GRPS SupportNode) may be positioned at UPE, also may be positioned at Inter AS Anchor.
At Wideband Code Division Multiple Access (WCDMA) (WCDMA, Wideband Code Division MultipleAddress) in the system, the state of mobile management (MM, Mobility Management) is divided into attachment removal (PMM-DETACHED) attitude, free time (PMM-IDLE) attitude and is connected three kinds of states of (PMM-CONNECTED) attitude.Fig. 2 has provided the MM state transitions schematic diagram in the WCDMA system, and as shown in Figure 2, the attachment removal attitude is that the mobile subscriber does not have attach to network state before; Behind mobile subscriber's success attach to network, if no signaling connects between mobile subscriber and the network, then the mobile subscriber is in Idle state, connects if having signaling between mobile subscriber and the network, and then the mobile subscriber is in connected state, and connected state is also referred to as activated state.
In the 3GPP system, when the user who is in Idle state need send up signaling or data, perhaps, when core net owing to will send downlink signaling or data when paging is in the mobile subscriber of Idle state, the mobile subscriber will initiate the foundation of service request (Service Request) flow process and be connected with the signaling of network side, if need to pass data, also to further finish the recovery of IP carrying, promptly rebuild the empty port load-supporting between mobile subscriber and the Access Network and recover user's face tunnel between Access Network and the core net.Above-mentioned two processes are called the service request flow process of mobile subscriber's initiation and the service request flow process that network is initiated.
Fig. 3 is in the 3GPP system, the service request information flow process sequential chart that portable terminal (MS, Mobile Station) is initiated, and as shown in Figure 3, its concrete steps are as follows:
Step 301: be in the MS of Idle state and radio network controller (RNC, RadioNetwork Controller) and be connected with RRC by mutual Radio Resource control (RRC, Radio ResourceControl) connection request and set up message, set up the RRC connection.
Step 302:MS sends service request information to SGSN, and this message is carried cells such as MS temporary identity sign (PTMSI), service request type.
The service request type value can be signaling or data, and when being signaling, expression MS will send up signaling; When being data, expression MS wants restore data to transmit.
Step 303:SGSN receives service request information, carries out safety function, and MS is carried out safety certification, simultaneously newly-established signaling is connected to start and encrypts and integrity protection.
Step 304:SGSN judges that the service request type value is data or signaling, if data, execution in step 305; If signaling, execution in step 311.
Step 305:SGSN returns service to MS and accepts (Service Accept) message.
Step 306:SGSN sends RAB (RAB, Radio AccessBearer) assignment request message to RNC, and order RNC eats dishes without rice or wine for all bearer reconstructions that need recover and the RAB carrying.
Step 307:RNC sends radio bearer to MS and sets up message, and MS sets up empty port load-supporting with notice.
After step 308:MS receives that this radio bearer is set up message, return radio bearer foundation to RNC and finish message, this message is carried newly-established empty port load-supporting sign (RB ID) and corresponding RAB ID.
Step 309:RNC is newly-built RAB Resources allocation, return RAB assignment response message to SGSN, this message comprises the service quality (QoS, Quality ofService) of the carrying of foundation, user's face IP address and the Tunnel End Point Identifier (TEID, TunnelEndpoint Identifier) of RNC.
Step 310:SGSN receives RAB assignment response message, detect qos value that this message carries and the packet data protocol (PDP of the MS of self, Packet Data Protocol) the qos value difference in the context, then qos value notice GGSN and the MS that this RAB assignment response message is carried by PDP context modification message.
Step 311:MS begins to send up signaling or data.
The service request information flow process sequential chart that Fig. 4 initiates for network side, as shown in Figure 4, its concrete steps are as follows:
Step 401:SGSN receives downlink signaling or data, and detects corresponding MS and be in Idle state.
Step 402:SGSN sends beep-page message to RNC, after RNC receives this beep-page message, initiates paging to MS.
Step 403:MS receives this beep-page message, detect self with RNC between also do not have RRC to be connected, then set up message by being connected with RRC with the mutual RRC connection request of RNC, set up with RNC between RRC be connected.
Step 404:MS sends service request information to SGSN, and this message is carried the PTMSI of MS, and the service request type value is a page response.
Step 405:SGSN carries out safety function, and MS is carried out safety certification, simultaneously newly-established signaling is connected to start and encrypts and integrity protection.
Step 406:SGSN judges will send downlink signaling or downlink data to MS, if signaling, execution in step 412; If data, execution in step 407.
Step 407:SGSN sends the RAB assignment request message to RNC.
Step 408~411 are identical with step 307~310.
Step 412:SGSN issues downlink signaling or data.
When MS enters into activated state from Idle state, RAN comprises above-mentioned signaling connection and user plane bearer information just for this MS has set up user's context in this user's context.In addition, also need comprise out of Memory in the user's context, as: security parameter, promptly be used for the key that the RRC connection is encrypted and integrality comprises, for another example: user's permanent identification (IMSI, International Mobile Subscriber Identifier), and the MM information that RAN need know for example: at present in the 3GPP system, share the demand of RAN owing to will support multi-operator, need SGSN that some user networks are selected in the WCDMA system or the policy distribution of roaming restriction is given RAN, so that by access selection and the network selecting of MS under the concrete control connection state of RAN.When MS when Idle state has just entered activated state, RAN does not comprise above-mentioned information in the newly-established user's context of MS, need SGSN with above-mentioned information by specific I u interface signaling message as: COMMON ID is handed down to RNC.In addition, when above-mentioned information changed, SGSN also needed to notify RNC.
In the WCDMA system, core net is mutual by different flow processs at present, and the information that RAN is needed is handed down to RAN.For example: SGSN with user plane bearer information notice RNC, finishes empty port load-supporting reconstruction and RAB reconstruction by RNC by the RAB assignment procedure among Fig. 3; Be handed down to RNC by the MM information that needs in the user's context of Common ID message with RNC.Though with different levels flexibly mutual, make MS long from the signaling time delay that Idle state enters into activated state.For improving user's service impression, accelerating MS is an important need of SAE system from the speed that Idle state enters into activated state.
In addition, in the SAE system, increase the notion of the maximum bearer rate (AMBR, Aggregated Maximum Bearer Rate) of polymerization newly, be the signatory total MBR parameter of each MS.The non-assurance bearer rate of all of MS (GBR, Guarantee BearerRate) business all no longer needs independent MBR parameter, the professional shared total AMBR parameter of the non-GBR of all of same MS, that is: the non-GBR business of all of a MS has a total bandwidth constraints.Obviously.Whenever MS when Idle state enters into activated state, this AMBR parameter all need be handed down to RAN by core net, so that RAN uses this parameter to implement maximum bandwidth limit to all non-GBR business of MS, avoids CU to cross multi-system resource.Specifically how this AMBR parameter is handed down to RAN, prior art does not provide solution.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
In the SAE system, the definition of Idle state is similarly: no signaling connects between MS and the network.Specifically refer to, do not set up between MS and the Access Network and eat dishes without rice or wine to connect, do not connect and also set up the S1 interface signaling between Access Network and the core net.For saving access network resource, Access Network can not keep user's context for the MS that is in Idle state, and core net still remains with user's context for the MS that is in Idle state, returns to activated state to make things convenient for MS from Idle state, and then the restore data transport service.Otherwise, under the activated state, set up between MS and the Access Network and eated dishes without rice or wine to connect, connect and also have the S1 interface signaling between Access Network and the core net.Preserved user's context on the Access Network, but this moment, not necessarily there was data transmission activity in MS, may have only signaling transmission activity.
Fig. 5 has provided the Idle state of MS in the SAE system and the conversion schematic diagram of activated state, and as shown in Figure 5, the MS that is in Idle state initiates the signaling connection and sets up process, enters activated state; The MS that is in activated state connects dispose procedure by signaling, gets back to Idle state.The MS that is in Idle state can further enter into the attachment removal state by the attachment removal flow process.
With the 3GPP system class seemingly, the SAE system needs the flow process of similar service request to realize that MS enters activated state from Idle state equally.For simplicity, the present invention continues to continue to use the abbreviation in the 3GPP system, will realize in the SAE system that MS is called the service request flow process from the flow process that Idle state enters activated state.
Fig. 6 for the embodiment of the invention one provide in the SAE system, the message flow sequential chart of the service request that MS initiates, as shown in Figure 6, its concrete steps are as follows:
Step 601: the MS that is in Idle state is connected with RRC by the RRC connection request and sets up message, and sets up RRC between the RAN of SAE system and is connected.
The MME of step 602:MS in the core net of SAE system sends service request information, and the service request type value in this message is signaling or data.
Step 603: core net MME carries out safety function, finishes the safety certification to MS.
Step 604: core net MME sends safe mode command to RAN, and the RRC that is used for that carries in this order that core net MME and MS consult is connected and encrypts and the key of integrity protection.
Step 605:RAN receives safe mode command, sends the RRC safe mode command to MS, and startup is encrypted and the algorithm and the parameter of integrity protection to consult with MS.
Step 606:MS receives the RRC safe mode command, returns the RRC safe mode to RAN and finishes message.
Step 607:RAN receives that the RRC safe mode finishes message, returns safe mode to core net MME and finishes message.
Whether step 603 and step 604~607 can carry out according to the configuration decision of SAE system.
Step 608: core net MME sends context to RAN and sets up request message, and this message comprises user context information.
Particularly, user context information can comprise: IMSI; MM information, for example: need the roaming restriction strategy of the MS that RAN uses and network selecting strategy as: allow or PLMN tabulation that restriction MS selects; The AMBR parameter of MS; The user plane information of the carrying that need set up for MS, for example: the corresponding tunnel of the QoS of bearing identification, load bearing requirements, carrying the parameter of core-network side as: with GRPS tunnel protocol (GTP, GRPS TunnelingProtocol) tunnel is an example, refers to corresponding RAN of carrying and the GTP tunnel between core net IP address and the TEID in core-network side.
Step 609:RAN receives that context sets up request message, preserves the user context information that comprises in this message, and is the user plane information of the MS carrying of setting up according to the needs in this user context information, initiates the loading establishing process of eating dishes without rice or wine to MS.
Step 610:RAN returns context foundation to core net MME and finishes message, this message comprises the result that core net requires the carrying foundation of foundation, RAN is user's face resource information that the carrying of described foundation distributes, with the GTP tunnel is example, is exactly corresponding Access Network of carrying and the GTP tunnel between core net IP address and the TEID in the Access Network side.
Step 611: core net MME receives that context is set up and finishes message, send renewal session context request message to core net UPE, this message is carried carrying and is set up relevant information, comprise: RAN is new user's face resource information of setting up the carrying distribution, with the GTP tunnel is example, is exactly corresponding RAN of carrying and the GTP tunnel between core net IP address and the TEID in the RAN side.
After step 612: core net UPE receives and upgrades the session context request message, return renewal session context response message to core net MME.
Step 613:MS sends upstream data or connects the up signaling of transmission by the signaling of setting up by the carrying of foundation.
Step 613 does not require and must carry out that when MS need send upstream data, step 613 also can be finished empty port load-supporting foundation back execution at the MS and the Access Network of step 609 after step 612; When MS need send up signaling, step 613 also can finish the back and carry out in the safety mode process of step 607.
When the signaling transfer protocol stack of the employing of the interface between core net MME and the core net UPE can guarantee the reliable transmission of signaling message, step 612 can be omitted.
Need to prove, among the embodiment provided by the invention, core net MME sends context to RAN and sets up request message, be not to mean that requirement RAN is after receiving this message, just set up user's context, in fact, RAN can be before carrying out safety mode process promptly: just can set up user's context for MS before the step 604, after receiving that core net MME sends context and sets up request message, the user context information that comprises in this message is saved in the described user's context of having set up gets final product again.In addition, about user's IMSI, core net MME can send to RAN immediately after obtaining user's IMSI, and does not require that must set up request message by context passes to RAN.
In actual applications, also process can be set up in safety mode process and context and merge,, accelerate MS enters activated state from Idle state speed with further minimizing Signalling exchange.
The message flow sequential chart that the MS that Fig. 7 provides for the embodiment of the invention two initiates service request, as shown in Figure 7, its concrete steps are as follows:
Step 701~703 are identical with step 601~603.
Step 704: core net MME sends context to RAN and sets up request message, and this message comprises user context information and safe mode parameter.
Particularly, the safe mode parameter comprises: the key that is used for RRC encryption and integrity protection.User context information is identical with step 608.
Step 705:RAN receives that context sets up request message, preserves the information that this message is carried, and is the user plane information of the MS carrying of setting up according to the needs in this message, initiates the loading establishing process of eating dishes without rice or wine to MS; RAN initiates the RRC safety mode process to MS simultaneously.
RAN is identical with step 605 shown in Figure 6~606 with safety mode process between the MS.
Step 706:RAN returns context foundation to core net MME and finishes message, and this message is carried the result of RAN and the negotiation of MS safe mode, the result that core net requires the carrying of foundation to set up, and RAN is user's face resource information of the carrying distribution of described foundation.
Step 707: core net MME receives that context is set up and finish message that send to core net UPE and upgrade the session context request message, this message is carried carrying and set up relevant information, comprising: RAN sets up user's face resource information that carrying distributes for new.
After step 708: core net UPE receives and upgrades the session context request message, return renewal session context response message to core net MME.
Step 709:MS sends upstream data or connects the up signaling of transmission by the signaling of setting up by the carrying of foundation.
Step 709 does not require and must carry out that when MS need send upstream data, step 709 also can be finished empty port load-supporting foundation back execution at the MS and the Access Network of step 705 after step 708; When MS need send up signaling, step 709 also can finish the back and carry out in the safety mode process of step 705.
In the SAE system, the time delay expense for the negotiation of avoiding QoS brings does not alternately allow the negotiation of QoS, i.e. RAN or accept the QoS that core net requires, or refusal.Therefore, RAN can be when the transmission service request be to core net MME, just distribute user's face resource for the carrying that needs to set up, with the GTP tunnel is example, user's face resource refers to the corresponding Access Network of carrying and the GTP tunnel between core net IP address and the TEID in the Access Network side, and the service request that the user resources information of same MS that will distribute sends is uploaded to core net MME together.Like this, core net MME just can directly be notified to core net UPE with this user's face resource information, thereby need not to wait for that RAN returns context foundation to core net MME and finishes message, thereby can further reduce the Signalling exchange in the service request flow process.
RAN will be with regard to distributing user face resource when receiving the service request of MS, and then RAN must learn the carrying that needs foundation.The embodiment of the invention provides two kinds of implementations:
Scheme one, MS are when activated state enters Idle state, still preserve the empty port load-supporting relevant parameter of having set up, so that after MS initiates service request, just finish the reconstruction of empty port load-supporting with RAN, that is: the initial wireless access phase that is based upon MS of empty port load-supporting is just finished, as following embodiment illustrated in fig. 8 three.
Scheme two, MS carry the bearing identification that needs foundation in service request information, as following embodiment illustrated in fig. 9 four.
The message flow sequential chart of the service request that the MS that Fig. 8 provides for the embodiment of the invention three initiates, as shown in Figure 8, its concrete steps are as follows:
Step 801:MS enters Idle state from connected state, preserves the empty port load-supporting relevant parameter.
Step 802: the MS that is in Idle state sends RRC connection request message to RAN, and this message is carried the empty port load-supporting relevant parameter that self preserves.
Step 803:RAN receives this RRC connection request message, and according to the empty port load-supporting relevant parameter that this message is carried, the empty port load-supporting between foundation and the MS returns the RRC connection to MS and sets up message.
Step 804:MS sends service request information to RAN, and the service request type value in this message is signaling or data.
Step 805:RAN receives service request information, judges that the service request type value that this message is carried is signaling or data, if signaling directly is transmitted to core net MME with this service request information, goes to step 806; Otherwise, determine to need to set up carrying, be the carrying distributing user face resource of needs foundation, this user's face resource information is carried at sends to core net MME in the service request information, execution in step 806.
Step 806~810 are identical with step 603~607.
Step 811: core net MME sends context to RAN and sets up request message, and this message comprises user context information; Core net MME sends to core net UPE and upgrades context request message simultaneously, and this message is carried carrying and set up relevant information, comprising: RAN is the new user's face resource information that carrying distributes of setting up; RAN receives that context sets up request message, preserves the user context information that this message is carried, and returns context to core net MME and sets up and finish message, and this message comprises the result that carrying that core net requires to set up is set up; After core net UPE receives and upgrades the session context request message, return renewal session context response message to core net MME.
User context information in this step is identical with step 608.
Context foundation in this step is finished message and can be omitted.
Step 812:MS sends upstream data or connects the up signaling of transmission by the signaling of setting up by the carrying of foundation.
Step 812 does not require and must carry out that when MS need send upstream data, step 812 also can be finished empty port load-supporting foundation execution later at MS and RAN, perhaps carries out after the safety mode process of step 810 finishes after step 811; If MS will send up signaling, carry out after then also can finishing in the safety mode process of step 810.
The message flow sequential chart that the MS that Fig. 9 provides for the embodiment of the invention four initiates service request, as shown in Figure 9, its concrete steps are as follows:
Step 901: the MS that is in Idle state is connected with RRC by the RRC connection request and sets up message, sets up RRC with RAN and is connected.
Step 902:MS sends service request information to RAN, and the service request type value in this message is signaling or data, if data, then this message is further carried the sign of the carrying that needs foundation.
Step 903:RAN receives service request information, detects the sign that this message is carried the carrying of need setting up, and the carrying distributing user face resource for needing to set up then is carried at user's face resource information of this distribution and sends to core net MME in the service request information.
With the GTP tunnel is example, and user's face resource refers to the RAN of the carrying correspondence of need setting up and the GTP tunnel between core net IP address and the TEID in the RAN side.
Step 904~908 are identical with step 603~607.
Step 909: core net MME sends context to RAN and sets up request message, and this message comprises user context information; Send to core net UPE simultaneously and upgrade context request message, this message is carried carrying and set up relevant information, comprising: RAN is the new user's face resource information that carrying distributes of setting up.
User context information in this step is identical with step 608.
Step 910:RAN receives that context sets up request message, preserves the user context information that comprises in this message, and is the user plane information of the MS carrying of setting up according to the needs in this user context information, initiates the loading establishing process of eating dishes without rice or wine to MS.
Step 911:RAN returns context foundation to core net MME and finishes message, and this message comprises the result that core net requires the carrying foundation of foundation; Core net UPE returns the renewal context response information to core net MME.
Step 912:MS sends upstream data or connects the up signaling of transmission by the signaling of setting up by the carrying of foundation.
Step 912 does not require and must carry out that when MS need send upstream data, step 912 also can be finished empty port load-supporting foundation execution later at the MS and the RAN of step 910 after step 911; If MS will send up signaling, then step 912 is carried out after also can finishing in the safety mode process of step 908.
Below provide the service request flow process that network side is initiated.
The message flow sequential chart of the service request that the network side that Figure 10 provides for the embodiment of the invention is initiated, as shown in figure 10, its concrete steps are as follows:
Step 1001: the UPE of core net receives downlink data, find that corresponding carrying is unavailable, be that tunnel between core net and the Access Network discharges in the resource of Access Network side, then core net UPE sends carrying to core net MME and sets up request message, and this message is carried the sign of the MS that downlink data will mail to or the sign that downlink data sends needed carrying.
Step 1002: core net MME receives that carrying sets up request message, finds that the MS that MS sign that this message carries or downlink data send needed bearing identification correspondence is in Idle state, and then to the RAN issuing page message, this message is carried the MS sign.
After step 1003:RAN received this beep-page message, the corresponding MS of MS sign that carries to this message sent beep-page message
Step 1004:MS receives that beep-page message is connected with RRC by the RRC connection request and sets up message, sets up RRC with RAN and be connected.
Step 1005:MS sends service request information to core net MME, and the service request type value in this message is a page response.
Step 1006~1015 are identical with step 603~612.
Step 1016: core net UPE issues downlink data by newly-established carrying.
Need to prove, easy for describing, among the embodiment provided by the invention, all be independent at the MME in the core net and situation UPE and Anchor unification is described, but other position grouping of not getting rid of the above-mentioned logic entity of core net, for example: MME and UPE unification, Anchor is independent; Perhaps MME, UPE and Anchor three unification, perhaps the three all separates.When MME and UPE unification, becoming alternately between MME and the UPE is inner mutual.And Anchor does not participate in the signalling interactive process in the foregoing description according to its functional definition, so the position of Anchor does not influence applicability of the present invention.
Figure 11 enters the system of activated state for the realization MS that the embodiment of the invention provides from Idle state, and as shown in figure 11, it mainly comprises: MS111, RAN112 and core net MME113, wherein,
MS111: determine that self will enter activated state from Idle state, set up RRC, send service request to RAN112 with RAN112.
MS111 preserves the empty port load-supporting relevant parameter of having set up further when activated state enters Idle state, and this empty port load-supporting relevant parameter is sent to RAN112 with described service request.
Perhaps, the sign of the carrying that further will set up of MS111 is carried in the service request.
RAN112: receive the service request that MS111 sends, this service request is sent to core net MME113, the user context information that core net MME113 is sent is kept in the user's context of MS.
The empty port load-supporting relevant parameter that RAN112 further sends according to MS111 is set up empty port load-supporting with MS111, and the carrying distributing user face resource for needing to set up, and this user's face resource information is carried at sends to core net MME113 in the service request.
Perhaps RAN112 is further, the sign of the carrying that the need that carry in the service request of sending according to MS111 are set up, carrying distributing user face resource for need foundation, this user's face resource information is carried in the service request, the user plane information of sending according to core net MME113, set up empty port load-supporting with MS111
Core net MME113: receive the service request that RAN112 sends, the user context information of MS correspondence is sent to RAN112.
Core net MME113 further will need to be carried in the user context information for the user plane information of the carrying of MS111 foundation.
The service request that core net MME113 further sends according to RAN112 is with the mutual safety mode process of carrying out MS of RAN112.
Further, this system comprises: HSS115 is used for alternately MS being carried out with core net MME113 the relevant parameter of safe mode;
Accordingly, the service request that core net MME113 further sends according to RAN112 is with RAN112 and the mutual safety mode process of carrying out MS of HSS115.
Further, this system comprises: core net UPE114: be used to receive user's face resource information of the MS that core net MME113 sends, and return to core net MME113 and to confirm to receive response;
Accordingly, core net MME113 is further, and the user plane information of the carrying that need set up for MS is carried at and sends to RAN112 in the user context information, and user's face resource information that RAN112 is sent sends to core net UPE114,
Simultaneously, the user plane information that RAN112 further sends according to core net MME113 is set up empty port load-supporting with MS111, and user's face resource information of the carrying that will set up for MS sends to core net MME113.
Figure 12 enters the core net MME of activated state for the realization MS that the embodiment of the invention provides from Idle state, and as shown in figure 12, it mainly comprises: service request receiver module 1131 and user context information sending module 1132, wherein:
Service request receiver module 1131: after receiving the service request of carrying the MS sign that RAN112 sends, send the indication that begins of carrying the MS sign to user context information sending module 1132.
User context information sending module 1132: receive that service request receiver module 1131 sends begin indication after, send the user context information of MS to RAN112.
Further, core net MME131 comprises: user's face resource information transceiver module: user's face resource information of the carrying of setting up for MS111 that RAN112 is sent sends to core net UPE114.
Further, core net MME131 comprises: security authentication module: receive the indication that begins that service request receiver module 1131 sends, MS111 is carried out safety function.
Further, core net MME131 comprises: the safe mode Executive Module: receive the indication that begins that service request receiver module 1131 sends, carry out safety mode process with MS111 and RAN112.
Enter the process of activated state for MS from Idle state, not only be confined to these above-mentioned embodiment.For accelerating MS enters activated state fast from Idle state speed, RAN receives service request information, can be defaulted as the direct distributing user face of default bearer resource, or by setting in advance, judge need be for the default bearer Resources allocation after, RAN distributing user face resource, thus the speed that MS enters activated state accelerated.
The reason that has default bearer is because in the 3GPP system before evolvement network, the contextual activation of attaching process and packet data protocol PDP (Packet Data Protocol) is two separating process.After start, MS at first can carry out a GPRS attaching process, wherein mainly comprises security process and position and upgrades.Adhere to finish after, MS does not obtain IP simultaneously and connects, and has only MS to initiate pdp context activation again one time, MS just can be assigned with an IP address and corresponding configuration parameters.That is to say that MS must finish one time pdp context activation earlier before carrying out business, cause MS to transfer the long time delay of data transmission state needs to like this, obviously be not inconsistent with the requirement of evolvement network from Idle state.
For reducing MS enters into data transmission state from idle condition reaction time, standard proposes the SAE/LTE system and network registry and default IP carrying are set up to combine finishes, be in the MS first attached network development process, network is just distributed to IP of MS and part corresponding bearer resource.Realize the always online of MS thus, so that MS is when need carry out data service, network can be faster, more fast provides service.Just need set up a default IP carrying when in brief, the MS in the evolvement network carries out network attachment.The data stream filters of default bearer is defined as general coupling (Match All), that is to say, will send when core net UPE side has downstream data flow, but can not find corresponding carrying can use the time, just can use the default bearer transmission.
When also 13 detailed descriptions are for default bearer distributing user face resource in conjunction with the accompanying drawings below by embodiment five, the implementation procedure of MS from the Idle state to the activated state.Referring to Figure 13,
Setting up RRC between step 1301:MS and the RAN is connected;
The MS that is in Idle state is connected with RRC by RRC connection request message and sets up message, and sets up RRC between the RAN and is connected.
Step 1302:MS sends service request information by the MME of RAN in core net;
In the service request information of MS by the MME transmission of RAN in core net, carry cells such as service request type, the service request type value can be signaling, data or page response; Can add in service request information also further perhaps that to require Access Network be the specific identifier that default bearer is allocated resource in advance;
RAN is receiving service request information and is being forwarded to MME, distributing user face resource simultaneously, and the information of distributing user face resource joined in the service request information together transmit.When distributing user face resource, RAN can be defaulted as the direct distributing user face of default bearer resource; In addition, also can require RAN to judge whether to be default bearer distributing user face resource by setting in advance by the type of service request, if, reallocation user face resource.For example: when RAN judges that service request type is signaling or page response, be default bearer distributing user face resource; Or utilize in the described service request information specific identifier to judge in the time of need allocating resource in advance for default bearer, carry out the operation of distributing user face resource again.
RAN is a default bearer distributing user face resource, is example with the GTP tunnel, is exactly the RAN of default bearer correspondence and the GTP tunnel between core net IP address and the TEID in the RAN side, and issues core net in the lump.In this case, core net just is defaulted as this IP and TEID and is the RAN of default bearer correspondence and the GTP tunnel between core net IP and the TEID in the RAN side when obtaining this TEID and IP.
Step 1303: after the MME in the core net receives service request information, carry out safe procedures, finish safety certification, simultaneously newly-established signaling is connected to start and encrypt and integrity protection to MS.
Step 1304:MME sends to RAN and sets up context request message;
MME sends and creates context request to RAN, and the user context information that RAN is needed sends to RAN by context request message, and context request message comprises MM Context information, safe mode parameter and the bearer related information of MS.More specifically, comprise: the mobile subscriber's that MS permanent identification IMSI (if core net is not also notified RAN before this), RAN use roaming restriction strategy and network selecting strategy, such as the PLMN tabulation that allows or restriction MS selects, the AMBR parameter of MS, need be that MS sets up the user plane information of carrying, such as the parameter of the corresponding tunnel of the service quality QoS parameter of bearing identification, load bearing requirements, carrying in core-network side, with the GTP tunnel is example, is exactly corresponding RAN of carrying and the GTP tunnel between core net IP address and the TEID in core-network side.The safe mode parameter comprises: the key that is used for RRC encryption and integrity protection.
Step 1305a:MME is when transmission establishment context request message is to RAN, send renewal session context request message to UPE, the situation that notice UPE carrying is set up, refer to user's face resource information in the present embodiment for the default bearer distribution, with the GTP tunnel is example, is exactly corresponding RAN of carrying and the GTP tunnel between core net IP address and the TEID in the RAN side.
Step 1305b:UPE preserves the renewal session context request message that receives from MME, and replys renewal session context response message to MME.At this moment, core net user face UPE just can be by the default bearer converting downlink data of setting up.
Set up radio bearer and safe mode layoutprocedure between step 1306:RAN and the MS;
User context information in the establishment context request message that the MME that the RAN preservation is received sends, and the beared information of setting up according to the needs in the message, initiate the loading establishing process eat dishes without rice or wine to MS, simultaneously RAN initiates the RRC safety mode process to MS, and RAN is identical with step 605 shown in Figure 6~606 with safety mode process between the MS.
Step 1307:RAN returns and sets up context and finish message and give MME, comprises the result that core net requires to set up carrying, and RAN is the carrying of described foundation user's face resource information of distributing etc.With the GTP tunnel is example, is exactly corresponding RAN of carrying and the GTP tunnel between core net IP address and the TEID in the RAN side.
Step 1308a:MME is receiving that creating context finishes message simultaneously, send renewal session context request message to UPE, the situation that notice UPE carrying is set up, comprise that RAN is user's face resource information that other the foundation carrying outside the default bearer distributes, with the GTP tunnel is example, is exactly corresponding Access Network of carrying and the GTP tunnel between core net IP address and the TEID in the Access Network side.
Step 1308b:UPE preserves the renewal session context request message that receives from MME, and replys renewal session context response message to MME.
Step 1309:MS sends upstream data by the carrying of setting up, and this step does not require execution step 1308b after, can be right after after MS and RAN finish the step 1306 of setting up empty port load-supporting; Perhaps MS connects by the signaling of setting up, and sends up signaling, does not also require after step 1308b and carries out this moment, can be immediately following carrying out in step 1306 back of setting up safety mode process.
Above embodiment five provides is MS process from the Idle state to the activated state when initiating service request, when initiating service request for network side, the process of MS from the Idle state to the activated state is by the following examples six explanations.Referring to Figure 14,
Step 1401:UPE receives downlink data, find that corresponding carrying is unavailable, be that tunnel between core net and the RAN discharges in the resource of RAN side, then UPE sends carrying to MME and sets up request message, and this message is carried the sign of the MS that downlink data will mail to or the sign that downlink data sends needed carrying.
Step 1402:MME receives that carrying sets up request message, finds that the MS that MS sign that this message carries or downlink data send needed bearing identification correspondence is in Idle state, and then to the RAN issuing page message, this message is carried the MS sign.
After step 1403:RAN received this beep-page message, the corresponding MS of MS sign that carries to this message sent beep-page message.
RAN is after MS initiates paging, and MS is execution in step 1404, step 1404 to step 1412 be corresponding one by one with step 1301 to step 1309 among the embodiment five and implementation identical, implementation is not being given unnecessary details.
Top embodiment five, embodiment six describe MS enter activated state from Idle state flow process in detail, among this embodiment, wireless access network is a default bearer distributing user face resource, can accelerate the speed that portable terminal enters activated state, save Signalling exchange, carry out adequate preparation in advance for user entity sends downlink data, be convenient to user entity and send downlink data to portable terminal more in time.In addition, when wireless access network is default bearer distributing user face resource, can be defaulted as default bearer distributing user face resource, also can be by judging that the RAN that requires in service request type or the service request information is the specific identifier that default bearer is allocated resource in advance, whether to determine distributing user face resource, realize comparatively flexible.
Realize the system embodiment of the foregoing description five, six flow processs below by embodiment seven explanations, referring to Figure 15, the system of mobile terminal to enter from free status to activated status shown in Figure 15 forms and comprises portable terminal 1501, wireless access network 1502, mobile management entity 1503;
Described portable terminal 1501 is used for sending service request information to described wireless access network 1502;
Described wireless access network 1502 when being used for that described service request information is forwarded to described mobile management entity 1503, is default bearer distributing user face resource; Receive user context information, utilize described user context information and described portable terminal 1501 to set up safety mode process from described mobile management entity 1503;
Described mobile management entity 1503, be used to receive described service request information after, send described user context information to described wireless access network 1502.
Wherein, described wireless access network 1502 comprises:
Transmit-Receive Unit 1504, the service request information that is used for receiving are sent to described mobile management entity 1503; Reception is from the user context information of described mobile management entity 1503;
Default allocation unit 1505 is used for after described Transmit-Receive Unit 1504 is received described service request information, is default bearer distributing user face resource;
Safe mode unit 1506 is used for after described Transmit-Receive Unit 1504 is received described user context information, utilizes described user context information and described portable terminal 1501 to set up safety mode process.
Wherein, described wireless access network 1502 also comprises:
Empty port load-supporting unit 1507 is used for when safe mode unit 1506 executable operations, utilizes described user context information and described portable terminal in the Transmit-Receive Unit 1504 to set up empty port load-supporting.
Wherein, described mobile management entity 1503 comprises:
First Transmit-Receive Unit 1508, be used to receive described service request information after, send described user context information to described wireless access network 1502.
Wherein, described system also comprises:
User entity 1509 is used for sending carrying to described mobile management entity and sets up request;
Described mobile management entity 1503 also comprises:
Second Transmit-Receive Unit 1510 is used to receive user's face resource information that wireless access network 1502 distributes for default bearer, and is sent to described user entity 1509; To be sent to user entity 1509 for user's face resource information that empty port load-supporting distributes;
Described mobile management entity 1503 also comprises paging unit 1511, be used to receive that request is set up in described carrying after, by the described portable terminal of described wireless access network 1502 pagings.
The above only is embodiment such as process of the present invention and method, system, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.