WO2008116378A1 - Procédé et dispositif correspondant pour le rétablissement d'un support de transmission - Google Patents

Procédé et dispositif correspondant pour le rétablissement d'un support de transmission Download PDF

Info

Publication number
WO2008116378A1
WO2008116378A1 PCT/CN2008/000495 CN2008000495W WO2008116378A1 WO 2008116378 A1 WO2008116378 A1 WO 2008116378A1 CN 2008000495 W CN2008000495 W CN 2008000495W WO 2008116378 A1 WO2008116378 A1 WO 2008116378A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
policy
user
establishment
establish
Prior art date
Application number
PCT/CN2008/000495
Other languages
English (en)
French (fr)
Inventor
Weihua Hu
Wenfu Wu
Yanping Zhang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008116378A1 publication Critical patent/WO2008116378A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present invention relates to the field of mobile communications technologies, and in particular, to a method for implementing bearer re-establishment, a mobility management device, and related network element devices. Background technique
  • SAE System Architecture Evolution
  • EUTRA evolved UMTS Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • MME responsible for control plane mobility management, including management of user context and mobility status, assigning user temporary identity, etc.
  • Server SAE GW Serving System Architecture Evolution Gateway
  • PDN SAE GW Packet Data Network System Architecture Evolution Gateway 40
  • PCRF Policy and Charging Rule Function 50
  • HSS Home Subscriber Server
  • LTE_DETACHED Detached
  • Idle LTE-IDLE
  • LTE-active refers to the state after the UE accesses the SAE system; When in the Idle state, the evolved access network side does not establish radio bearer resources for the user, and evolves the NodeB.
  • the corresponding S1 interface signaling connection does not exist between the core network and the access network.
  • the evolved access network side establishes radio bearer resources for the user.
  • the user's context exists on the eNB, and there is a corresponding S1 interface signaling connection between the core network and the access network.
  • normal context data processing and signaling message interaction can be performed.
  • the signaling connection of the S1 interface when the signaling connection of the S1 interface is released (C SI signaling connection released), the user can switch from the Active state.
  • C SI signaling connection released When the signaling connection of the S1 interface is released (SI signaling connection established), the user can switch from the Idle state to the Active state.
  • the signaling release of the S1 interface may be initiated by the core network (CN).
  • the MME notifies the eNB to release the S1 interface signaling connection of the user; the signaling release of the S1 interface may also be initiated by the eNB, for example, the eNB is During the monitoring and scheduling of the use of air interface resources, when the user's activity is not detected or the contact is lost, the eNB releases the user's S1 interface signaling connection.
  • the user initiates any signaling procedure, including attach, tracking area update (TAU, Tracking Area Update), initiating a service request (Service Request), responding to paging, and separating, etc., all triggering signaling to establish an S1 interface.
  • the connection will cause the user to enter the Active state until the next time the S1 interface signaling connection is released, the user will return to the Idle state.
  • FIG. 3 it is a flowchart of a process in which a user switches from an Idle state to an Active state by initiating a Service Request in an existing SAE system, where the process is: the UE sends a Service Request message to the MME. 1); If the MME accepts the service request sent by the UE, the MME will return a Service Accept message to the UE (step 2); if the service type requested by the UE is signaling, the MME does not initiate the establishment of the radio access bearer.
  • the MME sends a Radio Access Bearer Assignment Request (Radio Access Bearer Assignment Request) message to the eNB to request the eNB to initiate a radio access bearer setup procedure (step 3);
  • the bearer setup (Radio Bearer Setup) message is sent to the UE to establish a radio bearer (step 4); the UE back to the radio bearer setup is completed (Radio Bearer Setup) Complete) message to the eNB (step 5); the eNB returns a Radio Access Bearer Assignment Response message to the MME (step 6);
  • the MME sends a Update Bearer Context Request message to the Serving SAE Gateway (Step 7); Serving SAE Gateway returns the Update Bearer Context Response message to the MME (Step 8).
  • the signaling connection and the radio bearer of the SI interface can be established, so that the user can be switched from the Idle state to the Active state.
  • the user initiates a service request to implement the switch from the Idle state to the Active state.
  • the network side can also send a page to the user to instruct the user to initiate a service request, thereby implementing the switch from the Idle state to the Active state.
  • the evolved access network side When the user is in the Idle state, the evolved access network side does not establish radio bearer resources for the user, and the S1 interface signaling connection between the access network and the core network is also released, so that the user in the Idle state needs to be
  • the network side is required to re-establish the corresponding bearer resources, such as re-establishing the radio bearer and allocating the air interface radio resources, in the process of switching from the Idle state to the Active state.
  • the bearer is generally divided into a guaranteed bit rate (GBR) bearer and a non-GBR bearer.
  • GBR bearer the network side needs to allocate a dedicated network resource.
  • a non-GBR bearer the network side allocation is not required.
  • the network side only rebuilds the bearer resources that the user needs to use, but does not rebuild other bearer resources.
  • bearer A is used to carry the video service of the user.
  • the UE will request the network side to re-establish the bearer A for the network, so that the network side only re-establishes the bearer A for the user, and for the default SAE bearer and the signaling bearer, Will not be re-established.
  • the service request procedure will be initiated again to request the network side to re-establish the signaling bearer, so that the IMS service process can be established based on the re-established signaling bearer, thus causing the establishment of the service process.
  • the increase is increased. Summary of the invention
  • the embodiment of the invention provides a method for implementing bearer re-establishment to reduce the establishment delay of a service flow.
  • a corresponding embodiment of the present invention also proposes a mobility management device and related network element device.
  • An embodiment of the present invention provides a method for implementing bearer re-establishment, including the following steps: In a process of a user switching from an idle state to an active state, the core network instructs the access network to establish a corresponding access-side bearer according to the pre-configured bearer re-establishment policy. The access network establishes a corresponding access side bearer according to the indication of the core network.
  • the embodiment of the present invention further provides a mobility management device, including: a unit for obtaining a pre-configured bearer re-establishment policy; and a method for re-establishing a policy according to a pre-configured bearer during a process of switching from an idle state to an active state
  • the access network establishes a unit corresponding to the bearer on the access side.
  • the embodiment of the present invention further provides a network element device, including: a unit for storing a pre-configured bearer reestablishment policy; a unit for notifying a stored bearer re-establishment policy to a mobility management entity in the core network.
  • the embodiment of the present invention further provides a method for implementing bearer re-establishment, including the following steps: in a process of a user switching from an idle state to an active state, the core network instructs the access network to establish all non-guaranteed bit rate access side bearers; The network establishes all non-guaranteed bit rate access side bearers according to the instructions of the core network.
  • the embodiment of the present invention further provides a mobility management device, including a unit for instructing an access network to establish all non-guaranteed bit rate access side bearers in a process of a user switching from an idle state to an active state.
  • the network side may re-establish the corresponding bearer resource according to the pre-configured bearer re-establishment policy, so that the non-GBR bearer may be re-established for the user at one time.
  • the corresponding GBR bearer is pre-established, so that when the user needs to use these non-GBR bearers or GBR bearers to establish a service flow, the user can directly use the re-established non-GBR bearer and the GBR bearer, so that the service startup speed can be improved. , reduce the establishment time of business processes, and improve the user experience.
  • Figure 1 is a block diagram of the architecture of an existing SAE system
  • FIG. 2 is a schematic diagram of mutual conversion between an Idle state and an Active state by a user in a SAE system
  • FIG. 3 is a flowchart of a process in which a user switches from an Idle state to an Active state by initiating a Service Request in a SAE system;
  • FIG. 4 is a flowchart of a method for implementing a bearer re-establishment in an evolved network according to the present invention
  • FIG. 5 is a schematic diagram of a process of implementing a non-GBR bearer for a user to re-establish a non-GBR bearer
  • FIG. 7 is a schematic diagram of a process of implementing a third embodiment of a user to re-establish a non-GBR bearer
  • FIG. 8 is a schematic diagram of a process of implementing a fourth embodiment for re-establishing a non-GBR bearer by a user
  • FIG. 9 is a schematic diagram of a processing example in which a user sends a subscription information of a user to an MME during an attach process;
  • Figure 10 shows the SPR or PCRF sending pre-configured policy information to the user during the attach process.
  • the embodiment of the present invention provides that when the user switches from the Idle state to the active state, the network side can re-establish a non-GBR bearer for the user at a time, so that the user needs to use these non-GBR bearers to establish a service flow.
  • the non-GBR bearer that has been re-established can be directly used, so that the service startup speed can be improved, the establishment time of the business process can be reduced, and the user experience can be enhanced.
  • the GBR bearer does not occupy network transmission resources when there is no data transmission.
  • the network side re-establishes all non-GBR bearers (including the default SAE bearer and signaling bearer, etc.) for the user, so that the UE performs the IMS service later.
  • the IMS session process can be established directly through the re-established signaling bearer, and the IMS session process can be established after the IMS session process is established by re-establishing the signaling bearer through the Service Request process. Delay.
  • FIG. 4 it is a flowchart of an embodiment of a method for implementing a bearer re-establishment according to the present invention.
  • the core network instructs the access network to establish a corresponding according to a pre-configured bearer re-establishment policy.
  • the access side bearer (step 100); the access network establishes a corresponding access side bearer according to the indication of the core network (step 200).
  • the core network may default to that all non-GBR bearers need to be re-established during the process of the user switching from the Idle state to the active state, and the access network is instructed to re-establish all non-- The GBR access side bearer; the access network establishes all non-GBR access side bearers according to the instructions of the core network.
  • the establishment process of the access side bearer includes radio bearer establishment between the UE and the eNB, and establishment of a radio access bearer between the eNB and the user plane entity (such as the Serving SAE Gateway).
  • the re-established bearer resources are divided into non-GBR bearers and GBR bearers to describe the embodiments of the present invention.
  • the following description is first based on the case of re-establishing non-GBR bearer resources.
  • the first mode When the user switches from the Idle state to the active state, the UE carries the non-GBR bearer re-establishment policy in the message exchanged with the core network, and requires the core network to re-establish the non-GBR bearer.
  • Step 11 The UE sends a Service Request message to the MME.
  • the request message carries a non-GBR bearer re-establishment policy.
  • the non-GBR bearer re-establishment policy can be, but is not limited to, the following cases:
  • the non-GBR bearer re-establishment policy carried by the UE in the Service Request message sent to the MME may be, but is not limited to, implemented as follows:
  • the Service Request message is extended to add a Non-GBR Status cell to carry the non-GBR bearer re-establishment policy configured by the UE.
  • a Non-GBR Status cell to carry the non-GBR bearer re-establishment policy configured by the UE.
  • Table 1 an embodiment for extending the Service Request message (only cells related to the embodiment of the present invention are described in this embodiment, and other cells are not described here):
  • Non-GBR status Value octet 3 Table 3: Non-GBR status Value
  • the UE carries the configured non-GBR bearer re-establishment policy in the Uplink data status cell of the Service Request message, for example, the UE sets the state of the default SAE bearer to the active state (the state is set to the active state to indicate that the bearer needs to be re-established), or Set the status of all non-GBR bearers to the active state (including setting the default SAE bearer to the active state), or set the pre-established non-GBR bearer (such as default SAE bearer, signaling bearer, etc.) status to active. state.
  • the state of the default SAE bearer to the active state (the state is set to the active state to indicate that the bearer needs to be re-established), or Set the status of all non-GBR bearers to the active state (including setting the default SAE bearer to the active state), or set the pre-established non-GBR bearer (such as default SAE bearer, signaling bearer, etc.) status to active. state.
  • the non-GBR bearer re-establishment policy is to re-establish the default SAE bearer. Representing a non-GBR bearer re-establishment strategy to re-establish all For a non-GBR bearer, the non-GBR bearer re-establishment policy is to re-establish the pre-established non-GBR bearer when attaching.
  • Step 12 If the MME accepts the service request, it replies to the service accept message to the UE.
  • Step 13 The MME analyzes the non-GBR bearer re-establishment policy carried in the service request message sent by the UE, determines which non-GBR bearers need to be re-established, and then sends a radio access bearer setup request message to the eNB, where the radio access bearer is sent.
  • the setup request message includes the non-GBR bearer to be reestablished determined by the MME analysis. If the service request message sent by the UE does not carry the non-GBR bearer re-establishment policy, the MME defaults that all the non-GBR bearers need to be re-established, and the radio access bearer setup request message sent to the eNB carries the re-establishment all Information not carried by GBR.
  • Step 14 The eNB sends a radio bearer setup message to the UE according to the non-GBR bearer to be re-established included in the received radio access bearer setup request message, to indicate that the UE establishes a corresponding radio bearer.
  • Step 15 After the UE establishes the corresponding radio bearer, it replies to the radio bearer setup complete message to the eNB»
  • Step 16 The eNB replies to the radio access bearer setup response message to the MME.
  • Step 17. The MME sends a Modify Bearer Context Request message to the Serving SAE Gateway.
  • Step 18. The Serving SAE Gateway replies to modify the bearer context response message to the MME.
  • the process of the foregoing embodiment is to initiate a service request by the user to implement the service from the Idle state to the active state.
  • the network side may also send a paging service to the user to instruct the user to initiate a service request to the network side.
  • the switch from the Idle state to the Active state is implemented, so that the processing in the dotted line is performed before the step 11: the Serving SAE Gateway receives the downlink data packet sent to the user in the Idle state; the Serving SAE Gateway sends the paging message to The MME triggers a paging procedure; the MME sends a paging message to the eNB; the eNB sends a paging message to the UE, and then the UE sends a Service Request message to the MME after receiving the paging message.
  • the UE may also trigger the state switching by the network side. Since the principle is similar, the description will not be repeated below.
  • the foregoing first mode is not limited to the other processes in the process of the service request processing, and the user switches from the Idle state to the active state.
  • the network side may also re-establish non-GBR for the UE according to the indication sent by the UE. Hosted.
  • Step 31 The UE sends a tracking area update request (TAU Request) message to the MME, where the request message carries a non-GBR bearer re-establishment policy configured by the UE, where the non-GBR bearer re-establishment policy may include a type according to the foregoing first embodiment. Introduction.
  • TAU Request tracking area update request
  • the non-GBR bearer re-establishment policy carried by the UE in the TAU Request message sent to the MME may be, but is not limited to, implemented as follows:
  • the TAU Request message is extended to add a Non-GBR Status cell to carry the non-GBR bearer re-establishment policy configured by the UE.
  • a Non-GBR Status cell to carry the non-GBR bearer re-establishment policy configured by the UE.
  • Table 4 an embodiment for extending the TAU Request message (only cells related to the embodiment of the present invention are described in this embodiment, and other cells are not described here):
  • Non-GBR status cell For details of the Non-GBR status cell and the Non-GBR status value, please refer to Table 2 and Table 3 in the first embodiment described above.
  • the UE carries the configured non-GBR bearer re-establishment policy in the Uplink data status cell of the TAU Request message, for example, the UE sets the state of the default SAE bearer to an active state (the state is set to the active state to indicate that the bearer needs to be re-established), or Set the status of all non-GBR bearers to the active state (including setting the default SAE bearer to the active state), or set the pre-established non-GBR bearer (such as default SAE bearer, signaling bearer, etc.) status to active. state.
  • Step 32 If the MME accepts the tracking area update request, the reply tracking area update accept message is sent to UE.
  • Step 33 The MME analyzes the non-GBR bearer reestablishment policy carried in the TAU request message sent by the UE, and determines which non-GBR bearers need to be re-established. If the non-GBR bearer re-establishment policy is not carried in the TAU request message sent by the UE, the MME defaults that all non-GBR bearers need to be re-established.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the first embodiment, and no further description is given here.
  • the second mode When the user switches from the Idle state to the active state, the policy of re-establishing non-GBR bearers and re-establishing non-GBR bearers is pre-configured by the operator on the MME.
  • Step 41 The UE sends a Service Request message to the MME.
  • Step 42 If the MME accepts the service request, it replies to the service accept message to the UE.
  • Step 43 The MME re-establishes a policy according to the non-GBR bearer configured by the operator in the user, and determines which non-GBR bearers need to be re-established.
  • the types that may be included in the non-GBR bearer re-establishment policy refer to the introduction in the first embodiment above. If the non-GBR bearer re-establishment policy is not configured on the MME, the MME defaults that all non-GBR bearers need to be re-established.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the first embodiment, and no further description is given here.
  • the foregoing second method is not limited to the other processes in the process of the service request processing, and the user is in the process of switching from the Idle state to the active state.
  • the network side may also re-establish the UE according to the policy configured by the operator on the MME.
  • Non-GBR bearer may also be used to re-establish the UE according to the policy configured by the operator on the MME.
  • Step 51 The UE sends a tracking area update request message to the MME.
  • Step 52 If the MME accepts the tracking area update request, the reply tracking area update accept message is sent to
  • the MME re-establishes a policy according to the non-GBR bearer configured by the operator in the user, and determines which non-GBR bearers need to be re-established.
  • the types that may be included in the non-GBR bearer re-establishment policy refer to the introduction in the first embodiment described above. If the non-GBR bearer re-establishment policy is not configured on the MME, the MME defaults that all non-GBR bearers need to be re-established.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the foregoing first embodiment, and no further description is given here.
  • the third mode When the user switches from the Idle state to the Active state, whether the policy for re-establishing non-GBR bearers and re-establishing non-GBR bearers is determined by the subscription data saved in the user HSS.
  • the user sends the subscription information of the user to the MME for saving by the HSS.
  • the MME After receiving the service request request message sent by the UE, the MME determines whether to re-establish non-GBR bearers and re-establish non-GBR bearers according to the saved user subscription information.
  • FIG. 9 a schematic diagram of a processing example in which the HSS sends the user's subscription information to the MME during the attaching process, where the specific processing procedure is as follows:
  • Step 61 The UE sends an attach request message to the MME to request attach processing.
  • Step 62. The MME sends a Location Update message to the HSS.
  • Step 63 The HSS sends an Insert Subscriber Data message to the MME, where the sent insertion subscription data includes a non-GBR bearer re-establishment policy configured for the user UE, where the non-GBR bearer re-establishment policy may include a type reference.
  • Step 64 The MME replies to the Insert Subscriber Data Ack message to the HSS.
  • Step 65 The HSS sends a Location Update Ack message to the MME.
  • Step 66 The MME saves the non-GBR bearer re-establishment policy included in the insertion subscription data, and returns an Attach Accept message to the UE.
  • the subsequent MME After receiving the Service Request message sent by the UE, the subsequent MME replies to the service acceptance message to the UE, and determines which non-GBR bearers need to be re-established according to the saved non-GBR bearer re-establishment policy. If the non-GBR bearer re-establishment policy configured for the user UE is not included in the insertion subscription data sent by the HSS, the MME defaults to all non-bearers. All need to be re-established.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the foregoing first embodiment, and no further description is given here.
  • the subsequent MME replies to the tracking area update accept message to the UE after receiving the tracking area update request, and determines that the re-establishment needs to be re-established according to the saved non-GBR bearer re-establishment policy. Which non-GBR bearers.
  • the fourth mode When the user switches from the Idle state to the active state, whether the policy for re-establishing non-GBR bearers and re-establishing non-GBR bearers is pre-configured by the operator in the PCRF, or pre-configured in the policy and charging execution.
  • PCEF Policy and Charging Enforcement Function
  • SPR User Profile Subscription Database
  • the user sends the pre-configured policy to the MME for saving by PCRF, or PCEF, or SPR.
  • the MME determines whether to re-establish non-GBR bearers and re-establish non-GBR bearers according to the saved user subscription information.
  • the SPR or the PCRF sends the pre-configured policy information to the MME to save the processing example.
  • the specific processing procedure is as follows:
  • Step 71 The UE sends an Attach Request message to the MME.
  • Step 72 The MME sends a Create Bearer Context Request message to the Serving SAE Gateway to request Serving SAE Gatewa to create a SAE bearer.
  • Step 73 The Serving SAE Gateway sends a Create Bearer Context Request message to the PDN SAE Gateway to request the PDN SAE Gateway to create a SAE bearer.
  • Step 74 The PDN SAE Gateway sends a Request Policy and Charging Rules message to the PCRF.
  • the pre-configured policy is returned to the PDN SAE Gateway through a Policy and Charging Rules Provision message; If the user's subscription data does not exist in the PCRF, then in step 75, the PCRF sends a subscription data request (Profile Request) message.
  • Profile Request subscription data request
  • the SPR stores the policy and the charging-related subscription data that the PCRF needs to use, and then obtains the subscription data of the user.
  • Step 76 The SPR returns a subscription data response (Profile Response) message to the PCRF, where the user's subscription data is carried, and the user's subscription data may include a non-GBR bearer re-establishment policy preset by the operator for the user.
  • Profile Response subscription data response
  • Step 77 The PCR and Charging Rules Provision message is sent to the PDN SAE Gateway, and the reply message carries the non-GBR bearer re-establishment policy of the user.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the first embodiment, and no further description is given here.
  • the non-GBR bearer re-establishment policy may be configured in the PCRF in advance, or may be configured in the SPR in advance, and carried in the subscription data response message by the SPR to the PCRF.
  • Step 78 The PDN SAE Gateway replies with a Create Bearer Context Response message to the Serving SAE Gateway, which carries the non-GBR bearer re-establishment policy of the UE.
  • the non-GBR bearer re-establishment policy can also be configured in the PDN SAE Gateway, and the PDN SAE Gateway carries the Serving SAE Gateway through the Create Bearer Context Response message.
  • Step 79 The Serving SAE Gateway replies to the Create Bearer Context Response message to the MME, and the replies message carries the non-GBR bearer reestablishment policy of the UE.
  • Step 80 The MME saves the non-GBR bearer re-establishment policy included in the received Create Bearer Context Response message, and initiates a radio bearer setup process to establish a radio access bearer corresponding to the SAE bearer. This part of the process is a well-known technique and will not be elaborated here.
  • Step 81 The MME replies to the Attach Accept message to the UE.
  • the bearer creation process (steps 2 to 10) and the user's attachment process have no contingency relationship, and the bearer creation process can be completed in the process of attaching (such as creating a default SAE bearer). It is also possible to perform bearer creation processing (such as establishing a signaling bearer) after the attachment is completed.
  • the subsequent MME After receiving the request message sent by the UE (including the Service Request message or the TAU Request message), the subsequent MME, if accepting the service request or the tracking area update request, responds to the service accept message or the tracking area update accept message to the UE, and according to the The saved non-GBR bearer re-establishment policy determines which non-GBR bearers need to be re-established.
  • the re-establishment process of the non-GBR bearer is the same as the steps 13-18 in the foregoing first embodiment, and no further description is given here.
  • the re-establishment principle of the non-GBR bearer can also be applied to the re-establishment of the GBR bearer.
  • the terminal generally has a signaling bearer and a GBR bearer, and the signaling bearer is used to perform a video service session establishment process, GBR.
  • the bearer is used to transport video traffic. Both the signaling bearer and the GBR bearer will be released when the user is in the Idle state.
  • the video service flow is processed at the same time as the video service session is established. Therefore, for such a terminal, a policy for re-establishing all bearers can be configured.
  • the network When the terminal is switched from the Idle state to the active state, the network re-establishes the signaling bearer and the GBR bearer for the user according to the pre-configured bearer re-establishment policy. After the user completes the video service session establishment process on the signaling bearer, the terminal can The video service flow is processed on the re-established GBR bearer, which can also speed up the access of the video service and enhance the user experience. .
  • the scheme for determining which bearers to re-establish according to the bearer re-establishment policy may also be applied to a general packet radio service (GPRS) system, for example, when the UE switches from the Idle state to the active state process.
  • GPRS general packet radio service
  • the Serving GPRS Supporting Node (SGSN) may re-establish a corresponding radio access bearer for the UE according to the bearer re-establishment policy preset for the user.
  • the embodiment of the present invention further provides a mobility management device (such as an MME in an SAE system or an SGSN in a GPRS system) in an evolved network, where the method includes obtaining a pre-configured bearer re-establishment. a unit of the policy, and a unit for instructing the access network to establish a corresponding access side bearer according to the pre-configured bearer re-establishment policy.
  • the MME may further include a unit that stores the pre-configured bearer re-establishment policy, so that the MME may determine which bearer resources are re-established according to the stored policy; or the unit for obtaining the policy may also send the external network element device.
  • Pre-configured bearer re-establishment strategy to achieve the corresponding bearer re-establishment policy slightly.
  • a network element device in an evolved network including: a unit for storing a pre-configured bearer re-establishment policy; and a unit for notifying the stored bearer re-establishment policy to the MME in the core network.
  • the network element device here may be a UE, or may be an HSS in the core network, or a PCRF, or a PCEF, or an SPR.
  • the embodiment of the present invention further provides a mobility management device in the second evolved network, which is configured to instruct the access network to establish all non-GBR connections during the process of the user switching from the Idle state to the Active state.
  • the mobility management device (such as the MME) defaults to the user when the user switches from the Idle state to the Active state. Re-establish all non-GBR bearer resources.
  • the mobility management device can also be, but is not limited to, an MME in the SAE system, or an SGSN in the GPRS system.
  • the functional components included in the mobility management device and related network element devices may be implemented by corresponding software programs, or may be implemented based on upgrading and upgrading related hardware components.
  • the network side may re-establish the corresponding bearer resource according to the pre-configured bearer re-establishment policy, so that the user can be A non-GBR bearer is set up, so that when the user needs to use these non-GBR bearers to establish a service process, the user can directly use the non-GBR bearer that has been re-established. Therefore, the service startup speed can be improved and the setup time of the service process can be reduced.
  • non-GBR bearers that are re-established in advance will not occupy network transmission resources when there is no data transmission.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

