Method and device for controlling RRC state, and computer storage medium

Abstract

Disclosed are a method and device for controlling an RRC state, and a computer storage medium. The method includes: sending, by a terminal device, a first RRC message to a network device, the first RRC message comprising an RRC connection resume request message; receiving, by the terminal device, a second RRC message sent by the network device, the second RRC message carrying first indication information which is indicative of a target RRC state of the terminal device; and entering, by the terminal device, the target RRC state based on the first indication information.

Claims

1. A method for controlling an RRC state in a UE-initiated RRC connection resume procedure, comprising: sending, by a terminal device which is in an inactive state, a radio resource control (RRC) connection resume request message to a network device; receiving, by the terminal device, an RRC connection release message sent from the network device in response to the connection resume request message, the RRC connection release message carrying first indication information which indicates a target state of the terminal device; and entering, by the terminal device, the target RRC state based on the first indication information; wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message carrying at least one of I-RNTI, radio access network (RAN) discontinuous reception (DRX) cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses the at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers; and wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message not carrying the at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses locally stored at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers; wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC idle state, entering, by the terminal device, the RRC idle state; wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC connected state, entering, by the terminal device, the RRC connected state.

2. The method according to claim 1, wherein the RRC connection resume request message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target state of the terminal device in a connection resume procedure.

3. A method for controlling an RRC state in a UE-initiated RRC connection resume procedure, comprising: receiving, by a network device, a radio resource control (RRC) connection resume request message sent from a terminal device which is in an inactive state; and sending, by the network device, an RRC connection release message to the terminal device in response to the connection resume request message, the RRC connection release message carrying first indication information which indicates a target RRC state of the terminal device, wherein the terminal device enters the target RRC state based on the first indication information, wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message carrying at least one of I-RNTI, radio access network (RAN) discontinuous reception (DRX) cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses the at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers configuration information that is carried in RRC connection release message; and wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message not carrying at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses locally stored at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers; wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC idle state, the terminal device enters the RRC idle state; and wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC connected state, the terminal device enters the RRC connected state.

4. The method according to claim 3, wherein the RRC connection resume request message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target state of the terminal device in a connection resume procedure.

5. A terminal device, comprising: a processor; a transmission device; a memory for storing instructions executable by the processor; wherein the processor is configured to control the transmission device to: in a UE-initiated RRC connection resume procedure, send to a network device a radio resource control (RRC) connection resume request message when the terminal device is in an inactive state; receive an RRC connection release message sent from the network device in response to the connection resume request message, the RRC connection release message carrying first indication information which indicates a target state of the terminal device; and wherein the processor is further configured to: enter the target RRC state based on the first indication information; wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message carrying at least one of I-RNTI, radio access network (RAN) discontinuous reception (DRX) cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses the at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers; and wherein in response to the target RRC state being an RRC inactive state and the RRC connection release message not carrying at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers, after entering the RRC inactive state, the terminal device uses locally stored at least one of I-RNTI, RAN DRX cycle, and periodic RAN notification area update timers; wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC idle state, the terminal device enters the RRC idle state; wherein in response to the target RRC state as indicated in first indication information carried in the RRC connection release message being an RRC connected state, the terminal device enters the RRC connected state.

6. The device according to claim 5, wherein the RRC connection resume request message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target state of the terminal device in a connection resume procedure.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The accompanying drawings, which constitute a part of the present application, provide further understanding of the present disclosure. Exemplary embodiments of the present disclosure together with the descriptions thereof serve to explain the disclosure and are not intended to be restrictive of the present disclosure.

(2) FIG. 1 is a schematic diagram of an RRC connection resume procedure;

(3) FIG. 2 is a first schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure;

(4) FIG. 3 is a second schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure;

(5) FIG. 4 is a third schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure;

(6) FIG. 5 is a fourth schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure;

(7) FIG. 6 is a first schematic structural diagram of a device for controlling an RRC state according to an embodiment of the present disclosure;

(8) FIG. 7 is a second schematic structural diagram of a device for controlling an RRC state according to an embodiment of the present disclosure;

(9) FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

(10) In order to understand features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and are not intended to limit the embodiments of the disclosure.

(11) The technical solutions of the embodiments of the present disclosure are mainly applied to a 5G mobile communication system. Of course, technical solutions of embodiments of the present disclosure are not limited to the 5G mobile communication system but can be applied to other types of mobile communication systems. The main application scenarios in the 5G mobile communication system will be described as follows:

(12) 1) the eMBB scenario: eMBB is intended to allow users to obtain multimedia contents, services and data and its service demand is growing rapidly. Since eMBB may be deployed in various scenarios, such as indoors, urban areas and rural areas, there will be great differences in its service capabilities and requirements. Therefore, services are analyzed in combination with specific deployment scenarios.

