WO2021003753A1

WO2021003753A1 - Method and device for sending release assistance indication message

Info

Publication number: WO2021003753A1
Application number: PCT/CN2019/095655
Authority: WO
Inventors: 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-07-11
Filing date: 2019-07-11
Publication date: 2021-01-14
Also published as: CN113196858B; CN113196858A

Abstract

Provided are a method and device for sending a release assistance indication message. A clear solution is provided for the state conversion of a terminal device. The method comprises: a terminal device determining, according to the quantity of data to be transmitted in all logic channel groups, whether to send a release assistance indication message to a network device, wherein the release assistance indication message is used for the network device to determine whether a radio resource control (RRC) connection with the terminal device needs to be disconnected.

Description

Method and equipment for sending release auxiliary indication message

Technical field

This application relates to the field of communications, and more specifically, to a method and device for sending a release assistance indication message.

Background technique

The radio resource control (RRC) state of the terminal device may include three types: RRC connected state, RRC inactive state, and RRC idle state. When the terminal device is in the RRC connection state, the terminal device can transmit data with the network device, and the terminal device needs to continuously monitor the physical downlink control channel (PDCCH); but when the terminal device is in the RRC inactive state or idle with RRC In the state, the terminal device may not need to monitor the PDCCH. Therefore, compared to the RRC connected state, the terminal device saves more power in the RRC inactive state and the RRC idle state.

In order to save power, the terminal device can instruct the network device to perform state transition, for example, transition from the RRC connected state to the RRC idle state, but there is currently no clear solution for how the terminal device instructs the network device to perform state transition.

Summary of the invention

This application provides a method and device for sending a release assistance indication message, and provides a clear solution for the terminal device to perform state transition.

In a first aspect, a method for sending a release assistance indication message is provided, which includes: a terminal device determines whether to send a release assistance indication message to a network device according to the amount of data to be transmitted in all logical channel groups. The indication message is used by the network device to determine whether to disconnect the radio resource control RRC connection with the terminal device.

In a second aspect, a method for sending a release assistance indication message is provided, including: a network device receives a release assistance indication message sent by a terminal device; and the network device determines whether a disconnection is required according to the release assistance indication message. The radio resource of the terminal device controls the RRC connection.

In a third aspect, a terminal device is provided, which is used to execute the method in the foregoing first aspect or each of its implementation manners.

Specifically, the terminal device includes a functional module for executing the method in the foregoing first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided, which is configured to execute the method in the second aspect or its implementation manners.

Specifically, the network device includes a functional module for executing the method in the foregoing second aspect or each implementation manner thereof.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.

In a seventh aspect, a device is provided for implementing any one of the first aspect to the second aspect or the method in each implementation manner thereof.

Specifically, the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the second aspect or any of its implementation modes method.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the first aspect to the second aspect or the method in each implementation manner thereof.

In a ninth aspect, a computer program product is provided, which includes computer program instructions that cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In a tenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In the technical solution provided by this application, the terminal device can request the network device to switch the RRC state by sending the release auxiliary indication information to the network device, and whether the terminal device sends the RAI message can be determined based on the amount of data to be transmitted, which is The state transition of the terminal device provides a clear solution, which is beneficial to save the power consumption of the terminal device.

Description of the drawings

Fig. 1 is a schematic diagram of a wireless communication system applied in an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for sending release assistance indication information according to an embodiment of the present application.

FIG. 3 is a schematic flowchart of another method for sending release assistance indication information provided by an embodiment of the present application.

Fig. 4 is a schematic diagram of a BSR format provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of another BSR provided by an embodiment of the present application.

Fig. 6 is a schematic diagram of a format of a RAI message provided by an embodiment of the present application.

Fig. 7 is a schematic diagram of another format of a RAI message provided by an embodiment of the present application.

FIG. 8 is a schematic block diagram of another terminal device provided by an embodiment of the present application.

FIG. 9 is a schematic block diagram of a network device provided by an embodiment of the present application.

FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application.

FIG. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Fig. 12 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

Fig. 1 is a schematic diagram of a system 100 according to an embodiment of the present application.

As shown in FIG. 1, the terminal device 110 is connected to the first network device 130 under the first communication system and the second network device 120 under the second communication system. For example, the first network device 130 is a Long Term Evolution (Long Term Evolution). , A network device under LTE), the second network device 120 is a network device under a New Radio (NR).

Wherein, the first network device 130 and the second network device 120 may include multiple cells.

It should be understood that FIG. 1 is an example of a communication system in an embodiment of the present application, and the embodiment of the present application is not limited to that shown in FIG. 1.

As an example, the communication system to which the embodiment of the present application is adapted may include at least multiple network devices under the first communication system and/or multiple network devices under the second communication system.

For example, the system 100 shown in FIG. 1 may include one main network device under the first communication system and at least one auxiliary network device under the second communication system. At least one auxiliary network device is respectively connected to the one main network device to form multiple connections, and is connected to the terminal device 110 to provide services for it. Specifically, the terminal device 110 may simultaneously establish a connection through the main network device and the auxiliary network device.

Optionally, the connection established between the terminal device 110 and the main network device is the main connection, and the connection established between the terminal device 110 and the auxiliary network device is the auxiliary connection. The control signaling of the terminal device 110 may be transmitted through the main connection, and the data of the terminal device 110 may be transmitted through the main connection and the auxiliary connection at the same time, or may be transmitted only through the auxiliary connection.

As another example, the first communication system and the second communication system in the embodiment of the present application are different, but the specific types of the first communication system and the second communication system are not limited.

For example, the first communication system and the second communication system may be various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD) ), Universal Mobile Telecommunication System (UMTS), etc.

The main network device and the auxiliary network device may be any access network device.

Optionally, in some embodiments, the access network device may be a base station (Base Transceiver) in the Global System of Mobile Communication (GSM) system or Code Division Multiple Access (CDMA). Station, BTS), it can also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in a Long Term Evolution (LTE) system (Evolutional Node B, eNB or eNodeB).

