DATA TRANSMISSION METHOD AND DEVICE IN RRC INACTIVE STATE, TERMINAL AND NETWORK SIDE DEVICE

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims a priority of the Chinese patent application No. 201810646671.3 filed on Jun. 21, 2018, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the field of wireless technology, and in particular to a data transmission method and device in an Inactive radio resource control (Radio Resource Control, RRC) state, a user terminal, and a network side device.

BACKGROUND

Anew RRC state is defined in the New Radio (NR) network: an RRC Inactive state. A node in the radio access network can send an RRC Release message carrying “SuspendConfig” to a User Equipment in an RRC Connected state (also called a user terminal), to instruct the user terminal to enter into the RRC Inactive state. After that, the node is an anchor node of the user terminal, and the context information of the user terminal is stored in the node. The above RRC Release message also includes radio access network notification area (RAN Notification Area, RNA) configuration information, and the user terminal does not need to communicate with the network side when it moves within the configured RNA range.

In the related art, when the user terminal is in the RRC Inactive state and the user terminal needs to interact with the network side, or the user terminal performs the RNA update procedure, the user terminal will trigger the RRC connection resumption procedure. In this case, the anchor node needs to move the context information of the user terminal to a serving node where the user terminal is currently located, that is, the context transfer procedure is performed. However, in the related art, the wireless access network nodes may use a more complex structure such as a centralized unit (Centralized Unit, CU)-control plane (CP)/user plane (User Plane, UP) separation, and the context transfer procedure is relatively complicated. The signaling overhead is large, and the setup delay is long, which is not convenient for small data transmission in the RRC Inactive state. Therefore, it is necessary to improve the data transmission mode in the RRC Inactive state to simplify the data transfer procedure of the user terminal in the RRC Inactive state.

SUMMARY

The purpose of the present disclosure is to provide a data transmission method and device in the RRC Inactive state, a user terminal and a device, and solve the problem in the related art that when the user terminal is in the RRC Inactive state and the RRC connection resumption procedure is triggered, the anchor node move the context information of the user terminal to the serving node where the user terminal is currently located, the context transfer procedure is relatively complicated, setup deadly is long and signaling overhead is large.

Some embodiment of the present disclosure provides a data transmission method in a radio resource control (RRC) Inactive state, applied to a first node device, and the method includes: when a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, sending an interface message including at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) to the second node device; wherein the second node device is a current serving node of a user terminal in the RRC Inactive state, and the first node device is an anchor node of the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message comprises at least one of: indication information for instructing the user terminal to send an uplink RRC message through a default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; or indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, the interface message comprises at least one of: indication information for instructing the second node device to receive an uplink RRC message through a default SRB1; indication information for instructing the second node device to continue to send a downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through a default SRB2; or indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

Optionally, the sending an interface message including at least one PDCP PDU to the second node device includes: sending the interface message to the second node device through a Retrieve UE Context Response message, or sending the interface message to the second node device through a Retrieve UE Context Failure message.

Optionally, the data transmission method in the RRC Inactive state further includes: when obtaining the Retrieve UE Context Request message sent by the second node device and determining that the Retrieve UE Context Request message includes preset indication information, determining not to perform a context transfer procedure; wherein the preset indication information is used to indicate not to perform the context transfer procedure.

Some embodiment of the present disclosure provides a data transmission method in a radio resource control (RRC) Inactive state, applied to a second node device, and the method includes: after sending a Retrieve UE Context Request message to a first node device according to an RRC Resume Request sent by a user terminal in the RRC Inactive state, receiving an interface message sent by the first node device according to the Retrieve UE Context Request message; wherein the interface message includes at least one PDCP PDU; the first node device is an anchor node of the user terminal, and the second node device is a current serving node of the user terminal.

Optionally, the data transmission method in the RRC Inactive state further includes: sending the PDCP PDU to the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, when the interface message includes the indication message for instructing the second node device to receive the uplink RRC message through the default SRB1, the method further comprises: receiving the PDCP PDU sent by the user terminal through the default SRB1 and including the uplink RRC message to be sent; sending the PDCP PDU sent by the user terminal to the first node device; when the interface message includes the indication message for instructing the second node device to continue to send the downlink RRC message through the default SRB1, the method further comprises: sending the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB1; when the interface message includes the indication message for instructing the second node device to receive the uplink RRC message through the default SRB2, the method further comprises: receiving the PDCP PDU sent by the user terminal through the default SRB2 and including the uplink RRC message to be sent; sending the PDCP PDU sent by the user terminal to the first node device; when the interface message includes the indication message for instructing the second node device to send the downlink RRC message through the default SRB2, the method further comprises: sending the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB2.

Optionally, the data transmission method in the RRC Inactive state further includes: receiving an RRC Resume Request sent by the user terminal, wherein the RRC Resume Request includes preset indication information, the preset indication information is used to indicate not to perform a context transfer procedure; and sending the Retrieve UE Context Request message to the first node device, wherein the Retrieve UE Context Response message includes the preset indication information.

Some embodiments of the present disclosure provides a data transmission method in a radio resource control (RRC) Inactive state, applied to a user terminal, and the method includes: when the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to a second node device, receiving an RRC message sent by the second node device; wherein the RRC message includes at least one of: indication information for instructing the user terminal to send an uplink RRC message through a default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2; wherein the second node device is a current serving node of the user terminal, and an anchor node of the user terminal is the first node device different from the second node device.

Optionally, when the RRC message includes the indication message for instructing the user terminal to send the uplink RRC message through the default SRB1, the method further comprises sending the uplink RRC message to the second node device through the default SRB1; when the RRC message includes the indication message for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1, the method further comprises continuing to receive the downlink RRC message from the second node device through the default SRB1; when the RRC message includes the indication message for instructing the user terminal to send the uplink RRC message through the default SRB2, the method further comprises sending the uplink RRC message to be sent to the second node device through the default SRB2; when the RRC message includes the indication message for instructing the user terminal to receive the downlink RRC message through the default SRB2, the method further comprises receiving the downlink RRC message from the second node device through the default SRB2.

Optionally, the data transmission method in the RRC Inactive state further includes: when initiating the RRC connection resumption, sending the RRC Resume Request to the second node device, wherein the RRC Resume Request includes preset indication information, the preset indication information is used to indicate not to perform the context transfer procedure.

Some embodiments of the present disclosure provides a node device, wherein the node device is a first node device, and the node device comprises: a transceiver, a memory, a processor, and a computer program stored on the memory and executed by the processor; wherein, the processor is used to read the computer program in the memory and execute the following procedure: when a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, sending an interface message including at least one PDCP PDU to the second node device, wherein the second node device is a current serving node of a user terminal in the RRC Inactive state, and the first node device is an anchor node of the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; or indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, the interface message includes at least one of the following indication information: indication information for instructing the second node device to receive an uplink RRC message through a default SRB1; indication information for instructing the second node device to continue to send a downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through a default SRB2; or indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

