WO2020043211A1 - Rrc连接释放方法、相关设备及系统 - Google Patents

Rrc连接释放方法、相关设备及系统 Download PDF

Info

Publication number
WO2020043211A1
WO2020043211A1 PCT/CN2019/103889 CN2019103889W WO2020043211A1 WO 2020043211 A1 WO2020043211 A1 WO 2020043211A1 CN 2019103889 W CN2019103889 W CN 2019103889W WO 2020043211 A1 WO2020043211 A1 WO 2020043211A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
terminal
rrc
rrc connection
connection release
Prior art date
Application number
PCT/CN2019/103889
Other languages
English (en)
French (fr)
Inventor
徐海博
才宇
何彦召
王键
刘海涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020043211A1 publication Critical patent/WO2020043211A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to an RRC connection release method, related equipment, and system.
  • the radio resource control (RRC) state of a user equipment (UE) includes two types: RRC connected state (RRC_CONNECTED) and RRC idle state (RRC_IDLE). .
  • RRC connected state RRC_CONNECTED
  • RRC idle state RRC_IDLE
  • the UE When the UE has no service, the UE will be in an RRC idle state.
  • the UE When the UE has a service, the UE needs to transition to the RRC connected state for data transmission. Compared with the RRC connected state, the UE saves more power in the RRC idle state.
  • RRC_CONNECTED based on two RRC states: RRC_CONNECTED and RRC_IDLE
  • RRC_INACTIVE an RRC inactive state
  • the behavior of the UE in the RRC inactive state is basically the same as the behavior in the RRC idle state. Therefore, the UE has the same energy saving effect in the RRC inactive state and the RRC idle state, that is, it is more effective than the UE in the RRC connected state Save power.
  • the base station may send an RRC connection release message / RRC release message (RRCConnectionRelease / RRCRelease) to the UE to initiate an RRC connection release process for the UE.
  • RRC connection release message / RRC release message RRCConnectionRelease / RRCRelease
  • the UE can release the RRC connection and transition from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state.
  • the UE quickly enters the RRC_CONNECTED state again.
  • the prior art does not allow the UE in the RRC_CONNECTED state to transition to the RRC_IDLE state / RRC_INACTIVE state as soon as possible after ending the service transmission, but to continue to maintain the RRC_CONNECTED state for a period of time. This is not conducive to reducing UE power consumption.
  • This application provides an RRC connection release method, related equipment and system, which can save terminal power consumption.
  • the present application provides an RRC connection release method, which is applied to a terminal side.
  • the method may include: the terminal triggers an RRC connection release request and sends a first MAC CE to a network device.
  • the first MAC CE carries first instruction information, and the first instruction information instructs the first MAC CE to request the network device to initiate an RRC connection release process.
  • the terminal may trigger an RRC connection release request under a condition that a trigger condition of the RRC connection release request is satisfied.
  • the essence of the trigger condition of the RRC connection release request is the end of the terminal service. That is, once the terminal determines that the terminal service is over, it can trigger an RRC connection release request.
  • the present application provides an RRC connection release method applied to a network device side.
  • the method may include: the network device receives a first MAC CE sent by the terminal, and may determine to send the first MAC to the terminal according to the first MAC CE CE.
  • the terminal can release the RRC connection and transition from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • the network device may decide to immediately initiate an RRC connection release process for the terminal.
  • the network device may also wait for a short time (such as 30-50 ms) before deciding to initiate the RRC connection release process of the terminal.
  • the network device may wait for the terminal to receive one or several small downlink data packets before deciding to initiate the release of the RRC connection of the terminal.
  • Implementing the methods provided in the first aspect and the second aspect can enable the terminal in the RRC connected state to switch to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, instead of waiting for a period of time after the counter timeout
  • the RRC idle state or the RRC inactive state is beneficial to reducing the power consumption of the terminal.
  • the trigger condition of the RRC connection release request may include:
  • the first trigger condition the terminal has no service to transmit in the near future. Once the terminal determines that no service needs to be transmitted for a period of time after the current time, the terminal triggers an RRC connection release request. In this application, this period of time may be referred to as the first time, and the first time may be 20-30s, or other values.
  • the second trigger condition the uplink data currently transmitted by the terminal is the last uplink data packet of the current service. Once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, the terminal triggers an RRC connection release request.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal will not receive downlink data packets after sending the last uplink data packet.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal needs to receive another downlink data packet after sending the last uplink data packet.
  • the terminal transmits the last uplink data packet: the terminal no longer receives the downlink data packet, or the terminal needs to receive another downlink data packet.
  • the second case it is not limited to one downlink data packet, and may also be a downlink data packet that is less than the first data amount (that is, a small amount).
  • the data packet of the first data amount may include one, or two, or three or more downlink data packets. That is, once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, and the terminal needs to receive a small number of downlink data packets after sending the last uplink data packet, the terminal can trigger an RRC connection release request.
  • the small amount of offline data packets may be response data packets for the last uplink data packet, such as ACK / NACK.
  • the specific implementation of the terminal triggering the RRC connection release request may include the following methods:
  • a high-level protocol layer such as an application layer or a PDCP layer
  • the high-level protocol layer passes the instruction information to the MAC layer.
  • the MAC layer triggers an RRC connection release request.
  • this instruction information may be referred to as fifth instruction information.
  • the MAC layer determines that the terminal does not need to transmit services in the near future. Once the MAC layer determines that no service needs to be transmitted for a period of time after the current time, the MAC layer triggers an RRC connection release request.
  • the terminal can determine that near future has no service at the high-level protocol layer, and transmit the indication information to the MAC layer, and then trigger an RRC connection release request at the MAC layer.
  • the terminal may also trigger an RRC connection release request and trigger an RRC connection release request at the MAC layer.
  • the terminal may also determine that there is no service in near future by other methods, which is not limited in this application.
  • the specific implementation of the terminal triggering the RRC connection release request may include the following ways:
  • a high-level protocol layer such as an application layer or a PDCP layer, may be used to determine whether the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and transmit the indication information to the MAC layer.
  • the MAC layer receives the instruction, the MAC layer triggers an RRC connection release request.
  • the high-level protocol layer may send instruction information to the MAC layer, and the instruction information is used to notify the MAC layer of the current There will be no downlink data after the last uplink data packet of the service.
  • this instruction information may be referred to as sixth instruction information.
  • the MAC layer receives the sixth instruction information, the MAC layer triggers an RRC connection release request.
  • the higher-layer protocol layer may send instruction information to the MAC layer, and the instruction information is used to notify the MAC layer After the last uplink data packet of the current service, there will be a small amount of downlink data, such as a downlink data packet.
  • this instruction information may be referred to as seventh instruction information.
  • the MAC layer receives the seventh indication information, the MAC layer triggers an RRC connection release request.
  • the higher-level protocol layer needs to send the sixth indication information or the seventh indication information to the MAC layer only after it is determined that other uplink PDCP, SDU, or uplink PDCP PDUs have been correctly transmitted.
  • a high-level protocol layer such as an application layer or a PDCP layer, may be used to determine whether the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and transmit the indication information to the MAC layer.
  • the MAC layer receives the instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request.
  • the high-level protocol layer may send the sixth indication information to the MAC layer.
  • the MAC layer receives the sixth instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request.
  • the high-level protocol layer (such as the PDCP layer) determines that the above-mentioned second case (case 2) of the second triggering condition is satisfied, the high-level protocol layer may send the seventh indication information to the MAC layer.
  • the MAC layer receives the seventh instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request.
  • the terminal is not limited to the above two methods, and the terminal may also determine that the foregoing second trigger condition is satisfied by other methods, which is not limited in this application.
  • the specific implementation of the first MAC CE may be as follows:
  • the first MAC CE can be implemented by reusing the BSR MAC CE defined in the existing protocol.
  • the first indication information carried in the first MAC CE may indicate that the first MAC CE is a special BSR MAC CE, and the first MAC CE is used for RRC The MAC CE of the connection release request, that is, the MAC CE for RRC Connection Release Request.
  • the first indication information may include: an LCID field in which the value of the MAC subheader corresponding to the BSR MAC CE is a reserved LCID value (such as a value or a range of values in 100010–110100). And / or, the reserved bit R of the MAC subheader corresponding to the BSR MAC CE is set to a first value (such as 1). That is to say, the reserved LCID value or reserved bit R in the MAC subheader corresponding to the existing BSR MAC CE can be used to indicate that the BSR MAC CE is a special MAC CE, which is used for RRC connection release request, that is, MAC CE for RRC ConnectionReleaseRequest.
  • the value of the buffer size field in the BSR MAC CE is 0; the LCG ID field in the BSR MAC CE The value can be the ID of any LCG terminated, or the ID of the LCG containing the logical channel with the highest priority, or 0.
  • the BSR MAC may include only one bitmap byte, and the value of each bit in the bitmap byte Both are 0, indicating that there is no data buffer in the logical channel group corresponding to each bit. It can be seen that, since the buffer size field in the existing BSR MAC and CE is omitted, the first MAC CE can save bit overhead.
  • the first indication information may further include: a buffer size field that is set to a buffer size reserved value (that is, 255). That is to say, it is also possible to use the reserved buffer size value in the existing long BSR format or long truncated BSR format BSR MAC CE to indicate that the BSR MAC CE is a special MAC CE for RRC connection release request, that is, MAC CE for RRC Connection Release Request.
  • the BSR MAC CE may include only a bitmap byte and a buffer size field.
  • the first MAC CE may be a newly defined MAC CE.
  • the bit length of the newly defined MAC CE may be fixed to 0 bits; the first indication information carried in the first MACCE may include: a value in the MAC subheader corresponding to the newly defined MAC CE is reserved for LCID LCID field of a value (such as a value or a range of values in 100010-110100), and / or, a reserved bit R having a first value (such as 1) in a MAC subheader corresponding to the newly defined MAC CE. That is, the reserved LCID value or the reserved bit R in the MAC subheader may be used to indicate that the first MAC CE is used for the RRC connection release request.
  • the first MAC CE may carry the second indication information to indicate the RRC state to which the terminal preference is transferred.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the second indication information may include but is not limited to the following two implementation manners:
  • the second indication information may be a first indication bit in a MAC subheader corresponding to the newly defined MAC CE.
  • the value of the first indicator bit is the third value (such as 1), it indicates that the RRC state to which the terminal preference is transferred is the RRC idle state.
  • the value of the first indicator bit is the fourth value (such as 0), it indicates that The RRC state to which the terminal preference is transferred is the RRC inactive state.
  • a certain bit in the MAC subheader corresponding to the newly defined MAC CE (such as the reserved bit R as an indication bit) may be used to indicate the RRC state to which the terminal prefers to transition.
  • the second indication information may be the LCID field in the MAC subheader. When the value of the LCID field is the first
  • LCID value When a LCID value is reserved, it indicates that the RRC state that the terminal preference is transferred to is the RRC idle state. When the value of the LCID field is the second reserved LCID value, it indicates that the RRC state that the terminal preference is transferred to is the RRC inactive state.
  • the reserved LCID value in the LCID field in the MAC subheader can be used to indicate the RRC state to which the terminal preference is transferred.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE, but also indicate the RRC state to which the terminal preference is transferred.
  • the first MAC CE may carry third instruction information to indicate whether the terminal needs to receive another downlink data packet or does not need to receive a downlink data packet after sending the last uplink data packet.
  • the third indication information may include but is not limited to the following two implementation manners:
  • the third indication information may be a second indication bit in the MAC subheader.
  • the value of the second indicator bit is the fifth value (such as 1), it means that the terminal needs to receive another downlink data after sending the last uplink data; when the value of the second indicator bit is the sixth value (such as 0) , It means that the terminal does not need to receive downlink data after sending the last uplink data.
  • a bit in the MAC subheader corresponding to the existing BSR MAC and CE can be used to distinguish between case1 and case2 that indicate the second triggering condition.
  • the third indication information may be an LCID field in the MAC subheader.
  • the terminal When the value of the LCID field is the third reserved LCID value, it means that the terminal needs to receive another downlink data packet after sending the last uplink data packet; when the value of the LCID field is the fourth reserved LCID value, it means the terminal There is no need to receive a downlink data packet after sending the last uplink data packet.
  • the reserved LCID value in the LCID field in the MAC subheader corresponding to the existing BSR MAC and CE can be used to indicate the case 1 and case 2 of the second trigger condition.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE, but can also distinguish case1 and case2 indicating the second triggering condition at the same time.
  • the first MAC CE can both indicate the RRC state that the terminal prefers to transition to, and also indicate that the terminal needs to receive a downlink data packet or does not need to receive a downlink data packet after sending the last uplink data.
  • the first MAC CE may carry the first indication bit and the second indication bit at the same time, and the first indication bit and the second indication bit are two different indication bits in the MAC subheader.
  • bit I is the first indication bit, which is used to indicate the RRC state to which the terminal prefers to transition
  • bit D is the second indication bit, which is used to distinguish between case1 and case2, which indicate the second triggering condition
  • One of the reserved LCID values (such as 100011 in 100010-110100) or a range of values in the table shown at 9.
  • Bits I and D may be reserved bits R in the MAC subheader.
  • the first MAC CE may carry fourth instruction information, the fourth instruction information indicates the RRC state to which the terminal prefers to transition, and the terminal needs to receive another downlink data packet or no longer needs to be sent after the last uplink data is sent. Receive downlink packets.
  • the fourth indication information is the LCID field in the MAC subheader, which may indicate the following four cases:
  • the value of the LCID field is the fifth reserved LCID value (such as 100010 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC idle state and the terminal needs to receive another downlink after sending the last uplink data. data;
  • the value of the LCID field is the sixth reserved LCID value (such as 100011 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC inactive state and the terminal needs to receive one after sending the last uplink data.
  • the sixth reserved LCID value such as 100011 in 100010–110100
  • the value of the LCID field is the seventh reserved LCID value (such as 100100 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC idle state and the terminal does not need to receive downlink data after sending the last uplink data. ;
  • the value of the LCID field is the eighth reserved LCID value (such as 100101 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC inactive state and the terminal does not need to receive the downlink after sending the last uplink data data.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE of other functions, but also indicate any one of the above four cases.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following items: C-RNTI MAC, CE, Configured Grant, MAC, CE, BSR, MAC, CE, PHR, MAC except CE, PHR, MAC, CE, and data from any logical channel except data from UL-CCCH.
  • the first MAC CE can be prevented from preempting the resources carrying the data, and the data can be transmitted normally.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following items: C-RNTI MAC, CE, Configured Grant Confirmation MAC CE, BSR MAC CE other than BSR MAC MAC for padding.
  • the terminal if the terminal does not have sufficient uplink resources for carrying the first MAC CE, the terminal triggers a scheduling request SR.
  • a terminal including multiple functional units, for correspondingly executing the method provided in any one of the possible implementation manners of the first aspect.
  • a network device including multiple functional units, for correspondingly executing the method provided in any one of the possible implementation manners of the second aspect.
  • a terminal for performing the RRC connection release method described in the first aspect.
  • the network device may include a memory and a processor, a transmitter, and a receiver coupled to the memory, wherein the transmitter is configured to send a signal to another wireless communication device, and the receiver is configured to receive the other wireless communication device.
  • a signal sent by a wireless communication device the memory is used to store the implementation code of the RRC connection release method described in the first aspect, and the processor is used to execute the program code stored in the memory, that is, to perform a possible implementation of the first aspect
  • a network device for performing the RRC connection release method described in the second aspect.
  • the terminal may include a memory and a processor, a transmitter, and a receiver coupled to the memory, wherein the transmitter is configured to send a signal to another wireless communication device, and the receiver is configured to receive the another wireless communication device.
  • the signal sent by the wireless communication device, the memory is used to store the implementation code of the RRC connection release method described in the second aspect, and the processor is used to execute the program code stored in the memory, that is, to implement a possible implementation manner of the second aspect Any of the described RRC connection release methods.
  • a communication system includes: a network device and a terminal, where the terminal may be the terminal described in the first aspect.
  • the network device may be the network device described in the second aspect.
  • a computer-readable storage medium where instructions are stored on the readable storage medium, which when executed on the computer, causes the computer to perform the RRC connection release method described in the first aspect.
  • the readable storage medium stores instructions that, when running on the computer, causes the computer to execute the RRC connection release method described in the second aspect.
  • a computer program product containing instructions which, when run on a computer, causes the computer to execute the RRC connection release method described in the first aspect above.
  • FIG. 1 is a schematic structural diagram of a wireless communication system provided by the present application.
  • 2A-2B are the existing processes for releasing an RRC connection
  • FIG. 3 is a schematic flowchart of an RRC connection release method provided by the present application.
  • Figure 4-5 is a schematic diagram of several formats of the existing BSR MAC and CE;
  • FIG. 6 is a schematic diagram of values of a buffer size field of a BSR MAC and CE of a conventional short BSR or short truncated BSR;
  • FIG. 7 is a schematic diagram of values of a buffer size field of a BSR MAC and CE of a conventional long BSR or long truncated BSR;
  • Figure 8-9 is a schematic diagram of several formats of the existing MAC subheader
  • FIG. 10 is a schematic diagram of LCID field values in a conventional MAC subheader
  • FIG. 11 is a schematic flowchart of an RRC connection release method according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of an implementation of a terminal triggering an RRC connection release request
  • FIG. 13-14 are schematic diagrams of several types of MAC subheaders corresponding to the first MAC CE provided in this application;
  • 16 is a schematic diagram of a MAC subheader corresponding to the first MAC CE provided in this application;
  • FIG. 17 is a schematic flowchart of an RRC connection release method according to another embodiment of the present application.
  • 18A-18B are schematic flowcharts of two implementations of a terminal triggering an RRC connection release request
  • 19 is a schematic diagram of a relationship between an SDU and a PDU
  • 20A-20B are schematic flowcharts of two implementations of a terminal triggering an RRC connection release request
  • 21-23 are schematic diagrams of several types of MAC subheaders corresponding to the first MAC CE provided in this application;
  • 25 is a schematic diagram of a MAC subheader corresponding to the first MAC CE provided in this application;
  • FIG. 26 is a schematic diagram of a hardware architecture of a terminal device according to an embodiment of the present application.
  • FIG. 27 is a schematic diagram of a hardware architecture of a network device according to an embodiment of the present application.
  • FIG. 28 is a functional block diagram of a wireless communication system, a terminal, and a network device provided by the present application; FIG.
  • FIG. 29 is a schematic structural diagram of a processor according to the present application.
  • FIG. 1 shows a wireless communication system 100 according to the present application.
  • the wireless communication system 100 can work in a high-frequency band, and can be a 5th generation (5G) system, a new radio (NR) system, or a long term evolution (LTE) system.
  • 5G 5th generation
  • NR new radio
  • LTE long term evolution
  • System Machine-to-Machine (M2M) system, the sixth-generation communication system that will evolve in the future, etc.
  • the wireless communication system 100 may include: one or more network devices 101, one or more terminals 103, and a core network 115. among them:
  • the network device 101 may be a base station, and the base station may be used to communicate with one or more terminals, and may also be used to communicate with one or more base stations with partial terminal functions (such as a macro base station and a micro base station, such as an access point, Communication).
  • the base station can be a base transceiver station (BTS) in a Time Division Division Synchronous Code Division Multiple Access (TD-SCDMA) system, or an evolutionary base station (Evolutional Node B in an LTE system). , ENB), and base stations in 5G systems and New Air Interface (NR) systems.
  • the base station may also be an access point (AP), a transmission node (Trans TRP), a central unit (CU), or other network entities, and may include some or all of the functions of the above network entities .
  • the terminals 103 may be distributed throughout the wireless communication system 100, and may be stationary or mobile.
  • the terminal 103 may be a user equipment UE, a mobile device, a mobile station, a mobile unit, an M2M terminal, a wireless unit, a remote unit, a user agent, a mobile client, etc. Wait.
  • the network device 101 may be configured to communicate with the terminal 103 through the wireless interface 105 under the control of a network device controller (not shown).
  • the network device controller may be part of the core network 115, or may be integrated into the network device 101.
  • the network device 101 may be configured to transmit control information or user data to the core network 115 through a blackhaul interface 113 (such as an S1 interface).
  • the network device 101 and the network device 101 may also communicate with each other directly or indirectly through a blackhaul interface 111 (such as an X2 interface).
  • the wireless communication system 100 shown in FIG. 1 is only for more clearly illustrating the technical solution of the present application, and does not constitute a limitation on the present application.
  • Those skilled in the art will know that with the evolution of network architecture and new services In the emergence of scenarios, the technical solutions provided in this application are also applicable to similar technical problems.
  • Solution 1 The base station sends an RRC connection release message / RRC release message (RRCConnectionRelease / RRCRelease) to the UE. After receiving the RRC connection release message, the UE transitions from the RRC connection state to the RRC idle state.
  • RRC connection release message RRCConnectionRelease / RRCRelease
  • the base station when the base station sends an RRC connection release message depends on the implementation of the base station.
  • the base station side maintains a timer that detects UE activity.
  • the name of the timer is InactivityTimer.
  • the base station sends an RRC connection release message / RRC release message to the UE.
  • the timer According to the data obtained from the current network, the timer generally runs for about 10 to 20 seconds after the UE ends the service transmission. This also means that the UE needs to keep the RRC connected state for 10-20s after the service transmission ends. Therefore, it may cause unnecessary extra power consumption of the UE.
  • Solution 2 The base station configures a timer for the UE. When the UE has any uplink or downlink transmission, including signaling and data, the UE will restart the timer. When the timer expires, the UE automatically enters the RRC idle state.
  • the base station configures a timer for the UE through an RRC connection reconfiguration message / RRC reconfiguration message (RRCConnectionReconfiguration / RRCReconfiguration).
  • the name of the timer is DataInactivityTimer.
  • a media access control (MAC) entity of the UE maintains the timer.
  • DTCH dedicated traffic channel
  • DCCH dedicated control channel
  • CCCH common control channel
  • the UE needs to start or restart the timer.
  • the MAC entity When the timer expires, the MAC entity sends an indication to notify the RRC layer of the UE.
  • the RRC layer When the RRC layer receives the indication, it initiates a state transition from the RRC connected state to the RRC idle state, thereby releasing the RRC connection.
  • the main role of the solution 2 is to overcome the problem that the RRC status of the UE and the base station is inconsistent due to the UE not successfully receiving the RRC connection release message sent by the base station, thereby causing the UE to be in the RRC connected state.
  • the timing length of the DataInactivityTimer in scheme 2 is longer than the timing length of the InactivityTimer maintained by the base station side in scheme 1.
  • the existing technologies will allow the UE to remain in the RRC connected state for a period of time after the service ends. Specifically, in the above solution 1, the UE will remain in the RRC connected state for another 10-20s after the service ends. In the above solution 2, the UE will remain in the RRC connected state for an additional 10-20s after the service ends. time.
  • the main purpose is to prevent the UE from entering the RRC idle state / inactive state from the RRC connected state, and then quickly enter the ping pong conversion of the RRC connected state again.
  • the prior art does not allow the UE in the RRC connected state to switch to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, which is not conducive to reducing the power consumption of the UE.
  • This is mainly because the base station cannot accurately estimate the time when the UE service ends.
  • the technical solution provided in this application will determine or estimate the end time of the service based on the UE side implementation, and can trigger the RRC connection release request as soon as possible.
  • this application provides an RRC connection release method, which can save terminal power consumption.
  • the terminal determines whether the terminal service transmission ends or not.
  • the terminal sends a MAC control entity (control entity, CE) for the RRC connection release request to the network device.
  • CE control entity
  • the network device may decide to send an RRC connection release message / RRC release message to the terminal to initiate the RRC connection release process of the terminal.
  • the terminal in the RRC connected state can be switched to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, instead of waiting for a period of time after the counter expires and then switched to the RRC idle or RRC inactive state. Conducive to reducing terminal power consumption.
  • the RRC connection release method provided in this application may include:
  • the terminal triggers an RRC connection release request.
  • the terminal may trigger an RRC connection release request under a condition that a trigger condition of the RRC connection release request is satisfied.
  • the essence of the trigger condition of the RRC connection release request is the end of the terminal service. That is, once the terminal determines that the terminal service is over, it can trigger an RRC connection release request. Subsequent content will introduce this trigger condition in detail, so I won't repeat it here.
  • the terminal once the terminal triggers the RRC connection release request, the terminal generates a MAC (CE) for RRC connection release request for the RRC connection release request.
  • the RRC connection release request sent by the terminal can be carried in the MAC CE.
  • the terminal sends a MAC to the network device for the RRC connection release request.
  • the network device receives the MAC CE sent by the terminal.
  • the purpose of the terminal sending the MAC to the RRC connection release request to the network device is to request the network device to initiate the RRC connection release process of the terminal.
  • the RRC connection release process can be shown as S103-S104 in FIG.
  • the network device sends an RRC connection release message / RRC release message to the terminal.
  • the terminal receives the RRC connection release message / RRC release message sent by the network device, releases the RRC connection, and transitions from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • the network device may decide to immediately initiate an RRC connection release process for the terminal.
  • the network device may also wait for a short time (such as 30-50 ms) before deciding to initiate the RRC connection release process of the terminal.
  • the network device may wait for the terminal to receive one or several small downlink data packets, and then decide to initiate the release of the RRC connection of the terminal.
  • the terminal may instruct the network device in the MAC CE to wait for the terminal to receive one or several small downlink data packets after receiving the MAC CE, and then initiate the RRC connection release process. For specific implementation, refer to Subsequent embodiments are not repeated here.
  • a MAC (CE) for RRC connection release request (MAC, CE, RRC connection, release request) may be referred to as a first MAC (CE).
  • the first MAC CE may be implemented by reusing the MAC CE defined in the existing protocol, or may be a newly defined MAC CE.
  • the first MAC CE carries first indication information, and the first indication information indicates that the first MAC CE is used for an RRC connection release request.
  • the signaling implementation of the first MAC CE will be described in detail in the subsequent content, which is not described here again.
  • this application does not limit the naming of the first MAC CE.
  • the terminal may also report whether the terminal itself supports triggering an RRC connection release request through a UE capability report.
  • the network device may decide whether to allow the terminal to send the first MAC CE according to the instruction of the terminal. Specifically, if the terminal indicates that it can support the triggering of the RRC connection release request, the network device determines whether to allow the terminal to send the first MAC CE. If the network device allows the terminal to send the first MAC CE, the network device sends an indication to the terminal that it is allowed to send the first MAC CE. After receiving the indication, the terminal can trigger and send the first MAC CE.
  • the terminal determines whether the terminal service transmission ends or not, and the time when the terminal service transmission ends can be accurately determined as soon as possible.
  • the terminal may send the first MAC CE to the network device after determining that the service transmission ends, to request the network device to initiate an RRC connection release process.
  • the terminal in the RRC connected state can be switched to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, which is beneficial to reducing the power consumption of the terminal.
  • this application uses signaling such as MAC CE rather than RRC to request network equipment to initiate an RRC connection release process, which can further reduce terminal power consumption.
  • signaling such as MAC CE rather than RRC to request network equipment to initiate an RRC connection release process, which can further reduce terminal power consumption.
  • MAC CE omits automatic repeat request (ARQ) and saves energy.
  • the first trigger condition After the terminal sends or receives a data, there is no data transmission for a period of time, and the terminal determines that there is no service to be transmitted in the near future. The terminal triggers an RRC connection release request.
  • this period of time may be referred to as the first time, and the first time may be a few seconds, or other values.
  • the method for determining the first time may be: if the terminal finds that it has not received the scheduling information for data transmission and reception sent by the network device within N consecutive discontinuous reception (DRX) periods, Trigger an RRC connection release request.
  • the first time is the N DRX cycles.
  • the second trigger condition the uplink data currently transmitted by the terminal is the last uplink data packet of the current service. Once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, the terminal triggers an RRC connection release request.
  • the terminal can save the last 1G photo of the data
  • the data packet is determined to be the last uplink data packet of the current service.
  • the terminal may trigger an RRC connection release request.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal will not receive downlink data packets after sending the last uplink data packet.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal needs to receive another downlink data packet after sending the last uplink data packet.
  • the terminal transmits the last uplink data packet: the terminal no longer receives the downlink data packet, or the terminal needs to receive another downlink data packet.
  • the second case it is not limited to one downlink data packet, and may also be a downlink data packet that is less than the first data amount (that is, a small amount).
  • the data packet of the first data amount may include one, or two, or three or more downlink data packets. That is, once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, and the terminal needs to receive a small number of downlink data packets after sending the last uplink data packet, the terminal can trigger an RRC connection release request.
  • the small amount of offline data packets may be response data packets for the last uplink data packet, such as ACK / NACK.
  • the last uplink data packet refers to the last uplink PDCP service data unit (service unit) (SDU) or the last uplink PDCP packet data unit (packet unit) (PDU).
  • SDU service unit
  • PDU packet unit
  • buffer status report buffer status report (BSR) MAC CE) defined in the existing protocol.
  • BSR MAC CE contains four formats:
  • Short BSR format (short BSR format), its length is fixed, only 1 byte;
  • Short truncated BSR format (Short Truncated BSR format), its length is fixed, only 1 byte;
  • the BSR MAC and CE corresponding to the short BSR format and the short truncated BSR format are shown in FIG. 4; the BSR MAC and CE corresponding to the long BSR format and the long truncated BSR format are shown in FIG. 4; the BSR MAC and CE corresponding to the long BSR format and the long truncated BSR format are shown in FIG. 4; the BSR MAC and CE corresponding to the long BSR format and the long truncated BSR format are shown in FIG.
  • the LCG ID field represents an identification of a logical channel group (LCG).
  • the UE reports the amount of data in the corresponding buffer with the granularity of the logical channel group; the buffer size field indicates the amount of data in the buffer of the logical channel group corresponding to the LCG ID field.
  • the first byte is a bitmap. Each bit in the bitmap is used to indicate whether the LCG buffer size corresponding to the bit is reported. For the long truncated BSR format, each bit in the bitmap is used to indicate whether there is data in the LCG corresponding to the bit. Each buffer size field indicates the amount of data in the buffer of each corresponding logical channel group.
  • the buffer size buffer size is represented by 5 bits, and the value of the buffer size field and the data amount represented by it are shown in the table shown in FIG. 6.
  • the buffer size of the buffer size is represented by 8 bits, and the value of the buffer size field and the amount of data represented by it are shown in the table shown in FIG. 7.
  • R represents a reserved bit, and the value is fixedly set to 0.
  • F is used to indicate whether the L field is 1 byte or 2 bytes.
  • the L field is used to indicate the number of bytes occupied by the corresponding variable-length MAC CE.
  • LCID field When the MAC subheader containing the LCID field corresponds to a MAC CE, the LCID field is used to indicate the type of the MAC CE. For the uplink MAC CE, the correspondence between the value of the LCID field and the MAC CE type is shown in the table shown in FIG. 10. It can be seen from FIG. 10 that, for the MACs of the four BSR formats, four LCID values are used to represent them.
  • the first MAC CE can be implemented by reusing the BSR MAC CE defined in the existing protocol.
  • the first indication information carried in the first MAC CE may indicate that the first MAC CE is a special BSR MAC CE, and the first MAC CE is used for RRC The MAC CE of the connection release request, that is, the MAC CE for RRC Connection Release Request.
  • the first indication information may include: an LCID field in which the value of the MAC subheader corresponding to the BSR MAC CE is a reserved LCID value (such as a value or a range of values in 100010–110100). And / or, the reserved bit R of the MAC subheader corresponding to the BSR MAC CE is set to a first value (such as 1). That is to say, the reserved LCID value or reserved bit R in the MAC subheader corresponding to the existing BSR MAC CE can be used to indicate that the BSR MAC CE is a special MAC CE, which is used for RRC connection release request, that is, MAC CE for RRC ConnectionReleaseRequest.
  • the reserved LCID value if there is an individual reserved LCID value in the range of 100010-110100 in the existing protocol for other purposes, the use of the reserved LCID value mentioned in this application is not the same as the individual reserved LCID. Conflicting values.
  • the value of the buffer size field in the BSR MAC CE is 0; the LCG ID field in the BSR MAC CE The value can be the ID of any LCG terminated, or the ID of the LCG containing the logical channel with the highest priority, or 0.
  • the BSR MAC may include only one bitmap byte, and the value of each bit in the bitmap byte Both are 0, indicating that there is no data buffer in the logical channel group corresponding to each bit. It can be seen that, since the buffer size field in the existing BSR MAC and CE is omitted, the first MAC CE can save bit overhead.
  • the first indication information may further include: a buffer size field that is set to a buffer size reserved value (that is, 255). That is to say, it is also possible to use the reserved buffer size value in the existing long BSR format or long truncated BSR format BSR MAC CE to indicate that the BSR MAC CE is a special MAC CE for RRC connection release request, that is, MAC CE for RRC Connection Release Request.
  • the BSR MAC CE may include only a bitmap byte and a buffer size field.
  • the first MAC CE may be a newly defined MAC CE.
  • the bit length of the newly defined MAC CE may be fixed to 0 bits; the first indication information carried in the first MACCE may include: a value in the MAC subheader corresponding to the newly defined MAC CE is reserved for LCID LCID field of a value (such as a value or a range of values in 100010-110100), and / or, a reserved bit R having a first value (such as 1) in a MAC subheader corresponding to the newly defined MAC CE. That is, the reserved LCID value or the reserved bit R in the MAC subheader may be used to indicate that the first MAC CE is used for the RRC connection release request.
  • the reserved LCID value if there are individual reserved LCID values in the range 100010-110100 in the existing protocol for other purposes, the use of the reserved LCID value mentioned in this application is not the same as the reserved LCID value. Conflicting values.
  • the first MAC CE may carry indication information to indicate the RRC state to which the terminal preference is transferred.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the instruction information may be referred to as second instruction information.
  • the first MAC CE may carry instruction information to indicate whether the terminal needs to receive a downlink data packet or does not need to receive a downlink data packet after sending the last uplink data packet.
  • This instruction information may be referred to as third instruction information.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following: cell-radio network temporary identifier (C-RNTI) MAC, CE, configuration Authorization confirmation MAC (CE) (Configured Grant, MAC, CE), BSR except MAC (CE) (padding, BSR, MAC, CE), power headroom report (MAC, CE, PHR, MAC, CE) Data from any logical channel other than the data of the common control channel (UL-CCCH).
  • C-RNTI cell-radio network temporary identifier
  • CE configuration Authorization confirmation MAC
  • CE Configured Grant, MAC, CE
  • BSR except MAC (CE) padding, BSR, MAC, CE
  • power headroom report MAC, CE, PHR, MAC, CE
  • the first MAC CE can be prevented from preempting the resources carrying the data, and the data can be transmitted normally.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following items: C-RNTI MAC, CE, Configured Grant Confirm MAC CE, except for BSR MAC pad CE used for padding BSR MAC CE.
  • the terminal if the uplink resource cannot accommodate the first MAC CE, the terminal triggers a scheduling request SR.
  • the trigger condition of the RRC connection release request is the aforementioned first trigger condition, that is, after the terminal in the RRC_Connected state ends, when it is determined that there is no service in the near future, the terminal triggers the RRC connection release request.
  • the first MAC CE carrying the RRC connection release request is implemented by reusing the BSR MAC CE defined in the existing protocol.
  • FIG. 11 shows a specific flow of the RRC connection release method provided in the first embodiment. Expand below:
  • the terminal determines that no service needs to be transmitted for a period of time after the current time. Once the terminal determines that no service needs to be transmitted for a period of time after the current time, the terminal can trigger an RRC connection release request. That is, the condition for triggering the RRC connection release request in this embodiment is the foregoing first trigger condition.
  • this period of time may be referred to as the first time, and the first time may be 20-30s, or other values.
  • the terminal can trigger an RRC connection release request.
  • the terminal may determine whether there is sufficient uplink resources to bear the MAC CE (ie, the first MAC CE) used for the RRC connection release request. If there are not enough uplink resources, S204-S205 may be performed first, and then S206 may be performed; if there are sufficient uplink resources, S206 may be directly performed.
  • the MAC CE ie, the first MAC CE
  • the terminal sends a scheduling request SR to the network device to request to obtain an uplink resource to carry the first MAC CE.
  • the network device schedules uplink resources for the terminal and sends an uplink grant (UL grant) to the terminal.
  • the UL grant indicates what uplink resources the network device schedules for the terminal.
  • a network device can carry UL grant through downlink control information (DCL).
  • the terminal may reuse the existing BSR MAC and CE to generate the MAC CE (ie, the first MAC CE) used for the RRC connection release request.
  • S207 The terminal sends the MAC CE used for the RRC connection release request to the network device, that is, the first MAC CE.
  • the premise of performing S207 is that the terminal has sufficient uplink resources to carry the first MAC CE.
  • the network device receives the MAC CE used for the RRC connection release request sent by the terminal.
  • the network device sends an RRC connection release message to the terminal.
  • the network device may decide to immediately initiate an RRC connection release process for the terminal.
  • the network device may also wait for a short time (such as 30-50 ms) before deciding to initiate the RRC connection release process of the terminal.
  • the terminal receives an RRC connection release message sent by the network device.
  • the terminal releases the RRC connection according to the RRC connection release message, and transitions from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • S206 can also be executed before S203, that is, once the terminal triggers an RRC connection release request, the terminal can first generate a first MAC CE, and then determine whether the uplink resources can accommodate the first MAC CE For the first MAC CE, if the uplink resource cannot accommodate the first MAC CE, the terminal triggers a scheduling request SR.
  • a high-level protocol layer such as an application layer or a Packet Data Convergence Protocol (PDCP) layer
  • PDCP Packet Data Convergence Protocol
  • the high-level protocol layer transmits instruction information to the MAC layer (refer to S403).
  • the MAC layer triggers an RRC connection release request (refer to S404).
  • this instruction information may be referred to as fifth instruction information.
  • the MAC layer determines that the terminal does not need to transmit services in the near future. Once the MAC layer determines that no service needs to be transmitted for a period of time after the current time, the MAC layer triggers an RRC connection release request.
  • the terminal can determine that near future has no service at the high-level protocol layer, and transmit the indication information to the MAC layer, and then trigger an RRC connection release request at the MAC layer.
  • the terminal may also trigger an RRC connection release request and trigger an RRC connection release request at the MAC layer.
  • the terminal may also trigger an RRC connection release request by other methods, which is not limited in this application.
  • the first MAC CE carries the first indication information.
  • the first indication information indicates that the first MAC CE is a special BSR MAC CE, and specifically indicates that the first MAC CE is a MAC CE used for an RRC connection release request.
  • the implementation of the first MAC CE may include, but is not limited to:
  • the first MAC CE may be a short BSR or a short truncated BSR MAC BCE.
  • the value of the LCID field in the MAC subheader corresponding to the short BSR or short truncated BSR format MAC and CE may be a reserved LCID value.
  • the value of the LCID field can be one of the reserved LCID values 100010–110100 or a value range.
  • the reserved LCID value in the MAC subheader can be used to indicate that the existing BSR MAC CE is a special MAC CE, that is, MAC CE for RRC ConnectionReleaseRequest.
  • the LCID field in the MAC subheader with a reserved LCID value is used to indicate that the BSR MAC CE is a special MAC CE, that is, MAC CE for RRC ConnectionRelease Request. That is, the first indication information may be an LCID field in the MAC subheader whose value is a reserved LCID value.
  • the value of the buffer size field in the BSR MAC and CE may be 0, that is, the BS value (that is, 0) corresponding to the serial number 0 in the table shown in FIG. 6.
  • the value of the LCG ID field in the BSR MAC and CE can be the ID of any LCG terminated, or the ID of the LCG containing the logical channel with the highest priority, or 0.
  • the first MAC CE may be a short BSR or a short truncated BSR MAC BCE.
  • the reserved bit R in the MAC subheader corresponding to the short BSR or short truncated BSR format MAC and CE can be used to indicate that the BSR MAC CE is a special MAC CE, that is, MAC for RRC Connection Release Request.
  • the first indication information may be a reserved bit R in the MAC subheader that takes a first value (such as 1).
  • the reserved bit R in the MAC subheader corresponding to the existing BSR MAC CE can be used to indicate that the BSR MAC CE is a special MAC CE, that is, MAC for RRC Connection Release Request.
  • the value of the buffer size field in the BSR MAC and CE may be 0, that is, the BS value (that is, 0) corresponding to the serial number 0 in the table shown in FIG. 6.
  • the value of the LCG ID field in the BSR MAC and CE can be the ID of any LCG terminated, or the ID of the LCG containing the logical channel with the highest priority, or 0.
  • Method 3 It is not limited to the short BSR or short truncated BSR format shown in FIG. 11, the first MAC CE may also be a BSR MAC or CE with long BSR or long truncated BSR format.
  • the value of the buffer size field in the BSR MAC CE is fixed to the buffer size reserved value, that is, the BS reserved value corresponding to the serial number 255 in the table shown in FIG. 7.
  • the BSR MAC CE may include only a bitmap byte and a buffer size field.
  • the first MAC CE may be a long BSR or a long truncated BSR MAC BCE.
  • the reserved LCID value in the MAC subheader can be used to indicate the existing long BSR or long truncated BSR format BSR.
  • MAC CE is a special MAC CE, that is, MAC CE for RRC Connection Release Request. That is to say, the LCID field in the MAC subheader with a reserved LCID value is used to indicate that the BSR MAC CE is a special MAC CE Request. That is, the first indication information may be an LCID field in the MAC subheader whose value is a reserved LCID value.
  • the BSR MAC and CE may only include one bitmap byte, and each bit in the bitmap byte has a value of 0, indicating that there is no data buffer in the logical channel group corresponding to each bit. It can be seen that, since the buffer size field in the existing BSR MAC and CE is omitted, the first MAC CE can save bit overhead.
  • the first MAC CE may be a long BSR or a long truncated BSR MAC BCE.
  • the reserved bit R in the MAC subheader corresponding to the existing BSR MAC CE can be used to indicate that the BSR MAC CE is a special MAC CE, that is, MAC for RRC Connection Release Request That is, the first indication information may be a reserved bit R in the MAC subheader that takes a first value (such as 1).
  • the BSR MAC and CE may only include one bitmap byte, and each bit in the bitmap byte has a value of 0, indicating that there is no data buffer in the logical channel group corresponding to each bit. It can be seen that, since the buffer size field in the existing BSR MAC and CE is omitted, the first MAC CE can save bit overhead.
  • the terminal if the uplink resource cannot accommodate the first MAC CE, the terminal triggers a scheduling request SR.
  • the priority of the first MAC CE when performing logical channel priority processing may have the following considerations:
  • the priority of the first MAC when performing logical channel priority processing may be lower than the priorities of the following: C-RNTI MAC, CE, Configured Grant, MAC CE, BSR MAC except CE padding, MAC BSR, MAC CE, PHR MAC, CE, data from any logical channel except data from UL-CCCH.
  • the first MAC CE can be prevented from preempting the resources carrying the data, and the data can be transmitted normally.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following items: C-RNTI MAC, CE, Configured Grant Confirm MAC CE, except for BSR MAC pad CE used for padding BSR MAC CE.
  • the terminal after it is determined that there is no service in near future, the terminal triggers an RRC connection release request, and reuses the existing BSR MAC MAC to request the network device to initiate an RRC connection release process.
  • the first embodiment can not only enable the terminal to accurately switch to the RRC_IDLE or RRC_Inactive state as soon as possible, save terminal power consumption, but also reuse existing MAC CEs and make full use of existing MAC CEs.
  • the existing BSR MAC and CE (ie, the first MAC CE) used for the RRC connection release request may carry indication information to indicate the RRC state to which the terminal prefers to transfer.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the instruction information may be referred to as second instruction information.
  • the second indication information may include but is not limited to the following two implementation manners:
  • the second indication information may be a first indication bit in the MAC subheader.
  • the value of the first indicator bit is the third value (such as 1), it indicates that the RRC state to which the terminal preference is transferred is the RRC idle state.
  • the value of the first indicator bit is the fourth value (such as 0), it indicates that The RRC state to which the terminal preference is transferred is the RRC inactive state.
  • a certain bit in the MAC subheader corresponding to the existing BSR MAC and CE (such as the reserved bit R as an indication bit) can be used to indicate the RRC state to which the terminal preference is transferred.
  • the MAC subheader corresponding to the first MAC CE may be exemplarily shown in FIG. 13.
  • the value of the reserved bit R can be 0; bit I is the first indicator bit, which is used to indicate the RRC state to which the terminal prefers to transfer, and bit I can be the two preambles included in the MAC subheader (shown in Figure 8).
  • One of the reserved bits R; the value of the LCID field is one of the reserved LCID values or a value range in the table shown in FIG. 10.
  • the MAC subheader corresponding to the first MAC CE may be exemplarily shown in FIG. 14.
  • bit I is the first indication bit, and bit I may be a reserved bit R (refer to (B) in FIG. 14) or a bit F (refer to (A) in FIG. 14) in the MAC subheader (shown in FIG. 9). );
  • the value of the LCID field is one of the reserved LCID values or a value range in the table shown in FIG. 10.
  • the value of the first indicator bit when the value of the first indicator bit is 1, it may indicate that the terminal preference is transferred to the RRC_IDLE state; when the value of the first indicator bit is 0, it may indicate that the terminal preference is transferred to the RRC_Inactive state. At this time, the third value is 1, and the fourth value is 0. Conversely, when the value of the first indicator bit is 0, it may indicate that the terminal preference is transferred to the RRC_IDLE state; when the value of the first indicator bit is 1, it may indicate that the terminal preference is transferred to the RRC_Inactive state. At this time, the third value is 0 and the fourth value is 1.
  • the value of the first indication bit may be determined by a higher-level protocol layer (such as an application layer or an RRC layer) or a MAC layer.
  • the second indication information may be an LCID field in which a value in the MAC subheader is a reserved LCID value.
  • the value of the LCID field When the value of the LCID field is the first reserved LCID value, it indicates that the RRC state that the terminal preference is transferred to is the RRC idle state. When the value of the LCID field is the second reserved LCID value, it indicates the RRC that the terminal preference is transferred to. The state is RRC inactive.
  • the reserved LCID value in the LCID field in the MAC subheader can be used to indicate the RRC state to which the terminal preference is transferred.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE, but also indicate the RRC state to which the terminal preference is transferred.
  • the LCID field value is 100010 reserved, it means that the BSR MAC CE is used for the RRC connection release request, and it means that the terminal preference is transferred to the RRC_IDLE state;
  • the LCID field is set to a reserved value of 100011, it indicates that the BSR MAC is used for the RRC connection release request, and the terminal preference is transferred to the RRC_Inactive state.
  • the first reserved LCID value is 100011
  • the second reserved LCID value is 100011.
  • the first reserved LCID value and the second reserved LCID value may be two of the reserved LCID values in the table shown in FIG. 10.
  • the network device may determine, according to the second instruction information, in the RRC connection release message sent to the terminal, whether to carry the instruction information for transitioning to the RRC inactive state. For example, if the second instruction information indicates that the terminal preference is shifted to the RRC_IDLE state, the RRC connection release message issued by the network device does not carry the instruction to transition to the RRC inactive state; if the second instruction information indicates that the terminal preference is shifted to the RRC_Inactive state , The RRC connection release message issued by the network device carries the instruction information for transitioning to the RRC inactive state. In this way, the terminal has more choices and is more flexible when requesting the network device to initiate the RRC connection release process.
  • the trigger condition of the RRC connection release request is the aforementioned first trigger condition, that is, after the terminal in the RRC_Connected state ends, when it is determined that there is no service in the near future, the terminal triggers the RRC connection release. request.
  • the first MAC CE carrying the RRC connection release request is a newly defined MAC CE.
  • FIG. 15 shows a specific flow of the RRC connection release method provided in the second embodiment. Expand below:
  • the terminal determines that no service needs to be transmitted within a period of time after the current time. Once the terminal determines that no service needs to be transmitted for a period of time after the current time, the terminal can trigger an RRC connection release request.
  • the terminal may determine whether there is sufficient uplink resources to bear the MAC CE (ie, the first MAC CE) used for the RRC connection release request. If there are not enough uplink resources, S304-S305 can be executed first, and then S306 can be executed; if there are sufficient uplink resources, S306 can be directly executed.
  • the MAC CE ie, the first MAC CE
  • the terminal sends a scheduling request SR to the network device to request to obtain an uplink resource to carry the first MAC CE.
  • the network device schedules uplink resources for the terminal and sends an uplink grant (UL grant) to the terminal.
  • the UL grant indicates what uplink resources are scheduled by the network device for the terminal.
  • the terminal may use the newly defined MAC CE to generate a MAC CE (ie, a first MAC CE) used for the RRC connection release request.
  • a MAC CE ie, a first MAC CE
  • the terminal sends the MAC CE used for the RRC connection release request to the network device, that is, the first MAC CE.
  • the premise of performing S207 is that the terminal has sufficient uplink resources to carry the first MAC CE.
  • the network device receives the MAC CE for the RRC connection release request sent by the terminal.
  • the network device sends an RRC connection release message to the terminal.
  • the terminal receives an RRC connection release message sent by the network device.
  • the terminal releases the RRC connection according to the RRC connection release message, and transitions from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • S306 can also be executed before S303, that is, once the terminal triggers an RRC connection release request, the terminal can first generate the first MAC CE, and then determine whether the uplink resources are sufficient before sending the first MAC CE. If the uplink resources are insufficient, the terminal sends an SR to the network device.
  • the specific implementation of the trigger condition of the RRC connection release request in the second embodiment is the same as the specific implementation of the trigger condition of the RRC connection release request in the first embodiment, and reference may be made to the first embodiment, which is not repeated here.
  • the bit length of the first MAC CE may be fixed to 0 bits.
  • the first indication information carried in the first MACCE may include: an LCID field in a MAC subheader corresponding to the BSR MAC and the CE is a reserved LCID value (such as a value or a range of values in 100010-110100), and / or, the BSR
  • the reserved bit R in the MAC subheader corresponding to the MAC CE is the first value (such as 1). That is, the reserved LCID value or the reserved bit R in the MAC subheader may be used to indicate that the first MAC CE is used for the RRC connection release request.
  • the terminal if the uplink resource cannot accommodate the first MAC CE, the terminal triggers a scheduling request SR.
  • the terminal triggers an RRC connection release request and reuses the existing BSR MAC MAC to request the network device to initiate an RRC connection release process.
  • the second embodiment can not only enable the terminal to transit to the RRC_IDLE or RRC_Inactive state as soon as possible and save power consumption of the terminal, but also can use the newly defined MAC CE to bear the RRC connection release request and save signaling overhead.
  • the newly defined MAC CE (ie, the first MAC CE) used to carry the RRC connection release request may carry second instruction information to indicate the RRC state to which the terminal prefers to transfer.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the second indication information may include but is not limited to the following two implementation manners:
  • the second indication information may be a first indication bit in a MAC subheader corresponding to the newly defined MAC CE.
  • the value of the first indicator bit is the third value (such as 1), it indicates that the RRC state to which the terminal preference is transferred is the RRC idle state.
  • the value of the first indicator bit is the fourth value (such as 0), it indicates that The RRC state to which the terminal preference is transferred is the RRC inactive state.
  • a certain bit in the MAC subheader corresponding to the newly defined MAC CE (such as the reserved bit R as an indication bit) may be used to indicate the RRC state to which the terminal prefers to transition.
  • the MAC subheader corresponding to the newly defined MAC CE may include a reserved bit R, a bit I, and an LCID field.
  • bit I is the first indication bit
  • bit I may be a reserved bit R included in the MAC subheader
  • the value of the LCID field is a reserved LCID value, indicating that the newly defined MAC CE is used for RRC connection release. request.
  • the second indication information may be the LCID field in the MAC subheader.
  • the value of the LCID field is the first reserved LCID value, it indicates that the RRC state to which the terminal preference is transferred is the RRC idle state.
  • the value is the second reserved LCID value, it indicates that the RRC state to which the terminal preference is transferred is the RRC inactive state.
  • the reserved LCID value in the LCID field in the MAC subheader can be used to indicate the RRC state to which the terminal preference is transferred.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE, but also indicate the RRC state to which the terminal preference is transferred.
  • the trigger condition of the RRC connection release request is the foregoing second trigger condition, that is, the uplink data currently transmitted by the terminal is the last uplink data packet of the current service.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal will not receive downlink data packets after sending the last uplink data packet.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal needs to receive another downlink data packet after sending the last uplink data packet.
  • the terminal transmits the last uplink data packet there may be two situations after the terminal transmits the last uplink data packet: the terminal no longer receives the downlink data packet, or the terminal only receives one more downlink data packet.
  • the first MAC CE carrying the RRC connection release request is reused to implement the existing BSR MAC CE.
  • FIG. 17 shows a specific flow of the RRC connection release method provided in the third embodiment. Expand below:
  • the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service. Once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, the terminal can trigger an RRC connection release request.
  • the terminal may also be a downlink data packet that is less than the first data amount (ie, a small amount).
  • the data packet of the first data amount may include one, or two, or three or more downlink data packets. That is, once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, and the terminal needs to receive a small number of downlink data packets after sending the last uplink data packet, the terminal can trigger an RRC connection release request.
  • the terminal can determine whether there is sufficient uplink resources to carry the MAC CE (ie, the first MAC) used for the RRC connection release request. If there are not enough uplink resources, S404-S405 may be performed first, and then S406 is performed; if there are sufficient uplink resources, S406 may be directly performed.
  • the MAC CE ie, the first MAC
  • the terminal sends a scheduling request SR to the network device, so as to request to obtain an uplink resource to carry the first MAC CE.
  • the network device schedules uplink resources for the terminal and sends an uplink grant (UL grant) to the terminal.
  • the UL grant indicates what uplink resources the network device schedules for the terminal.
  • the terminal may use the existing BSR MAC and CE to generate a MAC CE (that is, the first MAC CE) for the RRC connection release request.
  • S407 The terminal sends the MAC CE used for the RRC connection release request to the network device, that is, the first MAC CE.
  • the premise of performing S407 is that the terminal has sufficient uplink resources to carry the first MAC CE.
  • the network device receives the MAC CE for the RRC connection release request sent by the terminal.
  • the network device sends an RRC connection release message to the terminal.
  • the terminal receives the RRC connection release message sent by the network device.
  • the terminal releases the RRC connection according to the RRC connection release message, and transitions from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • S406 can also be executed before S403, that is, once the terminal triggers an RRC connection release request, the terminal can first generate the first MAC CE, and then determine whether the uplink resources are sufficient before sending the first MAC CE. If the uplink resources are insufficient, the terminal sends an SR to the network device.
  • a high-level protocol layer such as an application layer or a PDCP layer, may be used to determine whether the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and transmit the indication information to the MAC layer.
  • the MAC layer receives the instruction, the MAC layer triggers an RRC connection release request.
  • the high-level protocol layer may send indication information to the MAC layer.
  • the indication information is used to inform the MAC layer that there will be no more downlink data after the last uplink data packet of the current service.
  • this instruction information may be referred to as sixth instruction information.
  • the MAC layer triggers an RRC connection release request (refer to S45).
  • the higher-layer protocol layer may send an instruction to the MAC layer Information (refer to S42), the indication information is used to inform the MAC layer that there will be a small amount of downlink data after the last uplink data packet, such as a downlink data packet.
  • this instruction information may be referred to as seventh instruction information.
  • the MAC layer receives the seventh indication information, the MAC layer triggers an RRC connection release request (refer to S44).
  • the higher-level protocol layer needs to send the sixth indication information or the seventh indication information to the MAC layer only after it is determined that other uplink PDCP, SDU, or uplink PDCP PDUs have been correctly transmitted.
  • a high-level protocol layer such as an application layer or a PDCP layer, may be used to determine whether the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and transmit the indication information to the MAC layer.
  • the MAC layer receives the instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request.
  • SDU is a data set that specifies the user services of the protocol layer. When it is transmitted to the receiver, the data will not change when the same protocol layer, that is, the business part.
  • the lower protocol layer encapsulates it in a PDU and sends it out.
  • the layer N SDU and the layer N protocol data unit (PDU) correspond one-to-one.
  • the protocol layer Protocol # 2 receives the Protocol # 1 PDU from the protocol layer Protocol # 1 of the previous layer, and uses the Protocol # 1 PDU as the SDU of the protocol layer Protocol # 2, that is, Protocol # 2 SDU, and then encapsulates it in Protocol # 2 PDU. It can be seen that the SDU of Protocol # 2 of Protocol # 2 and Protocol # 1 of Protocol # 1 have a one-to-one correspondence.
  • part or all of the last uplink data packet sent by the MAC layer may include but is not limited to the three cases described in A-C:
  • the MAC SDU sent in the MAC PDU contains all of the last uplink data packet
  • the MAC SDU sent in the MAC PDU contains the last part of the last uplink data packet
  • the MAC SDU sent in the MAC PDU contains the first part of the last uplink data packet.
  • Part or all of the last uplink data packet sent by the MAC layer may also include that the MAC SDU sent in the MAC PDU contains some middle part of the last uplink data packet.
  • the higher-layer protocol layer may send the first trigger condition to the MAC layer.
  • Six instructions (refer to S53).
  • the MAC layer receives the sixth instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request (refer to S55-S57).
  • the higher-layer protocol layer may send the first trigger condition to the MAC layer. Seven instructions (refer to S52). After the MAC layer receives the seventh instruction information, when the MAC layer sends part or all of the last uplink data packet, the MAC layer triggers an RRC connection release request (refer to S54-S56).
  • the terminal may also trigger an RRC connection release request by other methods, which is not limited in this application.
  • the terminal when it is determined that the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and there is no downlink data packet or there is only one downlink data packet after the last uplink data packet, the terminal triggers The RRC connection release request and reuses the existing BSR MAC and CE to request the network device to initiate the RRC connection release process.
  • the third embodiment can not only enable the terminal to switch to the RRC_IDLE or RRC_Inactive state as soon as possible and save power consumption of the terminal, but also reuse the existing MAC CE and make full use of the existing MAC CE.
  • the existing BSR MAC CE (ie, the first MAC CE) used for the RRC connection release request may carry instruction information to indicate the RRC state to which the terminal prefers to transition.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the instruction information may be referred to as second instruction information.
  • second indication information For specific implementation of the second indication information, reference may be made to related extensions of Embodiment 1, and details are not described herein again.
  • the existing BSR MAC MAC CE (ie, the first MAC CE) used for the RRC connection release request can carry instruction information to indicate whether the terminal needs to receive another downlink data packet or no more after sending the last uplink data packet. Receive downlink packets.
  • This instruction information may be referred to as third instruction information. That is to say, the third indication information can distinguish case1 and case2 that indicate the second trigger condition.
  • the third instruction information may include but is not limited to the following two implementation manners:
  • the third indication information may be a second indication bit in the MAC subheader.
  • the value of the second indicator bit is the fifth value (such as 1), it means that the terminal needs to receive another downlink data after sending the last uplink data; when the value of the second indicator bit is the sixth value (such as 0) , It means that the terminal does not need to receive downlink data after sending the last uplink data.
  • a bit in the MAC subheader corresponding to the existing BSR MAC and CE can be used to distinguish between case1 and case2 that indicate the second triggering condition.
  • the MAC subheader corresponding to the first MAC CE may be exemplarily shown in FIG. 21.
  • the value of the reserved bit R can be 0; the bit D is the second indicator bit, which is used to distinguish between the case 1 and case 2 indicating the second trigger condition, and the bit D can be included in the MAC subheader (shown in FIG. 8).
  • One of the two reserved bits R; the value of the LCID field is one of the reserved LCID values or a value range in the table shown in FIG. 10.
  • the MAC subheader corresponding to the first MAC CE may be exemplarily shown in FIG. 22.
  • bit D is the second indicator bit, and bit D can be a reserved bit R (refer to (B) in FIG. 22) or a bit F (refer to (A) in FIG. 22) in the MAC subheader (shown in FIG. 9). );
  • the value of the LCID field is one of the reserved LCID values or a value range in the table shown in FIG. 10.
  • the value of the second indicator bit when the value of the second indicator bit is 1, the case1 of the second trigger condition may be indicated; when the value of the second indicator bit is 0, the case1 of the second trigger condition may be indicated. At this time, the fifth value is 1, and the sixth value is 0. Conversely, when the value of the second indicator bit is 0, it can indicate the case 1 of the second trigger condition; when the value of the second indicator bit is 1, it can indicate the case 1 of the second trigger condition. At this time, the fifth value is 0 and the sixth value is 1.
  • the value of the second indicator bit may be determined by a higher-level protocol layer (such as an application layer or an RRC layer) or a MAC layer.
  • the third indication information may be an LCID field in the MAC subheader.
  • the terminal When the value of the LCID field is the third reserved LCID value, it means that the terminal needs to receive another downlink data packet after sending the last uplink data packet; when the value of the LCID field is the fourth reserved LCID value, it means the terminal There is no need to receive a downlink data packet after sending the last uplink data packet.
  • the reserved LCID value in the LCID field in the MAC subheader corresponding to the existing BSR MAC and CE can be used to indicate the case 1 and case 2 of the second trigger condition.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE, but can also distinguish case1 and case2 indicating the second triggering condition at the same time.
  • the LCID field value is reserved for 100010, it means that the BSRMACCE is used for the RRC connection release request, and it means that the terminal needs to send it after sending the last uplink data packet.
  • Receive another downlink data packet when the LCID field is set to 100011, it indicates that the BSR MAC is used for RRC connection release request, and that the terminal does not need to receive the downlink data packet after sending the last uplink data packet .
  • the third reserved LCID value is 100011
  • the fourth reserved LCID value is 100011.
  • the third reserved LCID value and the fourth reserved LCID value may be two reserved values among the reserved LCID values in the table shown in FIG. 10.
  • the network device can determine, according to the third instruction information, whether or not it needs to wait for a downlink data packet before issuing the RRC connection release message after receiving the first MAC CE. In this way, for case 2 of the second triggering condition, the network device can wait for a period of time after receiving the first MAC CE to prevent the RRC connection from being released immediately and the downlink data cannot be transmitted.
  • the existing BSR MAC and CE (ie, the first MAC CE) used for the RRC connection release request can both indicate the RRC state that the terminal prefers to transition to, and also indicate that the terminal needs to receive another downlink data after sending the last uplink data The packet may no longer need to receive downstream data packets.
  • the first MAC CE may carry the first indication bit and the second indication bit at the same time, and the first indication bit and the second indication bit are two different indication bits in the MAC subheader.
  • bit I is the first indication bit, which is used to indicate the RRC state to which the terminal prefers to transition
  • bit D is the second indication bit, which is used to distinguish between case1 and case2, which indicate the second triggering condition
  • One of the reserved LCID values (such as 100011 in 100010-110100) or a range of values in the table shown at 9.
  • Bits I and D may be reserved bits R in the MAC subheader.
  • the first MAC CE may carry fourth instruction information, the fourth instruction information indicates the RRC state to which the terminal prefers to transition, and the terminal needs to receive another downlink data packet or no longer needs to be sent after the last uplink data is sent. Receive downlink packets.
  • the fourth indication information is the LCID field in the MAC subheader, which may indicate the following four cases:
  • the value of the LCID field is the fifth reserved LCID value (such as 100010 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC idle state and the terminal needs to receive another downlink after sending the last uplink data. data;
  • the value of the LCID field is the sixth reserved LCID value (such as 100011 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC inactive state and the terminal needs to receive one after sending the last uplink data.
  • the sixth reserved LCID value such as 100011 in 100010–110100
  • the value of the LCID field is the seventh reserved LCID value (such as 100100 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC idle state and the terminal does not need to receive downlink data after sending the last uplink data. ;
  • the value of the LCID field is the eighth reserved LCID value (such as 100101 in 100010–110100), it indicates that the RRC state that the terminal prefers to transition to is the RRC inactive state and the terminal does not need to receive the downlink after sending the last uplink data data.
  • the reserved LCID value in the LCID domain can not only distinguish the first MAC CE from the existing BSR MAC CE of other functions, but also indicate any one of the above four cases.
  • the trigger condition of the RRC connection release request is the foregoing second trigger condition, that is, the uplink data currently transmitted by the terminal is the last uplink data packet of the current service.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal will not receive downlink data packets after sending the last uplink data packet.
  • the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and the terminal needs to receive another downlink data packet after sending the last uplink data packet.
  • the terminal transmits the last uplink data packet there may be two situations after the terminal transmits the last uplink data packet: the terminal no longer receives the downlink data packet, or the terminal only receives one more downlink data packet.
  • the terminal can save the last 1G photo of the data
  • the data packet is determined as the last uplink data packet of the current service. Further, the terminal may determine whether there is downlink response / feedback information (such as ACK / NACK) for the last uplink data packet according to the transport layer communication protocol used by the current service.
  • downlink response / feedback information such as ACK / NACK
  • the terminal If the transmission layer communication protocol used by the current service is transmission control protocol (TCP), then after the last uplink data packet, the terminal also needs to receive a downlink response / feedback for the last uplink data packet, that is, case two (case 2); If the transport layer communication protocol used by the current service is user datagram protocol (UDP), then after the last uplink data packet, the terminal does not need to receive a downlink response to the last uplink data packet / Feedback, which is case one.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • the first MAC CE carrying the RRC connection release request is a newly defined MAC CE.
  • FIG. 24 shows a specific flow of the RRC connection release method provided in the fourth embodiment. Expand below:
  • the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service. Once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, the terminal can trigger an RRC connection release request.
  • the terminal may determine whether there is sufficient uplink resources to bear the MAC CE (ie, the first MAC) used for the RRC connection release request. If there are not enough uplink resources, S504-S505 can be executed first, and then S506 can be executed; if there are sufficient uplink resources, S506 can be directly executed.
  • the MAC CE ie, the first MAC
  • the terminal sends a scheduling request SR to the network device to request to obtain an uplink resource to carry the first MAC CE.
  • the network device schedules uplink resources for the terminal and sends an uplink grant (UL grant) to the terminal.
  • the UL grant indicates what uplink resources the network device schedules for the terminal.
  • the terminal may use the existing BSR MAC and CE to generate a MAC CE (that is, a first MAC CE) for the RRC connection release request.
  • the terminal sends the MAC CE used for the RRC connection release request to the network device, that is, the first MAC CE.
  • the premise of performing S407 is that the terminal has sufficient uplink resources to carry the first MAC CE.
  • the network device receives the MAC CE used for the RRC connection release request sent by the terminal.
  • the network device sends an RRC connection release message to the terminal.
  • the terminal receives an RRC connection release message sent by the network device.
  • the terminal releases the RRC connection according to the RRC connection release message, and transitions from the RRC_Connected state to the RRC_IDLE or RRC_Inactive state.
  • S506 can also be executed before S503, that is, once the terminal triggers the RRC connection release request, the terminal can first generate the first MAC CE, and then determine whether the uplink resources are sufficient before sending the first MAC CE If the uplink resources are insufficient, the terminal sends an SR to the network device.
  • the specific implementation of the trigger condition of the RRC connection release request in the fourth embodiment is the same as the specific implementation of the trigger condition of the RRC connection release request in the third embodiment, and reference may be made to the third embodiment, which is not repeated here.
  • the terminal when it is determined that the uplink data currently transmitted by the terminal is the last uplink data packet of the current service, and there will be no downlink data packet or only one downlink data packet after the last uplink data packet, the terminal triggers
  • the RRC connection release request uses the newly defined MAC CE to request the network device to initiate an RRC connection release process.
  • the fourth embodiment can not only enable the terminal to switch to the RRC_IDLE or RRC_Inactive state as soon as possible and save power consumption of the terminal, but also use the newly defined MAC CE to bear the RRC connection release request and save signaling overhead.
  • the newly defined BSR MAC (CE) used for the RRC connection release request may carry indication information to indicate the RRC state to which the terminal prefers to transfer.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the instruction information may be referred to as second instruction information.
  • second indication information For specific implementation of the second indication information, reference may be made to related extensions in Embodiment 2, and details are not described herein again.
  • the newly defined BSR MAC (CE) (the first MAC CE) used for the RRC connection release request can carry instruction information to indicate whether the terminal needs to receive another downlink data packet or no more after sending the last uplink data packet. Receive downlink packets.
  • This instruction information may be referred to as third instruction information. That is to say, the third indication information can distinguish case1 and case2 that indicate the second trigger condition.
  • the third instruction information may include but is not limited to the following two implementation manners:
  • the third indication information may be a second indication bit in the MAC subheader.
  • the value of the second indicator bit is the fifth value (such as 1), it means that the terminal needs to receive another downlink data after sending the last uplink data; when the value of the second indicator bit is the sixth value (such as 0) , It means that the terminal does not need to receive downlink data after sending the last uplink data.
  • a certain bit in the MAC subheader corresponding to the newly defined MAC CE (such as the reserved bit R as an indication bit) can be used to indicate the RRC state to which the terminal prefers to transition.
  • the MAC subheader corresponding to the newly defined MAC CE may include a reserved bit R, a bit D, and an LCID field.
  • bit D is the second indicator bit, which is used to distinguish between case1 and case2 indicating the second triggering condition.
  • Bit D can be a reserved bit R in the MAC subheader; A value or range of values in the reserved LCID value.
  • the value of the second indicator bit when the value of the second indicator bit is 1, the case1 of the second trigger condition may be indicated; when the value of the second indicator bit is 0, the case1 of the second trigger condition may be indicated. At this time, the fifth value is 1, and the sixth value is 0. Conversely, when the value of the second indicator bit is 0, it can indicate the case 1 of the second trigger condition; when the value of the second indicator bit is 1, it can indicate the case 1 of the second trigger condition. At this time, the fifth value is 0 and the sixth value is 1.
  • the value of the second indicator bit may be determined by a higher-level protocol layer (such as an application layer or an RRC layer) or a MAC layer.
  • the third indication information may be an LCID field in the MAC subheader.
  • the terminal When the value of the LCID field is the third reserved LCID value, it means that the terminal needs to receive another downlink data packet after sending the last uplink data packet; when the value of the LCID field is the fourth reserved LCID value, it means the terminal There is no need to receive a downlink data packet after sending the last uplink data packet.
  • the reserved LCID value in the LCID field in the MAC subheader corresponding to the newly defined MAC CE can be used to indicate the case 1 and case 2 of the second trigger condition.
  • the newly defined BSR MAC (CE) for RRC connection release request can both indicate the RRC state that the terminal prefers to transition to, and also indicate that the terminal needs to receive another downlink data after sending the last uplink data The packet may no longer need to receive downstream data packets.
  • the first MAC CE may carry the first indication bit and the second indication bit at the same time, and the first indication bit and the second indication bit are two different indication bits in the MAC subheader.
  • the first MAC CE may carry fourth instruction information, the fourth instruction information indicates the RRC state to which the terminal prefers to transition, and the terminal needs to receive another downlink data packet or no longer needs to be sent after the last uplink data is sent. Receive downlink packets.
  • the fourth indication information is the LCID field in the MAC subheader.
  • the fourth indication information is the LCID field in the MAC subheader.
  • the terminal in order to avoid that the first MAC CE that the terminal has sent is still in a state waiting for processing by the network device (that is, a pendin state), the terminal The first MAC CE is repeatedly sent, and the terminal may cancel sending the first MAC CE bearing the RRC connection release request when any one of the following conditions is met: The multiplexing and combining process of the terminal generates the first MAC CE, Or, the terminal has sent a MAC PDU including the first MAC CE.
  • the terminal multiplexing and combining process means that the terminal multiplexes one or more LCH data, that is, MAC SDU, and / or one or more MAC CEs into one MAC PDU, and according to the MAC defined in the MAC protocol The process of assembling a PDU format to generate a MAC PDU.
  • FIG. 26 illustrates a terminal 300 provided by some embodiments of the present application.
  • the terminal 300 may include: an input / output module (including an audio input / output module 318, a key input module 316, a display 320, etc.), a user interface 302, one or more terminal processors 304, a transmitter 306, and a receiver.
  • FIG. 26 takes the connection through a bus as an example. among them:
  • the communication interface 301 may be used for the terminal 300 to communicate with other communication devices, such as a base station.
  • the base station may be the network device 400 shown in FIG. 27.
  • the communication interface 301 refers to an interface between the terminal processor 304 and a transceiving system (consisting of a transmitter 306 and a receiver 308), such as the X1 interface in LTE.
  • the communication interface 301 may include a Global System for Mobile Communication (GSM) (2G) communication interface, a Wideband Code Division Multiple Access (WCDMA) (3G) communication interface, and One or more of Long Term Evolution (LTE) (4G) communication interfaces, etc., may also be communication interfaces of 4.5G, 5G or future new air interfaces.
  • the terminal 300 may also be configured with a wired communication interface 301, such as a Local Access Network (LAN) interface.
  • LAN Local Access Network
  • the antenna 314 may be used to convert electromagnetic energy in a transmission line into electromagnetic waves in a free space, or convert electromagnetic waves in a free space into electromagnetic energy in a transmission line.
  • the coupler 310 is configured to divide the mobile communication signal received by the antenna 314 into multiple channels and distribute the signals to multiple receivers 308.
  • the transmitter 306 may be configured to perform transmission processing on a signal output by the terminal processor 304, such as modulating the signal in a licensed frequency band or modulating a signal in an unlicensed frequency band.
  • the transmitter 306 may support the terminal 300 to transmit signals on one or more unlicensed spectrums, or may support the terminal 300 to transmit signals on one or more licensed spectrums.
  • the receiver 308 may be configured to perform reception processing on a mobile communication signal received by the antenna 314. For example, the receiver 308 may demodulate a received signal that has been modulated on an unlicensed frequency band, and may also demodulate a received signal that is modulated on a licensed frequency band. In other words, the receiver 308 may support the terminal 300 to receive a signal modulated on an unlicensed spectrum, or may support the terminal 300 to receive a signal modulated on an authorized spectrum.
  • the transmitter 306 and the receiver 308 may be considered as a wireless modem.
  • the number of the transmitters 306 and the receivers 308 may be one or more.
  • the terminal 300 may further include other communication components, such as a GPS module, a Bluetooth module, a Wireless Fidelity (Wi-Fi) module, and the like. Not limited to the wireless communication signals described above, the terminal 300 may also support other wireless communication signals, such as satellite signals, short-wave signals, and the like. Not limited to wireless communication, the terminal 300 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input / output module may be used to implement interaction between the terminal 300 and a user / external environment, and may mainly include an audio input / output module 318, a key input module 316, a display 320, and the like. In specific implementation, the input / output module may further include a camera, a touch screen, a sensor, and the like.
  • the input and output modules communicate with the terminal processor 304 through the user interface 302.
  • the memory 312 is coupled to the terminal processor 304 and is configured to store various software programs and / or multiple sets of instructions.
  • the memory 312 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 312 may store an operating system (hereinafter referred to as a system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 312 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.
  • the memory 312 can also store a user interface program.
  • the user interface program can realistically display the content of the application program through a graphical operation interface, and receive user control operations on the application program through input controls such as menus, dialog boxes, and keys .
  • the memory 312 may be configured to store an implementation program of the RRC connection release method provided on the terminal 300 side provided by one or more embodiments of the present application.
  • the implementation of the RRC connection release method provided by one or more embodiments of this application please refer to the subsequent embodiments.
  • the terminal processor 304 may be used to read and execute computer-readable instructions. Specifically, the terminal processor 304 may be used to call a program stored in the memory 312, for example, an implementation program of the RRC connection release method provided on the terminal 300 side by one or more embodiments of the present application, and execute instructions included in the program.
  • the terminal processor 304 may be a modem processor, and it is a module that realizes the main functions in wireless communication standards such as 3GPP and ETSI.
  • the modem can be used as a separate chip or form a system-level chip or integrated circuit with other chips or circuits. These chips or integrated circuits can be applied to all devices that implement wireless communication functions, including: mobile phones, computers, notebooks, tablets, routers, wearable devices, automobiles, home appliances, etc.
  • the terminal processor 304 processor may be used as a separate chip and coupled with the off-chip memory, that is, the chip does not include memory; or the terminal processor 304 processor is coupled with the on-chip memory and Integrated in the chip, that is, the chip contains memory.
  • the terminal 300 may be the terminal 103 in the wireless communication system 100 shown in FIG. 1 and may be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, and a user agent. , Mobile clients, and more.
  • the terminal 300 shown in FIG. 26 is only an implementation manner of the present application. In actual applications, the terminal 300 may further include more or fewer components, which is not limited herein.
  • FIG. 27 illustrates a network device 400 provided by some embodiments of the present application.
  • the network device 400 may include a communication interface 403, one or more network device processors 401, a transmitter 407, a receiver 409, a coupler 411, an antenna 413, and a memory 405. These components may be connected through a bus or other methods.
  • FIG. 27 uses a bus connection as an example. among them:
  • the communication interface 403 may be used for the network device 400 to communicate with other communication devices, such as terminal devices or other base stations.
  • the terminal device may be the terminal 300 shown in FIG. 26.
  • the communication interface 301 refers to an interface between the network device processor 401 and a transceiver system (consisting of a transmitter 407 and a receiver 409), such as the S1 interface in LTE.
  • the communication interface 403 may include a Global System for Mobile Communications (GSM) (2G) communication interface, a Wideband Code Division Multiple Access (WCDMA) (3G) communication interface, and a Long Term Evolution (LTE) (4G) communication interface, etc.
  • GSM Global System for Mobile Communications
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • the network device 400 may also be configured with a wired communication interface 403 to support wired communication.
  • a backhaul link between one network device 400 and another network device 400 may be a wired communication connection.
  • the antenna 413 may be used to convert electromagnetic energy in a transmission line into electromagnetic waves in a free space, or convert electromagnetic waves in a free space into electromagnetic energy in a transmission line.
  • the coupler 411 can be used to divide the mobile communication signal into multiple channels and distribute the signals to multiple receivers 409.
  • the transmitter 407 may be configured to perform transmission processing on a signal output by the network device processor 401, for example, to modulate the signal in a licensed frequency band or to modulate a signal in an unlicensed frequency band.
  • the transmitter 407 may support the network device 400 to transmit signals on one or more unlicensed spectrums, or may also support the network device 400 to transmit signals on one or more licensed spectrums.
  • the receiver 409 may be configured to perform reception processing on a mobile communication signal received by the antenna 413.
  • the receiver 409 may demodulate a received signal that has been modulated on an unlicensed frequency band, and may also demodulate a received signal that is modulated on a licensed frequency band.
  • the receiver 409 may support the network device 400 to receive a signal modulated on an unlicensed spectrum, or may also support the network device 400 to receive a signal modulated on an authorized spectrum.
  • the transmitter 407 and the receiver 409 may be considered as a wireless modem.
  • the number of the transmitters 407 and the receivers 409 may be one or more.
  • the memory 405 is coupled to the network device processor 401 and is configured to store various software programs and / or multiple sets of instructions.
  • the memory 405 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 405 may store an operating system (hereinafter referred to as a system), such as an embedded operating system such as uCOS, VxWorks, and RTLinux.
  • the memory 405 may also store a network communication program, which can be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.
  • the network device processor 401 may be used to perform wireless channel management, implement call and communication link establishment and removal, and control handover of user equipment in the control area.
  • the network device processor 401 may include: an Administration / Communication Module / Communication Module (AM / CM) (a center for voice path exchange and information exchange), a basic module (Basic Module (BM)) To complete call processing, signaling processing, wireless resource management, wireless link management and circuit maintenance functions), code conversion and submultiplexing unit (Transcoder and SubMultiplexer (TCSM) (for completing multiplexing demultiplexing and code conversion Features) and so on.
  • AM / CM Administration / Communication Module / Communication Module
  • BM Basic Module
  • TCSM Transcoder and SubMultiplexer
  • the network device processor 401 may be used to read and execute computer-readable instructions.
  • the network device processor 401 may be configured to call a program stored in the memory 405, for example, an implementation program of the RRC connection release method provided by one or more embodiments of the present application on the network device 400 side, and execute the program included in the program. instruction.
  • the network device processor 401 may be a modem processor, and is a module that implements main functions in wireless communication standards such as 3GPP and ETSI.
  • the modem can be used as a separate chip or form a system-level chip or integrated circuit with other chips or circuits. These chips or integrated circuits can be applied to all network-side devices that implement wireless communication functions.
  • eNB evolved NodeB
  • eNodeB evolved NodeB
  • Node B Node B
  • NR NodeB, gNB 5G base station
  • the network device processor 401 may be used as a separate chip and coupled with the off-chip memory, that is, the chip does not include a memory; or the network device processor 401 processor is coupled with the on-chip memory and Integrated in the chip, that is, the chip contains memory.
  • the network device 400 may be the network device 101 in the wireless communication system 100 shown in FIG. 1, and may be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), and an extended service set (ESS). , NodeB, eNodeB, etc.
  • the network device 400 may be implemented as several different types of base stations, such as a macro base station, a micro base station, and the like.
  • the network device 400 may apply different wireless technologies, such as a cell wireless access technology, or a WLAN wireless access technology.
  • the network device 400 shown in FIG. 27 is only an implementation manner of the present application. In actual applications, the network device 400 may further include more or fewer components, which is not limited herein.
  • FIG. 28 is a wireless communication system 10 and a network device 500 and a terminal 600 in the wireless communication system 10 according to an embodiment of the present application.
  • the network device 500 may be the network device in the foregoing method embodiment
  • the terminal 600 may be the terminal in the foregoing method embodiment.
  • the terminal 600 may include a processing unit 601 and a communication unit 603. among them:
  • the processing unit 601 may be configured to trigger an RRC connection release request
  • the communication unit 603 may be configured to send the first media access control entity MAC CE to the network device 500, where the first MAC CE includes first indication information, and the first indication information indicates that the first MAC CE is used for The network device 500 is requested to initiate an RRC connection release process.
  • the communication unit 501 may be further configured to receive an RRC connection release message sent by the network device.
  • the processing unit 601 may be further configured to release the RRC connection according to the RRC connection release message, and transition from the RRC connected state to the RRC idle state or the RRC inactive state.
  • the processing unit 601 may be further configured to cancel the RRC connection release request when any one of the following conditions is satisfied: the multiplexing and combining process of the terminal generates the first MAC CE, the The terminal sends a MAC PDU including the first MAC CE.
  • the network device 500 may include a communication unit 501 and a processing unit 503. among them:
  • the communication unit 501 may be configured to receive a first MAC access control entity MAC CE sent by the terminal 600, where the first MAC CE includes first indication information, where the first indication information indicates that the first MAC CE is used for requesting The network device initiates an RRC connection release process.
  • the processing unit 503 may be configured to analyze the first MAC CE received by the communication unit 501.
  • the communication unit 501 may be further configured to send an RRC connection release message to the terminal according to the first MAC CE.
  • the terminal 600 sends a MAC CE for the RRC connection release request to the network device 500.
  • the network device 500 may decide to send an RRC connection release message / RRC release message to the terminal 600 to initiate the RRC connection release process of the terminal 600.
  • the terminal 600 in the RRC connected state can be switched to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, instead of waiting for a period of time after the counter expires and then switched to the RRC idle or RRC inactive state , Which is beneficial to reducing the power consumption of the terminal 600.
  • the trigger conditions of the RRC connection release request may include:
  • the first trigger condition the terminal has no services to transmit in the near future. Once the terminal determines that no service needs to be transmitted for a period of time after the current time, the terminal triggers an RRC connection release request. In this application, this period of time may be referred to as the first time, and the first time may be 20-30s, or other values.
  • the second trigger condition the uplink data currently transmitted by the terminal is the last uplink data packet of the current service. Once the terminal determines that the currently transmitted uplink data is the last uplink data packet of the current service, the terminal triggers an RRC connection release request.
  • the specific implementation of the first MAC CE may include:
  • the first MAC CE can be implemented by reusing the BSR MAC CE defined in the existing protocol.
  • the first indication information may include: a value in the MAC subheader corresponding to the BSR MAC CE is a reserved LCID value (such as a value or a value range in 100010-110100)
  • the LCID field, and / or, the reserved bit R in the MAC subheader corresponding to the BSR MAC and CE takes the first value (such as 1). That is to say, the reserved LCID value or reserved bit R in the MAC subheader corresponding to the existing BSR MAC CE can be used to indicate that the BSR MAC CE is a special MAC CE, which is used for RRC connection release request, that is, MAC CE for RRC ConnectionReleaseRequest.
  • the value of the buffer size field in the BSR MAC CE is 0; the LCG ID field in the BSR MAC CE The value can be the ID of any LCG terminated, or the ID of the LCG containing the logical channel with the highest priority, or 0.
  • the BSR MAC may include only one bitmap byte, and the value of each bit in the bitmap byte Both are 0, indicating that there is no data buffer in the logical channel group corresponding to each bit. It can be seen that, since the buffer size field in the existing BSR MAC and CE is omitted, the first MAC CE can save bit overhead.
  • the first indication information may further include: a buffer size field that is set to a buffer size reserved value (that is, 255). That is to say, it is also possible to use the reserved buffer size value in the existing long BSR format or long truncated BSR format BSR MAC CE to indicate that the BSR MAC CE is a special MAC CE for RRC connection release request, that is, MAC CE for RRC Connection Release Request.
  • the BSR MAC CE may include only a bitmap byte and a buffer size field.
  • the first MAC CE may be a newly defined MAC CE.
  • the bit length of the newly defined MAC CE may be fixed to 0 bits; the first indication information carried in the first MACCE may include: a value in the MAC subheader corresponding to the newly defined MAC CE is reserved for LCID LCID field of a value (such as a value or a range of values in 100010-110100), and / or, a reserved bit R having a first value (such as 1) in a MAC subheader corresponding to the newly defined MAC CE. That is, the reserved LCID value or the reserved bit R in the MAC subheader may be used to indicate that the first MAC CE is used for the RRC connection release request.
  • the first MAC CE may carry the second indication information to indicate the RRC state to which the terminal preference is transferred.
  • the RRC state to which the terminal preference is transferred may include an RRC idle state or an RRC inactive state.
  • the first MAC CE may carry the third indication information to indicate whether the terminal needs to receive a downlink data packet or does not need to receive a downlink data packet after sending the last uplink data packet.
  • the priority of the first MAC CE when performing logical channel priority processing may be considered as follows:
  • the priority of the first MAC when performing logical channel priority processing may be lower than the priorities of the following: C-RNTI MAC, CE, Configured Grant, MAC CE, BSR MAC except CE padding, MAC BSR, MAC CE, PHR MAC, CE, data from any logical channel except data from UL-CCCH.
  • the first MAC CE can be prevented from preempting the resources carrying the data, and the data can be transmitted normally.
  • the priority of the first MAC CE when performing logical channel priority processing may be lower than the priority of the following items: C-RNTI MAC, CE, Configured Grant Confirm MAC CE, except for BSR MAC pad CE used for padding BSR MAC CE.
  • an embodiment of the present invention also provides a wireless communication system.
  • the wireless communication system may be the wireless communication system 100 shown in FIG. 1 or the wireless communication system 10 shown in FIG. 28, and may include: network equipment And terminal.
  • the terminal may be the terminal in the foregoing embodiment, and the network device may be the network device in the foregoing embodiment.
  • the terminal may be the terminal 300 shown in FIG. 26, and the network device may be the network device 400 shown in FIG. 27.
  • the terminal may also be the terminal 600 in the embodiment of FIG. 28, and the network device may also be the network device 500 in the embodiment of FIG. 28.
  • the network and the terminal reference may be made to the foregoing embodiments, and details are not described herein again.
  • the terminal processor 304 is configured to call an instruction stored in the memory 312 to control the transmitter 306 to transmit and control the receiver 308 to receive.
  • the transmitter 306 is configured to support a terminal to perform a process of transmitting data and / or signaling.
  • the receiver 308 is used to support the terminal to perform a process of receiving data and / or signaling.
  • the memory 312 is configured to store program codes and data of the terminal.
  • the terminal processor 304 may be used to trigger an RRC connection release request.
  • the transmitter 306 may be used to transmit the first MAC CE.
  • the first MAC CE is used for the RRC connection release request.
  • the network device can decide to send an RRC connection release message / RRC release message to the terminal to initiate the RRC connection release process of the terminal, so that the terminal in the RRC connected state can end the service.
  • the specific implementation of the first MAC CE reference may be made to the foregoing embodiment, and details are not described herein again.
  • the network device processor 405 is configured to control the transmitter 407 to perform transmission and control the receiver 409 to perform reception.
  • the transmitter 407 is configured to support a network device to perform a process of transmitting data and / or signaling.
  • the receiver 409 is used to support a network device to perform a process of receiving data and / or signaling.
  • the memory 405 is configured to store program code and data of a network device.
  • the receiver 409 may be mainly used to receive a first MAC CE sent by a terminal.
  • the transmitter 407 may be mainly configured to send an RRC connection release message / RRC release message according to the first MAC CE.
  • the RRC connection release process of the terminal can be initiated, and the terminal in the RRC connected state can be switched to the RRC idle state or the RRC inactive state as soon as possible after ending the service transmission, instead of waiting for a period of time after the counter expires,
  • the RRC idle state or the RRC inactive state is beneficial to reducing the power consumption of the terminal.
  • the specific implementation of the first MAC CE reference may be made to the foregoing embodiment, and details are not described herein again.
  • FIG. 29 is a schematic structural diagram of a device provided by the present application.
  • the device 50 may include a processor 501 and one or more interfaces 502 coupled to the processor 501. among them:
  • the processor 501 may be used to read and execute computer-readable instructions.
  • the processor 501 may mainly include a controller, an arithmetic unit, and a register.
  • the controller is mainly responsible for decoding the instructions and issuing control signals for the operations corresponding to the instructions.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations. It can also perform address operations and conversions.
  • Registers are mainly responsible for storing register operands and intermediate operation results temporarily stored during instruction execution.
  • the hardware architecture of the processor 501 may be an application specific integrated circuit (ASIC) architecture, a MIPS architecture, an ARM architecture, or an NP architecture.
  • the processor 501 may be single-core or multi-core.
  • the interface 502 can be used to input data to be processed to the processor 501, and can output the processing result of the processor 501 to the outside.
  • the interface 502 may be a general input / output (GPIO) interface, and may be connected to multiple peripheral devices (such as a radio frequency module, etc.).
  • the interface 502 may also include multiple independent interfaces, such as an Ethernet interface, a mobile communication interface (such as an X1 interface), etc., which are respectively responsible for communication between different peripheral devices and the processor 501.
  • the processor 501 may be used to call an implementation program of the RRC connection release method provided by one or more embodiments of this application on a network device side or a terminal side from a memory, and execute instructions included in the program.
  • the interface 502 can be used to output the execution result of the processor 501.
  • the interface 503 may be specifically used to output the processing result of the processor 501.
  • the processor 501 may be configured to trigger the RRC connection request according to the foregoing trigger condition 1 or the foregoing trigger condition 2 of the RRC connection release request, and generate a first MAC CE.
  • the interface 503 may be used to output the first MAC CE generated by the processor 501.
  • the interface 503 may output the first MAC CE to the transmitter, and the transmitter may be configured to transmit the first MAC CE.
  • the interface 503 may be used to input the first MAC CE received by the receiver to the processor 501, and the processor 501 may be used to parse the first MAC CE.
  • the processor 501 may be further configured to generate an RRC connection release message according to the first MAC CE.
  • the interface 503 may also be used to output an RRC connection release message generated by the processor 501.
  • the interface 503 may output an RRC connection release message to a transmitter, and the transmitter may be used to transmit an RRC connection release message.
  • processor 501 and the interface 502 can be implemented through hardware design, software design, or a combination of software and hardware, which is not limited here.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented in a manner that a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules.
  • Software modules can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EPROM, EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC can be located in a transceiver or a relay device.
  • the processor and the storage medium may also exist as discrete components in a radio access network device or a terminal device.
  • the functions described in the embodiments of the present invention may be implemented by hardware, software, firmware, or any combination thereof.
  • the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

本申请涉及RRC连接释放方法、相关设备及系统，RRC连接释放方法由终端而非网络设备来确定终端业务传输结束与否。在终端确定业务传输结束后，终端向网络设备发送用于RRC连接释放请求的MAC CE。网络设备在收到用于RRC连接释放请求的MAC CE后，便可以决定向终端发送RRC连接释放消息或RRC释放消息，以发起该终端的RRC连接释放过程。这样，便可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或RRC非激活态，有利于降低终端功耗。

Description

RRC连接释放方法、相关设备及系统 技术领域
本申请涉及无线通信技术领域，尤其涉及一种RRC连接释放方法、相关设备及系统。
背景技术
在长期演进(long term evolution，LTE)系统中，用户设备(user equipment，UE)的无线资源控制(radio resource control，RRC)状态包括两种：RRC连接态(RRC_CONNECTED)和RRC空闲态(RRC_IDLE)。当UE没有业务时，UE会处于RRC空闲态。当UE有业务时，UE需要转入RRC连接态来进行数据传输。相比于RRC连接态，UE在RRC空闲态更节省功耗。
在5G新空口(new radio，NR)第一版本中，在RRC_CONNECTED和RRC_IDLE两个RRC状态的基础上，引入了RRC非激活态(RRC_INACTIVE)。UE在RRC非激活态下的行为和在RRC空闲态下的行为基本一致，因此，UE在RRC非激活态下和在RRC空闲态下有相同的节能效果，即比UE在RRC连接态下要节省功耗。
现有技术中，基站可以向UE发送RRC连接释放消息/RRC释放消息(RRCConnectionRelease/RRCRelease)，以发起该UE的RRC连接释放过程。这样，UE在收到RRC连接释放消息/RRC释放消息后，便可以释放RRC连接，从RRC_CONNECTED状态转换为RRC_IDLE状态或RRC_INACTIVE状态。
但是，为了避免UE从RRC_CONNECTED状态进入RRC_IDLE状态/RRC_INACTIVE状态后，很快再次进入RRC_CONNECTED状态的乒乓转化。现有技术没有让处于RRC_CONNECTED状态下的UE在结束业务传输后尽快转入RRC_IDLE状态/RRC_INACTIVE状态，而是继续保持RRC_CONNECTED状态一段时间。这样不利于降低UE功耗。
发明内容
本申请提供了一种RRC连接释放方法、相关设备及系统，可节省终端功耗。
第一方面，本申请提供了一种RRC连接释放方法，应用于终端侧，该方法可包括：终端触发RRC连接释放请求，向网络设备发送第一MAC CE。第一MAC CE携带第一指示信息，第一指示信息指示第一MAC CE用于请求所述网络设备发起RRC连接释放过程。
具体的，终端可以在RRC连接释放请求的触发条件被满足的条件下，触发RRC连接释放请求。RRC连接释放请求的触发条件的实质是终端业务结束。也即是说，一旦终端确定终端业务结束，便可以触发RRC连接释放请求。
第二方面，本申请提供了一种RRC连接释放方法，应用于网络设备侧，该方法可包括：网络设备接收终端发送的第一MAC CE，可以根据第一MAC CE决定向终端发送第一MAC CE。这样，终端接收到网络设备发送的RRC连接释放消息/RRC释放消息后，便可以释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
可选的，网络设备在接收到终端发送的用于RRC连接释放请求的MAC CE后，可以决定立即发起该终端的RRC连接释放过程。可选的，网络设备在接收到终端发送的该MAC CE之后，也可以稍微等待短暂时间(如30-50ms)，再决定发起该终端的RRC连接释放过程。可选的，网络设备在接收到终端发送的该MAC CE之后，还可以再等待终端接一个或几个少量下行数据包后，再决定发起该终端的 RRC连接释放过。
实施第一方面和第二方面提供的方法，可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或者RRC非激活态，有利于降低终端功耗。
结合第一方面或第二方面，在一些可选的实施例中，RRC连接释放请求的触发条件可包括：
1.第1种触发条件：终端在不久的将来没有业务需要传输。一旦终端确定当前时刻之后的一段时间内没有业务需要传输，终端便触发RRC连接释放请求。本申请中，可以将这一段时间称为第一时间，第一时间可以为20-30s，或其他值。
关于第1种触发条件的具体实现，可参考后续实施例，这里先不赘述。
2.第2种触发条件：终端当前传输的上行数据是当前业务的最后一个上行数据包。一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，终端便触发RRC连接释放请求。
具体的，第2种触发条件被满足可能会有两种情况：
情况一(case 1)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后不会再接收下行数据包。
情况二(case 2)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收一个下行数据包。
也即是说，在终端传输最后一个上行数据包后可能存在两种情况：终端不再接收下行数据包，或终端需要再接收一个下行数据包。
在情况二中，不限于一个下行数据包，还可以是少于第一数据量(即少量)的下行数据包。第一数据量的数据包可以包括一个，或两个，或三个等个数的下行数据包。也即是说，一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收少量下行数据包，终端便可以触发RRC连接释放请求。可选的，该少量下线数据包可以是针对最后一个上行数据包的应答数据包，例如应答/非应答(ACK/NACK)等。
结合第一方面或第二方面，在一些可选实施例中，当RRC连接释放请求的第1种触发条件满足时，终端触发RRC连接释放请求的具体实现可包括以下几种方式：
方式一，可以由高层协议层，如应用层或PDCP层，来确定终端在不久的将来没有业务需要传输。一旦高层协议层(如PDCP层)确定当前时刻之后的一段时间内没有业务需要传输，高层协议层便向MAC层传递指示信息。MAC层在收到该指示信息后便触发RRC连接释放请求。本申请中，可以将该指示信息称为第五指示信息。
方式二，可以由MAC层确定终端在不久的将来没有业务需要传输。一旦MAC层确定当前时刻之后的一段时间内没有业务需要传输，MAC层便触发RRC连接释放请求。
也即是说，终端可以在高层协议层确定near future没有业务，并传递指示信息至MAC层，然后在MAC层触发RRC连接释放请求。终端也可以在MAC层MAC层触发RRC连接释放请求，并触发RRC连接释放请求。
不限于上述两种方式，终端还可以通过其他方式确定near future没有业务，本申请对此不做限制。
结合第一方面或第二方面，在一些可选实施例中，当RRC连接释放请求的第2种触发条件满足时，终端触发RRC连接释放请求的具体实现可包括以下几种方式：
方式一，可以由高层协议层，如应用层或PDCP层，来确定终端当前传输的上行数据是否是当前业务的最后一个上行数据包，并向MAC层传递指示信息。当MAC层收到该指示信息时，MAC层触发 RRC连接释放请求。
具体的，如果高层协议层(如PDCP层)确定是第2种触发条件上述情况一(case 1)被满足，则高层协议层可以向MAC层发送指示信息，该指示信息用于通知MAC层当前业务的最后一个上行数据包之后不会再有下行数据。本申请中，可以将该指示信息称为第六指示信息。当MAC层收到第六指示信息时，MAC层便触发RRC连接释放请求。
具体的，如果高层协议层(如PDCP层)确定是第2种触发条件的上述情况二(case 2)被满足，则高层协议层可以向MAC层发送指示信息，该指示信息用于通知MAC层当前业务的最后一个上行数据包之后还会再有少量下行数据，例如一个下行数据包。本申请中，可以将该指示信息称为第七指示信息。当MAC层收到第七指示信息时，MAC层便触发RRC连接释放请求。
可选的，高层协议层需要在确定其他上行PDCP SDU或者上行PDCP PDU都已经正确发送后，才将第六指示信息或者第七指示信息发送给MAC层。
方式二，可以由高层协议层，如应用层或PDCP层，来确定终端当前传输的上行数据是否是当前业务的最后一个上行数据包，并向MAC层传递指示信息。在MAC层收到该指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求。
具体的，高层协议层(如PDCP层)确定是第2种触发条件的上述情况一(case 1)被满足，则高层协议层可以向MAC层发送第六指示信息。在MAC层收到第六指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求。
具体的，如果高层协议层(如PDCP层)确定是第2种触发条件的上述情况二(case 2)被满足，则高层协议层可以向MAC层发送第七指示信息。在MAC层收到第七指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求。
不限于上述两种方式，终端还可以通过其他方式确定前述第2种触发条件被满足，本申请对此不做限制。
结合第一方面或第二方面，在一些可选的实施例中，第一MAC CE的具体实现可如下：
(1)第一MAC CE可以重用现有协议中定义的BSR MAC CE来实现。
为了和现有协议中定义的其他功能的BSR MAC CE区别开来，第一MAC CE中携带的第一指示信息可以指示第一MAC CE是特殊的BSR MAC CE，第一MAC CE为用于RRC连接释放请求的MAC CE，即MAC CE for RRC Connection Release Request。
方式一，对于现有BSR MAC CE来说，第一指示信息可以包括：BSR MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，BSR MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用现有BSR MAC CE对应的MAC subheader中的预留LCID值或预留比特R来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
可选的，当第一MAC CE具体为短BSR格式或短截断BSR格式的BSR MAC CE时，该BSR MAC CE中的buffer size域的取值为0；该BSR MAC CE中的LCG ID域的取值可以为所终端的任意一个LCG的ID，或者为包含具有最高优先级的逻辑信道的LCG的ID，或者为0。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节，该bitmap字节中的每一个比特的取值均为0，表示各个比特各自对应的逻辑信道组中没有数据缓存。可以看出，由于省去了现有BSR MAC CE中的buffer size域，第一MAC CE可以节约比特开销。
方式二，对于长BSR格式或长截断BSR格式的BSR MAC CE来说，第一指示信息还可包括：取值为buffer size预留值(即255)的buffer size域。也即是说，还可以利用现有长BSR格式或长截断BSR格式的BSR MAC CE中的预留buffer size值来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节和一个buffer size域。
(2)第一MAC CE可以为新定义的MAC CE。
本申请中，该新定义的MAC CE的比特长度可以固定为0个比特；第一MACCE中携带的第一指示信息可包括：该新定义的MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，该新定义的MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用MAC subheader中的预留LCID值或预留比特R来指示第一MAC CE用于RRC连接释放请求。
可以看出，利用新定义的MAC CE来实现第一MAC CE，由于MAC CE部分为0bits，仅有MAC subheader部分，可以节约比特开销。
(3)第一MAC CE可以携带第二指示信息，以指示终端偏好转移到的RRC状态。
终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。
可选的，第二指示信息可包括但不限于以下两种实现方式：
1.方式一，第二指示信息可以为该新定义的MAC CE对应的MAC subheader中的第一指示比特。当第一指示比特的取值为第三值(如1)时，表示终端偏好转移到的RRC状态为RRC空闲态，当第一指示比特的取值为第四值(如0)时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用该新定义的MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指示比特)指示终端偏好转移到的RRC状态。
2.方式二，第二指示信息可以为MAC subheader中的LCID域，当LCID域的取值为第
一预留LCID值时，表示终端偏好转移到的RRC状态为RRC空闲态，当LCID域的取值为第二预留LCID值时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用MAC subheader中的LCID域的预留LCID值指示终端偏好转移到的RRC状态。LCID域的预留LCID值不仅可以将第一MAC CE与现有BSR MAC CE区别开来，还可以同时指示出终端偏好转移到的RRC状态。
(4)第一MAC CE可以携带第三指示信息，以指示终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包。
可选的，第三指示信息可包括但不限于以下两种实现方式：
1.方式一，第三指示信息可以为MAC subheader中的第二指示比特。
当第二指示比特的取值为第五值(如1)时，表示终端在发送最后一个上行数据之后需要再接收一个下行数据；当第二指示比特的取值为第六值(如0)时，表示终端在发送最后一个上行数据之后不需要接收下行数据。
也即是说，可利用现有的BSR MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指示比特)区别指示第2种触发条件的case1和case2。
2.方式二，第三指示信息可以为MAC subheader中的LCID域。
当LCID域的取值为第三预留LCID值时，表示终端在发送最后一个上行数据包之后需要再接收一个下行数据包；当LCID域的取值为第四预留LCID值时，表示终端在发送最后一个上行数据包之后不需要接收下行数据包。
也即是说，可利用现有BSR MAC CE对应的MAC subheader中的LCID域的预留LCID值区别指示第2种触发条件的case1和case2。LCID域的预留LCID值不仅可以将第一MAC CE与现有BSR MAC CE区别开来，还可以同时区别指示第2种触发条件的case1和case2。
(4)第一MAC CE可以既指示终端偏好转移到的RRC状态，也指示终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
1.方式一，第一MAC CE可以同时携带第一指示比特和第二指示比特，第一指示比特和第二指示比特为MAC subheader中的两个不同的指示比特。
具体的，如图23所示，第一MAC CE对应的MAC subheader可以如图23示例性所示。其中，比特I即第一指示比特，用于指示终端偏好转移到的RRC状态；比特D即第二指示比特，用于区别指示第2种触发条件的case1和case2；LCID域的取值为图9示出的表格中的预留LCID值(如100010–110100中的100011)中的一个值或一个值范围。比特I、比特D可以是MAC subheader中的预留比特R。
2.方式二，第一MAC CE可以携带第四指示信息，第四指示信息指示终端偏好转移到的RRC状态，以及，终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
具体的，第四指示信息为MAC subheader中的LCID域，可指示如下四种情况：
当LCID域的取值为第五预留LCID值(如100010–110100中的100010)时，表示终端偏好转移到的RRC状态为RRC空闲态且终端在发送最后一个上行数据之后需要再接收一个下行数据；
当LCID域的取值为第六预留LCID值(如100010–110100中的100011)时，表示终端偏好转移到的RRC状态为RRC非激活态且终端在发送最后一个上行数据之后需要再接收一个下行数据；
当LCID域的取值为第七预留LCID值(如100010–110100中的100100)时，表示终端偏好转移到的RRC状态为RRC空闲态且终端在发送最后一个上行数据之后不需要接收下行数据；
当LCID域的取值为第八预留LCID值(如100010–110100中的100101)时，表示终端偏好转移到的RRC状态为RRC非激活态且终端在发送最后一个上行数据之后不需要接收下行数据。
也即是说，LCID域的预留LCID值不仅可以将第一MAC CE与现有的其他功能的BSR MAC CE区别开来，还可以指示上述四种情况中的任意一种。
结合第一方面或第二方面，在一些可选的实施例中，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了padding BSR MAC CE外的BSR MAC CE、PHR MAC CE、除来自UL-CCCH的数据外的来自任意逻辑信道的数据。这样，可以避免第一MAC CE抢占承载数据的资源，确保数据正常传输。
结合第一方面或第二方面，在一些可选的实施例中，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了用于padding的BSR MAC CE外的BSR MAC CE。
结合第一方面或第二方面，在一些可选的实施例中，如果终端没有用于承载第一MAC CE的足够的上行资源，则终端触发调度请求SR。
第三方面，提供了一种终端，包括多个功能单元，用于相应的执行第一方面可能的实施方式中的任意一种所提供的方法。
第四方面，提供了一种网络设备，包括多个功能单元，用于相应的执行第二方面可能的实施方式中 的任意一种所提供的方法。
第五方面，提供了一种终端，用于执行第一方面描述的RRC连接释放方法。所述网络设备可包括：存储器以及与所述存储器耦合的处理器、发射器和接收器，其中：所述发射器用于与向另一无线通信设备发送信号，所述接收器用于接收所述另一无线通信设备发送的信号，所述存储器用于存储第一方面描述的RRC连接释放方法的实现代码，所述处理器用于执行所述存储器中存储的程序代码，即执行第一方面可能的实施方式中的任意一种所描述的RRC连接释放方法。
第六方面，提供了一种网络设备，用于执行第二方面描述的RRC连接释放方法。所述终端可包括：存储器以及与所述存储器耦合的处理器、发射器和接收器，其中：所述发射器用于与向另一无线通信设备发送信号，所述接收器用于接收所述另一无线通信设备发送的信号，所述存储器用于存储第二方面描述的RRC连接释放方法的实现代码，所述处理器用于执行所述存储器中存储的程序代码，即执行第二方面可能的实施方式中的任意一种所描述的RRC连接释放方法。
第七方面，提供了一种通信系统，所述通信系统包括：网络设备和终端，其中：所述终端可以是第一方面描述的终端。所述网络设备可以是第二方面描述的网络设备。
第八方面，提供了一种计算机可读存储介质，所述可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面描述的RRC连接释放方法。
第九方面，提供了另一种计算机可读存储介质，所述可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面描述的RRC连接释放方法。
结合第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面描述的RRC连接释放方法。
结合第十一方面，提供了另一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面描述的RRC连接释放方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请提供的一种无线通信系统的架构示意图；
图2A-2B是现有的释放RRC连接的流程；
图3是本申请提供的RRC连接释放方法的总体流程示意图；
图4-5是现有的BSR MAC CE的几种格式示意图；
图6是现有的短BSR或短截断BSR的BSR MAC CE的buffer size域的取值示意图；
图7是现有的长BSR或长截断BSR的BSR MAC CE的buffer size域的取值示意图；
图8-9是现有的MAC subheader的几种格式示意图；
图10是现有的MAC subheader中的LCID域的取值示意图；
图11是本申请的一个实施例提供的RRC连接释放方法的流程示意图；
图12是终端触发RRC连接释放请求的一种实现的流程示意图；
图13-14是本申请提供的第一MAC CE对应的几种MAC subheader的示意图；
图15是本申请的另一个实施例提供的RRC连接释放方法的流程示意图；
图16是本申请提供的第一MAC CE对应的一种MAC subheader的示意图；
图17是本申请的再一个实施例提供的RRC连接释放方法的流程示意图；
图18A-18B是终端触发RRC连接释放请求的2种实现的流程示意图；
图19是SDU和PDU的关系示意图；
图20A-20B是终端触发RRC连接释放请求的2种实现的流程示意图；
图21-23是本申请提供的第一MAC CE对应的几种MAC subheader的示意图；
图24是本申请的再一个实施例提供的RRC连接释放方法的流程示意图；
图25是本申请提供的第一MAC CE对应的一种MAC subheader的示意图；
图26是本申请的一个实施例提供的终端设备的硬件架构示意图；
图27是本申请的一个实施例提供的网络设备的硬件架构示意图；
图28是本申请的提供的无线通信系统，终端和网络设备的功能框图；
图29是本申请的一种处理器的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
图1示出了本申请涉及的无线通信系统100。无线通信系统100可以工作在高频频段上，可以是第五代移动通信(the 5th Generation，5G)系统、新空口(new radio，NR)系统，还可以是长期演进(Long Term Evolution，LTE)系统，机器与机器通信(Machine to Machine，M2M)系统，未来演进的第六代通信系统等。如图1所示，无线通信系统100可包括：一个或多个网络设备101，一个或多个终端103，以及核心网115。其中：
网络设备101可以为基站，基站可以用于与一个或多个终端进行通信，也可以用于与一个或多个具有部分终端功能的基站进行通信(比如宏基站与微基站，如接入点，之间的通信)。基站可以是时分同步码分多址(Time Division Synchronous Code Division Multiple Access，TD-SCDMA)系统中的基站收发台(Base Transceiver Station，BTS)，也可以是LTE系统中的演进型基站(Evolutional Node B，eNB)，以及5G系统、新空口(NR)系统中的基站。另外，基站也可以为接入点(Access Point，AP)、传输节点(Trans TRP)、中心单元(Central Unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的一些或所有功能。
终端103可以分布在整个无线通信系统100中，可以是静止的，也可以是移动的。在本申请的一些实施例中，终端103可以是用户设备UE、移动设备、移动台(mobile station)、移动单元(mobile unit)、M2M终端、无线单元，远程单元、用户代理、移动客户端等等。
具体的，网络设备101可用于在网络设备控制器(未示出)的控制下，通过无线接口105与终端103通信。在一些实施例中，所述网络设备控制器可以是核心网115的一部分，也可以集成到网络设备101中。具体的，网络设备101可用于通过回程(blackhaul)接口113(如S1接口)向核心网115传输控制信息或者用户数据。具体的，网络设备101与网络设备101之间也可以通过回程(blackhaul)接口111(如X2接口)，直接地或者间接地，相互通信。
需要说明的，图1示出的无线通信系统100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
在LTE和NR中，触发UE从RRC连接态转入RRC空闲态有如下几种现有方案：
方案1：基站发送RRC连接释放消息/RRC释放消息(RRCConnectionRelease/RRCRelease)给UE，UE接收到RRC连接释放消息后，从RRC连接态转入RRC空闲态。
如图2A所示，在方案1中，基站何时发送RRC连接释放消息取决于基站的实现。基站侧会维护一个检测UE活动的计时器。该计时器的名称为InactivityTimer。当该计时器超时后，基站发送RRC连接释放消息/RRC释放消息给UE。根据从现网中获取的数据，一般该计时器在UE结束业务传输后，会再运行10～20s左右。这样也就意味着UE在业务传输结束后，UE还需要保持RRC连接态10～20s。因此，会导致UE不必要的额外功耗。
方案2：基站为UE配置一个计时器。当UE有任何上行或者下行传输时，包括信令和数据，UE都会重启该计时器。而当该计时器超时后，UE自动转入RRC空闲态。
如图2B所示，在方案2中，在UE进入RRC连接态后，基站会通过RRC连接重配置消息/RRC重配消息(RRCConnectionReconfiguration/RRCReconfiguration)为UE配置一个计时器。该计时器的名称为DataInactivityTimer。UE的媒体接入控制(media access control，MAC)实体会维护该计时器。当UE的MAC实体在专用业务信道(dedicated traffic channel，DTCH)，或者专用控制信道(dedicated control channel，DCCH)或者公共控制信道(common control channel，CCCH)上接收到数据时，或者当UE的MAC实体在专用业务信道，或者专用控制信道上传输数据时，UE都需要启动或者重启该计时器。当该计时器超时时，MAC实体会发送指示通知UE的RRC层。当RRC层接收到该指示后，会发起从RRC连接态到RRC空闲态的状态转移，从而释放RRC连接。
方案2的主要作用是为了克服UE没有成功接收到基站发送的RRC连接释放消息而造成的UE和基站侧的RRC状态不一致，从而导致UE一致处于RRC连接态的问题。一般情况下，方案2中的DataInactivityTimer的定时长度会比方案1中基站侧维护的Inactivity Timer的定时长度更长。
可以看出，现有技术都会让UE在业务结束后还会在RRC连接态下再保持一段时间。具体的，上述方案1中，UE在业务结束后还会在RRC连接态下再保持10-20s，上述方案2中，UE在业务结束后还会在RRC连接态下再保持超多10-20s的时间。主要是为了避免UE从RRC连接态进入RRC空闲态/非激活态后，很快再次进入RRC连接态的乒乓转化。
但是，现有技术没有让处于RRC连接态下的UE在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，不利于降低UE功耗。这主要是由于基站无法准确估计UE业务结束的时刻。本申请提供的技术方案将基于UE侧实现确定或者估计业务结束的时刻，可实现尽快触发RRC连接释放请求。
为了解决现有的技术问题，本申请提供了一种RRC连接释放方法，可节约终端功耗。
在本申请实施例中，由终端而非网络设备来确定终端业务传输结束与否。在终端确定业务传输结束后，终端向网络设备发送用于RRC连接释放请求的MAC控制实体(control entity，CE)。网络设备在收到用于RRC连接释放请求的MAC CE后，便可以决定向终端发送RRC连接释放消息/RRC释放消息，以发起该终端的RRC连接释放过程。这样，便可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或者RRC非激活态，有利于降低终端功耗。
基于上述描述，下面说明本申请提供的RRC连接释放方法的总体流程。如图3所示，本申请提供的RRC连接释放方法可包括：
S101，终端触发RRC连接释放请求。
具体的，终端可以在RRC连接释放请求的触发条件被满足的条件下，触发RRC连接释放请求。RRC连接释放请求的触发条件的实质是终端业务结束。也即是说，一旦终端确定终端业务结束，便可以触发RRC连接释放请求。后续内容会详细介绍该触发条件，这里先不赘述。
具体的，一旦终端触发RRC连接释放请求后，终端会生成用于RRC连接释放请求的MAC CE(MAC CE for RRC connection release request)。也即是说，终端发送的RRC连接释放请求可以承载于MAC CE中。
S102，终端向网络设备发送用于RRC连接释放请求的MAC CE。相应的，网络设备接收到终端发送的该MAC CE。
本申请中，终端向网络设备发送用于RRC连接释放请求的MAC CE的目的是：请求网络设备发起该终端的RRC连接释放过程。RRC连接释放过程可如图3中的S103-S104所示。
S103-S104，网络设备向终端发送RRC连接释放消息/RRC释放消息。相应的，终端接收网络设备发送的RRC连接释放消息/RRC释放消息，释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
可选的，网络设备在接收到终端发送的用于RRC连接释放请求的MAC CE后，可以决定立即发起该终端的RRC连接释放过程。可选的，网络设备在接收到终端发送的该MAC CE之后，也可以稍微等待短暂时间(如30-50ms)，再决定发起该终端的RRC连接释放过程。可选的，网络设备在接收到终端发送的该MAC CE之后，还可以再等待终端接一个或几个少量下行数据包后，再决定发起该终端的RRC连接释放过。在最后一种可选方式中，终端可以在该MAC CE中指示网络设备在接收到该MAC CE后，等待终端接收一个或几个少量下行数据包，再发起RRC连接释放过程，具体实现可参考后续实施例，这里先不赘述。
本申请中，用于RRC连接释放请求的MAC CE(MAC CE for RRC connection release request)可以称为第一MAC CE。第一MAC CE可以重用现有协议中定义的MAC CE来实现，也可以为新定义的MAC CE。本申请中，第一MAC CE携带第一指示信息，第一指示信息指示第一MAC CE用于RRC连接释放请求。后续内容中会详细介绍第一MAC CE的信令实现，这里先不赘述。另，本申请对第一MAC CE的命名不做限制。
实际应用中，终端还可通过UE能力上报来指示终端自身是否支持触发RRC连接释放请求。相应的，网络设备可以根据终端的指示决定是否允许该终端发送第一MAC CE。具体的，如果终端指示能够支持触发RRC连接释放请求，则由网络设备决定是否允许该终端发送第一MAC CE。如果网络设备允许该终端发送第一MAC CE，则网络设备向终端发送允许其发送第一MAC CE的指示。在接收到该指示后，终端才可以触发和发送第一MAC CE。
实施图3所示的技术方案，由终端而非网络设备来确定终端业务传输结束与否，便可以尽快准确的确定出终端业务传输结束的时刻。终端可以在确定业务传输结束后向网络设备发送第一MAC CE，以请求网络设备发起RRC连接释放过程。这样，便可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，有利于降低终端功耗。
另外，本申请采用MAC CE而非RRC等信令来请求网络设备发起RRC连接释放过程，可进一步降低终端功耗。因为MAC CE相比于RRC等信令省去了自动重传请求(automatic repeat request，ARQ)，更节能。
其次，介绍本申请实施例涉及以下三点(一)至(三)。
(一)RRC连接释放请求的触发条件
1.第1种触发条件：终端在发送或者接收一个数据后，在一段时间内都没有任何数据传输，终端确定不久的将来没有业务需要传输。终端便触发RRC连接释放请求。
本申请中，可以将这一段时间称为第一时间，第一时间可以为几秒，或其他值。例如，第一时间的确定方法可以为：终端如果发现在连续N个非连续接收(discontinuous reception，DRX)周期内，都没有接收到网络设备的发送的对数据发送和接收的调度信息，则终端触发RRC连接释放请求。第一时间即为这N个DRX周期。
关于终端依据第1种触发条件触发RRC连接释放请求的具体实现，可参考后续实施例，这里先不赘述。
2.第2种触发条件：终端当前传输的上行数据是当前业务的最后一个上行数据包。一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，终端便触发RRC连接释放请求。
例如，在终端备份数据到云端的场景中，假设该终端需要备份1G的照片到云端，且备份期间该终端没有其他APP进行数据上传活动，那么终端便可以把这1G照片的数据中最后1个数据包确定为当前业务最后一个上行数据包，当终端传输该最后一个数据包时，终端可触发RRC连接释放请求。
具体的，第2种触发条件被满足可能会有两种情况：
情况一(case 1)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后不会再接收下行数据包。
情况二(case 2)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收一个下行数据包。
也即是说，在终端传输最后一个上行数据包后可能存在两种情况：终端不再接收下行数据包，或终端需要再接收一个下行数据包。
在情况二中，不限于一个下行数据包，还可以是少于第一数据量(即少量)的下行数据包。第一数据量的数据包可以包括一个，或两个，或三个等个数的下行数据包。也即是说，一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收少量下行数据包，终端便可以触发RRC连接释放请求。可选的，该少量下线数据包可以是针对最后一个上行数据包的应答数据包，例如应答/非应答(ACK/NACK)等。
最后一个上行数据包是指最后一个上行PDCP服务数据单元(service data unit，SDU)或者最后一个上行PDCP分组数据单元(packet data unit，PDU)。
关于终端依据第2种触发条件触发RRC连接释放请求的具体实现，可参考后续实施例，这里先不赘述。
(二)第一MAC CE的信令实现
在介绍第一MAC CE的信令实现之前，先介绍现有协议中定义的缓存状态报告(buffer status report，BSR)MAC CE。
(1)BSR MAC CE包含四种格式：
短BSR格式(Short BSR format)，其长度固定，只有1个字节；
短截断BSR格式(Short Truncated BSR format)，其长度固定，只有1个字节；
长BSR格式(Long BSR format)，其长度不固定；
长截断BSR格式(Long Truncated BSR format)，其长度不固定。
其中，短BSR格式和短截断BSR格式对应的BSR MAC CE如图4所示；长BSR格式和长截断BSR格式对应的BSR MAC CE如图5所示。
在图4中，LCG ID域表示逻辑信道组(logical channel group，LCG)的标识。在LTE和NR中， UE都是以逻辑信道组为粒度上报对应的缓存中的数据量的；buffer size域表示LCG ID域对应的逻辑信道组的缓存中的数据量。
在图5中，对于长BSR格式，第一个字节为一个bitmap。该bitmap中的每个bit用于指示是否上报了该bit对应的LCG的buffer size。而对于长截断BSR格式，所述bitmap中的每个bit用于指示该bit对应的LCG是否有数据。各个buffer size域表示各个相应的逻辑信道组的缓存中的数据量。
(2)对于短BSR格式和短截断BSR格式，其缓存大小buffer size用5bit表示，buffer size域的取值以及其表示的数据量如图6示出的表格所示。对于长BSR格式和长截断BSR格式，其缓存大小buffer size用8bit表示，buffer size域的取值以及其表示的数据量如图7示出的表格所示。
(3)BSR MAC CE有对应的MAC subheader。
对于短BSR格式和短截断BSR格式，其对应的MAC subheader如图8所示。
对于长BSR格式和长截断BSR格式，其对应的MAC subheader如图9所示。
其中，R表示预留比特，取值固定设为0。F用于指示L域是1个字节还是2个字节。
L域用于指示对应的可变长度的MAC CE的占用的字节数。LCID域：当包含LCID域的MAC subheader对应的是一个MAC CE时，LCID域用于指示该MAC CE的类型。对于上行MAC CE，LCID域的取值和MAC CE类型之间的对应关系如图10示出的表格所示。从图10可以看出，对于四种BSR格式的MAC CE，分别用四个LCID值来表示。
下面介绍本申请中的第一MAC CE的具体实现。
(1)第一MAC CE可以重用现有协议中定义的BSR MAC CE来实现。
为了和现有协议中定义的其他功能的BSR MAC CE区别开来，第一MAC CE中携带的第一指示信息可以指示第一MAC CE是特殊的BSR MAC CE，第一MAC CE为用于RRC连接释放请求的MAC CE，即MAC CE for RRC Connection Release Request。
方式一，对于现有BSR MAC CE来说，第一指示信息可以包括：BSR MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，BSR MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用现有BSR MAC CE对应的MAC subheader中的预留LCID值或预留比特R来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
对于预留LCID值，如果现有协议中这个范围100010-110100中有个别预留LCID值被用来做其他用途，本申请中提及的对预留LCID值的使用不与该个别预留LCID值发生冲突。
可选的，当第一MAC CE具体为短BSR格式或短截断BSR格式的BSR MAC CE时，该BSR MAC CE中的buffer size域的取值为0；该BSR MAC CE中的LCG ID域的取值可以为所终端的任意一个LCG的ID，或者为包含具有最高优先级的逻辑信道的LCG的ID，或者为0。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节，该bitmap字节中的每一个比特的取值均为0，表示各个比特各自对应的逻辑信道组中没有数据缓存。可以看出，由于省去了现有BSR MAC CE中的buffer size域，第一MAC CE可以节约比特开销。
方式二，对于长BSR格式或长截断BSR格式的BSR MAC CE来说，第一指示信息还可包括：取值为buffer size预留值(即255)的buffer size域。也即是说，还可以利用现有长BSR格式或长截断BSR格式的BSR MAC CE中的预留buffer size值来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节和一个buffer size域。
(2)第一MAC CE可以为新定义的MAC CE。
本申请中，该新定义的MAC CE的比特长度可以固定为0个比特；第一MACCE中携带的第一指示信息可包括：该新定义的MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，该新定义的MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用MAC subheader中的预留LCID值或预留比特R来指示第一MAC CE用于RRC连接释放请求。
对于预留LCID值，如果现有协议中这个范围100010-110100中有个别预留LCID值被用来做其他用途，本申请中提及的对预留LCID值的使用不与该个别预留LCID值发生冲突。
可以看出，利用新定义的MAC CE来实现第一MAC CE，由于MAC CE部分为0bits，仅有MAC subheader部分，可以节约比特开销。
(3)第一MAC CE可以携带指示信息，以指示终端偏好转移到的RRC状态。
终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。该指示信息可以称为第二指示信息。
(4)第一MAC CE可以携带指示信息，以指示终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包。
关于终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包，可具体参考关键技术(一)中的第2种触发条件的内容，这里不再赘述。该指示信息可以称为第三指示信息。
关于第一MAC CE的信令实现的详细描述，可参考后续实施例。
(三)第一MAC CE的传输
1.第一MAC CE在进行逻辑信道优先级处理时的优先级
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)MAC CE、配置授权确认MAC CE(Configured Grant Confirmation MAC CE)、除了填充BSR MAC CE(padding BSR MAC CE)外的BSR MAC CE、功率余量报告MAC CE(power headroom report MAC CE，PHR MAC CE)、除来自上行公共控制信道(uplink common control channel，UL-CCCH)的数据外的来自任意逻辑信道的数据。这样，可以避免第一MAC CE抢占承载数据的资源，确保数据正常传输。
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了用于padding的BSR MAC CE外的BSR MAC CE。
2.为第一MAC CE触发调度请求(scheduling request，SR)
具体的，如果上行资源不能够容纳第一MAC CE，终端触发调度请求SR。
下面结合图11-图25实施例进一步详细说明本申请提供的技术方案。
(一)实施例一
本实施例中，RRC连接释放请求的触发条件为前述第1种触发条件，即：处于RRC_Connected状态 的终端在业务结束后，当确定不久的将来(near future)没有业务时，终端触发RRC连接释放请求。
本实施例中，承载RRC连接释放请求的第一MAC CE重用现有协议中定义的BSR MAC CE来实现。
图11示出了实施例一提供的RRC连接释放方法的具体流程。下面展开：
S201-S202，终端确定当前时刻之后的一段时间内没有业务需要传输。一旦终端确定当前时刻之后的一段时间内没有业务需要传输，终端便可以触发RRC连接释放请求。即，本实施例中的触发RRC连接释放请求的条件为前述第1种触发条件。
本申请中，可以将这一段时间称为第一时间，第一时间可以为20-30s，或其他值。换句话说，一旦终端确定当前时刻之后的第一时间内没有业务需要传输，终端便可以触发RRC连接释放请求。
S203，在触发RRC连接释放请求之后，终端可以判断是否有足够的上行资源来承载用于RRC连接释放请求的MAC CE(即第一MAC CE)。如果没有足够的上行资源，则可以先执行S204-S205，再执行S206；如果有足够的上行资源，则可以直接执行S206。
S204-S205，终端向网络设备发送调度请求SR，以请求获得上行资源承载第一MAC CE。相应的，在收到终端发送的SR后，网络设备为终端调度上行资源，并向终端发送上行授权(UL grant)，UL grant指示网络设备为终端调度的上行资源有哪些。通常，网络设备可以通过下行控制信息(downlink control information，DCL)来携带UL grant。
S206，终端可以重用现有的BSR MAC CE生成用于RRC连接释放请求的MAC CE(即第一MAC CE)。
S207，终端向网络设备发送用于RRC连接释放请求的MAC CE，即第一MAC CE。执行S207的前提是终端具有足够的上行资源承载第一MAC CE。
S208，相应的，网络设备接收终端发送的用于RRC连接释放请求的MAC CE。网络设备向终端发送RRC连接释放消息。
可选的，网络设备在接收到终端发送的用于RRC连接释放请求的MAC CE后，可以决定立即发起该终端的RRC连接释放过程。可选的，网络设备在接收到终端发送的该MAC CE之后，也可以稍微等待短暂时间(如30-50ms)，再决定发起该终端的RRC连接释放过程。
S209，相应的，终端接收到网络设备发送的RRC连接释放消息。终端根据该RRC连接释放消息释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
不限于图11所示，S206也可以在S203之前被执行，即一旦终端触发RRC连接释放请求，终端便可以先生成第一MAC CE，然后再在发送第一MAC CE之前判断上行资源是否能够容纳第一MAC CE，如果上行资源不能够容纳第一MAC CE，则终端触发调度请求SR。
下面详细说明关键技术点(一)至(三)在实施例一中的具体实现。
1.RRC连接释放请求的触发条件
方式一，可以由高层协议层，如应用层或分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层，来确定终端在不久的将来没有业务需要传输。如图12所示，一旦高层协议层(如PDCP层)确定当前时刻之后的一段时间内没有业务需要传输(参考S401)，高层协议层便向MAC层传递指示信息(参考S403)。MAC层在收到该指示信息后便触发RRC连接释放请求(参考S404)。本申请中，可以将该指示信息称为第五指示信息。
方式二，可以由MAC层确定终端在不久的将来没有业务需要传输。一旦MAC层确定当前时刻之后的一段时间内没有业务需要传输，MAC层便触发RRC连接释放请求。
也即是说，终端可以在高层协议层确定near future没有业务，并传递指示信息至MAC层，然后在 MAC层触发RRC连接释放请求。终端也可以在MAC层MAC层触发RRC连接释放请求，并触发RRC连接释放请求。
不限于上述两种方式，终端还可以通过其他方式触发RRC连接释放请求，本申请对此不做限制。
2.第一MAC CE的具体实现
为了和现有的BSR MAC CE进行区别，第一MAC CE携带第一指示信息。第一指示信息指示第一MAC CE是特殊的BSR MAC CE，具体指示第一MAC CE为用于RRC连接释放请求的MAC CE。第一MAC CE的实现方式可包括但不限于：
(1)方式1：如图11所示，第一MAC CE可以是短BSR或短截断BSR格式的BSR MAC CE。该短BSR或短截断BSR格式的BSR MAC CE对应的MAC subheader中LCID域的取值可以为预留LCID值。例如，LCID域的取值可以为预留LCID值100010–110100中一个值或一个取值范围。也即是说，可以利用MAC subheader中的预留LCID值来表示现有BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。也即是说，MAC subheader中取值为预留LCID值的LCID域用于指示该BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。即，第一指示信息可以是MAC subheader中取值为预留LCID值的LCID域。
可选的，该BSR MAC CE中的buffer size域的取值可以为0，即图6所示的表格中序号0对应的BS值(即0)。可选的，该BSR MAC CE中的LCG ID域的取值可以为所终端的任意一个LCG的ID，或者为包含具有最高优先级的逻辑信道的LCG的ID，或者为0。
(2)方式2：第一MAC CE可以是短BSR或短截断BSR格式的BSR MAC CE。该短BSR或短截断BSR格式的BSR MAC CE对应的MAC subheader中预留比特R可用于指示该BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。即，第一指示信息可以是MAC subheader中取值为第一值(如1)的预留比特R。当预留比特R的取值为第一值(如1)时，表示该BSR MAC CE用于RRC连接释放请求。也即是说，可以利用现有BSR MAC CE对应的MAC subheader中的预留比特R来表示该BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。
可选的，该BSR MAC CE中的buffer size域的取值可以为0，即图6所示的表格中序号0对应的BS值(即0)。可选的，该BSR MAC CE中的LCG ID域的取值可以为所终端的任意一个LCG的ID，或者为包含具有最高优先级的逻辑信道的LCG的ID，或者为0。
(3)方式3：不限于图11中示出的短BSR或短截断BSR格式，第一MAC CE也可以是长BSR或长截断BSR格式的BSR MAC CE。该BSR MAC CE中的buffer size域的取值固定为buffer size预留值，即图7所示的表格中序号255对应的BS预留值。也即是说，可以利用现有长BSR或长截断BSR格式的BSR MAC CE中的buffer size预留值来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。即，第一指示信息可以是取值为buffer size预留值的buffer size域。
可选的，该BSR MAC CE中可以仅包含一个bitmap字节和一个buffer size域。
(4)方式4：第一MAC CE可以是长BSR或长截断BSR格式的BSR MAC CE。与方式1相同，可以利用MAC subheader中的预留LCID值来表示现有长BSR或长截断BSR格式的BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。也即是说，MAC subheader中取值为预留LCID值的LCID域用于指示该BSR MAC CE是一个特殊的MAC CE Request。即，第一指示信息可以是MAC subheader中取值为预留LCID值的LCID域。
可选的，该BSR MAC CE中可以仅包含一个bitmap字节，该bitmap字节中的每一个比特的取值均为0，表示各个比特各自对应的逻辑信道组中没有数据缓存。可以看出，由于省去了现有BSR MAC CE中的buffer size域，第一MAC CE可以节约比特开销。
(5)方式5：第一MAC CE可以是长BSR或长截断BSR格式的BSR MAC CE。与方式2相同，可以利用现有BSR MAC CE对应的MAC subheader中的预留比特R来表示该BSR MAC CE是一个特殊的MAC CE，即MAC CE for RRC Connection Release Request。即，第一指示信息可以是MAC subheader中取值为第一值(如1)的预留比特R。
可选的，该BSR MAC CE中可以仅包含一个bitmap字节，该bitmap字节中的每一个比特的取值均为0，表示各个比特各自对应的逻辑信道组中没有数据缓存。可以看出，由于省去了现有BSR MAC CE中的buffer size域，第一MAC CE可以节约比特开销。
3.第一MAC CE的传输
具体的，如果上行资源不能够容纳第一MAC CE，则终端触发调度请求SR。
另外，第一MAC CE在进行逻辑信道优先级处理时的优先级可以有如下考虑：
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了padding BSR MAC CE外的BSR MAC CE、PHR MAC CE、除来自UL-CCCH的数据外的来自任意逻辑信道的数据。这样，可以避免第一MAC CE抢占承载数据的资源，确保数据正常传输。
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了用于padding的BSR MAC CE外的BSR MAC CE。
在实施例一中，在确定near future没有业务之后，终端便触发RRC连接释放请求，并重用现有的BSR MAC CE来请求网络设备发起RRC连接释放过程。实施例一不仅可实现让终端尽快准确的转换为RRC_IDLE或RRC_Inactive状态，节约终端功耗，还可以重用现有MAC CE，充分利用现有MAC CE。
实施例一的相关扩展
用于RRC连接释放请求的现有的BSR MAC CE(即第一MAC CE)可以携带指示信息，以指示终端偏好转移到的RRC状态。终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。该指示信息可以称为第二指示信息。
具体的，第二指示信息可包括但不限于以下两种实现方式：
1.方式一，第二指示信息可以为MAC subheader中的第一指示比特。
当第一指示比特的取值为第三值(如1)时，表示终端偏好转移到的RRC状态为RRC空闲态，当第一指示比特的取值为第四值(如0)时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用现有的BSR MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指示比特)指示终端偏好转移到的RRC状态。
可选的，当第一MAC CE为现有短BSR或短截断BSR格式的BSR MAC CE时，第一MAC CE对应的MAC subheader可以如图13示例性所示。其中，预留比特R的取值可以为0；比特I即第一指示比特，用于指示终端偏好转移到的RRC状态，比特I可以是MAC subheader(图8所示)中包括的2个预留比特R中的一个；LCID域的取值为图10示出的表格中的预留LCID值中的一个值或一个值范围。
可选的，当第一MAC CE为现有长BSR或长截断BSR格式的BSR MAC CE时，第一MAC CE对 应的MAC subheader可以如图14示例性所示。其中，比特I即第一指示比特，比特I可以是MAC subheader(图9所示)中的预留比特R(参考图14中的(B))或比特F(参考图14中的(A))；LCID域的取值为图10示出的表格中的预留LCID值中的一个值或一个值范围。
可选的，当第一指示比特的取值为1时，可表示终端偏好转移到RRC_IDLE状态；当第一指示比特的取值为0时，可表示终端偏好转移到RRC_Inactive状态。此时，第三值为1，第四值为0。反之也可以，当第一指示比特的取值为0时，可表示终端偏好转移到RRC_IDLE状态；当第一指示比特的取值为1时，可表示终端偏好转移到RRC_Inactive状态。此时，第三值为0，第四值为1。可选的，第一指示比特的取值可以由高层协议层(如应用层或RRC层)或MAC层确定。
2.方式二，第二指示信息可以为MAC subheader中的取值为预留LCID值的LCID域。
当LCID域的取值为第一预留LCID值时，表示终端偏好转移到的RRC状态为RRC空闲态，当LCID域的取值为第二预留LCID值时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用MAC subheader中的LCID域的预留LCID值指示终端偏好转移到的RRC状态。LCID域的预留LCID值不仅可以将第一MAC CE与现有BSR MAC CE区别开来，还可以同时指示出终端偏好转移到的RRC状态。
例如，对于一个BSR MAC CE对应的MAC subheader来说，当其中的LCID域取值为预留值100010时，表示该BSR MAC CE用于RRC连接释放请求，且表示终端偏好转移到RRC_IDLE状态；当其中的LCID域取值为预留值100011时，表示该BSR MAC CE用于RRC连接释放请求，且表示终端偏好转移到RRC_Inactive状态。此时，第一预留LCID值为100011，第二预留LCID值为100011。示例仅用于解释本申请，实际应用中，第一预留LCID值、第二预留LCID值可以为图10所示的表格中的预留LCID值中的两个预留值。
在网络设备侧，网络设备可以根据第二指示信息在发送给终端的RRC连接释放消息中决定是否携带转入RRC非激活态的指示信息。例如，如果第二指示信息指示终端偏好转移到RRC_IDLE状态，则网络设备下发的RRC连接释放消息中不携带转入RRC非激活态的指示信息；如果第二指示信息指示终端偏好转移到RRC_Inactive状态，则网络设备下发的RRC连接释放消息中携带转入RRC非激活态的指示信息。这样，终端在请求网络设备发起RRC连接释放过程时具有更多选择，更灵活。
(二)实施例二
本实施例中，RRC连接释放请求的触发条件为前述第1种触发条件，即：处于RRC_Connected状态的终端在业务结束后，当确定不久的将来(near future)没有业务时，终端触发RRC连接释放请求。
本实施例中，承载RRC连接释放请求的第一MAC CE为新定义的MAC CE。
图15示出了实施例二提供的RRC连接释放方法的具体流程。下面展开：
S301-S302，终端确定当前时刻之后的一段时间内没有业务需要传输。一旦终端确定当前时刻之后的一段时间内没有业务需要传输，终端便可以触发RRC连接释放请求。
具体可参考实施例一种的S201-S202，这里不再赘述。
S303，在触发RRC连接释放请求之后，终端可以判断是否有足够的上行资源来承载用于RRC连接释放请求的MAC CE(即第一MAC CE)。如果没有足够的上行资源，则可以先执行S304-S305，再执行S306；如果有足够的上行资源，则可以直接执行S306。
S304-S305，终端向网络设备发送调度请求SR，以请求获得上行资源承载第一MAC CE。相应的，在收到终端发送的SR后，网络设备为终端调度上行资源，并向终端发送上行授权(UL grant)，UL grant 指示网络设备为终端调度的上行资源有哪些。
S306，终端可以利用新定义的MAC CE生成用于RRC连接释放请求的MAC CE(即第一MAC CE)。
S307，终端向网络设备发送用于RRC连接释放请求的MAC CE，即第一MAC CE。执行S207的前提是终端具有足够的上行资源承载第一MAC CE。
S308，相应的，网络设备接收终端发送的用于RRC连接释放请求的MAC CE。网络设备向终端发送RRC连接释放消息。具体可参考实施例一种的S308，这里不再赘述。
S309，相应的，终端接收到网络设备发送的RRC连接释放消息。终端根据该RRC连接释放消息释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
不限于图15所示，S306也可以在S303之前被执行，即一旦终端触发RRC连接释放请求，终端便可以先生成第一MAC CE，然后再在发送第一MAC CE之前判断上行资源是否足够，如果上行资源不够，终端向网络设备发送SR。
下面详细说明(一)至(三)在实施例二中的具体实现。
1.RRC连接释放请求的触发条件
实施例二中的RRC连接释放请求的触发条件的具体实现与实施例一中的RRC连接释放请求的触发条件的具体实现相同，可参考实施例一，这里不再赘述。
2.第一MAC CE的具体实现
如图15所示，第一MAC CE的比特长度可以固定为0个比特。第一MACCE中携带的第一指示信息可包括：BSR MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，BSR MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用MAC subheader中的预留LCID值或预留比特R来指示第一MAC CE用于RRC连接释放请求。
可以看出，利用新定义的MAC CE来实现第一MAC CE，由于MAC CE部分为0bits，仅有MAC subheader部分，可以节约比特开销。
3.第一MAC CE的传输
具体的，如果上行资源不能够容纳第一MAC CE，则终端触发调度请求SR。
另外，第一MAC CE在进行逻辑信道优先级处理时的优先级可以具体参考实施例一的相应内容，这里不再赘述。
在实施例二中，在确定near future没有业务之后，终端便触发RRC连接释放请求，并重用现有的BSR MAC CE来请求网络设备发起RRC连接释放过程。实施例二不仅可实现让终端尽快准确的转换为RRC_IDLE或RRC_Inactive状态，节约终端功耗，还可以利用新定义的MAC CE承载RRC连接释放请求，节约信令开销。
实施例二的相关扩展
用于承载RRC连接释放请求的新定义的MAC CE(即第一MAC CE)可以携带第二指示信息，以指示终端偏好转移到的RRC状态。终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。
具体的，第二指示信息可包括但不限于以下两种实现方式：
1.方式一，第二指示信息可以为该新定义的MAC CE对应的MAC subheader中的第一指示比特。当第一指示比特的取值为第三值(如1)时，表示终端偏好转移到的RRC状态为RRC空闲态，当第一指示比特的取值为第四值(如0)时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用该新定义的MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指示比特)指示终端偏好转移到的RRC状态。
具体的，如图16所示，新定义的MAC CE对应的MAC subheader可包括：预留比特R，比特I，以及LCID域。其中，比特I即为第一指示比特，比特I可以是MAC subheader中包括的某个预留比特R；LCID域的取值为预留LCID值，指示该新定义的MAC CE用于RRC连接释放请求。
2.方式二，第二指示信息可以为MAC subheader中的LCID域，当LCID域的取值为第一预留LCID值时，表示终端偏好转移到的RRC状态为RRC空闲态，当LCID域的取值为第二预留LCID值时，表示终端偏好转移到的RRC状态为RRC非激活态。
也即是说，可利用MAC subheader中的LCID域的预留LCID值指示终端偏好转移到的RRC状态。LCID域的预留LCID值不仅可以将第一MAC CE与现有BSR MAC CE区别开来，还可以同时指示出终端偏好转移到的RRC状态。
具体的，可参考实施例一的相关扩展中的相应内容，这里不再赘述。
(三)实施例三
本实施例中，RRC连接释放请求的触发条件为前述第2种触发条件，即：终端当前传输的上行数据是当前业务的最后一个上行数据包。
具体的，第2种触发条件被满足可能会有两种情况：
情况一(case 1)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后不会再接收下行数据包。
情况二(case 2)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收一个下行数据包。
也即是说，在终端传输最后一个上行数据包后可能存在两种情况：终端不再接收下行数据包，或终端只再接收一个下行数据包。
本实施例中，承载RRC连接释放请求的第一MAC CE重用现有的BSR MAC CE来实现。
图17示出了实施例三提供的RRC连接释放方法的具体流程。下面展开：
S401-S402，终端确定当前传输的上行数据是当前业务的最后一个上行数据包。一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，终端便可以触发RRC连接释放请求。
在上述情况二(case 2)中，不限于一个下行数据包，还可以是少于第一数据量(即少量)的下行数据包。第一数据量的数据包可以包括一个，或两个，或三个等个数的下行数据包。也即是说，一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收少量下行数据包，终端便可以触发RRC连接释放请求。
S403，在触发RRC连接释放请求之后，终端可以判断是否有足够的上行资源来承载用于RRC连接释放请求的MAC CE(即第一MAC CE)。如果没有足够的上行资源，则可以先执行S404-S405，再执行S406；如果有足够的上行资源，则可以直接执行S406。
S404-S405，终端向网络设备发送调度请求SR，以请求获得上行资源承载第一MAC CE。相应的，在收到终端发送的SR后，网络设备为终端调度上行资源，并向终端发送上行授权(UL grant)，UL grant指示网络设备为终端调度的上行资源有哪些。
S406，终端可以利用现有的BSR MAC CE生成用于RRC连接释放请求的MAC CE(即第一MAC CE)。
S407，终端向网络设备发送用于RRC连接释放请求的MAC CE，即第一MAC CE。执行S407的前提是终端具有足够的上行资源承载第一MAC CE。
S408，相应的，网络设备接收终端发送的用于RRC连接释放请求的MAC CE。网络设备向终端发送RRC连接释放消息。
S409，相应的，终端接收到网络设备发送的RRC连接释放消息。终端根据该RRC连接释放消息释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
不限于图17所示，S406也可以在S403之前被执行，即一旦终端触发RRC连接释放请求，终端便可以先生成第一MAC CE，然后再在发送第一MAC CE之前判断上行资源是否足够，如果上行资源不够，终端向网络设备发送SR。
下面详细说明关键技术点(一)至(三)在实施例三中的具体实现。
1.RRC连接释放请求的触发条件
方式一，可以由高层协议层，如应用层或PDCP层，来确定终端当前传输的上行数据是否是当前业务的最后一个上行数据包，并向MAC层传递指示信息。当MAC层收到该指示信息时，MAC层触发RRC连接释放请求。
具体的，如图18A所示，如果高层协议层(如PDCP层)确定是第2种触发条件上述情况一(case 1)被满足(参考S41)，则高层协议层可以向MAC层发送指示信息(参考S43)，该指示信息用于通知MAC层当前业务的最后一个上行数据包之后不会再有下行数据。本申请中，可以将该指示信息称为第六指示信息。当MAC层收到第六指示信息时，MAC层便触发RRC连接释放请求(参考S45)。
具体的，如图18B所示，如果高层协议层(如PDCP层)确定是第2种触发条件的上述情况二(case 2)被满足(参考S40)，则高层协议层可以向MAC层发送指示信息(参考S42)，该指示信息用于通知MAC层当前业务的最后一个上行数据包之后还会再有少量下行数据，例如一个下行数据包。本申请中，可以将该指示信息称为第七指示信息。当MAC层收到第七指示信息时，MAC层便触发RRC连接释放请求(参考S44)。
可选的，高层协议层需要在确定其他上行PDCP SDU或者上行PDCP PDU都已经正确发送后，才将第六指示信息或者第七指示信息发送给MAC层。
方式二，可以由高层协议层，如应用层或PDCP层，来确定终端当前传输的上行数据是否是当前业务的最后一个上行数据包，并向MAC层传递指示信息。在MAC层收到该指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求。
这里，先简单介绍PDU和SDU之间的关系。SDU是指定协议层的用户服务的数据集，传送到接收方的时候同一协议层时数据不会发生变化，即业务部分。SDU被发给下层协议层之后，下层协议层将其封装在PDU中发送出去。如图19所示，第N层SDU和第N层的上一层协议数据单元(PDU)是一一对应的。例如，协议层Protocol#2接收来自上一层协议层Protocol#1的Protocol#1 PDU，将Protocol#1 PDU作为协议层Protocol#2的SDU，即Protocol#2 SDU，然后将其封装在Protocol#2的PDU中。可以看出，协议层Protocol#2的Protocol#2的SDU和协议层Protocol#1的Protocol#1 PDU一一对应。
在方式二中，MAC层发送最后一个上行数据包的部分或全部可以包括但不限于A-C所述的3种情况：
A.在MAC PDU中发送的MAC SDU包含该最后一个上行数据包的全部；
B.在MAC PDU中发送的MAC SDU包含该最后一个上行数据包的最后一部分；
C.在MAC PDU中发送的MAC SDU包含该最后一个上行数据包的第一部分。
不限于A-C所述的3种情况，MAC层发送最后一个上行数据包的部分或全部还可以包括在MAC PDU中发送的MAC SDU包含该最后一个上行数据包的某个中间部分。
具体的，如图20A所示，如果高层协议层(如PDCP层)确定是第2种触发条件的上述情况一(case 1)被满足(参考S51)，则高层协议层可以向MAC层发送第六指示信息(参考S53)。在MAC层收到第六指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求(参考S55-S57)。
具体的，如图20B所示，如果高层协议层(如PDCP层)确定是第2种触发条件的上述情况二(case 2)被满足(参考S50)，则高层协议层可以向MAC层发送第七指示信息(参考S52)。在MAC层收到第七指示信息后，当MAC层发送最后一个上行数据包的部分或全部时，MAC层便触发RRC连接释放请求(参考S54-S56)。
不限于上述两种方式，终端还可以通过其他方式触发RRC连接释放请求，本申请对此不做限制。
2.第一MAC CE的具体实现
同于实施例一中的第一MAC CE的实现，具体可参考实施例一的相应内容，这里不再赘述。
3.第一MAC CE的传输
同于实施例一中的第一MAC CE的传输，具体可参考实施例一的相应内容，这里不再赘述。
在实施例三中，在确定终端当前传输的上行数据是当前业务的最后一个上行数据包，且最后一个上行数据包之后不会再有下行数据包或仅有一个下行数据包时，终端便触发RRC连接释放请求，并重用现有的BSR MAC CE来请求网络设备发起RRC连接释放过程。实施例三不仅可实现让终端尽快准确的转换为RRC_IDLE或RRC_Inactive状态，节约终端功耗，还可以重用现有MAC CE，充分利用现有MAC CE。
实施例三的相关扩展
(1)用于RRC连接释放请求的现有的BSR MAC CE(即第一MAC CE)可以携带指示信息，以指示终端偏好转移到的RRC状态。终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。该指示信息可以称为第二指示信息。第二指示信息的具体实现可参考实施例一的相关扩展，这里不再赘述。
(2)用于RRC连接释放请求的现有的BSR MAC CE(即第一MAC CE)可以携带指示信息，以指示终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包。该指示信息可以称为第三指示信息。也即是说，第三指示信息可以区别指示第2种触发条件的case1和case2。
具体的，第三指示信息可包括但不限于以下两种实现方式：
1.方式一，第三指示信息可以为MAC subheader中的第二指示比特。
当第二指示比特的取值为第五值(如1)时，表示终端在发送最后一个上行数据之后需要再接收一个下行数据；当第二指示比特的取值为第六值(如0)时，表示终端在发送最后一个上行数据之后不需要接收下行数据。
也即是说，可利用现有的BSR MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指示比特)区别指示第2种触发条件的case1和case2。
可选的，当第一MAC CE为现有短BSR或短截断BSR格式的BSR MAC CE时，第一MAC CE对应的MAC subheader可以如图21示例性所示。其中，预留比特R的取值可以为0；比特D即第二指示比特，用于区别指示第2种触发条件的case1和case2，比特D可以是MAC subheader(图8所示)中包括的2个预留比特R中的一个；LCID域的取值为图10示出的表格中的预留LCID值中的一个值或一个 值范围。
可选的，当第一MAC CE为现有长BSR或长截断BSR格式的BSR MAC CE时，第一MAC CE对应的MAC subheader可以如图22示例性所示。其中，比特D即第二指示比特，比特D可以是MAC subheader(图9所示)中的预留比特R(参考图22中的(B))或比特F(参考图22中的(A))；LCID域的取值为图10示出的表格中的预留LCID值中的一个值或一个值范围。
可选的，当第二指示比特的取值为1时，可指示第2种触发条件的case1；当第二指示比特的取值为0时，可指示第2种触发条件的case1。此时，第五值为1，第六值为0。反之也可以，当第二指示比特的取值为0时，可指示第2种触发条件的case1；当第二指示比特的取值为1时，可指示第2种触发条件的case1。此时，第五值为0，第六值为1。可选的，第二指示比特的取值可以由高层协议层(如应用层或RRC层)或MAC层确定。
2.方式二，第三指示信息可以为MAC subheader中的LCID域。
当LCID域的取值为第三预留LCID值时，表示终端在发送最后一个上行数据包之后需要再接收一个下行数据包；当LCID域的取值为第四预留LCID值时，表示终端在发送最后一个上行数据包之后不需要接收下行数据包。
也即是说，可利用现有BSR MAC CE对应的MAC subheader中的LCID域的预留LCID值区别指示第2种触发条件的case1和case2。LCID域的预留LCID值不仅可以将第一MAC CE与现有BSR MAC CE区别开来，还可以同时区别指示第2种触发条件的case1和case2。
例如，对于一个BSR MAC CE对应的MAC subheader来说，当其中的LCID域取值为预留值100010时，表示该BSRMACCE用于RRC连接释放请求，且表示终端在发送最后一个上行数据包之后需要再接收一个下行数据包；当其中的LCID域取值为预留值100011时，表示该BSR MAC CE用于RRC连接释放请求，且表示终端在发送最后一个上行数据包之后不需要接收下行数据包。此时，第三预留LCID值为100011，第四预留LCID值为100011。示例仅用于解释本申请，实际应用中，第三预留LCID值、第四预留LCID值可以为图10所示的表格中的预留LCID值中两个预留值。
在网络设备侧，网络设备可以根据第三指示信息确定在接收到第一MAC CE后，是否还需要等待一个下行数据包再下发RRC连接释放消息。这样，对于第2种触发条件的的case2，网络设备可以在收到第一MAC CE后等待一段时间，避免RRC连接被立刻释放而导致下行数据无法传输。
(3)用于RRC连接释放请求的现有的BSR MAC CE(即第一MAC CE)可以既指示终端偏好转移到的RRC状态，也指示终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
1.方式一，第一MAC CE可以同时携带第一指示比特和第二指示比特，第一指示比特和第二指示比特为MAC subheader中的两个不同的指示比特。
具体的，如图23所示，第一MAC CE对应的MAC subheader可以如图23示例性所示。其中，比特I即第一指示比特，用于指示终端偏好转移到的RRC状态；比特D即第二指示比特，用于区别指示第2种触发条件的case1和case2；LCID域的取值为图9示出的表格中的预留LCID值(如100010–110100中的100011)中的一个值或一个值范围。比特I、比特D可以是MAC subheader中的预留比特R。
2.方式二，第一MAC CE可以携带第四指示信息，第四指示信息指示终端偏好转移到的RRC状态，以及，终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
具体的，第四指示信息为MAC subheader中的LCID域，可指示如下四种情况：
当LCID域的取值为第五预留LCID值(如100010–110100中的100010)时，表示终端偏好转移到 的RRC状态为RRC空闲态且终端在发送最后一个上行数据之后需要再接收一个下行数据；
当LCID域的取值为第六预留LCID值(如100010–110100中的100011)时，表示终端偏好转移到的RRC状态为RRC非激活态且终端在发送最后一个上行数据之后需要再接收一个下行数据；
当LCID域的取值为第七预留LCID值(如100010–110100中的100100)时，表示终端偏好转移到的RRC状态为RRC空闲态且终端在发送最后一个上行数据之后不需要接收下行数据；
当LCID域的取值为第八预留LCID值(如100010–110100中的100101)时，表示终端偏好转移到的RRC状态为RRC非激活态且终端在发送最后一个上行数据之后不需要接收下行数据。
也即是说，LCID域的预留LCID值不仅可以将第一MAC CE与现有的其他功能的BSR MAC CE区别开来，还可以指示上述四种情况中的任意一种。
(四)实施例四
本实施例中，RRC连接释放请求的触发条件为前述第2种触发条件，即：终端当前传输的上行数据是当前业务的最后一个上行数据包。
具体的，第2种触发条件被满足可能会有两种情况：
情况一(case 1)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后不会再接收下行数据包。
情况二(case 2)，终端当前传输的上行数据是当前业务的最后一个上行数据包，且终端在发送最后一个上行数据包之后需要再接收一个下行数据包。
也即是说，在终端传输最后一个上行数据包后可能存在两种情况：终端不再接收下行数据包，或终端只再接收一个下行数据包。
例如，在终端备份数据到云端的场景中，假设该终端需要备份1G的照片到云端，且备份期间该终端没有其他APP进行数据上传活动，那么终端便可以把这1G照片的数据中最后1个数据包确定为当前业务的最后一个上行数据包。进一步的，终端可以根据当前业务使用的传输层通信协议来判断是否有针对最后一个上行数据包的下行响应/反馈信息(如ACK/NACK)。如果当前业务使用的传输层通信协议为传输控制协议(transmission control protocol，TCP)，那么在最后一个上行数据包后，终端还需要接收针对该最后一个上行数据包的下行响应/反馈，即情况二(case 2)；如果当前业务使用的传输层通信协议为用户数据报协议(user datagram protocol，UDP)，那么在最后一个上行数据包后，终端不需要接收针对该最后一个上行数据包的下行响应/反馈，即情况一(case 1)。
本实施例中，承载RRC连接释放请求的第一MAC CE为新定义的MAC CE。
图24示出了实施例四提供的RRC连接释放方法的具体流程。下面展开：
S501-S502，终端确定当前传输的上行数据是当前业务的最后一个上行数据包。一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，终端便可以触发RRC连接释放请求。
S503，在触发RRC连接释放请求之后，终端可以判断是否有足够的上行资源来承载用于RRC连接释放请求的MAC CE(即第一MAC CE)。如果没有足够的上行资源，则可以先执行S504-S505，再执行S506；如果有足够的上行资源，则可以直接执行S506。
S504-S505，终端向网络设备发送调度请求SR，以请求获得上行资源承载第一MAC CE。相应的，在收到终端发送的SR后，网络设备为终端调度上行资源，并向终端发送上行授权(UL grant)，UL grant指示网络设备为终端调度的上行资源有哪些。
S506，终端可以利用现有的BSR MAC CE生成用于RRC连接释放请求的MAC CE(即第一MAC  CE)。
S507，终端向网络设备发送用于RRC连接释放请求的MAC CE，即第一MAC CE。执行S407的前提是终端具有足够的上行资源承载第一MAC CE。
S508，相应的，网络设备接收终端发送的用于RRC连接释放请求的MAC CE。网络设备向终端发送RRC连接释放消息。
S509，相应的，终端接收到网络设备发送的RRC连接释放消息。终端根据该RRC连接释放消息释放RRC连接，从RRC_Connected状态转换为RRC_IDLE或RRC_Inactive状态。
不限于图24所示，S506也可以在S503之前被执行，即一旦终端触发RRC连接释放请求，终端便可以先生成第一MAC CE，然后再在发送第一MAC CE之前判断上行资源是否足够，如果上行资源不够，终端向网络设备发送SR。
下面详细说明关键技术点(一)至(三)在实施例三中的具体实现。
1.RRC连接释放请求的触发条件
实施例四中的RRC连接释放请求的触发条件的具体实现与实施例三中的RRC连接释放请求的触发条件的具体实现相同，可参考实施例三，这里不再赘述。
2.第一MAC CE的具体实现
同于实施例二中的第一MAC CE的实现，具体可参考实施例二的相应内容，这里不再赘述。
3.第一MAC CE的传输
同于实施例一中的第一MAC CE的传输，具体可参考实施例一的相应内容，这里不再赘述。
在实施例四中，在确定终端当前传输的上行数据是当前业务的最后一个上行数据包，且最后一个上行数据包之后不会再有下行数据包或仅有一个下行数据包时，终端便触发RRC连接释放请求，利用新定义的MAC CE来请求网络设备发起RRC连接释放过程。实施例四不仅可实现让终端尽快准确的转换为RRC_IDLE或RRC_Inactive状态，节约终端功耗，还可以利用新定义的MAC CE承载RRC连接释放请求，节约信令开销。
实施例四的相关扩展
(1)用于RRC连接释放请求的新定义的BSR MAC CE(即第一MAC CE)可以携带指示信息，以指示终端偏好转移到的RRC状态。终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。该指示信息可以称为第二指示信息。第二指示信息的具体实现可参考实施例二的相关扩展，这里不再赘述。
(2)用于RRC连接释放请求的新定义的BSR MAC CE(即第一MAC CE)可以携带指示信息，以指示终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包。该指示信息可以称为第三指示信息。也即是说，第三指示信息可以区别指示第2种触发条件的case1和case2。
具体的，第三指示信息可包括但不限于以下两种实现方式：
1.方式一，第三指示信息可以为MAC subheader中的第二指示比特。
当第二指示比特的取值为第五值(如1)时，表示终端在发送最后一个上行数据之后需要再接收一个下行数据；当第二指示比特的取值为第六值(如0)时，表示终端在发送最后一个上行数据之后不需要接收下行数据。
也即是说，可利用新定义的MAC CE对应的MAC subheader中的某个比特(如预留比特R作为指 示比特)指示终端偏好转移到的RRC状态。
具体的，如图25所示，新定义的MAC CE对应的MAC subheader可包括：预留比特R，比特D，以及LCID域。其中，比特D即第二指示比特，用于区别指示第2种触发条件的case1和case2，比特D可以是MAC subheader中的预留比特R；LCID域的取值为图10示出的表格中的预留LCID值中的一个值或一个值范围。
可选的，当第二指示比特的取值为1时，可指示第2种触发条件的case1；当第二指示比特的取值为0时，可指示第2种触发条件的case1。此时，第五值为1，第六值为0。反之也可以，当第二指示比特的取值为0时，可指示第2种触发条件的case1；当第二指示比特的取值为1时，可指示第2种触发条件的case1。此时，第五值为0，第六值为1。可选的，第二指示比特的取值可以由高层协议层(如应用层或RRC层)或MAC层确定。
2.方式二，第三指示信息可以为MAC subheader中的LCID域。
当LCID域的取值为第三预留LCID值时，表示终端在发送最后一个上行数据包之后需要再接收一个下行数据包；当LCID域的取值为第四预留LCID值时，表示终端在发送最后一个上行数据包之后不需要接收下行数据包。
也即是说，可利用新定义的MAC CE对应的MAC subheader中的LCID域的预留LCID值区别指示第2种触发条件的case1和case2。
(3)用于RRC连接释放请求的新定义的BSR MAC CE(即第一MAC CE)可以既指示终端偏好转移到的RRC状态，也指示终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
1.方式一，第一MAC CE可以同时携带第一指示比特和第二指示比特，第一指示比特和第二指示比特为MAC subheader中的两个不同的指示比特。
具体的，可参考实施例三的相关扩展中的相应内容，这里不再赘述。
2.方式二，第一MAC CE可以携带第四指示信息，第四指示信息指示终端偏好转移到的RRC状态，以及，终端在发送最后一个上行数据之后需要再接收一个下行数据包或不需要再接收下行数据包。
具体的，第四指示信息为MAC subheader中的LCID域，具体可参考实施例三的相关扩展中的相应内容，这里不再赘述。
结合实施例一至实施例四中的任一个实施例，在一些可选实现方式中，为了避免在终端已发送的第一MAC CE还处于等待网络设备处理的状态(即pendin状态)下，该终端又重复发送第一MAC CE，终端可以在如下条件中的任意一项被满足时，取消发送承载RRC连接释放请求的第一MAC CE：该终端的复用和组合过程生成了第一MAC CE，或，终端已经发送了包含第一MAC CE的MAC PDU。这里，终端的复用和组合过程是指终端将一个或者多个LCH的数据，即MAC SDU，和/或一个或者多个MAC CE复用到一个MAC PDU中，并按照MAC协议中定义的MAC PDU的格式组装生成一个MAC PDU的过程。
参考图26，图26示出了本申请的一些实施例提供的终端300。如图26所示，终端300可包括：输入输出模块(包括音频输入输出模块318、按键输入模块316以及显示器320等)、用户接口302、一个或多个终端处理器304、发射器306、接收器308、耦合器310、天线314以及存储器312。这些部件可通过总线或者其他方式连接，图26以通过总线连接为例。其中：
通信接口301可用于终端300与其他通信设备，例如基站，进行通信。具体的，所述基站可以是图27所示的网络设备400。通信接口301是指终端处理器304与收发系统(由发射器306和接收器308构成)之间的接口，例如LTE中的X1接口。具体实现中，通信接口301可包括：全球移动通信系统(Global System for Mobile Communication，GSM)(2G)通信接口、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)(3G)通信接口，以及长期演进(Long Term Evolution，LTE)(4G)通信接口等等中的一种或几种，也可以是4.5G、5G或者未来新空口的通信接口。不限于无线通信接口，终端300还可以配置有有线的通信接口301，例如局域接入网(Local Access Network，LAN)接口。
天线314可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器310用于将天线314接收到的移动通信信号分成多路，分配给多个的接收器308。
发射器306可用于对终端处理器304输出的信号进行发射处理，例如将该信号调制在授权频段的信号，或者调制在非授权频段的信号。换句话说，发射器306可以支持终端300在一个或多个非授权频谱上发射信号，或者可以支持终端300在一个或多个授权频谱上发射信号。
接收器308可用于对天线314接收的移动通信信号进行接收处理。例如，接收器308可以解调已被调制在非授权频段上的接收信号，也可以解调调制在授权频段上的接收信号。换句话说，接收器308可以支持终端300接收调制在非授权频谱上的信号，或者可以支持终端300接收调制在授权频谱上的信号。
在本申请的一些实施例中，发射器306和接收器308可看作一个无线调制解调器。在终端300中，发射器306和接收器308的数量均可以是一个或者多个。
除了图26所示的发射器306和接收器308，终端300还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(Wireless Fidelity，Wi-Fi)模块等。不限于上述表述的无线通信信号，终端300还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端300还可以配置有有线网络接口(如LAN接口)来支持有线通信。
所述输入输出模块可用于实现终端300和用户/外部环境之间的交互，可主要包括音频输入输出模块318、按键输入模块316以及显示器320等。具体实现中，所述输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，所述输入输出模块均通过用户接口302与终端处理器304进行通信。
存储器312与终端处理器304耦合，用于存储各种软件程序和/或多组指令。具体实现中，存储器312可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器312可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作系统。存储器312还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器312还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请的一些实施例中，存储器312可用于存储本申请的一个或多个实施例提供的RRC连接释放方法在终端300侧的实现程序。关于本申请的一个或多个实施例提供的RRC连接释放方法的实现，请参考后续实施例。
终端处理器304可用于读取和执行计算机可读指令。具体的，终端处理器304可用于调用存储于存储器312中的程序，例如本申请的一个或多个实施例提供的RRC连接释放方法在终端300侧的实现程序，并执行该程序包含的指令。
终端处理器304可以为调制解调器(Modem)处理器，是实现3GPP、ETSI等无线通信标准中主要 功能的模块。Modem可以作为单独的芯片，也可以与其他芯片或电路在一起形成系统级芯片或集成电路。这些芯片或集成电路可应用于所有实现无线通信功能的设备，包括：手机、电脑、笔记本、平板、路由器、可穿戴设备、汽车、家电设备等。需要说明的是，在不同的实施方式中，终端处理器304处理器可以作为单独的芯片，与片外存储器耦合，即芯片内不包含存储器；或者终端处理器304处理器与片内存储器耦合并集成于芯片中，即芯片内包含存储器。
可以理解的，终端300可以是图1示出的无线通信系统100中的终端103，可实施为移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图26所示的终端300仅仅是本申请的一种实现方式，实际应用中，终端300还可以包括更多或更少的部件，这里不作限制。
参考图27，图27示出了本申请的一些实施例提供的网络设备400。如图27所示，网络设备400可包括：通信接口403、一个或多个网络设备处理器401、发射器407、接收器409、耦合器411、天线413和存储器405。这些部件可通过总线或者其他方式连接，图27以通过总线连接为例。其中：
通信接口403可用于网络设备400与其他通信设备，例如终端设备或其他基站，进行通信。具体的，所述终端设备可以是图26所示的终端300。通信接口301是指网络设备处理器401与收发系统(由发射器407和接收器409构成)之间的接口，例如LTE中的S1接口。具体实现中，通信接口403可包括：全球移动通信系统(GSM)(2G)通信接口、宽带码分多址(WCDMA)(3G)通信接口，以及长期演进(LTE)(4G)通信接口等等中的一种或几种，也可以是4.5G、5G或者未来新空口的通信接口。不限于无线通信接口，网络设备400还可以配置有有线的通信接口403来支持有线通信，例如一个网络设备400与其他网络设备400之间的回程链接可以是有线通信连接。
天线413可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器411可用于将移动通信号分成多路，分配给多个的接收器409。
发射器407可用于对网络设备处理器401输出的信号进行发射处理，例如将该信号调制在授权频段的信号，或者调制在非授权频段的信号。换句话说，发射器407可以支持网络设备400在一个或多个非授权频谱上发射信号，或者还可以支持网络设备400在一个或多个授权频谱上发射信号。
接收器409可用于对天线413接收的移动通信信号进行接收处理。例如，接收器409可以解调已被调制在非授权频段上的接收信号，也可以解调调制在授权频段上的接收信号。换句话说，接收器409可以支持网络设备400接收调制在非授权频谱上的信号，或者还可以支持网络设备400接收调制在授权频谱上的信号。
在本申请的一些实施例中，发射器407和接收器409可看作一个无线调制解调器。在网络设备400中，发射器407和接收器409的数量均可以是一个或者多个。
存储器405与网络设备处理器401耦合，用于存储各种软件程序和/或多组指令。具体实现中，存储器405可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器405可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器405还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
网络设备处理器401可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内用户设备的过区切换进行控制等。具体实现中，网络设备处理器401可包括：管理/通信模块(Administration Module/Communication Module，AM/CM)(用于话路交换和信息交换的中心)、基本模 块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer，TCSM)(用于完成复用解复用及码变换功能)等等。
本申请中，网络设备处理器401可用于读取和执行计算机可读指令。具体的，网络设备处理器401可用于调用存储于存储器405中的程序，例如本申请的一个或多个实施例提供的RRC连接释放方法在网络设备400侧的实现程序，并执行该程序包含的指令。
网络设备处理器401可以为调制解调器(Modem)处理器，是实现3GPP、ETSI等无线通信标准中主要功能的模块。Modem可以作为单独的芯片，也可以与其他芯片或电路在一起形成系统级芯片或集成电路。这些芯片或集成电路可应用于所有实现无线通信功能的网络侧设备，例如，在LTE网络中，称为演进的节点B(evolved NodeB，eNB或eNodeB)，在第三代(the 3rd Generation，3G)网络中，称为节点B(Node B)等，在5G网络中，称为5G基站(NR NodeB，gNB)。需要说明的是，在不同的实施方式中，网络设备处理器401可以作为单独的芯片，与片外存储器耦合，即芯片内不包含存储器；或者网络设备处理器401处理器与片内存储器耦合并集成于芯片中，即芯片内包含存储器。
可以理解的，网络设备400可以是图1示出的无线通信系统100中的网络设备101，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB等等。网络设备400可以实施为几种不同类型的基站，例如宏基站、微基站等。网络设备400可以应用不同的无线技术，例如小区无线接入技术，或者WLAN无线接入技术。
需要说明的，图27所示的网络设备400仅仅是本申请的一种实现方式，实际应用中，网络设备400还可以包括更多或更少的部件，这里不作限制。
参见图28，图28是本申请的一个实施例提供的无线通信系统10，以及无线通信系统10中的网络设备500、终端600。网络设备500可以是前述方法实施例中的网络设备，终端600可以是前述方法实施例中的终端。
如图28所示，终端600可包括：处理单元601和通信单元603。其中：
处理单元601可用于触发RRC连接释放请求；
通信单元603可用于向网络设备500发送所述第一媒体接入控制控制实体MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求网络设备500发起RRC连接释放过程。
可选的，通信单元501还可用于接收所述网络设备发送的RRC连接释放消息。处理单元601还可用于根据所述RRC连接释放消息，释放RRC连接，从RRC连接态转换为RRC空闲态或RRC非激活态。
可选的，处理单元601还可用于在如下条件中的任意一项被满足时，取消所述RRC连接释放请求：所述终端的复用和组合过程生成了所述第一MAC CE，所述终端发送了包含所述第一MAC CE的MAC PDU。
如图28所示，网络设备500可包括：通信单元501和处理单元503。其中：
通信单元501，可用于接收终端600发送的第一媒体接入控制控制实体MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求所述网络设备发起RRC连接释放过程。
处理单元503，可用于解析通信单元501接收到的第一MAC CE。
可选的，通信单元501还可用于根据所述第一MAC CE向所述终端发送RRC连接释放消息。
可以看出，由终端600而非网络设备500来确定终端600业务传输结束与否。在终端600确定业务传输结束后，终端600向网络设备500发送用于RRC连接释放请求的MAC CE。网络设备500在收到用于RRC连接释放请求的MAC CE后，便可以决定向终端600发送RRC连接释放消息/RRC释放消息，以发起终端600的RRC连接释放过程。这样，便可以让处于RRC连接态下的终端600在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或者RRC非激活态，有利于降低终端600的功耗。
本申请中，RRC连接释放请求的触发条件可包括：
第1种触发条件：终端在不久的将来没有业务需要传输。一旦终端确定当前时刻之后的一段时间内没有业务需要传输，终端便触发RRC连接释放请求。本申请中，可以将这一段时间称为第一时间，第一时间可以为20-30s，或其他值。
第2种触发条件：终端当前传输的上行数据是当前业务的最后一个上行数据包。一旦终端确定当前传输的上行数据是当前业务的最后一个上行数据包，终端便触发RRC连接释放请求。
关于上述两种触发条件的具体内容，可参考前述实施例，这里不再赘述。
本申请中，第一MAC CE的具体实现方式可包括：
(1)第一MAC CE可以重用现有协议中定义的BSR MAC CE来实现。
方式一，对于任意BSR格式的BSR MAC CE来说，第一指示信息可以包括：BSR MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，BSR MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用现有BSR MAC CE对应的MAC subheader中的预留LCID值或预留比特R来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
可选的，当第一MAC CE具体为短BSR格式或短截断BSR格式的BSR MAC CE时，该BSR MAC CE中的buffer size域的取值为0；该BSR MAC CE中的LCG ID域的取值可以为所终端的任意一个LCG的ID，或者为包含具有最高优先级的逻辑信道的LCG的ID，或者为0。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节，该bitmap字节中的每一个比特的取值均为0，表示各个比特各自对应的逻辑信道组中没有数据缓存。可以看出，由于省去了现有BSR MAC CE中的buffer size域，第一MAC CE可以节约比特开销。
方式二，对于长BSR格式或长截断BSR格式的BSR MAC CE来说，第一指示信息还可包括：取值为buffer size预留值(即255)的buffer size域。也即是说，还可以利用现有长BSR格式或长截断BSR格式的BSR MAC CE中的预留buffer size值来表示该BSR MAC CE是一个特殊的MAC CE，用于RRC连接释放请求，即MAC CE for RRC Connection Release Request。
可选的，当第一MAC CE具体为长BSR格式或长截断BSR格式的BSR MAC CE时，该BSR MAC CE中可以仅包含一个bitmap字节和一个buffer size域。
(2)第一MAC CE可以为新定义的MAC CE。
本申请中，该新定义的MAC CE的比特长度可以固定为0个比特；第一MACCE中携带的第一指示信息可包括：该新定义的MAC CE对应的MAC subheader中取值为预留LCID值(如100010–110100中一个值或一个值范围)的LCID域，和/或，该新定义的MAC CE对应的MAC subheader中取值为第一值(如1)的预留比特R。也即是说，可以利用MAC subheader中的预留LCID值或预留比特R来指示第一MAC CE用于RRC连接释放请求。
可以看出，利用新定义的MAC CE来实现第一MAC CE，由于MAC CE部分为0bits，仅有MAC subheader部分，可以节约比特开销。
(3)第一MAC CE可以携带第二指示信息，以指示终端偏好转移到的RRC状态。
终端偏好转移到的RRC状态可包括RRC空闲态或RRC非激活态。
(4)第一MAC CE可以携带第三示信息，以指示终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包。
关于终端在发送最后一个上行数据包之后需要再接收一个下行数据包还是不需要再接收下行数据包，可具体参考前述实施例中关于第2种触发条件的内容，这里不再赘述。
关于第一MAC CE的信令实现的详细描述，可参考前述实施例，这里不再赘述。
本申请中，第一MAC CE在进行逻辑信道优先级处理时的优先级可以呈现如下考虑：
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了padding BSR MAC CE外的BSR MAC CE、PHR MAC CE、除来自UL-CCCH的数据外的来自任意逻辑信道的数据。这样，可以避免第一MAC CE抢占承载数据的资源，确保数据正常传输。
可选的，第一MAC CE在进行逻辑信道优先级处理时的优先级可以低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了用于padding的BSR MAC CE外的BSR MAC CE。
可以理解的，网络设备500和终端600各自包括的各个功能单元的具体实现可参考前述方法实施例，这里不再赘述。
另外，本发明实施例还提供了一种无线通信系统，所述无线通信系统可以是图1所示的无线通信系统100，也可以是图28所示的无线通信系统10，可包括：网络设备和终端。其中，该终端可以是前述实施例中的终端，该网络设备可以是前述实施例中的网络设备。具体的，该终端可以是图26所示的终端300，该网络设备可以是图27所示的网络设备400。该终端也可以是图28实施例中的终端600，该网络设备也可以是图28实施例中的网络设备500。关于所述网络和所述终端的具体实现可参考前述实施例，这里不再赘述。
以图26所示终端为例，终端处理器304用于调用存储于所述存储器312中的指令来控制发射器306在进行发送以及控制接收器308进行接收。发射器306用于支持终端执行对数据和/或信令进行发射的过程。接收器308用于支持终端执行对数据和/或信令进行接收的过程。存储器312用于存储终端的程序代码和数据。
本申请中，终端处理器304可用于触发RRC连接释放请求
本申请中，发射器306可用于发射第一MAC CE。
本申请中，第一MAC CE用于RRC连接释放请求。这样，网络设备在收到第一MAC CE后，便可以决定向终端发送RRC连接释放消息/RRC释放消息，以发起终端的RRC连接释放过程，便可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或者RRC非激活态，有利于降低终端的功耗。关于第一MAC CE的具体实现，可参考前述实施例，这里不再赘述。
关于终端中各部件的具体实现，可参考图前述方法实施例，这里不再赘述。
以图27所示网络设备为例，网络设备处理器405用于控制发射器407在进行发送以及控制接收器409在进行接收。发射器407用于支持网络设备执行对数据和/或信令进行发射的过程。接收器409用于 支持网络设备执行对数据和/或信令进行接收的过程。存储器405用于存储网络设备的程序代码和数据。
本申请中，接收器409可主要用于接收终端发送的第一MAC CE。发射器407可主要用于根据第一MAC CE发送RRC连接释放消息/RRC释放消息。这样便可以发起终端的RRC连接释放过程，便可以让处于RRC连接态下的终端在结束业务传输后尽快转入RRC空闲态或者RRC非激活态，而不是在计数器超时后等待一段时间再转入RRC空闲态或者RRC非激活态，有利于降低终端的功耗。关于第一MAC CE的具体实现，可参考前述实施例，这里不再赘述。
关于网络设备中各部件的具体实现，可参考图前述方法实施例，这里不再赘述。
参见图29，图29示出了本申请提供的一种装置的结构示意图。如图29所示，装置50可包括：处理器501，以及耦合于处理器501的一个或多个接口502。其中：
处理器501可用于读取和执行计算机可读指令。具体实现中，处理器501可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器501的硬件架构可以是专用集成电路(Application Specific Integrated Circuits,ASIC)架构、MIPS架构、ARM架构或者NP架构等等。处理器501可以是单核的，也可以是多核的。
接口502可用于输入待处理的数据至处理器501，并且可以向外输出处理器501的处理结果。具体实现中，接口502可以是通用输入输出(General Purpose Input Output，GPIO)接口，可以和多个外围设备(如射频模块等等)连接。接口502还可以包括多个独立的接口，例如以太网接口、移动通信接口(如X1接口)等，分别负责不同外围设备和处理器501之间的通信。
本申请中，处理器501可用于从存储器中调用本申请的一个或多个实施例提供的RRC连接释放方法在网络设备侧或终端侧的实现程序，并执行该程序包含的指令。接口502可用于输出处理器501的执行结果。本申请中，接口503可具体用于输出处理器501的处理结果。关于本申请的一个或多个实施例提供的RRC连接释放方法可参考前述各个实施例，这里不再赘述。
具体的，当装置50实现为本申请中的终端时，处理器501可用于根据RRC连接释放请求的前述触发条件1或前述触发条件2触发RRC连接请求，并生成第一MAC CE。接口503可用于输出处理器501生成的第一MAC CE。具体的，接口503可以输出第一MAC CE到发射器，发射器可用于发射第一MAC CE。
具体的，当装置50实现为本申请的中的网络设备时，接口503可用于将接收器接收到的第一MAC CE输入到处理器501，处理器501可用于解析第一MAC CE。处理器501还可用于根据第一MAC CE生成RRC连接释放消息。接口503还可用于输出处理器501生成的RRC连接释放消息。具体的，接口503可以输出RRC连接释放消息到发射器，发射器可用于发射RRC连接释放消息。
关于第一MAC CE的内容和格式可以参考前述实施例，这里不再赘述。
需要说明的，处理器501、接口502各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知 的任何其他形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于收发机或中继设备中。当然，处理器和存储介质也可以作为分立组件存在于无线接入网设备或终端设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (25)

  1. 一种释放无线资源控制RRC连接的方法，其特征在于，包括：
    终端触发RRC连接释放请求；
    终端向网络设备发送所述第一媒体接入控制控制实体MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求所述网络设备发起RRC连接释放过程。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述终端接收所述网络设备发送的RRC连接释放消息；
    所述终端根据所述RRC连接释放消息，释放RRC连接，从RRC连接态转换为RRC空闲态或RRC非激活态。
  3. 如权利要求1或2所述的方法，其特征在于，还包括：所述终端在如下条件中的任意一项被满足时，取消所述RRC连接释放请求：所述终端的复用和组合过程生成了所述第一MAC CE，所述终端发送了包含所述第一MAC CE的MAC PDU。
  4. 如权利要求1-3中任一项所述的方法，其特征在于，所述终端触发所述RRC连接释放请求，具体包括：
    如果所述终端确定在当前之后的第一时间段内不会有业务需要传输，则所述终端触发所述RRC连接释放请求。
  5. 如权利要求1-3中任一项所述的方法，其特征在于，所述终端触发所述RRC连接释放请求，具体包括：
    如果所述终端确定当前传输的上行数据包是当前业务的最后一个上行数据包且所述终端在发送所述最后一个上行数据包之后不会再接收下行数据包，或，所述终端确定当前传输的上行数据是当前业务的最后一个上行数据且所述终端在发送所述最后一个上行数据之后需要再接收少于第一数据量的下行数据包，则触发所述RRC连接释放请求。
  6. 如权利要求1-5中任一项所述的方法，其特征在于，所述第一MAC CE中还包括指示所述终端偏好转移到的RRC状态的第二指示信息，所述终端偏好转移到的RRC状态包括RRC空闲态或RRC非激活态。
  7. 一种释放无线资源控制RRC连接的方法，其特征在于，包括：
    网络设备接收终端发送的第一媒体接入控制控制实体MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求所述网络设备发起RRC连接释放过程。
  8. 如权利要求7所述的方法，其特征在于，还包括：所述网络设备根据所述第一MAC CE向所述终端发送RRC连接释放消息。
  9. 如权利要求7或8所述的方法，其特征在于，所述第一MAC CE中还包括指示所述终端偏好转移到的RRC状态的第二指示信息，所述终端偏好转移到的RRC状态包括RRC空闲态或RRC非激活态；如果所述第二指示信息指示所述终端偏好转移到的RRC状态为RRC非激活态，则所述RRC连接释放消息中包括转入RRC非激活态的指示信息。
  10. 如权利要求1-9中任一项所述的方法，其特征在于，所述第一MAC CE为BSR MAC CE，所述第一指示信息包括：所述BSR MAC CE对应的MAC子头部subheader中取值为预留LCID值的LCID域，和/或，所述BSR MAC CE对应的MAC subheader中取值为第一值的预留比特R。
  11. 如权利要求1-9中任一项所述的方法，其特征在于，所述第一MAC CE为长BSR格式或长截断BSR格式的BSR MAC CE，所述第一指示信息包括：取值为buffer size预留值的buffer size域。
  12. 如权利要求1-9中任一项所述的方法，其特征在于，所述第一MAC CE的比特长度固定为0个比特；所述第一指示信息包括：所述第一MAC CE对应的MAC subheader中取值为预留值的LCID域，和/或，所述第一MAC CE对应的MAC subheader中取值为第二值的预留比特R。
  13. 如权利要求1-12中任一项所述的方法，其特征在于，所述第一MAC CE中还包括第三指示信息，所述第三指示信息指示所述终端在发送最后一个上行数据包之后需要再接收少于第一数据量的下行数据包或不需要再接收下行数据包。
  14. 如权利要求1-13中任一项所述的方法，其特征在于，所述第一MAC CE在进行逻辑信道优先级处理时的优先级低于以下各项的优先级：小区无线网络临时标识C-RNTI MAC CE、配置授权确认Configured Grant Confirmation MAC CE、除了填充BSR MAC CE外的BSR MAC CE、功率余量报告PHR MAC CE、除来自上行公共控制信道UL-CCCH的数据外的来自任意逻辑信道的数据。
  15. 如权利要求1-14中任一项所述的方法，其特征在于，所述第一MAC CE在进行逻辑信道优先级处理时的优先级低于以下各项的优先级：C-RNTI MAC CE、Configured Grant Confirmation MAC CE、除了用于padding的BSR MAC CE外的BSR MAC CE。
  16. 一种终端，其特征在于，包括：收发器和接收器，存储器以及耦合于所述存储器的处理器，所述存储器用于存储可由所述处理器执行的指令，所述处理器用于调用所述存储器中的所述指令，执行权利要求1-6、10-15中任一项所述的方法。
  17. 一种网络设备，其特征在于，包括：发射器和接收器，存储器以及耦合于所述存储器的处理器，所述存储器用于存储可由所述处理器执行的指令，所述处理器用于调用所述存储器中的所述指令，执行权利要求7-9、10-15中任一项所述的方法。
  18. 一种装置，其特征在于，包括：处理器，以及耦合于所述处理器的一个或多个接口；其中：
    所述处理器用于触发RRC连接释放请求，生成第一媒体接入控制控制实体MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求所述网络设备发起 RRC连接释放过程；
    所述接口用于输出所述处理器生成的所述第一MAC CE。
  19. 如权利要求18所述的装置，其特征在于，所述处理器还用于执行如权利要求2-6、10-15中任一项所述方法。
  20. 一种装置，其特征在于，包括：处理器，以及耦合于所述处理器的一个或多个接口；其中：
    所述接口用于输入第一媒体接入控制控制实体MAC CE到所述处理器；
    所述处理器用于解析所述第一MAC CE，所述第一MAC CE包括第一指示信息，所述第一指示信息指示所述第一MAC CE用于请求所述网络设备发起RRC连接释放过程。
  21. 如权利要求20所述的装置，其特征在于，所述处理器还用于执行如权利要求7-15中任一项所述方法。
  22. 一种通信系统，其特征在于，包括：终端和网络设备，其中：
    所述终端为权利要求16所述的终端，所述网络设备为权利要求17所述的网络设备。
  23. 一种计算机可读存储介质，其特征在于，所述可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行1-15中任一项所述的方法。
  24. 一种包含指令的计算机程序产品，其特征在于当其在计算机上运行时，使得计算机执行1-15中任一项所述的方法。
  25. 一种芯片系统，其特征在于，包括收发器，存储器以及耦合于所述存储器的处理器，所述存储器用于存储可由所述处理器执行的指令，所述处理器用于调用所述存储器中的所述指令，执行权利要求1-15中任一项所述的方法。
