WO2021046758A1 - 无线通信方法、装置及系统 - Google Patents

无线通信方法、装置及系统 Download PDF

Info

Publication number
WO2021046758A1
WO2021046758A1 PCT/CN2019/105386 CN2019105386W WO2021046758A1 WO 2021046758 A1 WO2021046758 A1 WO 2021046758A1 CN 2019105386 W CN2019105386 W CN 2019105386W WO 2021046758 A1 WO2021046758 A1 WO 2021046758A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
scheduling request
message
configuration information
terminal
Prior art date
Application number
PCT/CN2019/105386
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 华为技术有限公司
Priority to PCT/CN2019/105386 priority Critical patent/WO2021046758A1/zh
Priority to EP19945286.3A priority patent/EP4024950A4/en
Priority to CN201980006481.8A priority patent/CN112789892B/zh
Publication of WO2021046758A1 publication Critical patent/WO2021046758A1/zh
Priority to US17/691,636 priority patent/US20220201791A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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

  • This application relates to the field of mobile communication technology, and in particular, to a wireless communication method, device, and system.
  • radio resource control radio resource control
  • UE user equipment
  • RRC radio resource control
  • NR new radio
  • the UE When the UE enters the RRC connected state from the RRC inactive state, the UE needs to obtain the uplink shared channel resource before it can send the uplink message.
  • the UE may additionally initiate random access to the wireless network device to obtain the uplink shared channel resource of the wireless network device to send a radio link control (RLC) status report (status report).
  • RLC radio link control
  • the waiting time of the random access process is long, which wastes UE power consumption.
  • the wireless network equipment receives additional random access initiated by the UE, which may cause wireless network equipment with imperfect functions. The status of the network device is abnormal, causing the UE to fail to complete the connection recovery.
  • the embodiments of the present application provide a wireless communication method, device, and system to prevent the UE from initiating unnecessary random access during the connection recovery process, thereby reducing the time delay, and achieving the purpose of the UE quickly recovering the connection.
  • the method in the embodiments of the present application may be executed by a wireless communication device, which may be the complete computer of a computing device, or part of the device in the computing device, such as a chip related to wireless communication functions, such as a system Chips, communication chips.
  • the system chip is also called a system on a chip, or called an SoC chip.
  • the wireless communication device may be a terminal such as a smart phone, or may be a system chip or a communication chip that can be set in the terminal.
  • the communication chip may include one or more of a radio frequency processing chip and a baseband processing chip.
  • the baseband processing chip is sometimes called a modem or baseband processor.
  • the communication chip can be integrated inside the SoC chip or not integrated with the SoC chip.
  • the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip.
  • the embodiments of the present application provide the following technical solutions:
  • the first aspect of the embodiments of the present application discloses a method for radio resource control RRC connection recovery, including:
  • a radio link control status report is sent, and the radio link control status report is used to provide a positive response of the radio link control service data unit.
  • the radio link control status report is carried by a physical uplink share channel (PUSCH).
  • PUSCH physical uplink share channel
  • the uplink shared channel resource is obtained through the scheduling request configuration information to send the radio link control status report, which can avoid the terminal from initiating unnecessary random access during the connection recovery process and reduce the power consumption of the terminal. Reduce the waiting time delay, in order to achieve the purpose of quickly recovering the connection of the terminal.
  • determining the scheduling request configuration information includes: in response to the RRC restore message, restoring the RRC connection, where the restoring the RRC connection includes: deactivating the stored user equipment
  • the primary cell group is restored in the context of the state access layer; according to the primary cell group, the scheduling request configuration information is determined.
  • the user equipment inactive state access stratum context is stored. Restore the primary cell group from the stored user equipment inactive state access stratum context to determine the scheduling request configuration information carried therein.
  • the scheduling request configuration information may be used to obtain uplink shared channel resources.
  • determining the scheduling request configuration information includes: determining the scheduling request configuration information according to the RRC recovery message.
  • the first wireless network device that instructs the terminal to suspend the RRC connection and the second wireless network device that instructs the terminal to resume the RRC connection may not be a wireless network device, the stored user equipment accesses in an inactive state when the RRC connection is suspended.
  • the scheduling request configuration information in the layer context may no longer be applicable, and the RRC recovery message issued by the second wireless network device may carry the scheduling request configuration information.
  • the scheduling request configuration information is used to obtain the uplink shared channel resources
  • the specific method may be as follows: sending a scheduling request signal according to the scheduling request configuration information, the scheduling request signal is carried by the physical uplink control channel, and the scheduling request signal is used to request the uplink Shared channel resources.
  • the method further includes: sending an RRC recovery complete message through the uplink shared channel resource, where the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the restoration of the RRC connection further includes: restoring the suspended radio bearer.
  • the scheduling request configuration information includes: a scheduling request identifier and a scheduling request resource identifier.
  • the method before receiving the RRC recovery message, further includes: sending an RRC recovery request message, where the RRC recovery request message is used to request recovery of the RRC connection; and receiving an RRC recovery message, where the RRC recovery message does not include Full configuration field, the RRC recovery message is used to instruct the recovery of the RRC connection.
  • the RRC recovery request message may be an RRC recovery request (RRCResumeRequest) message, or the RRC recovery request message may also be an RRC recovery request 1 (RRCResumeRequest1) message.
  • RRCResumeRequest RRC recovery request
  • RRCResumeRequest1 RRC recovery request 1
  • the second aspect of the embodiments of the present application discloses a wireless communication device, including:
  • Receiving module processing module and sending module
  • the receiving module is used to receive a radio resource control RRC recovery message
  • the processing module is further configured to determine scheduling request configuration information in response to the RRC recovery message, where the scheduling request configuration information is used to obtain uplink shared channel resources;
  • the sending module is used to send a radio link control status report through the uplink shared channel resource, and the radio link control status report is used to provide a positive response of the radio link control service data unit.
  • the processing module is configured to determine the scheduling request configuration information in response to the RRC recovery message, specifically including: the processing module is configured to determine the scheduling request configuration information according to the RRC recovery message.
  • the sending unit is further configured to send an RRC recovery complete message through the uplink shared channel resource, and the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the processing module is specifically configured to determine the scheduling request configuration information according to the RRC recovery message.
  • the scheduling request configuration information includes: a scheduling request identifier and a scheduling request resource identifier.
  • the processing module is also used to resume the suspended radio bearer.
  • the third aspect of the embodiments of the present application discloses a wireless communication device, including: a processor and a memory coupled with each other;
  • the memory is used to store program instructions for radio resource control RRC connection recovery
  • the processor is configured to run the program instructions for the radio resource control RRC connection restoration stored in the memory, wherein the program instructions for the connection restoration execute the radio resource control as disclosed in the first aspect of the embodiments of the present application when the program instructions are executed. RRC connection recovery method.
  • the fourth aspect of the embodiments of the present application discloses a user equipment.
  • the user equipment includes the wireless communication device disclosed in the second aspect of the embodiments of the present application and any possible implementation manner, or the third aspect and any one of the third aspects of the embodiments of the present application.
  • One possible implementation is disclosed in the wireless communication device.
  • the fourth aspect of the embodiments of the present application discloses a computer-readable storage medium having computer-executable instructions stored on the computer-readable storage medium, and the computer-executable instructions are used to cause the computer to execute the present application when called by the computer.
  • the first aspect of the embodiments and any one of the possible implementation manners disclose the method for radio resource control RRC connection recovery.
  • the fifth aspect of the embodiments of the present application discloses a computer program product.
  • the computer program product contains computer instructions.
  • the computer program product runs on a computer, the computer executes the first aspect of the embodiments of the present application and any possible options.
  • the sixth aspect of the embodiments of the present application discloses a wireless communication device.
  • the wireless communication device includes a processor and an interface circuit.
  • the interface circuit is used to read a computer program from a memory, and the processor is used to execute the computer program to execute The method for radio resource control RRC connection recovery disclosed in the first aspect of the embodiments of the present application and any possible implementation manner.
  • the sixth aspect of the embodiments of the present application discloses a communication system including a wireless network device, and any possible implementation manner of the second aspect or the third aspect or any one of the possible implementation manners of the third aspect The device disclosed in any one of the embodiments.
  • the terminal resumes the RRC connection, confirms the scheduling request configuration information, and obtains uplink shared channel resources through the scheduling request configuration information, thereby Based on the uplink shared channel resource, the radio link control status report is sent to complete the connection recovery of the terminal.
  • the power consumption of the terminal can be reduced, and the waiting time delay of the terminal can be reduced, so as to achieve the purpose of quickly recovering the connection.
  • FIG. 1 is a system architecture diagram of a communication system disclosed in an embodiment of this application;
  • Figure 2 is a hierarchical schematic diagram of a radio resource control plane disclosed in an embodiment of this application;
  • FIG. 3 is a schematic diagram of a flow chart of NR RRC state transition disclosed in an embodiment of this application;
  • FIG. 4 is a schematic diagram of the process of terminal connection restoration in the prior art
  • Figure 5 is a signaling interaction diagram for initiating random access in the prior art
  • FIG. 6 is a schematic flowchart of a wireless communication method disclosed in an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another wireless communication method disclosed in an embodiment of this application.
  • FIG. 8 is a diagram of a code example of an RRC recovery message disclosed in an embodiment of this application.
  • FIG. 9 is a schematic flowchart of another wireless communication method disclosed in an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a wireless communication device disclosed in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of another wireless communication device disclosed in an embodiment of this application.
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same function and effect. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
  • FIG. 1 is a system architecture diagram of a communication system disclosed in an embodiment of this application.
  • the communication system is a 5G system, also known as an NR system.
  • the communication system 10 includes: a wireless network device 101 and a UE 102. Among them, the wireless network device 101 and the UE 102 establish a wireless connection through the NR air interface. It should be understood that although only one wireless network device and one UE are shown in FIG. 1, the communication system 10 may include multiple wireless network devices or multiple UEs.
  • the wireless network device 101 includes but is not limited to: next generation Node B (gNB or gNodeB) in 5G.
  • gNB next generation Node B
  • gNodeB next generation Node B
  • UE including but not limited to: mobile terminal, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control (industrial control) , Wireless terminals in self-driving (self-driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), smart cities (smart) Wireless terminals in the city, wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in industrial control (industrial control) Wireless terminals in self-driving
  • wireless terminals in remote medical remote medical
  • wireless terminals in smart grid smart grid
  • wireless terminals in transportation safety transportation safety
  • smart cities smart cities
  • FIG. 2 is a schematic diagram of a layered structure of a new wireless protocol stack disclosed in an embodiment of the application.
  • the layering of the user plane of the NR protocol stack includes: non-access stratum (NAS), RRC layer, packet data convergence protocol (PDCP) layer, radio link control (Radio link control, RLC) layer, media access control (medium access control, MAC) layer, and physical (physical, PHY) layer.
  • NAS non-access stratum
  • PDCP packet data convergence protocol
  • RLC radio link control
  • media access control medium access control
  • PHY physical (physical, PHY) layer.
  • the PHY layer belongs to the first layer (L1) of NR; the PDCP layer, the RLC layer and the MAC layer belong to the second layer (L2) of NR, also known as the data link layer; the RRC layer belongs to the third layer (L3) of NR. ), also known as the network layer.
  • NAS is located in the mobility management of the core network. (access and mobility management function, AMF) entity.
  • FIG. 3 is a schematic diagram of a flow of NR RRC state transition disclosed in an embodiment of the application.
  • the UE has three different RRC states. Namely RRC idle state, RRC connected state and RRC inactive state. It is understandable that the above three RRC states can be transformed into each other under different conditions.
  • the UE after searching for a cell, the UE will camp on a suitable cell and enter the RRC idle state.
  • the UE in the RRC idle state can enter the RRC connected state after establishing an (estabish) RRC link.
  • the UE in the RRC connected state can also release the RRC link and return to the RRC idle state again.
  • the UE in the RRC connected state can suspend the RRC connection and enter the RRC inactive state when there is no service temporarily.
  • the UE in the RRC inactive state can also resume (resume) and enter the RRC connected state.
  • a UE in the RRC inactive state can also release the RRC link and enter the RRC idle state; a UE in the RRC inactive state may be triggered by a service or need to be based on a radio access network (RAN) Notification area update (RAN-based notification area update, RNAU), you can also restore the connection, try to enter the RRC connection state.
  • RAN radio access network
  • RNAU radio access network Notification area update
  • the terminal In the inactive state, after receiving the RRC resume (RRCResume) message, since the RRC resume message is an acknowledged mode (AM) message, according to the 3GPP technical specifications (such as 3GPP TS38.322 V15.5.0), the terminal’s
  • the RLC layer needs to send an RLC status report to the RLC layer of the wireless network device.
  • the RLC status report is used to provide a positive acknowledgement and/or a negative acknowledgement to the gNB.
  • the RLC status report is uplink data, which is carried by PUSCH. Therefore, in order to send the above-mentioned RLC status report, the terminal needs to obtain uplink shared channel resources first.
  • the terminal in response to the received RRC recovery message, the terminal additionally initiates a random access procedure to obtain uplink shared channel resources to send the RLC status report.
  • the priority of the random access process is higher, which will hinder the transmission of uplink data and the reception of downlink data of the terminal, and the random access process requires more time.
  • the terminal initiates the random access process before completing the restoration of the RRC connection and sending the RRC recovery complete message, it needs to wait for the end of the random access process, obtain the uplink shared channel resource, and send the RLC status report through the uplink shared channel resource ,
  • the RRC recovery message can be sent, and the terminal waits for a long time.
  • the wireless network device for the wireless network device to additionally receive random access initiated by the UE, if the wireless network device is not fully functional, it may cause the wireless network device to be in an abnormal state, thereby causing the UE to fail to complete connection recovery.
  • Fig. 4 is a schematic diagram of the process of terminal connection restoration in the prior art. As shown in Figure 4, the signaling interaction between the terminal and the gNB is taken as an example to illustrate the connection recovery process of the terminal.
  • the gNB sends an RRC release (RRCRelease) message to the terminal.
  • RRC release RRCRelease
  • the terminal receives the RRC release message, and suspends the RRC connection based on the RRC release message. At this time, the terminal enters the RRC inactive state from the RRC connected state.
  • the terminal sends an RRC resume request (RRCResumeRequesst) message to the gNB.
  • RRC resume request RRCResumeRequesst
  • the gNB receives the RRC recovery request message, and sends an RRC recovery (RRCResume) message to the terminal based on the RRC recovery request message.
  • RRC recovery RRCResume
  • the terminal receives the RRC recovery message.
  • the terminal initiates random access to the gNB.
  • the uplink shared channel resources can be obtained.
  • the random access process between the terminal and the gNB can be seen in Figure 5, where n ⁇ 2.
  • the terminal sends a random access preamble (RA preamble) to the gNB
  • the gNB sends a random access response (RA response) message to the terminal
  • the terminal sends the random access preamble to the gNB again
  • the gNB feeds back a response to the terminal again
  • the message is repeated at least twice to establish random access between the terminal and the gNB.
  • the gNB allocates uplink shared channel resources to the terminal.
  • the terminal restores the RRC connection according to the RRC restore message, and restoring the RRC connection includes entering the RRC connected state from the RRC inactive state.
  • the terminal sends an RLC status report to the gNB.
  • the terminal sends the RLC status report to the gNB through the uplink shared channel resource.
  • the terminal sends an RRC recovery complete message to the gNB.
  • the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery. After the gNB receives the RRC recovery complete message, it can confirm the successful completion of the RRC connection recovery.
  • the terminal sends an RRC recovery complete (RRCResumeComplete) message to the gNB through the above-mentioned uplink shared channel resource.
  • RRC recovery complete RRCResumeComplete
  • the terminal needs to reacquire a new uplink shared channel resource to send the RLC status report to the gNB.
  • the terminal additionally initiates random access to the wireless network device, which has the problems of increasing terminal power consumption, large waiting time delay, and affecting terminal performance.
  • the wireless network device when the terminal enters the RRC inactive state from the RRC connected state, the wireless network device will indicate a RAN area, RAN paging cycle, and so on.
  • the terminal When the terminal is in the RRC inactive state, there are usually four scenarios when trying to enter the RRC connected state from the RRC inactive state.
  • the first scenario receiving the RAN page of the network; the second scenario: triggering the uplink service or NAS signaling process; the third scenario: the RAN-based notification area update (RAN-based notification area update) is required after the terminal moves , RNAU); the fourth scenario: if the uplink service is not triggered, after the period timer (such as T380) previously set has expired.
  • the embodiments of the present application disclose a wireless communication method, device, and system.
  • UE connection recovery after receiving the RRC resume (RRCResume) message issued by the wireless network device, first determine whether there is scheduling request configuration information , And then perform subsequent operations. In this way, the UE is prevented from initiating unnecessary random access, and the power consumption and waiting delay of the UE are reduced, so that the UE can quickly resume the connection.
  • RRC resume RRCResume
  • the wireless connection restoration method of the present application is executed by a terminal-side device.
  • the device may be a terminal or a wireless communication device (such as a baseband processor) in the terminal. That is, the wireless communication method of the present application can be executed by the terminal or the wireless communication device in the terminal.
  • FIG. 6 is a schematic flowchart of a wireless communication method provided by an embodiment of the application. The method may be executed by a terminal or a chip inside the terminal. As shown in Figure 6, the method includes:
  • the terminal receives the RRC recovery message.
  • the terminal determines scheduling request configuration information in response to the RRC recovery message, where the scheduling request configuration information is used to obtain uplink shared channel resources.
  • the scheduling request configuration information is determined directly according to the RRC recovery message.
  • restoring the RRC connection includes restoring the primary cell group from the stored user equipment inactive access stratum (AS) context (UE Inactive AS context) (mastercellgroup).
  • AS user equipment inactive access stratum
  • UE Inactive AS context mastercellgroup
  • Scheduling request configuration (scheduling request config) information is used to obtain uplink shared channel resources.
  • the scheduling request configuration information includes a scheduling request identifier and a scheduling request resource identifier.
  • the scheduling request configuration information includes: a scheduling request identifier (SchedulingRequestID) and a scheduling request resource identifier (SchedulingRequestResourceID).
  • a scheduling request signal (signalling of Scheduling Request) is sent according to the foregoing scheduling request configuration information, where the scheduling request signal is carried by a physical uplink control channel (PUCCH), and the scheduling request signal is used to request PUSCH resources.
  • PUCCH physical uplink control channel
  • the primary cell group recovered from the stored user equipment inactive state access layer context includes: scheduling request configuration (SchedulingRequestConfig) information element (IE) ), a logical channel configuration (LogicalChannelConfig) cell, and a scheduling request resource configuration (SchedulingRequestResourceConfig) cell.
  • the foregoing three types of information elements all carry a scheduling request identifier, and the scheduling request resource configuration information element also carries a scheduling request resource identifier.
  • the RRC recovery message includes: a scheduling request configuration information element, a logical channel configuration information element, and a scheduling request resource configuration information element.
  • the foregoing three types of information elements all carry a scheduling request identifier, and the scheduling request resource configuration information element also carries a scheduling request resource identifier.
  • scheduling request identifiers determined from the above three types of information elements can it be
  • the scheduling request signal is sent by using the scheduling request identifier and the call request resource identifier determined from the above three types of information elements to request uplink shared channel resources. If they are inconsistent, the uplink shared channel resource can be obtained by initiating a random access procedure.
  • the terminal sends an RLC status report.
  • the terminal sends the RLC status report through the uplink shared channel resource.
  • the RLC status report is used to provide a positive response of the RLC service data unit (SDU), and the RLC status report is uplink data, which is carried by the PUSCH.
  • SDU RLC service data unit
  • the foregoing method further includes 604: sending an RRC recovery complete message.
  • the terminal sends an RRC recovery complete message through the uplink shared channel resource.
  • the terminal sends an RRC recovery complete (RRCResumeComplete) message through the obtained uplink shared channel resource, where the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the wireless network device After receiving the foregoing RRC recovery complete message, the wireless network device confirms that the RRC connection recovery process is successfully completed.
  • the terminal resumes the RRC connection, confirms the scheduling request configuration information, and obtains uplink shared channel resources through the scheduling request configuration information, thereby Based on the uplink shared channel resources, the RLC status report is sent and the RRC recovery complete message is sent to complete the connection recovery of the terminal.
  • FIG. 7 is a schematic flowchart of another wireless communication method provided by an embodiment of the application. This method can be executed by the terminal, or executed by a chip inside the terminal. As shown in Figure 7, the method includes:
  • the terminal receives an RRC release message from the wireless network device, where the RRC release message includes a suspension configuration field, and the RRC release message is used to indicate to suspend the RRC connection.
  • the terminal in the RRC connected state receives the above-mentioned RRC release message. If the RRC release (RRCRelease) message includes a suspendconfig (suspendconfig) field, the RRC release message is used to instruct the terminal to suspend the RRC connection .
  • RRC release RRCRelease
  • suspendconfig suspendconfig
  • the suspension configuration field may be carried by the RRC release information element (IE) in the RRC release message.
  • the wireless network device may be a wireless network device corresponding to the gNB.
  • the terminal suspends the RRC connection, and enters the RRC inactive state from the RRC connected state.
  • the terminal suspends the RRC connection according to the RRC release message, which specifically includes the following operations:
  • the suspended radio bearer includes SRB and data radio bearer (DRB) other than signaling radio bearer (SRB)0.
  • SRB1 stores the inactive access stratum context of the user equipment.
  • the terminal enters the RRC inactive state from the RRC connected state.
  • receiving the RRC release message also indicates that the packet data convergence protocol (PDCP) is suspended to the lower layers of all DRBs.
  • PDCP packet data convergence protocol
  • the terminal sends an RRC recovery request message, where the RRC recovery request message is used to request the recovery of the RRC connection.
  • the terminal sends an RRC resume request (RRCResumeRequest) message to the wireless network device.
  • RRC resume request RRCResumeRequest
  • the RRC recovery request message sent by the UE to the wireless network device is also different.
  • the RRC recovery request message may specifically be an RRCResumeRequest message or a RRCResumeRequest1 message.
  • the terminal receives an RRC recovery message from the wireless network device, where the RRC recovery message does not include a full configuration field, and the RRC recovery message is used to recover the RRC connection.
  • the wireless network device may send an RRC resume (RRCResume) message to the terminal, so that the terminal resumes the RRC connection.
  • RRC resume RRCResume
  • the RRC recovery message includes the full configuration (fullconfig) field, it means that the RRC is restored to the full configuration; otherwise, if the RRC recovery message does not include the full configuration field, it means that the RRC is restored to the incremental configuration.
  • the full configuration can be understood as: release or clear the current wireless configuration except the primary cell group radio network temporary identification (MCG-RNTI) and the AS security configuration coordinated with the master key, and reconfigure the wireless configuration related parameters; and Incremental configuration can be understood as only updating the parameter configuration carried in the message.
  • MCG-RNTI primary cell group radio network temporary identification
  • Incremental configuration can be understood as only updating the parameter configuration carried in the message.
  • FIG. 8 is a diagram of a code example of an RRC recovery message disclosed in an embodiment of this application.
  • the presence of 801 indicates that the RRC recovery message carries the full configuration field, and the full configuration field is carried by the RRC recovery cell in the RRC recovery message. If the RRC recovery message carries this field and the configuration is true ( true), it means full configuration. If this field is not carried in the RRC recovery message or the field is configured as false, it means incremental configuration.
  • the terminal restores the RRC connection according to the received RRC restore message, where restoring the RRC connection includes entering the RRC connected state from the RRC inactive state.
  • restoring the RRC connection may specifically include the following operations: restoring the master cell group (master cell group), PDCP configuration (pdcp-config), and previous hanging from the user equipment inactive AS context previously stored by the terminal. Wireless bearer.
  • the terminal determines the scheduling request configuration information.
  • the terminal may also determine scheduling request configuration information according to the primary cell group.
  • the terminal can pass
  • the terminal may directly determine the scheduling request configuration information according to the RRC recovery message. If the wireless network device that instructs the terminal to suspend RRC and the wireless network device that instructs the terminal to resume RRC are different, the information in the inactive AS context of the user equipment previously stored by the terminal may no longer be applicable, and the scheduling can be determined directly through the RRC resume message Request configuration information.
  • the scheduling request configuration information includes: a scheduling request identifier (SchedulingRequestID) and a scheduling request resource identifier (SchedulingRequestResourceID).
  • the scheduling request signal is sent according to the foregoing scheduling request configuration information, where the scheduling request signal is carried by the PUCCH, and the scheduling request signal is used to request PUSCH resources.
  • the RRC recovery message includes: a scheduling request configuration information element, a logical channel configuration information element, and a scheduling request resource configuration information element.
  • the foregoing three types of information elements all carry a scheduling request identifier, and the scheduling request resource configuration information element also carries a scheduling request resource identifier. Only when the scheduling request identifiers determined from the above three types of information elements are consistent, can the scheduling request identifier and the call request resource identifier determined from the above three types of information elements be used to send a scheduling request signal to request uplink shared channel resources .
  • the terminal sends an RLC status report to the wireless network device.
  • the terminal sends an RLC status report to the wireless network device through the uplink shared channel resource.
  • the RLC status report is used to provide the response of the RLC service date unit (SDU).
  • the RLC status report is uplink data and is carried by the PUSCH.
  • the terminal sends an RRC recovery complete message to the wireless network device.
  • the terminal sends an RRC recovery complete message to the wireless network device through the uplink shared channel resource.
  • the terminal sends an RRC recovery complete message through the obtained uplink shared channel resource.
  • the terminal After receiving the RRC recovery message from the wireless network device, the terminal confirms whether there is currently scheduling request configuration information, and in the case of confirming that there is scheduling request configuration information, based on the The scheduling request configuration information obtains the uplink shared channel resource to send the RLC status report and the RRC recovery complete message to complete the connection recovery of the terminal. This prevents the terminal from initiating unnecessary random access during the connection recovery process, reduces the power consumption of the terminal, improves the performance of the terminal, and achieves the purpose of quickly recovering the connection of the terminal.
  • FIG. 9 is a schematic flowchart of another wireless communication method provided by an embodiment of this application. This method can be executed by the terminal, or executed by a chip inside the terminal. As shown in Figure 9, the method includes:
  • the terminal receives an RRC release message from the wireless network device, where the RRC release message includes a suspension configuration field, and the RRC release message is used to indicate to suspend the RRC connection.
  • the terminal suspends the RRC connection, and enters the RRC inactive state from the RRC connected state.
  • the terminal sends an RRC recovery request message, where the RRC recovery request message is used to request the recovery of the RRC connection.
  • the terminal receives an RRC recovery message from the wireless network device, where the RRC recovery message does not include a full configuration field, and the RRC recovery message is used to recover the RRC connection.
  • the terminal sends a random access preamble (RA preamble) to the wireless network device to initiate a random access process.
  • RA preamble random access preamble
  • the terminal sends a random access preamble to the wireless network device on a specific resource element (RE), thereby initiating a random access process.
  • the specific process can be seen in Figure 5.
  • the terminal sends a random access preamble to the wireless network device on a specific RE, the wireless network device feeds back a response message to the terminal, the terminal again sends the random access preamble to the wireless network device, and the wireless network device feeds back a response message to the terminal again, and so on. , Until the random access between the terminal and the wireless network device is established or terminated.
  • the terminal terminates the random access process initiated to the wireless network device.
  • the previously initiated random access process can be terminated in advance.
  • the terminal may discard the random access response after receiving the random access response sent by the wireless network device, and stop sending the random access preamble to the wireless network device Code to terminate the random access process to the wireless network device.
  • the terminal may directly stop sending the random access preamble to the wireless network device, thereby terminating the initiation of the random access process to the wireless network device.
  • the terminal restores the RRC connection according to the RRC restore message, and restoring the RRC connection includes entering the RRC connected state from the RRC inactive state.
  • the terminal determines the scheduling request configuration information.
  • the terminal sends an RLC status report to the wireless network device.
  • the terminal sends an RRC recovery complete message to the wireless network device.
  • the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the terminal after receiving the RRC recovery message from the wireless network device, the terminal can terminate the random access process if it has initiated the random access process before confirming whether there is currently scheduling request configuration information. Enter the process, and when it is confirmed that the scheduling request configuration information exists, the uplink shared channel resource is obtained based on the scheduling request configuration information to send the RLC status report and the RRC recovery complete message to complete the connection recovery of the terminal. This prevents the terminal from initiating unnecessary random access during the connection recovery process, reduces the waiting time delay of the terminal, reduces the power consumption of the terminal, and improves the performance of the terminal, so as to achieve the purpose of quickly recovering the connection.
  • the embodiment of the present application also discloses several wireless communication devices.
  • the device may be a UE.
  • the specific description will be given by the following examples.
  • FIG. 10 is a schematic structural diagram of a wireless communication device disclosed in an embodiment of this application.
  • the wireless communication device 100 mainly includes: a receiving module 101, a processing module 102, and a sending module 103.
  • the receiving module 101 is configured to receive an RRC recovery message.
  • the processing module 102 is configured to determine scheduling request configuration information in response to the RRC recovery message, where the scheduling request configuration information is used to obtain uplink shared channel resources.
  • the sending module 103 is configured to send a radio link control status report through the uplink shared channel resource, where the radio link control status report is used to provide a response of the radio link control service data unit.
  • the sending module 103 is configured to send an RRC recovery complete message through the uplink shared channel resource, where the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the receiving module 101 is configured to receive an RRC release message, where the RRC release message includes a suspension configuration field, and the RRC release message is used to indicate that the RRC connection is suspended.
  • the processing module 102 is configured to suspend the RRC connection and enter the RRC inactive state from the RRC connected state.
  • the sending module 103 is configured to send an RRC recovery request message, where the RRC recovery request message is used to request the recovery of the RRC connection.
  • the receiving module 101 is configured to receive an RRC recovery message, where the RRC recovery message does not include a full configuration field, and the RRC recovery message is used to recover the RRC connection.
  • the processing module 102 is configured to restore the RRC connection according to the RRC restoration message, and restoring the RRC connection includes entering the RRC connection state from the RRC inactive state, and determining the scheduling request configuration information according to the RRC restoration message.
  • the scheduling request configuration information is used to obtain uplink shared channel resources.
  • the sending module 103 is configured to send a radio link control status report through the uplink shared channel resource, and the radio link control status report is used to provide a response of the radio link control service data unit
  • the sending module 103 is configured to send an RRC recovery complete message through the uplink shared channel resource, and the RRC recovery complete message is used to confirm the successful completion of the RRC connection recovery.
  • the terminal After receiving the RRC recovery message from the wireless network device, the terminal confirms that there is currently scheduling request configuration information, and can obtain uplink shared channel resources based on the scheduling request configuration information to send The RLC status report and the RRC recovery complete message are used to complete the connection recovery of the terminal. This prevents the terminal from initiating unnecessary random access during the connection recovery process, reduces the power consumption of the terminal, improves the performance of the terminal, and achieves the purpose of quickly recovering the connection of the terminal.
  • the processing module 102 is specifically configured to store the inactive access layer context of the user equipment and suspend the radio bearer.
  • radio bearers include signaling radio bearers and data radio bearers other than signaling radio bearer 0.
  • the processing module 102 is specifically configured to restore the primary cell group from the inactive access layer context of the user equipment and restore the radio bearer.
  • the processing module 102 is specifically configured to determine the scheduling request configuration information according to the primary cell group.
  • the processing module 102 is further configured to, after determining the scheduling request configuration information according to the RRC recovery message, send a scheduling request signal according to the scheduling request configuration information, and the scheduling request signal is carried by the physical uplink control channel, The scheduling request signal is used to request uplink shared channel resources.
  • the sending module 103 is also used to send an RRC recovery complete message through the uplink shared channel resource.
  • the sending module 103 is further configured to randomly access the preamble after the receiving module 101 receives the RRC recovery message, so as to initiate a random access process.
  • processing module 102 is further configured to terminate the random access process before determining the scheduling request configuration information according to the RRC recovery message.
  • the processing module 102 is specifically configured to discard the random access response message after the receiving module 101 receives the random access response message, and control The sending module 103 stops sending the random access preamble.
  • the processing module 102 is specifically configured to directly control the sending module 103 to stop sending the random access preamble.
  • FIG. 2 a schematic diagram of the layered structure of the new wireless protocol stack is disclosed.
  • the receiving module in the wireless communication device disclosed in the above embodiment of the application for example, the functions of the sending module and the processing module can be shown in Figure 2
  • the deployment is implemented in the RRC layer and RLC layer in the UE.
  • an embodiment of the present application also provides a communication system, which includes a wireless network device, and the wireless communication device disclosed in FIG. 10 of the foregoing embodiment of the present application.
  • the device disclosed in the embodiment of the present application suitable for the wireless communication method may also be directly implemented by hardware, a memory executed by a processor, or a combination of the two. It can also be the processor, controller, or chip on the terminal.
  • FIG. 11 is a schematic structural diagram of another wireless communication device disclosed in an embodiment of this application.
  • the wireless communication device includes a memory 111, a processor 112 and a communication interface 113 that communicate with the memory.
  • the communication interface 113 may also be referred to as an interface circuit.
  • the processor 112 is coupled with the memory 111 through a bus.
  • the processor 112 is coupled with the communication interface 113 through a bus.
  • the memory 111 may specifically be a content-addressable memory (CAM) or a random-access memory (RAM).
  • the CAM may be a ternary cam (TCAM).
  • the processor 112 may specifically be a central processing unit (CPU), a network processor (NP), an application-specific integrated circuit (ASIC), or a programmable logic device (PLD). ).
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA) or a generic array logic (GAL).
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL generic array logic
  • the communication interface 113 may be a wired interface, such as a fiber distributed data interface (FDDI) or an Ethernet (ethernet) interface.
  • FDDI fiber distributed data interface
  • Ethernet Ethernet
  • the memory 111 may also be integrated in the processor 112. If the memory 111 and the processor 112 are independent devices, the memory 111 and the processor 112 are connected.
  • the memory 111 and the processor 112 may communicate through a bus.
  • the communication interface 113 and the processor 112 may communicate through a bus, and the communication interface 113 may also be directly connected to the processor 112.
  • the memory 111 is used for storing wireless communication method program instructions.
  • the memory 111 includes an operating system and an application program, which is used to carry the operation program, code, or instruction of the wireless communication method disclosed in the above embodiment of the present application.
  • the processor 112 calls the wireless communication method program code in the memory 111, and executes the methods described in FIG. 6, FIG. 7, and FIG. 9, for example:
  • Receive the RRC release message suspend the RRC connection, enter the RRC inactive state from the RRC connected state, send the RRC recovery request message, receive the RRC recovery message, restore the RRC connection according to the RRC recovery message, and enter the RRC connection from the RRC inactive state According to the RRC recovery message, determine the scheduling request configuration information, and send the RRC recovery complete message.
  • receiving/sending involved in the wireless communication method embodiments shown in FIG. 6, FIG. 7, and FIG. 9 may refer to receiving/sending processing performed by the processor, or may refer to Receiver and transmitter complete the sending/receiving process, the receiver and transmitter can exist independently, or they can be integrated as a transceiver.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (such as a floppy disk, a hard disk, and a magnetic tape), an optical medium (such as an optical disk), or a semiconductor medium (such as a solid-state hard disk).
  • the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program.
  • the computer program is executed by related hardware to implement any wireless communication method provided in the embodiments of the present invention.
  • the embodiment of the present application also provides a user equipment.
  • the user equipment includes any wireless communication device disclosed in the foregoing embodiments of the present application. Wherein, when the terminal is running, the terminal is caused to execute any of the wireless communication methods provided in the embodiments of the present application.
  • the terminal when the terminal confirms that the scheduling request configuration information currently exists, it can obtain the uplink shared channel resource based on the scheduling request configuration information to send the RLC status report and RRC recovery complete message to complete the connection recovery of the terminal.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种无线通信方法、装置及系统，针对连接恢复的场景，通过调度请求配置信息获取上行共享信道资源，以发送无线链路控制状态报告，以及发送无线资源控制恢复完成消息，可以避免终端在连接恢复过程中发起不必要的随机接入，实现降低终端功耗，降低等待时延，提高终端性能，以达到终端快速恢复连接的目的。