Optionally, the processor sends the interface message to the second node device through a Retrieve UE Context Response message, or sends the interface message to the second node device through a Retrieve UE Context Failure message.

Optionally, the processor is further configured to: when obtaining the Retrieve UE Context Request message sent by the second node device and determining that the Retrieve UE Context Request message includes preset indication information, determine not to perform a context transfer procedure, wherein the preset indication information is used to indicate not to perform the context transfer procedure.

Some embodiment of the present disclosure provides a node device, wherein the node device is a second node device, the node device comprises: a transceiver, a memory, a processor, and a computer program stored on the memory and executed by the processor; wherein the processor is used to read the computer program in the memory and execute the following procedure: after sending a Retrieve UE Context Request message to a first node device according to an RRC Resume Request sent by a user terminal in the RRC Inactive state, receiving an interface message sent by the first node device according to the Retrieve UE Context Request message; wherein the interface message includes at least one PDCP PDU; the first node device is an anchor node of the user terminal, and the second node device is a current serving node of the user terminal.

Optionally, the processor is further configured to: send the PDCP PDU to the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through a default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; or indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, the interface message received in step S410 further includes at least one of: indication information for instructing the second node device to receive an uplink RRC message through a default SRB1; indication information for instructing the second node device to continue to send a downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through a default SRB2; or indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

Optionally, when the interface message includes an indication message for instructing the second node device to receive the uplink RRC message through the default SRB1, the processor is further configured to: receive the PDCP PDU sent by the user terminal through the default SRB1 and including the uplink RRC message to be sent; send the PDCP PDU sent by the user terminal to the first node device; when the interface message includes the indication message for instructing the second node device to continue to send downlink RRC messages through the default SRB1, the processor is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB1; when the interface message includes the indication message for instructing the second node device to receive the uplink RRC message through the default SRB2, the processor is further configured to: receive the PDCP PDU sent by the user terminal through the default SRB2 and including the uplink RRC message to be sent; send the PDCP PDU sent by the user terminal to the first node device; when the interface message includes the indication message for instructing the second node device to send the downlink RRC message through the default SRB2, the processor is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB2.

Optionally, the processor is further configured to: receive an RRC Resume Request sent by the user terminal, wherein the RRC Resume Request includes preset indication information; the preset indication information is used to indicate not to perform a context transfer procedure; and send the Retrieve UE Context Request message to the first node device, wherein the Retrieve UE Context Response message includes the preset indication information.

Some embodiments of the present disclosure provides a user terminal, includes: a transceiver, a memory, a processor, and a computer program stored on the memory and executed by the processor; wherein the processor is used to read the program in the memory and execute the following procedure: when the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to a second node device, receiving an RRC message sent by the second node device; wherein the RRC message includes at least one of: indication information for instructing the user terminal to send an uplink RRC message through a default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; or indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2, wherein the second node device is a current serving node of the user terminal, and an anchor node of the user terminal is the first node device different from the second node device.

Optionally, when the RRC message includes the indication message for instructing the user terminal to send the uplink RRC message through the default SRB1, the processor is further configured to send the uplink RRC message to the second node device through the default SRB1; when the RRC message includes the indication message for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1, the processor is further configured to continue to receive the downlink RRC message from the second node device through the default SRB1; when the RRC message includes the indication message for instructing the user terminal to send the uplink RRC message through the default SRB2, the processor is further configured to send the uplink RRC message to be sent to the second node device through the default SRB2; when the RRC message includes the indication message for instructing the user terminal to receive the downlink RRC message through the default SRB2, the processor is further configured to receive the downlink RRC message from the second node device through the default SRB2.

Optionally, the processor is further configured to: when initiating the RRC connection resumption, send the RRC Resume Request to the second node device, wherein the RRC Resume Request includes preset indication information; the preset indication information is used to indicate not to perform the context transfer procedure.

Some embodiments of the present disclosure provides a data transmission device in a radio resource control (RRC) Inactive state, applied to a first node device, the data transmission device includes: a sending module, configured to, when a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, send an interface message including at least one PDCP PDU to the second node device, wherein the second node device is a current serving node of a user terminal in the RRC Inactive state, and the first node device is an anchor node of the user terminal.

Some embodiments of the present disclosure provides a data transmission device in a radio resource control (RRC) Inactive state, applied to a second node device, the data transmission device includes: a data transmission module, configured to, after sending a Retrieve UE Context Request message to a first node device according to an RRC Resume Request sent by a user terminal in the RRC Inactive state, receive an interface message sent by the first node device according to the Retrieve UE Context Request message, wherein the interface message includes at least one PDCP PDU; the first node device is an anchor node of the user terminal, and the second node device is a current serving node of the user terminal.

Some embodiments of the present disclosure provides a data transmission device in a radio resource control (RRC) Inactive state, applied to a user terminal, the data transmission device includes: a transceiver module, configured to, when the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to a second node device, receive an RRC message sent by the second node device, wherein the RRC message includes at least one of the following: indication information for instructing the user terminal to send an uplink RRC message through a default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send the uplink RRC message through a default second signaling radio bearer SRB2; or indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2, wherein the second node device is a current serving node of the user terminal, and an anchor node of the user terminal is a first node device different from the second node device.

Some embodiments of the present disclosure provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor to implement the steps of the data transmission method in the RRC Inactive state.

The above technical solutions of the present disclosure have at least the following beneficial effects: in the data transmission method in the RRC Inactive state according to some embodiments of the present disclosure, after the anchor node receives the Retrieve UE Context Request message, it may decide not to perform the context transfer procedure, but to perform data interaction in the form of PDCP PDU through the current serving node of the user terminal, which can avoid the complicated context transfer procedure. When the data to be transmitted is small, the execution procedure can be simplified, the signaling overhead can be saved, and the setup delay can be reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing an architecture of a wireless communication system to which a data transmission method in an RRC Inactive state is applied according to some embodiments of the present disclosure;

FIG. 2 is a schematic flowchart of a data transmission method according to the first embodiment of the present disclosure;

FIG. 3 is a system structure diagram of a data transmission method according to some embodiments of the present disclosure;

FIG. 4 is a schematic flowchart of the data transmission methods according to the second embodiment of the present disclosure;

FIG. 5 is another schematic flowchart of the data transmission method according to the second embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of the data transmission method according to the third embodiment of the present disclosure;

FIG. 7 is another schematic flowchart of the data transmission method according to the third embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a first implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 9 is a schematic diagram of a second implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 10 is a schematic diagram of a third implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 11 is a schematic diagram of a fourth implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 12 is a schematic diagram of a fifth implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 13 is a schematic diagram of a sixth implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 14 is a schematic diagram of a seventh implementation procedure of the data transmission method according to some embodiments of the present disclosure;

