WO2017118397A1 - Ue上下文管理方法和设备 - Google Patents

Ue上下文管理方法和设备 Download PDF

Info

Publication number
WO2017118397A1
WO2017118397A1 PCT/CN2017/070266 CN2017070266W WO2017118397A1 WO 2017118397 A1 WO2017118397 A1 WO 2017118397A1 CN 2017070266 W CN2017070266 W CN 2017070266W WO 2017118397 A1 WO2017118397 A1 WO 2017118397A1
Authority
WO
WIPO (PCT)
Prior art keywords
context
rrc connection
timer
rrc
context management
Prior art date
Application number
PCT/CN2017/070266
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 EP17735835.5A priority Critical patent/EP3402300A4/en
Priority to US16/068,295 priority patent/US20190014614A1/en
Publication of WO2017118397A1 publication Critical patent/WO2017118397A1/zh

Links

Images

Classifications

    • 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
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers

Definitions

  • the present invention relates to the field of wireless communication technologies. More specifically, the present invention relates to a UE context management method and apparatus.
  • NB-IoT NarrowBand-Internet of Things
  • 3GPP has introduced a solution called user plane solution, which is briefly described as follows:
  • Radio Resource control RRC
  • DRB Data Radio Bearer
  • the UE and the evolved NodeB (eNB) release the RRC connection after the data transmission is completed, delete the UE context and enter the RRC idle state;
  • the UE and the eNB suspend the RRC connection and save the UE context.
  • the eNB informs the UE to suspend the RRC connection and save the UE context through RRC signaling.
  • the UE when the UE has uplink data transmission or downlink data reception, the UE initiates an RRC connection recovery procedure to the eNB. Because the UE and the eNB save the UE context, the RRC connection can be restored through the process. Data transmission without the need to establish DRB through the RRC reconfiguration process, and without security Establish a process for the establishment of air interface security. It can be seen that in this way, the signaling overhead of the air interface is saved.
  • the user plane solution reduces the control signaling overhead during data transmission by introducing an RRC connection suspension/recovery procedure, which means that after the RRC connection of the UE is suspended, both the UE and the eNB need to save the The context of the UE until the next uplink data or downlink data transmission occurs in order to successfully perform the RRC connection recovery procedure.
  • the UE context needs to be saved on both the eNB and the UE, and in some scenarios, there is a limitation in saving the UE context without limitation, and the mechanism cannot cover this.
  • a problem This has become a problem of concern and problem to be solved by the present invention.
  • the method of the present invention is not limited to the NB-IoT system of Release 13 described in the background art, and is also applicable to other non-NB-IoT devices and systems, such as Machine Type Communication (MTC) scenarios.
  • MTC Machine Type Communication
  • a UE context management method performed at a user equipment UE, comprising: receiving, when the UE or UE radio resource control RRC layer, an RRC connection suspension from an evolved node eNB When the message or the UE initiates an RRC connection suspension procedure, the UE or the UE RRC layer initiates a UE context management timer, and the RRC connection suspension message or the RRC connection suspension procedure is used to suspend the RRC connection at the UE. And saving the UE context; and releasing the saved UE context by the UE or UE RRC layer if the UE context management timer expires.
  • the method further includes: if the UE or UE RRC layer initiates an RRC connection recovery procedure or an RRC connection setup procedure when the UE context management timer is running, stopping by the UE or UE RRC layer The UE context management timer.
  • the UE or the UE RRC layer initiates an RRC connection recovery procedure, the UE context is still saved; if the UE or the UE RRC layer initiates an RRC connection setup procedure, releasing the saved UE Context.
  • the method further includes: if the paging message is received when the UE context management timer is running, stopping, by the UE or the UE RRC layer, the UE context management timer, and still saving the UE context.
  • the UE context is a UE access layer AS context.
  • the UE is a narrowband Internet of Things NB-IoT UE or a non-NB-IoT UE.
  • the value of the timer is preset to a fixed value.
  • the value of the timer is configured by the eNB via RRC signaling or by the mobility management entity MME via non-access stratum NAS signaling.
  • a user equipment UE for performing UE context management.
  • the UE includes: a timer management unit configured to: when the UE receives a radio resource control RRC connection suspension message from the evolved node eNB or the UE initiates an RRC connection suspension procedure, by the UE or the UE
  • the RRC layer starts a UE context management timer; and the UE context management unit is configured to: when the UE receives a radio resource control RRC connection suspension message from the evolved node eNB or the UE initiates an RRC connection suspension process, The UE suspends the RRC connection and saves the UE context; and if the UE context management timer expires, releases the saved UE context.
  • the timer management unit may be further configured to: if the UE or the UE RRC layer initiates an RRC connection recovery process or an RRC connection establishment procedure when the UE context management timer is running, stop the UE context management timer.
  • the UE context management unit may be further configured to: if the UE or UE RRC layer initiates an RRC connection recovery procedure when the UE context management timer is running, still save the UE context; When the UE or UE RRC layer initiates an RRC connection setup procedure while the UE context management timer is running, the saved UE context is released.
  • the timer management unit is further configured to stop the UE context management timer if a paging message is received when the UE context management timer is running.
  • FIG. 1 is a schematic diagram of an RRC connection suspension
  • FIG. 2 is a schematic diagram of an RRC connection recovery process
  • FIG. 3 is a flow diagram of a UE context management method performed at a UE in accordance with the present invention.
  • FIG. 4 is a schematic flowchart of UE side processing according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic flowchart of UE side processing according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic flowchart of UE side processing according to Embodiment 3 of the present invention.
  • 7-9 are schematic flowcharts of UE side processing according to Embodiment 4 of the present invention.
  • FIG. 10 is a schematic flowchart of a UE side configuration according to Embodiment 5 of the present invention.
  • FIG. 11 is a schematic flowchart of a network side configuration according to Embodiment 5 of the present invention.
  • FIG. 12 is a schematic diagram of a network side interaction process according to Embodiment 5 of the present invention.
  • FIG. 13 is a schematic diagram of a configuration of a UE according to Embodiment 6 of the present invention.
  • the LTE mobile communication system and its subsequent evolved versions are taken as an example application environment, and NB-IoT is used as an implementation technical scenario, and various embodiments according to the present invention are specifically described.
  • the present invention is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as future 5G cellular communication systems.
  • FIG. 3 is a flow chart showing a UE context management method 300 performed at a UE in accordance with the present invention.
  • the method includes the step 301, wherein when the UE or the UE radio resource control RRC layer receives an RRC connection suspension message from the evolved node eNB or the UE initiates an RRC connection suspension process, The UE or UE RRC layer initiates a UE context management timer.
  • the RRC Connection Suspend message or RRC Connection Suspend procedure is used to suspend an RRC connection at the UE and save the UE context.
  • the method also includes step 302, wherein the saved UE context is released by the UE or UE RRC layer if the UE context management timer expires.
  • the UE context can be effectively managed by setting a timer and releasing the saved UE context when the timer expires.
  • FIG. 4 is a flowchart of processing on the UE side in Embodiment 1 of the present invention. This embodiment provides a method for the UE side to manage the saved UE context according to the UE context management timer.
  • Step 401 The UE or the UE RRC layer receives an RRC connection suspension message or initiates an RRC connection suspension procedure.
  • the RRC connection suspension message is used to indicate that the UE suspends the RRC connection and saves the UE context, which is referred to as an RRC connection suspension message in the present invention; the RRC connection suspension procedure is used to suspend the RRC connection and save the UE context,
  • the invention is referred to as an RRC Connection Suspend Flow, the implementation of which is shown, for example, in the Background section.
  • Step 402 The UE or the UE RRC layer starts a UE context management timer.
  • the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • the value of the timer may be a fixed value, such as a fixed value in a predefined manner or a default manner, or may be a value configured by the network side, as described in Embodiment 5.
  • the UE context in this embodiment may be a UE access layer (AS) context; the UE may be an NB-IoT UE, or may be other types of UEs other than NB-IoT.
  • AS UE access layer
  • FIG. 5 is a flowchart of processing on the UE side in Embodiment 2 of the present invention. This embodiment provides a method for the UE side to manage the saved UE context according to the UE context management timer.
  • Step 501 The UE or the UE RRC layer initiates an RRC process or receives a paging message.
  • the RRC procedure is used to restore the previously suspended RRC connection, which is referred to as an RRC connection recovery procedure in the present invention, and the implementation manner is as shown in the background section, for example, or the RRC procedure may be an RRC connection establishment procedure.
  • Step 502 If the UE context management timer is running, the UE or UE RRC layer stops the timer.
  • the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • the UE still saves the UE context; if the UE or the UE RRC layer starts The RRC connection establishment procedure is performed, and the UE deletes the UE context.
  • the value of the timer may be a fixed value, such as a fixed value in a predefined manner or a default manner, or may be a value configured by the network side, as described in Embodiment 5.
  • the UE context in this embodiment may be an Access stratum (AS) context; the UE may be an NB-IoT UE, or may be other types of UEs other than NB-IoT.
  • AS Access stratum
  • FIG. 6 is a flowchart of processing on the UE side according to an embodiment of the present invention. This embodiment provides a method for the UE side to manage the saved UE context according to the UE context management timer.
  • Step 601 The UE context management timer expires.
  • the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • Step 602 The UE or the UE RRC layer performs the following actions:
  • Behavior 1 Release the saved UE context.
  • Behavior 2 Notifies the upper layer of the timer timeout and/or the release of the UE context.
  • the behaviors 1 to 3 are optional, that is, the UE can perform one or more of the behaviors 1 to 3.
  • a typical behavior is that the UE performs the behavior 1 to 2, that is, the UE or the UE RRC layer releases the saved UE context and informs the upper layer.
  • the value of the timer may be a fixed value, such as a fixed value in a predefined manner or a default manner, or may be a value configured by the network side, as described in Embodiment 5.
  • the UE context in this embodiment may be a UE access layer (AS) context; the UE may be an NB-IoT UE, or may be other types of UEs other than NB-IoT.
  • AS UE access layer
  • FIG. 7 is a flowchart of processing on the UE side according to an embodiment of the present invention. This embodiment provides a method for the UE side to manage the saved UE context according to the UE context management timer.
  • Step 701 The UE or the UE RRC layer receives an RRC message or initiates an RRC process.
  • the RRC message is used to indicate that the UE suspends the RRC connection and saves the UE context
  • the RRC connection suspension message is used in the invention; the RRC procedure is used to suspend the RRC connection and save the UE context, which is referred to as an RRC connection suspension procedure in the present invention, and its implementation is shown, for example, in the background section.
  • Step 702 The UE or the UE RRC layer starts a UE context management timer.
  • the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • Step 703 Determine whether the UE or the UE RRC layer initiates an RRC procedure, or whether a paging message is received. If yes, step 704a is performed; otherwise, step 704b is performed.
  • the RRC procedure is used to restore the previously suspended RRC connection, which is referred to as an RRC connection recovery procedure in the present invention, and the implementation manner is as shown in the background section, for example, or the RRC procedure may be an RRC connection establishment procedure.
  • Step 704a The UE or the UE RRC layer stops the UE context management timer.
  • the UE still saves the UE context; if the UE or the UE RRC layer initiates the RRC connection establishment procedure, the UE deletes UE context.
  • Step 704b Determine whether the UE context management timer has timed out. If yes, go to step 705, otherwise go back to step 703.
  • Step 705 The UE or the UE RRC layer performs the following actions:
  • Behavior 1 Release the saved UE context.
  • Behavior 2 Notifies the upper layer of the timer timeout and/or the release of the UE context.
  • the behaviors 1 to 3 are optional, that is, the UE can perform one or more of the behaviors 1 to 3.
  • a typical behavior is that the UE performs the behavior 1 to 2, that is, the UE or the UE RRC layer releases the saved UE context and informs the upper layer.
  • the value of the timer may be a fixed value, such as a fixed value in a predefined manner or a default manner, or may be a value configured by the network side, as described in Embodiment 5.
  • the UE context in this embodiment may be an Access stratum (AS) context; the UE may be an NB-IoT UE, or may be other types of UEs other than NB-IoT.
  • AS Access stratum
  • FIG. 8 shows a case where the step of determining whether the UE or the UE RRC layer initiates an RRC procedure or whether a paging message is received is performed first, and then the step of determining whether the UE context management timer has timed out is performed.
  • FIG. 9 shows a case where it is judged whether the UE or the UE RRC layer starts an RRC procedure or whether a paging message is received and a step of determining whether the UE context management timer has timed out is performed in parallel.
  • FIG. 10 is a flowchart of configuring a UE side according to Embodiment 5 of the present invention.
  • Step 1001 The UE receives a configuration message, where the UE context management timer configuration information is used, where the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • the configuration information includes a value of the timer.
  • the timer is named as T CTX_REL
  • the configuration information including the value of T CTX_REL may be ⁇ ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000, min5, min10, min20, min30
  • hr1, hr2, hr 8, hr16, day1, day2, day4 ⁇ of course, the value is not limited to the above value.
  • the configuration message received by the UE may be an RRC message sent by the eNB.
  • One mode is a system information message that is sent in a broadcast manner, such as a second system information block (SIB2), and the other mode is dedicated to the UE.
  • the RRC message is an RRC connection reconfiguration message, an RRC connection suspension message, or the like; or may be a NAS message sent by an MME (Mobility Management Entity).
  • MME Mobility Management Entity
  • the UE context in this embodiment may be an Access stratum (AS) context; the UE may be an NB-IoT UE, or may be other types of UEs other than NB-IoT.
  • AS Access stratum
  • Step 1002 The UE applies the received UE context management timer configuration information, and manages the saved UE context according to the timer configuration information.
  • the specific implementation manners of the UE managing the saved UE context according to the timer are given in the embodiments 1 to 4, but are not limited thereto.
  • FIG. 11 is a flowchart of network side configuration in Embodiment 5 of the present invention.
  • Step 1101 The network side sends a configuration message, where the UE context management timer configuration information is used, where the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • the configuration information includes a value of the timer.
  • the timer is named T CTX_RE L
  • the configuration information includes the value of T CTX_REL may be ⁇ ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000, min5, min10, min20, One of min30, hr1, hr2, hr 8, hr16, day1, day2, day4 ⁇ , of course, its value is not limited to the above values.
  • the configuration message sent by the network side may be an RRC message sent by the eNB.
  • One mode is a system information message that is sent in a broadcast manner, such as SIB2, and the other mode is a UE-specific RRC message, such as an RRC connection reconfiguration message and an RRC connection. Suspend the message, etc.; it may also be a NAS message sent by the MME (Mobility Management Entity).
  • MME Mobility Management Entity
  • FIG. 12 is a flow chart of interaction on the network side in Embodiment 5 of the present invention.
  • Step 1201 The MME sends a configuration message, where the UE context management timer configuration information is used, and the timer is used for UE context management, or UE context release, and is referred to as a UE context management timer in the present invention.
  • the configuration information includes a value of the timer.
  • the timer is named as T CTX_REL
  • the configuration information including the value of T CTX_REL may be ⁇ ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000, min5, min10, min20, min30
  • hr1, hr2, hr 8, hr16, day1, day2, day4 ⁇ of course, the value is not limited to the above value.
  • the configuration message sent by the MME is an S1AP message, such as an initial context request message, or a bearer setup/modification/release message, or a UE context release message.
  • S1AP message such as an initial context request message, or a bearer setup/modification/release message, or a UE context release message.
  • Step 1202 The eNB receives the configuration information, and configures the information to the UE according to the information.
  • An example of the manner in which the eNB configures the UE is as shown in FIG.
  • FIG. 13 is a block diagram showing the structure of a UE 1300 according to Embodiment 5 of the present invention.
  • the UE 1300 includes a timer management unit 1310 and a UE context management unit 1320.
  • the timer management unit 1310 is configured to start the UE context by the UE or the UE RRC layer when the UE receives the radio resource control RRC connection suspension message from the evolved node eNB or the UE initiates an RRC connection suspension procedure. Manage timers.
  • the UE context management unit 1320 is configured to suspend an RRC connection and save the UE context at the UE when the UE receives a radio resource control RRC connection suspension message from the evolved node eNB or the UE initiates an RRC connection suspension procedure And releasing the saved UE context if the UE context management timer expires.
  • the timer management unit may be further configured to: if the UE or the UE RRC layer initiates an RRC connection recovery process or an RRC connection establishment procedure when the UE context management timer is running, stop the UE context management timer.
  • the UE context management unit may be further configured to: if the UE or UE RRC layer initiates an RRC connection recovery procedure when the UE context management timer is running, still save the UE context; When the UE or UE RRC layer initiates an RRC connection setup procedure while the UE context management timer is running, the saved UE context is released.
  • the timer management unit may be further configured to stop the UE context management timer if a paging message is received when the UE context management timer is running.
  • the above-described embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware.
  • the base station and various components within the user equipment in the above embodiments may be implemented by various devices including, but not limited to, analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, and programmable processing. , Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (CPLDs), and more.
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • CPLDs Programmable Logic Devices
  • base station refers to a mobile having a large transmission power and a relatively large coverage area.
  • Communication data and control switching center including resource allocation scheduling, data receiving and sending functions.
  • User equipment refers to a user mobile terminal, for example, a terminal device including a mobile phone, a notebook, etc., which can perform wireless communication with a base station or a micro base station.
  • embodiments of the invention disclosed herein may be implemented on a computer program product.
  • the computer program product is a product having a computer readable medium encoded with computer program logic that, when executed on a computing device, provides related operations to implement The above technical solution of the present invention.
  • the computer program logic When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention.
  • Such an arrangement of the present invention is typically provided as software, code and/or other data structures, or such as one or more, that are arranged or encoded on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk.
  • Software or firmware or such a configuration may be installed on the computing device such that one or more processors in the computing device perform the technical solutions described in the embodiments of the present invention.

