WO2018119853A1 - 上下文释放方法、设备及系统 - Google Patents

上下文释放方法、设备及系统 Download PDF

Info

Publication number
WO2018119853A1
WO2018119853A1 PCT/CN2016/112970 CN2016112970W WO2018119853A1 WO 2018119853 A1 WO2018119853 A1 WO 2018119853A1 CN 2016112970 W CN2016112970 W CN 2016112970W WO 2018119853 A1 WO2018119853 A1 WO 2018119853A1
Authority
WO
WIPO (PCT)
Prior art keywords
context
release
context release
network side
request
Prior art date
Application number
PCT/CN2016/112970
Other languages
English (en)
French (fr)
Inventor
杨宁
Original Assignee
广东欧珀移动通信有限公司
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 广东欧珀移动通信有限公司 filed Critical 广东欧珀移动通信有限公司
Priority to PCT/CN2016/112970 priority Critical patent/WO2018119853A1/zh
Priority to CN201680091704.1A priority patent/CN110089193B/zh
Priority to JP2019535392A priority patent/JP7013474B2/ja
Priority to US16/474,014 priority patent/US20200128608A1/en
Priority to KR1020197021642A priority patent/KR20190100307A/ko
Priority to EP16925850.6A priority patent/EP3562259B1/en
Priority to TW106142300A priority patent/TW201824936A/zh
Publication of WO2018119853A1 publication Critical patent/WO2018119853A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to the field of communication technology applications, and in particular, to a context release method, device, and system.
  • the inactive state is introduced.
  • the terminal can move between cells in a certain area according to the mobility management mode when it is in an idle state, without performing measurement conversion, and at the same time, the relevant context and connection state of the terminal and the initial base station.
  • the same is stored in the terminal and the network side (at least in the initial base station on the network side), where the initial base station is the base station to which the cell to which the terminal belongs before the terminal transitions to the inactive state.
  • the terminal can be controlled to change from the inactive state to the connected state through the paging message, and then released through the radio resource control (English: Radio Resource Control; RRC) connection.
  • RRC Radio Resource Control
  • the present invention provides a context release method, device and system.
  • the technical solution is as follows:
  • the first aspect provides a context release method, including:
  • the terminal sends a context release request to the first base station, where the context release request is used to indicate the network
  • the side performs the release of the relevant context of the terminal.
  • the method further includes:
  • the terminal receives a context release response sent by the first base station.
  • the method before the sending, by the terminal, the context release request to the first base station, the method further includes:
  • the application layer or the non-access sublayer of the terminal determines that the terminal needs to transition from an inactive state to an idle state.
  • the terminal sends a context release request to the first base station, including:
  • the terminal sends the context release request to the first base station by using an access sublayer.
  • the context release request is a radio resource control RRC connection setup request carrying a release indication; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is carried An RRC connection setup complete message with a release indication; or the context release request is an RRC connection recovery complete request carrying a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • a context release method including:
  • the first base station receives a context release request sent by the terminal, where the context release request is used to indicate that the network side performs release of the related context of the terminal.
  • the method further includes:
  • the first base station sends a context release response to the terminal, where the context release response is used to trigger the terminal to release the related context.
  • the first base station triggers the network side device that saves the related context to release the related context, including:
  • the first base station sends the context release indication information to the network side device according to the context release request, where the context release indication information is used to indicate that the network side device performs the release of the related context;
  • the first base station sends a context release response to the terminal according to the context release completion information.
  • the first base station triggers the network side device that saves the related context to release the related context, including:
  • the first base station sends a context release authorization request to the core management device according to the context release request, where the context release authorization request is used to request the network side device to authorize the release of the related context.
  • the first base station receives the context release completion information sent by the core management device, where the context release completion information is sent by the core management device after triggering the network side device to release the related context, and is used to indicate the location Said network side device has completed the release of the relevant context;
  • the first base station sends a context release response to the terminal according to the context release completion information.
  • the first base station triggers the network side device that saves the related context to release the related context, including:
  • the first base station sends a context release authorization request to the core management device according to the context release request, where the context release authorization request is used to request the network side device to authorize the release of the related context.
  • the first base station sends a context release indication information to the network side device according to the context release authorization response, where the context release indication information is used to indicate that the network side device performs the release of the related context.
  • the first base station sends a context release response to the terminal according to the context release completion information.
  • the context release request is a radio resource control RRC connection setup request carrying a release indication; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is carried RRC connection establishment with release indication completes Or the context release request is an RRC connection recovery completion request carrying a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • the context release request is sent by a terminal accessing the first base station after determining that the terminal needs to transition from an inactive state to an idle state.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • a context release method comprising:
  • the core management device receives a context release authorization request sent by the first base station, where the context release authorization request is sent by the first base station after receiving a context release request sent by the terminal, where the context release request is used to indicate that the network side performs the The release of the relevant context of the terminal.
  • the method further includes:
  • the core management device releases the authorization request according to the context, and triggers the network side device that saves the related context to release the related context;
  • the core management device After the network side device releases the related context, the core management device sends a context release completion information to the first base station, where the context release completion information is used to indicate that the network side device has completed the related context. Release.
  • the core management device triggers the network side device that saves the related context to release the related context, including:
  • the core management device sends the context release indication information to the network side device according to the context release authorization request, where the context release indication information is used to indicate that the network side device performs the release of the related context.
  • the core management device sends the context release completion information to the first base station, including:
  • the core management device receives the context release completion information sent by the network side device, where the context release completion information is used to indicate that the network side device has completed the release of the related context;
  • the core management device sends the context release completion information to the first base station according to the context release completion information.
  • the method further includes:
  • the core management device generates a context release authorization response according to the context release authorization request, where the context release authorization response is used to indicate that the network side device that saves the related context is allowed to release the related context.
  • the core management device sends the context release authorization response to the first base station.
  • the context release request is sent after the terminal in the cell managed by the first base station determines that the transition from the inactive state to the idle state is required.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • a context release device including:
  • a sending module configured to send a context release request to the first base station, where the context release request is used to indicate that the network side performs release of the related context of the terminal.
  • the device further includes: a receiving module, configured to receive a context release response sent by the first base station.
  • a receiving module configured to receive a context release response sent by the first base station.
  • the device further includes:
  • a determining module configured to determine, by the application layer or the non-access sublayer, that the terminal needs to transition from an inactive state to an idle state.
  • the sending module is specifically configured to:
  • the context release request is sent to the first base station by using an access sublayer.
  • the context release request is a radio resource control RRC connection setup request carrying a release indication; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is carried An RRC connection setup complete message with a release indication; or the context release request is an RRC connection recovery complete request carrying a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • a context release device including:
  • a receiving module configured to receive a context release request sent by the terminal, where the context release request is used to indicate that the network side performs release of the related context of the terminal.
  • the device further includes:
  • a triggering module configured to trigger, according to the context release request, a network side device that saves the related context to release the related context
  • a sending module configured to send a context release response to the terminal, where the context release response is The terminal is triggered to release the relevant context.
  • the trigger module is specifically configured to:
  • Send module specifically for:
  • the trigger module is specifically configured to:
  • Send module specifically for:
  • the trigger module is specifically configured to:
  • context release indication information is used to indicate that the network side device performs release of the related context
  • Send module specifically for:
  • the context release request is a radio resource control RRC connection setup request carrying a release indication; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is carried An RRC connection setup complete message with a release indication; or the context release request is an RRC connection recovery complete request carrying a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • the context release request is sent by a terminal accessing the first base station after determining that the terminal needs to transition from an inactive state to an idle state.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • a context release device comprising:
  • a receiving module configured to receive a context release authorization request sent by the first base station, where the context release authorization request is sent by the first base station after receiving a context release request sent by the terminal, where the context release request is used to indicate the network side The release of the relevant context of the terminal is performed.
  • the device further includes:
  • a triggering module configured to release the authorization request according to the context, and trigger the network side device that saves the related context to release the related context;
  • a sending module configured to send, after the network side device releases the related context, context release completion information, where the context release completion information is used to indicate that the network side device has completed the related context Release.
  • the trigger module is specifically configured to:
  • the sending module is specifically configured to:
  • the device further includes:
  • a generating module configured to release an authorization request according to the context, and generate a context release authorization response,
  • the context release authorization response is used to indicate that the network side device that saves the related context is allowed to release the related context;
  • a sending module configured to send the context release authorization response to the first base station.
  • the context release request is sent after the terminal in the cell managed by the first base station determines that the transition from the inactive state to the idle state is required.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • a seventh aspect provides a context release system, including: a terminal and a first base station,
  • the terminal includes the context release device of any of the fourth aspects
  • the first base station includes the context release device of any of the fifth aspects.
  • system further includes: the context release device of any of the sixth aspects.
  • the context release method, device, and system provided by the embodiment of the present invention, when the terminal triggers the network side to release the related context, in the context release process, especially in the context release process in the inactive state, there is no need to first switch to the connection state. Switching to the idle state again effectively reduces the signaling interaction between the terminal and the network side, reduces signaling overhead, and simplifies the overall process.
  • FIG. 1 is a schematic diagram of an implementation environment of a context release system involved in a context release method provided in some embodiments of the present invention
  • FIG. 2-2 is a schematic flowchart of a method for establishing an RRC connection between a terminal and a first base station according to an embodiment of the present disclosure
  • 3-1 is a schematic flowchart of another context release method according to an embodiment of the present invention.
  • 3-2 is a schematic flowchart of triggering a network-side device to release a related context by a core management device according to an embodiment of the present disclosure
  • 3-3 is a schematic flowchart of a core management device sending context release completion information to a first base station according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of still another context release method according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of
  • 5-1 is a block diagram of a context release device according to an exemplary embodiment of the present invention.
  • FIG. 5-2 is a block diagram of another context release device according to an exemplary embodiment of the present invention.
  • FIG. 5-3 is a block diagram of still another context release device according to an exemplary embodiment of the present invention.
  • 6-1 is a block diagram of a context release device according to another exemplary embodiment of the present invention.
  • FIG. 6-2 is a block diagram of another context release device according to another exemplary embodiment of the present invention.
  • FIG. 7-1 is a block diagram of a context release device according to another exemplary embodiment of the present invention.
  • FIG. 7-2 is a block diagram of another context release device according to another exemplary embodiment of the present invention.
  • FIG. 7-3 is a block diagram of still another context release device according to another exemplary embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a context release device according to an exemplary embodiment of the present invention.
  • the context release system may be an LTE system or a 5G mobile communication system, or a heterogeneous network in which a plurality of mobile communication systems coexist.
  • the implementation environment may include: a first base station 110, a network side device 120, and a core management device. 130 and terminal 140.
  • the terminal 140 and the first base station 110 can communicate, and the first base station 110 can communicate with the network side device 120 and the core management device 130, respectively, and the network side device 120 and the core management device 130 can communicate.
  • the network side device 120 may include a base station, and/or a management device of the core network (such as an MME in LTE), and/or a network side central control node, where the foregoing base station includes at least
  • the initial base station is a base station to which the cell in which the terminal belongs before the terminal transitions to the inactive state.
  • the core management device 130 may be a server, or a server cluster composed of a plurality of servers, or a cloud computing service center.
  • the core management device may be a generalized concept, which may be a management device.
  • the core management device may be an MME, an MME cluster, or multiple MME clusters.
  • the core management device 130 can manage the first base station 110 and/or the network side device 120.
  • the terminal 140 can be a smartphone, a computer, a multimedia player, an e-reader, a wearable device, or the like.
  • the network side device 120 and the terminal 140 store related contexts of the terminal, and the related context may be part or all contexts related to the terminal.
  • the related context may include current bearer information, quality of service (QoS: QoS) information, security context, and the like related to the terminal.
  • QoS quality of service
  • the security context may include a network key and a non-access sublayer. :Non-Access Stratum; referred to as: NAS) serial number and so on.
  • the core management device 130 and the first base station 110 are different in devices represented by different mobile communication systems.
  • the core management device 130 may be one or more mobility management entities of the core network ( English: Mobility Management Entity; abbreviation: MME)
  • the first base station 110 may be an evolved base station (English: Evolved Node B; eNB for short);
  • the 5G mobile communication system is one or more management devices of the core network, first
  • the base station 110 is a next generation base station (English: generation Node B; abbreviated as: gNB).
  • the terminal usually has three states: an idle state, a connected state, and an inactive state.
  • the idle state refers to that the terminal is powered on, but does not establish radio resource control with the wireless network (English: Radio Resource Control; : RRC)
  • the state in which it is connected the connection state refers to the state in which the terminal is powered on and connected to the wireless network to establish radio resource control (English: Radio Resource Control; RRC for short);
  • the activation state is between the idle state and the connection state.
  • the inactive state the mobility management mode of the terminal is the same as the idle state, and the related context of the terminal and the initial base station is the same as the connection state.
  • the terminal 140 is currently in an inactive state
  • the network side device that saves the relevant context of the terminal before the transition to the inactive state is the network side device 120
  • the terminal in the inactive state is A cell in a certain area (which may be a range preset in the network side) may be moved between the cells, and it is assumed that the cell where the terminal 140 is currently located belongs to the first base station 110 (the first base station 110 may be the initial base station or may not be initial) Base station, this embodiment of the present invention does not After the terminal determines that the terminal needs to transition from the inactive state to the idle state, the terminal 140 can actively trigger the network side to perform the context release process, so that the network side device 120 storing the context of the terminal performs the release of the related context.
  • the terminal sends a context release request for instructing the network side to release the related context of the terminal to the first base station, and the first base station triggers the network side device to release the related context according to the context release request, and after the network side device releases the related context, And feeding back a context release response to the terminal, and after receiving the context release response sent by the first base station, the terminal may release the related context in the terminal.
  • the terminal may trigger the network side device to release the related context according to the context release request by the first base station, and the first base station may trigger the network side after being allowed by the core management device.
  • the device releases the related context, and the network management device can also trigger the network side device to release the related context.
  • the first base station may trigger the network side device to release the related context after being allowed by the core management device, as shown in FIG. 2-1, which specifically includes:
  • Step 201 The terminal determines that the terminal needs to transition from an inactive state to an idle state.
  • a high layer of the terminal may determine that the terminal needs to transition from an inactive state to an idle state.
  • the application layer acts as a high-level interaction with the user (that is, the application layer is user-oriented), and its main task is to directly provide services for the user's application process.
  • the application layer can specify the protocol that the application process follows when communicating. Every application managed by the application layer runs in its own process and usually has a separate virtual machine.
  • the process of the non-access sub-layer is a signaling process that needs to be processed by the terminal (also called User Equipment (UE)) and the core network (English: core network; CN: abbreviation: CN).
  • the RRC and Radio Access Network Application Part (RANAP) layer and the following protocol layers are called access sublayers (English: Access Stratum; AS: for short); Sex management (English: Mobile Management; abbreviation: MM), call control (English: Call Control; abbreviation: CC) and short message service (English: Short Message Service; referred to as: SMS) are called NAS.
  • RANAP Radio Access Network Application Part
  • the application layer can detect the network application in the terminal (that is, the network side needs to be An operating state of an interactive application, such as an instant messaging application (specifically, a process that can monitor the application), and determining, according to the operating state, whether the terminal needs to transition from an inactive state to an idle state, for example, when at least one terminal exists
  • an interactive application such as an instant messaging application (specifically, a process that can monitor the application)
  • the network application is in an open state
  • the application layer can determine that the terminal does not need to transition from the inactive state to the idle state.
  • the application layer can determine that the terminal needs to transition from the inactive state to the idle state.
  • the specific scenario may be: when the terminal is in an inactive state, if the application layer detects that the current terminal is open with a certain network application, such as a web browser, according to a preset rule, the application layer may consider that the user is When the network application operates, the terminal may perform data transmission with the network side in response to the corresponding user operation, and the application layer determines that the terminal may need to perform data transmission subsequently, because the terminal does not need to switch from the inactive state to the idle state, and the terminal maintains The inactive state can be converted to the connection state when the data needs to be transmitted; if the application layer detects that the current terminal has closed a certain network application, such as a web browser, according to the preset rule, the application layer can consider that the user is no longer After the operation of the network application, the terminal may not need to perform data transmission with the network side in response to the user operation, the application layer determines that the terminal may not need to perform data transmission subsequently, and therefore, the terminal may transition from the inactive state to the idle state.
  • the non-access sub-layer can detect the transceiving state of the NAS signaling in the terminal, and determine whether the terminal needs to transition from the inactive state to the idle state according to the transceiving state. For example, when at least one NAS signaling is in the to-be-transmitted state, The non-access sub-layer can determine that the terminal does not need to transition from the inactive state to the idle state. When there is no NAS signaling to be sent or received in the terminal, the application layer can determine that the terminal needs to transition from the inactive state to the idle state.
  • the specific scenario may be: when there is a signaling to be sent or received in the non-access sub-layer, indicating that the terminal and the core network need to perform signaling transmission, the non-access sub-layer determines that the terminal may need to perform signaling transmission subsequently. Therefore, the terminal does not need to switch from the inactive state to the idle state, and the terminal can remain in the inactive state.
  • the terminal When the subsequent signaling needs to be transmitted, the terminal can be converted into the connected state; when the non-access sublayer does not have the signaling to be sent and received, It is indicated that the terminal and the network side do not need to perform signaling transmission at present, and the non-access sublayer determines that the terminal does not need to perform signaling transmission at present, therefore, the terminal can switch from the inactive state to the idle state, thereby disconnecting the terminal from the network side. Reduce the energy consumption of the terminal.
  • Step 202 The terminal sends a context release request to the first base station.
  • the context release request is used to instruct the network side to perform release of the relevant context of the terminal.
  • the terminal may send a context release request to the first base station by using the access sublayer.
  • the terminal needs to establish an RRC connection with the first base station before the information can be exchanged.
  • RRC connection For the process of establishing an RRC connection between the terminal and the first base station, reference may be made to Figure 2-2, including:
  • Step 2021 The terminal sends an RRC connection setup request to the first base station (English: RRC Connection Resume Request).
  • the terminal may send an RRC connection setup request to the first base station according to the pre-received paging message.
  • Step 2022 The first base station sends an RRC connection setup response (English: RRC Connection Resume) to the terminal.
  • RRC connection setup response English: RRC Connection Resume
  • Step 2023 The terminal sends an RRC Setup Complete message (English: RRC Connection Resume Complete) to the first base station.
  • RRC Setup Complete message English: RRC Connection Resume Complete
  • the terminal will trigger an RRC connection reestablishment process.
  • the process is intended to reconstruct an RRC connection, which may include recovery of signaling radio bearer 1 (English: signalling radio bearers 1; SRB1) operation, and secure reactivation.
  • the terminal may send an RRC connection recovery request to the first base station, and after receiving the RRC connection recovery request, the first base station may send an RRC connection recovery response to the terminal according to the RRC connection recovery request, and the terminal receives the After the RRC connection recovery response, the RRC connection recovery response may be configured accordingly.
  • the RRC connection recovery complete request is sent to the first base station to notify the first base station to complete the RRC connection reestablishment process.
  • the context release request in the embodiment of the present invention may be a new signaling, or may be multiplexed with traditional signaling.
  • the context release request may be multiplexed with the signaling in the RRC connection establishment process, for example, the context release request may be an RRC connection setup request carrying a release indication (English: release indication); or the context release request is carried Release the indicated RRC connection setup complete message; on the other hand, the context release request may be multiplexed with the signaling in the RRC connection reestablishment process, for example, the context release request may be an RRC connection recovery request carrying a release indication; or The context release request is an RRC connection recovery complete request carrying a release indication.
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • the release The form of the indication may be consistent with the current RRC protocol, and the message carrying the release indication may be used to enable the terminal to trigger the release of the relevant context on the network side.
  • Step 203 The first base station sends a context release authorization request to the core management device according to the context release request.
  • the first base station may send a context release authorization request to the core management device to request the core management device to authorize the release of the context of the network side device.
  • the context release authorization request may also carry the release indication.
  • Step 204 The core management device releases the authorization request according to the context, and generates a context release authorization response.
  • the core management device releases the authorization request according to the context, and can determine whether the network side device is allowed to release the related context. For example, the core management device can predict whether the terminal has data transmission in the preset time period. If it is predicted that the terminal has data transmission in the preset time period, the network side device is not allowed to release the related context, thereby avoiding the terminal and the network. If the network is not connected to the network, the network side device is allowed to release the related context. This reduces the load on the network side device.
  • the core management device counts down when receiving the context release authorization request, and the duration of the countdown is equal to the duration of the preset time period. If the core network receives the data transmission request for the terminal before the countdown ends, the preset is predicted. There is data transmission in the terminal during the time period.
  • the core management device may generate a context release authorization response.
  • the context release authorization response is used to indicate that the network side device is allowed to release the related context.
  • Step 205 The core management device sends a context release authorization response to the first base station.
  • Step 206 The first base station releases the authorization response according to the context, and sends the context release indication information to the network side device.
  • the first base station may release the authorization response according to the context, where the context release indication information is used to indicate that the network side device performs the release of the related context.
  • the first base station sends the context release indication information to the network side device to trigger the network side device to release the related context.
  • Step 207 The network side device releases the related context according to the context release indication information.
  • the process of releasing the related context is essentially a process in which the network side device deletes the related context.
  • the process of releasing the related context is essentially a process in which the network side device deletes the related context.
  • the process of releasing the related context refers to the content in the related protocol, which is not described in detail in this embodiment of the present invention.
  • Step 208 The network side device sends the context release completion information to the first base station.
  • the context release completion information may be sent to the first base station to notify the first base station.
  • the context release completion information is used to indicate that the network side device has completed the release of the related context.
  • Step 209 The first base station sends a context release response to the terminal according to the context release completion information.
  • the first base station may send a context release response to the terminal to notify the terminal that the network side device has completed the release of the related context, where the content in the context release completion information and the context release response may be the same, Can be different.
  • Step 210 The terminal releases the response according to the context, and releases the related context in the terminal.
  • the terminal may release the response according to the context, and release the related context of the terminal to reduce the load of the user.
  • the terminal may not release the related context. .
  • the network side device may indirectly trigger the network side device to release the related context by the core management device, as shown in Figure 3-1, which specifically includes:
  • Step 301 The terminal determines that the terminal needs to transition from an inactive state to an idle state.
  • step 301 For the specific process of step 301, refer to step 201, which is not described in detail in the embodiment of the present invention.
  • Step 302 The terminal sends a context release request to the first base station.
  • step 302 The foregoing context release request is used to instruct the network side to perform release of the related context of the terminal.
  • step 302 For other content in step 302, reference may be made to step 202, which is not described in detail in the embodiment of the present invention.
  • Step 303 The first base station sends a context release authorization request to the core management device according to the context release request.
  • step 303 The foregoing context release authorization request is used to request that the network side device be authorized to release the related context.
  • step 303 For other content in step 303, reference may be made to step 203, which is not described in detail in the embodiment of the present invention.
  • Step 304 The core management device releases the authorization request according to the context, and triggers saving the relevant upper and lower
  • the network side device of the text releases the relevant context.
  • the core management device releases the authorization request according to the context
  • the process of triggering the network side device that saves the related context to release the related context may include:
  • Step 3041 The core management device sends a context release indication information to the network side device according to the context release authorization request, where the context release indication information is used to indicate that the network side device performs the release of the related context.
  • the core management device releases the authorization request according to the context, and can determine whether the network side device is allowed to release the related context. For example, the core management device can predict whether the terminal has data transmission in the preset time period. If it is predicted that the terminal has data transmission in the preset time period, the network side device is not allowed to release the related context, thereby avoiding the terminal and the network. If the network is not connected to the network, the network side device is allowed to release the related context. This reduces the load on the network side device.
  • the core management device counts down when receiving the context release authorization request, and the duration of the countdown is equal to the duration of the preset time period. If the core network receives the data transmission request for the terminal before the countdown ends, the preset is predicted. There is data transmission in the terminal during the time period.
  • the core management device may send the context release indication information to the network side device to trigger the network side device to release the related context.
  • Step 3042 The network side device releases the related context according to the context release indication information.
  • Step 3042 can refer to the foregoing step 207, which is not described in detail in the embodiment of the present invention.
  • Step 305 The core management device sends the context release completion information to the first base station.
  • the foregoing context release completion information is used to indicate that the network side device has completed the release of the related context.
  • the process for the core management device to send the context release completion information to the first base station may include:
  • Step 3051 The network side device sends the context release completion information to the core management device, where the context release completion information is used to indicate that the network side device has completed the release of the related context.
  • the context release completion information may be sent to the core management device to notify the core management device.
  • Step 3052 The core management device sends the context release completion information to the first base station according to the context release completion information.
  • Receiving the context release completion information by the core management device may send the context release to the first base station
  • the completion information is sent to notify the first base station that the network side device has completed the release of the relevant context.
  • context release completion information sent by the network side sending device and the context release completion information sent by the core management device may be the same or different.
  • Step 306 The first base station sends a context release response to the terminal according to the context release completion information.
  • the step 306 can refer to the foregoing step 209, which is not described in detail in the embodiment of the present invention.
  • Step 307 The terminal releases the response according to the context, and releases the related context in the terminal.
  • the step 307 can refer to the foregoing step 210, which is not described in detail in the embodiment of the present invention.
  • the first base station may directly trigger the network side device to release the related context, as shown in FIG. 4, which specifically includes:
  • Step 401 The terminal determines that the terminal needs to transition from an inactive state to an idle state.
  • step 401 For the specific process of the step 401, reference may be made to the step 201, which is not described in detail in the embodiment of the present invention.
  • Step 402 The terminal sends a context release request to the first base station.
  • step 402 The foregoing context release request is used to instruct the network side to perform release of the related context of the terminal.
  • step 402 For other content in step 402, reference may be made to step 202, which is not described in detail in the embodiment of the present invention.
  • Step 403 The first base station sends the context release indication information to the network side device according to the context release request.
  • the first base station may send the context release indication information to the network side device according to the context release request, to trigger the network side device to release the related context.
  • the context release indication information is used to indicate that the network side device performs release of the related context.
  • Step 404 The network side device releases the related context according to the context release indication information.
  • Step 404 can refer to step 207, which is not described in detail in the embodiment of the present invention.
  • Step 405 The network side device sends the context release completion information to the first base station.
  • the context release completion information is used to indicate that the network side device has completed the release of the related context.
  • the context release completion information is used to indicate that the network side device has completed the release of the related context.
  • Step 406 The first base station sends a context release response to the terminal according to the context release completion information.
  • the step 406 can refer to the foregoing step 209, which is not described in detail in the embodiment of the present invention.
  • Step 407 The terminal releases the response according to the context, and releases the related context in the terminal.
  • the step 407 can refer to the foregoing step 210, which is not described in detail in the embodiment of the present invention.
  • a release indication can be directly added to a paging message sent by the network side, so that the terminal directly releases the relevant context and enters an idle state.
  • a new manner in which the terminal triggers the network side to release the related context is provided, which increases the flexibility of the related context release.
  • the context release method provided by the embodiment of the present invention triggers the release of the related context by the terminal, and does not need to first switch to the connection state during the context release process, especially in the context release process in the inactive state. Switching to the idle state again effectively reduces the signaling interaction between the terminal and the network side, reduces signaling overhead, and simplifies the overall process.
  • the embodiment of the present invention provides a context release device 50, as shown in FIG. 5-1, including:
  • the sending module 501 is configured to send a context release request to the first base station, where the context release request is used to instruct the network side to perform release of the related context of the terminal.
  • the context release device provided by the embodiment of the present invention triggers the network side to release the related context by using the sending module, and does not need to first switch to the connection state during the context release process, especially in the context release process in the inactive state. Then, the switch to the idle state effectively reduces the signaling interaction between the terminal and the network side, reduces the signaling overhead, and simplifies the overall process.
  • the device 50 further includes:
  • the receiving module 502 is configured to receive a context release response sent by the first base station.
  • the device 50 further includes:
  • the determining module 503 is configured to determine, by using an application layer or a non-access sublayer, that the terminal needs to transition from an inactive state to an idle state.
  • the sending module 501 is specifically configured to:
  • the context release request is sent to the first base station by using an access sublayer.
  • the context release request is a radio resource control RRC connection carrying a release indication.
  • the establishment request is received; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is an RRC connection setup complete message carrying a release indication; or the context release request is carried An RRC connection recovery completion request with a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • the context release device provided by the embodiment of the present invention triggers the network side to release the related context by using the sending module, and does not need to first switch to the connection state during the context release process, especially in the context release process in the inactive state. Then, the switch to the idle state effectively reduces the signaling interaction between the terminal and the network side, reduces the signaling overhead, and simplifies the overall process.
  • the embodiment of the present invention provides a context release device 60, as shown in Figure 6-1, including:
  • the receiving module 601 is configured to receive a context release request sent by the terminal, where the context release request is used to instruct the network side to perform release of the related context of the terminal.
  • the context release device provided by the embodiment of the present invention triggers the release of the related context by the terminal, and does not need to first switch to the connection state during the context release process, especially in the context release process in the inactive state. Switching to the idle state again effectively reduces the signaling interaction between the terminal and the network side, reduces signaling overhead, and simplifies the overall process.
  • the device 60 further includes:
  • the triggering module 602 is configured to trigger, according to the context release request, a network side device that saves the related context to release the related context.
  • the sending module 603 is configured to send a context release response to the terminal, where the context release response is used to trigger the terminal to release the related context.
  • the triggering module 602 is specifically configured to:
  • the sending module 603 is specifically configured to:
  • the triggering module 602 is specifically configured to:
  • the sending module 603 is specifically configured to:
  • the triggering module 602 is specifically configured to:
  • context release indication information is used to indicate that the network side device performs release of the related context
  • the sending module 603 is specifically configured to:
  • the context release request is a radio resource control RRC connection setup request carrying a release indication; or the context release request is an RRC connection recovery request carrying a release indication; or the context release request is carried An RRC connection setup complete message with a release indication; or the context release request is an RRC connection recovery complete request carrying a release indication;
  • the release indication is used to instruct the network side to perform release of the related context of the terminal.
  • the context release request is sent by a terminal accessing the first base station after determining that the terminal needs to transition from an inactive state to an idle state.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • the embodiment of the present invention provides a context release device 70.
  • the device 70 includes:
  • the receiving module 701 is configured to receive a context release authorization request sent by the first base station, where the context release authorization request is sent by the first base station after receiving a context release request sent by the terminal, where the context release request is used to indicate the network
  • the side performs the release of the relevant context of the terminal.
  • the context release device provided by the embodiment of the present invention triggers the release of the related context by the terminal, and does not need to first switch to the connection state during the context release process, especially in the context release process in the inactive state. Switching to the idle state again effectively reduces the signaling interaction between the terminal and the network side, reduces signaling overhead, and simplifies the overall process.
  • the device further includes:
  • the triggering module 702 is configured to: according to the context release authorization request, trigger the network side device that saves the related context to release the related context;
  • the sending module 703 is configured to send the context release completion information to the first base station after the network side device releases the related context, where the context release completion information is used to indicate that the network side device has completed the correlation The release of the context.
  • the triggering module 702 is specifically configured to:
  • the sending module 703 is specifically configured to:
  • the device 70 further includes:
  • a generating module 704 configured to generate a context release authorization response according to the context release authorization request, where the context release authorization response is used to indicate that the network side device is allowed to release the related context;
  • the sending module 705 is configured to send the context release authorization response to the first base station.
  • the context release request is sent after the terminal in the cell managed by the first base station determines that the transition from the inactive state to the idle state is required.
  • the network side device includes an initial base station, and/or a management device of a core network, and/or a network side central control node;
  • the initial base station is a base station to which the cell in which the terminal belongs before transitioning to the inactive state.
  • An embodiment of the present invention provides a context release system, including: a terminal and a first base station,
  • the terminal may include the context release device described in any of the foregoing Figures 5-1 to 5-3;
  • the first base station may include the context release device of any of Figures 6-1 to 6-2.
  • system further includes: the context release device of any of Figures 7-1 to 7-3.
  • the context release system provided by the embodiment of the present invention triggers the release of the related context by the terminal, and does not need to switch to the connection state in the context release process, especially in the context release process in the inactive state. Switching to the idle state again effectively reduces the signaling interaction between the terminal and the network side, reduces signaling overhead, and simplifies the overall process.
  • FIG. 8 is a schematic structural diagram of a context release device 10 according to an exemplary embodiment of the present invention.
  • the context release device 10 may be the first base station 110, the network side device 120, the core management device 130, or the terminal 140.
  • the network device 10 includes a processor 12 and a network interface 14.
  • Processor 12 includes one or more processing cores.
  • the processor 12 executes various functional applications and data processing by running software programs and modules.
  • Network interfaces 14 There may be multiple network interfaces 14, which are used to communicate with other storage devices or network devices.
  • the network device 10 further includes components such as a memory 16, a bus 18, and the like.
  • the memory 16 and the network interface 14 are connected to the processor 12 via a bus 18, respectively.
  • Memory 16 can be used to store software programs as well as modules. Specifically, the memory 16 can store an operating system 162, an application module 164 required for at least one function.
  • the operating system 162 can be an operating system such as Real Time eXecutive (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • the network interface 14 can be a transceiver antenna (which can also be regarded as a transmitter and a receiver), and the application module 164 stored in the memory 16 can perform the above step 203. Steps 206, 209, 303, 306, 403, or 406;
  • the network interface 14 may be a transceiver antenna (which may also be regarded as a transmitter and a receiver), and the application module 164 stored in the memory 16 may perform the above steps 201, 202, 210, and 301. Steps such as step 302, step 307, step 401, step 402 or step 407;
  • the application module 164 stored in the memory 16 can perform the steps of step 204, step 202, step 210, step 304, step 305 and the like described above.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本申请提供了一种上下文释放方法、设备及系统，涉及通信技术应用领域，所述方法包括：终端向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。本发明解决了目前的上下文释放流程较为复杂的问题，能够有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。本申请用于移动通信系统中上下文的释放。

Description

上下文释放方法、设备及系统 技术领域
本公开涉及通信技术应用领域，特别涉及一种上下文释放方法、设备及系统。
背景技术
随着社会发展和科技进步，用户对移动终端接入技术提出更高的要求。在第四代移动通信技术(英文：4rd-Generation；简称：4G)移动通信系统的长期演进(英文：Long Term Evolution；简称：LTE)系统以及5G移动通信系统中，除了大家所熟知的空闲(英文：idle)状态与连接(英文：connected)状态之外，引入了非激活(英文：inactive)状态。在非激活状态中，终端可以按照其处于空闲状态时的移动性管理方式在一定区域范围内的小区之间移动，无需进行测量转换，与此同时，终端与初始基站的相关上下文与连接状态时相同，该相关上下文分别保存在终端和网络侧(在网络侧至少保存在初始基站中)，其中，初始基站为终端转换至非激活状态之前所在小区所属的基站。
目前，如果网络侧需要终端由非激活状态转换至空闲状态，可以通过寻呼消息控制终端由非激活状态转换至连接状态，再通过无线资源控制(英文：Radio Resource Control；简称：RRC)连接释放消息，控制终端由连接状态转换至空闲状态，并释放终端与初始基站的相关上下文(Context)，相应的，网络侧也释放保存的相关上下文。
但是，上述非激活状态下的上下文释放方法中，网络侧与终端需要交互较多的消息才能实现上下文的释放，整体流程较为复杂。
发明内容
为了解决目前的上下文释放流程较为复杂的问题，本发明提供了一种上下文释放方法、设备及系统。所述技术方案如下：
第一方面提供一种上下文释放方法，包括：
终端向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络 侧进行所述终端的相关上下文的释放。
可选的，所述终端向第一基站发送上下文释放请求之后，所述方法还包括：
所述终端接收所述第一基站发送的上下文释放响应。
可选的，在所述终端向第一基站发送上下文释放请求之前，所述方法还包括：
所述终端的应用层或非接入子层确定所述终端需要从非激活状态转换至空闲状态。
可选的，所述终端向第一基站发送上下文释放请求，包括：
所述终端通过接入子层向第一基站发送所述上下文释放请求。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
第二方面，提供一种上下文释放方法，包括：
第一基站接收终端发送的上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
可选的，在所述第一基站接收终端发送的上下文释放请求之后，所述方法还包括：
所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
所述第一基站向所述终端发送上下文释放响应，所述上下文释放响应用于触发所述终端释放所述相关上下文。
可选的，所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
所述第一基站根据所述上下文释放请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
所述第一基站向所述终端发送上下文释放响应，包括：
所述第一基站接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
所述第一基站根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
所述第一基站向所述终端发送上下文释放响应，包括：
所述第一基站接收所述核心管理设备发送的上下文释放完成信息，所述上下文释放完成信息为所述核心管理设备在触发所述网络侧设备释放所述相关上下文后发送的，用于指示所述网络侧设备已完成所述相关上下文的释放；
所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
所述第一基站根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
所述第一基站接收所述核心管理设备发送的上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
所述第一基站根据所述上下文释放授权响应，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
所述第一基站向所述终端发送上下文释放响应，包括：
所述第一基站接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消 息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述上下文释放请求是接入所述第一基站的终端在确定所述终端需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
第三方面，提供一种上下文释放方法，所述方法包括：
核心管理设备接收第一基站发送的上下文释放授权请求，所述上下文释放授权请求是所述第一基站在接收终端发送的上下文释放请求后发送的，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述核心管理设备接收第一基站发送的上下文释放授权请求之后，所述方法还包括：
所述核心管理设备根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
所述核心管理设备在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放。
可选的，所述核心管理设备根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
所述核心管理设备根据所述上下文释放授权请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
所述核心管理设备在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，包括：
所述核心管理设备接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
所述核心管理设备根据所述上下文释放完成信息，向所述第一基站发送上下文释放完成信息。
可选的，所述核心管理设备接收第一基站发送的上下文释放授权请求之后，所述方法还包括：
所述核心管理设备根据所述上下文释放授权请求，生成上下文释放授权响应，所述上下文释放授权响应用于指示允许保存有所述相关上下文的网络侧设备进行所述相关上下文的释放；
所述核心管理设备向所述第一基站发送所述上下文释放授权响应。
可选的，所述上下文释放请求是所述第一基站管理的小区中的终端确定需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
第四方面，提供一种上下文释放设备，包括：
发送模块，用于向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述设备还包括：接收模块，用于接收所述第一基站发送的上下文释放响应。
可选的，所述设备还包括：
确定模块，用于通过应用层或非接入子层确定所述终端需要从非激活状态转换至空闲状态。
可选的，所述发送模块，具体用于：
通过接入子层向第一基站发送所述上下文释放请求。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
第五方面，提供一种上下文释放设备，包括：
接收模块，用于接收终端发送的上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述设备还包括：
触发模块，用于根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
发送模块，用于向所述终端发送上下文释放响应，所述上下文释放响应用 于触发所述终端释放所述相关上下文。
可选的，触发模块，具体用于：
根据所述上下文释放请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
发送模块，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，触发模块，具体用于：
根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
发送模块，具体用于：
接收所述核心管理设备发送的上下文释放完成信息，所述上下文释放完成信息为所述核心管理设备在触发所述网络侧设备释放所述相关上下文后发送的，用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，触发模块，具体用于：
根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
接收所述核心管理设备发送的上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
根据所述上下文释放授权响应，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
发送模块，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述上下文释放请求是接入所述第一基站的终端在确定所述终端需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
第六方面，提供一种上下文释放设备，所述设备包括：
接收模块，用于接收第一基站发送的上下文释放授权请求，所述上下文释放授权请求是所述第一基站在接收终端发送的上下文释放请求后发送的，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述设备还包括：
触发模块，用于根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
发送模块，用于在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放。
可选的，所述触发模块，具体用于：
根据所述上下文释放授权请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
所述发送模块，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述第一基站发送上下文释放完成信息。
可选的，所述设备还包括：
生成模块，用于根据所述上下文释放授权请求，生成上下文释放授权响应， 所述上下文释放授权响应用于指示允许保存有所述相关上下文的网络侧设备进行所述相关上下文的释放；
发送模块，用于向所述第一基站发送所述上下文释放授权响应。
可选的，所述上下文释放请求是所述第一基站管理的小区中的终端确定需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
第七方面，提供一种上下文释放系统，包括：包括：终端和第一基站，
所述终端包括第四方面任一所述的上下文释放设备；
所述第一基站包括第五方面任一所述的上下文释放设备。
可选的，所述系统还包括：第六方面任一所述的上下文释放设备。
本发明实施例中提供的上下文释放方法、设备及系统，通过终端触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明部分实施例中提供的上下文释放方法所涉及的上下文释放系统的实施环境的示意图；
图2-1是本发明实施例提供的一种上下文释放方法的流程示意图；
图2-2是本发明实施例提供的一种终端与第一基站建立RRC连接的方法流程示意图；
图3-1是本发明实施例提供的另一种上下文释放方法的流程示意图；
图3-2是本发明实施例提供的一种核心管理设备触发网络侧设备释放相关上下文的流程示意图；
图3-3是本发明实施例提供的一种核心管理设备向第一基站发送上下文释放完成信息的流程示意图；
图4是本发明实施例提供的又一种上下文释放方法的流程示意图；图1是
图5-1是本发明一示意性实施例提供的一种上下文释放设备的框图；
图5-2是本发明一示意性实施例提供的另一种上下文释放设备的框图；
图5-3是本发明一示意性实施例提供的又一种上下文释放设备的框图；
图6-1是本发明另一示意性实施例提供的一种上下文释放设备的框图；
图6-2是本发明另一示意性实施例提供的另一种上下文释放设备的框图；
图7-1是本发明又一示意性实施例提供的一种上下文释放设备的框图；
图7-2是本发明又一示意性实施例提供的另一种上下文释放设备的框图；
图7-3是本发明又一示意性实施例提供的又一种上下文释放设备的框图；
图8是本发明一示意性实施例提供的一种上下文释放设备的结构示意图。
通过上述附图，已示出本发明明确的实施例，后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本发明构思的范围，而是通过参考特定实施例为本领域技术人员说明本发明的概念。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
请参见图1，其示出了本发明部分实施例中提供的上下文释放方法所涉及的上下文释放系统的实施环境的示意图。该上下文释放系统可以为LTE系统或者5G移动通信系统，或者多种移动通信系统并存的混合网络(heterogeneous network)等等，该实施环境可以包括：第一基站110、网络侧设备120、核心管理设备130和终端140。其中，终端140和第一基站110可以进行通信，第一基站110可以分别与网络侧设备120和核心管理设备130进行通信，网络侧设备120和核心管理设备130可以进行通信。
在本发明实施例中，网络侧设备120可以包括基站，和/或，核心网的管理设备(如LTE中的MME)，和/或，网络侧中心控制节点，上述基站至少包括 初始基站，该初始基站为终端转换至非激活状态之前所在小区所属的基站。核心管理设备130可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心，在本发明实施例中核心管理设备可以是一个广义的概念，其可以是一个管理设备，也可以是一个管理设备簇，也可以是多个管理设备簇，示例的，在LTE系统中，该核心管理设备可以是一个MME，也可以是一个MME簇，也可以是多个MME簇，该核心管理设备130可以管理第一基站110和/或网络侧设备120。终端140可以为智能手机、电脑、多媒体播放器、电子阅读器、可穿戴式设备等。其中，网络侧设备120和终端140中保存有终端的相关上下文，该相关上下文可以为与终端相关的部分或所有上下文。该相关上下文可以包括与终端相关的当前的承载信息、服务质量(英文：Quality ofService；简称：QoS)信息和安全上下文等等，例如，安全上下文可以包括网络密钥和非接入子层(英文：Non-Access Stratum；简称：NAS)序列号等。
上述实施环境中，核心管理设备130和第一基站110在不同移动通信系统中所代表的设备不同，例如，在LTE系统中，核心管理设备130可以为核心网的一个或多个移动管理实体(英文：Mobility Management Entity；简称：MME)，第一基站110可以为演进型基站(英文：Evolved Node B；简称：eNB)；在5G移动通信系统为核心网的一个或多个管理设备，第一基站110为下一代基站(英文：generation Node B；简称：gNB)。
在上述实施环境中，终端通常有三种状态：空闲状态、连接状态和非激活状态，其中，空闲状态指的是终端已开机，但没有与无线网络建立无线资源控制(英文：Radio Resource Control；简称：RRC)连接时，其所处的状态；连接状态指的是终端已开机，且与无线网络建立无线资源控制(英文：Radio Resource Control；简称：RRC)连接时，其所处的状态；非激活状态介于空闲状态与连接状态之间，在非激活状态中，终端的移动性管理方式与空闲状态相同，终端与初始基站的相关上下文与连接状态时相同。
在本发明实施例中，假设终端140当前处于非激活状态，在其转换至该非激活状态之前保存该终端的相关上下文的网络侧设备为上述网络侧设备120，由于处于非激活状态的终端在一定区域范围内(可以是网络侧预先设置的一个范围)的小区之间可以移动，假设，终端140当前所在的小区属于第一基站110(该第一基站110可以为初始基站也可以不为初始基站，本发明实施例对此不 作限定)，则在终端确定该终端需要从非激活状态转换至空闲状态后，终端140可以主动触发网络侧执行上下文释放流程，使得存储有终端的上下文的网络侧设备120进行相关上下文的释放。具体的，终端向第一基站发送用于指示网络侧进行终端的相关上下文的释放的上下文释放请求，第一基站根据上下文释放请求触发网络侧设备释放相关上下文，并在网络侧设备释放相关上下文后，向终端反馈上下文释放响应，终端在接收第一基站发送的上下文释放响应后，可以释放终端中的相关上下文。
在本发明实施例中，终端可以通过向发送上下文释放请求，由第一基站根据上下文释放请求触发网络侧设备释放相关上下文，其中，第一基站可以在经过核心管理设备的允许后再触发网络侧设备释放相关上下文，也可以间接由核心管理设备触发网络侧设备释放相关上下文，还可以直接触发网络侧设备释放相关上下文。本发明实施例以以下几方面为例进行说明：
第一方面，第一基站可以在经过核心管理设备的允许后再触发网络侧设备释放相关上下文，如图2-1所示，具体包括：
步骤201、终端确定终端需要从非激活状态转换至空闲状态。
在本发明实施例中，终端的高层，例如，应用层(英文：Application Layer)或非接入子层，可以确定终端需要从非激活状态转换至空闲状态。
其中，应用层作为和用户交互的高层(也即是应用层是面向用户的)，其主要任务是直接为用户的应用进程提供服务。应用层可以规定应用进程在通信时所遵循的协议。应用层所管理的每一个应用程序都在它自己的进程中运行，通常都拥有一个独立的虚拟机。
在协议栈中，非接入子层的流程是终端(也称用户设备(英文：User Equipment；简称：UE))和核心网(英文：core network；简称：CN)需要处理的信令流程。RRC和无线接入网络应用部分(英文：Radio Access Network Application Part；简称：RANAP)层及其以下的协议层称为接入子层(英文：Access Stratum；简称：AS)；它们之上的移动性管理(英文：Mobile Management；简称：MM)、呼叫控制(英文：Call Control；简称：CC)和短信服务(英文：Short Message Service；简称：SMS)等称为NAS。
在本发明实施例中，应用层可以检测终端中的网络应用(即需要与网络侧 进行交互的应用，例如即时通讯应用)的运行状态(具体的，可以监控该应用的进程)，根据该运行状态确定终端是否需要从非激活状态转换至空闲状态，例如，当终端中存在至少一个网络应用处于开启状态，应用层可以确定终端不需要从非激活状态转换至空闲状态，当终端中所有的网络应用处于关闭状态，应用层可以确定终端需要从非激活状态转换至空闲状态。
示例的，具体场景可以为：在终端处于非激活状态时，若应用层监测到当前终端开启着某一网络应用，如网页浏览器，根据预设的规则，应用层可以认为用户正在对该某一网络应用进行操作，终端后续可能与网络侧进行数据传输以响应相应的用户操作，则应用层确定该终端后续可能需要进行数据传输，因为，终端无需从非激活状态转换至空闲状态，终端保持非激活状态即可，在需要传输数据时，可以转换成连接状态；若应用层监测到当前终端关闭了某一网络应用，如网页浏览器，根据预设的规则，应用层可以认为用户不再对该某一网络应用进行操作，终端后续可能无需与网络侧进行数据传输以响应用户操作，则应用层确定该终端后续可能无需进行数据传输，因此，终端可以从非激活状态转换至空闲状态，从而断开终端与网络侧连接，减少终端的能耗。
非接入子层可以检测终端中的NAS信令的收发状态，根据该收发状态确定终端是否需要从非激活状态转换至空闲状态，例如，当终端中存在至少一个NAS信令处于待收发状态，非接入子层可以确定终端不需要从非激活状态转换至空闲状态，当终端中不存在待收发的NAS信令，应用层可以确定终端需要从非激活状态转换至空闲状态。
示例的，具体场景可以为：当非接入子层中存在待收发的信令，说明终端和核心网需要进行信令传输，则非接入子层确定该终端后续可能需要进行信令传输，因此，终端无需从非激活状态转换至空闲状态，终端保持非激活状态即可，在后续需要传输信令时，终端可以转换成连接状态；当非接入子层不存在待收发的信令，说明终端与网络侧当前不需要进行信令传输，则非接入子层确定该终端当前无需进行信令传输，因此，终端可以从非激活状态转换至空闲状态，从而断开终端与网络侧连接，减少终端的能耗。
实际应用中，还可以采用其他方式确定终端需要从非激活状态转换至空闲状态，本发明实施例对此不做限定。
步骤202、终端向第一基站发送上下文释放请求。
该上下文释放请求用于指示网络侧进行终端的相关上下文的释放。可选 的，终端可以通过接入子层向第一基站发送上下文释放请求。
实际应用中，终端需要和第一基站建立RRC连接，然后才能进行信息的交互。终端与第一基站建立RRC连接的过程可以参考图2-2，包括：
步骤2021、终端向第一基站发送RRC连接建立请求(英文：RRC Connection Resume Request)。
可选的，终端可以根据预先接收寻呼消息向第一基站发送RRC连接建立请求。
步骤2022、第一基站向终端发送RRC连接建立响应(英文：RRC Connection Resume)。
步骤2023、终端向第一基站发送RRC建立完成消息(英文：RRC Connection Resume Complete)。
上述步骤2021至2023的具体过程可以参考LTE RRC协议：3GPP36.331，本发明实施例对比不作赘述。
需要说明的是，当终端和第一基站完成了RRC连接的建立后，如果出现切换失败、无线链路失败、完整性保护失败或RRC重配置失败等情况，终端将会触发RRC连接重建过程。该过程旨在重建RRC连接，可以包括信令无线承载1(英文：signalling radio bearers1；简称：SRB1)操作的恢复，以及安全的重新激活等。示例的，终端可以向第一基站发送RRC连接恢复请求，第一基站在接收到该RRC连接恢复请求后，可以根据该RRC连接恢复请求，向该终端发送RRC连接恢复响应，终端在接收到该RRC连接恢复响应后，可以根据该RRC连接恢复响应进行相应的配置，在配置完成后，向第一基站发送RRC连接恢复完成请求，以通知第一基站完成RRC连接的重建过程。
可选的，本发明实施例中的上下文释放请求可以为新的信令，也可以复用传统的信令，当该上下文释放请求复用传统信令时，一方面，请参考图2-2，上下文释放请求可以与RRC连接建立过程中的信令进行复用，例如，该上下文释放请求可以为携带有释放指示(英文：release indication)的RRC连接建立请求；或者，上下文释放请求为携带有释放指示的RRC连接建立完成消息；另一方面，上下文释放请求可以与RRC连接重建过程中的信令进行复用，例如，该上下文释放请求可以为携带有释放指示的RRC连接恢复请求；或者，该上下文释放请求为携带有释放指示的RRC连接恢复完成请求。
其中，该释放指示用于指示网络侧进行终端的相关上下文的释放。该释放 指示的形式可以符合目前的RRC协议，携带该释放指示的消息可以用来实现终端触发网络侧的相关上下文的释放。
步骤203、第一基站根据上下文释放请求，向核心管理设备发送上下文释放授权请求。
在本发明实施例中，第一基站可以向核心管理设备发送上下文释放授权请求，以请求核心管理设备授权进行网络侧设备的上下文的释放。可选的，该上下文释放授权请求也可以携带上述释放指示。
步骤204、核心管理设备根据上下文释放授权请求，生成上下文释放授权响应。
核心管理设备根据上下文释放授权请求，可以判断是否允许网络侧设备释放相关上下文。示例的，核心管理设备可以预测预设时间段内终端是否存在数据传输，若预测得到在该预设时间段内终端存在数据传输，则不允许网络侧设备释放相关上下文，这样可以避免终端与网络侧断开连接后再重建连接所造成的网络资源浪费；若预测得到在该预设时间段内终端不存在数据传输，则允许网络侧设备释放相关上下文，这样可以减少网络侧设备的负载。
例如，核心管理设备在接收到上下文释放授权请求时进行倒计时，该倒计时的时长等于上述预设时间段的时长，核心网若在倒计时结束前接收到针对终端的数据传输请求，则预测该预设时间段内终端存在数据传输。
在本发明实施例中，假设核心管理设备根据上下文释放授权请求，确定允许网络侧设备释放相关上下文，则核心管理设备可以生成上下文释放授权响应。该上下文释放授权响应用于指示允许网络侧设备进行相关上下文的释放。
步骤205、核心管理设备向第一基站发送上下文释放授权响应。
核心管理设备与第一基站进行数据传输的过程可以参考相关协议，本发明实施例对此不作限定。
步骤206、第一基站根据上下文释放授权响应，向网络侧设备发送上下文释放指示信息。
由于核心管理设备允许网络侧设备进行上下文释放，则第一基站可以根据上下文释放授权响应，该上下文释放指示信息用于指示网络侧设备进行相关上下文的释放。第一基站向网络侧设备发送上下文释放指示信息，以触发网络侧设备进行相关上下文的释放。
步骤207、网络侧设备根据上下文释放指示信息，进行相关上下文的释放。
相关上下文的释放过程实质上是网络侧设备删除相关上下文的过程，具体可以参考相关协议中内容，本发明实施例对此不作赘述。
步骤208、网络侧设备向第一基站发送上下文释放完成信息。
网络侧设备完成相关上下文释放后，可以向第一基站发送上下文释放完成信息，以通知第一基站。该上下文释放完成信息用于指示网络侧设备已完成相关上下文的释放。
步骤209、第一基站根据上下文释放完成信息，向终端发送上下文释放响应。
第一基站接收到上下文释放完成信息后，可以向终端发送上下文释放响应，以通知终端：网络侧设备已完成相关上下文的释放，其中，上下文释放完成信息和上下文释放响应中的内容可以相同，也可以不同。
步骤210、终端根据上下文释放响应，释放终端中的相关上下文。
在本发明实施例中，终端可以根据上下文释放响应，释放自身的相关上下文，以减少自身的负载，但实际应用中，终端也可以不进行自身的相关上下文释放，本发明实施例对此不作限定。
需要说明的是，上述实施例提供的上下文释放方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本发明的保护范围之内，因此不再赘述。
第二方面，网络侧设备可以间接由核心管理设备触发网络侧设备释放相关上下文，如图3-1所示，具体包括：
步骤301、终端确定终端需要从非激活状态转换至空闲状态。
步骤301的具体过程可以参考步骤201，本发明实施例对此不作赘述。
步骤302、终端向第一基站发送上下文释放请求。
上述上下文释放请求用于指示网络侧进行终端的相关上下文的释放。步骤302中的其他内容可以参考步骤202，本发明实施例对此不作赘述。
步骤303、第一基站根据上下文释放请求，向核心管理设备发送上下文释放授权请求。
上述上下文释放授权请求用于请求授权网络侧设备进行相关上下文的释放。步骤303中的其他内容可以参考步骤203，本发明实施例对此不作赘述。
步骤304、核心管理设备根据上下文释放授权请求，触发保存有相关上下 文的网络侧设备释放相关上下文。
可选的，请参考图3-2，核心管理设备根据上下文释放授权请求，触发保存有相关上下文的网络侧设备释放相关上下文的过程可以包括：
步骤3041、核心管理设备根据上下文释放授权请求，向网络侧设备发送上下文释放指示信息，该上下文释放指示信息用于指示网络侧设备进行相关上下文的释放。
核心管理设备根据上下文释放授权请求，可以判断是否允许网络侧设备释放相关上下文。示例的，核心管理设备可以预测预设时间段内终端是否存在数据传输，若预测得到在该预设时间段内终端存在数据传输，则不允许网络侧设备释放相关上下文，这样可以避免终端与网络侧断开连接后再重建连接所造成的网络资源浪费；若预测得到在该预设时间段内终端不存在数据传输，则允许网络侧设备释放相关上下文，这样可以减少网络侧设备的负载。
例如，核心管理设备在接收到上下文释放授权请求时进行倒计时，该倒计时的时长等于上述预设时间段的时长，核心网若在倒计时结束前接收到针对终端的数据传输请求，则预测该预设时间段内终端存在数据传输。
在本发明实施例中，假设核心管理设备根据上下文释放授权请求，确定允许网络侧设备释放相关上下文，则核心管理设备可以向网络侧设备发送上下文释放指示信息，以触发网络侧设备释放相关上下文。
步骤3042、网络侧设备根据上下文释放指示信息，进行相关上下文的释放。
步骤3042可以参考上述步骤207，本发明实施例对此不作赘述。
步骤305、核心管理设备向第一基站发送上下文释放完成信息。
上述上下文释放完成信息用于指示网络侧设备已完成相关上下文的释放。
可选的，请参考图3-3，核心管理设备向第一基站发送上下文释放完成信息的过程可以包括：
步骤3051、网络侧设备向核心管理设备发送上下文释放完成信息，上下文释放完成信息用于指示网络侧设备已完成相关上下文的释放。
网络侧设备完成相关上下文释放后，可以向核心管理设备发送上下文释放完成信息，以通知核心管理设备。
步骤3052、核心管理设备根据上下文释放完成信息，向第一基站发送上下文释放完成信息。
核心管理设备接收到上下文释放完成信息可以向第一基站发送上下文释 放完成信息，以通知第一基站：网络侧设备已完成相关上下文的释放。
需要说明的是，网络侧送设备发送的上下文释放完成信息和核心管理设备发送的上下文释放完成信息可以相同，也可以不同。
步骤306、第一基站根据上下文释放完成信息，向终端发送上下文释放响应。
步骤306可以参考上述步骤209，本发明实施例对此不作赘述。
步骤307、终端根据上下文释放响应，释放终端中的相关上下文。
步骤307可以参考上述步骤210，本发明实施例对此不作赘述。
需要说明的是，上述实施例提供的上下文释放方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本发明的保护范围之内，因此不再赘述。
第三方面，第一基站可以直接触发网络侧设备释放相关上下文，如图4所示，具体包括：
步骤401、终端确定终端需要从非激活状态转换至空闲状态。
步骤401的具体过程可以参考步骤201，本发明实施例对此不作赘述。
步骤402、终端向第一基站发送上下文释放请求。
上述上下文释放请求用于指示网络侧进行终端的相关上下文的释放。步骤402中的其他内容可以参考步骤202，本发明实施例对此不作赘述。
步骤403、第一基站根据上下文释放请求，向网络侧设备发送上下文释放指示信息。
第一基站可以根据上下文释放请求，向网络侧设备发送上下文释放指示信息，以触发网络侧设备进行相关上下文的释放。该上下文释放指示信息用于指示网络侧设备进行相关上下文的释放。
步骤404、网络侧设备根据上下文释放指示信息，进行相关上下文的释放。
步骤404可以参考步骤207，本发明实施例对此不作赘述。
步骤405、网络侧设备向第一基站发送上下文释放完成信息。
该上下文释放完成信息用于指示网络侧设备已完成相关上下文的释放。步骤405中的其他内容可以参考上述步骤208，本发明实施例对此不作赘述。
步骤406、第一基站根据上下文释放完成信息，向终端发送上下文释放响应。
步骤406可以参考上述步骤209，本发明实施例对此不作赘述。
步骤407、终端根据上下文释放响应，释放终端中的相关上下文。
步骤407可以参考上述步骤210，本发明实施例对此不作赘述。
需要说明的是，上述实施例提供的上下文释放方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本发明的保护范围之内，因此不再赘述。
相关技术中，还提出了可以通过在网络侧发送的寻呼消息中直接加入释放指示，使终端直接释放相关上下文，进入空闲状态。而本发明实施例中提供了一种终端触发网络侧释放相关上下文的新的方式，增加了相关上下文释放的灵活性。
综上所述，本发明实施例提供的上下文释放方法，通过终端触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
本发明实施例提供一种上下文释放设备50，如图5-1所示，包括：
发送模块501，用于向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
综上所述，本发明实施例提供的上下文释放设备，通过发送模块触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
进一步的，如图5-2所示，所述设备50还包括：
接收模块502，用于接收所述第一基站发送的上下文释放响应。
可选的，如图5-3所示，所述设备50还包括：
确定模块503，用于通过应用层或非接入子层确定所述终端需要从非激活状态转换至空闲状态。
其中，所述发送模块501，具体用于：
通过接入子层向第一基站发送所述上下文释放请求。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连 接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
综上所述，本发明实施例提供的上下文释放设备，通过发送模块触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
本发明实施例提供一种上下文释放设备60，如图6-1，包括：
接收模块601，用于接收终端发送的上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
综上所述，本发明实施例提供的上下文释放设备，通过终端触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
进一步的，如图6-2所示，所述设备60还包括：
触发模块602，用于根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
发送模块603，用于向所述终端发送上下文释放响应，所述上下文释放响应用于触发所述终端释放所述相关上下文。
一方面，触发模块602，具体用于：
根据所述上下文释放请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
发送模块603，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
另一方面，触发模块602，具体用于：
根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的 释放；
发送模块603，具体用于：
接收所述核心管理设备发送的上下文释放完成信息，所述上下文释放完成信息为所述核心管理设备在触发所述网络侧设备释放所述相关上下文后发送的，用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
又一方面，触发模块602，具体用于：
根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
接收所述核心管理设备发送的上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
根据所述上下文释放授权响应，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
发送模块603，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
可选的，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
可选的，所述上下文释放请求是接入所述第一基站的终端在确定所述终端需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
本发明实施例提供一种上下文释放设备70，如图7-1所示，所述设备70包括：
接收模块701，用于接收第一基站发送的上下文释放授权请求，所述上下文释放授权请求是所述第一基站在接收终端发送的上下文释放请求后发送的，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
综上所述，本发明实施例提供的上下文释放设备，通过终端触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
一方面，如图7-2所示，所述设备还包括：
触发模块702，用于根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
发送模块703，用于在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放。
其中，所述触发模块702，具体用于：
根据所述上下文释放授权请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
所述发送模块703，具体用于：
接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
根据所述上下文释放完成信息，向所述第一基站发送上下文释放完成信息。
另一方面，如图7-3所示，所述设备70还包括：
生成模块704，用于根据所述上下文释放授权请求，生成上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
发送模块705，用于向所述第一基站发送所述上下文释放授权响应。
可选的，所述上下文释放请求是所述第一基站管理的小区中的终端确定需要从非激活状态转换至空闲状态后发送的。
可选的，所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
本发明实施例提供一种上下文释放系统，包括：终端和第一基站，
该终端可以包括上述图5-1至5-3任一所述的上下文释放设备；
所述第一基站可以包括图6-1至6-2任一所述的上下文释放设备。
进一步的，该系统还包括：图7-1至7-3任一所述的上下文释放设备。
综上所述，本发明实施例提供的上下文释放系统，通过终端触发网络侧进行相关上下文的释放，在上下文释放过程，尤其在非激活状态下的上下文释放过程中，无需先转换至连接状态，再转换至空闲状态，有效减少了终端与网络侧信令交互，减少了信令开销，简化了整体流程。
请参考图8，其示出了本发明示例性实施例涉及的一种上下文释放设备10的结构示意图。该上下文释放设备10可以是上述第一基站110、网络侧设备120、核心管理设备130或终端140，该网络设备10包括：处理器12和网络接口14。
处理器12包括一个或者一个以上处理核心。处理器12通过运行软件程序以及模块，从而执行各种功能应用以及数据处理。
网络接口14可以为多个，该网络接口14用于与其它存储设备或者网络设备进行通信。
可选的，网络设备10还包括存储器16、总线18等部件。其中，存储器16与网络接口14分别通过总线18与处理器12相连。
存储器16可用于存储软件程序以及模块。具体的，存储器16可存储操作系统162、至少一个功能所需的应用程序模块164。操作系统162可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
在一些实施方式中，当上下文释放设备10为第一基站时，网络接口14可以为收发天线(也可以视为发射机和接收机)，存储器16存储的应用程序模块164可以执行上述步骤203、步骤206、步骤209、步骤303、步骤306、步骤403或步骤406等步骤；
当上下文释放设备10为终端时，网络接口14可以为收发天线(也可以视为发射机和接收机)，存储器16存储的应用程序模块164可以执行上述步骤201、步骤202、步骤210、步骤301、步骤302、步骤307、步骤401、步骤402或步骤407等步骤；
当上下文释放设备10为核心管理设备时，存储器16存储的应用程序模块164可以执行上述步骤204、步骤202、步骤210、步骤304、步骤305等步骤。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，设备和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本发明实施例中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (40)

  1. 一种上下文释放方法，其特征在于，包括：
    终端向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  2. 根据权利要求1所述的方法，其特征在于，所述终端向第一基站发送上下文释放请求之后，所述方法还包括：
    所述终端接收所述第一基站发送的上下文释放响应。
  3. 根据权利要求1所述的方法，其特征在于，在所述终端向第一基站发送上下文释放请求之前，所述方法还包括：
    所述终端的应用层或非接入子层确定所述终端需要从非激活状态转换至空闲状态。
  4. 根据权利要求1所述的方法，其特征在于，
    所述终端向第一基站发送上下文释放请求，包括：
    所述终端通过接入子层向第一基站发送所述上下文释放请求。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
    其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
  6. 一种上下文释放方法，其特征在于，包括：
    第一基站接收终端发送的上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  7. 根据权利要求6所述的方法，其特征在于，在所述第一基站接收终端发送的上下文释放请求之后，所述方法还包括：
    所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
    所述第一基站向所述终端发送上下文释放响应，所述上下文释放响应用于触发所述终端释放所述相关上下文。
  8. 根据权利要求7所述的方法，其特征在于，
    所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
    所述第一基站根据所述上下文释放请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    所述第一基站向所述终端发送上下文释放响应，包括：
    所述第一基站接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  9. 根据权利要求7所述的方法，其特征在于，
    所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
    所述第一基站根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
    所述第一基站向所述终端发送上下文释放响应，包括：
    所述第一基站接收所述核心管理设备发送的上下文释放完成信息，所述上下文释放完成信息为所述核心管理设备在触发所述网络侧设备释放所述相关上下文后发送的，用于指示所述网络侧设备已完成所述相关上下文的释放；
    所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  10. 根据权利要求7所述的方法，其特征在于，
    所述第一基站根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
    所述第一基站根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
    所述第一基站接收所述核心管理设备发送的上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
    所述第一基站根据所述上下文释放授权响应，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    所述第一基站向所述终端发送上下文释放响应，包括：
    所述第一基站接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    所述第一基站根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  11. 根据权利要求6至10任一所述的方法，其特征在于，
    所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
    其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
  12. 根据权利要求6至10任一所述的方法，其特征在于，
    所述上下文释放请求是接入所述第一基站的终端在确定所述终端需要从非激活状态转换至空闲状态后发送的。
  13. 根据权利要求7至10任一所述的方法，其特征在于，
    所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧 中心控制节点；
    所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
  14. 一种上下文释放方法，其特征在于，所述方法包括：
    核心管理设备接收第一基站发送的上下文释放授权请求，所述上下文释放授权请求是所述第一基站在接收终端发送的上下文释放请求后发送的，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  15. 根据权利要求14所述的方法，其特征在于，
    所述核心管理设备接收第一基站发送的上下文释放授权请求之后，所述方法还包括：
    所述核心管理设备根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
    所述核心管理设备在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放。
  16. 根据权利要求15所述的方法，其特征在于，所述核心管理设备根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文，包括：
    所述核心管理设备根据所述上下文释放授权请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    所述核心管理设备在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，包括：
    所述核心管理设备接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    所述核心管理设备根据所述上下文释放完成信息，向所述第一基站发送上下文释放完成信息。
  17. 根据权利要求14所述的方法，其特征在于，
    所述核心管理设备接收第一基站发送的上下文释放授权请求之后，所述方法还包括：
    所述核心管理设备根据所述上下文释放授权请求，生成上下文释放授权响应，所述上下文释放授权响应用于指示允许保存有所述相关上下文的网络侧设备进行所述相关上下文的释放；
    所述核心管理设备向所述第一基站发送所述上下文释放授权响应。
  18. 根据权利要求14至17任一所述的方法，其特征在于，
    所述上下文释放请求是所述第一基站管理的小区中的终端确定需要从非激活状态转换至空闲状态后发送的。
  19. 根据权利要求15至17任一所述的方法，其特征在于，
    所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
    所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
  20. 一种上下文释放设备，其特征在于，包括：
    发送模块，用于向第一基站发送上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  21. 根据权利要求20所述的设备，其特征在于，所述设备还包括：
    接收模块，用于接收所述第一基站发送的上下文释放响应。
  22. 根据权利要求20所述的设备，其特征在于，所述设备还包括：
    确定模块，用于通过应用层或非接入子层确定所述终端需要从非激活状态转换至空闲状态。
  23. 根据权利要求20所述的设备，其特征在于，
    所述发送模块，具体用于：
    通过接入子层向第一基站发送所述上下文释放请求。
  24. 根据权利要求20至23任一所述的设备，其特征在于，所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
    其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
  25. 一种上下文释放设备，其特征在于，包括：
    接收模块，用于接收终端发送的上下文释放请求，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  26. 根据权利要求25所述的设备，其特征在于，所述设备还包括：
    触发模块，用于根据所述上下文释放请求触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
    发送模块，用于向所述终端发送上下文释放响应，所述上下文释放响应用于触发所述终端释放所述相关上下文。
  27. 根据权利要求26所述的设备，其特征在于，
    触发模块，具体用于：
    根据所述上下文释放请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    发送模块，具体用于：
    接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  28. 根据权利要求26所述的设备，其特征在于，
    触发模块，具体用于：
    根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释 放；
    发送模块，具体用于：
    接收所述核心管理设备发送的上下文释放完成信息，所述上下文释放完成信息为所述核心管理设备在触发所述网络侧设备释放所述相关上下文后发送的，用于指示所述网络侧设备已完成所述相关上下文的释放；
    根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  29. 根据权利要求26所述的设备，其特征在于，
    触发模块，具体用于：
    根据所述上下文释放请求，向核心管理设备发送上下文释放授权请求，所述上下文释放授权请求用于请求授权所述网络侧设备进行所述相关上下文的释放；
    接收所述核心管理设备发送的上下文释放授权响应，所述上下文释放授权响应用于指示允许所述网络侧设备进行所述相关上下文的释放；
    根据所述上下文释放授权响应，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    发送模块，具体用于：
    接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    根据所述上下文释放完成信息，向所述终端发送上下文释放响应。
  30. 根据权利要求25至29任一所述的设备，其特征在于，
    所述上下文释放请求为携带有释放指示的无线资源控制RRC连接建立请求；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复请求；或者，所述上下文释放请求为携带有释放指示的RRC连接建立完成消息；或者，所述上下文释放请求为携带有释放指示的RRC连接恢复完成请求；
    其中，所述释放指示用于指示网络侧进行所述终端的相关上下文的释放。
  31. 根据权利要求25至29任一所述的设备，其特征在于，
    所述上下文释放请求是接入所述第一基站的终端在确定所述终端需要从非 激活状态转换至空闲状态后发送的。
  32. 根据权利要求26至29任一所述的设备，其特征在于，
    所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
    所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
  33. 一种上下文释放设备，其特征在于，所述设备包括：
    接收模块，用于接收第一基站发送的上下文释放授权请求，所述上下文释放授权请求是所述第一基站在接收终端发送的上下文释放请求后发送的，所述上下文释放请求用于指示网络侧进行所述终端的相关上下文的释放。
  34. 根据权利要求33所述的设备，其特征在于，所述设备还包括：
    触发模块，用于根据所述上下文释放授权请求，触发保存有所述相关上下文的网络侧设备释放所述相关上下文；
    发送模块，用于在所述网络侧设备释放所述相关上下文后，向所述第一基站发送上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放。
  35. 根据权利要求34所述的设备，其特征在于，所述触发模块，具体用于：
    根据所述上下文释放授权请求，向所述网络侧设备发送上下文释放指示信息，所述上下文释放指示信息用于指示所述网络侧设备进行所述相关上下文的释放；
    所述发送模块，具体用于：
    接收所述网络侧设备发送的上下文释放完成信息，所述上下文释放完成信息用于指示所述网络侧设备已完成所述相关上下文的释放；
    根据所述上下文释放完成信息，向所述第一基站发送上下文释放完成信息。
  36. 根据权利要求33所述的设备，其特征在于，所述设备还包括：
    生成模块，用于根据所述上下文释放授权请求，生成上下文释放授权响应，所述上下文释放授权响应用于指示允许保存有所述相关上下文的网络侧设备进 行所述相关上下文的释放；
    发送模块，用于向所述第一基站发送所述上下文释放授权响应。
  37. 根据权利要求33至36任一所述的设备，其特征在于，
    所述上下文释放请求是所述第一基站管理的小区中的终端确定需要从非激活状态转换至空闲状态后发送的。
  38. 根据权利要求34至36任一所述的设备，其特征在于，
    所述网络侧设备包括初始基站，和/或，核心网的管理设备，和/或，网络侧中心控制节点；
    所述初始基站为所述终端转换至非激活状态之前所在小区所属的基站。
  39. 一种上下文释放系统，其特征在于，包括：终端和第一基站，
    所述终端包括权利要求20至24任一所述的上下文释放设备；
    所述第一基站包括权利要求25至32任一所述的上下文释放设备。
  40. 根据权利要求39所述的系统，其特征在于，所述系统还包括：33至38任一所述的上下文释放设备。
PCT/CN2016/112970 2016-12-29 2016-12-29 上下文释放方法、设备及系统 WO2018119853A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
PCT/CN2016/112970 WO2018119853A1 (zh) 2016-12-29 2016-12-29 上下文释放方法、设备及系统
CN201680091704.1A CN110089193B (zh) 2016-12-29 2016-12-29 上下文释放方法、设备及系统
JP2019535392A JP7013474B2 (ja) 2016-12-29 2016-12-29 コンテキスト解放方法、機器及びシステム
US16/474,014 US20200128608A1 (en) 2016-12-29 2016-12-29 Context release method, device and system
KR1020197021642A KR20190100307A (ko) 2016-12-29 2016-12-29 컨텍스트 릴리즈 방법, 기기 및 시스템
EP16925850.6A EP3562259B1 (en) 2016-12-29 2016-12-29 Context release method and devices
TW106142300A TW201824936A (zh) 2016-12-29 2017-12-01 上下文釋放方法、設備及系統

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/112970 WO2018119853A1 (zh) 2016-12-29 2016-12-29 上下文释放方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2018119853A1 true WO2018119853A1 (zh) 2018-07-05

Family

ID=62710186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/112970 WO2018119853A1 (zh) 2016-12-29 2016-12-29 上下文释放方法、设备及系统

Country Status (7)

Country Link
US (1) US20200128608A1 (zh)
EP (1) EP3562259B1 (zh)
JP (1) JP7013474B2 (zh)
KR (1) KR20190100307A (zh)
CN (1) CN110089193B (zh)
TW (1) TW201824936A (zh)
WO (1) WO2018119853A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111526550B (zh) * 2018-02-14 2022-01-25 Oppo广东移动通信有限公司 通信方法、网络设备和终端设备
WO2021229136A1 (en) 2020-05-13 2021-11-18 Nokia Technologies Oy Prolonging voice service in an active state
CN113438646B (zh) * 2021-06-30 2022-08-23 展讯通信（上海）有限公司 业务建立方法、装置、终端及网络侧设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067937A (zh) * 2012-12-04 2013-04-24 大唐移动通信设备有限公司 状态信息处理方法与系统
EP2852244A1 (en) * 2012-05-14 2015-03-25 NTT DOCOMO, Inc. Mobile communication method, wireless base station, and mobile management node
CN104812070A (zh) * 2014-01-29 2015-07-29 北京三星通信技术研究有限公司 一种ue资源维护和释放的方法和设备
US9131424B2 (en) * 2011-03-25 2015-09-08 Lg Electronics Inc. Method and apparatus for releasing user equipment context in wireless communication system

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100499921C (zh) * 2007-01-19 2009-06-10 重庆重邮信科通信技术有限公司 一种缩短用户终端从连接模式返回空闲模式时延的方法
CN101500322B (zh) * 2008-02-02 2012-04-04 中兴通讯股份有限公司 资源释放方法
CN101572943B (zh) * 2008-04-28 2011-07-20 电信科学技术研究院 Mme释放isr情况下空闲态ue上下文的方法、装置及系统
WO2010088794A1 (zh) * 2009-02-03 2010-08-12 华为技术有限公司 处理演进网络中上下文的方法和系统
EP2978253B1 (en) * 2013-03-20 2020-09-30 LG Electronics Inc. Method and apparatus for providing proximity service
WO2015085273A1 (en) * 2013-12-06 2015-06-11 Interdigital Patent Holdings, Inc. Layered connectivity in wireless systems

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9131424B2 (en) * 2011-03-25 2015-09-08 Lg Electronics Inc. Method and apparatus for releasing user equipment context in wireless communication system
EP2852244A1 (en) * 2012-05-14 2015-03-25 NTT DOCOMO, Inc. Mobile communication method, wireless base station, and mobile management node
CN103067937A (zh) * 2012-12-04 2013-04-24 大唐移动通信设备有限公司 状态信息处理方法与系统
CN104812070A (zh) * 2014-01-29 2015-07-29 北京三星通信技术研究有限公司 一种ue资源维护和释放的方法和设备

Also Published As

Publication number Publication date
CN110089193A (zh) 2019-08-02
EP3562259B1 (en) 2021-11-10
US20200128608A1 (en) 2020-04-23
TW201824936A (zh) 2018-07-01
JP2020504956A (ja) 2020-02-13
EP3562259A4 (en) 2019-12-11
EP3562259A1 (en) 2019-10-30
JP7013474B2 (ja) 2022-02-15
CN110089193B (zh) 2023-11-10
KR20190100307A (ko) 2019-08-28

Similar Documents

Publication Publication Date Title
US12075277B2 (en) Method of processing network slice based congestion, device and system thereof
WO2021057389A1 (zh) 一种双连接管理方法和通信装置
US20200187144A1 (en) Communication method, apparatus, and system
US9681339B2 (en) Security processing method and system in network handover process
US11212864B2 (en) Method and device for processing non-matching between UE and network state
WO2018126535A1 (zh) 一种会话管理方法及装置
WO2018019001A1 (zh) 一种终端状态转换方法及装置
WO2020135850A1 (zh) 通信方法和装置
US10972999B2 (en) Method for determining paging area, access network node and core network node
US20220287135A1 (en) Efficient use of physical and logical resources in dual connectivity
EP3799514A1 (en) RATE CONTROL METHOD, DEVICE AND SYSTEM

WO2017133295A1 (zh) 数据传输方法、装置和系统
WO2018119853A1 (zh) 上下文释放方法、设备及系统
TW201838438A (zh) 一種消息傳輸控制方法及裝置
CN108377522A (zh) 一种信息前转方法及基站
EP3720163A1 (en) Method and device for determining security algorithm, and computer storage medium
WO2024027638A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
WO2024199148A1 (zh) 一种通信方法及装置
CN114071604B (zh) 数据传输方法、设备、装置及存储介质
WO2023151587A1 (zh) 目标面数据传输方法、终端及网络侧设备
WO2023185794A1 (zh) 通信处理方法、终端及网络侧设备
WO2019028920A1 (zh) 一种数据传输方法及设备
US20220287002A1 (en) Network-triggered paging for multi-radio dual connectivity
CN118829012A (zh) 一种通信方法及通信系统
WO2019033945A1 (zh) 一种ue和网络状态不匹配的处理方法及装置

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: 16925850

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019535392

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197021642

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016925850

Country of ref document: EP

Effective date: 20190724