PCT/CN2019/103889 2018-08-31 2019-08-31 Rrc连接释放方法、相关设备及系统 WO2020043211A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811021991.6 2018-08-31
CN201811021991.6A CN110876183B (zh) 2018-08-31 2018-08-31 Rrc连接释放方法、相关设备及系统

Publications (1)

Publication Number Publication Date
WO2020043211A1 true WO2020043211A1 (zh) 2020-03-05

Family

ID=69643387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103889 WO2020043211A1 (zh) 2018-08-31 2019-08-31 Rrc连接释放方法、相关设备及系统

Country Status (2)

Country Link
CN (1) CN110876183B (zh)
WO (1) WO2020043211A1 (zh)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111263471A (zh) * 2020-04-10 2020-06-09 龙尚科技（上海）有限公司 Rrc连接释放方法、装置、无线模块、终端、系统和介质
CN111727614A (zh) * 2020-04-30 2020-09-29 北京小米移动软件有限公司 终端状态切换处理、控制方法及装置、通信设备及介质
WO2020263691A1 (en) * 2019-06-28 2020-12-30 Qualcomm Incorporated Ue assisted fast transition between rrc states
CN112312448A (zh) * 2020-11-27 2021-02-02 中国联合网络通信集团有限公司 一种rrc连接数的评估方法和装置
CN112911732A (zh) * 2021-01-13 2021-06-04 恒安嘉新（北京）科技股份公司 一种消息关联方法、装置、电子设备及存储介质
CN113784436A (zh) * 2020-06-09 2021-12-10 大唐移动通信设备有限公司 指示方法及设备
CN113795046A (zh) * 2021-09-14 2021-12-14 北京小米移动软件有限公司 通信方法、通信装置、通信设备及存储介质
CN114097259A (zh) * 2020-06-24 2022-02-25 北京小米移动软件有限公司 一种通信处理方法、通信处理装置及存储介质
CN114173431A (zh) * 2020-09-11 2022-03-11 华为技术有限公司 一种rrc连接释放的方法及装置
CN114258113A (zh) * 2020-09-21 2022-03-29 大唐移动通信设备有限公司 数据传输控制方法、终端、网络设备、装置及存储介质
WO2023035116A1 (zh) * 2021-09-07 2023-03-16 北京小米移动软件有限公司 一种无线资源控制rrc状态切换方法、装置、用户设备、基站及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112492695B (zh) * 2019-09-11 2022-11-11 维沃移动通信有限公司 sidelink BSR传输方法和设备
US20230141487A1 (en) * 2020-04-14 2023-05-11 FG Innovation Company Limited Wireless communication method and user equipment for performing transmission in rrc_inactive state
CN116530191A (zh) * 2020-12-25 2023-08-01 华为技术有限公司 一种数据传输方法及装置
CN116830779A (zh) * 2021-02-26 2023-09-29 Oppo广东移动通信有限公司 资源处理方法、装置、设备及存储介质
CN113055989B (zh) * 2021-03-31 2022-10-25 联想(北京)有限公司 通信控制方法、装置和基站
CN113508638B (zh) * 2021-06-08 2024-02-20 北京小米移动软件有限公司 一种通信方法、装置及设备
CN113596966A (zh) * 2021-07-09 2021-11-02 Oppo广东移动通信有限公司 一种功耗控制方法、终端设备、网络设备及存储介质
WO2023039807A1 (zh) * 2021-09-16 2023-03-23 北京小米移动软件有限公司 能力上报方法及装置、存储介质
CN114449631A (zh) * 2022-01-27 2022-05-06 上海擎昆信息科技有限公司 状态切换方法及装置、终端设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102958073A (zh) * 2011-08-19 2013-03-06 普天信息技术研究院有限公司 支持并行prach传输的ue获取定时提前量的方法
CN104703171A (zh) * 2013-12-07 2015-06-10 北京信威通信技术股份有限公司 集群业务属性处理的方法、装置和系统
CN106900033A (zh) * 2015-12-17 2017-06-27 中国电信股份有限公司 载波重选方法和系统及灵活带宽终端
WO2017171475A1 (en) * 2016-04-01 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for wireless communication in wireless communication system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0608753D0 (en) * 2006-05-03 2006-06-14 Nokia Corp User equipment
CN101873667B (zh) * 2009-04-24 2013-05-15 中国移动通信集团公司 一种主载波的选择方法及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102958073A (zh) * 2011-08-19 2013-03-06 普天信息技术研究院有限公司 支持并行prach传输的ue获取定时提前量的方法
CN104703171A (zh) * 2013-12-07 2015-06-10 北京信威通信技术股份有限公司 集群业务属性处理的方法、装置和系统
CN106900033A (zh) * 2015-12-17 2017-06-27 中国电信股份有限公司 载波重选方法和系统及灵活带宽终端
WO2017171475A1 (en) * 2016-04-01 2017-10-05 Samsung Electronics Co., Ltd. Method and apparatus for wireless communication in wireless communication system

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020263691A1 (en) * 2019-06-28 2020-12-30 Qualcomm Incorporated Ue assisted fast transition between rrc states
CN111263471A (zh) * 2020-04-10 2020-06-09 龙尚科技（上海）有限公司 Rrc连接释放方法、装置、无线模块、终端、系统和介质
CN111263471B (zh) * 2020-04-10 2024-03-15 龙尚科技（上海）有限公司 Rrc连接释放方法、装置、无线模块、终端、系统和介质
CN111727614A (zh) * 2020-04-30 2020-09-29 北京小米移动软件有限公司 终端状态切换处理、控制方法及装置、通信设备及介质
CN111727614B (zh) * 2020-04-30 2023-10-03 北京小米移动软件有限公司 终端状态切换处理、控制方法及装置、通信设备及存储介质
CN113784436A (zh) * 2020-06-09 2021-12-10 大唐移动通信设备有限公司 指示方法及设备
CN114097259B (zh) * 2020-06-24 2024-03-01 北京小米移动软件有限公司 一种通信处理方法、通信处理装置及存储介质
CN114097259A (zh) * 2020-06-24 2022-02-25 北京小米移动软件有限公司 一种通信处理方法、通信处理装置及存储介质
CN114173431B (zh) * 2020-09-11 2023-12-29 华为技术有限公司 一种rrc连接释放的方法及装置
CN114173431A (zh) * 2020-09-11 2022-03-11 华为技术有限公司 一种rrc连接释放的方法及装置
CN114258113A (zh) * 2020-09-21 2022-03-29 大唐移动通信设备有限公司 数据传输控制方法、终端、网络设备、装置及存储介质
CN112312448B (zh) * 2020-11-27 2023-07-18 中国联合网络通信集团有限公司 一种rrc连接数的评估方法和装置
CN112312448A (zh) * 2020-11-27 2021-02-02 中国联合网络通信集团有限公司 一种rrc连接数的评估方法和装置
CN112911732B (zh) * 2021-01-13 2023-03-17 恒安嘉新（北京）科技股份公司 一种消息关联方法、装置、电子设备及存储介质
CN112911732A (zh) * 2021-01-13 2021-06-04 恒安嘉新（北京）科技股份公司 一种消息关联方法、装置、电子设备及存储介质
WO2023035116A1 (zh) * 2021-09-07 2023-03-16 北京小米移动软件有限公司 一种无线资源控制rrc状态切换方法、装置、用户设备、基站及存储介质
CN113795046B (zh) * 2021-09-14 2023-09-26 北京小米移动软件有限公司 通信方法、通信装置、通信设备及存储介质
CN113795046A (zh) * 2021-09-14 2021-12-14 北京小米移动软件有限公司 通信方法、通信装置、通信设备及存储介质