Description

无线通信方法、装置及系统 技术领域
本申请涉及移动通信技术领域，尤其是，涉及一种无线通信方法、装置及系统。
背景技术
在第五代移动通信(the 5th generation mobile communication，5G)技术领域中，对于无线资源控制(radio resource control，RRC)层，用户设备(user equipment，UE)具有RRC空闲态，RRC连接态和RRC非激活态三种不同的新无线(new radio，NR)RRC状态。
在UE从RRC非激活态进入RRC连接态时，UE需要获取上行共享信道资源后才能够发送上行消息。在现有技术中，UE可以通过额外向无线网络设备发起随机接入，来获取无线网络设备的上行共享信道资源，以发送无线链路控制(radio link control，RLC)状态报告(status report)。但是，随机接入过程的等待时延较长，浪费UE功耗，同时，无线网络设备对于额外接收到UE所发起的随机接入，在无线网络设备功能不完善的情况下，可能会导致无线网络设备状态异常，从而导致UE无法完成连接恢复。
发明内容
有鉴于此，本申请实施例提供一种无线通信方法、装置及系统，以避免UE在连接恢复过程中发起不必要的随机接入，从而降低时延，以达到UE快速恢复连接的目的。
应理解，本申请实施例中的方法可以由无线通信装置执行，该无线通信装置可以是计算设备的整机，也可以是该计算设备中的部分器件，例如无线通信功能相关的芯片，如系统芯片、通信芯片。其中，系统芯片也称为片上系统，或称为SoC芯片。具体地，无线通信装置可以是诸如智能手机这样的终端，也可以是能够被设置在终端中的系统芯片或通信芯片。通信芯片可以包括射频处理芯片和基带处理芯片的一种或多种。基带处理芯片有时也称为调制解调器(modem)或基带处理器。在物理实现中，通信芯片可集成在SoC芯片内部，也可以不与SoC芯片集成。例如，基带处理芯片集成在SoC芯片中，射频处理芯片不与SoC芯片集成。
本申请实施例提供如下技术方案：本申请实施例第一方面公开了一种无线资源控制RRC连接恢复的方法，包括：
接收无线资源控制RRC恢复消息；
响应于该RRC恢复消息，确定调度请求配置信息，其中，该调度请求配置信息用于获取上行共享信道资源；
通过该上行共享信道资源，发送无线链路控制状态报告，该无线链路控制状态报告用于提供无线链路控制业务数据单元的肯定响应。
应理解，其中，无线链路控制状态报告由物理上行共享信道(physical uplink share channel，PUSCH)承载。针对RRC连接恢复的场景，通过调度请求配置信息来获取上行共享信道资源，以发送无线链路控制状态报告，可以避免终端在连接恢复过程中发起不必要的随机接入，实现降低终端功耗，降低等待时延，以达到终端快速恢复连接的目的。
在一种可能的实现方式中，响应于该RRC恢复消息，确定调度请求配置信息，包括：响应于该RRC恢复消息，恢复RRC连接，其中，该恢复RRC连接包括：从存储的用户设备非激活态接入层上下文中恢复主小区组；根据该主小区组，确定调度请求配置信息。
应理解，在终端挂起RRC连接时，会存储用户设备非激活态接入层上下文。从存储的用户设备非激活态接入层上下文中恢复主小区组，以确定其中所携带的调度请求配置信息。在指示终端挂起RRC连接的无线网络设备和指示终端恢复RRC连接的无线网络设备为同一无线网络设备时，该调度请求配置信息可以用于获取上行共享信道资源。
在一种可能的实现方式中，响应于该RRC恢复消息，确定调度请求配置信息，包括：根据该RRC恢复消息，确定调度请求配置信息。
应理解，由于指示终端挂起RRC连接的第一无线网络设备和指示终端恢复RRC连接的第二无线网络设备可能不是一个无线网络设备，所以挂起RRC连接时存储的用户设备非激活态接入层上下文中的调度请求配置信息可能不再适用，第二无线网络设备所下发的RRC恢复消息中可能会携带调度请求配置信息。
这里，该调度请求配置信息用于获取上行共享信道资源，具体可以通过以下方式：根据调度请求配置信息发送调度请求信号，该调度请求信号由物理上行控制信道承载，该调度请求信号用于请求上行共享信道资源。
在一种可能的实施方式中，该方法还包括：通过该上行共享信道资源，发送RRC恢复完成消息，该RRC恢复完成消息用于确认该RRC连接恢复的成功完成。
在一种可能的实现方式中，该恢复RRC连接还包括：恢复挂起的无线承载。
在一种可能的实现方式中，该调度请求配置信息包括：调度请求标识以及调度请求资源标识。
在一种可能的实现方式中，在接收RRC恢复消息之前，该方法还包括：发送RRC恢复请求消息，该RRC恢复请求消息用于请求恢复RRC连接；接收RRC恢复消息，该RRC恢复消息不包括全量配置字段，该RRC恢复消息用于指示恢复RRC连接。
其中，RRC恢复请求消息可以是RRC恢复请求(RRCResumeRequest)消息，或者，RRC恢复请求消息还可以是RRC恢复请求1(RRCResumeRequest1)消息。
本申请实施例第二方面公开了一种无线通信装置，包括：
接收模块，处理模块以及发送模块；
该接收模块，用于接收无线资源控制RRC恢复消息；
该处理模块，还用于响应于该RRC恢复消息，确定调度请求配置信息，其中，该调度请求配置信息用于获取上行共享信道资源；
该发送模块，用于通过该上行共享信道资源，发送无线链路控制状态报告，该无线链路控制状态报告用于提供无线链路控制业务数据单元的肯定响应。
在一种可能的实现方式中，该处理模块，用于响应于该RRC恢复消息，确定调度请求配置信息，具体包括：该处理模块，用于根据该RRC恢复消息，确定调度请求配置信息。
在一种可能的实现方式中，该发送单元，还用于通过该上行共享信道资源，发送RRC恢复完成消息，该RRC恢复完成消息用于确认该RRC连接恢复的成功完成。
在一种可能的实现方式中，该处理模块，具体用于根据该RRC恢复消息，确定调度请求配置信息。
在一种可能的实施方式中，该调度请求配置信息包括：调度请求标识以及调度请求资源标识。
在一种可能的实现方式中，该处理模块，还用于恢复挂起的无线承载。
本申请实施例第三方面公开了一种无线通信装置，包括：相互耦合的处理器和存储器；
该存储器，用于存储用于无线资源控制RRC连接恢复的程序指令；
该处理器，用于运行该存储器存储的用于该无线资源控制RRC连接恢复的程序指令，其中，该连接恢复的程序指令运行时执行如本申请实施例第一方面公开的该的无线资源控制RRC连接恢复的方法。
本申请实施例第四方面公开了一种用户设备，该用户设备包括本申请实施例第二方面及任一种可能的实现方式公开的无线通信装置，或者本申请实施例第三方面及任一种可能的实现方式公开的该的无线通信装置。
本申请实施例第四方面公开了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机可执行指令，该计算机可执行指令在被该计算机调用时用于使该计算机执行本申请实施例第一方面及任一种可能的实现方式公开的无线资源控制RRC连接恢复的方法。
本申请实施例第五方面公开了一种计算机程序产品，该计算机程序产品包含计算机指令，当该计算机程序产品在计算机上运行时，使得计算机执行本申请实施例第一方面及任一种可能的实现方式公开的无线资源控制RRC连接恢复的方法。
本申请实施例第六方面公开了一种无线通信装置，该无线通信装置包括：处理器以及接口电路，接口电路用于从存储器中读取计算机程序，该处理器用于执行该计算机程序，以执行本申请实施例第一方面及任一种可能的实现方式公开的无线资源控制RRC连接恢复的方法。
本申请实施例第六方面公开了一种通信系统，该通信系统包括无线网络设备，以及第二方面或第三方面或第二方面任一种可能的实施方式或第三方面任一种可能的实施方式公开的任一项该的装置。在本申请实施例中，针对连接恢复的场景，终端在接收到来自无线网络设备的RRC恢复消息之后，恢复RRC连接，确认调度请求配置信息，并通过调度请求配置信息获取上行共享信道资源，从而基于上行共享信道资源发送无线链路控制状态报告，完成终端的连接恢复。以避免终端在连接恢复过程中发起不必要的随机接入，实现降低终端功耗，降低终端等待时延，以达到终端快速恢复连接的目的。
附图说明
图1为本申请实施例公开的一种通信系统的系统架构图；
图2为本申请实施例公开的一种无线资源控制面的分层示意图；
图3为本申请实施例公开的一种NR RRC状态转换的流程示意图；
图4为现有技术中终端连接恢复的流程示意图；
图5为现有技术中发起随机接入的信令交互图；
图6为本申请实施例公开的一种无线通信方法流程示意图；
图7为本申请实施例公开的另一种无线通信方法流程示意图；
图8为本申请实施例公开的RRC恢复消息的代码示例图；
图9为本申请实施例公开的另一种无线通信方法的流程示意图；
图10为本申请实施例公开的一种无线通信装置的结构示意图；
图11为本申请实施例公开的另一种无线通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
此外，本申请实施例和权利要求书及附图中的术语“包括”和“具有”不是排他的。例如，包括了一系列步骤或模块的过程、方法、系统、产品或设备没有限定于已列出的步骤或模块，还可以包括没有列出的步骤或模块。
图1为本申请实施例公开的一种通信系统的系统架构图。该通信系统为5G系统，又称NR系统。如图1所示，该通信系统10包括：无线网络设备101和UE 102。其中，无线网络设备101和UE102通过NR空口建立无线连接。应理解，虽然图1中仅示出一个无线网络设备和一个UE，但通信系统10中可以包括多个无线网络设备，也可以包括多个UE。
这里，无线网络设备101，包括但不限于：5G中的下一代基站(next generation Node B，gNB或者gNodeB)。
UE，包括但不限于：移动终端、平板电脑、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
图2为本申请实施例公开的一种新无线协议栈的分层结构示意图。如图2所示，该NR协议栈用户面的分层包括：非接入层(non access stratum，NAS)，RRC层，分组数据聚合协议(packet data convergence protocol，PDCP)层，无线链路控制(radio link control，RLC)层，媒体接入控制(medium access control，MAC)层和物理(physical， PHY)层。
其中，PHY层属于NR的第一层(L1)；PDCP层，RLC层和MAC层属于NR的第二层(L2)，也称为数据链路层；RRC层属于NR的第三层(L3)，也称为网络层。
如图2所示，UE的全部协议栈都位于UE内，而在网络侧，gNB上部署有RRC层，PDCP层，RLC层，MAC层和PHY层，其中，NAS位于核心网的移动性管理(access and mobility management function，AMF)实体中。
图3为本申请实施例公开的一种NR RRC状态转换的流程示意图。如图3所示，在NR中，UE具有三种不同的RRC状态。即RRC空闲态，RRC连接态和RRC非激活态。可以理解的是，上述三种RRC状态可以在不同条件下相互转化。
具体地，例如，UE在搜索小区后，会驻留到合适的小区内，并进入RRC空闲态。处于RRC空闲态的UE在注册或者业务触发等场景，可以建立(estabish)RRC链路后进入RRC连接态。
进一步地，处于RRC连接态的UE还可以释放(release)RRC链路，重新返回RRC空闲态。为了节省功耗，处于RRC连接态的UE在暂时没有业务时，可以挂起该RRC连接，进入RRC非激活态。处于RRC非激活态的UE，也可以重新恢复(resume)进入RRC连接态。类似的，处于RRC非激活态的UE，也可以释放RRC链路进入RRC空闲态；处于RRC非激活态的UE，在有业务触发或者需要做基于无线接入网络(radio access network，RAN)的通知区域更新(RAN-based notification area update，RNAU)，也可以进行连接恢复，尝试进入RRC连接态。
处于非激活态的终端，在接收到RRC恢复(RRCResume)消息后，由于RRC恢复消息为确认模式(acknowledged mode，AM)消息，根据3GPP技术规范(如3GPP TS38.322 V15.5.0)，终端的RLC层需要向无线网络设备的RLC层发送RLC状态报告，该RLC状态报告用于向gNB提供肯定响应(positive acknowledgements)，和/或，否定响应(negative acknowledgements)。其中，RLC状态报告为上行数据(uplink data)，由PUSCH承载。因此，为了发送上述RLC状态报告，终端需要先获取上行共享信道资源。在现有技术中，终端响应于所接收的RRC恢复消息，会额外发起随机接入过程以获取上行共享信道资源来发送RLC状态报告。但随机接入过程的优先级较高，会阻碍终端上行数据的发送以及下行数据的接收，并且随机接入过程所需时间较多。若终端在完成恢复RRC连接，并发送RRC恢复完成消息前，发起了随机接入过程，则需要等待随机接入过程结束，获得上行共享信道资源，并通过该上行共享信道资源发送RLC状态报告后，才可发送RRC恢复消息，终端等待时延较长。同时，无线网络设备对于额外接收到UE所发起的随机接入，在无线网络设备功能不完善的情况下，可能会导致无线网络设备状态异常，从而导致UE无法完成连接恢复。
图4为现有技术中终端连接恢复的流程示意图。如图4所示，以终端与gNB之间的信令交互为例，说明终端的连接恢复过程。
401：gNB向终端发送RRC释放(RRCRelease)消息。
402：终端接收该RRC释放消息，并基于该RRC释放消息挂起(suspend)RRC连 接。此时，终端从RRC连接态进入RRC非激活态。
403：终端向gNB发送RRC恢复请求(RRCResumeRequesst)消息。
404：gNB接收该RRC恢复请求消息，并基于该RRC恢复请求消息向终端发送RRC恢复(RRCResume)消息。
405：终端接收该RRC恢复消息。
为了发送上述RLC状态报告需要先获取上行共享信道资源。
406：终端向gNB发起随机接入。
通过发起随机接入过程，可以获取上行共享信道资源。其中，终端和gNB之间的随机接入流程可参见图5，其中，n≥2。如图5所示，终端向gNB发送随机接入前导码(RA preamble)，gNB向终端随机接入响应(RA response)消息，终端再次向gNB发送随机接入前导码，gNB再次向终端反馈响应消息，如此反复至少两次，以建立起终端与gNB之间的随机接入。
但每次随机接入前导码的发送和随机接入响应消息的接收都会耗时较久，随机接入流程会带来额外较长的延时。
407：gNB在随机接入建立好之后，向终端分配上行共享信道资源。
408：终端根据RRC恢复消息恢复该RRC连接，恢复该RRC连接包括由RRC非激活态进入RRC连接态。
409：终端向gNB发送RLC状态报告。
具体地，终端通过上行共享信道资源向gNB发送RLC状态报告。
410：终端向gNB发送RRC恢复完成消息。
其中，RRC恢复完成消息用于确认RRC连接恢复的成功完成。gNB接收到该RRC恢复完成消息，便可确认RRC连接恢复的成功完成。
在具体实现过程中，一种可能的实施方式中，终端通过上述上行共享信道资源向gNB发送RRC恢复完成(RRCResumeComplete)消息。
另一种可能的实施方式中，终端需要重新获取一个新的上行共享信道资源来向gNB发送RLC状态报告。
由上述可知，在基于现有技术进行终端连接恢复的过程中，终端额外向无线网络设备发起随机接入，存在提高终端功耗，等待时延较大，影响终端性能的问题。
需要说明的是，在实现上述终端连接恢复过程中，在终端由RRC连接态进入RRC非激活态时，无线网络设备会指示出一个RAN区域，RAN寻呼周期等。当终端处于RRC非激活态时，尝试由RRC非激活态进入RRC连接态通常有四种场景。第一种场景：收到网络的RAN寻呼；第二种场景：触发上行业务或者NAS信令流程；第三种场景：在终端移动之后需要做基于RAN的通知区域更新(RAN based notification area update，RNAU)之前；第四种场景：若没有触发上行业务，在之前设置的周期定时器(如T380)超时之后。
因此，本申请实施例公开了一种无线通信方法、装置及系统，针对UE连接恢复的场景，在接收到无线网络设备下发的RRC恢复(RRCResume)消息后，先确定是否存 在调度请求配置信息，再执行后续操作。从而避免UE发起不必要的随机接入，实现降低UE功耗和等待时延，以达到UE快速恢复连接。
需要说明的是，本申请的无线连接恢复的方法由终端侧的装置执行。其中，该装置可以为终端，也可以为终端中的无线通信装置(如基带处理器)。即可以由终端或终端中的无线通信装置执行本申请的无线通信方法。
具体实现过程通过下述本申请实施例详细进行说明。
图6为本申请实施例提供的一种无线通信方法流程示意图，该方法可以由终端执行，或者由终端内部的芯片执行。如图6所示，该方法包括：
601：终端接收RRC恢复消息。
602：终端响应于RRC恢复消息，确定调度请求配置信息，其中，调度请求配置信息用于获取上行共享信道资源。
可选的，直接根据RRC恢复消息，确定调度请求配置信息。
可选的，响应于RRC恢复消息，恢复RRC连接，其中，恢复RRC连接包括包括从存储的用户设备非激活态接入层(access stratum，AS)上下文(UE Inactive AS context)中恢复主小区组(mastercellgroup)。通过恢复RRC连接是从存储的用户设备非激活态接入层上下文中恢复主小区组，根据主小区组确定调度请求配置信息。
调度请求配置(scheduling request config)信息用于获取上行共享信道资源。该调度请求配置信息包括调度请求标识以及调度请求资源标识。其中，调度请求配置信息包括：调度请求标识(SchedulingRequestID)以及调度请求资源标识(SchedulingRequestResourceID)。根据上述调度请求配置信息发送调度请求信号(signalling of Scheduling Request)，其中，调度请求信号由物理上行控制信道(physical uplink control channel，PUCCH)承载，该调度请求信号用于请求PUSCH资源。
应理解，在具体实现过程中，一种可选的实施方式，从存储的用户设备非激活态接入层上下文恢复的主小区组中包括:调度请求配置(SchedulingRequestConfig)信元(information element，IE)、逻辑信道配置(LogicalChannelConfig)信元、以及调度请求资源配置(SchedulingRequestResourceConfig)信元。上述三种信元均携带调度请求标识，其中，调度请求资源配置信元还携带了调度请求资源标识。另一种可选的实施方式，RRC恢复消息中包括:调度请求配置信元、逻辑信道配置信元、以及调度请求资源配置信元。上述三种信元均携带调度请求标识，其中，调度请求资源配置信元还携带了调度请求资源标识。
可选的，在具体实现过程中，只有在从上述三种信元(调度请求配置信元、逻辑信道配置信元、以及调度请求资源配置信元)中确定的调度请求标识一致时，才可以采用从上述三种信元中确定的调度请求标识和调取请求资源标识来发送调度请求信号，以请求上行共享信道资源。若不一致，则可以通过发起随机接入过程来获得上行共享信道资源。
603：终端发送RLC状态报告。
具体地，终端通过该上行共享信道资源，发送RLC状态报告。其中，RLC状态报告用于提供RLC业务数据单元(service data unit，SDU)的肯定响应，RLC状态报告 为上行数据，由PUSCH承载。
可选的，上述方法还包括604：发送RRC恢复完成消息。
具体地，终端通过该上行共享信道资源，发送RRC恢复完成消息。终端通过所获得的上行共享信道资源来发送RRC恢复完成(RRCResumeComplete)消息，其中RRC恢复完成消息用于确认RRC连接恢复的成功完成。无线网络设备在接收到上述RRC恢复完成消息后，确认该RRC连接恢复过程成功地完成。
在本申请实施例中，针对连接恢复的场景，终端在接收到来自无线网络设备的RRC恢复消息之后，恢复RRC连接，确认调度请求配置信息，并通过调度请求配置信息获取上行共享信道资源，从而基于上行共享信道资源发送RLC状态报告、以及发送RRC恢复完成消息，完成终端的连接恢复。从而避免终端在连接恢复过程中发起不必要的随机接入，降低终端等待时延，实现降低终端功耗，提高终端性能，以达到终端快速恢复连接。
图7为本申请实施例提供的另一种无线通信方法流程示意图。该方法可以由终端执行，或者由终端内部的芯片执行。如图7所示，该方法包括：
可选的，701：终端接收来自无线网络设备的RRC释放消息，该RRC释放消息包括挂起配置字段，该RRC释放消息用于指示挂起RRC连接。
在701中，处于RRC连接态的终端接收到上述RRC释放消息，若该RRC释放(RRCRelease)消息中包括挂起配置(suspendconfig)字段(field)，该RRC释放消息用于指示终端挂起RRC连接。
其中，该挂起配置字段可以由RRC释放消息中的RRC释放信元(information element，IE)承载。无线网络设备可以是gNB对应的无线网络设备。
可选的，702：终端挂起该RRC连接，由RRC连接态进入RRC非激活态。
在702中，终端根据该RRC释放消息，挂起该RRC连接，具体包括下述操作：
应用接收到的挂起配置；如果存在预定义(default)的MAC小区组配置，则释放上述MAC小区组配置，并重配置MAC层；挂起无线承载。
其中，挂起的无线承载包括除信令无线承载(signaling radio bearer，SRB)0以外的SRB和数据无线承载(data radio bearer，DRB)。例如，SRB1；存储用户设备非激活态接入层上下文。
终端由RRC连接态进入RRC非激活态。
可以理解的是，接收到该RRC释放消息，也指示分组数据汇聚协议(packet data convergence protocol，PDCP)挂起至全部DRB的较低层。
可选的，703：终端发送RRC恢复请求消息，该RRC恢复请求消息用于请求恢复该RRC连接。
在703中，终端向无线网络设备发送RRC恢复请求(RRCResumeRequest)消息。因UE所处的小区不同，UE向无线网络设备发送的RRC恢复请求消息也会有所不同。其中，RRC恢复请求消息具体可以是RRCResumeRequest消息或者RRCResumeRequest1消息。
可选的，704：终端接收来自无线网络设备的RRC恢复消息，该RRC恢复消息不 包括全量配置字段，该RRC恢复消息用于恢复所述RRC连接。
在704中，响应于终端所发送的RRC恢复请求消息，无线网络设备可以向终端发送RRC恢复(RRCResume)消息，以使得终端恢复该RRC连接。
值得注意的是，若RRC恢复消息包括全量配置(fullconfig)字段，则意味着该RRC恢复为全量配置；否则，若RRC恢复消息不包括全量配置字段，则意味着该RRC恢复为增量配置。其中，全量配置可以理解为：释放或清除除主小区组无线网络临时标识(MCG-RNTI)和与主密钥协同的AS安全配置之外的当前无线配置，并重新配置无线配置相关参数；而增量配置可以理解为只更新消息中所携带的参数配置。为了更进一步地介绍该字段，下面给出一种RRC恢复消息的代码示意图。图8为本申请实施例公开的RRC恢复消息的代码示例图。如图8所示，801的存在表示该RRC恢复消息携带全量配置字段，且该全量配置字段由RRC恢复消息中的RRC恢复信元承载，若RRC恢复消息中携带该字段，且配置为真(true)，则意味着全量配置。若RRC恢复消息中不携带该字段或该字段配置为假(false)，则意味着增量配置。
705：终端根据该接收的RRC恢复消息，恢复该RRC连接，其中，恢复该RRC连接包括由RRC非激活态进入RRC连接态。
在705中，具体地，恢复该RRC连接具体可以包括下述操作：从终端之前存储的用户设备非激活态AS上下文中，恢复主小区组(mastercellgroup)、PDCP配置(pdcp-config)和之前挂起的无线承载。
706：终端确定调度请求配置信息。
在706中，可选的，终端还可以根据主小区组来确定调度请求配置信息。终端可以通过
可选的，终端可以直接根据RRC恢复消息来确定调度请求配置信息。若指示终端挂起RRC的无线网络设备和指示终端恢复RRC的无线网络设备不同，则终端之前存储的用户设备非激活态AS上下文中的信息可能不再适用，可以直接通过RRC恢复消息来确定调度请求配置信息。
其中，调度请求配置信息包括：调度请求标识(SchedulingRequestID)以及调度请求资源标识(SchedulingRequestResourceID)。根据上述调度请求配置信息发送调度请求信号，其中，调度请求信号由PUCCH承载，该调度请求信号用于请求PUSCH资源。
应理解，在具体实现过程中，一种可选的实施方式，RRC恢复消息中包括:调度请求配置信元、逻辑信道配置信元、以及调度请求资源配置信元。上述三种信元均携带调度请求标识，其中，调度请求资源配置信元还携带了调度请求资源标识。只有在从上述三种信元中确定的调度请求标识一致时，才可以采用从上述三种信元中确定的调度请求标识和调取请求资源标识来发送调度请求信号，以请求上行共享信道资源。
707：终端向无线网络设备发送RLC状态报告。
其中，终端通过上行共享信道资源，向无线网络设备发送RLC状态报告。RLC状态报告用于提供RLC业务数据单元(service date unit，SDU)的响应，RLC状态报告为上行数据，由PUSCH承载。
708：终端向无线网络设备发送RRC恢复完成消息。
其中，终端通过上行共享信道资源，向无线网络设备发送RRC恢复完成消息。在708中，具体的，终端通过所获得的上行共享信道资源发送RRC恢复完成消息。
在本申请实施例中，针对连接恢复的场景，终端在接收到来自无线网络设备的RRC恢复消息之后，确认当前是否存在调度请求配置信息，并在确认存在调度请求配置信息的情况下，基于该调度请求配置信息获得上行共享信道资源，以发送RLC状态报告和RRC恢复完成消息，以完成终端的连接恢复。从而避免终端在连接恢复过程中发起不必要的随机接入，实现降低终端功耗，提高终端性能，以达到终端快速恢复连接的目的。
图9为本申请实施例提供的另一种无线通信方法流程示意图。该方法可以由终端执行，或者由终端内部的芯片执行。如图9所示，该方法包括：
可选的，901：终端接收来自无线网络设备的RRC释放消息，该RRC释放消息包括挂起配置字段，该RRC释放消息用于指示挂起RRC连接。
可选的，902：终端挂起该RRC连接，由RRC连接态进入RRC非激活态。
可选的，903：终端发送RRC恢复请求消息，该RRC恢复请求消息用于请求恢复该RRC连接。
可选的，904：终端接收来自无线网络设备的RRC恢复消息，该RRC恢复消息不包括全量配置字段，该RRC恢复消息用于恢复所述RRC连接。
可选的，905：终端向无线网络设备发送随机接入前导码(RA preamble)，发起随机接入过程。
在905中，终端在特定资源单元(resource element，RE)上向无线网络设备发送随机接入前导码，由此发起随机接入过程。具体过程可参见图5。终端在特定RE上向无线网络设备发送随机接入前导码，无线网络设备向终端反馈响应消息，终端再次向无线网络设备发送随机接入前导码，无线网络设备再次向终端反馈响应消息，如此反复，直至终端与无线网络设备之间建立起随机接入或者被终止。
906：终端终止向无线网络设备发起的随机接入过程。
在906中，为了降低随机接入过程所带来的时延，可以提前终止之前发起的随机接入过程。可选的，终端在与无线网络设备建立随机接入的过程中，终端可以接收无线网络设备发送的随机接入响应之后，丢弃该随机接入响应，并停止向无线网络设备发送随机接入前导码，从而终止向无线网络设备发起随机接入过程。
可选的，终端在与无线网络设备建立随机接入的过程中，终端可以直接停止向无线网络设备发送随机接入前导码，从而终止向无线网络设备发起随机接入过程。
907：终端根据该RRC恢复消息，恢复该RRC连接，恢复该RRC连接包括由RRC非激活态进入RRC连接态。
908：终端确定调度请求配置信息。
909：终端向无线网络设备发送RLC状态报告。
910：终端向无线网络设备发送RRC恢复完成消息。
其中，所述RRC恢复完成消息用于确认所述RRC连接恢复的成功完成。
应理解，本申请中的901至910的细节可以参考图6至图8相关表述。这里不再 重复赘述。
在本申请实施例中，针对连接恢复的场景，终端在接收到来自无线网络设备的RRC恢复消息之后，确认当前是否存在调度请求配置信息之前，若已发起随机接入过程，可终止该随机接入过程，并在确认存在调度请求配置信息的情况下，基于该调度请求配置信息获得上行共享信道资源，以发送RLC状态报告和RRC恢复完成消息，以完成终端的连接恢复。从而避免终端在连接恢复过程中发起不必要的随机接入，降低终端等待时延，实现降低终端功耗，提高终端性能，以达到终端快速恢复连接的目的。
基于上述本申请实施例公开的无线通信方法，相应地，本申请实施例还公开了几种无线通信装置。该装置可以为UE。具体通过以下实施例进行说明。
图10为本申请实施例公开的一种无线通信装置的结构示意图。如图10所示，无线通信装置100主要包括：接收模块101、处理模块102以及发送模块103。
接收模块101，用于接收RRC恢复消息。
处理模块102，用于响应于RRC恢复消息，确定调度请求配置信息，其中，该调度请求配置信息用于获取上行共享信道资源。
发送模块103，用于通过上行共享信道资源，发送无线链路控制状态报告，其中，该无线链路控制状态报告用于提供无线链路控制业务数据单元的响应。
在具体实现中，
可选的，发送模块103，用于通过上行共享信道资源，发送RRC恢复完成消息，该RRC恢复完成消息用于确认RRC连接恢复的成功完成。
可选的，接收模块101，用于接收RRC释放消息，该RRC释放消息包括挂起配置字段，该RRC释放消息用于指示挂起RRC连接。
可选的，处理模块102，用于挂起RRC连接，由RRC连接态进入RRC非激活态。
可选的，发送模块103，用于发送RRC恢复请求消息，该RRC恢复请求消息用于请求恢复所述RRC连接。
可选的，接收模块101，用于接收RRC恢复消息，该RRC恢复消息不包括全量配置字段，该RRC恢复消息用于恢复该RRC连接。
可选的，处理模块102，用于根据RRC恢复消息，恢复RRC连接，恢复该RRC连接包括由RRC非激活态进入RRC连接态，根据RRC恢复消息，确定调度请求配置信息。
其中，调度请求配置信息用于获取上行共享信道资源。
可选的，发送模块103，用于通过上行共享信道资源，发送无线链路控制状态报告，该无线链路控制状态报告用于提供无线链路控制业务数据单元的响应
可选的，发送模块103，用于通过上行共享信道资源，发送RRC恢复完成消息，RRC恢复完成消息用于确认RRC连接恢复的成功完成。
在本申请实施例中，针对连接恢复的场景，终端在接收到来自无线网络设备的RRC恢复消息之后，确认当前存在调度请求配置信息，可以基于该调度请求配置信息获得上行共享信道资源，以发送RLC状态报告和RRC恢复完成消息，以完成终端的连接 恢复。从而避免终端在连接恢复过程中发起不必要的随机接入，实现降低终端功耗，提高终端性能，以达到终端快速恢复连接的目的。
在挂起RRC连接的情况下，在一些可能的实施方式中，该处理模块102，具体用于存储用户设备非激活态接入层上下文，挂起无线承载。
其中，无线承载包括除信令无线承载0以外的信令无线承载和数据无线承载。
在恢复所述RRC连接的情况下，在一些可能的实施方式中，该处理模块102，具体用于从用户设备非激活态接入层上下文中恢复主小区组，以及恢复所述无线承载。
在根据RRC恢复消息，确定调度请求配置信息的情况下，在一些可能的实施方式中，该处理模块102，具体用于根据主小区组，确定调度请求配置信息。
在一些可能的实施方式中，该处理模块102，还用于在根据RRC恢复消息，确定调度请求配置信息之后，根据调度请求配置信息发送调度请求信号，该调度请求信号由物理上行控制信道承载，所述调度请求信号用于请求上行共享信道资源。
相应地，该发送模块103，还用于通过上行共享信道资源，发送RRC恢复完成消息。
在一些可能的实施方式中，该发送模块103，还用于在接收模块101接收RRC恢复消息之后，随机接入前导码，使得发起随机接入过程。
相应地，处理模块102，还用于在根据RRC恢复消息，确定调度请求配置信息之前，终止随机接入过程。
在所述终止所述随机接入过程的情况下，在一些可能的实施方式中，处理模块102，具体用于在接收模块101接收随机接入响应消息之后，丢弃随机接入响应消息，并控制发送模块103停止发送随机接入前导码。
在所述终止所述随机接入过程的情况下，在一些可能的实施方式中，处理模块102，具体用于直接控制发送模块103停止发送随机接入前导码。
结合上述本申请实施例图2公开新无线协议栈的分层结构示意图，上述本申请实施例公开的无线通信装置中的接收模块，例如，发送模块和处理模块的功能可以利用图2中示出的部署于UE中的RRC层和RLC层实现。
此外，本申请实施例还提供了一种通信系统，该通信系统包括无线网络设备，以及上述本申请实施例图10公开无线通信装置。
结合本申请实施例公开的无线通信方法，本申请实施例所公开的适用于该无线通信方法的装置，也可以直接用硬件、处理器执行的存储器，或者二者的结合来实施。也可以是终端上的中的处理器、控制器或者芯片。
图11为本申请实施例公开的另一种无线通信装置的结构示意图。如图11所示，该无线通信装置包括：存储器111以及与存储器通信的处理器112和通信接口113。其中，通信接口113也可以称为接口电路。
该处理器112通过总线与存储器111耦合。处理器112通过总线与该通信接口113耦合。
存储器111具体可以是内容寻址存储器(content-addressable memory，CAM)或者随机存取存储器(random-access memory，RAM)。CAM可以是三态内容寻址存储器 (ternary cam，TCAM)。
处理器112具体可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，专用集成电路(application-specific integrated circuit，ASIC)或者可编程逻辑器件(programmable logic device，PLD)。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)或者通用阵列逻辑(generic array logic，GAL)。
通信接口113可以是有线接口，例如光纤分布式数据接口(fiber distributed data interface，FDDI)或者以太网(ethernet)接口。
存储器111也可以集成在处理器112中。如果存储器111和处理器112是相互独立的器件，存储器111和处理器112相连。
例如存储器111和处理器112可以通过总线通信。通信接口113和处理器112可以通过总线通信，通信接口113也可以与处理器112直接连接。
存储器111，用于存储无线通信方法程序指令。
可选的，该存储器111包括操作系统和应用程序，用于承载上述本申请实施例公开的无线通信方法的操作程序、代码或指令。
当处理器112或硬件设备要进行上述本申请实施例公开的无线通信方法的相关操作时，调用并执行存储器111中存储的操作程序、代码或指令可以完成上述本申请实施例中涉及连接恢复方法的过程。
具体过程为：处理器112调用存储器111中的无线通信方法程序代码，执行如图6、图7、图9所述的方法，例如：
接收RRC释放消息，挂起该RRC连接，由RRC连接态进入RRC非激活态，发送RRC恢复请求消息，接收RRC恢复消息，根据该RRC恢复消息，恢复RRC连接，由RRC非激活态进入RRC连接态，根据RRC恢复消息，确定调度请求配置信息，发送RRC恢复完成消息。
可以理解的是，上述图6、图7、图9所示的无线通信方法实施例所涉及到的接收/发送等操作可以是指在由处理器实现的接收/发送处理，也可以是指通过接收器和发射器完成的发送/接收过程，接收器和发射器可以独立存在，也可以集成为收发器。
在上述实施例中，可全部或部分地通过软件、硬件、固件、或其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如软盘、硬盘、磁带)、光介质 (例如光盘)、或者半导体介质(例如固态硬盘)等。在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序。其中，该计算机程序被相关硬件执行，以完成执行本发明实施例提供的任意一种无线通信方法。
此外，本申请实施例还提供一种用户设备。该用户设备包括上述本申请实施例公开的任一无线通信装置。其中，当该终端在运行时，使得该终端执行本申请实施例提供的任意一种无线通信方法。
在上述实施例中对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
综上所述，在本申请实施例中，针对连接恢复的场景，在终端确认当前存在调度请求配置信息的情况下，可以基于该调度请求配置信息获得上行共享信道资源，以发送RLC状态报告和RRC恢复完成消息，以完成终端的连接恢复。从而避免终端在连接恢复过程中发起不必要的随机接入，实现降低等待时延，降低终端功耗，提高终端性能，以达到终端快速恢复连接的目的。
最后应说明的是：以上实施例仅用以示例性说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请及本申请带来的有益效果进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请权利要求的范围。