(13) 2) the URLLC scenario: typical applications of URLLC include industrial automation, power automation, telemedicine operations, and traffic security, and so on.

(14) 3) the mMTC scenario: the URLLC includes typical characteristics of high connection density, small data volume, delay-insensitive service, low cost and long service life of modules.

(15) Three kinds of RRC states in the 5G network environment will be described below:

(16) 1) RRC_IDLE state: the mobility refers to the UE based cell reselection and paging is initiated by a CN and a paging area is configured by the CN. There is no UE AS context on a base station side. There is no RRC connection.

(17) 2) RRC_CONNECTED state: there is an RRC connection and there is a UE AS context on the base station and the UE sides. The network side knows that the location of the UE is at a specific cell level. The mobility is controlled by the network side. Unicast data can be transmitted between the UE and the base station.

(18) 3) RRC_INACTIVE state: the mobility refers to the UE-based cell reselection and there is a connection between a CN and an RAN and UE AS contexts exist on a certain base station; paging is triggered by the RAN and a RAN-based paging area is managed by the RAN and the network side knows that the location of the UE is at a level of the RAN based paging area.

(19) FIG. 1 is a schematic diagram of an RRC connection resume procedure. As shown in FIG. 1, the RRC connection resume procedure includes the following procedures:

(20) In step 101, an UE is in an INACTIVE state and an RRC connection is to be resumed.

(21) In step 102, the UE sends a preamble to a gNB.

(22) In step 103, the gNB sends a random access response (RAR) to the UE.

(23) In step 104, the UE sends an RRC connection resume request message to the gNB.

(24) In step 105, the gNB requests UE context information from an anchor gNB.

(25) In step 106, the gNB sends an RRC connection resume message to the UE.

(26) In step 107, the UE enters an RRC_CONNECTED state.

(27) The purpose of the embodiment of the present disclosure is to control, by a network side, the UE to enter any one of the RRC_CONNECTED state, an RRC_INACTIVE state and an RRC_IDLE state.

(28) FIG. 2 is a first schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes the following steps:

(29) In step 201, a terminal device sends a first RRC message to a network device. The first RRC message includes an RRC connection resume request message.

(30) In an embodiment of the present disclosure, the terminal may be any device which is capable of communicating with the network device, such as a mobile phone, a tablet computer, a notebook computer, a desktop computer or the like.

(31) In an embodiment of the present disclosure, the network device refers to a base station, such as a gNB in 5G.

(32) In an embodiment of the present disclosure, when initiating an RRC connection resume procedure, the terminal device initiates a random access procedure at first and then sends an RRC connection resume request message (corresponding to the first RRC message) to the network side in MSG3.

(33) In step 202, the terminal device receives a second RRC message sent by the network device. The second RRC message carries first indication information, which is used for indicating a target RRC state of the terminal device.

(34) In an embodiment of the present disclosure, the second RRC message includes an RRC connection resume message, an RRC connection release message, or a newly defined RRC message.

(35) In an embodiment, the first RRC message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target RRC state of the terminal device in a connection resume procedure.

(36) In step 203, the terminal device enters the target RRC state based on the first indication information.

(37) In an embodiment of the present disclosure, the target RRC state is an RRC connected state, an RRC inactive state, or an RRC idle state.

(38) In an embodiment, if the target RRC state is an RRC inactive state and the second RRC message does not carry configuration information corresponding to the RRC inactive state, after entering the RRC inactive state, the terminal device uses locally stored configuration information that corresponds to the RRC inactive state.

(39) In an embodiment, if the target RRC state is an RRC inactive state and the second RRC message carries configuration information corresponding to the RRC inactive state, after entering the RRC inactive state, the terminal device uses the configuration information carried in the second RRC message and corresponding to the RRC inactive state.

(40) In the above solutions, the configuration information corresponding to the RRC inactive state includes at least one of I-RNTI, RAN notification area, RAN DRX cycle, periodic RAN notification area update timer.

(41) FIG. 3 is a second schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 3, the method includes the following steps:

(42) In step 301, a UE is in an INACTIVE state and an RRC connection is to be resumed.

(43) In step 302, the UE sends a preamble to a gNB.

(44) In step 303, the gNB sends a random access response (RAR) to the UE.

(45) In step 304, the UE sends an RRC connection resume request message to the gNB.

(46) The gNB determines a target RRC state of the UE in this RRC connection resume procedure according to indication information for indicating a reason for the RRC connection resume in the RRC connection resume request message.

(47) In step 305, the gNB requests UE context information from an anchor gNB.