FIG. 15 is a schematic diagram showing an implementation structure of a node device according to some embodiments of the present disclosure;

FIG. 16 is a schematic diagram showing another implementation structure of a node device according to some embodiments of the present disclosure;

FIG. 17 is a schematic diagram showing the implementation structure of the device according to some embodiments of the present disclosure;

FIG. 18 is a schematic diagram showing a first structure of a data transmission device according to some embodiments of the present disclosure;

FIG. 19 is a schematic diagram showing a second structure of the data transmission device according to some embodiments of the present disclosure;

FIG. 20 is a schematic diagram showing a third structure of the data transmission device according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

In order to make the technical problem to be solved by the present disclosure, the technical solution and the advantages of the present disclosure clearer, the drawings and the embodiment are combined for detail description.

A data transmission method, a node device, and a user terminal in the RRC Inactive state described in some embodiments of the present disclosure are applied to a wireless communication system, and the wireless communication system may be a TD-LTE or NR system. FIG. 1 is a schematic diagram showing an architecture of the wireless communication system provided by some embodiments of the disclosure. As shown in FIG. 1, the wireless communication system includes at least two node devices 10 and a user terminal 20. In practical applications, the at least two node devices 10 are connected in a wireless mode. In order to conveniently and intuitively indicate the connection relationship between the node devices 10, a solid line is used in FIG. 1.

In some embodiments of the present disclosure, each node device 10 may be a base station, and there may be a plurality of base stations included in the wireless communication system. Each base station may be a commonly used base station or an evolved node base station (eNB), may also be a network side device in a 5G system (for example, a next generation node base station (gNB) or a transmission and reception point (TRP) or a cell or other device.

It should be noted that the wireless communication system described in some embodiments of the present disclosure may include a plurality of user terminals 20, and the node device 10 may communicate with the plurality of user terminals 20 for transmitting signaling or data.

Specifically, the user terminal 20 may be a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (Ultra-Mobile Personal Computer, UMPC), a netbook, or a personal digital assistant (Personal Digital Assistant, PDA), etc.

The wireless communication system of some embodiments of the present disclosure is applied for data transmission of the user terminal 20 in the RRC Inactive state. The RRC Inactive state is another RRC state besides the RRC connected state and the RRC idle state. In principle, the RRC Inactive state is only applied on the access layer (Access Stratum, AS) between the radio access network node and the mobile user terminal, and is not applied on the non-access layer (Non-access Stratum, NAS) between the node device and the core network.

In the wireless communication system of some embodiments of the present disclosure, one node device 11 of the plurality of node devices 10 may send an RRC Release message carrying “SuspendConfig” to one of the user terminals 20 in the RRC connected state, indicating the corresponding user terminal 20 to enter the RRC Inactive state. The node device 11 is the anchor node of the user terminal 20, which stores the context information of the user terminal 20, and the RRC Release message also includes RNA configuration information, so that the user terminal 20 does not need to communicate with the network side when the user terminal moves within the configured RNA range. In addition, when the user terminal 20 is in the coverage area of another node device 12 other than the anchor node, the node device 12 becomes the serving node where the user terminal 20 is currently located.

Further, the user terminal 20 can learn whether it is currently within the configured RNA range by broadcasting. When the user terminal 20 finds that the cell it resides does not belong to the RNA range configured by the RNA configuration information, the user terminal 20 usually initiates an RNA update procedure to request a new RNA from the network side, to ensure that the wireless access network can still find the user terminal 20 by paging.

If the user terminal 20 or the network side needs to send data, or the user terminal 20 needs to perform an RNA update procedure, the user terminal will trigger the RRC connection resumption procedure.

In related art, when the user terminal is in the RRC Inactive state and the RRC connection resumption procedure is triggered based on the above reasons, the anchor node needs to move the context information of the user terminal to the serving node where the user terminal is currently located. The context transfer procedure is cumbersome and the signaling overhead is large. In order to solve the above technical problem, in the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, when the anchor node of the user terminal in the RRC Inactive state receives the Retrieve UE Context Request message, it may decide not to perform the context transfer procedure, but adopt a mechanism similar to SRB1b in the dual-connection scenario to perform data interaction though the current serving node of the user terminal in the form of Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU), so as to avoid complicated context transfer procedure. When the data capacity to be transmitted is small, the effect of simplifying the procedure, saving signaling overhead, and reducing the establishment delay is achieved.

Specifically, as shown in FIG. 2, the data transmission method in the RRC Inactive state described in one embodiment of the present disclosure is applied to the first node device, the method includes the following step.

S210: if a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, an interface message including at least one PDCP PDU is sent to the second node device. The second node device is a current serving node of a user terminal in an RRC Inactive state, and the first node device is an anchor node of the user terminal.

With reference to the schematic diagram of the application architecture of the data transmission method in the RRC Inactive state according to some embodiments of the present disclosure shown in FIG. 3, when a user terminal in the RRC Inactive state moves to a serving range of another wireless access network node (the second node device) that is different from the anchor node (the first node device) and needs to transmit data (either control plane data or user plane data), after receiving the Retrieve UE Context Request message sent based on the RRC Resume Request message of the user terminal, the anchor node of the user terminal determines not to perform the context transfer procedure, but still retains the context information of the user terminal. The control data and user data connection between the radio access network node and the core network is still setup between the anchor node and the core network. In this way, the anchor node interacts the control data and the user data with the user terminal through the current serving node (the second node device) of the user terminal. On the node interface between the anchor node and the current serving node of the user terminal, data is exchanged in the form of PDCP PDU to realize data transmission when the user terminal is in an RRC Inactive state.

After receiving the Retrieve UE Context Request message sent based on the RRC Resume Request message of the user terminal, the anchor node determines not to perform the context transfer procedure, but still retains the context information of the user terminal, which can be regarded as a transient state, in the transient state, data is exchanged in the form of PDCP PDU between the anchor node and the current serving node of the user terminal, to realize data transmission when the user terminal is in an RRC Inactive state. The data transmission procedure does not require a complicated context transfer procedure. When the data to be transmitted is small, the effect of simplifying the execution procedure, saving signaling overhead, and reducing the setup delay can be achieved.

The above-mentioned method of data exchange in the form of PDCP PDU between the anchor node and the current serving node of the user terminal is used in the NR system, which allows the signaling radio bearer (Signaling Radio Bearer, SRB) to adopt a dual-connection structure, through the interaction between the auxiliary node and the user terminal, the signaling delay is reduced, or the reliability of the signaling is improved. By using a mechanism similar to SRB1b in the dual connectivity scenario, the current serving node exchanges data with the user terminal in the form of PDCP PDU, so as to realize the data transmission when the user terminal is in the RRC Inactive state.

Based on the foregoing principle, those skilled in the art should be able to understand the specific network structure for data exchange in the form of PDCP PDU among the anchor node, the current serving node and the user terminal, which will not be described in detail here. In the following, the data transmission methods described in some embodiments of the present disclosure will be described in detail based on the specific procedure of the above data transmission methods.