Claims (16)

  1. 一种无线通信方法，其特征在于，包括：
    接收无线资源控制RRC恢复消息；
    响应于所述RRC恢复消息，确定调度请求配置信息，其中，所述调度请求配置信息用于获取上行共享信道资源；
    通过所述上行共享信道资源，发送无线链路控制状态报告，所述无线链路控制状态报告用于提供无线链路控制业务数据单元的肯定响应。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于所述RRC恢复消息，确定调度请求配置信息，包括：
    响应于所述RRC恢复消息，恢复RRC连接，其中，所述恢复RRC连接包括：从存储的用户设备非激活态接入层上下文中恢复主小区组；
    根据所述主小区组，确定调度请求配置信息。
  3. 根据权利要求1所述的方法，其特征在于，所述响应于所述RRC恢复消息，确定调度请求配置信息，包括：
    根据所述RRC恢复消息，确定调度请求配置信息。
  4. 根据权利要求1至3任一所述的方法，其特征在于，还包括：
    通过所述上行共享信道资源，发送RRC恢复完成消息，所述RRC恢复完成消息用于确认所述RRC连接恢复的成功完成。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述调度请求配置信息包括：调度请求标识以及调度请求资源标识。
  6. 一种无线通信装置，其特征在于，包括：
    接收模块，处理模块以及发送模块；
    所述接收模块，用于接收无线资源控制RRC恢复消息；
    所述处理模块，还用于响应于所述RRC恢复消息，确定调度请求配置信息，其中，所述调度请求配置信息用于获取上行共享信道资源；
    所述发送模块，用于通过所述上行共享信道资源，发送无线链路控制状态报告，所述无线链路控制状态报告用于提供无线链路控制业务数据单元的肯定响应。
  7. 根据权利要求6所述的无线通信装置，其特征在于，所述处理模块，用于响应于所述RRC恢复消息，确定调度请求配置信息，具体包括：
    所述处理模块，用于响应于所述RRC恢复消息，恢复RRC连接，其中，所述恢复RRC连接包括：从存储的用户设备非激活态接入层上下文中恢复主小区组；
    所述处理模块，还用于根据所述主小区组，确定调度请求配置信息。
  8. 根据权利要求6所述的无线通信装置，其特征在于，所述处理模块，用于响应于所述RRC恢复消息，确定调度请求配置信息，具体包括：
    所述处理模块，用于根据所述RRC恢复消息，确定调度请求配置信息。
  9. 根据权利要求6至8任一所述的无线通信装置，其特征在于，所述发送单元，还用于通过所述上行共享信道资源，发送RRC恢复完成消息，所述RRC恢复完成消 息用于确认所述RRC连接恢复的成功完成。
  10. 根据权利要求6至9任一所述的无线通信装置，其特征在于，所述调度请求配置信息包括：调度请求标识以及调度请求资源标识。
  11. 一种无线通信装置，其特征在于，包括：相互耦合的处理器和存储器；
    所述存储器，用于存储用于无线资源控制RRC连接恢复的程序指令；
    所述处理器，用于运行所述存储器存储的用于所述无线通信方法的程序指令，其中，所述连接恢复的程序指令运行时执行如权利要求1至5中任一所述的无线资源控制RRC连接恢复的方法。
  12. 一种无线通信装置，其特征在于，包括：处理器以及接口电路，接口电路用于从存储器中读取计算机程序，所述处理器用于执行所述计算机程序，以执行权利要求1至5任一项所述的方法。
  13. 一种用户设备，其特征在于，所述用户设备包括权利要求6至12任一所述的无线通信装置。
  14. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行权利要求1至5任一项所述的方法。
  15. 一种计算机程序产品，其特征在于，所述计算机程序产品包含计算机指令，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求1至5任一项所述的方法。
  16. 一种通信系统，其特征在于，所述通信系统包括无线网络设备，以及权利要求6至12任一项所述的装置。