Optionally, the access network device may also be a Next Generation Radio Access Network (NG RAN), or a base station (gNB) in an NR system, or a cloud radio access network (Cloud The radio controller in Radio Access Network, CRAN, or the access network device can be a relay station, access point, in-vehicle device, wearable device, or in the future evolution of Public Land Mobile Network (PLMN) Network equipment, etc.

In the system 100 shown in FIG. 1, the first network device 130 is taken as the main network device, and the second network device 120 is taken as an auxiliary network device as an example.

The first network device 130 may be an LTE network device, and the second network device 120 may be an NR network device. Or, the first network device 130 may be an NR network device, and the second network device 120 may be an LTE network device. Or both the first network device 130 and the second network device 120 may be NR network devices. Or the first network device 130 may be a GSM network device, a CDMA network device, etc., and the second network device 120 may also be a GSM network device, a CDMA network device, etc. Or the first network device 130 may be a Macrocell, and the second network device 120 may be a Microcell, Picocell, Femtocell, or the like.

Optionally, the terminal device 110 may be any terminal device, and the terminal device 110 includes but is not limited to:

Connected via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/ Or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and/or another terminal device A device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article.

Taking the NR system as an example, the terminal device can support three radio resource control (radio resource control, RRC) states, namely the RRC idle state, the RRC inactive state and the RRC connected state.

In the RRC idle state, mobility is UE-based cell selection or reselection, paging is initiated by the core network (core network, CN), and the paging area is configured by the CN. There is no UE access stratum (AS) context on the base station side. In the RRC idle state, there is no RRC connection.

In the RRC inactive state, mobility is based on UE-based cell selection or reselection, there is a connection between the core network and the base station, the UE AS context is stored on a certain base station, and paging is performed by the radio access network (RAN) Triggered, the RAN-based paging area is managed by the RAN, and the network side knows that the location of the UE is based on the RAN paging area level.

In the RRC connected state, there is an RRC connection, and a UE AS context exists between the base station and the UE. The network side knows that the location of the UE is of a specific cell level. Mobility is the mobility controlled by the network side. Data can be transmitted between the UE and the base station.

For a UE in the RRC idle state or RRC inactive state, there is no other data communication between the UE and the network, and the UE does not need to monitor the physical downlink control channel (PDCCH), so the UE is in the RRC idle state or RRC inactive state. More power saving in the state.

In the standardization process of 5G NR, from the perspective of saving power for terminal equipment, consider introducing a release assistance indication (RAI) mechanism in NR. This RAI mechanism can be used for terminal equipment to instruct network equipment to perform RRC state transition. For example, switch from the RRC connected state to the RRC idle state to save the power of the terminal device. However, there is currently no clear solution for how the terminal device instructs the network device to perform state transition.

To solve the problem of how the terminal equipment instructs the network equipment to perform state transition, the following three aspects can be considered: 1. What kind of signaling is used to carry the RAI; 2. Under what conditions the RAI is triggered; 3. What is specifically included in the RAI .

Based on the foregoing problems, the embodiments of the present application provide a method for sending release assistance indication information, which provides a clear solution for the terminal device to perform state transition. As shown in Figure 2, the method includes step S210.

S210. The terminal device determines whether to send the RAI message to the network device according to the amount of data to be transmitted.

For example, the terminal device may send an RAI message to the network device when the amount of data to be transmitted is zero to request the network device to switch the terminal device from the RRC connected state to the RRC idle state or the RRC inactive state. If the terminal device has no data to be transmitted and it continues to remain in the RRC connection state, it still needs to continuously monitor the PDCCH, which is not conducive to saving the power of the terminal device. Therefore, the solution of the embodiment of the present application can make the terminal device without service switch to the idle state or the inactive state as soon as possible, thereby saving the energy consumption of the terminal device.

For another example, the terminal device may not send the RAI message to the network device when the amount of data to be transmitted is not zero. In other words, if the terminal device has data to be transmitted, it means that the terminal device still needs to maintain the RRC connection state for data transmission. In this case, the terminal device cannot send a RAI message to the network device to request state transition .

The embodiment of the present application also provides another method for sending RAI messages. As shown in FIG. 3, the method includes steps S310 and S320.

S310. The terminal device sends a RAI message to the network device.

S320. The network device determines whether the RRC connection with the terminal device needs to be disconnected according to the RAI message.

After the network device receives the RAI message sent by the terminal device, it can combine its own implementation to determine whether it needs to disconnect the RRC connection with the terminal device. For example, after the network device receives the RAI message sent by the terminal device, it will determine whether to move the terminal device out of the connected state based on its own estimate of the terminal device's downlink service activity and the target duration indicated in the RAI message.

The content described below is applicable to the methods shown in FIGS. 2 and 3.

The amount of data to be transmitted may include the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.

Taking the NR system as an example, the terminal device can support at least one logical channel group (logical channel group, LCG). The amount of data to be transmitted by the terminal device is zero, which may indicate that the amount of data to be transmitted in at least one logical channel group of the terminal device is zero, where at least one logical channel group is all logical channel groups supported by the terminal device. In other words, the terminal device can determine whether to send the RAI message to the network device according to the amount of data to be transmitted in all logical channel groups supported by the terminal device. In the case where the amount of data to be transmitted in the at least one logical channel group is all zero, the RAI message is sent to the network device.

For example, if the terminal device supports 4 logical channel groups, the terminal device can determine whether to send the RAI message to the network device according to the amount of data to be transmitted in the 4 logical channel groups. When the amount of data to be transmitted in the 4 logical channel groups is 0, the RAI message is sent to the network device; as long as one logical channel group in the 4 logical channel groups has data to be transmitted, the terminal device will not The network device sends a RAI message.

Taking the NR system as an example, the terminal device can support up to 8 logical channel groups.

In the embodiment of the present application, a new logical channel can be redefined to send RAI messages, and the logical channel can be understood as a logical channel dedicated to sending RAI messages. When the terminal device has a RAI message to be sent, it can use the new logical channel to send it. After receiving the logical channel, the network device can determine that the RAI message is carried on the logical channel.

The zero amount of data to be transmitted may indicate that the current amount of data to be transmitted by the terminal device is 0 and the amount of data to be transmitted in the subsequent preset time period is zero. If the terminal device currently has no data transmission, and the terminal device predicts that there will be no data transmission for a period of time in the future, send a RAI message to the network device; if the terminal device currently has no data transmission, the terminal device predicts that there will be Data transmission, the terminal device may not send the RAI message to the network device.

The preset duration can be the duration specified in the protocol or the duration configured by the network device.

If the terminal device currently has no data to be transmitted, and there is no data to be transmitted in the subsequent time period less than the preset time period, the terminal device does not send the RAI message to the network device; if the terminal device does not currently transmit data, and there is no data to be transmitted If there is no data to be transmitted for a period of time greater than or equal to the preset period of time, the terminal device may send a RAI message to the network device.

Assuming that the terminal device currently has no data to be transmitted, and the terminal device predicts that there is no data to be transmitted in the first time period in the future, the terminal device can determine whether to send the RAI message to the network device according to the size of the first time period.

For example, in the case that the first duration is not less than the minimum duration of at least one duration, the terminal device sends a RAI message to the network device; if the first duration is less than the minimum duration of the at least one duration, the terminal device does not send a message to the network device. Send a RAI message.

The at least one duration may be a predefined duration, or may also be a duration configured by the network device for the terminal device. The network device may, for example, configure the at least one duration for the terminal device through RRC signaling.

If the at least one duration includes 10s, 20s, 30s, and 40s, when determining whether to send a RAI message to the network device, the terminal device can base on whether the current amount of data to be transmitted is zero, and whether the duration of no data to be transmitted is greater than Or equal to 10s for judgment.

For example, if the current amount of data to be transmitted by the terminal device is zero, and there is no data to be transmitted within 11s after the terminal device predicts, the terminal device can send a RAI message to the network device; if the amount of data currently to be transmitted by the terminal device is zero , And the terminal device predicts that there is no data transmission within 9s after the prediction, the terminal device does not send the RAI message to the network device.

The embodiment of the present application does not specifically limit the timing of the terminal device sending the RAI message. For example, the terminal device may send a RAI message to the network device when a buffer status report (BSR) is triggered. For another example, the terminal device may send a RAI message to the network device when the first timer expires, that is, the time interval between two consecutive RAI messages sent by the terminal device to the network device is greater than or equal to that of the first timer. Duration, the first timer may be set for the time interval for the terminal device to send the release assistance instruction message, and the first timer may be referred to as the RAI prohibit timer (RAIProhibitTimer).

Through the triggering of the BSR and the setting of the first timer, the time interval for the terminal device to report the RAI can be limited, and the terminal device can avoid reporting too frequently.

The above two methods are described below in combination with specific conditions.

In case 1, the terminal device can send a RAI message to the network device when the BSR is triggered. In the case of sending RAI messages triggered by BSR, RAI messages can be carried by MAC CE. For example, a terminal device can send RAI MAC CE to indicate RAI to a network device. Of course, this is only an example, and RAI messages can also be carried by RRC signaling.

For example, the terminal device may receive the RRC configuration information sent by the network device, and the RRC configuration information may include the configuration parameters of the uplink logical channel and the configuration parameters of the BSR. Among them, the configuration parameters of the uplink logical channel may include the priority of the logical channel and the identification of the logical channel group corresponding to the logical channel. The configuration parameters of the BSR may include a periodic BSR timer (periodicBSR-Timer) and a retransmission BSR timer (retxBSR-Timer).

The terminal device can determine whether the following conditions are met:

(1) The terminal equipment triggers the BSR and the network equipment allocates resources for reporting the BSR to the terminal equipment;

(2) The current amount of data to be transmitted in all logical channel groups of the terminal device is zero, that is, the terminal device is ready to report zero BSR or zero Long BSR;

(3) The terminal equipment predicts that there will be no uplink and/or downlink data transmission demand for a period of time in the future.

If the above three conditions are met at the same time, the terminal device can send the RAI message on the uplink resource. Specifically, the terminal device can send the RAI message on the uplink resource through the MAC CE.

For example, if the terminal device triggers the BSR, and the terminal device determines that the amount of data to be transmitted in all the logical channel groups currently is zero, and the terminal device predicts that there will be a data transmission demand in the near future, the terminal device can be in the network The BSR is sent on the uplink resources allocated by the device, but the RAI message is not sent. After a period of time, the terminal device triggers the BSR again, and the amount of data to be transmitted in all the current logical channel groups of the terminal device is zero, and the terminal device predicts that it will not be in the future for a period of time (such as the first duration). If there is a data transmission demand, the terminal device sends the RAI message on the uplink resource allocated by the network device.

The BSR is mainly used to notify the network equipment of the amount of uplink data currently to be transmitted by the terminal equipment. The terminal equipment can make the serving base station know the amount of uplink buffered data of the terminal equipment through the BSR, so that the base station can schedule the terminal equipment according to the data volume information provided by the terminal equipment.

In order to save BSR reporting overhead, BSR reporting adopts a grouped reporting method, that is, BSRs are mainly sent in the form of logical channel groups. Each uplink logical channel corresponds to a logical channel group, and multiple logical channels can correspond to the same logical channel group, that is, a logical channel group can include multiple logical channels. The correspondence between logical channels and logical channel groups may be configured by network equipment through RRC signaling. The terminal device can report the BSR based on the logical channel group.

The trigger conditions of BSR can be as follows:

1. Uplink data arrives on a logical channel with a higher priority of the terminal device, in this case, a regular BSR is triggered. The terminal device has logical channel data that needs to be sent, and at this time data of a logical channel with a higher priority comes again, the BSR will be triggered by the logical channel with a higher priority.

2. The padding part of the uplink resources allocated to the terminal equipment can carry the BSR after carrying other uplink data. In this case, the padding BSR will be triggered. For example, for the uplink data sent this time, the allocated resources are relatively large, and some padding bits do not need to transmit data. At this time, some triggered BSRs can use these padding data to send. This kind of BSR sent using padding data is called padding. BSR.

3. The retransmission BSR timer (retxBSR-Timer) times out, and there is currently at least one uplink logical channel with uplink data to be sent, at this time a regular BSR is triggered.

4. When the periodic timer (periodicBSR-Timer) expires, the periodic (Periodic) BSR will be triggered.

If the terminal device triggers the BSR, and the terminal device determines that the amount of data currently to be transmitted is zero, the terminal device can report a zero BSR to the network device.

The BSR can be carried by the BSR media access control (MAC) control element (CE). According to the content and format of the report, the BSR can be divided into the following 4 types: Short BSR (Short BSR), Short Truncated BSR (Short Truncated BSR), Long BSR (long BSR), and Long Truncated BSR (Long Truncated BSR).

Short BSR indicates that the number of logical channel groups with uplink data is less than or equal to one, and the terminal device only reports the buffered data volume of one logical channel group. Short Truncated BSR indicates that there are more than one uplink logical channel group, but the terminal device only reports the buffered data volume of one of the logical channel groups. Long BSR indicates that the number of logical channel groups with uplink data is greater than one, and what the terminal device reports is the amount of buffered data of all logical channel groups with uplink data. Long Truncated BSR indicates that the number of logical channel groups with uplink data is greater than one, and what the terminal device reports is the amount of buffered data of some logical channel groups, and the number of reported logical channel groups is greater than one.

Among the above four types of BSR, Short BSR and Short Truncated BSR use Short BSR and Short Truncated BSR MAC CE bearers. The size of Short BSR and Short Truncated BSR MAC CE is fixed, as defined in Figure 4. The MAC CE may include a first field and a second field. The first field is used to indicate the logical channel group identification (logical channel group identity, LCD ID), and the second field is used to indicate the size of buffered data of the logical channel group.

It can be seen from Figure 4 that Short BSR and Short Truncated BSR can only indicate the size of the buffered data of a logical channel group.

If the terminal device currently has only one logical channel group triggering the BSR, the terminal device can use Short BSR and Short Truncated BSR MAC CE to send the BSR.

Long BSR and Long Truncated BSR use Long BSR and Long Truncated BSR MAC CE bearer. The size of Long BSR and Long Truncated BSR MAC CE is variable, as defined in Figure 5.

For Long BSR and Long Truncated BSR, the MAC CE may include multiple first fields and multiple second fields. The multiple first fields are used to indicate whether the number of each logical channel group is to be reported. The fields are respectively used to indicate the size of the buffer data corresponding to multiple logical channel groups that need to be reported.

For example, for a terminal device that supports 8 logical channel groups, layer 1 may include 8 bits, and each bit is used to indicate whether the buffer data amount of the 8 logical channel groups is reported. If the bit value is 0, it means not to report; if the bit value is 1, it means to report. The buffer size of each layer from layer 2 to layer (m+1) respectively represents the buffer data size of the logical channel group that needs to be reported in layer 1. The order of the logical channel groups indicated in layer 2 to layer (m+1) is the ascending order of the identifiers of the logical channel groups that need to be reported in layer 1, and the value of m is equal to the number of logical channel groups that need to report the amount of buffered data .

For example, if only the logical channel groups of LCG ₁ , LCG ₂ , LCG ₅ , and LCG ₇ need to report the buffer amount, then the value of the bit corresponding to LCG ₁ , LCG ₂ , LCG ₅ , and LCG ₇ is 1, and LCG ₀ , The value of the bits corresponding to LCG ₃ , LCG ₄ , and LCG ₆ is 0, that is, the value of the bit in layer 1 can be 01100101 from right to left. In this case, the value of m is 4. The Long BSR also includes layer 2 to layer 5. Each layer of layer 2 to layer 5 represents the buffered data volume of LCG ₁ , LCG ₂ , LCG ₅ , and LCG ₇ respectively. . Layer 2 can represent the buffered data volume of LCG ₁ , layer 3 can represent the buffered data volume of LCG ₂ , layer 4 can represent the buffered data volume of LCG ₅ , and layer 5 can represent the buffered data volume of LCG ₇ .

It can be seen from Figure 5 that Long BSR and Long Truncated BSR can be used to indicate the size of the buffered data of multiple logical channel groups.

If the terminal device currently has multiple logical channel groups triggering the BSR at the same time, the terminal device can use Long BSR and Long Truncated BSR MAC CE to send the BSR.

For Regular BSR and Periodic BSR, if the number of logical channel groups for which the terminal device has uplink data is greater than 1, the terminal device reports the long BSR, and the terminal device reports the amount of buffered data for all logical channel groups with uplink data ; If the number of logical channel groups for which the terminal device has uplink data is less than or equal to 1, the terminal device reports a short BSR.

For padding BSR, it can be described in two cases.

The first case: when the padding bits are enough to carry short BSR but not long BSR, if the number of logical channel groups with uplink data is less than or equal to 1, the terminal device reports the short BSR; if there is an uplink If the number of logical channel groups for data is greater than 1, and the padding bits are just enough to carry the short BSR, the terminal device reports Short Truncated BSR, and the terminal device reports the logical channel with the highest priority in the logical channel group for uplink data. The data volume of the corresponding logical channel group; if the number of padding bits is greater than the number of bits needed for a short BSR, the terminal device can report the Long Truncated BSR, and the data volume of the logical channel group that the terminal device specifically reports can be determined by the uplink data. The priority of the logical channel with the highest priority included in the logical channel group is determined.

For example, the first logical channel group, the second logical channel group, and the third logical channel group all have uplink data to be sent. The highest priority logical channel contained in the first logical channel group has priority 3, and the second logical channel group The priority of the logical channel with the highest priority contained in the channel group is 1, and the priority of the logical channel with the highest priority contained in the third logical channel group is 2. The number of bits in the padding can only carry two logical channel groups In the case of a larger amount of data, the terminal device preferentially sends the buffered data amount of the second logical channel group and the third logical channel group.

The second case: When the padding bits are sufficient to carry the Long BSR, the terminal device reports the Long BSR, which reports the amount of data to be transmitted for all logical channel groups with uplink data.

For example, if the terminal device has 3 logical channel groups that have uplink data to be sent, and if the padding bits are enough to carry the buffered data volume of the 3 logical channel groups, the terminal device reports the Long BSR.

In case 2, the first timer can be used to limit the minimum time interval for the terminal device to report the RAI to avoid the terminal device from reporting too frequently. For example, the first timer may be predefined, for example, the first timer is preset in the terminal device, or the first timer is specified in the protocol; the first timer may be, for example, a network device Configured to terminal equipment.

As an example, the terminal device may receive RRC configuration information sent by the network device, and the configuration information may include RAI related parameters, which may specifically include: 1. At least one duration, that is, the terminal device has no future uplink and/or downlink data transmission requirements Duration; 2. RAI Prohibit Timer (RAIProhibitTimer), which is used to limit the minimum time interval for terminal equipment to report RAI.

The terminal device may maintain a RAI prohibition timer, the method is as follows: each time the terminal device reports an RAI indication, the terminal device starts or restarts the RAI prohibition timer.

The terminal device can determine whether the following conditions are met:

1) The amount of data to be transmitted in all logical channel groups of the terminal equipment is zero;