Optionally, when the data transmission method described in some embodiments of the present disclosure is applied to the first node device, the method further includes: when the Retrieve UE Context Request message sent by the second node device is obtained and it is determined that the Retrieve UE Context Request message includes preset indication information, it is determined not to perform the context transfer procedure. The preset indication information is used to indicate that the context transfer procedure does not need to be performed.

Based on the foregoing implementation, the Retrieve UE Context Request message sent by the current serving node (second node device) of the user terminal to the anchor node (first node device) of the user terminal may include a preset indication information indicating that the context transfer procedure does not need to be performed, so that the anchor node can determine not to perform the context transfer procedure according to the preset indication information.

Optionally, when the user terminal sends an RRC Resume Request to the current serving node, the RRC Resume Request may include preset indication information used to indicate that the context transfer procedure does not need to be performed, so that the current serving node sends the Retrieve UE Context Request message to the anchor node of the user terminal, the preset indication information is carried in the Retrieve UE Context Request message.

Based on the above method, the user terminal can determine whether context transfer is not required, so that the anchor node can determine not to perform the context transfer procedure.

Optionally, in some embodiments of the present disclosure, according to FIG. 2, step S210, the interface message including the PDCP PDU is sent to the second node device, wherein the PDCP PDU includes the RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Based on the above method, according to the specific instruction information indicated in the RRC message, the user terminal can perform data transmission with the radio access network node.

In addition, according to FIG. 2, in step S210, in the interface message including the PDCP PDU sent to the second node device, the interface message also includes at least one of the following indication information: indication information for instructing the second node device to receive the uplink RRC message through the default SRB1; indication information for instructing the second node device to continue sending downlink RRC messages through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through the default SRB2; and indication information for instructing the second node device to send a downlink RRC message through the default SRB2.

In the above manner, the indication information indicated in the interface message is used to enable the current serving node of the user terminal to perform data transmission with the anchor node of the user terminal and the user terminal.

Further, in step S210, when the interface message including the PDCP PDU is sent to the second node device, the interface message may be sent to the second node device through the Retrieve UE Context Response message, or the interface message may be sent to the second node device through Retrieve UE Context Failure message.

Another embodiment of the data transmission method in the RRC Inactive state of the present disclosure is applied to a second node device. As shown in FIG. 4, the method includes:

S410: after sending the Retrieve UE Context Request message to the first node device according to an RRC Resume Request sent by the user terminal in the RRC Inactive state, receiving the interface message sent by the first node device according to the Retrieve UE Context Request message. The interface message includes at least one PDCP PDU; the first node device is the anchor node of the user terminal, and the second node device is the current serving node of the user terminal.

Optionally, as shown in FIG. 4, the method further includes:

S420, sending the PDCP PDU to the user terminal.

Based on the above method, when the user terminal is in the RRC Inactive state, the anchor node of the user terminal, the current serving node of the user terminal, and the user terminal can perform data exchange in the form of PDCP PDU to realize data transmission when the user terminal is in the RRC Inactive state. Therefore, the complicated context transfer procedure is avoided, and the execution procedure is simplified, the signaling overhead is saved, and the setup delay is reduced.

In addition, the PDCP PDU in the received interface message in step S410 and the PDCP PDU sent to the user terminal in step S420 include the RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive downlink RRC messages through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Based on the above method, according to the specific instruction information indicated in the RRC message, the user terminal can perform data transmission with the radio access network node.

In addition, the interface message received in step S410 further includes at least one of the following indication information: indication information for instructing the second node device to receive the uplink RRC message through the default SRB1; indication information for instructing the second node device to continue to send the downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through the default SRB2; and indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

In the above mode, the indication information indicated in the interface message is used to enable the current serving node of the user terminal to perform data transmission with the anchor node of the user terminal and the user terminal.

When the interface message includes an indication message for instructing the second node device to receive the uplink RRC message through the default SRB1, the method further includes: receiving the PDCP PDU sent by the user terminal through the default SRB1 and including the uplink RRC message to be sent; sending the PDCP PDU sent by the user terminal to the first node device.

When the interface message includes an indication message for instructing the second node device to continue sending downlink RRC messages through the default SRB1, the method further includes: sending the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB1.

When the interface message includes an indication message for instructing the second node device to receive the uplink RRC message through the default SRB2, the method further includes: receiving the PDCP PDU sent by the user terminal through the default SRB2 and including the uplink RRC message to be sent; sending the PDCP PDU sent by the user terminal to the first node device.

When the interface message includes an indication message for instructing the second node device to send a downlink RRC message through the default SRB2, the method further includes: sending the PDCP PDU including the downlink RRC message to be sent to the user terminal to the user terminal through the default SRB2.

Optionally, when the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure is applied to the second node device, as shown in FIG. 5, the method further includes:

S401: receiving an RRC Resume Request sent by the user terminal, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that a context transfer procedure does not need to be performed;

S402. sending the Retrieve UE Context Request message to the first node device, in which the Retrieve UE Context Response message includes the preset indication information.

Based on the above method, the user terminal can determine whether context transfer is not required, so that the anchor node can determine not to perform the context transfer procedure.

Another embodiment of the data transmission method in the RRC Inactive state described in the present disclosure is applied to a user terminal. As shown in FIG. 6, the method includes the following step.

S610: when the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to the second node device, receiving the RRC message sent by the second node device.

The RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

The second node device is a current serving node for the user terminal, and the anchor node of the user terminal is a first node device different from the second node device.

According to some embodiments of the present disclosure, in the data transmission method in the RRC Inactive state, when the user terminal is in the RRC Inactive state and sends an RRC Resume Request to the second node device, the user terminal can receive indication information including the specific data transmission method from the second node device, so as to further perform data transmission according to the indication information indicated in the RRC message.

Optionally, when the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB1, the method further includes: sending the uplink RRC message to the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1, the method further includes: continuing to receive the downlink RRC message from the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB2, the method further includes: sending the uplink RRC message to be sent to the second node device through the default SRB2.

When the RRC message includes an indication message for instructing the user terminal to receive the downlink RRC message through the default SRB2, the method further includes: receiving a downlink RRC message from the second node device through the default SRB2.

Optionally, when the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure is applied to a user terminal, as shown in FIG. 7, the method further includes the following step.

S600: when initiating the RRC connection resumption, sending the RRC Resume Request to the second node device, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that the context transfer procedure does not need to be performed.

Based on the above method, the user terminal can determine whether the context transfer procedure is not required. When it is determined that the context transfer procedure is not required, the RRC Resume Request sent to the second node device includes a preset indication information for indicating that the context transfer procedure does not need to be performed, so that the anchor node can determine not to perform the context transfer procedure.

When the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure is adopted, data interaction among the user terminal, the anchor node and the current serving node is described based on the following implementation modes 1 to 7.