PCT/CN2019/105386 2019-09-11 2019-09-11 无线通信方法、装置及系统 WO2021046758A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2019/105386 WO2021046758A1 (zh) 2019-09-11 2019-09-11 无线通信方法、装置及系统
EP19945286.3A EP4024950A4 (en) 2019-09-11 2019-09-11 RADIO COMMUNICATION METHOD, APPARATUS AND SYSTEM
CN201980006481.8A CN112789892B (zh) 2019-09-11 2019-09-11 无线通信方法、装置及系统
US17/691,636 US20220201791A1 (en) 2019-09-11 2022-03-10 Wireless communication method and apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/105386 WO2021046758A1 (zh) 2019-09-11 2019-09-11 无线通信方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/691,636 Continuation US20220201791A1 (en) 2019-09-11 2022-03-10 Wireless communication method and apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021046758A1 true WO2021046758A1 (zh) 2021-03-18

Family

ID=74867161

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105386 WO2021046758A1 (zh) 2019-09-11 2019-09-11 无线通信方法、装置及系统

Country Status (4)

Country Link
US (1) US20220201791A1 (zh)
EP (1) EP4024950A4 (zh)
CN (1) CN112789892B (zh)
WO (1) WO2021046758A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210274525A1 (en) * 2020-02-27 2021-09-02 FG Innovation Company Limited User equipment and method for small data transmission
US11818621B2 (en) * 2020-04-09 2023-11-14 Qualcomm Incorporated Handling of listen before talk failures during radio resource control procedures

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080069053A1 (en) * 2006-09-20 2008-03-20 Samsung Electronics Co., Ltd. Handover method and apparatus in a mobile communication system
CN103428786A (zh) * 2012-05-14 2013-12-04 上海贝尔股份有限公司 一种获得上行传输信息的方法及设备
CN107006056A (zh) * 2014-12-05 2017-08-01 诺基亚技术有限公司 用于具有突发性交互式业务的用户设备的延迟减少
WO2018201898A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 资源调度方法及设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3132555B1 (en) * 2014-04-15 2020-01-01 Telefonaktiebolaget LM Ericsson (publ) Uplink based selection of downlink connectivity configuration
PL3582551T3 (pl) * 2015-02-06 2021-12-06 Huawei Technologies Co., Ltd. Sposób i urządzenie do optymalizacji sygnalizacji
US20190104553A1 (en) * 2017-09-29 2019-04-04 Media Tek Inc. High Reliability and Early Data Transmission
CN109756991B (zh) * 2017-11-06 2021-11-19 华为技术有限公司 通信方法及装置
US10849181B2 (en) * 2018-01-11 2020-11-24 Apple Inc. NR RRC connection setup optimisation
EP3512272A1 (en) * 2018-01-12 2019-07-17 Panasonic Intellectual Property Corporation of America User equipment and base station supporting network slices and participating in paging procedure and connection setup

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080069053A1 (en) * 2006-09-20 2008-03-20 Samsung Electronics Co., Ltd. Handover method and apparatus in a mobile communication system
CN103428786A (zh) * 2012-05-14 2013-12-04 上海贝尔股份有限公司 一种获得上行传输信息的方法及设备
CN107006056A (zh) * 2014-12-05 2017-08-01 诺基亚技术有限公司 用于具有突发性交互式业务的用户设备的延迟减少
WO2018201898A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 资源调度方法及设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Connection control TP", 3GPP DRAFT; R2-1808961 - TP ON NR RRC CONNECTION CONTROL BASED ON DRAFT TS38331 V15.1.0_V0-RAN2-101BIS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, Korea; 20180521 - 20180525, 25 May 2018 (2018-05-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051520312 *
3GPP TS38.322
See also references of EP4024950A4