实现承载重建立的方法、 及其相关设备 技术领域
本发明涉及移动通信技术领域， 尤其是涉及一种实现承载重建立的方法、 移动性管理设备及其相关的网元设备。 背景技术
第三代移动通信标准组织 （3GPP )为了增强未来网络的竟争能力， 正在 研究一种全新的演进网络， 命名为***架构演进（ SAE, System Architecture Evolution )***。如图 1所示，为现有 SAE***的架构框图，包括演进的 UMTS 陆地无线接入网（ EUTRA , Evolved UMTS Terrestrial Radio Access Network ) 10， 用于实现所有与演进网络无线接入有关的功能； 移动性管理实体（MME, Mobility Management Entit ) 20， 负责控制面移动性管理， 包括对用户上下文 和移动状态的管理， 分配用户临时身份标识等； 服务***架构演进网关
( Serving SAE GW, Serving System Architecture Evolution Gateway ) 30, 是 3GPP接入***间的用户面锚点， 负责终止 ETURAN 10的接口； 分组数据网 络***架构演进网关（ PDN SAE GW, Packet Data Network System Architecture Evolution Gateway ) 40， 是 3GPP接入***和非 3GPP接入***之间的用户面 锚点， 负责终止和外部分组数据网络（PDN, Packet Data Network )的接口； 策略和计费规则功能实体（PCRF, Policy and Charging Rule Function ) 50, 用 于处理策略控制和流计费控制； 归属用户服务器 （HSS， Home Subscriber Server ) 60, 用于存储用户的签约信息。
其中现有的 SAE***架构还处在不断的演进过程中，在 SAE***中定义 了三种用户状态： 分离状态 （LTE_DETACHED， 简称 Detached ), 指 UE未 接入 SAE ***时的状态； 空闲状态 （LTE— IDLE, 简称 Idle )和激活状态
( LTE— ACTIVE, 简称 Active ), 指 UE接入 SAE***后的状态； 其中当用户 处于 Idle状态时， 演进接入网侧没有为用户建立无线承载资源， 演进 NodeB
(简称 eNB )上也不存在用户的上下文， 核心网与接入网之间也不存在对应 的 S1接口信令连接； 当用户处于 Active状态时， 演进接入网侧为用户建立了 无线承载资源， eNB 上存在用户的上下文， 且核心网与接入网之间存在对应 的 S1接口信令连接，用户处在 Active状态下时能够进行正常的上下文数据处 理和信令消息交互。
如图 2所示， 为现有在 SAE***中用户在 Idle状态和 Active状态之间的 相互转换示意图， 当 S1 接口的信令连接被释放 C SI signaling connection released ) 时， 用户可以从 Active状态切换到 Idle状态； 当 S 1接口的信令连 接被建立 （ SI signaling connection established ) 时， 用户可以从 Idle状态切换 到 Active状态。 其中 S1接口的信令释放可以由核心网 （CN )发起， 比如用 户分离关机时， MME会通知 eNB释放用户的 S1接口信令连接； S1接口的信 令释放也可以由 eNB发起， 比如 eNB在监控和调度空口资源的使用过程中， 当探测不到用户的活动或者失去联系时， eNB会释放用户的 S 1接口信令连接。 此外，用户发起任何信令流程，包括附着（Attach )、跟踪区更新（TAU, Tracking Area Update )、 向 MME发起服务请求（ Service Request )、 响应寻呼以及分离 等都会触发建立 S1接口的信令连接， 从而用户就会进入 Active状态， 直到下 次再释放 S1接口信令连接时， 用户才会重新回到 Idle状态。
如图 3所示，为现有在 SAE***中，用户通过发起 Service Request从 Idle 状态切换到 Active状态的处理流程图， 其中的处理过程为： UE发送业务请求 ( Service Request ) 消息给 MME (步骤 1 ); 如果 MME接受 UE发来的业务 请求， MME将回业务接受 （Service Accept ) 消息给 UE (步骤 2 ); 如果 UE 请求的业务类型为信令， 则 MME不发起无线接入承载的建立流程， 如果 UE 请求的业务类型为数据， 则 MME发送无线接入承载建立请求（Radio Access Bearer Assignment Request )消息给 eNB , 以请求 eNB发起无线接入承载的建 立流程（步骤 3 ); eNB发送无线承载建立 （Radio Bearer Setup ) 消息给 UE 以建立无线承载 （步骤 4 ); UE 回无线承载建立完成（Radio Bearer Setup Complete )消息给 eNB (步骤 5 ); eNB回无线接入承载建立响应（ Radio Access Bearer Assignment Response ) 消息给 MME (步骤 6 ); MME发送修改承载上 下文请求（ Update Bearer Context Request ) 消息给 Serving SAE Gateway (步 骤 7 ); Serving SAE Gateway回修改承载上下文响应 （ Update Bearer Context Response ) 消息给 MME (步骤 8 )。 通过该过程可以建立起 SI接口的信令连 接和无线承载， 因此可以使用户从 Idle状态切换到 Active状态。 上述过程是 由用户主动发起业务请求实现自身从 Idle状态切换到 Active状态的， 此外网 络侧也可以通过向用户下发寻呼， 以指示用户发起业务请求，从而实现从 Idle 状态切换到 Active状态。
由于用户处在 Idle状态下时， 演进接入网侧没有为用户建立无线承载资 源， 且接入网和核心网之间的 S1接口信令连接也是被释放的， 这样处于 Idle 状态下的用户要使用相关业务时， 要在从 Idle状态切换到 Active状态过程中 要求网络侧为其重建立相应的承载资源， 如重建立无线承载， 分配空口无线 资源等。承载一般分为保证比特率（GBR, Guaranteed Bit Rate )承载和非 GBR 承载， 其中对于 GBR承载而言， 需要网络侧分配专有的网络资源； 对于非 GBR承载而言， 不需要网络侧分配专有的网络资源， 包括缺省 SAE承载和信 令承载等。
目前， 用户在从 Idle状态切换到 Active状态时， 网络侧通常只重建用户 需要使用的承载资源，而不重建其它的承载资源，例如存在三个承载：承载 A, 缺省 SAE承载，信令承载，其中承载 A用于承载用户的视频业务。当处于 Idle 状态下的用户想使用视频业务时， UE将请求网络側为其重建立承载 A, 这样 网络侧只为用户重建立承载 A， 而对于缺省 SAE承载和信令承载而言， 将不 会重建立。 这样如果用户想继续使用 IMS业务， 将要再次发起业务请求流程 以请求网络侧为其重建立信令承载， 才能基于重建立的信令承载进行 IMS业 务流程的建立， 因此就会导致业务流程的建立时延增大。 发明内容
本发明实施例提出一种实现承载重建立的方法， 以减小业务流程的建立 时延。
相应的本发明实施例还提出了一种移动性管理设备及其相关的网元设 备。
本发明实施例提出一种实现承载重建立的方法， 包括步骤： 在用户由空 闲状态切换到激活状态过程中 , 核心网根据预先配置的承载重建立策略指示 接入网建立对应的接入侧承载； 接入网按照核心网的指示建立对应的接入侧 承载。
本发明实施例还提出一种移动性管理设备， 包括用于获得预先配置的承 载重建立策略的单元； 用于在用户由空闲状态切换到激活状态过程中， 根据 预先配置的承载重建立策略指示接入网建立对应接入侧承载的单元。
本发明实施例还提出一种网元设备， 包括用于存储预先配置的承载重建 立策略的单元； 用于将存储的承载重建立策略通知给核心网中的移动性管理 实体的单元。
本发明实施例还提出一种实现承载重建立的方法， 包括步骤： 在用户由 空闲状态切换到激活状态过程中， 核心网指示接入网建立所有的非保证比特 率接入侧承载； 接入网按照核心网的指示建立所有非保证比特率接入侧承载。
本发明实施例还提出一种移动性管理设备， 包括用于在用户由空闲状态 切换到激活状态过程中， 指示接入网建立所有的非保证比特率接入侧承载的 单元。
本发明实施例在用户从 Idle状态切换到 Active状态过程中， 网络侧可以 根据预先配置的承载重建立策略为用户重建立相应的承载资源， 因此可以实 现一次性地为用户重建立非 GBR承载、 或预先建立相应的 GBR承载， 这样 用户在后续需要使用这些非 GBR承载或 GBR承载建立业务流程时， 可以直 接使用已经重建立好的非 GBR承载及 GBR承载， 因此可以较好的提高业务 启动速度， 减少业务流程的建立时间， 提高用户的使用体验。 附图说明
为了使本发明实施例及其对应能够达到的有益效果更加明了 , 下面将结 合各个附图对本发明实施例进行详细阐述， 在各附图中：
图 1为现有 SAE***的架构框图；
图 2为现有在 SAE***中用户在 Idle状态和 Active状态之间的相互转换 示意图；
图 3为现有在 SAE***中， 用户通过发起 Service Request从 Idle状态切 换到 Active状态的处理流程图；
图 4为本发明在演进网络中实现承载重建立方法的实施例流程图； 图 5为实现为用户重建立非 GBR承载的第一实施例处理过程示意图； 图 6为实现为用户重建立非 GBR承载的第二实施例处理过程示意图； 图 7为实现为用户重建立非 GBR承载的第三实施例处理过程示意图； 图 8为实现为用户重建立非 GBR承载的第四实施例处理过程示意图； 图 9为用户在附着过程中， HSS将用户的签约信息发送至 MME保存的 处理实施例示意图；
图 10为用户在附着过程中， SPR或 PCRF将预配置的策略信息发送至
MME保存的处理实施例示意图。 具体实施方式
在 SAE***中， 对于非 GBR承载在基于共享信道的方式下， 只有在实 际传输数据时才会占用空口资源， 所以即使在没有业务使用的情况下重建立 非 GBR承载也不会浪费网络传输资源。 基于该原理， 本发明实施例提出在用 户从 Idle状态切换到 Active状态过程中， 网络側可以一次性地为用户重建立 非 GBR承载， 这样用户在后续需要使用这些非 GBR承载建立业务流程时， 可以直接使用已经重建立好的非 GBR承载， 因此可以较好的提高业务启动速 度， 减少业务流程的建立时间， 增强用户的使用体验。 此外预先重建立的非 GBR承载在没有数据传输时也不会占用网络传输资源。
例如在用户从 Idle状态切换到 Active状态过程中， 网络侧一次性地为用 户重建立所有的非 GBR承载（包括缺省 SAE承载和信令承载等等）， 这样 UE在后续进行 IMS业务时就可以直接通过已经重建立的信令承载来进行 IMS 会话流程的建立， 而不再需要通过 Service Request流程来重建立信令承载后， 再进行 IMS会话流程的建立， 这样就可以减小 IMS会话流程建立的时延。
如图 4所示， 为本发明实现承载重建立方法的实施例流程图， 其中在用 户由 Idle状态切换到 Active状态过程中， 核心网根据预先配置的承载重建立 策略指示接入网建立对应的接入侧承载（步骤 100 ); 接入网按照核心网的指 示建立对应的接入侧承载（步骤 200 )。 如果预先没有为用户配置对应的承载 重建立策略， 在用户由 Idle状态切换到 Active状态过程中， 核心网可以默认 为所有的非 GBR承载都需要重建立， 则指示接入网重建立所有的非 GBR接 入侧承载； 接入网按照核心网的指示建立所有的非 GBR接入侧承载。 其中接 入侧承载的建立过程包括 UE到 eNB之间的无线承载建立 , 和 eNB到用户面 实体（如 Serving SAE Gateway )之间的无线接入承载建立。
为方便描述， 将重建立的承载资源分为非 GBR承载和 GBR承载两种情 况来对本发明实施例进行阐述， 下面首先基于重建立非 GBR承载资源的情况 来描述。
第一种方式： 用户从 Idle状态切换到 Active状态时， UE在与核心网交互 的消息中携带非 GBR承载重建立策略，要求核心网为其重建立非 GBR承载。
如图 5所示， 为实现为用户重建立非 GBR承载的第一实施例处理过程示 意图， 其中具体实施过程如下：
步驟 11. UE发送 Service Request消息给 MME， 该请求消息中携带有非 GBR承载重建立策略，其中非 GBR承载重建立策略可以但不限于包括如下几 种情况：
1 )重建立缺省 SAE承载；
2 )重建立所有非 GBR承载； 3 )重建立附着时预建立的非 GBR承载（如缺省 SAE承载、信令承载等）。
UE在向 MME发送的 Service Request消息中携带非 GBR承载重建立策 略可以但不限于通过如下方式来实现：
对 Service Request消息进行扩展， 以在其中增力口一个 Non-GBR Status信 元，用于携带 UE配置的非 GBR承载重建立策略。如下表 1所示，为对 Service Request消息进行扩展的一个实施例（该实施例中只描述与本发明实施例相关 的信元， 其它信元这里不予描述）：
表 1： 扩展后 Service Request消息的内容
Figure imgf000009_0001
表 2: 为 Non-GBR status信元的具体内容
5 4
Non-GBR status I£I octet 1
Length of Non-GBR status octet 2
Non-GBR status Value octet 3 表 3： 为 Non-GBR status Value
Non-GBR status Value
0 establish Default SAE Bearer
1 establish all non-GBR Bearers
2 establish pre-non-GBR Bearers
UE在 Service Request消息的 Uplink data status信元中携带配置的非 GBR 承载重建立策略， 如 UE将缺省 SAE承载的状态设置为激活态（状态设置为 激活态表明这个承载需要重建立）， 或将所有非 GBR承载的状态设置为激活 态（包括将缺省 SAE承载设置为激活态)， 或者将附着时预建立的非 GBR承 载（如缺省 SAE承载、 信令承载等）状态设置为激活态。
基于上述表中内容所示， 例如扩 的 Service Request消息中 Non-GBR status信元承载的 Non-GBR status Value为 0时，代表非 GBR承载重建立策略 为重建立缺省 SAE承载， 为 1时代表非 GBR承载重建立策略为重建立所有 非 GBR承载， 为 2时代表非 GBR承载重建立策略为重建立附着时预建立的 非 GBR承载。
步骤 12. 如果 MME接受业务请求， 则回复业务接受消息给 UE。
步骤 13. MME分析 UE发来的业务请求消息中携带的非 GBR承载重建立 策略， 确定需要重建立哪些非 GBR承载， 然后发送无线接入承载建立请求消 息给 eNB, 其中发送的无线接入承载建立请求消息中包括 MME分析确定的 要重建立的非 GBR承载。如果 UE发来的 Service Request消息中未携带非 GBR 承载重建立策略， 则 MME默认为所有的非 GBR承载都需要重建立， 则在发 送给 eNB的无线接入承载建立请求消息中携带重建立所有非 GBR承载的信 息。
步骤 14. eNB根据接收的无线接入承载建立请求消息中包括的要重建立 的非 GBR承载， 发送无线承载建立消息给 UE, 以指示 UE建立对应的无线 承载；
步骤 15. UE建立完成相应的无线承载后， 回复无线承载建立完成消息给 eNB»
步骤 16. eNB回复无线接入承载建立响应消息给 MME。
步骤 17. MME发送修改承栽上下文请求消息给 Serving SAE Gateway。 步骤 18. Serving SAE Gateway回复修改承载上下文响应消息给 MME。 上述第一实施例的处理过程是由用户主动发起业务请求实现自身从 Idle 状态切换到 Active状态的， 此外网络侧也可以通过向用户下发寻呼业务， 以 指示用户向网络侧发起业务请求， 从而实现从 Idle状态切换到 Active状态， 这样在步骤 11前面还要执行虚线框内处理： Serving SAE Gateway收到下发给 处于 Idle状态下的用户的下行数据包； Serving SAE Gateway发送寻呼消息到 MME触发寻呼流程； MME发送寻呼消息到 eNB; eNB发送寻呼消息到 UE, 然后 UE接收到寻呼消息后再向 MME发送 Service Request消息。下面各个以 Service Request为实施例的处理流程图中同样可以由网络侧触发 UE进行状态 切换， 由于原理类似， 下面将不再重复描述。 上述第一种方式不局限于 Service Request处理流程中， 用户从 Idle状态 切换到 Active状态时的其他流程， 比如在 TAU处理流程中网络侧也可以才艮据 UE发送的指示为 UE重建立非 GBR承载。
如图 6所示， 为实现为用户重建立非 GBR承载的第二实施例处理过程示 意图， 其中具体实施过程如下：
步骤 31. UE发送跟踪区更新请求（TAU Request ) 消息给 MME， 该请求 消息中携带 UE配置的非 GBR承载重建立策略， 其中非 GBR承载重建立策 略可能包括的类型参照上述第一实施例中的介绍。
UE在向 MME发送的 TAU Request消息中携带非 GBR承载重建立策略 可以但不限于通过如下方式来实现：
对 TAU Request消息进行扩展，以在其中增加一个 Non-GBR Status信元， 用于携带 UE配置的非 GBR承载重建立策略。如下表 4所示，为对 TAU Request 消息进行扩展的一个实施例（该实施例中只描述与本发明实施例相关的信元， 其它信元这里不予描述）：
表 4: 扩展后 TAU Request消息的内容
Figure imgf000011_0001
有关 Non-GBR status信元的具体内容和 Non-GBR status Value请具体参见 上述第一实施例中的表 2和表 3。
UE在 TAU Request消息的 Uplink data status信元中携带配置的非 GBR承 载重建立策略， 如 UE将缺省 SAE承载的状态设置为激活态（状态设置为激 活态表明需要重建立这个承载）， 或将所有非 GBR承载的状态设置为激活态 (包括将缺省 SAE承载设置为激活态）， 或者将附着时预建立的非 GBR承载 (如缺省 SAE承载、 信令承载等）状态设置为激活态。
步骤 32. 如果 MME接受跟踪区更新请求，则回复跟踪区更新接受消息给 UE。
步骤 33. MME分析 UE发来的 TAU请求消息中携带的非 GBR承载重建 立策略，确定需要重建立哪些非 GBR承载。如果 UE发来的 TAU请求消息中 未携带非 GBR承载重建立策略， 则 MME默认为所有的非 GBR承载都需要 重建立。其中有关非 GBR承载的重建立过程同上述第一实施例中的步骤 13 ~ 18， 这里不再给以过多赘述。
第二种方式： 用户从 Idle状态切换到 Active状态时， 是否为用户重建立 非 GBR承载以及重建立哪些非 GBR承载的策略由运营商预先配置在 MME 上。
如图 7所示， 为实现为用户重建立非 GBR承载的第三实施例处理过程示 意图， 其中具体实施过程如下：
步骤 41. UE发送 Service Request消息给 MME。
步骤 42. 如果 MME接受业务请求， 则回复业务接受消息给 UE。
步骤 43. MME根据运营商在自身中为用户配置的非 GBR承载重建立策 略, 确定需要重建立哪些非 GBR承载。 其中非 GBR承载重建立策略可能包 括的类型参照上述第一实施例中的介绍。如果运营商未在 MME上配置非 GBR 承载重建立策略， 则 MME默认为所有的非 GBR承载都需要重建立。 其中有 关非 GBR承载的重建立过程同上述第一实施例中的步骤 13 ~ 18,这里不再给 以过多赘述。
上述第二种方式不局限于 Service Request处理流程中， 用户从 Idle状态 切换到 Active状态时的其他流程， 比如在 TAU处理流程中网络側也可以根据 运营商在 MME上配置的策略为 UE重建立非 GBR承载。
如图 8所示， 为实现为用户重建立非 GBR承载的第四实施例处理过程示 意图， 其中具体实施过程如下：
步骤 51. UE发送跟踪区更新请求消息给 MME。
步骤 52. 如果 MME接受跟踪区更新请求，则回复跟踪区更新接受消息给
UE„ 步 53. MME根据运营商在自身中为用户配置的非 GBR承载重建立策 略， 确定需要重建立哪些非 GBR承载。 其中非 GBR承载重建立策略可能包 括的类型参照上述第一实施例中的介绍。如果运营商未在 MME上配置非 GBR 承载重建立策略， 则 MME默认为所有的非 GBR承载都需要重建立。 其中有 关非 GBR承载的重建立过程同上述第一实施例中的步骤 13 ~ 18,这里不再给 以过多赘述。
第三种方式： 用户从 Idle状态切换到 Active状态时， 是否为用户重建立 非 GBR承载以及重建立哪些非 GBR承载的策略由用户 HSS中保存的签约数 据决定。 用户在附着过程中， 由 HSS将该用户的签约信息发送至 MME保存。 后续 MME接收到 UE发来的 service request请求消息后， 根据保存的用户签 约信息来决定是否为用户重建立非 GBR承载以及重建立哪些非 GBR承载。
如图 9所示， 为用户在附着过程中， HSS将用户的签约信息发送至 MME 保存的处理实施例示意图， 其中具体的处理过程如下：
步骤 61. UE发送附着请求（ Attach request )消息给 MME，请求附着处理。 步骤 62. MME发送位置更新 ( Update Location ) 消息到 HSS。
步骤 63. HSS发送***签约数据 ( Insert Subscriber Data )消息到 MME， 其中该发送的***签约数据中包括为用户 UE配置的非 GBR承载重建立策略， 其中非 GBR承载重建立策略可能包括的类型参照上述第一实施例中的介绍。
步骤 64. MME回复***签约数据确认（ Insert Subscriber Data Ack ) 消息 给 HSS。
步骤 65. HSS发送位置更新确认（ Update Location Ack ) 消息给 MME。 步骤 66. MME保存***签约数据中包括的非 GBR承载重建立策略， 并 回复附着接受 （Attach Accept ) 消息给 UE。
后续 MME在接收到 UE发来的 Service Request消息后，如果接受该业务 请求， 则回复业务接受消息给 UE， 并根据保存的非 GBR承载重建立策略， 确定需要重建立哪些非 GBR承载。如果 HSS发来的***签约数据中不包括为 用户 UE配置的非 GBR承载重建立策略，则 MME默认为所有的非 承载 都需要重建立。 其中有关非 GBR承载的重建立过程同上述第一实施例中的步 骤 13 ~ 18, 这里不再给以过多赘述。
同理， 后续 MME在接收到 UE发来的 TAU Request消息后， 如果接受该 跟踪区更新请求， 则回复跟踪区更新接受消息给 UE， 并根据保存的非 GBR 承载重建立策略， 确定需要重建立哪些非 GBR承载。
第四种方式： 用户从 Idle状态切换到 Active状态时， 是否为用户重建立 非 GBR承载以及重建立哪些非 GBR承载的策略由运营商预先配置在 PCRF 中， 或预先配置在策略和计费执行功能实体（PCEF， Policy and Charging Enforcement Function ) 中， 还可以预先配置在用户策略签约数据库（ SPR， Subscription Profile Repository ) 中。 用户在附着过程中， 由 PCRF、 或 PCEF、 或 SPR将预配置的策略发送至 MME保存。后续 MME接收到 UE发来的 service request请求消息后， 根据保存的用户签约信息来决定是否为用户重建立非 GBR承载以及重建立哪些非 GBR承载。
如图 10所示， 为用户在附着过程中， SPR或 PCRF将预配置的策略信息 发送至 MME保存的处理实施例示意图， 其具体的处理过程如下：
步骤 71. UE发送附着请求（ Attach Request ) 消息到 MME。
步骤 72. MME发送创建承载上下文请求（ Create Bearer Context Request ) 消息到 Serving SAE Gateway, 以请求 Serving SAE Gatewa 创建 SAE承载。
步骤 73. Serving SAE Gateway发送创建承载上下文请求（Create Bearer Context Request ) 消息到 PDN SAE Gateway, 以请求 PDN SAE Gateway创建 SAE承载。
步骤 74. PDN SAE Gateway发送请求策略和计费规则（ Request Policy and Charging Rules ) 消息到 PCRF。
如果 PCRF中存在预先为用户配置的非 GBR承载重建立策略， 则在后续 步骤 77中， 将预配置的策略通过策略和计费规则供应 ( Policy and Charging Rules Provision )消息返回给 PDN SAE Gateway; 如果 PCRF中不存在用户的 签约数据， 则在步骤 75中， PCRF发送签约数据请求（Profile Request ) 消息 到 SPR, 其中 SPR中存储有 PCRF需要使用的策略和计费相关的签约数据， 进而获取用户的签约数据。
步骤 76. SPR返回签约数据响应 （ Profile Response ) 消息给 PCRF, 其中 携带用户的签约数据， 用户的签约数据中可以包括运营商为用户预先配置的 非 GBR承载重建立策略。
步骤 77. PCRF 回策略和计费规则供应 （Policy and Charging Rules Provision )消息到 PDN SAE Gateway, 该回复消息中携带用户的非 GBR承载 重建立策略。 其中有关非 GBR承载的重建立过程同上述第一实施例中的步骤 13 ~ 18, 这里不再给以过多赘述。
即非 GBR承载重建立策略可以预先在 PCRF中配置， 也可以预先在 SPR 中配置， 在签约数据响应消息中由 SPR携带给 PCRF。
步骤 78. PDN SAE Gateway 回复创建承载上下文响应 （Create Bearer Context Response ) 消息给 Serving SAE Gateway, 该回复消息中携带 UE的非 GBR承载重建立策略。 当然非 GBR承载重建立策略也可以在 PDN SAE Gateway 中给予配置， 由 PDN SAE Gateway 通过 Create Bearer Context Response消息携带给 Serving SAE Gateway。
步骤 79. Serving SAE Gateway回复创建承载上下文响应 （Create Bearer Context Response ) 消息给 MME, 消回复消息中携带 UE的非 GBR承载重建 立策略。
步骤 80. MME保存接收到的 Create Bearer Context Response消息中包含 的非 GBR承载重建立策略， 并发起无线承载建立处理过程， 以建立 SAE承 载对应的无线接入承载。 这部分处理过程为公知技术， 这里不再做详细阐述。
步骤 81. MME回复附着接受（ AttachAccept ) 消息到 UE。
其中在本实施例中， 承载创建处理过程 (步骤 2 ~ 10 )与用户的附着处理 过程没有肘序的先后关系，承载创建处理过程可以在附着处理过程中完成（如 创建缺省 SAE承载），也可以在附着完成后再进行承载创建处理（如建立信令 承载 )。 后续 MME在接收到 UE发来的请求消息后 （包括 Service Request消息或 TAU Request消息）， 如果接受该业务请求或跟踪区更新请求， 则回复业务接 受消息或跟踪区更新接受消息给 UE，并根据保存的非 GBR承载重建立策略， 确定需要重建立哪些非 GBR承载。 其中有关非 GBR承载的重建立过程同上 述第一实施例中的步骤 13 ~ 18， 这里不再给以过多赘述。
对于非 GBR承载的重建立原理也可以应用到 GBR承载的重建立， 如对 于视频终端而言， 这些终端一般具有信令承载和一个 GBR承载， 信令承载用 来进行视频业务会话建立流程， GBR承载用来传输视频业务流。用户处在 Idle 状态时信令承载和 GBR承载都将被释放。 对于这样的终端， 进行视频业务会 话建立的同时就存在视频业务流的处理， 所以对于这样的终端， 可以配置重 建立所有承载的策略。 这样终端从 Idle状态切换到 Active状态时， 按照预先 配置的承载重建立策略， 网络侧将为用户重建立信令承载和 GBR承载， 用户 在信令承载上完成视频业务会话建立流程后， 就可以在重建立的 GBR承载上 进行视频业务流的处理， 这样也可以加快视频业务的接入， 增强用户使用体 验。 .
上述在 SAE通信***中， 根据承载重建立策略来决定重建立哪些承载的 方案也可以应用到通用分组无线业务 ( GPRS, General Packet Radio Service ) ***中， 例如在 UE从 Idle状态切换到 Active状态过程中， 服务 GPRS支持 节点（SGSN, Serving GPRS Supporting Node )可以根据为用户预设的承载重 建立策略， 来为 UE重建立对应的无线接入承载。
基于上述方法实施原理， 本发明实施例还提出一种演进网络中的移动性 管理设备（如 SAE***中的 MME, 或 GPRS***中的 SGSN等）， 其中包括 用于获得预先配置的承载重建立策略的单元， 和用于根据预先配置的承载重 建立策略指示接入网建立对应接入侧承载的单元。 MME上还可以进而包括存 储有预先配置的承载重建立策略的单元，这样 MME可以根据本身存储的策略 确定重建立哪些承载资源； 或者用于获得策略的单元还可以通过接收外界网 元设备发来的预先配置的承载重建立策略来实现获得对应的承载重建立策 略。
对应的提出一种演进网络中的网元设备， 包括用于存储预先配置的承载 重建立策略的单元； 和用于将存储的承载重建立策略通知给核心网中 MME 的单元。其中这里的网元设备可以为 UE,也可以为核心网中的 HSS、或 PCRF、 或 PCEF, 或 SPR等。
基于上述方法实施原理， 本发明实施例还提出了第二种演进网络中的移 动性管理设备， 包括用于在用户由 Idle状态切换到 Active状态过程中， 指示 接入网建立所有的非 GBR接入侧承载的单元， 这个移动性管理设备用在没有 预先为用户配置承载重建立策略的情况下， 移动性管理设备（如 MME )在用 户由 Idle状态切换到 Active状态过程中， 会默认为用户重建立所有的非 GBR 承载资源。 同理这个移动性管理设备也可以但不限于为 SAE***中的 MME, 或 GPRS***中的 SGSN。
上述移动性管理设备和相关网元设备中包含的功能组成部分可以由相应 的软件程序来实现， 也可以基于对相关硬件组件进行升级改进来实现。
综上所述， 本发明实施例在用户从 Idle状态切换到 Active状态过程中， 网络侧可以根据预先配置的承载重建立策略为用户重建立相应的承载资源， 因此可以实现一次性地为用户重建立非 GBR承载， 这样用户在后续需要使用 这些非 GBR承载建立业务流程时， 可以直接使用已经重建立好的非 GBR承 载， 因此可以较好的提高业务启动速度， 减少业务流程的建立时间。 此外预 先重建立的非 GBR承载在没有数据传输时也不会占用网络传输资源。对于根 据预先配置的承载重建立策略为用户预先建立 GBR承载资源的情况也可以进 而提高业务的启动速度。 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种实现承载重建立的方法， 其特征在于， 包括步骤：
在用户由空闲状态切换到激活状态过程中， 核心网才 据预先配置的承载 重建立策略指示接入网建立对应的接入侧承载；
接入网按照核心网的指示建立对应的接入侧承载。
2、 如权利要求 1所述的方法， 其特征在于， 由核心网中的移动性管理实 体指示接入网建立对应的接入侧承载。
3、 如权利要求 2所述的方法， 其特征在于， 所述承载重建立策略预先配 置在用户设备侧；
所述用户设备将预先配置的策略携带在请求消息中上报给移动性管理实 体。
4、 如权利要求 2所述的方法， 其特征在于， 所述承载重建立策略预先配 置在移动性管理实体中。
5、 如权利要求 2所述的方法， 其特征在于， 所述承载重建立策略预先配 置在归属用户服务器中；
所述归属用户服务器通过位置更新过程将预先配置的策略通知给移动性 管理实体。
6、 如权利要求 2所述的方法， 其特征在于， 所述承载重建立策略预先配 置在策略和计费规则功能实体中， 或预先配置在策略和计费执行功能实体中， 或预先配置在用户策略签约数据库中；
所述策略和计费规则功能实体、 或策略和计费执行功能实体、 或用户策 略签约数据库在创建承载过程中将预先配置的策略通知给移动性管理实体。
7、 如 1 - 6任意权利要求所述的方法， 其特征在于， 所述承载重建立策 略为：
重建立缺省***架构演进承载； 或
重建立所有非保证比特率承载； 或 重建立附着时预建立的非保证比特率承载； 或
重建立所有承载。
8、 如权利要求 2所述的方法， 其特征在于， 由移动性管理实体指示接入 网中的演进 NodeB建立对应的接入侧承载；
演进 NodeB建立对应接入侧承载包括： 建立自身和用户设备之间的对应 无线承载， 及建立自身和用户面实体之间的对应无线接入承载。
9、 一种移动性管理设备， 其特征在于， 包括：
用于获得预先配置的承载重建立策略的单元；
用于在用户由空闲状态切换到激活状态过程中， 才艮据预先配置的承载重 建立策略指示接入网建立对应接入侧承载的单元。
10、 如权利要求 9所述的设备， 其特征在于， 还包括存储有预先配置的 承载重建立策略的单元；
所述用于获得策略的单元从自身存储有策略的单元中获得预先配置的承 载重建立策略。
11、 如权利要求 9所述的设备， 其特征在于， 所述用于获得策略的单元 通过接收外界网元设备发来的预先配置的承载重建立策略来实现获得所述策 略。
12、 如权利要求 9、 10或 11所述的设备， 其特征在于， 所述移动性管理 设备为：
***架构演进网络中的移动性管理实体 MME; 或
通用分组无线业务***中的服务 GPRS支持节点。
13、 一种网元设备， 其特征在于， 包括：
用于存储预先配置的承载重建立策略的单元；
用于将存储的承载重建立策略通知给核心网中的移动性管理实体的单 元。
14、 如权利要求 13所述的设备， 其特征在于， 所述设备为：
用户设备； 或 核心网中的归属用户服务器、 或策略和计费规则功能实体、 或策略和计 费执行功能实体、 或用户策略签约数据库。
15、 一种实现承载重建立的方法， 其特征在于， 包括步骤：
在用户由空闲状态切换到激活状态过程中， 核心网指示接入网建立所有 的非保证比特率接入侧承载；
接入网按照核心网的指示建立所有非保证比特率接入侧承载。
16、 如权利要求 15所述的方法， 其特征在于， 由核心网中的移动性管理 实体指示接入网中的演进 NodeB建立所有的非保证比特率接入側承载；
演进 NodeB建立所有的非保证比特率接入侧承载包括： 建立自身和用户 设备之间的所有非保证比特率无线承载， 及建立自身和用户面实体之间的所 有非保证比特率无线接入承载。
17、 一种移动性管理设备， 其特征在于， 包括： 用于在用户由空闲状态 切换到激活状态过程中， 指示接入网建立所有的非保证比特率接入侧承载的 单元。
18、 如权利要求 17所述的设备， 其特征在于， 所述移动性管理设备为： ***架构演进网络中的移动性管理实体 MME; 或
通用分组无线业务***中的服务 GPRS支持节点。
PCT/CN2008/000495 2007-03-23 2008-03-13 Procédé et dispositif correspondant pour le rétablissement d'un support de transmission WO2008116378A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007100871981A CN101272600B (zh) 2007-03-23 2007-03-23 实现承载重建立的方法、及其相关设备
CN200710087198.1 2007-03-23