Implementation Mode One

The data transmission method in the RRC Inactive state described in some embodiments of the present disclosure can be used to update the radio access network area.

As shown in FIG. 8, specifically, the data transmission method includes the following steps.

S810: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S820: after the user terminal moves to the coverage area of the second node device, the user terminal sends an RRC Resume Request to the second node device; optionally, the RRC Resume Request indicates that the reason for the RRC Resume Request is the radio access network notification area update; therefore, the second node device becomes the current serving node of the user terminal.

S830: the second node device sends the Retrieve UE Context Request message to the first node device, in which the message indicates that the reason for retrieving UE context request is the radio access network notification area update.

S840: the first node device determines that it is not necessary to perform the anchor node change and context transfer procedure, and generates an RRC message with the message name of RRC Release, and the message content instructs the user terminal to maintain the RRC Inactive state; then, the first node device utilize the current PDCP configuration of the user terminal to package this RRC message into one or more PDCP PDUs.

S850: the first node device feeds back an interface message to the second node device, which contains the above-mentioned PDCP PDU.

S860: the second node device directly sends the aforementioned PDCP PDU to the user terminal on the default SRB1, and then releases the air interface resources.

Based on the foregoing implementation mode, when the first node device determines that the anchor node change and context transfer procedure does not need to be performed currently according to the Retrieve UE Context Request message sent by the second node device indicating that the reason is the radio access network notification area update, an RRC message instructing the user terminal to maintain the RRC Inactive state is generated, and the RRC message is packaged into one or more PDCP PDUs, and an interface message including the PDCP PDU is sent to the second node device, and the second node device directly sends a PDCP PDU to the user terminal on the default SRB1, so that the user terminal maintains the RRC Inactive state after receiving the PDCP PDU.

Implementation Mode Two

The data transmission method in the RRC Inactive state described in some embodiments of the present disclosure can be used to transmit the RRC connection release message triggered by the core network.

Specifically, as shown in FIG. 9, the method includes the following step.

S910: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S920: after the user terminal moves to the coverage area of the second node device, the core network sends a message to the radio access network to indicate that the RRC connection of the user terminal needs to be released; currently, the second node device becomes the current serving node of the user terminal, and the first node device can obtain messages sent by the core network.

S930: the first node device initiates a paging procedure, and instructs nodes in a certain area to page the user terminal, and the nodes in the certain area include the second node device.

S940: the second node device pages the user terminal.

S950: after acquiring the paging, the user terminal sends an RRC Resume Request to the second node device, in where the indicated reason is paging.

S960: the second node device sends the Retrieve UE Context Request message to the first node device, in which the indicated reason is paging.

S970: the first node device determines that the anchor node change and context transfer procedure does not need to be performed currently, and an RRC message with the message name of RRCRelease is generated, and the message content instructs the user terminal to release the RRC connection and enter the RRC Idle state; the first node device utilizes the current PDCP configuration of the user terminal to package this RRC message into one or more PDCP PDUs.

S980: the first node device feeds back an interface message to the second node device, the interface message includes the above-mentioned PDCP PDU.

S990: the second node device directly sends the aforementioned PDCP PDU to the user terminal on the default SRB1, and then releases the air interface resources.

After that, the first node device releases the user terminal context at the right timing.

Based on the foregoing implementation mode, when the first node device determines that the anchor node change and context transfer procedure does not need to be performed currently according to the Retrieve UE Context Request message sent by the second node device indicating that the reason is paging, an RRC message instructing the user terminal to release the RRC connection is generated, and the RRC message is packaged into one or more PDCP PDUs, and an interface message including the PDCP PDU is sent to the second node device, and the second node device directly sends a PDCP PDU to the user terminal on the default SRB1, so that the user terminal release the RRC connection after receiving the PDCP PDU.

Implementation Mode Three

In the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, the uplink NAS message can be transmitted through the default SRB1.

Specifically, as shown in FIG. 10, the method includes the following steps.

S1010: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S1020: after the user terminal moves to the coverage area of the second node device, when it needs to send uplink NAS messages and the number of the NAS messages to be sent is small, the user terminal may determine that it does not need to enter the RRC Connected state, and send an RRC Resume Request to the second node device, and the RRC Resume Request includes preset indication information used to indicate that the user terminal needs not to enter the RRC Connected state, that is, the context transfer procedure does not need to be performed.

S1030: the second node device sends the Retrieve UE Context Request message to the first node device, and the message includes the foregoing preset indication information for instructing that the user terminal needs not to enter the RRC Connected state.

S1040: the first node device determines that it is not necessary to perform the anchor node change and context transfer procedure, and an RRC message is generated, the content of the RRC message is to confirm that the user terminal can send the uplink NAS message through the default SRB1 (that is, the RRC message includes instruction indication information for instructing the user terminal to send the uplink RRC message through the default SRB1); in addition, the first node device uses the current PDCP configuration of the user terminal to package the RRC message into one or more PDCP PDUs.

S1050: the first node device feeds back an interface message to the second node device, the interface message includes the above-mentioned PDCP PDU, and instructs the second node device not to release air interface resources for the time being, and prepares to receive uplink PDCP PDUs through the default SRB1; that is, the interface message includes indication information for instructing the second node device to receive an uplink RRC message through SRB1.

S1060: the second node device directly sends the foregoing PDCP PDU to the user terminal.

S1070: the user terminal sends one or more PDCP PDUs to the second node device on the default SRB1, the content of which is one or more RRC messages, the message name is UL InformationTransfer, which includes one or more pieces of Uplink NAS messages to be sent.

S1080: the second node device sends the foregoing PDCP PDU to the first node device through the default SRB1.

S1090: the first node device sends the NAS message in the PDCP PDU to the core network.

S1000: the second node device and the user terminal release air interface resources at the right timing.

Based on the foregoing implementation mode, when a user terminal in an RRC Inactive state needs to send uplink NAS messages and the number of the NAS messages to be sent is small, the user terminal may send an RRC Resume Request including preset indication information to the second node device, to indicate that the context transfer procedure does not need to be performed; and the first node device can generate an RRC message indicating that the user terminal can send uplink NAS messages through the default SRB1 according to the RRC Resume Request, and package the RRC messages into one or more PDCP PDUs, to send an interface message including the PDCP PDUs to the second node device, and instruct the second node device to prepare to receive the uplink PDCP PDU through the default SRB1; after that, the second node device directly sends the PDCP PDU to the user terminal on the default SRB1, and obtains the PDCP PDU to be sent by the user terminal, and transmit the same to the first node device.

Therefore, in the above implementation mode, data is interacted on the node interface among the first node device, the second node device and the user terminal in the form of PDCP PDU, and the uplink NAS message is transmitted through the default SRB1.

Implementation Mode Four

In the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, one RRC message may be used, and the default SRB1 is used to transmit the downlink NAS message.