Landscapes

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

Abstract

本发明提供了一种用户设备UE处执行的UE上下文管理方法以及相关的UE。所述方法包括：当所述UE或UE无线资源控制RRC层从演进节点eNB接收到RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器。所述RRC连接挂起消息或RRC连接挂起过程用于在UE处挂起RRC连接并保存UE上下文。所述方法还包括：如果所述UE上下文管理定时器到期，由所述UE或UE RRC层释放所保存的UE上下文。

Description

UE上下文管理方法和设备 技术领域
本发明涉及无线通信技术领域。更具体地，本发明涉及UE上下文管理方法和设备。
背景技术
随着物联网应用和物联网终端设备的广泛应用，设计出一种适应于物联网通信的无线网络技术成为必须解决的问题。第三代合作伙伴计划(3rd Generation Partnership Proiect，3GPP)正在研究一种新的接入***，用于设计出一种低复杂性、低吞吐量的无线接入技术来解决无线物联网所面临的需求，称为窄带物联网(NarrowBand-Internet of Things，NB-IoT)。这种接入技术的特性包括支持低吞吐量的大量设备、低时延敏感度、超低设备成本，超低功耗和优化的网络架构。
在优化的网络架构方面，目前3GPP引入了一种解决方案，称为用户面解决方案，简述如下：
1.用户设备(UE，User Equipment)入网后，采用现有机制建立和网络侧的连接，进行数据传输，如图1所示进行无线资源控制(Radio Resource Control，RRC)连接建立、数据无线承载(Data Radio Bearer，DRB)建立和安全建立，然后若有需要则进行数据传输。
2.区别于在现有长期研究(Long Term Evolution，LTE)***中，UE和演进基站(evolved NodeB，eNB)在数据传输完成后，释放RRC连接，删除UE上下文并进入RRC idle状态；在用户面解决方案中，当数据传输完成后，UE和eNB挂起RRC连接，保存UE上下文，如图1所示，eNB通过RRC信令告知UE挂起RRC连接并保存UE上下文。
3.如图2所示，当UE有上行数据发送或下行数据接收时，UE向eNB发起RRC连接恢复流程，因为UE和eNB上保存了UE上下文，通过该流程可以恢复其RRC连接，直接进行数据传输，而无需再通过RRC重配置流程进行DRB的建立，和无需通过安全 建立流程进行空口安全的建立。可以看出，通过这种方式，节省了空口的信令开销。
如上所述，用户面解决方案中通过引入RRC连接挂起/恢复流程来降低数据传输时的控制信令开销，这就意味着当UE的RRC连接挂起之后，UE和eNB上都需要保存该UE的上下文，直到下一次有上行数据或下行数据传输发生，以便成功执行RRC连接恢复流程。考虑到网络中，尤其是物联网中繁杂多样的应用，有大量的传输小数据业务的UE设备数如用于水电费抄表的终端设备，eNB上需要维护大量的UE上下文；同时考虑到很多业务应用的数据发送并不频繁，则在两次数据传输之间，eNB和UE需要长时间保存UE上下文，这就形成了一种负担。在另一种场景下，如果UE移动到了其他eNB覆盖下，则原eNB上保存的UE上下文是无用的。考虑到上述问题，如何合理管理UE上下文成为需要解决的问题。
发明内容
如背景技术部分所述，NB-IoT技术中引入了用户面解决方案后，eNB和UE上都需要保存UE上下文，而在一些场景下，无限制地保存UE上下文存在弊端，现在机制无法覆盖这一问题。这成为本发明所关注并要解决的问题。
本发明所述方法并不限于背景技术部分所述的Release 13的NB-IoT***，也适用于其他非NB-IoT装置和***，如机器类型通信(Machine Type Communication，MTC)场景等。
根据本发明实施例的第一个方面，提供了一种在用户设备UE处执行的UE上下文管理方法，包括：当所述UE或UE无线资源控制RRC层从演进节点eNB接收到RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器，所述RRC连接挂起消息或RRC连接挂起过程用于在UE处挂起RRC连接并保存UE上下文；以及如果所述UE上下文管理定时器到期，由所述UE或UE RRC层释放所保存的UE上下文。
可选地，所述方法还包括：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程或RRC连接建立过程，由所述UE或UE RRC层停止所述UE上下文管理定时器。可选地，如果所述UE或UE RRC层发起的是RRC连接恢复过程，则仍保存所述UE上下文；如果所述UE或UE RRC层发起的是RRC连接建立过程，则释放所保存的UE上下文。
可选地，所述方法还包括：如果在所述UE上下文管理定时器正在运行时接收到寻呼消息，由所述UE或UE RRC层停止所述UE上下文管理定时器，并且仍保存所述UE上下文。
可选地，所述UE上下文是UE接入层AS上下文。
可选地，所述UE是窄带物联网NB-IoT UE或非NB-IoT UE。
可选地，所述定时器的值预先设置为固定值。
可选地，所述定时器的值是由eNB经由RRC信令或由移动性管理实体MME经由非接入层NAS信令配置的。
根据本发明的第二方面，提供了一种用户设备UE，用于执行UE上下文管理。所述UE包括：定时器管理单元，被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器；以及UE上下文管理单元，被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，在UE处挂起RRC连接并保存UE上下文；以及如果所述UE上下文管理定时器到期，释放所保存的UE上下文。
可选地，所述定时器管理单元还可以被配置为：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程或RRC连接建立过程，停止所述UE上下文管理定时器。进一步地，所述UE上下文管理单元还可以被配置为：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程，则仍保存所述UE上下文；如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接建立过程，则释放所保存的UE上下文。
可选地，所述定时器管理单元还被配置为：如果在所述UE上下文管理定时器正在运行时接收到寻呼消息，停止所述UE上下文管理定时器。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
参照以下的附图可以更好地理解本发明的很多方面。附图中的部件不是成比例绘制的，而只是为了示出本发明的原理。为了便于示出和描述本发明的一些部分，附图中对应部分可能被放大或缩小。
在本发明的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是RRC连接挂起示意图；
图2是RRC连接恢复流程示意图；
图3是根据本发明的在UE处执行的UE上下文管理方法的流程图。
图4是根据本发明实施例1的UE侧处理的一种流程示意图。
图5是根据本发明实施例2的UE侧处理的一种流程示意图。
图6是根据本发明实施例3的UE侧处理的一种流程示意图。
图7-9是根据本发明实施例4的UE侧处理的一种流程示意图。
图10是根据本发明实施例5的UE侧配置的一种流程示意图。
图11是根据本发明实施例5的网络侧配置的一种流程示意图。
图12是根据本发明实施例5的网络侧交互流程示意图。
图13是根据本发明实施例6的UE的一构成示意图。
具体实施方式
参照附图，通过下面的说明书，本发明的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本发明的特定实施方式，其表明了其中可以采用本发明的原则的部分实施方式，应了解的是，本发明不限于所描述的实施方式，相反，本发明包括落入所附权利要求的范围内的全部修改、变型以及等同物。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
以下将结合附图和具体实施例，对本发明所提出的UE上下文管理方法进行进一步说明。
下文以LTE移动通信***及其后续的演进版本作为示例应用环境，以NB-IoT为实施技术场景，具体描述了根据本发明的多个实施例。然而，需要指出的是，本发明不限于以下实施例，而是可适用于更多其它的无线通信***，例如今后的5G蜂窝通信***。
图3是示出了根据本发明的在UE处执行的UE上下文管理方法300的流程图。
如图所示，该方法包括步骤301，其中，当所述UE或UE无线资源控制RRC层从演进节点eNB接收到RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器。所述RRC连接挂起消息或RRC连接挂起过程用于在UE处挂起RRC连接并保存UE上下文。该方法还包括步骤302，其中，如果所述UE上下文管理定时器到期，由所述UE或UE RRC层释放所保存的UE上下文。
通过设置定时器并在定时器到期时释放所保存的UE上下文，可以有效地管理UE上下文。
以下依次详细描述本发明的实施例1～6。
实施例1
图4为本发明实施例1中UE侧处理流程图。本实施例提供了一种UE侧根据UE上下文管理定时器对所保存的UE上下文管理的方法。
步骤401：UE或UE RRC层接收RRC连接挂起消息或启动RRC连接挂起流程。所述RRC连接挂起消息用于指示UE挂起RRC连接并保存UE上下文，本发明中称为RRC连接挂起消息；所述RRC连接挂起流程用于挂起RRC连接并保存UE上下文，本发明中称为RRC连接挂起流程，其实现方式举例如背景技术部分所示。
步骤402：UE或UE RRC层启动UE上下文管理定时器。所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
在本实施例中，所述定时器的值可以是固定值，如通过预定义方式或默认方式的固定值，也可以是由网络侧配置的值，如实施例5所述方式。
该实施例中的UE上下文可以是UE接入层(Access stratum，AS)上下文；UE可以是NB-IoT UE，也可以是非NB-IoT的其他类型UE。
实施例2
图5为本发明实施例2中UE侧处理流程图。本实施例提供了一种UE侧根据UE上下文管理定时器对所保存的UE上下文管理的方法。
步骤501：UE或UE RRC层启动一个RRC流程，或接收到寻呼消息。所述RRC流程用于恢复之前挂起的RRC连接，本发明中称为RRC连接恢复流程，其实现方式举例如背景技术部分所示；或者所述RRC流程可以是RRC连接建立流程。
步骤502：如果UE上下文管理定时器正在运行，UE或UE RRC层停止该定时器。所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
可选的，在该步骤中，若步骤501中UE或UE RRC层启动的是RRC连接恢复流程，则UE仍然保存UE上下文；若UE或UE RRC层启动 的是RRC连接建立流程，则UE删除UE上下文。
在本实施例中，所述定时器的值可以是固定值，如通过预定义方式或默认方式的固定值，也可以是由网络侧配置的值，如实施例5所述方式。
该实施例中的UE上下文可以是UE接入层(Access stratum，AS)上下文；UE可以是NB-IoT UE，也可以是非NB-IoT的其他类型UE。
实施例3
图6为本发明实施例中UE侧处理流程图。本实施例提供了一种UE侧根据UE上下文管理定时器对所保存的UE上下文管理的方法。
步骤601：UE上下文管理定时器超时。所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
步骤602：UE或UE RRC层执行以下行为：
行为1：释放所保存的UE上下文。
行为2：通知上层所述定时器超时和/或UE上下文的释放。
行为3：重置MAC层。
在该步骤中，行为1～3是可选的，即UE可以执行行为1～3中的一种或多种。典型的行为是UE执行行为1～2，即UE或UE RRC层释放所保存的UE上下文并告知上层。
在本实施例中，所述定时器的值可以是固定值，如通过预定义方式或默认方式的固定值，也可以是由网络侧配置的值，如实施例5所述方式。
该实施例中的UE上下文可以是UE接入层(Access stratum，AS)上下文；UE可以是NB-IoT UE，也可以是非NB-IoT的其他类型UE。
实施例4
图7为本发明实施例中UE侧处理流程图。本实施例提供了一种UE侧根据UE上下文管理定时器对所保存的UE上下文管理的方法。
步骤701：UE或UE RRC层接收一个RRC消息或启动一个RRC流程。所述RRC消息用于指示UE挂起RRC连接并保存UE上下文，本 发明中称为RRC连接挂起消息；所述RRC流程用于挂起RRC连接并保存UE上下文，本发明中称为RRC连接挂起流程，其实现方式举例如背景技术部分所示。
步骤702：UE或UE RRC层启动UE上下文管理定时器。所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
步骤703：判断UE或UE RRC层是否启动一个RRC流程，或是否接收到寻呼消息。如果是，则执行步骤704a；否则，执行步骤704b。
所述RRC流程用于恢复之前挂起的RRC连接，本发明中称为RRC连接恢复流程，其实现方式举例如背景技术部分所示；或者所述RRC流程可以是RRC连接建立流程。
步骤704a：UE或UE RRC层停止UE上下文管理定时器。
可选的，在该步骤中，若步骤703中UE或UE RRC层启动的是RRC连接恢复流程，则UE仍然保存UE上下文；若UE或UE RRC层启动的是RRC连接建立流程，则UE删除UE上下文。
步骤704b：判断UE上下文管理定时器是否超时。如果是，则执行步骤705，否则返回执行步骤703。
步骤705：UE或UE RRC层执行以下行为：
行为1：释放所保存的UE上下文。
行为2：通知上层所述定时器超时和/或UE上下文的释放。
行为3：重置MAC层。
在该步骤中，行为1～3是可选的，即UE可以执行行为1～3中的一种或多种。典型的行为是UE执行行为1～2，即UE或UE RRC层释放所保存的UE上下文并告知上层。
在本实施例中，所述定时器的值可以是固定值，如通过预定义方式或默认方式的固定值，也可以是由网络侧配置的值，如实施例5所述方式。
该实施例中的UE上下文可以是UE接入层(Access stratum，AS)上下文；UE可以是NB-IoT UE，也可以是非NB-IoT的其他类型UE。
本领域技术人员将理解：图7所示的方法是说明性而非限制性的。具体地，该方法的实现可以不依赖于图7所示的执行操作的特定顺序。
例如，图8示出了先执行判断UE或UE RRC层是否启动一个RRC流程或是否接收到寻呼消息的步骤再执行判断UE上下文管理定时器是否超时的步骤的情形。图9示出了判断UE或UE RRC层是否启动一个RRC流程或是否接收到寻呼消息的步骤和判断UE上下文管理定时器是否超时的步骤并行执行的情形。
实施例5
图10为本发明实施例5中UE侧配置流程图。
步骤1001：UE接收配置消息，其中包含UE上下文管理定时器配置信息，所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
在本实施例中，所述配置信息包含所述定时器的值。举例，以所述定时器命名为TCTX_REL为例，所述配置信息包含TCTX_REL的取值可以是{ms100，ms200，ms300，ms400，ms600，ms1000，ms1500，ms2000，min5，min10，min20，min30，hr1，hr2，hr 8，hr16，day1，day2，day4}中的一种，当然其取值并不限于上述值。
所述UE接收的配置消息可以是由eNB发送的RRC消息，一种方式是以广播方式发送的***信息消息如第二***信息块(System Information Block 2，SIB2)，另一种方式是UE专用RRC消息如RRC连接重配置消息、RRC连接挂起消息等；也可以是由MME(Mobility Management Entity)发送的NAS消息。上述仅为配置消息的部分实施方式举例，并不限于此。
该实施例中的UE上下文可以是UE接入层(Access stratum，AS)上下文；UE可以是NB-IoT UE，也可以是非NB-IoT的其他类型UE。
步骤1002：UE应用所接收到的UE上下文管理定时器配置信息，并根据该定时器配置信息管理所保存的UE上下文。UE根据该定时器管理所保存的UE上下文的具体实现方式在实施例1～4中给出了示例，但并不限于此。
图11为本发明实施例5中网络侧配置流程图。
步骤1101：网络侧发送一个配置消息，其中包含UE上下文管理定时器配置信息，所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
在本实施例中，所述配置信息包含所述定时器的值。举例，以所述定时器命名为TCTX_REL为例，所述配置信息包含TCTX_REL的取值可以是{ms100，ms200，ms300，ms400，ms600，ms1000，ms1500，ms2000，min5，min10，min20，min30，hr1，hr2，hr 8，hr16，day1，day2，day4}中的一种，当然其取值并不限于上述值。
所述网络侧发送的配置消息可以是由eNB发送的RRC消息，一种方式是以广播方式发送的***信息消息如SIB2，另一种方式是UE专用RRC消息如RRC连接重配置消息、RRC连接挂起消息等；也可以是由MME(Mobility Management Entity)发送的NAS消息。上述仅为配置消息的部分实施方式举例，并不限于此。
图12为本发明实施例5中网络侧交互流程图。
步骤1201：MME发送一个配置消息，其中包含UE上下文管理定时器配置信息，所述定时器用于UE上下文管理，或者说UE上下文释放，本发明中称为UE上下文管理定时器。
在本实施例中，所述配置信息包含所述定时器的值。举例，以所述定时器命名为TCTX_REL为例，所述配置信息包含TCTX_REL的取值可以是{ms100，ms200，ms300，ms400，ms600，ms1000，ms1500，ms2000，min5，min10，min20，min30，hr1，hr2，hr 8，hr16，day1，day2，day4}中的一种，当然其取值并不限于上述值。
所述MME发送的配置消息为S1AP消息，例如初始上下文请求消息，或承载建立/修改/释放消息，或UE上下文释放消息等。上述仅为配置消息的部分实施方式举例，并不限于此。
步骤1202：eNB接收该配置信息，并据此将该信息配置给UE。eNB向UE配置的方式举例如图11所述方式。
实施例6
图13示出了根据本发明实施例5的UE 1300的结构示意图。如图所示，UE 1300包括定时器管理单元1310和UE上下文管理单元1320。定时器管理单元1310被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器。UE上下文管理单元1320被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，在UE处挂起RRC连接并保存UE上下文；以及如果所述UE上下文管理定时器到期，释放所保存的UE上下文。
可选地，所述定时器管理单元还可以被配置为：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程或RRC连接建立过程，停止所述UE上下文管理定时器。进一步地，所述UE上下文管理单元还可以被配置为：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程，则仍保存所述UE上下文；如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接建立过程，则释放所保存的UE上下文。
可选地，所述定时器管理单元还可以被配置为：如果在所述UE上下文管理定时器正在运行时接收到寻呼消息，停止所述UE上下文管理定时器。
应该理解，本发明的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
在本申请中，“基站”是指具有较大发射功率和较广覆盖面积的移动 通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”是指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
此外，这里所公开的本发明的实施例可以在计算机程序产品上实现。更具体地，该计算机程序产品是如下的一种产品：具有计算机可读介质，计算机可读介质上编码有计算机程序逻辑，当在计算设备上执行时，该计算机程序逻辑提供相关的操作以实现本发明的上述技术方案。当在计算***的至少一个处理器上执行时，计算机程序逻辑使得处理器执行本发明实施例所述的操作(方法)。本发明的这种设置典型地提供为设置或编码在例如光介质(例如CD-ROM)、软盘或硬盘等的计算机可读介质上的软件、代码和/或其他数据结构、或者诸如一个或多个ROM或RAM或PROM芯片上的固件或微代码的其他介质、或一个或多个模块中的可下载的软件图像、共享数据库等。软件或固件或这种配置可安装在计算设备上，以使得计算设备中的一个或多个处理器执行本发明实施例所描述的技术方案。
尽管以上已经结合本发明的优选实施例示出了本发明，但是本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，可以对本发明进行各种修改、替换和改变。因此，本发明不应由上述实施例来限定，而应由所附权利要求及其等价物来限定。