2) The terminal device has no uplink and/or downlink transmission requirements for a period of time in the future (predict_data_inactivity_duration), and predict_data_inactivity_duration is not less than the minimum value of at least one duration in the RRC configuration information;

3) The terminal device has not sent RAI or the RAI prohibition timer has expired.

If the above three conditions are met at the same time, the terminal device can send a RAI message to the network device. Specifically, the terminal device can send a RAI message to the network device through RRC signaling.

The terminal device in the embodiment of the present application may refer to a terminal device with RAI capability. A terminal device with RAI capability can directly send a RAI message to a network device when the amount of data to be transmitted is zero; or, a terminal device with RAI capability can only send a message to the network device when the network device activates the RAI capability. When the amount of data to be transmitted is zero, a RAI message is sent to the network device. The specific activation process is as follows:

The terminal device can inform the network device whether it can support the RAI function through the RRC message, and the indication information can be carried in the UE capability message. The network device can send the RAI function activation instruction to the terminal device. The RAI function activation instruction can be carried by an RRC message or MAC CE. After the terminal device receives the RAI function activation instruction, it indicates that the RAI function of the terminal device is activated, and the terminal device can subsequently Use this function to report RAI messages to network devices.

The specific content included in the RAI message is described below.

The RAI message may include the target duration and/or the RRC state that the terminal device expects to transition to. The RRC state that the terminal device expects to transition to includes the RRC idle state and/or the RRC inactive state, and the target duration is used to indicate the terminal device The length of time there is no data to be transmitted.