Also Published As

Publication number Publication date
CN110876183B (zh) 2022-01-14
CN110876183A (zh) 2020-03-10

Similar Documents

Publication Publication Date Title
WO2020043211A1 (zh) Rrc连接释放方法、相关设备及系统
US11871349B2 (en) Sleep method for terminal device and apparatus
RU2578666C2 (ru) Уменьшение избыточной сигнализации при переходах между состояниями управления радиоресурсами (rrc)
JP7241237B2 (ja) 間欠受信方法、関連する装置及びシステム
US20200221538A1 (en) Data transmission method, terminal device, and network device
US11399361B2 (en) V2X sidelink communication
WO2019062837A1 (zh) 通信方法、装置和设备
US11937324B2 (en) Data transmitting/receiving apparatuses and methods and communication system
TWI646849B (zh) 用於演進節點ｂ參數調諧的輔助資訊
US20160234713A1 (en) Information Transmission Method, Apparatus, and System
US20210251032A1 (en) Communication method, apparatus, and system
US20220078715A1 (en) Methods and apparatuses for using power-saving signal pattern, device and system
US20140204820A1 (en) Method and Arrangement in a Telecommunication System
WO2016031662A1 (ja) 基地局及び無線ｌａｎ終端装置
CN112312588A (zh) 用于传输数据的方法、终端设备和网络设备
CN116437484A (zh) 一种通信方法及装置
WO2020241429A1 (ja) 通信制御方法及びユーザ装置
CN113303002B (zh) 一种通信方法及装置
JP2024511608A (ja) サイドリンク不連続受信命令のトリガー方法、装置及びシステム
WO2023065987A1 (zh) 一种传输信息的方法及装置
WO2021189446A1 (zh) 辅助载波的睡眠指示方法、装置、终端及存储介质
WO2023272744A1 (en) Methods, devices, and medium for communication
WO2023072258A1 (en) Method and apparatus for carrier aggregation
WO2023051366A1 (zh) 一种控制传输的方法及相关装置
WO2022236681A1 (zh) 通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19853648

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19853648

Country of ref document: EP

Kind code of ref document: A1