Publications (1)

Publication Number Publication Date
WO2008116378A1 true WO2008116378A1 (fr) 2008-10-02

Family

ID=39788035

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/000495 WO2008116378A1 (fr) 2007-03-23 2008-03-13 Procédé et dispositif correspondant pour le rétablissement d'un support de transmission

Country Status (2)

Country Link
CN (1) CN101272600B (zh)
WO (1) WO2008116378A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182233A3 (en) * 2013-05-08 2015-02-19 Telefonaktiebolaget L M Ericsson (Publ) Packet data transfer re-establishment
WO2018119559A1 (zh) * 2016-12-26 2018-07-05 华为技术有限公司 一种通信接口故障的处理方法和装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196562B (zh) * 2010-03-04 2015-05-06 电信科学技术研究院 触发条件通知方法及装置
CN102196563B (zh) * 2010-03-04 2014-12-24 电信科学技术研究院 触发条件通知方法和装置
EP3567977B1 (en) * 2012-06-28 2022-07-20 Huawei Technologies Co., Ltd. Downlink data transmission method, base station, and network
US10206144B2 (en) 2014-03-04 2019-02-12 Telefonaktiebolaget Lm Ericsson (Publ) Scheduling based on data traffic patterns
CN108617034B (zh) * 2016-12-30 2021-02-23 华为技术有限公司 终端的连接态控制方法、设备及***
CN109392042B (zh) * 2017-08-14 2021-10-26 华为技术有限公司 一种会话管理方法、异***互操作的方法及网络装置
CN109845320B (zh) * 2018-02-09 2020-12-04 Oppo广东移动通信有限公司 基于业务质量进行数据传输的方法和设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1893428A (zh) * 2005-11-29 2007-01-10 华为技术有限公司 媒体网关控制协议的承载***及其方法
EP1745668A1 (en) * 2004-05-13 2007-01-24 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Reestablishing wireless communication between a radio access network and a mobile station
CN1910839A (zh) * 2004-01-09 2007-02-07 Lg电子株式会社 用于建立移动终端的无线承载的装置和方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100563254C (zh) * 2006-03-21 2009-11-25 华为技术有限公司 一种演进网络中漫游用户数据路由方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1910839A (zh) * 2004-01-09 2007-02-07 Lg电子株式会社 用于建立移动终端的无线承载的装置和方法
EP1745668A1 (en) * 2004-05-13 2007-01-24 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Reestablishing wireless communication between a radio access network and a mobile station
CN1893428A (zh) * 2005-11-29 2007-01-10 华为技术有限公司 媒体网关控制协议的承载***及其方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014182233A3 (en) * 2013-05-08 2015-02-19 Telefonaktiebolaget L M Ericsson (Publ) Packet data transfer re-establishment
US9999086B2 (en) 2013-05-08 2018-06-12 Telefonaktiebolaget L M Ericsson (Publ) Packet data transfer re-establishment
WO2018119559A1 (zh) * 2016-12-26 2018-07-05 华为技术有限公司 一种通信接口故障的处理方法和装置