Specifically, as shown in FIG. 11, the method includes the following steps.

S1110: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S1120: after the user terminal moves to the coverage area of the second node device, the core network sends one or more messages to the radio access network, including one or more NAS messages that should be sent to the user terminal.

S1130: the first node device initiates a paging procedure and instructs nodes in a certain area to page the user terminal, in which the nodes in the certain area include the second node device.

S1140: the second node device pages the user terminal.

S1150: after acquiring the paging, the user terminal sends an RRC Resume Request to the second node device, in which the indicated reason is paging.

S1160: the second node device sends the Retrieve UE Context Request message to the first node device, in which the indicated reason is paging.

S1170: the first node device determines that there is no need to perform the anchor node change and context transfer procedure, and an RRC message with the message name of DLInformationTransfer is generated, the RRC message includes the downlink NAS message to be sent; the first node device packages this RRC message into one or more PDCP PDUs using the current PDCP configuration of the user terminal.

S1180: the first node device feeds back an interface message to the second node device, which contains the above-mentioned PDCP PDU.

S1190: the second node device directly sends the foregoing PDCP PDU to the user terminal on the default SRB1.

S1100: the second node device and the user terminal release air interface resources at the right timing.

Based on the foregoing implementation mode, when the reason of the Retrieve UE Context Request message is paging, and the paging is initiated based on the core network sending a downlink NAS message to the user terminal, the first node device can determine that there is no need to perform anchor node change and context transfer procedure and an RRC message is generated, the RRC message includes a downlink NAS message to be sent to the user terminal, then the RRC message is packaged into one or more PDCP PDUs, and the interface message including the PDCP PDU is sent to the second node device, so that the second node device sends the PDCP PDU to the user terminal through the default SRB1.

Therefore, in the above implementation mode, data is interacted on the node interface among the first node device, the second node device and the user terminal in the form of PDCP PDU, and the downlink NAS message is transmitted through the default SRB1.

Implementation Mode Five

In the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, one or more RRC messages can be used, and the default SRB1 is used to transmit the downlink NAS message.

Specifically, as shown in FIG. 12, the method includes the following steps.

S1210: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S1220: after the user terminal moves to the coverage area of the second node device, the core network sends one or more messages to the radio access network, including one or more NAS messages that should be sent to the user terminal.

S1230: the first node device initiates a paging procedure and instructs nodes in a certain area to page the user terminal, and the nodes in the certain area include the second node device.

S1240: the second node device pages the user terminal.

S1250: after acquired the paging, the user terminal sends an RRC Resume Request to the second node device, in which the indicated reason is paging.

S1260: the second node device sends the Retrieve UE Context Request message to the first node device, in which the indicated reason is paging.

S1270: the first node device determines that there is no need to perform the anchor node change and context transfer procedure, and an RRC message is generated. The content of the RRC message is to confirm that the user terminal continues to receive the downlink NAS message through SRB1 (that is, the RRC message includes instruction indication information for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1); then the first node device uses the current PDCP configuration of the user terminal to package this RRC message into one or more PDCP PDUs.

S1280: the first node device generates one or more RRC messages, the message name is DLInformationTransfer, which includes the downlink NAS message to be sent; the first node device uses the current PDCP configuration of the user terminal to package the RRC message into one or more PDCP PDUs.

S1290: the first node device feeds back an interface message to the second node device, which sequentially includes the PDCP PDUs packaged in step S1270 and step S1280, and the interface message includes instruction indication information for instructing the second node device to continue to send the downlink RRC message through the default SRB1.

S1200: the second node device directly sends the PDCP PDUs packaged in step S1270 sequentially to the user terminal on the default SRB1.

S1201: the second node device directly sends the PDCP PDU packaged in step S1280 sequentially to the user terminal on the default SRB1.

S1202: the second node device and the user terminal release air interface resources at the right timing.

In the above implementation mode, data is interacted on the node interface among the first node device, the second node device and the user terminal in the form of PDCP PDUs, a plurality of RRC messages are used, and the downlink NAS messages is transmitted through the default SRB1.

Implementation Mode Six

In the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, the default SRB2 can be used to transmit the uplink NAS message.

Specifically, as shown in FIG. 13, the method includes the following steps.

S1310: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S1320: after the user terminal moves to the coverage area of the second node device, when it needs to send uplink NAS messages and the number of the NAS messages to be sent is small, the user terminal may determine that it does not need to enter the RRC Connected state, and send an RRC Resume Request to the second node device, and the RRC Resume Request includes preset indication information, which is used to indicate that the user terminal needs not to enter the RRC Connected state, that is, the context transfer procedure does not need to be performed.

S1330: the second node device sends the Retrieve UE Context Request message to the first node device, and the message includes the foregoing preset indication information to instruct the user terminal not to enter the RRC Connected state.

S1340. the first node device determines that the anchor node change and context transfer procedure does not need to be performed currently, and an RRC message is generated. The content of the RRC message is to confirm that the user terminal can send an uplink NAS message through the default SRB2 (that is, the RRC message includes instruction indication information for instructing the user terminal to send the uplink RRC message through the default SRB2); in addition, the first node device uses the current PDCP configuration of the user terminal to package the RRC message into one or more PDCP PDUs.

S1350: the first node device feeds back an interface message to the second node device, which contains the above-mentioned PDCP PDU, and instructs the second node device not to release air interface resources for the time being, and prepares to receive uplink PDCP PDUs through the default SRB2; that is, the interface message includes indication information for instructing the second node device to receive the uplink RRC message through SRB2.

S1360: the second node device directly sends the foregoing PDCP PDU to the user terminal.

S1370: the user terminal sends one or more PDCP PDUs to the second node device on the default SRB2, the content of which is one or more RRC messages, the message name is UL InformationTransfer, which includes one or more Uplink NAS messages to be sent.

S1380: the second node device sends the foregoing PDCP PDU to the first node device through the default SRB1.

S1390: the first node device sends the NAS message in the PDCP PDU to the core network.

S1300: the second node device and the user terminal release air interface resources at the right timing.

In the above implementation mode, data is interacted on the node interface among the first node device, the second node device and the user terminal in the form of PDCP PDU, and the uplink NAS message is transmitted through the default SRB2.

Implementation Mode Seven

In the data transmission method in the RRC Inactive state described in some embodiments of the present disclosure, one or more RRC messages can be used, and the default SRB2 is used to transmit the downlink NAS message.

Specifically, as shown in FIG. 14, the method includes the following steps.

S1410: the first node device in the radio access network sends an RRC Release message to the user terminal, to instruct the user terminal to enter (or maintain) the RRC Inactive state; therefore, the first node device has the user terminal context and becomes the anchor node of the user terminal.

S1420: after the user terminal moves to the coverage area of the second node device, the core network sends one or more messages to the radio access network, including one or more NAS messages that should be sent to the user terminal.