Claims (16)

  1. 一种在用户设备UE处执行的UE上下文管理方法，包括：
    当所述UE或UE无线资源控制RRC层从演进节点eNB接收到RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器，所述RRC连接挂起消息或RRC连接挂起过程用于在UE处挂起RRC连接并保存UE上下文；以及
    如果所述UE上下文管理定时器到期，由所述UE或UE RRC层释放所保存的UE上下文。
  2. 根据权利要求1所述的方法，还包括：
    如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程或RRC连接建立过程，由所述UE或UE RRC层停止所述UE上下文管理定时器。
  3. 根据权利要求2所述方法，还包括：
    如果所述UE或UE RRC层发起的是RRC连接恢复过程，则仍保存所述UE上下文；
    如果所述UE或UE RRC层发起的是RRC连接建立过程，则释放所保存的UE上下文。
  4. 根据权利要求1至3中任一项所述的方法，还包括：
    如果在所述UE上下文管理定时器正在运行时接收到寻呼消息，由所述UE或UE RRC层停止所述UE上下文管理定时器，并且仍保存所述UE上下文。
  5. 根据权利要求1至3中任一项所述的方法，其中，所述UE上下文是UE接入层AS上下文。
  6. 根据权利要求1至3中任一项所述的方法，其中，所述UE是窄带物联网NB-IoT UE或非NB-IoT UE。
  7. 根据权利要求1至3中任一项所述的方法，其中，所述定时器的值预先设置为固定值。
  8. 根据权利要求1至3中任一项所述的方法，其中，所述定时器的值是由eNB经由RRC信令或由移动性管理实体MME经由非接入层NAS信令配置的。
  9. 一种用户设备UE，用于执行UE上下文管理，所述UE包括：
    定时器管理单元，被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，由所述UE或UE RRC层启动UE上下文管理定时器；以及
    UE上下文管理单元，被配置为：当所述UE从演进节点eNB接收到无线资源控制RRC连接挂起消息或所述UE发起RRC连接挂起过程时，在UE处挂起RRC连接并保存UE上下文；以及如果所述UE上下文管理定时器到期，释放所保存的UE上下文。
  10. 根据权利要求9所述的UE，其中，所述定时器管理单元还被配置为：如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程或RRC连接建立过程，停止所述UE上下文管理定时器。
  11. 根据权利要求10所述的UE，其中，所述UE上下文管理单元还被配置为：
    如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接恢复过程，则仍保存所述UE上下文；
    如果在所述UE上下文管理定时器正在运行时所述UE或UE RRC层发起了RRC连接建立过程，则释放所保存的UE上下文。
  12. 根据权利要求9至11中任一项所述的UE，其中，所述定时器管理单元还被配置为：如果在所述UE上下文管理定时器正在运行时接收到寻呼消息，停止所述UE上下文管理定时器。
  13. 根据权利要求9至11中任一项所述的UE，其中，所述UE上下文是UE接入层AS上下文。
  14. 根据权利要求9至11中任一项所述的UE，其中，所述UE是窄带物联网NB-IoT UE或非NB-IoT UE。
  15. 根据权利要求9至11中任一项所述的UE，其中，所述定时器的值预先设置为固定值。
  16. 根据权利要求9至11中任一项所述的UE，其中，所述定时器的值是由eNB经由RRC信令或由移动性管理实体MME经由非接入层NAS信令配置的。
