WO2011097813A1 - 去激活isr的方法、修改承载参数的方法和网络*** - Google Patents
去激活isr的方法、修改承载参数的方法和网络*** Download PDFInfo
- Publication number
- WO2011097813A1 WO2011097813A1 PCT/CN2010/070666 CN2010070666W WO2011097813A1 WO 2011097813 A1 WO2011097813 A1 WO 2011097813A1 CN 2010070666 W CN2010070666 W CN 2010070666W WO 2011097813 A1 WO2011097813 A1 WO 2011097813A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bearer
- parameter
- terminal
- mme
- sgsn
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Definitions
- the present invention relates to mobile communication technologies, and in particular, to a method for deactivating an ISR, a method for modifying a bearer parameter, and a network system. Background technique
- UE User Equipment
- UTRAN Universal Terrestrial Radio Access Network
- GSM Global System for Mobile Global System for Mobile. Communications
- EDGE Enhanced Data Rate for GSM Evolution
- GSM GSM Radio Access Network GERAN
- EPC Evolved Packet Core
- the EPC mainly includes the following network elements: Packet Data Network (PDN) Gateway (PDN Gateway, PGW), Serving Gateway (SGW), Mobile Management Entity (MME), General Packet Radio Service (General Packet Radio Service (GPRS) Service Serving GPRS Support Node (SGSN) and Policy and Charging Rule Function (PCRF) to implement data transmission between the UE and the packet data network.
- PGW Packet Data Network
- SGW Serving Gateway
- MME Mobile Management Entity
- MME General Packet Radio Service
- GPRS General Packet Radio Service
- SGSN Service Serving GPRS Support Node
- PCRF Policy and Charging Rule Function
- the MME mainly completes the mobility management, session management, and non-access stratum (NAS) signaling encryption and integrity protection of the UE under E-UTRAN access; when the UE is in the idle (Idle) state, the MME The bearer context information can be saved.
- the SGSN mainly performs functions such as mobility management and session management of the UE under GERAN/UTRAN access; when the UE is in Idle In the state, the SGSN can save the bearer context information.
- the PCRF is mainly used to implement policy charging control. When the UE uses different radio access technologies, the idle state corresponding to the UE can be classified into three cases.
- the corresponding idle state is represented by ECM-IDLE; in this state, the UE and the MME save the user context, where the user context includes the mobility context and the bearer context.
- the corresponding idle state is represented by GPRA STANDBY or PMM-IDLE; in this state, the UE and the SGSN save the user context, and the user context includes the mobility context and the bearer context.
- the Idle Mode Signaling Reduction is a mechanism for reducing signaling interaction provided when the UE in the idle state reselects the radio access technology.
- the radio access technology includes E-UTRAN and GERAN/UTRAN.
- the ISR includes an active state and a deactivated state.
- the user context is only saved in the MME or SGSN on the network side.
- the bearer parameters need to be modified, the bearer parameters need only be modified on the side with the bearer context, and no synchronization between the MME and the SGSN is required.
- the user context is saved in both the MME and the SGSN on the network side. If the bearer parameters need to be modified, the MME and the SGSN need to be modified, that is, the MME and the SGSN are required to synchronize.
- a location update is initiated, where the location update procedure uses the identity identifier corresponding to the reselected access network, for example, when re-selecting the E-UTRAN, Globally Unique Temporary Identity (GUTI), when GERAN/UTRAN is reselected, Packet Temporary Mobile Subscriber Identity (P-TMSI) is used. Since the re-selected access network corresponding identifier is used, the reselected mobility management network element (MME or SGSN, ie, core network management device) does not perform mobility management corresponding to another access technology. The network element (SGSN or MME) synchronizes bearer context information.
- GUI Globally Unique Temporary Identity
- P-TMSI Packet Temporary Mobile Subscriber Identity
- a location update is initiated, where the location update procedure uses the corresponding identity of the access network before the reselection, for example, when the E-UTRAN is reselected, the P is carried.
- -TMSI when GERAN/UTRAN is reselected, GUTL is used because the identifier corresponding to the access network before reselection is used, so the mobility tube after reselection
- MME mobility management network element
- the activation process of the ISR is completed by the parameters in the Acceptance message of the Routing Area Update (RAU) or the Tracking Area Update (TAU) process.
- the UE changes the status to "ISR activated".
- the UE is informed of the bearer context modification, for example, the UE is notified to modify the Access Point Name Aggregate Maximum Bit Rate (APN-AMBR), the Traffic Flow Template (TFT), the Quality of Service Category.
- APN-AMBR Access Point Name Aggregate Maximum Bit Rate
- TFT Traffic Flow Template
- the UE will deactivate the ISR, such as the Quality of Service Class Identifier (QCI), the Guaranteed Bit Rate (GBR), and the Maximum Bit Rate (MBR).
- QCI Quality of Service Class Identifier
- GRR Guaranteed Bit Rate
- MRR Maximum Bit Rate
- the Allocation and Retention Priority is used to indicate the ability of bearers of different priorities to preempt resources when the bearer resources are insufficient. This parameter has no meaning for the UE, so it is not necessary to notify the UE, and only needs to notify the network element of the radio access side, such as a Radio Access Network (RAN) or an evolved base station (eNodeB), the radio access side.
- the network element performs resource preemption and release according to the priority.
- the embodiment of the present invention provides a method for deactivating an ISR, a method for modifying a bearer parameter, and a network system, so that the ISR can be deactivated when the bearer parameter to be modified is only an APR parameter.
- An embodiment of the present invention provides a method for deactivating an ISR, including:
- the network side device When the ISR is in an active state and the network side device detects that the bearer parameter to be modified is only the allocation and retention priority ARP parameter, the network side device adds the terminal related bearer parameter to the first update bearer request; The network side device routes the terminal-related bearer parameters carried in the first update bearer request to the terminal through the access network device, so that the terminal activates the ISR after receiving the terminal-related bearer parameters.
- An embodiment of the present invention provides a method for modifying a bearer parameter, including:
- the serving gateway SGW receives the first update bearer request sent by the packet data network gateway PGW, and the bearer parameter to be modified carried in the first update bearer request is only the updated allocation and hold priority ARP parameter;
- the SGW sends a second update bearer request to the first mobility management entity MME and the first general packet radio service support node SGSN, where the second update bearer request carries the
- the updated ARP parameter is configured to enable the first MME and the first SGSN to modify the ARP parameters saved by themselves to the updated ARP parameters.
- the embodiment of the invention provides a network side device, including:
- Adding a module when the idle state signaling reduces the ISR to be in an active state, and the network side device detects that the bearer parameter to be modified is only the allocation and holding priority ARP parameter, adding the terminal related bearer parameter to the first update bearer request;
- a sending module configured to route the terminal-related bearer parameter carried in the first update bearer request to the terminal by using the access network device, so that the terminal activates the ISR after receiving the terminal-related bearer parameter.
- the embodiment of the invention provides a network system, including:
- the serving gateway SGW is configured to add the terminal-related bearer parameter to the first update bearer request when the idle state signaling reduces the ISR to be in an active state and detects that the bearer parameter to be modified is only the allocation and holding priority ARP parameter;
- the core network management device is configured to receive the first update bearer request, and send the terminal related bearer parameter to the terminal by using the access network device, so that the terminal deactivates after receiving the terminal related bearer parameter.
- ISR the terminal-related bearer parameter to enable the UE to deactivate the ISR, or causes the SGW to send the updated ARP to both the MME and the SGSN.
- the update bearer message of the parameter provides a basis for realizing synchronization between the MME and the SGSN.
- FIG. 1 is a schematic flow chart of a method according to a first embodiment of the present invention
- FIG. 2 is a schematic flow chart of a method according to a second embodiment of the present invention.
- FIG. 3 is a schematic flow chart of a method according to a third embodiment of the present invention.
- FIG. 4 is a schematic flow chart of a method according to a fourth embodiment of the present invention.
- FIG. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention.
- FIG. 6 is a schematic flow chart of a method according to a sixth embodiment of the present invention.
- FIG. 7 is a schematic flow chart of a method according to a seventh embodiment of the present invention.
- FIG. 8 is a schematic flow chart of a method according to an eighth embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of a network side device according to a ninth embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of a network system according to a tenth embodiment of the present invention. detailed description
- the ARP parameter does not notify the UE. Therefore, for the user who activates the ISR, after modifying the ARP parameter, the UE cannot know the ISR and will not deactivate the ISR. At this time, the modification of the bearer parameters can only be modified in the MME or the SGSN, but cannot be modified simultaneously in the MME and the SGSN, and the synchronization between the MME and the SGSN cannot be implemented.
- the embodiment of the present invention provides a scheme to deactivate the ISR when the ISR is in an active state and only needs to modify the ARP parameters, so as to provide a basis for implementing synchronization between the SGSN and the MME.
- FIG. 1 is a schematic flowchart of a method according to a first embodiment of the present invention, including:
- Step 11 When the ISR is in the active state and the network side device detects that the bearer parameter to be modified is only the ARP parameter, the network side device adds the terminal related bearer parameter to the first update bearer request.
- Step 12 The network side device routes the terminal-related bearer parameters carried in the first update bearer request to the terminal by using the access network device, so that the terminal activates the ISR after receiving the terminal-related bearer parameters. .
- the network side device is an SGW or a core network management device.
- the core network management device is an MME
- the corresponding access network device is an eNodeB
- the core network management device is an SGSN
- the corresponding access network device is a RAN. .
- the terminal related bearer parameters include at least one of the following: TFT, APN-AMBR, QCI, Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), or a new one for deactivating the ISR. Instructions. After receiving the terminal-related bearer parameters, the terminal deactivates the ISR regardless of whether the terminal-related bearer parameters are modified.
- the terminal-related bearer parameter is a bearer parameter that needs to be sent to the UE.
- the network side device when the ISR is in the active state and the network side device detects that the bearer parameter to be modified is only the allocation and holding priority ARP parameter, the network side device adds the terminal related bearer parameter, and routes the terminal related bearer parameter. To the terminal, the UE can be deactivated.
- the network side device is a serving gateway SGW: the network side device routes the terminal related bearer parameter carried in the first update bearer request to the terminal by using the access network device to: The SGW sends the first update bearer request to the core network management device, where the core network management device is configured to send the terminal related bearer parameter to the terminal by using the access network device.
- the method further includes: the SGW receiving the second update bearer request sent by the packet data network gateway (PGW), and the bearer parameter to be modified carried in the second update bearer request is only the updated ARP parameter. .
- PGW packet data network gateway
- the core network management device is the mobility management entity MME
- the first update bearer request further includes the updated ARP parameter
- the SGW sends the first update bearer request to the core network management device.
- the method further includes:
- the MME modifies the ARP parameter saved by itself to the updated ARP parameter; after the terminal reselects the GERAN/UTRAN access network, the general packet radio service support node in the GERAN/UTRAN access network Receiving, by the SGSN, a location update request sent by the terminal, when detecting that the ISR is in a deactivated state, sending a context request to the MME; the SGSN receiving a context response returned by the MME, where the context response carries the update After ARP parameters;
- the SGSN modifies the ARP parameter saved by itself to the updated ARP parameter.
- the core network management device is an SGSN
- the first update bearer request further includes an updated ARP parameter
- the SGW sends the first update bearer request to the core network management device
- the method further includes: modifying, by the SGSN, the ARP parameter saved by itself to the updated ARP parameter; after the terminal reselects the E-UTRAN access network of the evolved universal terrestrial radio access network, the E- The MME in the UTRAN access network receives the location update request sent by the terminal, and checks Sending a context request to the SGSN when the ISR is determined to be in a deactivated state;
- the MME modifies the ARP parameter saved by itself to the updated ARP parameter.
- the core network management device is the MME or the SGSN
- the specific steps respectively provide a specific manner for the SGSN to synchronize with the MME after the UE re-accesses the network, so that the bearer context between the SGSN and the MME is kept synchronized.
- the network side device is a core network management device: the adding, by the network side device, the terminal related bearer parameter to the first update bearer request includes: adding, by the core network management device, a terminal related bearer The parameter is sent to the bearer modification request; the network side device routing the terminal-related bearer parameter carried in the first update bearer request to the terminal by using the access network device, and the core network management device sends the bearer modification request And the access network device sends the terminal related bearer parameters to the terminal by using the access network device.
- the method further includes: the core network management device receiving the update bearer request sent by the serving gateway SGW, where the update bearer request sent by the SGW is carried
- the bearer parameters that need to be modified are only the updated ARP parameters.
- the method further includes: modifying, by the MME, the ARP parameter saved by the MME to The updated ARP parameter; after the terminal reselects the universal terrestrial radio access network or the global mobile communication system GSM/enhanced data rate GSM evolved EDGE radio access network GERAN/UTRAN access network, the GERAN/ General Packet Radio Service Support Node SGSN in the UTRAN Access Network Receiving a location update request sent by the terminal; after receiving the location update request, the SGSN sends a context request to the MME;
- the SGSN modifies the ARP parameter saved by itself to the updated ARP parameter.
- the method further includes: the SGSN modifying the ARP parameter saved by itself to the update After the terminal reselects the evolved universal terrestrial radio access network E-UTRAN access network, the MME in the E-UTRAN access network receives the location update request sent by the terminal; After receiving the location update request, sending a context request to the SGSN;
- the MME modifies the ARP parameter saved by itself to the updated ARP parameter.
- the core network management device is the MME or the SGSN
- the specific steps respectively provide a specific manner for the SGSN to synchronize with the MME after the UE re-accesses the network, so that the bearer context between the SGSN and the MME is kept synchronized.
- Step 21 A serving gateway SGW receives a first update bearer request sent by a packet data network gateway (PGW), and a bearer to be modified carried in the first update bearer request
- PGW packet data network gateway
- the parameters are only the updated allocation and retention priority ARP parameters
- Step 22 When the idle state signaling reduces the ISR to be in an active state, the SGW moves to the first The MME and the first general packet radio service support node SGSN send a second update bearer request, where the second update bearer request carries the updated ARP parameter, so that the first MME and the first SGSN Modify the ARP parameters saved by itself to the updated ARP parameters.
- the SGW when the ISR is in an active state, when the SGW detects that the bearer parameter to be modified is only the updated allocation and hold priority ARP parameter, the SGW sends the updated ARP parameter to the MME and the SGSN, thereby After the UE is reselected to access the network, it can be ensured that the MME and the SGSN before and after the synchronization keep the parameters synchronized.
- the embodiment of the present invention may further include the following steps: when the terminal reselects E - When the UT is connected to the network and the reselected MME is different from the first MME, the reselected MME obtains the updated ARP from the first MME; or
- the reselected SGSN obtains the updated ARP from the first SGSN.
- the parameter synchronization can be guaranteed even when the core network management device changes after re-accessing the network.
- FIG. 3 is a schematic flowchart of a method according to a third embodiment of the present invention.
- an SGW adds a bearer parameter as an example
- an application scenario of the embodiment is reselecting from an E-UTRAN access network to a GERAN/UTRAN access network. See Figure 3, including:
- Step 301 The PGW initiates a bearer context ARP parameter modification process, and sends an update bearer request (Update Bearer Request) to the SGW, where the update bearer request message carries the 7-digit identifier for determining the modification and the updated ARP parameter.
- update bearer request (Update Bearer Request)
- Step 302 After receiving the update bearer request sent by the PGW, the SGW determines whether the ARP needs to be modified only according to the parameters carried in the update bearer request, and only needs to modify the ARP and the ISR is in the When the state is activated, the SGW adds the bearer parameters that need to be sent to the UE to the update bearer request.
- the update bearer modification request does not carry the bearer parameter that needs to be sent to the UE, but only includes the ARP, it indicates that only the ARP needs to be modified.
- the update bearer request also carries the bearer parameter that needs to be sent to the UE, it indicates that the ARP is not only required to be modified.
- Whether the ISR is in the active state is determined by the network side and notifies the UE. Therefore, the SGW can learn whether the ISR is in an active state.
- the existing technology can be used as for how the network side determines whether the ISR is activated. This embodiment is not particularly concerned.
- the added bearer parameter that needs to be sent to the UE may be at least one of the following: TFT, APN-AMBR, QCI, GBR, MBR, or an additional indication for deactivating the ISR.
- Step 303 The SGW adds an update bearer request that needs to be sent to the UE, and sends the update bearer request to the MME.
- Step 304 The MME modifies the ARP, and establishes a session management request, and sends the session management request to the eNodeB, which carries the ARP and the added bearer parameters that need to be sent to the UE.
- Step 305 The eNodeB modifies the ARP, and then sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE to establish a radio side bearer. And carrying the Session Management Request in the RRC connection reconfiguration message.
- RRC Connection Reconfiguration RRC Connection Reconfiguration
- Step 306 After receiving the RRC connection reconfiguration message, the UE deactivates the ISR regardless of whether the parameter carried in the UE is modified.
- Step 307 The UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the eNodeB to confirm the tampering of the radio.
- RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
- Step 308 The eNodeB sends a Bearer Modify Response to the MME to confirm the modification of the radio bearer.
- Step 309 The NAS layer of the UE establishes a session management response, where the session management response includes an EPS bearer identifier. Thereafter, the UE sends a Direct Transfer message to the eNodeB, where the direct transfer message includes a session management response.
- Step 311 After receiving the bearer modification response of step 308 and the session management response of step 310, the MME sends an Update Bearer Response to the SGW as an acknowledgement of the bearer tampering.
- Step 312 The SGW sends an update bearer response to the PGW as a response to the bearer modification.
- Step 314 The UE sends a Location Update Request to the SGSN in the GERAN/UTRAN access network to initiate a location update process, where the location update request may carry the GUTI.
- Step 315 After receiving the location update request, the SGSN performs a location update process.
- the context request is sent to the MME according to the value of the GUTI carried in the location update request to synchronize the bearer context.
- Step 316 After receiving the context request, send the bearer context to the SGSN by using a context response (Context), where the bearer context includes the modified ARP.
- Context context response
- Step 317 After completing the bearer context synchronization and location update related operations, the SGSN sends a Routing Area Update Response to the UE to notify the UE that the location update process ends.
- This embodiment takes an example from E-UTRAN reselection to GERAN/UTRAN. It can be understood that the above principle can also be applied to the scenario from GERAN/UTRAN reselection to E-UTRAN. In this case, the above needs to be The operation performed by the MME and the SGSN is interchanged, and the operation performed by the eNodeB is replaced with the operation performed by the RAN, and the GUTI described above is replaced with the P-TMSL.
- the SGW adds other bearer parameters that need to be sent to the UE, so that the UE can deactivate the ISR.
- the MME updates the ARP parameter stored by the MME according to the updated ARP parameter included in the bearer update request sent by the SGW.
- the SGSN in the access network may Obtained from MME
- the updated ARP parameters are described, thereby implementing synchronization between the MME and the SGSN.
- the scenario in which the SGW adds the bearer parameter to the E-UTRAN access network or the GERAN/UTRAN access network is not limited to the application scenario, and the applicability is improved.
- FIG. 4 is a schematic flowchart of a method according to a fourth embodiment of the present invention.
- an MME adds a load parameter as an example. See Figure 4, including:
- Step 401 Corresponding to step 301.
- Step 402 The SGW sends an update bearer request received from the PGW to the MME.
- Step 403 After receiving the update bearer request sent by the SGW, the MME modifies the ARP. And determining, according to the parameters carried in the update bearer request, whether to modify the ARP only. When the ARP needs to be modified and the ISR is in the active state, the MME adds the bearer parameter that needs to be sent to the UE to the update bearer request.
- the update bearer modification request does not carry the bearer parameter that needs to be sent to the UE, but only includes the updated ARP, it indicates that only the ARP needs to be modified.
- the update bearer request also carries the bearer parameter that needs to be sent to the UE, it indicates that the ARP is not only required to be modified.
- Whether the ISR is in the active state is determined by the network side and notified to the UE. Therefore, the SGW can learn whether the ISR is in an active state.
- the existing technology can be used as for how the network side determines whether the ISR is activated. This embodiment is not particularly concerned.
- the added bearer parameter that needs to be sent to the UE may be at least one of the following: TFT, APN-AMBR, QCI, GBR, MBR or an additional indication for deactivating the ISR.
- Step 404 The MME establishes a session management request (Session Management Request), and sends the bearer modification request (Bearer Modify Request) to the eNodeB, where the ARP and the added bearer parameters that need to be sent to the UE are carried.
- Session Management Request Session Management Request
- Bearer Modify Request the bearer modification request
- Steps 405-417 Corresponding to steps 305-317.
- the MME adds other bearer parameters that need to be sent to the UE, so that the UE can deactivate the ISR to implement synchronization between the MME and the SGSN.
- This embodiment performs an adding operation by the MME, and can be applied to a scenario from the E-UTRAN access network reselection to the GERAN/UTRAN access network.
- FIG. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention. This embodiment uses an SGSN to add a bearer parameter as an example. See Figure 5, including:
- Step 501 Corresponding to step 301.
- Step 502 The SGW sends an update bearer request received from the PGW to the SGSN.
- Step 503 After receiving the update bearer request sent by the SGW, the SGSN modifies the ARP. And determining, according to the parameter carried in the update bearer request, whether the ARP needs to be modified only. When the ARP needs to be modified and the ISR is in the active state, the SGSN adds the bearer parameter that needs to be sent to the UE to the update bearer request.
- the update bearer modification request does not carry the bearer parameter that needs to be sent to the UE, but only includes the ARP, it indicates that only the ARP needs to be modified.
- the update bearer request further carries the bearer parameter that needs to be sent to the UE, it indicates that the ARP is not only required to be modified.
- Whether the ISR is in the active state is determined by the network side and notifies the UE. Therefore, the SGW can learn whether the ISR is in an active state.
- the existing technology can be used as for how the network side determines whether the ISR is activated. This embodiment is not particularly concerned.
- the added bearer parameter that needs to be sent to the UE may be at least one of the following: TFT, APN-AMBR, QCI, GBR, MBR, or an additional indication for deactivating the ISR.
- Step 504 The SGSN sends a Radio Access Bearer Modification (Radio Access Bearer Modification) message to the RAN, where the MME carries the ARP and the added bearer parameters that need to be sent to the UE.
- Radio Access Bearer Modification Radio Access Bearer Modification
- Step 505 The RAN modifies the ARP, and then sends a Radio Access Bearer Modification message to the UE to establish a radio bearer.
- Step 506 The SGSN sends a Modify Bearer Context Request to the UE.
- Step 507 After receiving the modification bearer context request, the UE deactivates the ISR regardless of whether the parameter carried in the modification is modified.
- Step 508 The UE sends a modify bearer context response to the SGSN (Modify Bearer Context) Respond) to confirm the tampering of the wireless 7- load.
- SGSN Modify Bearer Context
- Step 509 The SGSN sends an Update Bearer Response to the SGW as an acknowledgement of the bearer modification.
- Step 510 The SGW sends an update bearer response to the PGW as a response to the bearer modification.
- Step 512 The UE sends a Location Update Request to the E-UTRAN access network to initiate a location update procedure.
- Step 513 After receiving the location update request, the location update process is performed.
- a context request (Context Request) is sent to the SGSN according to the value of the P-TMSI to synchronize the bearer context.
- Step 514 After receiving the context request, the SGSN sends the bearer context to the MME by using a context response (Context Response), where the bearer context includes the modified ARP.
- Context Response Context Response
- Step 515 After completing the bearer context synchronization and location update related operations, the MME sends a Routing Area Update Response to the UE to notify the UE that the location update process ends.
- the SGSN adds other bearer parameters that need to be sent to the UE, so that the UE can deactivate the ISR to implement synchronization between the MME and the SGSN.
- This embodiment performs an adding operation by the SGSN, and can be applied to a scenario from GERAN/UTRAN reselection to E-UTRAN.
- the third-fifth embodiment is to implement the deactivation of the ISR by adding a bearer parameter, and then after the reselection of the access technology, the synchronization between the SGSN and the MME can be implemented.
- FIG. 6 is a schematic flowchart of a method according to a sixth embodiment of the present invention. See Figure 6, including:
- Step 601 Corresponding to step 301.
- Step 602 After receiving the update bearer request sent by the PGW, the SGW determines whether the ARP needs to be modified only when the ARP is modified, and the ISR is in the In the active state, the SGW determines the first MME and the first SGSN according to the bearer context maintained by the SGW in the ISR activation state, and sends an update bearer request to the first MME and the first SGSN, where the updated ARP is carried.
- the update bearer modification request does not carry the bearer parameter that needs to be sent to the UE, but only includes the ARP, it indicates that only the ARP needs to be modified.
- the update bearer request further carries the bearer parameter that needs to be sent to the UE, it indicates that the ARP is not only required to be modified.
- Whether the ISR is in the active state is determined by the network side and notifies the UE. Therefore, the SGW can learn whether the ISR is in an active state.
- the existing technology can be used as for how the network side determines whether the ISR is activated. This embodiment is not particularly concerned.
- Step 603 After receiving the update bearer request, the first MME, when detecting that the UE is in the idle state (Idle), modifies the ARP in the storage bearer context according to the ARP carried in the update bearer request.
- Step 604 The first MME sends an Update Bearer Response (Update Bearer Response) to the SGW.
- Update Bearer Response Update Bearer Response
- Step 605 After receiving the update bearer request, the first SGSN, when detecting that the UE is in the idle state (Idle), modifies the ARP in the storage bearer context according to the ARP carried in the update bearer request.
- Step 606 The first SGSN sends an Update Bearer Response to the SGW.
- steps 603-604 have no timing constraint relationship with steps 605-606.
- Step 607 SGW carrier 7 after the update in response to receiving an update bearer response to the step 604 and step 606 transmits the transmission, the transmission in response to the PGW carrier 7 to update (Update Bearer Response), as a bearer modification response.
- update Update Bearer Response
- the core network management device may change, and the UE reselects.
- the E-UTRAN access technology is used as an example.
- the process of reselecting the GERAN/UTRAN by the UE is similar to this, and will not be described again.
- This embodiment may further include: Step 608: The UE reselects the E-UTRAN access technology, and when the reselected MME (represented as the second MME) is different from the first MME, the second MME receives the location update request sent by the UE, where the GUTI is carried.
- Step 609 The second MME acquires information of the first MME according to the GUTI, and sends a context request (Context Request) to the first MME.
- Step 610 The first MME returns a context response (Context Response) to the second MME, where the updated ARP is carried. After that, the first MME modifies the ARP saved by itself to the updated ARP.
- Context Response Context Response
- the context information in the old MME and the SGSN may be deleted, so that the latest information is saved in the new MME, and the ISR is deactivated, that is, the method may further include:
- Step 611 The second MME returns an Acknowledge message to the first MME, and then the first MME may delete the bearer context information saved by itself.
- the second MME after updating the bearer parameter, the second MME also sends an indication to the UE to instruct the UE to activate the ISR.
- Step 612 The first MME returns a determination message to the SGW, and the SGW sends an acknowledgement message to the first SGSN, and then the SGSN deletes the bearer context information saved by itself.
- the update bearer message is sent to the MME and the SGSN by using the SGW, and the ARP carrying the context can be modified in both the MME and the SGSN to implement synchronization between the MME and the SGSN. Thereafter, when the UE enters the Connected state, the UE performs bearer context synchronization with the MME or the SGSN to ensure correct execution of the process.
- FIG. 7 is a schematic flowchart of a method according to a seventh embodiment of the present invention.
- a UE is in a connected state on an MME side as an example. See Figure 7, including:
- Steps 701-702 Corresponding to steps 601-602.
- Step 703 After receiving the update bearer request, the MME, when detecting that the UE is in the Connected state, modifies the ARP in the storage bearer context according to the ARP carried in the update bearer request.
- Step 704 The MME sends a session management request to the eNodeB, where the ARP is carried.
- Step 705 The eNodeB modifies the ARP stored by the eNodeB according to the ARP carried in the session management request.
- Step 706 The eNodeB returns a Session Management Response to the MME.
- Step 707 The MME sends an Update Bearer Response to the SGW.
- Step 708 After receiving the update bearer request, the SGSN detects that the UE is in a connected state, and
- the UE performs the service connection on the MME side, instead of performing the service connection on the SGSN side, and modifies the ARP in the storage bearer context according to the ARP carried in the update bearer request.
- Step 709 The SGSN sends an Update Bearer Response to the SGW. It can be understood that steps 703-607 have no timing constraint relationship with steps 708-709.
- Step 710 SGW carrier 7 after updating step in response to receiving an update bearer response 707 transmitted in step 709 and transmitted, transmits the response to the PGW carrier 7 to update (Update Bearer Response), as a bearer modification response.
- update Update Bearer Response
- the core network management device may be changed.
- the processing may be performed as described in steps 608-612, and details are not described herein.
- the SGW sends an update bearer message to the MME and the SGSN, and the ARP carrying the context can be modified in both the MME and the SGSN to implement synchronization between the MME and the SGSN. If the UE enters the idle state and then switches to the SGSN side, the UE will perform bearer context synchronization with the SGSN when the service connection is required, to ensure the correct execution of the process.
- FIG. 8 is a schematic flowchart of a method according to an eighth embodiment of the present invention.
- a UE is in a connected state on an SGSN side as an example. See Figure 8, including:
- Steps 801-802 Corresponding to steps 601-602.
- Step 803 After receiving the update bearer request, the MME detects that the UE is in the connected state, and the UE performs the service connection on the SGSN side, instead of performing the service connection on the MME side, according to the update
- the ARP carried in the request is modified to modify the ARP in the storage bearer context.
- Step 804 The MME sends an Update Bearer Response to the SGW.
- Step 805 After receiving the update bearer request, the SGSN, when detecting that the UE is in the Connected state, modifies the ARP in the context of the self-storage bearer according to the ARP carried in the update bearer request.
- Step 806 The SGSN sends a session management request to the RAN (Session Management
- Step 807 The RAN modifies the ARP stored by itself according to the ARP carried in the session management request.
- Step 809 The SGSN sends an Update Bearer Response to the SGW. Steps 803-804 have no timing constraint relationship with steps 805-809.
- Step 810 After receiving the step 804 to update the 7-load response and the step 809 to update the 7-load response, the SGW sends an Update Bearer Response to the PGW as a response to the bearer modification.
- the core network management device may be changed.
- the processing may be performed as described in steps 608-612, and details are not described herein.
- the SGW sends an update bearer message to the MME and the SGSN, and the ARP carrying the context can be modified in both the MME and the SGSN to implement synchronization between the MME and the SGSN. If the UE enters the idle state and then switches to the MME side, the UE will perform bearer context synchronization with the MME when the service connection is required, so as to ensure the correct execution of the process.
- FIG. 9 is a schematic structural diagram of a network side device according to a ninth embodiment of the present invention, including an adding module 91 and a sending module 92, where the adding module 91 is configured to reduce the ISR in an active state and the network side device detects the need
- the modified bearer parameter is used to add the terminal-related bearer parameter to the first update bearer request only when the priority and the priority ARP parameter are allocated;
- the sending module 92 is configured to: pass the terminal-related bearer parameter carried in the first update bearer request
- the network access device routes to the terminal, So that the terminal deactivates the ISR after receiving the terminal related bearer parameters.
- the network side device is specifically a serving gateway SGW
- the sending module is specifically configured to send the first update bearer request to a core network management device, where the core network management device is used.
- the terminal-related bearer parameters are sent to the terminal by the access network device, so that the terminal deactivates the ISR after receiving the terminal-related bearer parameters.
- the SGW further includes: a receiving module 93, configured to be connected to the adding module 91, configured to receive a second update bearer request sent by the packet data network gateway PGW, where the bearer parameter to be modified carried in the second update bearer request is only For the updated ARP parameters.
- the bearer parameter that needs to be sent to the UE is added by the SGW, so that the UE can deactivate the ISR.
- the bearer context between the SGSN and the MME is synchronized, and synchronization between the SGSN and the MME is implemented.
- the network side device is specifically a core network management device, and the adding module 91 is specifically configured to: when the idle state signaling reduces the ISR being activated, and the core network management device detects the bearer that needs to be modified.
- the parameter is only used to allocate and maintain the priority ARP parameter, and the terminal-related bearer parameter is added to the bearer modification request.
- the sending module 92 is specifically configured to send the bearer modification request to the access network device, and The network access device sends the terminal-related bearer parameters to the terminal, so that the terminal activates the ISR after receiving the terminal-related bearer parameters.
- the core network management device further includes: a receiving module 93, configured to be connected to the adding module 91, configured to receive an update bearer request sent by the serving gateway SGW, where the bearer parameter to be modified carried in the update bearer request is only updated ARP parameters.
- the bearer parameters that need to be sent to the UE are added through the core network management device, and The UE is used to activate the ISR, so that when the access network is reselected, the bearer context between the SGSN and the MME is synchronized, and synchronization between the SGSN and the MME is implemented.
- 10 is a schematic structural diagram of a network system according to a tenth embodiment of the present invention, including an SGW 101 and a core network management device 102.
- the SGW 101 is configured to reduce idle ISR in an idle state and detect that the bearer parameters to be modified are only When the priority ARP parameter is allocated and maintained, the terminal-related bearer parameter is added to the first update bearer request; the core network management device 102 is configured to receive the first update bearer request, and connect the terminal-related bearer by using the access network device. The parameter is sent to the terminal, so that the terminal activates the ISR after receiving the terminal-related bearer parameter.
- the first update bearer request further includes the updated ARP parameter
- the core network management device 102 may be an MME, where the MME is configured to modify the ARP parameter saved by itself to the updated ARP parameter
- the system of the embodiment may further include an SGSN 103, where the SGSN 103 is configured to receive a location update request sent by the terminal after the terminal reselects the GERAN/UTRAN access technology, and when detecting that the ISR is in a deactivated state,
- the MME sends a context request, and receives a context response returned by the MME, where the context response carries the updated ARP parameter, and the ARP parameter saved by itself is modified into the updated ARP parameter.
- the SGSN is connected to the sending module as the core network management device, and is configured to modify the ARP parameter saved by itself to the updated ARP parameter; and the MME is used to reselect the E-UTRAN access in the terminal.
- the routing update request sent by the terminal when detecting that the ISR is in the deactivated state, sending a context request to the SGSN; and receiving a context response returned by the SGSN, where the context response carries the update After the ARP parameter; modify the ARP parameter saved by itself to the updated ARP parameter.
- the terminal-related bearer parameter may be specifically at least one of the following: TFT, APN-AMBR, QCI, GBR, MBR, or an additional indication for deactivating the ISR.
- the UE may be deactivated.
- the active ISR is such that when the access network is reselected, the bearer context between the SGSN and the MME is synchronized, and synchronization between the SGSN and the MME is implemented.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
去激活 ISR的方法、 修改承载参数的方法和网絡***
技术领域
本发明涉及移动通信技术, 尤其涉及一种去激活 ISR的方法、 修改承载 参数的方法和网络***。 背景技术
第三代合作伙伴计划 (3rd Generation Partnership Project, 3GPP ) 中, 用 户设备 ( User Equipment, UE ) 可以通过通用陆地无线接入网络 ( Universal Terrestrial Radio Access Network , UTRAN ) 或者全球移动通信*** Global System for Mobile communications, GSM )或者增强型数据速率 GSM 演进( Enhanced Data Rate for GSM Evolution, EDGE )无线接入网( GSM EDGE Radio Access Network, GERAN )接入演进分组核心 ( Evolved Packet Core , EPC ), 也可以通过演进通用陆地无线接入网络 ( Evolved Universal Terrestrial Radio Access Network, E-UTRAN )接入 EPC。 EPC主要包括如下网元: 分 组数据网 ( Packet Data Network, PDN ) 网关 (PDN Gateway, PGW )、 服务 网关 ( Serving Gateway , SGW )、 移动管理实体 ( Mobile Management Entity , MME )、 通用分组无线业务( General Packet Radio Service, GPRS )服务支持 节点( Serving GPRS Support Node, SGSN )和策略与计费规则功能实体( Policy and Charging Rule Function, PCRF ), 以实现 UE与分组数据网之间的数据传 输。 其中, PGW是分组数据网的网关, 负责对用户数据流进行转发和过滤。 SGW主要负责在 UE和 PGW之间中继用户业务流, 以及基站间切换时作为 锚定点。 MME主要完成 E-UTRAN接入下 UE的移动性管理、 会话管理、 非 接入层(Non- Access Stratum, NAS )信令的加密和完整性保护; 当 UE处于 空闲 (Idle ) 态时, MME 可以保存承载上下文信息。 SGSN 主要完成 GERAN/UTRAN接入下 UE的移动性管理、会话管理等功能; 当 UE处于 Idle
态时, SGSN可以保存承载上下文信息。 PCRF主要用于实现策略计费控制。 当 UE釆用不同的无线接入技术时 , UE对应的空闲态可以分为三种情况。 具体为 , 当 UE釆用 E-UTRAN接入时 , 对应的空闲态用 ECM-IDLE表示; 在该状态下, UE和 MME会保存用户上下文, 该用户上下文包括移动性上下 文和承载上下文。当 UE釆用 GERAN/UTRAN接入时,对应的空闲态用 GPRA STANDBY或 PMM-IDLE表示; 该状态下, UE和 SGSN会保存用户上下文, 该用户上下文包括移动性上下文和承载上下文。
空闲态信令减少 ( Idle mode Signalling Reduction, ISR )是处于空闲态的 UE重选无线接入技术时, 提供的减少信令交互的机制。 其中, 无线接入技术 包括 E-UTRAN和 GERAN/UTRAN。 ISR包括激活状态和去激活状态。 对于 非激活 ISR的用户, 只会在网络侧的 MME或者 SGSN中保存用户上下文。 当需要修改承载参数时, 只需在有承载上下文的一侧修改承载参数即可, 无 需 MME和 SGSN两者进行同步。 对于激活 ISR的用户, 网络侧的 MME和 SGSN中均会保存用户上下文。如果需要修改承载参数,需要在 MME和 SGSN 中均进行修改, 即需要 MME和 SGSN进行同步。
对于激活 ISR的用户, 当 UE重选无线接入网络时, 发起位置更新, 其 中位置更新流程釆用重选后的接入网络对应的身份标识, 例如, 当重选 E-UTRAN, 则釆用全球唯一临时标识( Globally Unique Temporary Identity, GUTI ), 当重选 GERAN/UTRAN, 则釆用分组临时移动用户标识 (Packet Temporary Mobile Subscriber Identity, P-TMSI )。 由于釆用的是重选后的接入 网络对应的标识, 所以重选后的移动性管理网元( MME或 SGSN , 即核心网 管理设备) 不会向另外的接入技术对应的移动性管理网元(SGSN或 MME ) 同步承载上下文信息。 对于去激活 ISR的用户, 当 UE重选无线接入网络时, 发起位置更新, 其中位置更新流程釆用重选前的接入网络对应身份标识, 例 如, 当重选 E-UTRAN, 则携带 P-TMSI, 当重选 GERAN/UTRAN, 则釆用 GUTL 由于釆用的是重选前的接入网络对应的标识, 所以重选后的移动性管
理网元( MME或 SGSN )将向另外的接入技术对应的移动性管理网元( SGSN 或 MME ) 同步承载上下文信息。
ISR的激活过程由路由区更新( Routing Area Update , RAU )或追踪区更 新( Tracking Area Update , TAU )流程的接受消息中的参数来完成, UE收到 该消息后将状态修改为 "ISR activated"。 当 UE被告知承载上下文修改时, 例如, UE被告知修改接入点名合计最大比特率( Access Point Name Aggregate Maximum Bit Rate, APN-AMBR )、传输流模板 ( Traffic Flow Template, TFT )、 服务质量类别识别符(Quality of Service Class Identifier, QCI )、 保证比特率 ( Guaranteed Bit Rate, GBR ), 最大比特率( Maximum Bit Rate , MBR )等, UE会去激活 ISR。
分配与保持优先级( Allocation and Retention Priority, ARP )用于指示在 承载资源不足时, 不同优先级的承载抢占资源的能力。 该参数对于 UE没有 意义, 所以不必通知到 UE, 仅需要通知到无线接入侧的网元, 例如无线接入 网 (Radio Access Network, RAN )或者演进基站( eNodeB )即可, 无线接入 侧的网元根据该优先级来执行资源抢占和释放。
现有技术中至少存在如下问题: 由于 ARP参数不会通知到 UE, 因此, 对于激活 ISR的用户, 当修改 ARP参数后, UE无法获知, 从而不会去激活 ISR。 发明内容
本发明实施例是提供一种去激活 ISR的方法、 修改承载参数的方法和网 络***, 使得当需要修改的承载参数仅为 APR参数时可以去激活 ISR。
本发明实施例提供了一种去激活 ISR的方法, 包括:
当 ISR处于激活状态且网络侧设备检测到需要修改的承载参数仅为分配 与保持优先级 ARP参数时,所述网络侧设备添加终端相关承载参数到第一更 新承载请求中;
所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端, 以使所述终端在接收到所述终端相关承载参数后 去激活 ISR。
本发明实施例提供了一种修改承载参数的方法, 包括:
服务网关 SGW接收分组数据网网关 PGW发送的第一更新承载请求,所 述第一更新承载请求中携带的需要修改的承载参数仅为更新后的分配与保持 优先级 ARP参数;
当空闲态信令减少 ISR处于激活状态时, 所述 SGW向第一移动管理实 体 MME和第一通用分组无线业务服务支持节点 SGSN发送第二更新承载请 求, 所述第二更新承载请求中携带所述更新后的 ARP 参数, 以使所述第一 MME和第一 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。
本发明实施例提供了一种网络侧设备, 包括:
添加模块, 当空闲态信令减少 ISR处于激活状态且所述网络侧设备检测 到需要修改的承载参数仅为分配与保持优先级 ARP参数时,添加终端相关承 载参数到第一更新承载请求中;
发送模块, 用于将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端, 以使所述终端在接收到所述终端相关承载参数后 去激活 ISR。
本发明实施例提供了一种网络***, 包括:
服务网关 SGW,用于当空闲态信令减少 ISR处于激活状态且检测到需要 修改的承载参数仅为分配与保持优先级 ARP参数时,添加终端相关承载参数 到第一更新承载请求中;
核心网管理设备, 用于接收所述第一更新承载请求, 并通过接入网设备 将所述终端相关承载参数发送给终端, 以使所述终端在接收到所述终端相关 承载参数后去激活 ISR。
由上述技术方案可知, 本发明实施例在 ISR 处于激活状态且仅需修改 ARP参数时 ,通过添加终端相关承载参数以便 UE去激活 ISR,或者使得 SGW 向 MME和 SGSN均发送携带有更新后的 ARP参数的更新承载消息, 为实现 MME和 SGSN的同步提供基础。 附图说明
为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例描述中 所需要使用的附图作一简单地介绍, 显而易见地, 下面描述中的附图是本发 明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的 前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明第一实施例的方法流程示意图;
图 2为本发明第二实施例的方法流程示意图;
图 3为本发明第三实施例的方法流程示意图;
图 4为本发明第四实施例的方法流程示意图;
图 5为本发明第五实施例的方法流程示意图;
图 6为本发明第六实施例的方法流程示意图;
图 7为本发明第七实施例的方法流程示意图;
图 8为本发明第八实施例的方法流程示意图;
图 9为本发明第九实施例的网络侧设备的结构示意图;
图 10为本发明第十实施例的网络***的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获
得的所有其他实施例, 都属于本发明保护的范围。
由于 ARP参数不会通知到 UE,因此,对于激活 ISR的用户,当修改 ARP 参数后, UE无法获知, 从而不会去激活 ISR。 此时, 承载参数的修改只能在 MME或者 SGSN中修改, 而不能在 MME和 SGSN中同时修改, 不能实现 MME和 SGSN的同步。 为了实现 MME和 SGSN的同步, 本发明实施例在 ISR处于激活状态且仅需要修改 ARP参数时, 提供一种方案来去激活 ISR, 为实现 SGSN和 MME同步提供基础。
图 1为本发明第一实施例的方法流程示意图, 包括:
步骤 11 : 当 ISR处于激活状态且网络侧设备检测到需要修改的承载参数 仅为 ARP参数时,所述网络侧设备添加终端相关承载参数到第一更新承载请 求中;
步骤 12: 所述网络侧设备将所述第一更新承载请求中携带的终端相关承 载参数通过接入网设备路由到终端, 以使所述终端在接收到所述终端相关承 载参数后去激活 ISR。
所述网络侧设备为 SGW或核心网管理设备, 当核心网管理设备为 MME 时, 对应的接入网设备为 eNodeB; 或者, 当核心网管理设备为 SGSN时, 对 应的接入网设备为 RAN。
该终端相关承载参数包括以下至少一种: TFT、 APN-AMBR, QCI、 保 证比特率 ( Guaranteed Bit Rate , GBR ) 、 最大比特率 ( Maximum Bit Rate, MBR )或者新增的用于去激活 ISR的指示。 终端在接收到终端相关承载参数 后, 不论该终端相关承载参数是否修改, 均去激活 ISR。
需要说明的是, 在下述各实施例的描述中, 所述终端相关承载参数即为 需要发送给 UE的承载参数。
本实施例中, 当 ISR处于激活状态且网络侧设备检测到需要修改的承载 参数仅为分配与保持优先级 ARP参数时,网络侧设备添加终端相关承载参数, 并将所述终端相关承载参数路由到终端, 从而可以使得 UE去激活 ISR。
在一种具体的实施场景下, 所述网络侧设备为服务网关 SGW: 所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端包括: 所述 SGW将所述第一更新承载请求发送给 核心网管理设备, 所述核心网管理设备用于通过接入网设备将所述终端相关 承载参数发送给终端。
在步骤 11之前,所述方法还包括: 所述 SGW接收分组数据网网关 PGW 发送的第二更新承载请求 , 所述第二更新承载请求中携带的需要修改的承载 参数仅为更新后的 ARP参数。
一方面, 当所述核心网管理设备为移动管理实体 MME时, 所述第一更 新承载请求中还包含更新后的 ARP参数, 所述 SGW将所述第一更新承载请 求发送给核心网管理设备之后, 所述方法还包括:
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选 GERAN/UTRAN接入网络后 , 所述 GERAN/UTRAN接 入网络中的通用分组无线业务服务支持节点 SGSN接收所述终端发送的位置 更新请求, 当检测到 ISR处于去激活状态时, 向所述 MME发送上下文请求; 所述 SGSN接收所述 MME返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。 另一方面, 当所述核心网管理设备为 SGSN时, 所述第一更新承载请求 中还包含更新后的 ARP参数, 所述 SGW将所述第一更新承载请求发送给核 心网管理设备之后, 所述方法还包括: 所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选演进通用陆地无线接入网络 E-UTRAN接入网络后, 所 述 E-UTRAN接入网络中的 MME接收所述终端发送的位置更新请求, 当检
测到 ISR处于去激活状态时, 向所述 SGSN发送上下文请求;
所述 MME接收所述 SGSN返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数。 当核心网管理设备为 MME或 SGSN时, 上述具体步骤分别给出了 UE 重新接入网络后, SGSN和 MME进行同步的具体方式, 使得 SGSN与 MME 之间的承载上下文保持同步。
在另一种具体的实施场景下, 所述网络侧设备为核心网管理设备: 所述网络侧设备添加终端相关承载参数到第一更新承载请求中包括: 所 述核心网管理设备添加终端相关承载参数到承载修改请求中; 所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端包括: 所述核心网管理设备将所述承载修改请求发 送给接入网设备, 并通过所述接入网设备将所述终端相关承载参数发送给终 端。
所述网络侧设备检测到需要修改的承载参数仅为 ARP参数之前,所述方 法还包括: 所述核心网管理设备接收服务网关 SGW发送的更新承载请求, 所述 SGW发送的更新承载请求中携带的需要修改的承载参数仅为更新后的 ARP参数。 当所述核心网管理设备为移动管理实体 MME时, 所述核心网管理设备 检测到需要修改的承载参数仅为 ARP参数之后, 所述方法还包括: 所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选通用陆地无线接入网络或者全球移动通信*** GSM/增 强型数据速率 GSM演进 EDGE无线接入网 GERAN/UTRAN接入网络后,所 述 GERAN/UTRAN接入网络中的通用分组无线业务服务支持节点 SGSN接
收所述终端发送的位置更新请求; 所述 SGSN在接收到所述位置更新请求后, 向所述 MME发送上下文请 求;
所述 SGSN接收所述 MME返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。 当所述核心网管理设备为 SGSN时, 所述核心网管理设备检测到需要修 改的承载参数仅为 ARP参数之后, 所述方法还包括: 所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选演进通用陆地无线接入网络 E-UTRAN接入网络后, 所 述 E-UTRAN接入网络中的 MME接收所述终端发送的位置更新请求; 所述 MME在接收到所述位置更新请求后, 向所述 SGSN发送上下文请 求;
所述 MME接收所述 SGSN返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数。 当核心网管理设备为 MME或 SGSN时, 上述具体步骤分别给出了 UE 重新接入网络后, SGSN和 MME进行同步的具体方式, 使得 SGSN与 MME 之间的承载上下文保持同步。
图 2为本发明第二实施例的方法流程示意图, 包括: 步骤 21:服务网关 SGW接收分组数据网网关 PGW发送的第一更新承载 请求, 所述第一更新承载请求中携带的需要修改的承载参数仅为更新后的分 配与保持优先级 ARP参数;
步骤 22: 当空闲态信令减少 ISR处于激活状态时, 所述 SGW向第一移
动管理实体 MME和第一通用分组无线业务服务支持节点 SGSN发送第二更 新承载请求, 所述第二更新承载请求中携带所述更新后的 ARP参数, 以使所 述第一 MME和第一 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP 参数。
本发明实施例中, ISR处于激活状态时, 当 SGW检测到需要修改的承载 参数仅为更新后的分配与保持优先级 ARP参数, SGW将所述更新后的 ARP 参数发送给 MME和 SGSN, 从而使得 UE重新选择接入网络后, 可以保证重 新前后的 MME和 SGSN保持参数同步。
更进一步的, 当 UE重新选择接入网络后, 如果重新选择的接入网络的 移动性管理网元(MME或 SGSN )发生变化, 本发明实施例还可以包括下述 步骤: 当终端重选 E-UTRAN接入网络且重选后的 MME与所述第一 MME不同 时 , 则重选后的 MME从所述第一 MME获取所述更新后的 ARP; 或者,
当终端重选 GERAN/UTRAN接入网络且重选后的 SGSN 与所述第一 SGSN不同时,则重选后的 SGSN从所述第一 SGSN获取所述更新后的 ARP。
从而保证在重新接入网络后核心网管理设备发生变化的情况下, 仍然可 以保证参数同步。
图 3为本发明第三实施例的方法流程示意图, 本实施例以 SGW添加承 载参数为例, 且本实施例应用场景是从 E-UTRAN 接入网络重选到 GERAN/UTRAN接入网络。 参见图 3 , 包括:
步骤 301 : PGW发起承载上下文 ARP参数修改流程, 向 SGW发送更新 承载请求( Update Bearer Request ) , 该更新承载请求消息中携带用于确定修 改的 7 载标识和更新后的 ARP参数。
步骤 302: SGW接收到 PGW发送的更新承载请求后, 根据该更新承载 请求中携带的参数判断是否仅需要修改 ARP,当仅需要修改 ARP且 ISR处于
激活状态时, SGW将需要发送给 UE的承载参数添加到该更新承载请求中。 其中, 当该更新承载修改请求中不携带需要发送给 UE的承载参数时, 而仅包含 ARP时,则表明仅需要修改 ARP。 当该更新承载请求中还携带需要 发送给 UE的承载参数时, 则表明非仅需要修改 ARP。
ISR是否处于激活状态是网络侧决定并通知 UE的, 因此 SGW可以获知 ISR是否处于激活状态, 至于网络侧如何决定 ISR是否激活, 可以釆用现有 技术实现, 本实施例并不特别关注。
该添加的需要发送给 UE的承载参数可以为如下项中的至少一项: TFT、 APN-AMBR, QCI、 GBR、 MBR或者新增的用于去激活 ISR的指示等。
步骤 303: SGW将添加了需要发送给 UE的承载参数后的更新承载请求, 发送给 MME。
步骤 304: MME修改 ARP, 并建立会话管理请求( Session Management Request ) , 并通过 载爹改请求 ( Bearer Modify Request )发送给 eNodeB, 其中携带 ARP和添加的需要发送给 UE的承载参数。
步骤 305: eNodeB修改 ARP, 然后向 UE发送 RRC连接重配置 ( RRC Connection Reconfiguration ) 消息, 以建立无线侧承载。 并在 RRC连接重配 置消息中携带 Session Management Request。
步骤 306: UE接收到该 RRC连接重配置消息后, 不管其中携带的参数 是否修改, 都把 ISR去激活。
步骤 307: UE向 eNodeB发送 RRC连接重配置完成(RRC Connection Reconfiguration Complete ) 消息, 以确认无线 载的爹改。
步骤 308: eNodeB向 MME发送承载修改响应( Bearer Modify Response ), 确认无线承载的修改。
步骤 309 : UE 的 NAS 层建立会话管理响应 (Session Management Response ) , 该会话管理响应中包括 EPS承载标识。 之后, UE向 eNodeB发 送直传( Direct Transfer ) 消息, 该直传消息中包含会话管理响应。
步骤 310: eNodeB向 MME发送上行 NAS传输( Uplink NAS Transport ) 消息 , 该消息中也携带 Session Management Response。
步骤 311 : 当收到步骤 308的承载修改响应和步骤 310的会话管理响应 后, MME向 SGW发送更新承载响应 ( Update Bearer Response ) , 作为承载 爹改的确认。
步骤 312: SGW向 PGW发送更新承载响应, 作为承载修改的响应。 步骤 313: UE在空闲态重选 GERAN/UTRAN接入网络。
步骤 314: UE向 GERAN/UTRAN接入网络中的 SGSN发送位置更新请 求( Routing Area Update Request ) , 发起位置更新流程, 该位置更新请求中 可以携带 GUTI。
步骤 315: SGSN收到位置更新请求后,执行位置更新流程。当检测到 ISR 处于去激活状态时, 根据位置更新请求中携带的 GUTI的值向 MME发送上 下文请求 ( Context Request ) , 以同步承载上下文。
步骤 316: ΜΜΕ 收到该上下文请求后, 把承载上下文通过上下文响应 ( Context )发送到 SGSN, 该承载上下文包含修改后的 ARP。
步骤 317: SGSN完成承载上下文同步和位置更新相关操作之后, 向 UE 发送位置更新响应( Routing Area Update Response ) , 以通知 UE位置更新流 程结束。
本实施例以从 E-UTRAN重选到 GERAN/UTRAN为例 , 可以理解的是, 釆用上述原理同样可以应用到从 GERAN/UTRAN重选到 E-UTRAN的场景, 此时, 需要将上述的 MME和 SGSN执行的操作互换, 将 eNodeB执行的操 作替换为 RAN执行的操作, 将上述的 GUTI替换为 P-TMSL
本实施例通过 SGW添加其他需要发送给 UE的承载参数, 可以使得 UE 去激活 ISR。 进一步的, 步骤 304中 MME根据 SGW发送的承载更新请求中 包含的更新后的 ARP 参数更新自身存储的 ARP 参数, 当 UE 重新选择 GERAN/UTRAN接入网络后, 所述接入网络中的 SGSN可以从 MME获得所
述更新后的 ARP参数, 从而实现 MME和 SGSN的同步。 本实施例由 SGW 添加承载参数可以应用于重选 E-UTRAN接入网络或者 GERAN/UTRAN接入 网络的场景, 不受限于应用场景, 提高适用性。
图 4为本发明第四实施例的方法流程示意图, 本实施例以 MME添加承 载参数为例。 参见图 4, 包括:
步骤 401: 与步骤 301对应相同。
步骤 402: SGW将从 PGW接收的更新承载请求发送给 MME。
步骤 403: MME接收到 SGW发送的更新承载请求后, 修改 ARP。 并根 据该更新承载请求中携带的参数判断是否仅需要修改 ARP, 当仅需要修改 ARP且 ISR处于激活状态时, MME将需要发送给 UE的承载参数添加到该 更新承载请求中。
其中, 当该更新承载修改请求中不携带需要发送给 UE的承载参数时, 而仅包含更新后的 ARP时 , 则表明仅需要修改 ARP。 当该更新承载请求中还 携带需要发送给 UE的承载参数时, 则表明非仅需要修改 ARP。
ISR是否处于激活状态是网络侧决定并通知 UE的, 因此 SGW可以获 知 ISR是否处于激活状态, 至于网络侧如何决定 ISR是否激活, 可以釆用现 有技术实现, 本实施例并不特别关注。
该添加的需要发送给 UE的承载参数可以为如下项中的至少一项 TFT、 APN-AMBR, QCI、 GBR、 MBR或者新增的用于去激活 ISR的指示。
步骤 404: MME建立会话管理请求( Session Management Request ) , 并 通过承载修改请求( Bearer Modify Request )发送给 eNodeB , 其中携带 ARP 和添加的需要发送给 UE的承载参数。
步骤 405-417: 与步骤 305-317对应相同。
本实施例通过 MME添加其他需要发送给 UE的承载参数, 可以使得 UE 去激活 ISR , 实现 MME和 SGSN的同步。 本实施例由 MME执行添加操作 , 可以应用于从 E-UTRAN接入网络重选到 GERAN/UTRAN接入网络的场景。
图 5为本发明第五实施例的方法流程示意图, 本实施例以 SGSN添加承 载参数为例。 参见图 5, 包括:
步骤 501 : 与步骤 301对应相同。
步骤 502: SGW将从 PGW接收的更新承载请求发送给 SGSN。
步骤 503: SGSN接收到 SGW发送的更新承载请求后, 修改 ARP。 并根 据该更新承载请求中携带的参数判断是否仅需要修改 ARP, 当仅需要修改 ARP且 ISR处于激活状态时, SGSN将需要发送给 UE的承载参数添加到该 更新承载请求中。
其中, 当该更新承载修改请求中不携带需要发送给 UE的承载参数时, 而仅包含 ARP时,则表明仅需要修改 ARP。 当该更新承载请求中还携带需要 发送给 UE的承载参数时, 则表明非仅需要修改 ARP。
ISR是否处于激活状态是网络侧决定并通知 UE的, 因此 SGW可以获知 ISR是否处于激活状态, 至于网络侧如何决定 ISR是否激活, 可以釆用现有 技术实现, 本实施例并不特别关注。
该添加的需要发送给 UE的承载参数可以为如下项中的至少一项: TFT、 APN-AMBR, QCI、 GBR、 MBR或者新增的用于去激活 ISR的指示。
步骤 504: SGSN向 RAN发送无线接入承载修改(Radio Access Bearer Modification )消息, 其中 MME携带 ARP和添加的需要发送给 UE的承载参 数。
步骤 505: RAN修改 ARP, 然后向 UE发送无线接入承载修改(Radio Access Bearer Modification ) 消息, 以建立无线侧 载。
步骤 506: SGSN向 UE发送修改承载上下文请求( Modify Bearer Context Request ) 。
步骤 507: UE接收到该修改承载上下文请求后, 不管其中携带的参数是 否修改, 都把 ISR去激活。
步骤 508: UE向 SGSN发送修改承载上下文响应( Modify Bearer Context
Respond ) , 以确认无线 7 载的爹改。
步骤 509: SGSN向 SGW发送更新承载响应( Update Bearer Response ) , 作为承载修改的确认。
步骤 510: SGW向 PGW发送更新承载响应, 作为承载修改的响应。 步骤 511 : UE在空闲态重选 E -UTRAN接入网络。
步骤 512: UE 向 E-UTRAN接入网络中的 ΜΜΕ发送位置更新请求 ( Routing Area Update Request ) , 发起位置更新流程。
步骤 513: ΜΜΕ收到位置更新请求后,执行位置更新流程。当检测到 ISR 处于去激活状态时, 根据 P-TMSI 的值向 SGSN发送上下文请求 (Context Request ) , 以同步承载上下文。
步骤 514: SGSN收到该上下文请求后, 把承载上下文通过上下文响应 ( Context Response )发送到 MME, 该承载上下文包含修改后的 ARP。
步骤 515: MME完成承载上下文同步和位置更新相关操作之后, 向 UE 发送位置更新响应( Routing Area Update Response ) , 以通知 UE位置更新流 程结束。
本实施例通过 SGSN添加其他需要发送给 UE的承载参数,可以使得 UE 去激活 ISR, 实现 MME和 SGSN的同步。 本实施例由 SGSN执行添加操作, 可以应用于从 GERAN/UTRAN重选到 E-UTRAN的场景。
第三-五实施例是釆用添加承载参数的方法实现 ISR的去激活,之后在重 选接入技术后, 可以实现 SGSN与 MME的同步。
本发明实施例还可以由 SGW指示 MME和 SGSN同步。 具体如下: 图 6为本发明第六实施例的方法流程示意图, 本实施例以 UE处于空闲 态为例。 参见图 6, 包括:
步骤 601: 与步骤 301对应相同。
步骤 602: SGW接收到 PGW发送的更新承载请求后, 根据该更新承载 请求中携带的参数判断是否仅需要修改 ARP,当仅需要修改 ARP且 ISR处于
激活状态时, SGW根据 ISR激活状态下 SGW维护的承载上下文确定第一 MME和第一 SGSN, 并向第一 MME和第一 SGSN发送更新承载请求, 其中 携带更新后的 ARP。
其中, 当该更新承载修改请求中不携带需要发送给 UE的承载参数时, 而仅包含 ARP时,则表明仅需要修改 ARP。 当该更新承载请求中还携带需要 发送给 UE的承载参数时, 则表明非仅需要修改 ARP。
ISR是否处于激活状态是网络侧决定并通知 UE的, 因此 SGW可以获知 ISR是否处于激活状态, 至于网络侧如何决定 ISR是否激活, 可以釆用现有 技术实现, 本实施例并不特别关注。
步骤 603: 第一 MME接收到更新承载请求后, 检测到 UE处于空闲态 ( Idle ) 时, 根据更新承载请求中携带的 ARP, 修改自身存储承载上下文中 的 ARP。
步骤 604 : 第一 MME 向 SGW 发送更新承载响应 (Update Bearer Response ) 。
步骤 605: 第一 SGSN接收到更新承载请求后, 检测到 UE处于空闲态 ( Idle ) 时, 根据更新承载请求中携带的 ARP, 修改自身存储承载上下文中 的 ARP。
步骤 606 : 第一 SGSN 向 SGW 发送更新承载响应 (Update Bearer Response ) 。
可以理解的是, 步骤 603-604与步骤 605-606无时序限制关系。
步骤 607: SGW在接收到步骤 604发送的更新承载响应和步骤 606发送 的更新 7 载响应后, 向 PGW发送更新7 载响应 ( Update Bearer Response ) , 作为承载修改的响应。
进一步地, 当 UE重选接入技术时核心网管理设备可能改变, 以 UE重选
E-UTRAN接入技术为例, UE重选 GERAN/UTRAN的流程与此类似, 不再 赘述。 本实施例还可以包括:
步骤 608: UE重选 E-UTRAN接入技术, 且重选后的 MME (表示为第 二 MME )与第一 MME不同时, 第二 MME接收 UE发送的位置更新请求, 其中携带 GUTI。
步骤 609: 第二 MME根据该 GUTI获取第一 MME的信息, 并向第一 MME发送上下文请求 ( Context Request ) 。
步骤 610:第一 MME向第二 MME返回上下文响应( Context Response ) , 其中携带更新后的 ARP。之后, 第一 MME将自身保存的 ARP修改为更新后 的 ARP。
进一步地, 可以将旧 MME和 SGSN中的上下文信息删除, 以便最新信 息保存在新的 MME中, 并去激活 ISR, 即, 还可以包括:
步骤 611 : 第二 MME向第一 MME返回确定消息 ( Acknowledge ) , 之 后, 第一 MME可以将自身保存的承载上下文信息删除。
另外, 第二 MME在更新承载参数后, 也会向 UE发送指示, 指示 UE去 激活 ISR。
步骤 612: 第一 MME向 SGW返回确定消息, SGW将确认消息发送给 第一 SGSN, 之后, SGSN删除自身保存的承载上下文信息。
本实施例通过 SGW向 MME和 SGSN发送更新承载消息, 可以在 MME 和 SGSN中都修改了承载上下文的 ARP, 实现 MME和 SGSN的同步。此后, 当 UE进入连接态( Connected )时, UE会与 MME或 SGSN进行承载上下文 同步, 保证流程的正确执行。
图 7为本发明第七实施例的方法流程示意图, 本实施例以 UE在 MME 侧处于连接态为例。 参见图 7, 包括:
步骤 701-702: 与步骤 601-602对应相同。
步骤 703 : MME 接收到更新承载请求后, 检测到 UE 处于连接态 ( Connected )时, 根据更新承载请求中携带的 ARP, 修改自身存储承载上下 文中的 ARP。
步骤 704: MME 向 eNodeB 发送会话管理请求 ( Session Management Request ) , 其中携带 ARP。
步骤 705: eNodeB根据该会话管理请求中携带的 ARP修改自身存储的 ARP。
步骤 706: eNodeB 向 MME返回会话管理响应 ( Session Management Response ) 。
步骤 707: MME向 SGW发送更新承载响应( Update Bearer Response ) 。 步骤 708: SGSN接收到更新承载请求后, 检测到 UE处于连接态, 且
UE在 MME侧进行业务连接, 而不是在 SGSN侧进行业务连接时, 根据更新 承载请求中携带的 ARP, 修改自身存储承载上下文中的 ARP。
步骤 709: SGSN向 SGW发送更新承载响应( Update Bearer Response ) 。 可以理解的是, 步骤 703-607与步骤 708-709无时序限制关系。
步骤 710: SGW在接收到步骤 707发送的更新承载响应和步骤 709发送 的更新 7 载响应后, 向 PGW发送更新7 载响应 ( Update Bearer Response ) , 作为承载修改的响应。
当 UE重选接入网络后, 核心网管理设备可能会发生变化, 此时, 可以 参照步骤 608-612所述进行处理, 不再赘述。
本实施例通过 SGW向 ΜΜΕ和 SGSN发送更新承载消息, 可以在 MME 和 SGSN中都修改了承载上下文的 ARP, 实现 MME和 SGSN的同步。 如果 此后 UE进入空闲态并切换到 SGSN侧, 在需要业务连接时 UE会与 SGSN 进行承载上下文同步, 保证流程的正确执行。
图 8为本发明第八实施例的方法流程示意图, 本实施例以 UE在 SGSN 侧处于连接态为例。 参见图 8, 包括:
步骤 801-802: 与步骤 601-602对应相同。
步骤 803: MME接收到更新承载请求后,检测到 UE处于连接态,且 UE 在 SGSN侧进行业务连接, 而不是在 MME侧进行业务连接时, 根据更新承
载请求中携带的 ARP, 修改自身存储承载上下文中的 ARP。
步骤 804: MME向 SGW发送更新承载响应( Update Bearer Response ) 。 步骤 805 : SGSN 接收到更新承载请求后, 检测到 UE 处于连接态 ( Connected )时, 根据更新承载请求中携带的 ARP, 修改自身存储承载上下 文中的 ARP
步骤 806 : SGSN 向 RAN 发送会话管理请求 (Session Management
Request ) , 其中携带 ARP。
步骤 807: RAN根据该会话管理请求中携带的 ARP修改自身存储的 ARP。 步骤 808 : RAN 向 SGSN 返回会话管理响应 (Session Management
Response ) 。
步骤 809: SGSN向 SGW发送更新承载响应( Update Bearer Response ) 。 步骤 803-804与步骤 805-809无时序限制关系。
步骤 810: SGW在接收到步骤 804更新 7 载响应和步骤 809更新 7 载响 应后, 向 PGW发送更新承载响应( Update Bearer Response ) , 作为承载修改 的响应。
当 UE重选接入网络后, 核心网管理设备可能会发生变化, 此时, 可以 参照步骤 608-612所述进行处理, 不再赘述。
本实施例通过 SGW向 ΜΜΕ和 SGSN发送更新承载消息, 可以在 MME 和 SGSN中都修改了承载上下文的 ARP, 实现 MME和 SGSN的同步。 如果 此后 UE进入空闲态并切换到 MME侧 ,在需要业务连接时 UE会与 MME进 行承载上下文同步, 保证流程的正确执行。
图 9为本发明第九实施例的网络侧设备的结构示意图, 包括添加模块 91 和发送模块 92, 添加模块 91用于当空闲态信令减少 ISR处于激活状态且所 述网络侧设备检测到需要修改的承载参数仅为分配与保持优先级 ARP 参数 时, 添加终端相关承载参数到第一更新承载请求中; 发送模块 92用于将所述 第一更新承载请求中携带的终端相关承载参数通过接入网设备路由到终端,
以使所述终端在接收到所述终端相关承载参数后去激活 ISR。
在一种具体实施场景下, 所述网络侧设备具体为服务网关 SGW, 所述发送模块, 具体用于将所述第一更新承载请求发送给核心网管理设 备, 所述核心网管理设备用于通过接入网设备将所述终端相关承载参数发送 给终端, 以使所述终端在接收到所述终端相关承载参数后去激活 ISR。 所述 SGW还包括: 接收模块 93 , 与所述添加模块 91连接, 用于接收分组数据网网关 PGW 发送的第二更新承载请求 , 所述第二更新承载请求中携带的需要修改的承载 参数仅为更新后的 ARP参数。
上述模块的具体功能可以参见方法实施例, 不再赘述。 本实施例通过 SGW添加需要发送给 UE的承载参数, 可以使得 UE去激 活 ISR, 这样在重选接入网络时, 会同步 SGSN与 MME之间的承载上下文, 实现 SGSN和 MME两者的同步。 在另一种具体场景下, 所述网络侧设备具体为核心网管理设备, 所述添加模块 91, 具体用于当空闲态信令减少 ISR处于激活状态且核心 网管理设备检测到需要修改的承载参数仅为分配与保持优先级 ARP参数时, 添加终端相关承载参数到承载修改请求中; 所述发送模块 92, 具体用于将所述承载修改请求发送给接入网设备, 并 通过所述接入网设备将所述终端相关承载参数发送给终端, 以使所述终端在 接收到所述终端相关承载参数后去激活 ISR。 所述核心网管理设备还包括: 接收模块 93 , 与所述添加模块 91 连接, 用于接收服务网关 SGW发送的更新承载请求, 所述更新承载请求中携带的 需要修改的承载参数仅为更新后的 ARP参数。 本实施例通过核心网管理设备添加需要发送给 UE的承载参数, 可以使
得 UE去激活 ISR, 这样在重选接入网络时,会同步 SGSN与 MME之间的承 载上下文, 实现 SGSN和 MME两者的同步。 图 10为本发明第十实施例的网络***的结构示意图, 包括 SGW 101和 核心网管理设备 102; SGW 101用于当空闲态信令减少 ISR处于激活状态且 检测到需要修改的承载参数仅为分配与保持优先级 ARP参数时,添加终端相 关承载参数到第一更新承载请求中; 核心网管理设备 102用于接收所述第一 更新承载请求, 并通过接入网设备将所述终端相关承载参数发送给终端, 以 使所述终端在接收到所述终端相关承载参数后去激活 ISR。 其中, 所述第一更新承载请求中还包含更新后的 ARP参数, 该核心网管 理设备 102可以为 MME, 所述 MME用于将自身保存的 ARP参数修改为所 述更新后的 ARP参数; 本实施例的***还可以包括 SGSN 103 , SGSN 103用 于在所述终端重选 GERAN/UTRAN接入技术后,接收所述终端发送的位置更 新请求, 当检测到 ISR处于去激活状态时, 向所述 MME发送上下文请求; 并接收所述 MME返回的上下文响应, 所述上下文响应中携带所述更新后的 ARP参数; 将自身保存的 ARP参数修改为所述更新后的 ARP参数。 或者, SGSN作为上述的核心网管理设备, 与所述发送模块连接, 用于 将自身保存的 ARP参数修改为所述更新后的 ARP参数; MME 用于在所述 终端重选 E-UTRAN接入技术后, 接收所述终端发送的路由更新请求, 当检 测到 ISR处于去激活状态时, 向所述 SGSN发送上下文请求; 并接收所述 SGSN返回的上下文响应, 所述上下文响应中携带所述更新后的 ARP参数; 将自身保存的 ARP参数修改为所述更新后的 ARP参数。
该终端相关承载参数可以具体为如下项中的至少一项: TFT、 APN-AMBR, QCI、 GBR、 MBR或者新增的用于去激活 ISR的指示。
上述模块的具体功能可以参见方法实施例, 不再赘述。
本实施例通过 SGW添加需要发送给 UE的承载参数, 可以使得 UE去激
活 ISR, 这样在重选接入网络时, 会同步 SGSN与 MME之间的承载上下文, 实现 SGSN和 MME两者的同步。 需要说明的是, 本发明实施例中的 "第一" 、 "第二" 等仅用于区分, 并不代表实施例的优劣。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其 限制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术 人员应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或 者对其中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。
Claims
1、 一种去激活空闲态信令减少 ISR的方法, 其特征在于, 包括: 当 ISR处于激活状态且网络侧设备检测到需要修改的承载参数仅为分配 与保持优先级 ARP参数时,所述网络侧设备添加终端相关承载参数到第一更 新承载请求中;
所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端, 以使所述终端在接收到所述终端相关承载参数后 去激活 ISR。
2、 根据权利要求 1所述的方法, 其特征在于, 所述网络侧设备为服务网 关 SGW,所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参 数通过接入网设备路由到终端包括:
所述 SGW将所述第一更新承载请求发送给核心网管理设备, 所述核心 网管理设备用于通过接入网设备将所述终端相关承载参数发送给终端。
3、 根据权利要求 2所述的方法, 其特征在于, 所述网络侧设备检测到需 要修改的承载参数仅为 ARP参数之前, 所述方法还包括: 所述 SGW接收分组数据网网关 PGW发送的第二更新承载请求,所述第 二更新承载请求中携带的需要修改的承载参数仅为更新后的 ARP参数。
4、 根据权利要求 2所述的方法, 其特征在于, 所述核心网管理设备为移 动管理实体 MME, 所述第一更新承载请求中还包含更新后的 ARP参数, 所 述 SGW将所述第一更新承载请求发送给核心网管理设备之后, 所述方法还 包括:
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选通用陆地无线接入网络或者全球移动通信*** GSM/增 强型数据速率 GSM演进 EDGE无线接入网 GERAN/UTRAN接入网络后,所 述 GERAN/UTRAN接入网络中的通用分组无线业务服务支持节点 SGSN接 收所述终端发送的位置更新请求, 当检测到 ISR处于去激活状态时, 向所述 MME发送上下文请求; 所述 SGSN接收所述 MME返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。
5、 根据权利要求 2 所述的方法, 其特征在于, 所述核心网管理设备为 SGSN, 所述第一更新承载请求中还包含更新后的 ARP参数, 所述 SGW将 所述第一更新承载请求发送给核心网管理设备之后, 所述方法还包括:
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选演进通用陆地无线接入网络 E-UTRAN接入网络后, 所 述 E-UTRAN接入网络中的 MME接收所述终端发送的位置更新请求, 当检 测到 ISR处于去激活状态时, 向所述 SGSN发送上下文请求;
所述 MME接收所述 SGSN返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数。
6、 根据权利要求 1所述的方法, 其特征在于, 所述网络侧设备为核心网 管理设备,
所述网络侧设备添加终端相关承载参数到第一更新承载请求中包括: 所 述核心网管理设备添加终端相关承载参数到承载修改请求中; 所述网络侧设备将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端包括: 所述核心网管理设备将所述承载修改请求发送给接入网设备, 并通过所 述接入网设备将所述终端相关承载参数发送给终端。
7、 根据权利要求 6所述的方法, 其特征在于, 所述网络侧设备检测到需 要修改的承载参数仅为 ARP参数之前, 所述方法还包括: 所述核心网管理设备接收服务网关 SGW发送的更新承载请求, 所述 SGW发送的更新承载请求中携带的需要修改的承载参数仅为更新后的 ARP 参数。
8、 根据权利要求 7所述的方法, 其特征在于, 所述核心网管理设备为移 动管理实体 MME,所述核心网管理设备检测到需要修改的承载参数仅为 ARP 参数之后, 所述方法还包括: 所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选通用陆地无线接入网络或者全球移动通信*** GSM/增 强型数据速率 GSM演进 EDGE无线接入网 GERAN/UTRAN接入网络后,所 述 GERAN/UTRAN接入网络中的通用分组无线业务服务支持节点 SGSN接 收所述终端发送的位置更新请求; 所述 SGSN在接收到所述位置更新请求后, 向所述 MME发送上下文请 求;
所述 SGSN接收所述 MME返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。
9、 根据权利要求 7 所述的方法, 其特征在于, 所述核心网管理设备为 SGSN,所述核心网管理设备检测到需要修改的承载参数仅为 ARP参数之后, 所述方法还包括:
所述 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数; 在所述终端重选演进通用陆地无线接入网络 E-UTRAN接入网络后, 所 述 E-UTRAN接入网络中的 MME接收所述终端发送的位置更新请求; 所述 MME在接收到所述位置更新请求后, 向所述 SGSN发送上下文请 求;
所述 MME接收所述 SGSN返回的上下文响应, 所述上下文响应中携带 所述更新后的 ARP参数;
所述 MME将自身保存的 ARP参数修改为所述更新后的 ARP参数。
10、 根据权利要求 1-9任一项所述的方法, 其特征在于, 所述终端相关 承载参数包括以下至少一种: 传输流模板 TFT、 接入点名合计最大比特率 APN-AMBR,服务质量类别识别符 QCI、保证比特率 GBR、最大比特率 MBR 或者新增的用于去激活 ISR的指示。
11、 一种修改承载参数的方法, 其特征在于, 包括: 服务网关 SGW接收分组数据网网关 PGW发送的第一更新承载请求,所 述第一更新承载请求中携带的需要修改的承载参数仅为更新后的分配与保持 优先级 ARP参数; 当空闲态信令减少 ISR处于激活状态时, 所述 SGW向第一移动管理实 体 MME和第一通用分组无线业务服务支持节点 SGSN发送第二更新承载请 求, 所述第二更新承载请求中携带所述更新后的 ARP 参数, 以使所述第一 MME和第一 SGSN将自身保存的 ARP参数修改为所述更新后的 ARP参数。
12、 根据权利要求 11所述的方法, 其特征在于,
当终端在 MME侧处于连接态时, 所述第一 MME用于将所述更新后的 ARP参数发送给演进基站 eNodeB, 以使所述 eNodeB将自身保存的 ARP参 数修改为所述更新后的 ARP参数; 或者, 当终端在 SGSN侧处于连接态时, 所述第一 SGSN用于将所述更新后的 ARP参数发送给无线接入网 RAN,以使所述 RAN将自身保存的 ARP参数修 改为所述更新后的 ARP参数。
13、 根据权利要求 11所述的方法, 其特征在于, 还包括: 当终端重选演进通用陆地无线接入网络 E-UTRAN接入网络且重选后的 MME与所述第一 MME不同时, 则重选后的 MME从所述第一 MME获取所 述更新后的 ARP; 或者,
当终端重选通用陆地无线接入网络或者全球移动通信*** GSM/增强型 数据速率 GSM演进 EDGE无线接入网 GERAN/UTRAN接入网络且重选后的 SGSN与所述第一 SGSN不同时, 则重选后的 SGSN从所述第一 SGSN获取 所述更新后的 ARP。
14、 一种网络侧设备, 其特征在于, 包括: 添加模块, 用于当空闲态信令减少 ISR处于激活状态且所述网络侧设备 检测到需要修改的承载参数仅为分配与保持优先级 ARP参数时,添加终端相 关承载参数到第一更新承载请求中;
发送模块, 用于将所述第一更新承载请求中携带的终端相关承载参数通 过接入网设备路由到终端, 以使所述终端在接收到所述终端相关承载参数后 去激活 ISR。
15、 根据权利要求 14所述的网络侧设备, 其特征在于, 所述网络侧设备 具体为服务网关 SGW, 所述发送模块, 具体用于将所述第一更新承载请求发送给核心网管理设 备, 所述核心网管理设备用于通过接入网设备将所述终端相关承载参数发送 给终端, 以使所述终端在接收到所述终端相关承载参数后去激活 ISR。
16、 根据权利要求 15所述的网络侧设备, 其特征在于, 还包括: 接收模块, 与所述添加模块连接, 用于接收分组数据网网关 PGW发送 的第二更新承载请求, 所述第二更新承载请求中携带的需要修改的承载参数 仅为更新后的 ARP参数。
17、 根据权利要求 14所述的网络侧设备, 其特征在于, 所述网络侧设备 具体为核心网管理设备, 所述添加模块, 具体用于当空闲态信令减少 ISR处于激活状态且核心网 管理设备检测到需要修改的承载参数仅为分配与保持优先级 ARP参数时,添 加终端相关承载参数到承载修改请求中; 所述发送模块, 具体用于将所述承载修改请求发送给接入网设备, 并通 过所述接入网设备将所述终端相关承载参数发送给终端, 以使所述终端在接 收到所述终端相关承载参数后去激活 ISR。
18、 根据权利要求 17所述的网络侧设备, 其特征在于, 还包括: 接收模块, 与所述添加模块连接, 用于接收服务网关 SGW发送的更新 承载请求, 所述更新承载请求中携带的需要修改的承载参数仅为更新后的 ARP参数。
19、 根据权利要求 17所述的网络侧设备, 其特征在于, 所述核心网管理 设备为移动管理实体 MME或者通用分组无线业务服务支持节点 SGSN。
20、 一种网络***, 其特征在于, 包括: 服务网关 SGW,用于当空闲态信令减少 ISR处于激活状态且检测到需要 修改的承载参数仅为分配与保持优先级 ARP参数时,添加终端相关承载参数 到第一更新承载请求中;
核心网管理设备, 用于接收所述第一更新承载请求, 并通过接入网设备 将所述终端相关承载参数发送给终端, 以使所述终端在接收到所述终端相关 承载参数后去激活 ISR。
21、 根据权利要求 20所述的***, 其特征在于, 所述第一更新承载请求 中还包含更新后的 ARP参数, 所述核心网管理设备为移动管理实体 MME, 所述 MME用于将自身保存的 ARP参数修改为所述更新后的 ARP参数, 所述***还包括:
通用分组无线业务服务支持节点 SGSN, 用于在所述终端重选通用陆地 无线接入网络或者全球移动通信*** GSM/增强型数据速率 GSM演进 EDGE 无线接入网 GERAN/UTRAN接入网络后, 接收所述终端发送的位置更新请 求, 当检测到 ISR处于去激活状态时, 向所述 MME发送上下文请求; 并接 收所述 MME返回的上下文响应, 所述上下文响应中携带所述更新后的 ARP 参数; 将自身保存的 ARP参数修改为所述更新后的 ARP参数。
22、 根据权利要求 20所述的***, 其特征在于, 所述第一更新承载请求 中还包含更新后的 ARP参数, 所述核心网管理设备为 SGSN, 所述 SGSN用 于将自身保存的 ARP参数修改为所述更新后的 ARP参数; 所述***还包括:
MME, 用于在所述终端重选 E-UTRAN接入网络后, 接收所述终端发送 的位置更新请求, 当检测到 ISR处于去激活状态时, 向所述 SGSN发送上下 文请求; 并接收所述 SGSN返回的上下文响应, 所述上下文响应中携带所述 更新后的 ARP参数;将自身保存的 ARP参数修改为所述更新后的 ARP参数。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201080001650.8A CN102934406B (zh) | 2010-02-11 | 2010-02-11 | 去激活isr的方法、修改承载参数的方法和网络*** |
PCT/CN2010/070666 WO2011097813A1 (zh) | 2010-02-11 | 2010-02-11 | 去激活isr的方法、修改承载参数的方法和网络*** |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2010/070666 WO2011097813A1 (zh) | 2010-02-11 | 2010-02-11 | 去激活isr的方法、修改承载参数的方法和网络*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011097813A1 true WO2011097813A1 (zh) | 2011-08-18 |
Family
ID=44367163
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/070666 WO2011097813A1 (zh) | 2010-02-11 | 2010-02-11 | 去激活isr的方法、修改承载参数的方法和网络*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102934406B (zh) |
WO (1) | WO2011097813A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109906663A (zh) * | 2016-11-02 | 2019-06-18 | 华为技术有限公司 | 一种信息发送方法、设备和*** |
CN112911706A (zh) * | 2021-02-20 | 2021-06-04 | 中国联合网络通信集团有限公司 | 一种isr去激活方法、数据业务寻呼方法、msc以及sgw |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108260171A (zh) | 2016-12-29 | 2018-07-06 | 维沃移动通信有限公司 | 一种业务请求处理方法和相关设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040085930A1 (en) * | 2002-10-31 | 2004-05-06 | Lung-Sheng Lee | Radio device capable of anticipating a link state and method thereof |
CN101472312A (zh) * | 2008-01-31 | 2009-07-01 | 华为技术有限公司 | 一种资源释放控制方法及通讯***以及相关设备 |
CN101568178A (zh) * | 2008-04-22 | 2009-10-28 | 大唐移动通信设备有限公司 | 一种用户终端去附着方法、***及装置 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101483850B (zh) * | 2008-01-07 | 2010-12-08 | 华为技术有限公司 | 一种接入网络的方法及*** |
CN101483845A (zh) * | 2008-01-09 | 2009-07-15 | 华为技术有限公司 | 承载更新方法和核心网移动性管理网元、用户面实体、*** |
CN101500223B (zh) * | 2008-02-01 | 2012-08-29 | 华为技术有限公司 | 终端跨接入网元切换的方法及移动性管理网元 |
-
2010
- 2010-02-11 WO PCT/CN2010/070666 patent/WO2011097813A1/zh active Application Filing
- 2010-02-11 CN CN201080001650.8A patent/CN102934406B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040085930A1 (en) * | 2002-10-31 | 2004-05-06 | Lung-Sheng Lee | Radio device capable of anticipating a link state and method thereof |
CN101472312A (zh) * | 2008-01-31 | 2009-07-01 | 华为技术有限公司 | 一种资源释放控制方法及通讯***以及相关设备 |
CN101568178A (zh) * | 2008-04-22 | 2009-10-28 | 大唐移动通信设备有限公司 | 一种用户终端去附着方法、***及装置 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109906663A (zh) * | 2016-11-02 | 2019-06-18 | 华为技术有限公司 | 一种信息发送方法、设备和*** |
US10849097B2 (en) | 2016-11-02 | 2020-11-24 | Huawei Technologies Co., Ltd. | Information sending method, device, and system |
CN112911706A (zh) * | 2021-02-20 | 2021-06-04 | 中国联合网络通信集团有限公司 | 一种isr去激活方法、数据业务寻呼方法、msc以及sgw |
CN112911706B (zh) * | 2021-02-20 | 2023-02-17 | 中国联合网络通信集团有限公司 | 一种isr去激活方法、数据业务寻呼方法、msc以及sgw |
Also Published As
Publication number | Publication date |
---|---|
CN102934406A (zh) | 2013-02-13 |
CN102934406B (zh) | 2015-09-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6947878B2 (ja) | 無線通信システムにおける登録解除方法及びこのための装置 | |
JP6985455B2 (ja) | 無線通信システムにおけるネットワーク間の相互連動方法及びそのための装置 | |
JP6972023B2 (ja) | 無線通信システムの端末の方法、無線通信システムの基地局の方法、端末、及び基地局 | |
CN107548127B (zh) | 支持数据传输的方法和设备 | |
US11477633B2 (en) | Method and apparatus for managing packet data network connection on basis of local area in wireless communication system | |
KR101519547B1 (ko) | 사용자 장비의 위치 정보를 갱신하기 위한 방법 및 장치 | |
EP3100516B1 (en) | Efficient session management method and apparatus guaranteeing terminal mobility | |
US9491732B2 (en) | Paging processing method, user equipment and system | |
RU2607612C1 (ru) | Система мобильной связи, sgw, способ связи в терминале и способ управления | |
WO2017045149A1 (zh) | 一种释放无线资源控制rrc连接的方法及装置 | |
WO2008092408A1 (en) | Method, device and system for establishing s1 signaling connection in evolved network | |
WO2010031353A1 (zh) | 服务请求的处理方法、装置及*** | |
WO2009117879A1 (zh) | 一种指示服务网关承载管理的方法 | |
WO2016145575A1 (zh) | 一种业务处理方法、相关装置及*** | |
WO2010028580A1 (zh) | 网关设备负载处理方法、网络设备和网络*** | |
CN108307443B (zh) | 一种轻连接用户设备的业务控制的方法 | |
WO2017028637A1 (zh) | 网关的恢复处理方法及装置 | |
WO2012103773A1 (zh) | 中继***的过载控制方法及*** | |
WO2011097813A1 (zh) | 去激活isr的方法、修改承载参数的方法和网络*** | |
CN108307465B (zh) | 一种轻连接用户设备的连接控制的方法及设备 | |
WO2017166291A1 (zh) | 一种通信方法、终端、基站和移动性管理设备 | |
CN103781041B (zh) | 计费同步方法、装置及*** | |
WO2015176256A1 (zh) | 一种位置区更新的信息处理方法及装置 | |
WO2015024424A1 (zh) | Isr激活及去激活的方法 | |
WO2012167467A1 (zh) | 处理电路交换域业务返回传统网络的方法、移动管理实体和*** |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080001650.8 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10845487 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: 10845487 Country of ref document: EP Kind code of ref document: A1 |