S1430: the first node device initiates a paging procedure and instructs nodes in a certain area to page the user terminal, and the nodes in the certain area include the second node device.

S1440: the second node device pages the user terminal.

S1450: after acquiring the paging, the user terminal sends an RRC Resume Request to the second node device, in which the indicated reason is paging.

S1460: the second node device sends the Retrieve UE Context Request message to the first node device, in which the indicated reason is paging.

S1470: the first node device determines that there is no need to perform the anchor node change and context transfer procedure, and an RRC message is generated. The content of the message is to confirm that the user terminal continues to receive the downlink NAS message through SRB2 (that is, the RRC message includes instruction indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2); then the first node device uses the current PDCP configuration of the user terminal to package this RRC message into one or more PDCP PDUs.

S1480: the first node device generates one or more RRC messages, the message name is DLInformationTransfer, which contains the downlink NAS message to be sent; the first node device uses the current PDCP configuration of the user terminal to package the RRC message into one or Multiple PDCP PDUs.

S1490: the first node device feeds back an interface message to the second node device, which includes the PDCP PDUs packaged in step S1470 and step S1480 sequentially, and the interface message includes instruction indication information for instructing the second node device to send downlink RRC message through the default SRB2.

S1400: the second node device directly sends the PDCP PDU packaged in step S1470 sequentially to the user terminal on the default SRB2.

S1401: the second node device directly sends the PDCP PDU packaged in step S1480 sequentially to the user terminal on the default SRB2.

S1402: the second node device and the user terminal release air interface resources at the right timing.

FIG. 15 is a schematic structural diagram of a node device according to one embodiment of the present disclosure. The node device may be a first node device and includes: a processor 1500, a memory 1520 connected to the processor 1500 through a bus interface 1530, and a transceiver 1510 connected to the processor 1500 through a bus interface. The memory 1520 is used to store programs and data used by the processor when performing operations; and data information or pilots are sent through the transceiver 1510, the uplink control channel is also received through the transceiver 1510. When the processor 1500 calls and executes the programs and data stored in the memory 1520, the following functions are realized.

If a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, an interface message including at least one PDCP PDU is sent to the second node device. The second node device is a current serving node of a user terminal in an RRC Inactive state, and the first node device is an anchor node of the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, the interface message includes at least one of the following indication information: indication information for instructing the second node device to receive the uplink RRC message through the default SRB1; indication information for instructing the second node device to continue to send the downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through the default SRB2; and indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

Optionally, the processor 1500 sends an interface message to the second node device through a Retrieve UE Context Response message, or sends the interface message to the second node device through a Retrieve UE Context Failure message.

Optionally, the processor 1500 is further configured to, when obtaining the Retrieve UE Context Request message sent by the second node device and determining that the Retrieve UE Context Request message includes preset indication information, determine not to perform context transfer procedure. The preset indication information is used to indicate that the context transfer procedure does not need to be performed.

In addition, in FIG. 15, the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1500 and the memory represented by the memory 1520 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein. The bus interface provides the interface. The transceiver 1510 may be a plurality of elements, which include a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium. The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 can store data used by the processor 1500 to perform operations.

Those skilled in the art can understand that all or part of the steps in the above-mentioned embodiments can be implemented by hardware, or by a computer program to instruct relevant hardware. The computer program includes instructions for performing part or all of the steps of the above-mentioned method; and the computer program can be stored in a readable storage medium, which can be any form of storage medium.

FIG. 16 is a schematic structural diagram of a node device according to another embodiment of the present disclosure. The node device may be a second node device and includes: a processor 1600; a memory 1620 connected to the processor 1600 through a bus interface 1630, and a transceiver 1610 connected to the processor 1600 through a bus interface; the memory 1620 is used to store programs and data used by the processor to perform operations; data information or pilots are sent through the transceiver 1610, the uplink control channel is also received through the transceiver 1610; when the processor 1600 calls and executes the programs and data stored in the memory 1620, the following functions are realized.

After sending the Retrieve UE Context Request message to the first node device according to an RRC Resume Request sent by the user terminal in the RRC Inactive state, the interface message sent by the first node device according to the Retrieve UE Context Request message is received. The interface message includes at least one PDCP PDU; the first node device is the anchor node of the user terminal, and the second node device is the current serving node of the user terminal.

Optionally, the processor 1600 is further configured to: send the PDCP PDU to the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive downlink RRC messages through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, the interface message received in step S410 further includes at least one of the following indication information: indication information for instructing the second node device to receive the uplink RRC message through the default SRB1; indication information for instructing the second node device to continue to send the downlink RRC message through the default SRB1; indication information for instructing the second node device to receive the uplink RRC message through the default SRB2; and indication information for instructing the second node device to send the downlink RRC message through the default SRB2.

When the interface message includes an indication message for instructing the second node device to continue to send downlink RRC messages through the default SRB1, the processor 1600 is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB1.

When the interface message includes an indication message for instructing the second node device to receive the uplink RRC message through the default SRB2, the processor 1600 is further configured to: receive the PDCP PDU sent by the user terminal through the default SRB2 and including the uplink RRC message to be sent; send the PDCP PDU sent by the user terminal to the first node device.

When the interface message includes an indication message for instructing the second node device to send a downlink RRC message through the default SRB2, the processor 1600 is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal to the user terminal through the default SRB2.

Optionally, the processor 1600 is further configured to: receive an RRC Resume Request sent by the user terminal, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that a context transfer procedure does not need to be performed; and send the Retrieve UE Context Request message to the first node device, in which the Retrieve UE Context Response message includes the preset indication information.

In addition, in FIG. 16, the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1600 and the memory represented by the memory 1620 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein. The bus interface provides the interface. The transceiver 1610 may be a plurality of elements, which include a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium. The processor 1600 is responsible for managing the bus architecture and general processing, and the memory 1620 can store data used by the processor 1600 to perform operations.

FIG. 17 is a schematic structural diagram of a user terminal according to some embodiments of the present disclosure. The user terminal includes a processor 1701, a memory 1703 connected to the processor 1701 through a bus interface 1702, and a transceiver 1704 connected to the bus interface 1702. The memory 1703 is used to store programs and data used by the processor 1701 to perform operations, the transceiver 1704 is used to receive and send data under the control of the processor 1701, and the processor 1701 calls and executes the programs and data stored in the memory 1703 to perform the following procedure.

When the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to the second node device, the RRC message sent by the second node device is received.

The second node device is the current serving node of the user terminal, and the anchor node of the user terminal is a first node device different from the second node device.

Optionally, when the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB1, the processor 1701 is further configured to send the uplink RRC message to the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1, the processor 1701 is further configured to continue to receive the downlink RRC message from the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB2, the processor 1701 is further configured to send the uplink RRC message to be sent to the second node device through the default SRB2.

When the RRC message includes an indication message for instructing the user terminal to receive the downlink RRC message through the default SRB2, the processor 1701 is further configured to receive a downlink RRC message from the second node device through the default SRB2.

