CN116709587A

CN116709587A - Method for transmitting data, terminal device and network device

Info

Publication number: CN116709587A
Application number: CN202310637993.2A
Authority: CN
Inventors: 娄崇; 徐小英; 黄曲芳; 曾清海
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-07-31
Filing date: 2019-07-31
Publication date: 2023-09-05
Also published as: CN112312588A; CN112312588B

Abstract

The application provides a method for transmitting data, a terminal device and a network device.

Description

Method for transmitting data, terminal device and network device

The present application is a divisional application, the application number of the original application is 201910702662.6, the original application date is 31 of 2019, 07, and the whole content of the original application is incorporated by reference.

Technical Field

The present application relates to the field of communications, and more particularly, to a method, a terminal device and a network device for transmitting data.

Background

In existing wireless communication systems, a plurality of communication states are defined for terminal devices. For example, if the terminal device establishes a communication connection with the network device, the terminal device is defined to be in a connected (connected) state; if the terminal device is in a standby state, the terminal device is defined to be in an idle state. In addition, an inactive (inactive) state is defined in the 5G communication system, in which the terminal device may retain some context information of the communication connection with the network device. Wherein in the connected state, the terminal device may be capable of continuous communication with the network device. In either the idle state or the inactive state, the terminal device is in a power saving state.

When the terminal device is switched from the connected state to the inactive state, there is a possibility that there is data pending in the packet data convergence layer protocol (packet data convergence protocol, PDCP) layer of the terminal device. The terminal device continues to save the suspended data since it can be given these data transmission opportunities again when it resumes the connected state. However, if the terminal device does not enter the connected state for a long time or the data does not obtain a transmission opportunity for a long time, the suspended data may fail due to too long stay time in the buffer of the terminal device, so that the data packet is lost in the state transition process of the terminal device.

Disclosure of Invention

The application provides a method for transmitting data, a terminal device and a network device, which can reduce the probability of losing a data packet in the state transition process of the terminal device.

In a first aspect, the present application provides a method for transmitting data, the method comprising: when suspended data exist, the terminal equipment sends a first message to the network equipment, wherein the terminal equipment is in an inactive state, the first message is used for requesting to recover Radio Resource Control (RRC) connection and indicating to the network equipment that the terminal equipment has data to send, and the suspended data are data stored in a PDCP layer of the terminal equipment; and the terminal equipment receives a second message sent by the network equipment, wherein the second message is used for indicating the terminal equipment to restore the RRC connection.

In the above technical solution, when the terminal device has suspended data, the terminal device sends a first message to the network device, requests to recover the RRC connection, and informs the network device that there is data to send, so that the network device performs scheduling, thereby reducing the probability of failure of the suspended data due to excessively long residence time, and further reducing the probability of losing the data packet in the state transition process of the terminal device.

In one possible implementation, the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to suspend.

Optionally, the suspension data is data stored in the PDCP layer during the process that the terminal device enters an inactive state. The data may be, for example, SDUs or PDUs of the PDCP layer.

Optionally, the suspension data is data stored by the PDCP layer and not receiving an acknowledgement ACK message in the process that the terminal device enters the inactive state, and likewise, the data may be an SDU or PDU of the PDCP layer.

It will be appreciated that in case there is also a suspension operation in the medium access control MAC layer or the radio link control RLC layer, the suspension data also includes data held in the MAC layer or the RLC layer of the terminal device.

In one possible implementation, before the terminal device sends the first message, the method further includes: the terminal equipment determines that a triggering condition is met, wherein the triggering condition is at least one of the following conditions: the data quantity of the suspended data is larger than a preset threshold value; the presence of the suspension data by the network device designated at least one radio bearer RB, the network device designated at least one logical channel, or the network device designated at least one logical channel group; a first timer is overtime, and the first timer is started after the terminal equipment enters an inactive state; receiving a paging message; requiring execution of a radio access network notification area update, RNAU; the terminal device sends a first message to the network device when the suspended data exists, and the first message comprises: and when the terminal equipment meets the triggering condition, the terminal equipment sends the first message to the network equipment.

Alternatively, the preset threshold value may be agreed upon by the terminal device and the network device without transmission, for example, embodied in a protocol. That is, the threshold value may not be configured by the network device through a configuration message.

Alternatively, the preset threshold value may be configured by the network device, for example, the threshold value is configured by the network device through a configuration message.

Alternatively, the at least one RB, the at least one logical channel, or the at least one logical channel group may be agreed by the terminal device and the network device without requiring configuration of the network device. For example, embodied in a protocol.

Alternatively, the first timer may be agreed upon by the terminal device and the network device without requiring configuration by the network device. For example, embodied in a protocol.

It is to be appreciated that the RB can be either a data radio bearer DRB or a signaling radio bearer SRB, which is not limited by the present application.

In the above technical solution, when the data amount of the suspended data is greater than the threshold value, the terminal device sends the first message, so that the terminal device can be prevented from frequently requesting to enter the connection state, and signaling overhead is reduced. When there is pending data in the designated RB or the designated logical channel, the terminal device transmits the first message, which can improve flexibility of data transmission. Because the service network equipment of the terminal equipment may change, the new service network equipment cannot realize that suspended data exists in the terminal equipment, and when a paging message is received or RNAU is executed, the new service network equipment cannot give a transmission opportunity of the suspended data in time, and the first message in the technical scheme of the application can indicate that the terminal equipment has data to send while requesting to restore RRC connection, so that the probability of failure of the suspended data of the terminal equipment due to long-time stay can be reduced.

In one possible implementation, the first message includes a first cell, where the first cell is used to indicate that the terminal device has data to send.

It will be appreciated that the first cell may be a newly added cell or may be a multiplexed existing cell.

In one possible implementation, the first message is an RRC connection resume request message, and a resume reason cell in the RRC connection resume request message indicates that the terminal device has data to send.

It may be understood that the recovery cause cell may use an existing cause value to indicate that the terminal device has data to send, or may add a cause value to indicate that the terminal device has data to send from the suspended data, which is not limited in the embodiment of the present application.

In the above technical solution, when there is suspended data, the terminal device sends an RRC connection recovery request message, and indicates, through a recovery reason cell of the RRC connection recovery request message, that the terminal device has data to send, that is, the RRC connection recovery request is triggered by the suspended data, so that the probability that the suspended data fails due to excessively long residence time can be reduced, and further the probability that a data packet is lost in the state transition process of the terminal device can be reduced.

In one possible implementation manner, the first message includes an RRC connection restoration request message and a buffer status report BSR, where the RRC connection restoration request message is used to request restoration of an RRC connection, and the BSR is used to indicate that the terminal device has data to send; or, the first message includes an RRC connection restoration request message and a medium access control element MAC CE, where the RRC connection restoration request message is used to request restoration of an RRC connection, and the MAC CE is used to indicate that the suspension data exists in the terminal device.