The target duration may be a duration that the terminal device actually predicts that there is no data to be transmitted in the future. For example, if the terminal device predicts that there is no data to be transmitted in the next 12s, the terminal device can carry the target duration of 12s in the RAI message and report it to the network device.

The target duration may also be a duration of at least one duration. The target duration is, for example, the largest duration of the at least one duration that does not exceed the first duration, and the first duration is that none of the logical channel groups predicted by the terminal device The duration of the data to be transmitted. With reference to the above description, the at least one duration may be a predefined duration, or the at least one duration may be a duration configured by the network device to the terminal device.

For example, the at least one duration includes 10s, 20s, 30s, and 40s. The terminal device predicts that there is no data to be transmitted in the next 12s. Since 12s is greater than 10s and less than 20s, the duration of 10s is the maximum of at least one duration that does not exceed 12s. Of a duration. The terminal device can carry the 10s target duration in the RAI message and report it to the network device.

Since the time period predicted by the terminal device that there is no data to be transmitted can be any natural number greater than zero, if the terminal device is allowed to report according to the actual predicted time period, the complexity of the RAI message will increase and the resources occupied by the RAI message will increase. Therefore, by limiting the target duration reported by the terminal device, when the terminal device reports the target duration, it only needs to determine one duration in at least one duration to report, and the network device only needs to configure the terminal device with at least one duration of the resource length occupied In this way, the complexity of RAI messages can be reduced, and the resources occupied by RAI messages can be saved.