(48) In step 306, the gNB sends an RRC connection resume message to the UE. The RRC connection resume message carries indication information which is used for indicating the target RRC state of the UE.

(49) In step 307, the UE enters the target RRC state according to the indication information.

(50) Here, when the RRC connection resume message does not carry configuration information corresponding to an RRC_INACTIVE state and meanwhile a network side instructs the UE to enter the RRC_INACTIVE state, the UE uses the originally stored configuration information corresponding to the RRC_INACTIVE state by default.

(51) In step 308, the UE sends an RRC connection resume complete message to the gNB.

(52) Here, the UE may not perform the step 308.

(53) FIG. 4 is a third schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 4, the method includes the following steps:

(54) In step 401, a UE is in an INACTIVE state and an RRC connection is to be resumed.

(55) In step 402, the UE sends a preamble to a gNB.

(56) In step 403, the gNB sends a random access response (RAR) to the UE.

(57) In step 404, the UE sends an RRC connection resume request message to the gNB.

(58) The gNB determines a target RRC state of the UE in this RRC connection resume procedure according to indication information for indicating a reason for the RRC connection resume in the RRC connection resume request message.

(59) In step 405, the gNB requests UE context information from an anchor gNB.

(60) In step 406, the gNB sends an RRC connection release message to the UE. The RRC connection release message carries indication information which is used for indicating the target RRC state of the UE.

(61) In step 407, the UE enters the target RRC state according to the indication information.

(62) Here, when the RRC connection resume message does not carry configuration information corresponding to an RRC_INACTIVE state and meanwhile a network side instructs the UE to enter the RRC_INACTIVE state, the UE uses the originally stored configuration information corresponding to the RRC_INACTIVE state by default.

(63) FIG. 5 is a fourth schematic flowchart of a method for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 5, the method includes the following steps:

(64) In step 501, a network device receives a first RRC message sent by a terminal device. The first RRC message includes an RRC connection resume request message.

(65) In step 502, the network device sends a second RRC message to the terminal device. The second RRC message carries first indication information, which is indicative of a target RRC state of the terminal device, so that the terminal device enters the target RRC state based on the first indication information.

(66) In an embodiment, if the target RRC state is an RRC inactive state, the second RRC message may carry configuration information corresponding to the RRC inactive state or may not carry configuration information corresponding to the RRC inactive state.

(67) In an embodiment, the configuration information corresponding to the RRC inactive state includes at least one of I-RNTI, RAN notification area, RAN DRX cycle, periodic RAN notification area update timer.

(68) In an embodiment, the second RRC message includes an RRC connection resume message, an RRC connection release message, or a newly defined RRC message.

(69) In an embodiment, the first RRC message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target RRC state of the terminal device in a connection resume procedure.

(70) In an embodiment, the target RRC state is an RRC connected state, an RRC inactive state, or an RRC idle state.

(71) FIG. 6 is a first schematic structural diagram of a device for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 6, the device includes a sending unit 601, a receiving unit 602 and a control unit 603.

(72) The sending unit 601 is configured to send to a network device a first RRC message which includes an RRC connection resume request message.

(73) The receiving unit 602 is configured to receive a second RRC message sent by the network device, the second RRC message carrying first indication information which is indicative of a target RRC state of the terminal device.

(74) The control unit 603 is configured to control the terminal device to enter the target RRC state based on the first indication information.

(75) In an embodiment, if the target RRC state is an RRC inactive state and the second RRC message does not carry configuration information corresponding to the RRC inactive state, after entering the RRC inactive state, the terminal device uses locally stored configuration information that corresponds to the RRC inactive state.

(76) In an embodiment, if the target RRC state is an RRC inactive state and the second RRC message carries configuration information corresponding to the RRC inactive state, after entering the RRC inactive state, the terminal device uses the configuration information that is carried in the second RRC message and corresponds to the RRC inactive state.

(77) In an embodiment, the configuration information corresponding to the RRC inactive state includes at least one of I-RNTI, RAN notification area, RAN DRX cycle, periodic RAN notification area update timer.

(78) In an embodiment, the second RRC message includes an RRC connection resume message, an RRC connection release message, or a newly defined RRC message.

(79) In an embodiment, the first RRC message carries indication information for indicating a reason for the RRC connection resume, wherein the indication information for indicating the reason for the RRC connection resume is used by the network device to determine the target RRC state of the terminal device in a connection resume procedure.

(80) In an embodiment, the target RRC state is an RRC connected state, an RRC inactive state, or an RRC idle state.

(81) It should be appreciated by those skilled in the art that functions of the units in the RRC state control device shown in FIG. 6 will be understood with reference to the relevant descriptions of the foregoing methods for controlling the RRC state. The functions of the units in the RRC state control device shown in FIG. 6 can be implemented by programs running on a processor, or by a specific logic circuit.