It can be appreciated that the MAC CEs in the above technical solutions may be preconfigured.

In one possible implementation manner, after the terminal device receives the second message sent by the network device, the method further includes: the terminal device switches from an inactive state to a connected state.

In a second aspect, the present application provides a method for transmitting data, the method comprising: the network equipment receives a first message sent by the terminal equipment, wherein the first message is used for requesting to recover Radio Resource Control (RRC) connection and indicating to the network equipment that the terminal equipment has data to send, the terminal equipment stores suspension data, and the suspension data is data stored in a PDCP layer of the terminal equipment; and the network equipment sends a second message to the terminal equipment, wherein the second message is used for indicating the terminal equipment to restore the RRC connection.

In one possible implementation, before the network device receives the first message sent by the terminal device, the method further includes: the network device sends configuration information to the terminal device, wherein the configuration information is used for: configuring a threshold value, wherein the threshold value indicates the minimum data quantity of the suspended data triggering the terminal equipment to send the first message; and/or designating at least one radio bearer RB, at least one logical channel, or at least one logical channel group; and/or configuring a first timer, wherein the first timer is started after the terminal equipment enters an inactive state, and the first message is sent after the first timer is overtime.

In the above technical solution, the network device configures the threshold value, so that the terminal device sends the first message when the data amount of the suspended data is greater than the threshold value, thereby avoiding frequent requests of the terminal device to enter the connection state and reducing signaling overhead. The network device designates an RB or a logical channel so that the terminal device transmits the first message when the designated RB or the designated logical channel group has pending data, and thus flexibility of data transmission can be improved.

In a third aspect, the present application provides a method for transmitting data, the method comprising: the terminal equipment receives a third message sent by the network equipment, wherein the third message is used for indicating the terminal equipment to release Radio Resource Control (RRC) connection; the terminal device sends a fourth message to the network device, where the fourth message is used to instruct the terminal device to prepare to release the RRC connection with the network device.

In the above technical solution, before entering the inactive state, the terminal device actively feeds back to the network device that the terminal device is ready to release the RRC connection, instead of entering the inactive state after receiving the third message, so that the terminal device may enter the inactive state only when the terminal device is ready to enter the inactive state (for example, when no data is suspended), thereby reducing the probability of losing the data packet during the state transition of the terminal device.

In one possible implementation manner, after the terminal device receives the third message sent by the network device, the method further includes: and the terminal equipment sends a fifth message to the network equipment when the suspended data exists, wherein the suspended data is the data stored in the PDCP layer of the terminal equipment, and the fifth message is used for indicating that the terminal equipment has data to be sent.

In the above technical solution, before the terminal device enters the inactive state, the suspended data check is added, so that before the terminal device enters the inactive state, the opportunity for transmitting the suspended data is given, thereby reducing the probability of failure of the suspended data due to overlong residence time, and further reducing the probability of losing the data packet in the state transition process of the terminal device.

Compared with the method that the terminal equipment gives the opportunity to suspend data transmission after entering the inactive state, the technical scheme can finish at least partial transmission of the suspend data in advance, reduce the residence time of the suspend data, and further reduce the probability of losing data packets in the state transition process of the terminal equipment.

In one possible implementation, the method further includes: the terminal device releases an RRC connection with the network device.

In one possible implementation, the terminal device releases the RRC connection with the network device, including: and after the suspended data is sent, the terminal equipment releases the RRC connection with the network equipment.

In the above technical solution, the terminal device enters the inactive state or the idle state after the completion of the suspended data transmission. That is, the terminal device does not enter the inactive state or the idle state until the suspended data of the terminal device is transmitted, so that the probability of losing the data packet in the state transition of the terminal device can be reduced.

In one possible implementation manner, the sending, by the terminal device, a fourth message to the network device includes: and after the suspended data is sent, the terminal equipment sends the fourth message to the network equipment.

In one possible implementation, the terminal device releases the RRC connection with the network device, including: and when the second timer expires, the terminal equipment releases the RRC connection with the network equipment.

In the above technical solution, the network device and the terminal device can release the RRC connection after reaching the agreed time by setting a period of time to send the suspension data, so that signaling interaction between the terminal device and the network device can be reduced.

In a possible implementation manner, the second timer is started after the terminal device receives the third message; or, the second timer is started after the terminal device sends an acknowledgement ACK message for the third message to the network device.

In a possible implementation manner, the timeout of the second timer is after the end of a preset time period, where the preset time period starts when the terminal device receives the third message; or, the timeout time of the second timer is after the terminal device sends an acknowledgement ACK message for the third message to the network device.

In one possible implementation, the fifth message includes a buffer status report BSR.

It will be appreciated that the terminal device may trigger the BSR to be sent when the third message is received, or may trigger the BSR to be sent when there is pending data and the third message is received.

In a possible implementation manner, the fourth message includes an RRC connection release complete message and an RRC connection release confirm message.

In a fourth aspect, the present application provides a method for transmitting data, the method comprising:

the network equipment sends a third message to the terminal equipment, wherein the third message is used for indicating the terminal equipment to release Radio Resource Control (RRC) connection; the network device receives a fourth message sent by the terminal device, where the fourth message is used to indicate that the terminal device is ready to release the RRC connection with the network device.

In one possible implementation, after the network device sends the third message to the terminal device, the method further includes: the network device receives a fifth message sent by the terminal device, the terminal device stores suspension data, the suspension data is data stored in a PDCP layer of the terminal device, and the fifth message is used for indicating that the terminal device has data to be sent.

In one possible implementation, the indication message is indicated by a buffer status report BSR.

In a fifth aspect, the present application provides a terminal device, comprising means for performing the first aspect or any implementation manner of the first aspect.

In a sixth aspect, the application provides a network device comprising means for performing the second aspect or any implementation of the second aspect.

In a seventh aspect, the present application provides a terminal device, comprising means for performing the third aspect or any implementation of the third aspect.

In an eighth aspect, the present application provides a network device comprising means for performing the fourth aspect or any implementation of the fourth aspect.

In a ninth aspect, the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, so as to implement the method in the first aspect or any implementation manner of the first aspect.

In a tenth aspect, the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, so as to implement the method in the second aspect or any implementation manner of the second aspect.

In an eleventh aspect, the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, so as to implement the method in the third aspect or any implementation manner of the third aspect.

In a twelfth aspect, the present application provides a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, so as to implement the method according to any one of the implementation manners of the fourth aspect or the fourth aspect.

In a thirteenth aspect, the present application provides a terminal device, including a transceiver, a processor and a memory, configured to perform the method according to the first aspect or any implementation manner of the first aspect.

In a fourteenth aspect, the present application provides a network device comprising a transceiver, a processor and a memory for performing the method of the second aspect or any implementation of the second aspect.

In a fifteenth aspect, the present application provides a terminal device comprising a transceiver, a processor and a memory for performing the method of the third aspect or any implementation of the third aspect.