Also Published As

Publication number Publication date
CN112789892B (zh) 2022-04-22
CN112789892A (zh) 2021-05-11
EP4024950A4 (en) 2022-09-28
US20220201791A1 (en) 2022-06-23
EP4024950A1 (en) 2022-07-06

Similar Documents

Publication Publication Date Title
AU2019207029B2 (en) Communication method, communications device, and communications system
CN109565896B (zh) 低功率rrc操作方法和装置
WO2018019001A1 (zh) 一种终端状态转换方法及装置
WO2019153517A1 (zh) 无线链路失败处理方法及相关产品
WO2018014661A1 (zh) 一种数据或者信令发送、传输方法及装置
US11310855B2 (en) Methods and systems for managing bearer configuration of user equipment with EN-DC capability
WO2022205381A1 (zh) 广播多播业务传输方法、装置及存储介质
US20220201791A1 (en) Wireless communication method and apparatus, and system
CA3106045A1 (en) Control method for user equipment, and user equipment
TW201831031A (zh) 處理無線通訊系統中狀態不匹配的裝置及方法
TWI670954B (zh) 處理承載型態改變的裝置
US20230143942A1 (en) Managing a ue preferred configuration
WO2017118012A1 (zh) 一种数据传输方法、装置及系统
WO2020088305A1 (zh) 一种通信方法、通信装置及系统
CN113747478A (zh) 通信方法及装置
WO2021062797A1 (zh) 配置方法和装置
WO2017133679A1 (zh) Nas承载数据的传输方法及装置
KR20210042328A (ko) 데이터 무선 베어러 복원 방법 및 장치, 저장 매체, 전자 장치
KR20230107216A (ko) 뉴 라디오에서 통합 액세스 백홀 네트워크를 향상시키기 위한 방법 및 디바이스
WO2020088091A1 (zh) 状态上报、消息接收方法及装置、存储介质、电子装置
JP2024517912A (ja) ユーザ装置、及びユーザ装置の方法
WO2022252133A1 (zh) 一种安全激活失败后的恢复方法和装置
WO2023236061A1 (zh) 一种失败恢复方法及其装置
US20230337304A1 (en) Resuming multi-radio dual connectivity
WO2022032672A1 (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: 19945286

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019945286

Country of ref document: EP

Effective date: 20220331