Optionally, the processor 1701 is further configured to when initiating the RRC connection resumption, send the RRC Resume Request to the second node device, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that the context transfer procedure does not need to be performed.

It should be noted that in FIG. 17, the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1701 and the memory represented by the memory 1703 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein. The bus interface provides the interface. The transceiver 1704 may be a plurality of elements, which include a transmitter and a transceiver, provide a unit for communicating with various other devices on the transmission medium. For different user terminals, the user interface 1705 may also be an interface capable of connecting externally and internally with required device. The connected device includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc. The processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1703 can store data used by the processor 1701 to perform operations.

Further, some embodiments of the present disclosure also provide a data transmission device in an RRC Inactive state, which is applied to a first node device. As shown in FIG. 18, the device includes a sending module 1810, configured to, when a Retrieve UE Context Request message is received from a second node device, in respond to the Retrieve UE Context Request message, send an interface message including at least one PDCP PDU to the second node device. The second node device is a current serving node of a user terminal in an RRC Inactive state, and the first node device is an anchor node of the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive a downlink RRC message through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, in the step of sending the interface message including at least one PDCP PDU to the second node device, an interface message is sent to the second node device through a Retrieve UE Context Response message, or the interface message is sent to the second node device through a Retrieve UE Context Failure message.

Optionally, the data transmission device further includes a processing module 1820, configured to, when obtaining the Retrieve UE Context Request message sent by the second node device and determining that the Retrieve UE Context Request message includes preset indication information, determine not to perform context transfer procedure. The preset indication information is used to indicate that the context transfer procedure does not need to be performed.

Further, a data transmission device in the RRC Inactive state according another embodiment of the present disclosure is applied to a second node device. As shown in FIG. 19, the device includes: a data transmission module 1910, configured to, after sending the Retrieve UE Context Request message to the first node device according to an RRC Resume Request sent by the user terminal in the RRC Inactive state, receive the interface message sent by the first node device according to the Retrieve UE Context Request message. The interface message includes at least one PDCP PDU; the first node device is the anchor node of the user terminal, and the second node device is the current serving node of the user terminal.

Optionally, the data transmission module 1910 is further configured to: send the PDCP PDU to the user terminal.

Optionally, the PDCP PDU includes an RRC message sent to the user terminal.

Optionally, the RRC message includes at least one of the following indication information: indication information for instructing the user terminal to send an uplink RRC message through the default first signaling radio bearer SRB1; indication information for instructing the user terminal to continue to receive downlink RRC messages through the default SRB1; indication information for instructing the user terminal to send an uplink RRC message through the default second signaling radio bearer SRB2; and indication information for instructing the user terminal to receive the downlink RRC message through the default SRB2.

Optionally, when the interface message includes an indication message for instructing the second node device to receive an uplink RRC message through the default SRB1, the data transmission module 1910 is further configured to: receive the PDCP PDU sent by the user terminal through the default SRB1 and including the uplink RRC message to be sent; send the PDCP PDU sent by the user terminal to the first node device.

When the interface message includes an indication message for instructing the second node device to continue to send downlink RRC messages through the default SRB1, the data transmission module 1910 is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal through the default SRB1.

When the interface message includes an indication message for instructing the second node device to receive the uplink RRC message through the default SRB2, the data transmission module 1910 is further configured to: receive the PDCP PDU sent by the user terminal through the default SRB2 and including the uplink RRC message to be sent; send the PDCP PDU sent by the user terminal to the first node device.

When the interface message includes an indication message for instructing the second node device to send a downlink RRC message through the default SRB2, the data transmission module 1910 is further configured to: send the PDCP PDU including the downlink RRC message to be sent to the user terminal to the user terminal through the default SRB2.

Optionally, the data transmission module 1910 is further configured to receive an RRC Resume Request sent by the user terminal, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that a context transfer procedure does not need to be performed; and send the Retrieve UE Context Request message to the first node device, in which the Retrieve UE Context Response message includes the preset indication information.

Further, a data transmission device in the RRC Inactive state according to another embodiment of the present disclosure is applied to a user terminal. As shown in FIG. 20, the device includes: a transceiver module 2010, configured to, when the user terminal is in the RRC Inactive state, after sending an RRC Resume Request to the second node device, receive the RRC message sent by the second node device.

The second node device is the current serving node of the user terminal, and the anchor node of the user terminal is a first node device different from the second node device.

Optionally, when the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB1, the transceiver module 2010 is further configured to send the uplink RRC message to the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to continue to receive the downlink RRC message through the default SRB1, the transceiver module 2010 is further configured to continue to receive the downlink RRC message from the second node device through the default SRB1.

When the RRC message includes an indication message for instructing the user terminal to send an uplink RRC message through the default SRB2, the transceiver module 2010 is further configured to send the uplink RRC message to be sent to the second node device through the default SRB2.

When the RRC message includes an indication message for instructing the user terminal to receive the downlink RRC message through the default SRB2, the transceiver module 2010 is further configured to receive a downlink RRC message from the second node device through the default SRB2.

Optionally, the transceiver module 2010 is further configured to when initiating the RRC connection resumption, send the RRC Resume Request to the second node device, in which the RRC Resume Request includes preset indication information; the preset indication information is used to indicate that the context transfer procedure does not need to be performed.

Some embodiments of the present disclosure also provide a computer-readable storage medium storing a computer program on the computer-readable storage medium, and when the computer program is executed by a processor, the data transmission method in the RRC Inactive state as described above is realized and the same technical effect is achieved. In order to avoid repetition, it will not be repeated here. The computer-readable storage medium may be such as read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc.

The computer-readable storage medium of the present disclosure may be a volatile computer-readable storage medium or a non-volatile computer-readable storage medium.

It should be noted that in this disclosure, the terms “include”, “comprise” or any other variants thereof are intended to cover non-exclusive inclusion, so that a procedure, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or elements inherent to the procedure, method, article, or device. Without more restrictions, the element defined by the sentence “including a . . . ” does not exclude the existence of other identical elements in the procedure, method, article or device that includes the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. Based on this understanding, the technical solution of the present disclosure essentially or the part that contributes to the related technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes several instructions to make a user terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) execute the methods described in the various embodiments of the present disclosure.

The embodiments of the present disclosure are described above with reference to the accompanying drawings, but the present disclosure is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art may made many forms without departing from the purpose of the present disclosure and the scope of protection of the claims, all of which fall within the protection of the present disclosure.

The above are optional implementations of the present disclosure. It should be note that for those of ordinary skill in the art, without departing from the principles described in the present disclosure, several improvements and modifications can be made. These improvements and modifications should also be within the protection scope of this disclosure

DATA TRANSMISSION METHOD AND DEVICE IN RRC INACTIVE STATE, TERMINAL AND NETWORK SIDE DEVICE

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

Priority Claims (1)

PCT Information