In a sixteenth aspect, the present application provides a network device comprising a transceiver, a processor and a memory for performing the method of the fourth aspect or any implementation of the fourth aspect.

In a seventeenth aspect, the present application provides a computer readable storage medium comprising instructions which, when run on a terminal device, cause the terminal device to perform the method of the first aspect or any implementation of the first aspect.

In an eighteenth aspect, the present application provides a computer readable storage medium comprising instructions which, when run on a network device, cause the network device to perform the method of the second aspect or any implementation of the second aspect.

In a nineteenth aspect, the present application provides a computer readable storage medium comprising instructions which, when run on a terminal device, cause the terminal device to perform the method according to the third aspect or any implementation of the third aspect.

In a twentieth aspect, the present application provides a computer readable storage medium comprising instructions that when run on a network device cause the network device to perform the method of the fourth aspect or any implementation of the fourth aspect.

In a twenty-first aspect, the present application provides a computer program product which, when run on a terminal device, causes the terminal device to perform the method of the first aspect or any implementation of the first aspect.

In a twenty-second aspect, the present application provides a computer program product which, when run on a network device, causes the network device to perform the method of the second aspect or any implementation of the second aspect.

In a twenty-third aspect, the present application provides a computer program product which, when run on a terminal device, causes the terminal device to perform the method of the third aspect or any implementation of the third aspect.

In a twenty-fourth aspect, the present application provides a computer program product which, when run on a network device, causes the network device to perform the method of the fourth aspect or any implementation of the fourth aspect.

In a twenty-fifth aspect, the present application provides a communication system, which includes the terminal device according to the fifth aspect and the network device according to the sixth aspect, or the terminal device according to the seventh aspect and the network device according to the eighth aspect, or the terminal device according to the ninth aspect and the network device according to the tenth aspect, or the terminal device according to the eleventh aspect and the network device according to the twelfth aspect.

The network device or the terminal device may also be other communication devices or integrated circuit (integrated circuit, IC) chips or the like capable of realizing similar functions.

Drawings

Fig. 1 is a schematic architecture diagram of a wireless communication system to which embodiments of the present application may be applied.

Fig. 2 is a schematic flow chart of a terminal device switching from a connected state to an inactive state.

Fig. 3 is a schematic flow chart of a terminal device switching from an inactive state to a connected state.

Fig. 4 is a schematic flow chart of a method for transmitting data according to an embodiment of the present application.

Fig. 5 is a MAC CE provided in an embodiment of the present application.

Fig. 6 is a schematic diagram of a MAC layer sub-header according to an embodiment of the present application.

Fig. 7 is a schematic flow chart diagram of a method for transmitting data in accordance with another embodiment of the present application.

Fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

Fig. 9 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a terminal device according to another embodiment of the present application.

Fig. 11 is a schematic block diagram of a network device according to another embodiment of the present application.

Fig. 12 is a schematic block diagram of a terminal device according to another embodiment of the present application.

Fig. 13 is a schematic block diagram of a network device according to another embodiment of the present application.

Fig. 14 is a schematic block diagram of a terminal device according to another embodiment of the present application.

Fig. 15 is a schematic block diagram of a network device according to another embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (global system for mobile communications, GSM), code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, future fifth generation (5th generation,5G) system, or New Radio (NR), etc. It can be appreciated that the technical solution of the embodiment of the present application may be applied to a communication system used in an licensed band, for example, LTE, 5G, NR, etc., and may also be applied to LTE, 5G, NR, etc. used in an unlicensed band, for example, licensed spectrum assisted access (licensed assisted access, LAA) or NR-based unlicensed carrier access (NR-based access to unlicensed spectrum).

Fig. 1 is a schematic architecture diagram of a wireless communication system to which embodiments of the present application may be applied. As shown in fig. 1, the wireless communication system 100 may include a network device 120 and at least one terminal device (e.g., terminal device 130 of fig. 1). The terminal device 130 is connected to the network device 120 by wireless means. The terminal device may be fixed in position or may be movable. Fig. 1 is only a schematic diagram, and other network devices may be further included in the communication system, for example, a wireless relay device and a wireless backhaul device may also be included, which are not shown in fig. 1. The embodiment of the present application does not limit the number of network devices and terminal devices included in the mobile communication system.

In the wireless communication system 100, the terminal device 130 may also be referred to as a terminal, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), or the like. The terminal device in the embodiment of the application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, or a wireless terminal applied to Virtual Reality (VR), augmented reality (augmented reality, AR), industrial control (industrial control), unmanned driving (self driving), remote medical (remote medical), smart grid (smart grid), transportation security (transportation safety), smart city (smart home), smart home (smart home) and other scenes. The terminal device and the chip applicable to the terminal device are collectively called as a terminal device in the present application. It should be understood that the embodiment of the present application does not limit the specific technology and the specific device configuration adopted by the terminal device.