(82) FIG. 7 is a second schematic structural diagram of a device for controlling an RRC state according to an embodiment of the present disclosure. As shown in FIG. 7, the device includes a receiving unit 701 and a sending unit 702.

(83) The receiving unit 701 is configured to receive a first RRC message sent by a terminal device, the first RRC message including an RRC connection resume request message.

(84) The sending unit 702 is configured to send a second RRC message to the terminal device, wherein the second RRC message carries first indication information, which is indicative of a target RRC state of the terminal device, so that the terminal device enters the target RRC state based on the first indication information.

(85) In an embodiment, if the target RRC state is an RRC inactive state, the second RRC message may or may not carry configuration information corresponding to the RRC inactive state.

(86) In an embodiment, the configuration information corresponding to the RRC inactive state includes at least one of I-RNTI, RAN notification area, RAN DRX cycle, periodic RAN notification area update timer.

(87) In an embodiment, the second RRC message includes an RRC connection resume message, an RRC connection release message, or a newly defined RRC message.

(88) In an embodiment, the first RRC message carries indication information for indicating a reason for the RRC connection resume, and the device further includes:

(89) a determining unit 703 configured to determine the target RRC state of the terminal device in a connection resume procedure based on the indication information for indicating the reason for the RRC connection resume.

(90) In an embodiment, the target RRC state is an RRC connected state, an RRC inactive state, or an RRC idle state.

(91) It should be appreciated by those skilled in the art that functions of the units in the RRC state control device shown in FIG. 7 will be understood with reference to the relevant descriptions of the foregoing methods for controlling the RRC state. The functions of the units in the RRC state control device shown in FIG. 7 can be implemented by programs running on a processor, or by a specific logic circuit.

(92) The devices for controlling an RRC state according to the embodiments of the present disclosure may also be stored in a computer readable storage medium when it is implemented as a software function module and sold or used as a stand-alone product. Based on this understanding, the essence of the technical solutions of the embodiments of the present disclosure, or the contribution of the technical solutions of the embodiments of the present disclosure over prior art, may be embodied in the form of a software product, and the computer software product is stored in a storage medium including a number of instructions such that a computer device (which may be a personal computer, a server, or a network device, etc.) performs all or part of the methods described in the various embodiments of the present disclosure. The foregoing storage medium includes various media that can store program codes, such as a USB flash disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk. Therefore the embodiments of the present disclosure are not limited to any specific combination of hardware and software.

(93) Correspondingly, an embodiment of the present disclosure further provides a computer storage medium having computer-executable instructions stored thereon. When executed by a processor, the computer-executable instructions implement the foregoing methods for controlling the RRC state according to the embodiments of the present disclosure.

(94) FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure. The computer device may be a terminal device or a network device. As shown in FIG. 8, a computer device 100 may include one or more processor 1002 (only one processor is shown, and the processor 1002 may include, but is not limited to a process device such as a Micro Controller Unit (MCU) or a Field Programmable Gate Array (FPGA)), a memory 1004 for storing data and a transmission device 1006 for communication. It will be understood by those skilled in the art that the structure shown in FIG. 8 is merely illustrative and it does not impose any limitation on the structure of the above electronic device. For example, the computer device 100 may also include more or less components than those shown in FIG. 8, or have a different configuration from that shown in FIG. 8.

(95) The memory 1004 may be used to store software programs and modules of application software, for example, program instructions/modules corresponding to the methods in the embodiments of the present disclosure, and the processor 1002 executes various function applications and data processing by running software programs and modules stored in the memory 1004. Namely, the above methods are implemented. The memory 1004 may include a high speed random access memory and a non-volatile memory, for example, one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 1004 may further include a remote memory which is remotely deployed from the processor 1002, which can be connected to the computer device 100 via a network. Examples of the network include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks and a combination thereof.

(96) The transmission device 1006 receives or transmits data via a network. A specific example of the network described above may include a wireless network provided by a communication provider of the computer device 100. In one example, the transmission device 1006 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission device 1006 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.

(97) The technical solutions described in the embodiments of the present disclosure can be arbitrarily combined if such combination will not result in conflict.

(98) In the embodiments provided by the present disclosure, it should be understood that the disclosed methods and smart devices may be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a kind of logical function division. In practice, other division manner may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the illustrated or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

(99) The units described as separated parts may or may not be physically separated, and the parts shown as units may or may not be physical units, that is, may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions in the embodiments.

(100) In addition, each functional unit in each embodiment of the present application may be integrated in one second processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The above integrated units can be implemented with hardware or hardware and software functional units.

(101) The exemplary embodiments of the present disclosure are described above, the scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or substitutions that should fall into the scope of the present disclosure.