Also Published As

Publication number Publication date
CN101272600A (zh) 2008-09-24
CN101272600B (zh) 2012-12-12

Similar Documents

Publication Publication Date Title
WO2008116378A1 (fr) Procédé et dispositif correspondant pour le rétablissement d'un support de transmission
FI110563B (fi) Resurssien varaus pakettimuotoisessa tiedonsiirrossa
JP5373404B2 (ja) 通信のための方法と装置
KR101457823B1 (ko) 모바일 무선 장치에서 네트워크 혼잡 동안의 무선 자원 재설정 시그널링
CN107005930B (zh) 一种寻呼用户设备的方法和mme
WO2009097818A1 (zh) 一种用户设备紧急接入的方法、设备和***
WO2013064104A1 (zh) 一种数据传输方法、移动性管理实体和移动终端
JP2004507932A (ja) パケット無線サービスにおける情報転送の改良された方法及び装置
WO2011134329A1 (zh) 一种小数据包传输的方法和***
WO2013053339A2 (zh) 传输速率控制方法、移动性管理实体和通讯***
WO2020173137A1 (zh) 一种数据传输方法、相关设备、程序产品以及存储介质
WO2014005536A1 (zh) 临近终端的通信方法及装置、***
KR20170132249A (ko) 사용자 플레인 베어러 확립을 제어하는 방법 및 장치
KR20080096875A (ko) 이동통신 시스템의 무선자원 할당 제어방법
WO2008014684A1 (fr) Procédé permettant la mise en oeuvre de l'équilibrage des charges
WO2010111814A1 (zh) 用于以最小包损失移动wcdma移动台的装置和方法
WO2015013869A1 (zh) 传输机制的转换方法、用户设备以及基站
WO2021083353A1 (zh) 连接处理方法及通信设备
WO2012097706A1 (zh) 一种承载修改的***及方法
WO2005079138A2 (en) Enhancement of dual transfer mode when circuit switched resources are released
CN103096391B (zh) 多pdn连接下资源优化的方法及装置
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
WO2012024989A1 (zh) 承载释放方法及***
WO2008154783A1 (fr) Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service
WO2009067912A1 (fr) Procédé et dispositif de commutation pour mettre en œuvre une commutation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08714948

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08714948

Country of ref document: EP

Kind code of ref document: A1