In the wireless communication system 100, the network device 120 may be a device for communicating with a terminal device, and the network device 120 may be any device having a wireless transceiving function. The apparatus includes, but is not limited to: an evolved node B (eNB), a radio network controller (radio network controller, RNC), a Node B (NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved nodeB, or home node B, HNB), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (wireless fidelity, WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, e.g., NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network node constituting a gNB or transmission point, e.g., a baseband unit (BBU), or a Distributed Unit (DU), etc. In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a Core Network (CN), which the present application is not limited to. It should be understood that, in the present application, the network device may refer to the network device itself, or may be a chip applied to the network device to perform a wireless communication processing function.

Taking the 5G communication system as an example, in 5G, the terminal device 130 may be in different states. For example, a radio resource control CONNECTED state (rrc_connected) in which the terminal device 130 has established an RRC context, i.e. the terminal device 130 has established an RRC connection, i.e. parameters necessary for communication between the terminal device 130 and the network device 120 are known to both, the rrc_connected state being mainly used for data transmission by the terminal device 130, hereinafter referred to as CONNECTED state. For another example, the radio resource control IDLE state (rrc_idle) is a state in which the terminal device 130 is in a standby state, hereinafter referred to as IDLE state.

In addition, a radio resource control INACTIVE state (rrc_inactive), also called a third state, hereinafter referred to as an INACTIVE state, is also defined in the 5G communication system. The inactive state is similar to the idle state in that the terminal device 130 can only receive the content of the common search space, e.g. receive paging messages, broadcast messages, etc., but can also perform measurements and cell reselection. The difference between the two is that the terminal device in the inactive state needs to receive the core network page and the radio access network page at the same time, and when the terminal device moves to a new radio access network notification area (radio access network based notification area, RNA), the new service network device may need to acquire the context information of the terminal device from the previous service network device, so that the radio access network notification area update (RNAU) needs to be initiated to perform the context information moving process.

When the terminal device 130 needs to enter the connected state from the inactive state, the current serving network device may directly resume the currently suspended (suspended) RRC connection, communicating with the terminal device 130 using the acquired context information of the terminal device 130, wherein resuming the currently suspended RRC connection includes resuming the suspended signaling radio bearer (signaling radio bearer, SRB) and the data radio bearer (data radio bearer, DRB). Thus, the signaling overhead of the complex SRB, DRB, etc. configuration can be omitted, and the service of the terminal device 130 can be recovered more quickly.

The terminal device 130 may transition between a connected state, an inactive state, and an idle state.

Taking the transition of the terminal device 130 from the connected state to the inactive state as an example, as shown in fig. 2, the network device 120 notifies the terminal device 130 to enter the inactive state by carrying a suspend configuration (suspend) in the RRC connection release message. Wherein, the suspension configuration can carry an inactive radio network temporary identifier (inactive radio network temporary identity, I-RNTI) for identifying suspended context information of the terminal device in an inactive state; radio access network notification area information (RAN-notification wireless info), radio network paging cycle, T380 timer, etc., for the terminal device 130 to perform the procedure of paging, RNAU, etc. in the inactive state.

Taking the transition of the terminal device 130 from the inactive state to the connected state as an example, as shown in fig. 3, the terminal device 130 requests to resume the suspended RRC connection by sending an RRC connection resume request or an RRC connection resume request 1 to the network device 310, including resuming SRBs, DRBs, and the like; after receiving the RRC connection restoration request or the RRC connection restoration request 1, the network device 310 sends an RRC connection restoration message to the terminal device 130, instructing the terminal device 130 to restore the suspended RRC connection; after the RRC connection recovery, the terminal device 130 transmits an RRC connection recovery complete message to the network device. Wherein network device 310 may be the same as network device 120 or different from network device.

For the terminal device 130 to enter the inactive state from the connected state, 5G introduces the PDCP layer suspending operation. When the terminal device 130 enters the inactive state from the connected state, the terminal device 130 may continue to save data that has arrived at the PDCP layer, rather than directly discard it, since these data transmission opportunities may be re-granted when the terminal device 130 resumes the connected state. In this way, the loss of data packets during the state transition of the terminal device 130 can be avoided to a certain extent.

However, in the actual processing, the terminal device 130 may not enter the connected state for a long time or the data may not obtain a transmission opportunity for a long time, which results in that the data may fail due to too long residence time in the buffer memory of the terminal device, so that the terminal device 130 loses the data packet in the state transition process.

In view of the above problems, the present application provides a method for transmitting data, which can reduce the probability of a terminal device losing a data packet during a state transition process.

Fig. 4 is a schematic flow chart of a method for transmitting data according to an embodiment of the present application. The method of fig. 4 may be used for the terminal device 130 and the network device 120 in the wireless communication system shown in fig. 1. In the embodiment of the present application, the terminal device 130 and the network device 120 are described as an execution body, and it should be understood that the execution body may be a chip applied to the terminal device and a chip applied to the network device, and the embodiment of the present application is not limited specifically. The method in fig. 4 includes at least part of the following.

In 410, the terminal device sends a first message to the network device when there is pending data, and the network device receives the first message sent by the terminal device. Wherein the terminal device is in an inactive state at this time.

The suspension data is data stored in the PDCP layer of the terminal device when the RRC layer of the terminal device requests the PDCP layer to suspend. The suspended data is data that has arrived at the PDCP layer when the terminal device enters an inactive state, but has not transmitted or has not received a transmission success Acknowledgement (ACK), unlike the data that the application layer newly arrived. As an example, the suspension data is a service data unit (service data unit, SDU) or a protocol data unit (protocol data unit, PDU) stored in the PDCP layer of the terminal device when the terminal device enters an inactive state. As another example, the pending data is SDUs or PDUs which have not yet received a successful acknowledgement ACK message, which are stored by the PDCP layer of the terminal device, when the terminal device enters an inactive state.

It will be appreciated that in the case where there is also a suspension operation in the MAC layer or RLC layer, the suspension data also includes data held in the MAC layer or RLC layer of the terminal device when the terminal device enters an inactive state.

There are many cases where the terminal device sends the first message, and embodiments of the present application are not specifically limited.

As an example, when the terminal device has the above-mentioned suspended data, the terminal device may actively transmit a first message to request to resume the RRC connection and inform the network device that there is data to transmit. That is, when there is pending data, the terminal device may be triggered to initiate an RRC connection recovery procedure without waiting for new data to arrive at the application layer, receiving a paging message, or performing RNAU.

As another example, when the terminal device receives the paging message or performs the RNAU, if the terminal device has the suspension data, the terminal device transmits a first message to request to restore the RRC connection and informs the network device that there is data to transmit. That is, the present application uses the terminal device to request to recover the RRC connection by receiving the paging message or executing the RNAU-triggered RRC connection recovery procedure, and informs the network device that there is data to be transmitted, so as to achieve the purpose of transmitting the suspended data.

When the suspension data exists in the terminal equipment, a triggering condition can be set, and the terminal equipment can trigger the RRC connection recovery process only when the triggering condition is met.

As an example, the RRC connection recovery procedure may be triggered in case the data amount of the suspended data is greater than a preset threshold value. The preset threshold value may be configured by the network device, for example, the preset threshold value is configured by the network device through a configuration message; but also may be configured by a third party device (e.g., a network management device), for example, the preset threshold value is configured by the third party device through a control message; the preset threshold value may be agreed upon by the terminal device and the network device without transmission, for example, as embodied in a protocol.

As another example, the RRC connection recovery procedure is triggered when suspension data exists for a specific at least one Radio Bearer (RB), a specific at least one logical channel, or a specific at least one logical channel group. Also, the specific at least one RB, the specific at least one logical channel, or the specific at least one logical channel group may be configured by the network device or the third party device, or may be agreed upon by the terminal device and the network device without requiring configuration of the network device, for example, as embodied in a protocol. For example, configured by the network device or the third party device, a switch cell may be configured to indicate that the RRC connection recovery procedure may be triggered only when the RB, the logical channel or the logical channel group is specified to have suspended data, where the switch cell may be configured through an RRC message or may be configured through MAC layer signaling. In particular, the switch cell may be carried in a specific RB, logical channel or logical channel group configuration, and RRC connection restoration may be triggered when the switch cell of the specific RB, logical channel or logical channel group is configured to be on, real (real) or carries the switch cell, and there is pending data for the specific RB, logical channel or logical channel group.

It may be appreciated that the RB may be a data radio bearer DRB or a signaling radio bearer SRB, which is not limited by the embodiment of the present application.

As yet another example, a first timer may be set, and when the first timer expires and the terminal device holds the suspended data, an RRC connection recovery procedure is triggered. The first timer may be started after the terminal device enters the inactive state. Likewise, the first timer may be configured by the network device or a third party device, or may be agreed upon by the terminal device and the network device without requiring configuration by the network device, e.g., embodied in a protocol.

It will be appreciated that the above-described triggering conditions may be used alone, or in any combination possible, embodiments of the application are not particularly limited,

for the case where the triggering condition is configured by the network device, the network device may send configuration information to the terminal device before the terminal device sends the first message, and the terminal device receives the configuration information. The configuration information is used for configuring a threshold value, the threshold value indicates a minimum data amount of suspended data triggering the terminal equipment to send a first message, and/or is used for designating at least one Radio Bearer (RB), at least one logic channel or at least one logic channel group, and/or is used for configuring a first timer, the first timer is started after the terminal equipment enters an inactive state, and the first message is sent after the first timer is overtime.

There are many implementations of the first message, as long as it can request to restore the radio resource control RRC connection and indicate to the network device that the terminal device has data to send, and embodiments of the present application are not limited in particular.

As an example, the first message may be an RRC connection resume request message, an RRC connection resume request message 1, or other messages that may implement the above functions. The first message may comprise a first cell indicating that the terminal device has data to send. It will be appreciated that the first cell may be a newly added cell or may be a multiplexed existing cell.

The RRC connection restoration request message and the RRC connection restoration request message 1 are used to request restoration of RRC connection, including restoration of SRBs and DRBs that were suspended before, so as to perform data transmission or perform RNAU. The message size of the RRC connection resume and RRC connection resume message 1 may be different. When the uplink resource size available for sending the RRC message is smaller, the terminal device may send an RRC connection resume message, where the RRC connection resume message includes a shorter I-RNTI identifier, and is used to indicate that the terminal device is in an inactive state, for example, may be a truncated I-RNTI, and uses a fewer number of bits (bits) to identify a suspension context of the UE in the inactive state than the I-RNTI, so that the terminal device may be guaranteed to send in the smaller uplink resource; when the uplink resource size available for sending the RRC message is larger, the terminal device may send the RRC connection resume message 1, including the I-RNTI of a complete UE, so as to ensure that more information can be sent on the larger uplink resource.

Taking the first message as an RRC connection recovery request message as an example, if the first cell is a newly added cell, the message may include the following:

still taking the first message as an RRC connection resume request message as an example, if the first cell multiplexes the existing cells, for example, a resume reason cell, the resume reason cell is used to indicate the reason of the RRC connection resume request. Specifically, a new cause value may be added to indicate suspended data, or an existing cause value may be multiplexed to indicate only new data. When a new cause value is added, the recovery cause information element included in the message may be as follows:

ResumeCAuse =ENUMERATED { email, highPrioritityAccess, mt-Access, mo-Signalling, mo-Data, mo-Voiceall, mo-video Call, mo-SMS, rn-Update, mps-PrioritityAccess, mcs-PrioritityAccess, new cause values, spark 1, spark 2, spark 3, spark 4, spark 5}, respectively

When the terminal device carries a new cause value in the RRC connection resume request message, it indicates that the terminal device has suspended data.

Alternatively, the new cause value may represent more than one restoration cause, e.g. RANU and presence of suspended data, terminal device with data transfer request and presence of suspended data, terminal device with voice/video telephony and presence of suspended data, etc.

Alternatively, the first cell may be a boolean variable (boolean), which when true indicates that the terminal device has pending data.

As another example, the first message may include at least one of an RRC connection resume request message, an RRC connection resume request message 1, or other messages that may implement the above functions, and indication information. As an example, the first message may include an RRC connection restoration request message for requesting restoration of an RRC connection and indication information independent of the RRC connection restoration request message for indicating that the terminal device has data to transmit. The description of the RRC connection recovery request message and the RRC connection recovery request message 1 may refer to the above, and will not be repeated here.

For example, the first message may further include an RRC connection resume request message and a buffer status report (buffer status report, BSR), where the RRC connection resume request message is used to request that the RRC connection be resumed, and the BSR is used to indicate that the terminal device has data to send, that is, when the terminal device has pending data, and triggers an RRC connection resume procedure, the terminal device is triggered to send the BSR. Alternatively, the BSR may be a regular BSR. For example, the buffer size of all logical channel groups with pending data may be reflected in a long BSR format; the buffer size of one logical channel group in which pending data exists may be reflected, for example, a logical channel group having the highest priority among priorities of all logical channels in at least one logical channel group, or a specific one of the logical channel groups. The BSR may also be a padding BSR for transmitting BSR information as useful as possible in case that the padding bit is equal to or greater than the BSR size.

For another example, the first message includes an RRC connection restoration request message for requesting restoration of the RRC connection and a MAC CE for indicating presence of the suspended data in the terminal device. Alternatively, as shown in fig. 5, the MAC CE may have only a MAC sub-header (sub-header) and no payload portion, and when the terminal device carries a preset MAC header, the terminal device may be indicated to store the suspension data by a specific logical channel identifier (logical channel identity, LCID) in the preset MAC header, for example, lcid=x indicates that the LCID corresponding to the MAC CE is used to indicate that the terminal device stores the suspension data.

For another example, the first message includes an RRC connection resume request message for requesting resumption of an RRC connection and a MAC layer sub-header (sub-header) indication for indicating that suspended data exists in the terminal device. Alternatively, the MAC layer sub-header indication may be a separate MAC layer sub-header or may be indicated by a new cell added to the existing MAC layer sub-header. Taking the newly added cell as an example, as shown in fig. 6, when the P field is set to 1, it indicates that the terminal device has the pending data.

In 420, the network device sends a second message to the terminal device, where the terminal device receives the second message, where the second message is used to instruct the terminal device to resume the RRC connection.

The second message may be an RRC connection resume message or other message that may instruct the terminal device to resume the RRC connection, which is not particularly limited in the present application.

Alternatively, the terminal device may switch from the inactive state to the connected state after receiving the second message, and the specific flow may refer to fig. 2. After the network device sends the second message to the terminal device, the network device may schedule the suspended data according to the actual situation.

It may be appreciated that the terminal device may initiate data transmission in an inactive state, for example, the terminal device may perform data transmission in a random access process, or may perform data direct transmission in a manner that the terminal device does not perform random access; or the terminal device may first switch from the inactive state to the connected state and then initiate data transmission, and embodiments of the present application are not specifically limited.

The embodiment of the application also provides another method for transmitting data, as shown in fig. 7, and fig. 7 is a schematic flow chart of the method for transmitting data according to another embodiment of the application.

In 710, the network device sends a third message to the terminal device, the terminal device receiving the third message, wherein the third message is for instructing the terminal device to release the radio resource control, RRC, connection.

In 720, the terminal device sends a fourth message to the network device, and the network device receives the fourth message, wherein the fourth message is used to indicate that the terminal device is ready to release the RRC connection with the network device.

That is, before entering the inactive state, the terminal device actively feeds back to the network device that it is ready to release the RRC connection, instead of entering the inactive state after receiving the third message, so that the terminal device may enter the inactive state only when it is ready to enter the inactive state (e.g., when it is not suspending data), thereby enabling to reduce the probability of losing the data packet during the state transition of the terminal device.

Alternatively, the fourth message may be an RRC connection release complete message, an RRC connection release confirm message, an ACK message for the third message, or the like.

Optionally, after 710, when the terminal device has the suspended data stored therein, the terminal device may send a fifth message to the network device, wherein the fifth message is used to indicate that the terminal device is to be sent by the data. That is, before the terminal device enters the inactive state, the suspended data check is added, so that the opportunity for transmitting the suspended data is given before the terminal device enters the inactive state, so that the probability that the suspended data fails due to overlong residence time can be reduced, and the probability of losing the data packet in the state transition process of the terminal device can be further reduced. And compared with the method that the terminal equipment is given the opportunity to transmit the suspended data after entering the inactive state, the method can finish the transmission of at least part of the suspended data in advance, reduce the residence time of the suspended data, and further reduce the probability of losing the data packet in the state transition process of the terminal equipment.

It is to be understood that 720 may be performed before or after the terminal device sends the fifth message, which is not limited by the embodiment of the present application.

As an example, which is performed before the terminal device sends the fifth message, 720, the terminal device may release the RRC connection with the network device after 720.

As an example, the terminal device releases the RRC connection with the network device after at least a portion of the pending data transmission is completed. Optionally, after at least part of the pending data transmission is completed, the terminal device sends a feedback message for the third message to the network device.

As another example, the terminal device releases the RRC connection with the network device when the second timer expires. Specifically, the second timer is started after the terminal equipment receives the third message; or, starting the second timer after the terminal equipment receives the preset time period after receiving the third message; or the second timer is started after the terminal equipment sends a fourth message to the network equipment; or after the overtime of the second timer is at the end of the preset time period, the preset time period starts from the terminal equipment receiving the third message; or, the timeout of the second timer is after the terminal device sends the fourth message to the network device.

Alternatively, the second timer may be configured by the network device or a third party device, or may be agreed upon by the terminal device and the network device without requiring configuration by the network device, e.g., embodied in a protocol.

The fifth message may indicate that there is data to be sent in any manner, and embodiments of the present application are not specifically limited. As one example, the fifth message includes a BSR by buffer status report. That is, the terminal device triggers the BSR when receiving the third message or transmitting the fourth message. Optionally, the terminal device may trigger to send the BSR each time the third message is received, or may meet a certain trigger condition and trigger to send the BSR when the third message is received. The description of the trigger condition may be referred to above and will not be repeated here.

It will be appreciated that the method of fig. 4 and the method of fig. 7 may be implemented alone or in combination, and the application is not limited by comparison.

An embodiment of the device of the present application is described below with reference to fig. 8 to 15.

Fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application. The terminal device 800 shown in fig. 8 may correspond to the above terminal device, and as shown in fig. 8, the terminal device 800 includes a receiving module 810 and a transmitting module 820.

A sending module 820, configured to send a first message to a network device when the terminal device 800 has suspended data, where the terminal device 800 is in an inactive state, where the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device 800 has data to send, and the suspended data is data stored in a PDCP layer of the terminal device 800.

A receiving module 810, configured to receive a second message sent by a network device, where the second message is used to instruct the terminal device 800 to restore RRC connection.

Alternatively, the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device 800 requests the PDCP layer to be suspended.

Optionally, the terminal device 800 further includes a processing module 830, configured to determine, before the sending module sends the first message, that a trigger condition is met, where the trigger condition is at least one of the following conditions: the data quantity of the suspended data is larger than a preset threshold value; the presence of the suspension data by at least one radio bearer RB specified by the network device, at least one logical channel specified by the network device, or at least one logical channel group specified by the network device; a first timer times out, and the first timer is started after the terminal device 800 enters an inactive state; receiving a paging message; the radio access network notification area update RNAU needs to be performed. The sending module 820 is specifically configured to send the first message to the network device when the terminal device meets the trigger condition.

Optionally, the first message is an RRC connection restoration request message, and a restoration reason cell in the RRC connection restoration request message indicates that the terminal device 800 has data to send.

Optionally, the first message includes an RRC connection restoration request message and a buffer status report BSR, where the RRC connection restoration request message is used to request restoration of an RRC connection, and the BSR is used to indicate that the terminal device 800 has data to send; alternatively, the first message includes an RRC connection restoration request message for requesting restoration of an RRC connection and a medium access control element MAC CE for indicating that the suspended data exists in the terminal device 800.

Optionally, the processing module 830 is further configured to switch the terminal device 800 from the inactive state to the connected state after the receiving module receives the second message sent by the network device.

The receiving module 810 and the transmitting module 820 may be implemented by transceivers. The processing module 830 may be implemented by a processor. The specific functions and advantages of the receiving module 810, the transmitting module 820 and the processing module 830 can be referred to as the method shown in fig. 4, and will not be described herein.

Fig. 9 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 900 shown in fig. 9 may correspond to the above network device, and as shown in fig. 9, the network device 900 includes a receiving module 910 and a transmitting module 920.

A receiving module 910, configured to receive a first message sent by a terminal device, where the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device has data to send, where the terminal device stores suspension data, and the suspension data is data stored in a PDCP layer of the terminal device;

a sending module 920, configured to send a second message to the terminal device, where the second message is used to instruct the terminal device to restore RRC connection.

Optionally, the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to suspend.

Optionally, the sending module 920 is further configured to send, before the receiving module 910 receives the first message sent by the terminal device, configuration information to the terminal device, where the configuration information is used to:

configuring a threshold value, wherein the threshold value indicates the minimum data quantity of the suspended data triggering the terminal equipment to send the first message; and/or the number of the groups of groups,

Designating at least one radio bearer RB, at least one logical channel, or at least one logical channel group; and/or the number of the groups of groups,

and configuring a first timer, wherein the first timer is started after the terminal equipment enters an inactive state, and the first message is sent after the first timer is overtime.

The receiving module 910 and the transmitting module 920 may be implemented by transceivers. The specific functions and advantages of the receiving module 910 and the transmitting module 920 may be referred to as a method shown in fig. 4, and will not be described herein.

Fig. 10 is a schematic block diagram of a terminal device according to another embodiment of the present application. The terminal device 1000 shown in fig. 10 may correspond to the above terminal device, and as shown in fig. 10, the terminal device 1000 includes a receiving module 1010 and a transmitting module 1020.

A receiving module 1010, configured to receive a third message sent by a network device, where the third message is used to instruct the terminal device 1000 to release a radio resource control RRC connection.

A sending module 1020, configured to send a fourth message to the network device, where the fourth message is used to indicate that the terminal device 1000 is ready to release the RRC connection with the network device.

Optionally, the sending module 1020 is further configured to send a fifth message to a network device when the terminal device 1000 has pending data, where the pending data is data stored in the PDCP layer of the terminal device 1000, and the fifth message is used to indicate that the terminal device 1000 has data to send.

Alternatively, the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device 1000 requests the PDCP layer to be suspended.

Optionally, the terminal device 1000 further comprises a processing module 1030 for releasing the RRC connection with the network device.

Optionally, the processing module 1030 is specifically configured to release the RRC connection with the network device after the suspended data is sent.

Optionally, the sending module 1020 is further configured to send the fourth message to the network device after the suspended data is sent.

Optionally, the processing module 1030 is specifically configured to release the RRC connection with the network device when the second timer expires.

Optionally, the indication message includes a buffer status report BSR.

The receiving module 1010 and the transmitting module 1020 may be implemented by transceivers. The processing module 1030 may be implemented by a processor. The specific functions and advantages of the receiving module 1010, the transmitting module 1020 and the processing module 1030 may be referred to as a method shown in fig. 7, and will not be described herein.

Fig. 11 is a schematic block diagram of a network device according to another embodiment of the present application. The network device 1100 shown in fig. 11 may correspond to the above network device, and as shown in fig. 11, the network device 1100 includes a receiving module 1110 and a transmitting module 1120.

A sending module 1120, configured to send a third message to a terminal device, where the third message is used to instruct the terminal device to release a radio resource control RRC connection;

a receiving module 1110, configured to receive a fourth message sent by the terminal device, where the fourth message is used to indicate that the terminal device is ready to release the RRC connection with the network device 1100.

Optionally, the receiving module 1110 is further configured to receive a fifth message sent by the terminal device, where the terminal device stores suspension data, where the suspension data is data stored in a PDCP layer of the terminal device, and the fifth message is used to indicate that the terminal device has data to send.

The receiving module 1110 and the transmitting module 1120 may be implemented by transceivers. The specific functions and advantages of the receiving module 1110 and the transmitting module 1120 can be referred to as the method shown in fig. 7, and will not be described herein.

Fig. 12 is a schematic block diagram of a terminal device according to another embodiment of the present application. As shown in fig. 12, the terminal device 1200 may include a transceiver 1210, a processor 1220, and a memory 1230.

Only one memory and processor is shown in fig. 12. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

The transceiver 1210, processor 1220 and memory 1230 communicate with each other via internal communication paths to transfer control and/or data signals.

Specifically, the transceiver 1210 is configured to send a first message to a network device when the terminal device 1200 has suspended data, where the terminal device 1200 is in an inactive state, and the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device 1200 has data to send, where the suspended data is data stored in the PDCP layer of the terminal device 1200.

The transceiver 1210 is further configured to receive a second message sent by a network device, where the second message is used to instruct the terminal device 1200 to restore the RRC connection.

The specific operation and advantages of the terminal device 1200 may be described in the embodiment shown in fig. 4, and will not be described herein.

Fig. 13 is a schematic block diagram of a network device according to another embodiment of the present application. As shown in fig. 13, the network device 1300 may include a transceiver 1310, a processor 1320, and a memory 1330.

Only one memory and processor is shown in fig. 13. In an actual network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

The transceiver 1310, the processor 1320, and the memory 1330 communicate with each other via internal communication paths to transfer control and/or data signals.

Specifically, the transceiver 1310 is configured to receive a first message sent by a terminal device, where the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device has data to send, where the terminal device stores suspension data, and the suspension data is data stored in a PDCP layer of the terminal device.

The transceiver 1310 is further configured to send a second message to the terminal device, where the second message is used to instruct the terminal device to restore the RRC connection.

The specific operation and advantages of the network device 1300 may be described in the embodiment shown in fig. 4, and will not be described herein.

Fig. 14 is a schematic block diagram of a terminal device according to another embodiment of the present application. As shown in fig. 14, the terminal device 1400 may include a transceiver 1410, a processor 1420, and a memory 1430.

Only one memory and processor is shown in fig. 14. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

The transceiver 1410, the processor 1420, and the memory 1430 communicate with each other via internal communication paths to transfer control and/or data signals.

Specifically, the transceiver 1410 is configured to receive a third message sent by a network device, where the third message is configured to instruct the terminal device 1400 to release a radio resource control RRC connection.

The transceiver 1410 is further configured to send a fourth message to the network device, where the fourth message is used to indicate that the terminal device 1400 is ready to release the RRC connection with the network device.

The specific operation and advantages of the terminal device 1400 may be described in the embodiment shown in fig. 7, and will not be described herein.

Fig. 15 is a schematic block diagram of a network device according to another embodiment of the present application. As shown in fig. 15, the network device 1500 may include a transceiver 1510, a processor 1520, and a memory 1530.

Only one memory and processor is shown in fig. 15. In an actual network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

The transceiver 1510, the processor 1520, and the memory 1530 communicate with each other via internal communication paths, delivering control and/or data signals.

Specifically, the transceiver 1510 is configured to send a third message to a terminal device, where the third message is configured to instruct the terminal device to release a radio resource control RRC connection.

The transceiver 1510 is further configured to receive a fourth message sent by the terminal device, where the fourth message is used to indicate that the terminal device is ready to release the RRC connection with the network device 1500.

The specific operation and advantages of the network device 1500 may be described in the embodiment shown in fig. 7, and will not be described herein.

The transceiver according to the embodiments of the present application may also be referred to as a transceiver unit, a transceiver device, etc. The processor may also be referred to as a processing unit, processing board, processing module, processing device, etc. Alternatively, the device for implementing the receiving function in the transceiver may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver may be regarded as a transmitting unit, i.e. the transceiver comprises a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, or receiving circuit, among others. The transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

The memory described in various embodiments of the application is used to store computer instructions and parameters required for the operation of the processor.

The processor according to the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor described by embodiments of the application may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a memory medium well known in the art such as random access memory (random access memory, RAM), flash memory, read-only memory (ROM), programmable read-only memory, or electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads instructions from the memory and, in combination with its hardware, performs the steps of the method described above.

It should be understood that the manner, the case, the category, and the division of the embodiments in the embodiments of the present application are merely for convenience of description, and should not be construed as a particular limitation, and the features in the various manners, the categories, the cases, and the embodiments may be combined without contradiction.

It should be noted that the "first", "second" and "third" in the embodiments of the present application are only for distinguishing, and should not be construed as limiting the present application in any way.

It should be further noted that, in the embodiment of the present application, the "preset" and "preconfiguring" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the present application is not limited to the specific implementation manner thereof.

It should also be noted that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in the present application is merely an association relation describing the association object, and indicates that three kinds of relations may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It is also noted that "at least one of … …" in embodiments of the present application means one of the listed items or any combination thereof, e.g., "at least one of A, B and C" means: there are six cases where A alone, B alone, C alone, both A and B, both A and C, both B and C, and both A, B and C.

In various embodiments of the present application, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Claims

1. A method for transmitting data, comprising:

when suspended data exists, the terminal equipment sends a first message to the network equipment, wherein the terminal equipment is in an inactive state, and the first message is used for requesting to recover Radio Resource Control (RRC) connection and indicating that the terminal equipment has data to be sent to the network equipment;

and the terminal equipment receives a second message sent by the network equipment, wherein the second message is used for indicating the terminal equipment to restore the RRC connection.

2. The method of claim 1, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

3. The method of claim 2, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

4. A method according to any of claims 1 to 3, characterized in that before the terminal device sends the first message, the method further comprises:

the terminal equipment determines that a triggering condition is met, wherein the triggering condition is at least one of the following conditions:

the data quantity of the suspended data is larger than a preset threshold value;

The presence of the suspension data by at least one radio bearer RB specified by the network device, at least one logical channel specified by the network device, or at least one logical channel group specified by the network device;

a first timer is overtime, and the first timer is started after the terminal equipment enters an inactive state;

receiving a paging message;

requiring execution of a radio access network notification area update, RNAU;

the terminal device sends a first message to the network device when the suspended data exists, and the first message comprises:

and when the terminal equipment meets the triggering condition, the terminal equipment sends the first message to the network equipment.

5. The method according to any one of claim 1 to 4, wherein,

the first message is an RRC connection recovery request message, and a recovery reason cell in the RRC connection recovery request message indicates that the terminal equipment has data to send; or alternatively, the process may be performed,

the first message comprises an RRC connection recovery request message and a Buffer Status Report (BSR), wherein the RRC connection recovery request message is used for requesting to recover RRC connection, and the BSR is used for indicating that the terminal equipment has data to send; or alternatively, the process may be performed,

The first message includes an RRC connection restoration request message for requesting restoration of an RRC connection and a medium access control element MAC CE for indicating that the suspended data exists in the terminal device.

6. A method for transmitting data, comprising:

the network equipment receives a first message sent by the terminal equipment, wherein the first message is used for requesting to recover Radio Resource Control (RRC) connection and indicating to the network equipment that the terminal equipment has data to send, and the terminal equipment stores suspension data;

and the network equipment sends a second message to the terminal equipment, wherein the second message is used for indicating the terminal equipment to restore the RRC connection.

7. The method of claim 6, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

8. The method of claim 7, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to suspend.

9. A method according to any of claims 6 to 8, characterized in that before the network device receives the first message sent by the terminal device, the method further comprises:

The network device sends configuration information to the terminal device, wherein the configuration information is used for:

10. A method for transmitting data, comprising:

the terminal equipment receives a third message sent by the network equipment, wherein the third message is used for indicating the terminal equipment to release Radio Resource Control (RRC) connection;

the terminal device sends a fourth message to the network device, where the fourth message is used to instruct the terminal device to prepare to release the RRC connection with the network device.

11. The method of claim 10, wherein after the terminal device receives the third message sent by the network device, the method further comprises:

and the terminal equipment sends a fifth message to the network equipment when the suspended data exists, wherein the fifth message is used for indicating that the terminal equipment has data to be sent.

12. The method of claim 11, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

13. The method of claim 12, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

14. The method according to any one of claims 10 to 13, further comprising:

the terminal device releases an RRC connection with the network device.

15. The method of claim 14, wherein the terminal device releases the RRC connection with the network device, comprising:

and when the second timer expires, the terminal equipment releases the RRC connection with the network equipment.

16. A method for transmitting data, comprising:

the network equipment sends a third message to the terminal equipment, wherein the third message is used for indicating the terminal equipment to release Radio Resource Control (RRC) connection;

the network device receives a fourth message sent by the terminal device, where the fourth message is used to indicate that the terminal device is ready to release the RRC connection with the network device.

17. The method of claim 16, wherein after the network device sends the third message to the terminal device, the method further comprises:

the network device receives a fifth message sent by the terminal device, the terminal device stores suspension data, and the fifth message is used for indicating that the terminal device has data to send.

18. The method of claim 17, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

19. The method of claim 18, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

20. A terminal device, comprising:

a sending module, configured to send a first message to a network device when the terminal device has suspended data, where the terminal device is in an inactive state, where the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device has data to send;

and the receiving module is used for receiving a second message sent by the network equipment, wherein the second message is used for indicating the terminal equipment to recover the RRC connection.

21. The terminal device of claim 20, wherein the hold data is data stored in a packet data convergence layer protocol PDCP layer of the terminal device.

22. The terminal device of claim 21, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

23. The terminal device according to any of the claims 20 to 22, further comprising a processing module for determining that a trigger condition is met before the sending module sends the first message, the trigger condition being at least one of:

receiving a paging message;

requiring execution of a radio access network notification area update, RNAU;

the sending module is specifically configured to send the first message to the network device when the terminal device meets the trigger condition.

24. Terminal device according to any of the claims 20 to 23, characterized in that,

25. A network device, comprising:

a receiving module, configured to receive a first message sent by a terminal device, where the first message is used to request to restore a radio resource control RRC connection and indicate to the network device that the terminal device has data to send, and the terminal device stores suspended data;

and the sending module is used for sending a second message to the terminal equipment, wherein the second message is used for indicating the terminal equipment to restore the RRC connection.

26. The network device of claim 25, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

27. The network device of claim 26, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

28. The network device according to any of claims 25 to 27, wherein the sending module is further configured to send configuration information to the terminal device before the receiving module receives the first message sent by the terminal device, the configuration information being configured to:

29. A terminal device, comprising:

A receiving module, configured to receive a third message sent by a network device, where the third message is used to instruct the terminal device to release radio resource control RRC connection;

and the sending module is used for sending a fourth message to the network equipment, wherein the fourth message is used for indicating that the terminal equipment is ready to release the RRC connection with the network equipment.

30. The terminal device of claim 29, wherein the sending module is further configured to send a fifth message to a network device when there is pending data for the terminal device, the fifth message being configured to indicate that the terminal device has data to send.

31. The terminal device of claim 30, wherein the hold data is data stored in a packet data convergence layer protocol PDCP layer of the terminal device.

32. The terminal device of claim 31, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.

33. The terminal device according to any of the claims 29 to 32, characterized in that the terminal device further comprises a processing module for releasing the RRC connection with the network device.

34. The terminal device according to claim 33, wherein the processing module is configured to release the RRC connection with the network device when the second timer expires.

35. A network device, comprising:

a sending module, configured to send a third message to a terminal device, where the third message is used to instruct the terminal device to release radio resource control RRC connection;

and the receiving module is used for receiving a fourth message sent by the terminal equipment, wherein the fourth message is used for indicating that the terminal equipment is ready to release the RRC connection with the network equipment.

36. The network device of claim 35, wherein the receiving module is further configured to receive a fifth message sent by the terminal device, the terminal device storing pending data, the fifth message being configured to indicate that the terminal device has data to send.

37. The network device of claim 36, wherein the pending data is data stored at a packet data convergence layer protocol PDCP layer of the terminal device.

38. The network device of claim 37, wherein the suspension data is data stored in the PDCP layer when the RRC layer of the terminal device requests the PDCP layer to be suspended.