PCT/CN2017/070266 2016-01-06 2017-01-05 Ue上下文管理方法和设备 WO2017118397A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17735835.5A EP3402300A4 (en) 2016-01-06 2017-01-05 CONTEXT MANAGEMENT PROCESS AND DEVICE FOR USER DEVICE
US16/068,295 US20190014614A1 (en) 2016-01-06 2017-01-05 Method and device for ue context management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610007236.7 2016-01-06
CN201610007236.7A CN106954282A (zh) 2016-01-06 2016-01-06 Ue上下文管理方法和设备

Publications (1)

Publication Number Publication Date
WO2017118397A1 true WO2017118397A1 (zh) 2017-07-13

Family

ID=59273259

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070266 WO2017118397A1 (zh) 2016-01-06 2017-01-05 Ue上下文管理方法和设备

Country Status (4)

Country Link
US (1) US20190014614A1 (zh)
EP (1) EP3402300A4 (zh)
CN (1) CN106954282A (zh)
WO (1) WO2017118397A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11991526B2 (en) 2019-12-16 2024-05-21 Qualcomm Incorporated Sidelink paired and unpaired states
CN114158141B (zh) * 2020-09-08 2024-03-22 华硕电脑股份有限公司 无线通信***中用于连接恢复程序的方法和设备
CN114449547B (zh) * 2020-11-03 2024-04-16 中国电信股份有限公司 用于释放挂起信息的方法、基站和通信***
EP4243509A4 (en) * 2021-02-05 2024-01-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. STATE SWITCHING METHOD, APPARATUS, DEVICE, AND STORAGE MEDIUM

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011134504A1 (en) * 2010-04-28 2011-11-03 Nokia Siemens Networks Oy Connection control in restart/recovery scenario
CN102448045A (zh) * 2010-09-30 2012-05-09 电信科学技术研究院 一种处理移动性管理上下文的方法和设备
CN102958194A (zh) * 2011-08-25 2013-03-06 中兴通讯股份有限公司 一种维持大量连接的方法、用户设备及***
CN104115454A (zh) * 2012-06-27 2014-10-22 联发科技股份有限公司 移动通信网络中ue数据的挂起的方法及用户设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9247575B2 (en) * 2012-03-27 2016-01-26 Blackberry Limited eNB storing RRC configuration information at another network component
EP3634035B1 (en) * 2014-10-28 2023-05-24 Telefonaktiebolaget LM Ericsson (publ) Network nodes, a user equipment and methods therein for handling a connection between the user equipment and a wireless communications network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011134504A1 (en) * 2010-04-28 2011-11-03 Nokia Siemens Networks Oy Connection control in restart/recovery scenario
CN102448045A (zh) * 2010-09-30 2012-05-09 电信科学技术研究院 一种处理移动性管理上下文的方法和设备
CN102958194A (zh) * 2011-08-25 2013-03-06 中兴通讯股份有限公司 一种维持大量连接的方法、用户设备及***
CN104115454A (zh) * 2012-06-27 2014-10-22 联发科技股份有限公司 移动通信网络中ue数据的挂起的方法及用户设备