If the RAI message only indicates the target duration, but not the RRC state that the terminal device expects to transition to, a new logical channel can be defined to identify the RAI message. In the RAI message, n bits can be used to indicate the target duration, and n is greater than An integer of 0, as shown in Figure 6, the RAI message can be represented in format 1.

For example, the at least one duration may include 10s, 20s, 30s, and 40s, and the duration of the RAI prohibition timer is 2s.

If the amount of data to be transmitted in all the logical channel groups of the terminal device is zero, and the terminal device predicts that there will be no uplink and/or downlink data transmission requirements in the next 2s, because the 2s duration is less than the minimum of at least one duration Value (10s), therefore, the terminal device may not send RAI messages. After a period of time, the amount of data to be transmitted in all the current logical channel groups of the terminal device is zero, and the terminal device predicts that there will be no uplink and/or downlink data transmission requirements in the next 10s, then the terminal device can use RRC signaling Send a RAI message, the target duration carried in the RAI message is 10s, and the terminal device can start or restart the RAI prohibit timer. After 1s after the terminal device sends the RAI message, the current amount of data to be transmitted by the terminal device is zero, and the terminal device predicts that there will be no uplink and/or downlink data transmission requirements in the next 30s, but because RAI is prohibited at this time The timer has not expired, so the terminal device does not send RAI messages. After another 1s has passed, the RAI prohibition timer expires, the terminal device can send the RAI message through RRC signaling, and the target duration carried in the RAI message is 20s.

The RRC state that the terminal device expects to transition to may be indicated by one or more bits in the RAI message and/or the identifier of the logical channel carrying the RAI message.

As an example, the RRC state that the terminal device expects to transition to can be indicated by one or more bits in the RAI message. As shown in FIG. 7, the RAI message can be represented in format 2.

One bit can be used in the RAI message to indicate the RRC state that the terminal device expects to transition to. For example, when the bit value is 0, it means that the terminal device expects to transition to the RRC idle state; when the bit value is 1, , Which means that the terminal device expects to switch to the RRC inactive state.

Of course, multiple bits can also be used to indicate the RRC state that the terminal device expects to transition to, which is not specifically limited in the embodiment of the present application.

In FIG. 7, the RAI message can use other n bits to indicate the target duration, and n is an integer greater than zero.

As another example, the RRC state that the terminal device expects to transition to can be indicated by the logical channel group identity (LCD ID). The embodiment of this application can define two new logical channel IDs to respectively identify the RRC idle state and the RRC inactive state that the terminal device expects to transition to. The network device can also identify the terminal device according to the logical channel used by the received RAI message The RRC state you want to transition to. For example, the terminal device may indicate the desire to transition to the RRC idle state through the first logical channel, and indicate the desire to transition to the RRC inactive state through the second logical channel. When the terminal device expects to switch to the RRC idle state, the terminal device can use the first logical channel to send the RAI message. When the network device receives the RAI message sent by the terminal device on the first logical channel, the network device can determine that the terminal device expects to switch to RRC idle state; when the terminal device expects to switch to the RRC inactive state, the terminal device can use the second logical channel to send the RAI message, and the network device can determine when the network device receives the RAI message sent by the terminal device on the second logical channel The terminal device expects to switch to the RRC inactive state.

As shown in FIG. 6, the RAI message can be represented in format 1. In this case, the bits in the RAI message only need to indicate the target duration.

Figures 6 and 7 are only examples of the two formats of the RAI message, but do not determine the size of the field indicating the target duration in the RAI message, the field indicating the state that the terminal device expects to transition to, and the location of the field indicating the target duration. Cause limitations. For example, the field indicating the RRC state that the terminal device expects to transition to may be located before, after, in the middle, or any position of the field indicating the target duration.

The RRC state that the terminal device expects to transition to can be determined according to the terminal device's own implementation.

After the network device receives the RAI message sent by the terminal device, it determines whether to move the terminal device out of the connected state based on its own estimation of the terminal device's downlink service activity and the target duration indicated in the RAI message. If the network device decides to move the terminal device out of the connected state, the network device can switch the state of the terminal device to the state expected by the terminal device according to the RRC state that the terminal device expects to switch to. If the RAI message does not carry the RRC that the terminal device expects to switch to State, the network device can switch the terminal device to any non-connected state.

In the embodiments of this application, the RAI message can be used to replace the sending of the zero BSR, or the RAI message can also be sent together with the zero BSR.

As an example, the terminal device needs to send the RAI message while sending the BSR, the terminal device may only send the RAI message without sending the BSR. In this case, due to the sending of RAI, the terminal device can cancel the triggered BSR, that is, the RAI message can be used to indicate that the amount of data currently to be transmitted by the terminal device is zero.

For example, taking the RAI message using the MAC CE bearer as an example, the terminal device needs to send the RAI MAC CE while sending the zero BSR. The zero BSR may be a periodic BSR or a padding BSR. The terminal device can use the RAI MAC CE to replace the BSR MAC CE, that is, the terminal device cancels the sending of the zero BSR. In this way, RAI MAC CE and BSR MAC CE have the same priority. When the terminal device sends the RAI MAC CE, it can determine the sending order of the RAI MAC CE and other MAC CEs according to the priority relationship between the BSR MAC CE and other MAC CEs to be sent.

As another example, the RAI message can be sent simultaneously with the zero BSR. Take RAI messages using MAC CE as an example. In this mode, the priority of RAI MAC CE is higher than that of BSR MAC CE, and the priority relationship of other uplink transmissions remains unchanged. In other words, when the uplink resources are sufficient to carry the RAI message and BSR, the terminal device sends the RAI message and the BSR at the same time; when the uplink resources are insufficient to carry the RAI message and the BSR, the priority of sending the RAI message is higher than that of the BSR. Send priority.

Specifically, the terminal device can send according to the following rules:

When the terminal device sends a RAI message to the network device and there is a triggered BSR, if the size of the uplink resources currently allocated to the terminal device can meet the resources required for the simultaneous transmission of the RAI message and the BSR, the terminal device is on the current resource Simultaneous transmission of RAI messages and BSR. Otherwise, if the current uplink resource size allocated to the terminal device can only meet the resources required to transmit RAI messages, but cannot meet the resources required to transmit RAI messages and BSR simultaneously, the terminal device will only transmit RAI messages on the current resources. No BSR is transmitted.

When a terminal device sends a RAI message, whether or not it sends a BSR at the same time, it can cancel the triggered BSR at this time.

The RAI message in the embodiment of the present application is only a schematic description, and may also be referred to as other messages. As long as the RAI message achieves the same function as the RAI message, it is included in the protection scope of the present application.

The foregoing describes in detail the method for sending release assistance indication information according to the embodiment of the present application. The device according to the embodiment of the present application will be described below in conjunction with FIG. 8 to FIG. 12. The technical features described in the method embodiment are applicable to the following Device embodiment.