Also Published As

Publication number Publication date
EP3402300A4 (en) 2019-10-02
EP3402300A1 (en) 2018-11-14
US20190014614A1 (en) 2019-01-10
CN106954282A (zh) 2017-07-14

Similar Documents

Publication Publication Date Title
WO2017118399A1 (zh) 无线资源控制流程监测方法和设备
JP6645583B2 (ja) Ｒｒｃコネクションの再開手順
JP7222052B2 (ja) 端末、通信方法及び無線通信システム
WO2018113661A1 (zh) 用户移动性方法和设备
EP3337285B1 (en) Base station, user apparatus, and capability information transmission methods
US10342066B2 (en) Method and apparatus for dual connectivity management
JP6887495B2 (ja) ユーザ装置、無線通信システム及び無線通信方法
US12035401B2 (en) UE behavior with rejection of resume request
JP6208296B1 (ja) ユーザ装置、基地局、及び接続確立方法
WO2017078143A1 (ja) ユーザ装置、基地局、接続確立方法、及びコンテクスト情報取得方法
WO2018014661A1 (zh) 一种数据或者信令发送、传输方法及装置
WO2020063666A1 (zh) 用户设备及其执行的方法、基站及其执行的方法、移动控制实体及其执行的方法
WO2018019001A1 (zh) 一种终端状态转换方法及装置
CN113475109A (zh) 随着rrc恢复完成之类的消息的早期测量报告
WO2017118397A1 (zh) Ue上下文管理方法和设备
WO2017045149A1 (zh) 一种释放无线资源控制rrc连接的方法及装置
WO2018137459A1 (zh) 通信的方法、终端和接入网设备
JP6998943B2 (ja) ユーザ装置、無線通信システム及び無線通信方法
US11825546B2 (en) Method and device for updating a wait timer
WO2018198176A1 (ja) ユーザ装置、無線基地局及び無線通信方法
JPWO2018207775A1 (ja) ネットワーク装置及び無線通信方法
TW202123767A (zh) 用於在通訊網路中管理無線電承載相容性之系統和方法
JP2023519587A (ja) 端末装置及び基地局
US9094981B2 (en) Method, system and device for processing release failure of packet data network
CN108353452B (zh) 用户装置、基站、和连接建立方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2017735835

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017735835

Country of ref document: EP

Effective date: 20180806