FIG. 8 is a schematic block diagram of a terminal device provided by an embodiment of the present application. The terminal device may be any terminal device described above. The terminal device 800 in FIG. 8 includes a processing unit 810, where:

The processing unit 810 is configured to determine whether to send a release assistance instruction message to the network device according to the amount of data to be transmitted in all logical channel groups, where the release assistance instruction message is used by the network device to determine whether it needs to disconnect from the The radio resource of the terminal device controls the RRC connection.

Optionally, the processing unit 810 is configured to send a release assistance instruction message to the network device when the amount of data to be transmitted in all the logical channel groups is zero.

Optionally, that the amount of data to be transmitted is zero includes that the amount of data to be transmitted currently is zero, and the amount of data to be transmitted within the first time period is zero.

Optionally, the processing unit 810 is configured to send the release assistance instruction message to the network device when the first duration is not less than the minimum duration of at least one duration; In the case of the minimum duration of the at least one duration, the release assistance indication message is not sent to the network device; wherein, the first duration is that none of the logical channel groups predicted by the terminal device are to be transmitted For the duration of the data, the at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.

Optionally, the processing unit 810 is configured to: when the buffer status report BSR is triggered and the amount of data to be transmitted in all the logical channel groups is zero, send the release assistance to the network device Indicates the message.

Optionally, the time interval between two consecutive release assistance indication messages sent by the terminal device to the network device is greater than or equal to the duration of a first timer, and the first timer may be for sending a release assistance indication to the terminal device The time interval of the message is set.

Optionally, the processing unit 810 is configured to send the release assistance indication message to the network device when the amount of data to be transmitted is zero and the first timer expires; and/or, When the amount of data to be transmitted in all the logical channel groups is zero and the first timer has not expired, the release assistance indication message is not sent to the network device, and the first timer It is started when the terminal device sends the release assistance instruction message last time.

Optionally, the at least one duration and/or the first timer are configured by the network device to the terminal device through RRC signaling.

Optionally, the release assistance indication message is carried in a media access control unit MAC CE or RRC signaling.

Optionally, the release assistance indication message includes the target duration and/or the RRC state that the terminal device expects to transition to, and the RRC state that the terminal device expects to transition to includes the RRC idle state and/or the RRC inactive state, The target duration is used to indicate the duration when the terminal device has no data to be transmitted.

Optionally, the target duration is a duration predicted by the terminal device that there is no data to be transmitted.

Optionally, the target duration is a maximum duration that does not exceed a first duration among at least one duration, and the first duration is a duration during which all logical channel groups predicted by the terminal device have no data to be transmitted, so The at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.

Optionally, the RRC state that the terminal device expects to transition to is indicated by one or more bits in the release assistance indication message and/or the identifier of the logical channel carrying the release assistance indication message.

Optionally, the processing unit 810 is configured to: in the case of sending the release assistance indication message to the network device, there is no need to send a buffer status report BSR to the network device.

Optionally, the terminal device further includes a communication unit 820, configured to send the release assistance indication message to the network device and there is a triggered BSR, if the uplink resource can simultaneously carry the release assistance indication Message and BSR to send the triggered BSR to the network device.

Optionally, in a case where uplink resources are insufficient to carry the release assistance indication message and the BSR at the same time, the sending priority of the release assistance indication message is higher than the sending priority of the BSR.

Optionally, the processing unit 810 is configured to: when sending the release assistance indication message to the network device, and when the uplink resources are insufficient to carry the release assistance indication message and the BSR at the same time, cancel the triggered BSR.

Optionally, the amount of data to be transmitted includes the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.

FIG. 9 is a schematic block diagram of a network device provided by an embodiment of the present application. The network device may be any of the network devices described above. The network device 900 in FIG. 9 includes a communication unit 910 and a processing unit 920, where:

The communication unit 910 is configured to receive a release assistance instruction message sent by a terminal device;

The processing unit 920 is configured to determine whether the radio resource control RRC connection with the terminal device needs to be disconnected according to the release assistance instruction message.

Optionally, the communication unit 910 is further configured to configure at least one duration to the terminal device, and the minimum duration of the at least one duration is used by the terminal device to determine whether it is necessary to send the release to the network device. Auxiliary instruction message.

Optionally, the communication unit 910 is further configured to receive a buffer status report BSR sent by the terminal device.

Optionally, the time interval for the network device to receive two consecutive release assistance indication messages sent by the terminal device is greater than the duration of a first timer, and the first timer may be for the terminal device to send release assistance indication messages The time interval is set.

Optionally, the communication unit 910 is further configured to configure a first timer for the terminal device, and the first timer is used for the terminal device to determine a time interval for sending a release assistance instruction message to the network device.

Optionally, the processing unit 920 is further configured to not receive the BSR sent by the terminal device in the case of receiving the release assistance instruction message sent by the terminal device.

Optionally, the communication unit 910 is further configured to: in the case of receiving the release assistance instruction message sent by the terminal device, further receive the BSR sent by the terminal device.

FIG. 10 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present application. The communication device 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 10, the communication device 1000 may further include a memory 1020. The processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

The memory 1020 may be a separate device independent of the processor 1010, or it may be integrated in the processor 1010.

Optionally, as shown in FIG. 10, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 1000 may specifically be a network device of an embodiment of the application, and the communication device 1000 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For brevity, details are not repeated here .

Optionally, the communication device 1000 may specifically be a mobile terminal/terminal device of an embodiment of the present application, and the communication device 1000 may implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For simplicity , I won’t repeat it here.

Fig. 11 is a schematic structural diagram of a device according to an embodiment of the present application. The apparatus 1100 shown in FIG. 11 includes a processor 1110, and the processor 1110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11, the apparatus 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

The memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.

Optionally, the device 1100 may further include an input interface 1130. The processor 1110 can control the input interface 1130 to communicate with other devices or devices, and specifically, can obtain information or data sent by other devices or devices.

Optionally, the device 1100 may further include an output interface 1140. The processor 1110 can control the output interface 1140 to communicate with other devices or devices, and specifically, can output information or data to other devices or devices.

Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For brevity, details are not described herein again.

Optionally, the device can be applied to the mobile terminal/terminal device in the embodiment of this application, and the device can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of this application. For brevity, here is No longer.

It should be understood that the device mentioned in the embodiments of the present application may be a chip, and the chip may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-chip.

FIG. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application. As shown in FIG. 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.

Wherein, the terminal device 1210 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 1220 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I will not repeat it here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. In response to this understanding, the technical solution of this application essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A method for sending a release assistance indication message, characterized in that it comprises:

The terminal device determines whether to send a release assistance instruction message to the network device according to the amount of data to be transmitted in all logical channel groups. The release assistance instruction message is used by the network device to determine whether it needs to disconnect the wireless connection with the terminal device. Resource control RRC connection.
The method according to claim 1, wherein the terminal device determines whether to send a release assistance instruction message to the network device according to the amount of data to be transmitted in all logical channel groups, comprising:

The terminal device sends a release assistance instruction message to the network device when the amount of data to be transmitted in all logical channel groups is zero.
The method according to claim 2, wherein said zero amount of data to be transmitted includes zero amount of data to be transmitted currently and zero amount of data to be transmitted within a preset time period.
The method according to any one of claims 1 to 3, wherein the terminal device determines whether to send a release assistance indication message to the network device according to the amount of data to be transmitted in all logical channel groups, comprising:

Sending, by the terminal device, the release assistance instruction message to the network device when the first duration is not less than the minimum duration among at least one duration;

The terminal device does not send the release assistance instruction message to the network device when the first duration is less than the minimum duration of the at least one duration;

Wherein, the first duration is the duration for which all logical channel groups predicted by the terminal device have no data to be transmitted, and the at least one duration is configured by the network device for the terminal device, or the at least one duration It is a predefined duration.
The method according to any one of claims 1-4, wherein the terminal device determines whether to send a release assistance indication message to the network device according to the amount of data to be transmitted in all logical channel groups, comprising:

The terminal device sends the release assistance indication message to the network device when the buffer status report BSR is triggered and the amount of data to be transmitted in all logical channel groups is zero.
The method according to any one of claims 1 to 4, wherein the time interval between two consecutive release assistance indication messages sent by the terminal device to the network device is greater than or equal to the duration of the first timer, The first timer is set for the time interval for the terminal device to send the release assistance instruction message.
The method according to any one of claims 1-4 and 6, wherein the terminal device determines whether to send a release assistance instruction message to the network device according to the amount of data to be transmitted in all logical channel groups, including :

When the amount of data to be transmitted in the all logical channel groups is zero and the first timer expires, the terminal device sends the release assistance indication message to the network device; and/or,

When the amount of data to be transmitted in the all logical channel groups is zero and the first timer has not expired, the terminal device does not send the release assistance indication message to the network device, and The first timer is started when the terminal device sends the release assistance instruction message last time.
The method according to any one of claims 4, 6, and 7, wherein the at least one duration and/or the first timer is configured by the network device to the terminal device through RRC signaling of.
The method according to any one of claims 1-8, wherein the release auxiliary indication message is carried in a media access control unit MAC CE or RRC signaling.
The method according to any one of claims 1-9, wherein the release assistance indication message includes the target duration and/or the RRC state that the terminal device expects to transition to, and the terminal device expects to transition to The RRC state includes an RRC idle state and/or an RRC inactive state, and the target duration is used to indicate the duration when the terminal device has no data to be transmitted.
The method according to claim 10, wherein the target duration is a duration predicted by the terminal device that there is no data to be transmitted.
The method according to claim 10, wherein the target duration is a maximum duration that does not exceed a first duration among at least one duration, and the first duration is the average of all logical channel groups predicted by the terminal device. There is no duration of data to be transmitted, the at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.
The method according to any one of claims 10-12, wherein the RRC state that the terminal device expects to transition to is determined by one or more bits in the release assistance indication message and/or bearer The release of the auxiliary indication message is indicated by the identifier of the logical channel.
The method according to any one of claims 1-13, wherein the method further comprises:

When the terminal device sends the release assistance instruction message to the network device, it does not need to send the buffer status report BSR to the network device.
The method according to any one of claims 1-13, wherein the method further comprises:

When the terminal device sends the release assistance indication message to the network device and the BSR has been triggered, if the uplink resource can carry the release assistance indication message and the BSR at the same time, the terminal device sends the Send the triggered BSR.
The method according to any one of claims 1-13, wherein when uplink resources are insufficient to carry both the release assistance indication message and the BSR, the sending priority of the release assistance indication message is higher than The sending priority of the BSR.
The method according to any one of claims 1-13 and 16, wherein the method further comprises:

The terminal device cancels the triggered BSR when the terminal device sends the release assistance indication message to the network device, and when uplink resources are insufficient to carry the release assistance indication message and the BSR at the same time.
The method according to any one of claims 1-17, wherein the amount of data to be transmitted includes the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.
A method for sending a release assistance indication message, characterized in that it comprises:

The network device receives the release assistance instruction message sent by the terminal device;

The network device determines whether the radio resource control RRC connection with the terminal device needs to be disconnected according to the release assistance instruction message.
The method of claim 19, wherein the method further comprises:

The network device configures the terminal device with at least one duration, and the minimum duration of the at least one duration is used by the terminal device to determine whether it is necessary to send the release assistance instruction message to the network device.
The method according to claim 19 or 20, wherein the method further comprises:

The network device receives the buffer status report BSR sent by the terminal device.
The method according to any one of claims 19-21, wherein the time interval for the network device to receive two consecutive release assistance indication messages sent by the terminal device is greater than the duration of the first timer, and The first timer is set for the time interval for the terminal device to send the release assistance instruction message.
The method according to any one of claims 19-22, wherein the method further comprises:

The network device configures a first timer for the terminal device, where the first timer is used by the terminal device to determine a time interval for sending a release assistance instruction message to the network device.
The method according to any one of claims 20, 22, 23, wherein the at least one duration and/or the first timer is configured by the network device to the terminal device through RRC signaling of.
The method according to any one of claims 19-24, wherein the release assistant indication message is carried in a media access control unit MAC CE or RRC signaling.
The method according to any one of claims 19-25, wherein the release assistance indication message includes a target duration and/or an RRC state that the terminal device expects to transition to, and the terminal device expects to transition to The RRC state includes an RRC idle state and/or an RRC inactive state, and the target duration is used to indicate the duration when the terminal device has no data to be transmitted.
The method according to claim 26, wherein the target duration is a duration predicted by the terminal device that there is no data to be transmitted.
The method according to claim 26, wherein the target duration is a maximum duration that does not exceed a first duration among at least one duration, and the first duration is the average of all logical channel groups predicted by the terminal device. There is no duration of data to be transmitted, the at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.
The method according to any one of claims 26-28, wherein the RRC state that the terminal device expects to transition to is determined by one or more bits in the release assistance indication message, and/or bearer The release of the auxiliary indication message is indicated by the identifier of the logical channel.
The method according to any one of claims 19-29, wherein the method further comprises:

When the network device receives the release assistance instruction message sent by the terminal device, it does not receive the BSR sent by the terminal device.
The method according to any one of claims 19-29, wherein the method further comprises:

In the case of receiving the release assistance instruction message sent by the terminal device, the network device also receives the BSR sent by the terminal device.
The method according to any one of claims 19-31, wherein the amount of data to be transmitted includes the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.
A terminal device, characterized in that it comprises:

The processing unit is configured to determine whether to send a release assistance instruction message to the network device according to the amount of data to be transmitted in all logical channel groups, where the release assistance instruction message is used by the network device to determine whether it needs to disconnect from the terminal The radio resource of the device controls the RRC connection.
The terminal device according to claim 33, wherein the processing unit is configured to:

In a case where the amount of data to be transmitted in all the logical channel groups is zero, sending a release assistance instruction message to the network device.
The terminal device according to claim 34, wherein said zero amount of data to be transmitted includes zero amount of data to be transmitted currently and zero amount of data to be transmitted within a preset time period.
The terminal device according to any one of claims 33-35, wherein the processing unit is configured to:

In the case that the first duration is not less than the minimum duration among at least one duration, sending the release assistance instruction message to the network device;

In a case where the first duration is less than the minimum duration among the at least one duration, not sending the release assistance instruction message to the network device;

The first duration is the duration predicted by the terminal device that all logical channel groups have no data to be transmitted, and the at least one duration is configured by the network device for the terminal device, or the at least A duration is a predefined duration.
The terminal device according to any one of claims 33-36, wherein the processing unit is configured to:

When the buffer status report BSR is triggered, and the amount of data to be transmitted in all the logical channel groups is zero, the release assistance indication message is sent to the network device.
The terminal device according to any one of claims 33-36, wherein the time interval between two consecutive release assistance indication messages sent by the terminal device to the network device is greater than or equal to the duration of the first timer The first timer is set for the time interval for the terminal device to send the release assistance instruction message.
The terminal device according to any one of claims 33-36 and 38, wherein the processing unit is configured to:

When the amount of data to be transmitted in all the logical channel groups is zero and the first timer expires, sending the release assistance indication message to the network device; and/or,

When the amount of data to be transmitted in all the logical channel groups is zero and the first timer has not expired, the release assistance indication message is not sent to the network device, and the first timer It is started when the terminal device sends the release assistance instruction message last time.
The terminal device according to any one of claims 35, 38, 39, wherein the at least one duration and/or the first timer is configured by the network device to the terminal through RRC signaling equipment.
The terminal device according to any one of claims 33-40, wherein the release assistance indication message is carried in a media access control unit MAC CE or RRC signaling.
The terminal device according to any one of claims 33-41, wherein the release assistance indication message includes a target duration and/or an RRC state that the terminal device expects to transition to, and the terminal device expects to transition to The obtained RRC state includes an RRC idle state and/or an RRC inactive state, and the target duration is used to indicate a duration during which the terminal device has no data to be transmitted.
The terminal device according to claim 42, wherein the target duration is a duration predicted by the terminal device that there is no data to be transmitted.
The terminal device according to claim 42, wherein the target duration is a maximum duration of at least one duration that does not exceed a first duration, and the first duration is all logical channel groups predicted by the terminal device There is no duration of data to be transmitted, the at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.
The terminal device according to any one of claims 42-44, wherein the RRC state that the terminal device expects to transition to is determined by one or more bits in the release assistance indication message, and/or bearer The release of the auxiliary indication message is indicated by the identifier of the logical channel.
The terminal device according to any one of claims 33-45, wherein the processing unit is configured to:

In the case of sending the release assistance instruction message to the network device, there is no need to send the buffer status report BSR to the network device.
The terminal device according to any one of claims 33-45, wherein the terminal device further comprises a communication unit, configured to:

In the case where the release assistance indication message is sent to the network device and the BSR has been triggered, if the uplink resource can carry the release assistance indication message and the BSR at the same time, the triggered BSR is sent to the network device.
The terminal device according to any one of claims 33-45, wherein when uplink resources are insufficient to carry the release assistance indication message and the BSR at the same time, the sending priority of the release assistance indication message is high The sending priority of the BSR.
The terminal device according to any one of claims 33-45 and 48, wherein the processing unit is configured to:

Sending the release assistance indication message to the network device, and in the case that uplink resources are insufficient to carry the release assistance indication message and the BSR at the same time, cancel the triggered BSR.
The terminal device according to any one of claims 33-49, wherein the amount of data to be transmitted includes the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.
A network device, characterized by comprising:

The communication unit is used to receive the release assistance instruction message sent by the terminal device;

The processing unit is configured to determine whether the radio resource control RRC connection with the terminal device needs to be disconnected according to the release assistance instruction message.
The network device according to claim 51, wherein the communication unit is further configured to:

At least one duration is configured for the terminal device, and the minimum duration among the at least one duration is used by the terminal device to determine whether it is necessary to send the release assistance instruction message to the network device.
The network device according to claim 51 or 52, wherein the communication unit is further configured to:

Receiving the buffer status report BSR sent by the terminal device.
The network device according to any one of claims 51-53, wherein the time interval for the network device to receive two consecutive release assistance indication messages sent by the terminal device is greater than the duration of the first timer, so The first timer is set for the time interval for the terminal device to send the release assistance instruction message.
The network device according to any one of claims 51-53, wherein the communication unit is further configured to:

A first timer is configured for the terminal device, where the first timer is used for the terminal device to determine a time interval for sending a release assistance instruction message to the network device.
The network device according to any one of claims 52, 54, 55, wherein the at least one duration and/or the first timer is configured by the network device to the terminal through RRC signaling equipment.
The network device according to any one of claims 52-56, wherein the release assistance indication message is carried in a media access control unit MAC CE or RRC signaling.
The network device according to any one of claims 52-57, wherein the release assistance indication message includes the target duration and/or the RRC state that the terminal device expects to transition to, and the terminal device expects to transition to The obtained RRC state includes an RRC idle state and/or an RRC inactive state, and the target duration is used to indicate a duration during which the terminal device has no data to be transmitted.
The network device according to claim 58, wherein the target duration is a duration predicted by the terminal device that there is no data to be transmitted.
The network device according to claim 58, wherein the target duration is a maximum duration of at least one duration that does not exceed a first duration, and the first duration is all logical channel groups predicted by the terminal device There is no duration of data to be transmitted, the at least one duration is configured by the network device to the terminal device, or the at least one duration is a predefined duration.
The network device according to any one of claims 58-60, wherein the RRC state that the terminal device expects to transition to is determined by one or more bits in the release assistance indication message, and/or bearer The release of the auxiliary indication message is indicated by the identifier of the logical channel.
The network device according to any one of claims 51-61, wherein the processing unit is further configured to:

In the case of receiving the release assistance instruction message sent by the terminal device, the BSR sent by the terminal device is not received.
The network device according to any one of claims 51-61, wherein the communication unit is further configured to:

In the case of receiving the release assistance instruction message sent by the terminal device, the BSR sent by the terminal device is also received.
The network device according to any one of claims 51-63, wherein the amount of data to be transmitted includes the amount of uplink data to be transmitted and/or the amount of downlink data to be transmitted.
A terminal device, characterized in that the terminal device includes a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute claim 1. The method of any one of to 18.
A network device, wherein the network device comprises a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute claim 19 To the method of any one of 32.
A communication device, characterized in that the communication device includes a processor, the processor is used to call and run a computer program from a memory, so that the equipment installed with the communication device executes any one of claims 1 to 18 The method described.
A communication device, characterized in that the communication device includes a processor, the processor is used to call and run a computer program from a memory, so that the equipment installed with the communication device executes any one of claims 19 to 32 The method described.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 1 to 18.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 19 to 32.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 18.
A computer program product, characterized by comprising computer program instructions that cause a computer to execute the method according to any one of claims 19 to 32.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 18.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 19 to 32.
A communication system, characterized by comprising the terminal equipment according to any one of claims 1 to 18.
A communication system, characterized by comprising the network equipment according to any one of claims 19 to 32.