Event processing method and device

Abstract

An event processing method and device, relating to the field of communications, are used to prevent network equipment from misunderstanding the occurrence of a first event or a second event. The event processing method comprises: determining first indication information, wherein the first indication information is used to indicate a random access RA triggered by a first event or a second event, the first event refers to the number of transmissions of a scheduling request SR reaching the maximum number of SR transmissions, and the second event refers to the absence of available physical uplink control channel PUCCH resources for a triggered and suspended SR; and sending the first indication information.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to an event processing method and device. Background Art

[0002] In a communication system, such as a new radio (NR) communication system, data of different service types can be carried through different logical channels (LCH), and one or more LCHs can be associated with a logical channel group (LCG). Each LCH can be associated with a scheduling priority, which can be configured by a network device. High-priority services (such as ultra-reliable and lowlatency communications (URLLC) services) can be configured with LCHs with high scheduling priorities, and low-priority services (such as enhanced mobile broadband (eMBB) services) can be configured with LCHs with low scheduling priorities.

[0003] When the terminal device has new uplink data, uplink resource allocation can be prioritized according to high-priority services. When the terminal device has new uplink data and any LCH contained in all LCGs has no uplink data to be sent, or a higher-priority LCH has uplink data to be sent, the terminal device can trigger a buffer status report (BSR) to reflect the amount of data to be sent by at least one LCG, so that the network device can schedule according to the amount of data to be sent.

[0004] Before sending control signaling to indicate uplink resources, the network device may not know that the terminal device has uplink data to send. Therefore, the terminal device must first request the network device to allocate uplink resources through pre-configured or public uplink resources. For example, the terminal device can send a scheduling request (SR) on the physical uplink control channel (PUCCH) resource to request uplink resources, or send a random access (RA) on the physical random access channel (PRACH) to request uplink resources. Among them, after the terminal device triggers the SR, it enters the pending state to wait for the SR transmission occasion to send the SR.

[0005] Case 1: When the terminal device triggers SR and there are available PUCCH resources, when SR fails because the maximum number of transmissions is reached (which can be called the first event), the terminal device triggers RA and releases uplink resources. Case 2: When the terminal device triggers SR but there are no available PUCCH resources (which can be called the second event), the terminal device triggers RA and cancels the suspended SR. The RA in both cases can include BSR to indicate the amount of data to be sent by at least one LCG. The network device determines whether the RA is triggered by the first event or the second event based on the amount of data to be sent by each LCG in the BSR and the known uplink resource configuration, and then determines different processing methods for uplink resources.

[0006] When the BSR indicates that only one LCG has a non-zero amount of data to be sent, the network device can determine the service type corresponding to the LCG and the uplink resource configuration to determine whether the RA is triggered by the first event or the second event. However, when the BSR indicates that the amount of data to be sent by two or more LCGs is not zero, the network device will not be able to determine which LCG's corresponding service type triggers the RA, and will not be able to determine whether the RA is triggered by the first event or the second event based on the uplink resource configuration. If the network device misunderstands the occurrence of the first event or the second event, it will use the wrong processing method for the uplink resources, wasting air interface signaling overhead or affecting system performance. Summary of the invention

[0007] The embodiments of the present application provide an event processing method and apparatus for preventing a network device from misunderstanding the occurrence of a first event or a second event.

[0008] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0009] In a first aspect, an event processing method is provided, comprising: determining first indication information, wherein the first indication information is used to indicate a random access RA triggered by a first event or a second event, the first event refers to the number of transmissions of a scheduling request SR reaching a maximum number of SR transmissions, and the second event refers to the absence of available physical uplink control channel PUCCH resources for a triggered and suspended SR; and sending the first indication information.

[0010] In the event processing method provided in the embodiment of the present application, the terminal device sends a first indication information to the network device, and the first indication information is used to indicate the RA triggered by the first event or the second event, so as to prevent the network device from misunderstanding the occurrence of the first event or the second event, adopting an incorrect processing method for uplink resources, wasting air interface signaling overhead or affecting system performance.

[0011] In a possible implementation manner, the first indication information is indicated by an information element IE or a cause value of a radio resource control RRC message. In this implementation manner, the first indication information is indicated by the RRC layer.

[0012] In a possible implementation, the first indication information includes second indication information indicating the arrival of high priority data or third indication information indicating the arrival of low priority data, and the second indication information or the third indication information is used to determine the first event or the second event. This implementation implicitly indicates the first indication information.

[0013] In a possible implementation manner, the first indication information is indicated by a logical channel identifier LCID, a reserved bit or a load in a media access control element MAC CE. In this implementation manner, the first indication information is indicated by a MAC layer.

[0014] In a possible implementation, when the first indication information is indicated by the LCID, or when the first indication information is indicated by the load in the MAC CE, the first indication information is also used to indicate that the load in the MAC CE is the first cell radio network temporary identifier C-RNTI. This implementation reuses the first indication information and can also be used to indicate the C-RNTI.

[0015] In a possible implementation, the first indication information is indicated by a BSR in the RA, wherein, among the amounts of data to be sent of all logical channel groups of the BSR, when the RA is triggered by the first event, the amount of data to be sent of the LCG corresponding to at least one logical channel without available PUCCH resources is set to 0; or, when the RA is triggered by the second event, the amount of data to be sent of the LCG corresponding to at least one LCH with available PUCCH resources is set to 0. This implementation forces the amount of data to be sent of the LCG that is not triggered by the first event or the second event to be set to 0, so that the network device can determine the RA triggered by the first event or the second event according to the BSR.

[0016] In a possible implementation manner, the first indication information is indicated through different random access channel RACH resources. In this implementation manner, the first indication information is indicated through a physical layer.

[0017] In a possible implementation manner, the first indication information is indicated by uplink control information UCI in the PUCCH resource. In this implementation manner, the first indication information is indicated by UCI.

[0018] According to a second aspect, an event processing method is provided, comprising: receiving first indication information, wherein the first indication information is used to indicate a random access RA triggered by a first event or a second event, the first event refers to the number of transmissions of a scheduling request SR reaching a maximum number of SR transmissions, and the second event refers to the absence of available physical uplink control channel PUCCH resources for a triggered and suspended SR; and a RA triggered by the first event or the second event according to the first indication information.

[0019] In a possible implementation manner, the first indication information is indicated by an information element IE or a cause value of a radio resource control RRC message.

[0020] In a possible implementation, the first indication information includes second indication information indicating the arrival of high priority data or third indication information indicating the arrival of low priority data, and the second indication information or the third indication information is used to determine the first event or the second event.

[0021] In a possible implementation manner, the first indication information is indicated by a logical channel identifier LCID, a reserved bit, or a load in a media access control control element MAC CE.

[0022] In a possible implementation, when the first indication information is indicated by the LCID, or when the first indication information is indicated by the load in the MAC CE, the first indication information is also used to indicate that the load in the MAC CE is the first cell radio network temporary identifier C-RNTI.

[0023] In a possible implementation, the first indication information is indicated by the BSR in the RA, wherein, among the amount of data to be sent of all logical channel groups of the BSR, when the RA is triggered by the first event, the amount of data to be sent of the LCG corresponding to at least one logical channel without available PUCCH resources is set to 0; or, when the RA is triggered by the second event, the amount of data to be sent of the LCG corresponding to at least one LCH with available PUCCH resources is set to 0.

[0024] In a possible implementation manner, the first indication information is indicated by using different random access channel RACH resources.

[0025] In a possible implementation manner, the first indication information is indicated by uplink control information UCI in the PUCCH resource.

[0026] The technical effect of this implementation refers to the first aspect and any of its implementation methods.

[0027] According to a third aspect, an event handling method is provided, including: determining first indication information, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to the number of uplink listen-before-talk (LBT) failures reaching a maximum preset number; and sending the first indication information.

[0028] In the event processing method provided in the embodiment of the present application, the terminal device sends a first indication message to the network device, the first indication message is used to indicate the cell where the first event occurs, and the first event refers to the number of uplink LBT failures reaching a maximum preset number, so that the network device is informed of the cell where the first event occurs.

[0029] In a possible implementation manner, the method further includes: sending second indication information, where the second indication information is used to indicate the bandwidth part BWP where the first event occurs. This implementation manner may also indicate the BWP where the first event occurs.

[0030] In a possible implementation manner, the first indication information is indicated by a media access control control element MAC CE. In this implementation manner, the first indication convenience store is indicated by a MAC layer.

[0031] In a possible implementation manner, the first indication information is an identifier of a cell where the first event occurs. In this implementation manner, the first indication information is indicated in an explicit manner.

[0032] In a possible implementation manner, the first indication information is a bitmap, and the cell where the first event occurs corresponds to a bit in the bitmap. This implementation manner indicates the first indication information in an implicit manner.

[0033] In a possible implementation manner, the method further includes: determining not to send data through the uplink authorization of the cell where the first event occurs or the BWP where the first event occurs.

[0034] In a fourth aspect, an event handling method is provided, including: receiving first indication information, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to the number of uplink listen-before-talk (LBT) failures reaching a maximum preset number; determining the cell where the first event occurs based on the first indication information.

[0035] In a possible implementation manner, the method further includes: receiving second indication information, where the second indication information is used to indicate the bandwidth part BWP where the first event occurs.

[0036] In a possible implementation manner, the first indication information is indicated by a media access control control element MAC CE.

[0037] In a possible implementation manner, the first indication information is an identifier of a cell where the first event occurs.

[0038] In a possible implementation manner, the first indication information is a bitmap, and the cell where the first event occurs corresponds to a bit in the bitmap.

[0039] In a possible implementation, it further includes:

[0040] Determine not to receive data from the uplink grant of the cell where the first event occurs or the BWP where the first event occurs.

[0041] The technical effect of this implementation refers to the third aspect and any of its implementation methods.

[0042] In the fifth aspect, an event processing method is provided, including: determining a first event, wherein the first event refers to the number of transmissions of a first scheduling request SR reaching the maximum number of SR transmissions, and the first SR is carried on a first physical uplink control channel PUCCH resource; sending a second SR on a second PUCCH resource, wherein the cell to which the second PUCCH resource belongs and the cell to which the first PUCCH resource belongs belong to different time advance groups TAGs, or the cell to which the second PUCCH resource belongs and the primary service cell belong to different TAGs.

[0043] The event processing method provided in the embodiment of the present application is that when the terminal device determines that a first event occurs on a first PUCCH resource, a second SR is sent on a second PUCCH resource, which can avoid the RA triggered by the first event and allow the RA triggered by the second event, thereby preventing the network device from misunderstanding the occurrence of the first event or the second event, and adopting an incorrect processing method for the uplink resources, thereby wasting air interface signaling overhead or affecting system performance.

[0044] In a possible implementation, the method further includes: releasing uplink resources of at least one serving cell belonging to a first TAG and / or configuring downlink resource allocation, where the first TAG refers to a TAG of a cell to which the first PUCCH resource belongs.

[0045] In the sixth aspect, an event processing method is provided, including: determining whether a first event or a second event triggers a random access RA, wherein the first event refers to the number of transmissions of a scheduling request SR reaching the maximum number of SR transmissions, and the second event refers to the fact that there are no available physical uplink control channel PUCCH resources for the triggered and suspended SR; when the first event triggers the RA, the suspended SR that triggered the first event is canceled, and the uplink resources of all service cells and / or the downlink resource allocation is not released; when the second event triggers the RA, the suspended SR that triggered the second event is canceled after the RA is completed.

[0046] The event processing method provided in the embodiment of the present application cancels the suspended SR that triggers the first event when the first event triggers the RA, and does not release the uplink resources of all service cells and / or configure the downlink resource allocation, so that the SR triggered by the second event still has the opportunity to be transmitted, and will not be canceled due to the RA triggered by the first event. When the second event triggers the RA, the suspended SR that triggers the second event is canceled after the RA is completed, so as to avoid the RA triggered by the second event being interrupted by other RAs, thereby giving the RA triggered by the second event more transmission opportunities. By optimizing the cancellation of the SR when the RA is triggered by the first event or the second event, it is prevented that the RAs triggered by the concurrent first event or the second event affect each other, and it is also possible to prevent the services of other cells where the first event has not occurred from being affected.

[0047] In a possible implementation, the method further includes: when the first event triggers the RA, releasing uplink resources of at least one serving cell belonging to a first timing advance group TAG and / or configuring downlink resource allocation, wherein the first TAG refers to the TAG of the cell corresponding to the logical channel LCH that triggers the first event. This implementation may not affect the TAG of the cell corresponding to the LCH that does not trigger the first event.

[0048] In the seventh aspect, a communication device is provided, comprising a processing module and a transceiver module, the processing module being used to control the transceiver module to execute the method as described in the first aspect and any one of its embodiments, as well as the method as described in the third aspect and any one of its embodiments, as well as the method as described in the fifth aspect and any one of its embodiments, and as described in the sixth aspect and any one of its embodiments.

[0049] In an eighth aspect, a communication device is provided, comprising a processing module and a transceiver module, wherein the processing module is used to control the transceiver module to execute the method described in the second aspect and any embodiment thereof, and the method described in the fourth aspect and any embodiment thereof.

[0050] In a ninth aspect, a communication device is provided, comprising a processor, a memory and a transceiver, wherein the processor is coupled to the memory, and when the processor executes a computer program or instruction in the memory, the method as described in the first aspect and any embodiment thereof, as well as the method as described in the third aspect and any embodiment thereof, as well as the method as described in the fifth aspect and any embodiment thereof, and as described in the sixth aspect and any embodiment thereof is performed.

[0051] In the tenth aspect, a communication device is provided, comprising a processor, a memory and a transceiver, wherein the processor is coupled to the memory, and when the processor executes a computer program or instruction in the memory, the method described in the second aspect and any embodiment thereof, and the method described in the fourth aspect and any embodiment thereof are performed.

[0052] In the eleventh aspect, a chip is provided, comprising: a processor and an interface, for calling and running a computer program stored in a memory from the memory, and executing the method as described in the first aspect to the sixth aspect and any one of them.

[0053] In the twelfth aspect, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed on a computer or a processor, the computer or the processor executes the method as described in the first to sixth aspects and any one of them.

[0054] In the thirteenth aspect, a computer program product comprising instructions is provided, which, when executed on a computer or a processor, enables the computer or the processor to execute the method as described in the first to sixth aspects and any one of the aspects.

[0055] The technical effects of the seventh to thirteenth aspects can refer to the contents of various possible implementation methods of the first to sixth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0057] Figure 2 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0058] Figure 3 A schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0059] Figure 4 A flowchart of a four-step random access process provided in an embodiment of the present application;

[0060] Figure 5 A schematic diagram of the format of a RAR message provided in an embodiment of the present application;

[0061] Figure 6 A schematic diagram of an event processing method provided in an embodiment of the present application Figure 1 ;

[0062] Figure 7 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 1 ;

[0063] Figure 8 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 2 ;

[0064] Fig. 9 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 3 ;

[0065] Fig.10 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 4 ;

[0066] Fig.11 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 5 ;

[0067] Fig.12 A schematic diagram of the structure of a MAC CE provided in an embodiment of the present application Figure 6 ;

[0068] Fig.13 A schematic diagram of an event processing method provided in an embodiment of the present application Figure 2 ;

[0069] Fig.14 A schematic diagram of an event processing method provided in an embodiment of the present application Figure 3 ;

[0070] Fig.15 A schematic diagram of an event processing method provided in an embodiment of the present application Figure 4 ;

[0071] Fig.16 A schematic diagram of a MAC CE load structure provided in an embodiment of the present application Figure 1 ;

[0072] Fig.17 A schematic diagram of a MAC CE load structure provided in an embodiment of the present application Figure 2 ;

[0073] Fig.18 A schematic diagram of a MAC CE load structure provided in an embodiment of the present application Figure 3 ;

[0074] Fig.19 A schematic diagram of a MAC CE load structure provided in an embodiment of the present application Figure 4 ;

[0075] Fig. 20 A schematic diagram of a communication device provided in an embodiment of the present application Figure 1 ;

[0076] Fig.21 A schematic diagram of a communication device provided in an embodiment of the present application Figure 2 . DETAILED DESCRIPTION

[0077] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0078] The embodiments of the present application can be applied to both time division duplexing (TDD) scenarios and frequency division duplexing (FDD) scenarios.

[0079] The embodiments of the present application can be applied to both licensed spectrum systems and unlicensed spectrum systems, such as licensed-assisted access (LAA), new radio-based access to unlicensed spectrum (NRU), etc.

[0080] The embodiments of the present application can be applied to universal mobile telecommunications systems (UMTS), code division multiple access (CDMA) systems, wireless local area networks (WLAN) or future fifth generation (5G) wireless communication systems, such as new radio (NR) systems, new radio access technology (new radio access technology) evolved LTE (evolved LTE, eLTE), etc., wherein the access network equipment of eLTE can be connected to the core network of LTE and the core network of future 5G at the same time.

[0081] The embodiments of the present application are described based on the scenario of a 5G network in a wireless communication network. It should be noted that the solutions in the embodiments of the present application can also be applied to other wireless communication networks, and the corresponding names can also be replaced by the names of corresponding functions in other wireless communication networks.

[0082] like Figure 1 As shown, the communication system 100 provided in the embodiment of the present application includes a network device 101 and terminal devices 102-107.

[0083] The terminal device involved in the embodiments of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. A wireless terminal may communicate with one or more core networks via a radio access network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, user equipment (UE), personal communication service (PCS) phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) and other devices. A wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment. For example, the terminal device may be a high-speed rail communication device 102, an intelligent air conditioner 103, an intelligent gas station 104, a mobile phone 105, an intelligent tea cup 106, a printer 107, etc., which is not limited in this application.

[0084] In an embodiment of the present application, a network device may refer to a device in an access network that is connected to a terminal device through a sector on an air interface. The network device may be used to convert received air frames to Internet Protocol (IP) packets, as a router between the terminal device and the rest of the access network, wherein the rest of the access network may include an IP network. The network device may also coordinate the attribute management of the air interface. For example, the base station may be an evolutionary node B (eNB or e-NodeB) in LTE, or a gNB in ​​5G, a transmission and reception point (TRP), a centralized unit (CU), a distributed unit (DU), etc., which are not limited in the embodiment of the present application. The above base stations are only examples, and the network device may also be a relay station, an access point, a vehicle-mounted device, a wearable device, and other types of devices.

[0085] like Figure 2 As shown, taking the terminal device as a mobile phone as an example, the structure of the terminal device is explained.

[0086] The terminal device 105 may include: a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a wireless fidelity (Wi-Fi) module 170, a processor 180, a Bluetooth module 181, and a power supply 190 and other components.

[0087] The RF circuit 110 can be used to receive and send signals during the process of sending and receiving information or making calls. It can receive downlink data from the base station and hand it over to the processor 180 for processing; it can send uplink data to the base station. Generally, the RF circuit includes but is not limited to antennas, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer and other devices.

[0088] The memory 120 can be used to store software programs and data. The processor 180 executes various functions and data processing of the terminal device 105 by running the software programs or data stored in the memory 120. The memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. The memory 120 stores an operating system that enables the terminal device 105 to run, such as the operating system developed by Apple Inc. Operating system, developed by Google Open source operating system developed by Microsoft Operating system, etc. In the present application, the memory 120 can store an operating system and various application programs, and can also store codes for executing the method of the embodiment of the present application.

[0089] The input unit 130 (e.g., a touch screen) may be used to receive input digital or character information and generate signal inputs related to user settings and function control of the terminal device 105. Specifically, the input unit 130 may include a touch screen 131 disposed on the front of the terminal device 105, which may collect user touch operations on or near it.

[0090] The display unit 140 (i.e., display screen) can be used to display information input by the user or information provided to the user and a graphical user interface (GUI) of various menus of the terminal device 105. The display unit 140 may include a display screen 141 disposed on the front of the terminal device 105. Among them, the display screen 141 can be configured in the form of a liquid crystal display, a light emitting diode, etc. The display unit 140 can be used to display various graphical user interfaces described in this application. The touch screen 131 can be covered on the display screen 141, or the touch screen 131 can be integrated with the display screen 141 to realize the input and output functions of the terminal device 105, and the integration can be referred to as a touch display screen.

[0091] The terminal device 105 may further include at least one sensor 150, such as a light sensor, a motion sensor, or other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor.

[0092] The audio circuit 160, the speaker 161, and the microphone 162 can provide an audio interface between the user and the terminal device 105. The audio circuit 160 can transmit the electrical signal converted from the received audio data to the speaker 161, which is converted into a sound signal for output; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, and then the audio data is output to the RF circuit 110 to be sent to, for example, another terminal, or the audio data is output to the memory 120 for further processing.

[0093] Wi-Fi is a short-range wireless transmission technology. The terminal device 105 can help users send and receive emails, browse web pages, and access streaming media through the Wi-Fi module 170, which provides users with wireless broadband Internet access.

[0094] The processor 180 is the control center of the terminal device 105. It uses various interfaces and lines to connect various parts of the entire terminal. It executes various functions of the terminal device 105 and processes data by running or executing software programs stored in the memory 120 and calling data stored in the memory 120. In this application, the processor 180 may refer to one or more processors, and the processor 180 may include one or more processing units; the processor 180 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the baseband processor mainly processes wireless communications. It can be understood that the above-mentioned baseband processor may not be integrated into the processor 180. In this application, the processor 180 can execute the method involved in the embodiment of the present application.

[0095] The Bluetooth module 181 is used to exchange information with other Bluetooth devices having Bluetooth modules through the Bluetooth protocol. For example, the terminal device 105 can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 181 to exchange data.

[0096] The terminal device 105 also includes a power supply 190 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 180 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption.

[0097] like Figure 3 As shown, an embodiment of the present application provides a structural schematic diagram of a network device. The network device 300 may include one or more radio frequency units, such as a remote radio unit (RRU) 310 and one or more baseband units (BBU) (also referred to as a digital unit (DU)) 320. The RRU 310 may be referred to as a transceiver unit. Optionally, the transceiver unit 310 may also be referred to as a transceiver, a transceiver circuit, a transceiver, a transmitter and a receiver, etc., and may include at least one antenna 311 and an RF circuit 312. Optionally, the transceiver unit 310 may include a receiving unit and a sending unit, the receiving unit may correspond to a receiver (or a receiver, a receiving circuit), and the sending unit may correspond to a transmitter (or a transmitter, a transmitting circuit). The RRU 310 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals, for example, for sending indication information to a terminal device. The BBU 320 part is mainly used for baseband processing, controlling network devices, etc. The RRU 310 and the BBU 320 may be physically arranged together or physically separated, that is, a distributed base station.

[0098] The BBU 320 is the control center of the network device, which may also be called a processing unit, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU 320 may be used to control the network device to execute the method involved in the present application.

[0099] In one example, the BBU 320 may be composed of one or more single boards, and multiple single boards may jointly support a wireless access network of a single access standard (such as an LTE network), or may respectively support wireless access networks of different access standards (such as an LTE network, a 5G network, or other networks). The BBU 320 also includes a memory 322 and a processor 321. The memory 322 is used to store necessary instructions and data. The processor 321 is used to control the network device to perform necessary actions, such as controlling the network device to execute the method involved in this application. The processor 321 in this application may refer to one or more processors. The memory 322 and the processor 321 may serve one or more single boards. In other words, a memory and a processor may be separately set on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be set on each single board.

[0100] In addition, the network equipment is not limited to the above-mentioned forms, but may also be in other forms: for example, including a BBU and an adaptive radio unit (ARU), or a BBU and an active antenna unit (AAU); it may also be customer premises equipment (CPE), or it may be in other forms, which are not limited in the present application.

[0101] First, some concepts involved in this application are described.

[0102] Scheduling request (SR):

[0103] As mentioned above, data of different service types in the NR system can be carried through different LCHs, different service types can be carried through different logical channels, and one or more LCHs can be associated with an LCG. Each LCH can be associated with a scheduling priority, which can be configured by the network device. High-priority services (such as URLLC) can be configured with LCHs with high scheduling priorities, and low-priority services (such as eMBB) can be configured with LCHs with low scheduling priorities.

[0104] When the terminal device has new uplink data, uplink resource allocation can be prioritized according to high-priority services. When the terminal device has new uplink data and any LCH contained in all LCGs has no uplink data to be sent, or a higher-priority LCH has uplink data to be sent, the terminal device can trigger a BSR to reflect the amount of data to be sent by at least one LCG, so that the network device can schedule according to the amount of data to be sent.

[0105] However, before the network device sends control signaling to indicate uplink resources, it may not know that the terminal device has uplink data to send. Therefore, when the terminal device triggers the BSR and there are no available uplink resources for data transmission, the terminal device must first request the network device to allocate uplink resources through pre-configured or public uplink resources. For example, the terminal device can transmit SR on the PUCCH resources to request uplink resources, or it can transmit RA on the PRACH to request uplink resources.

[0106] The above-mentioned PUCCH resources are periodic resources. The network equipment will configure the frequency domain resource information and time domain resource information (such as the start time information and period, etc.) of the PUCCH resources. After the terminal equipment obtains the above-mentioned frequency domain resource information and time domain resource information, it can determine the periodic SR transmission occasion. After the terminal equipment triggers the SR, it enters the pending state to wait for the SR transmission occasion to transmit the SR.

[0107] Binding of SR and services:

[0108] In the NR system, the network device can indicate one or more SR configurations to the terminal device. Each SR configuration includes PUCCH resources available for SR. These PUCCH resources can be distributed in different cells, or in bandwidth parts (BWP) at different frequency domain locations in the same cell.

[0109] For the LCH of the terminal device used to carry data of various service types, each LCH can be associated with 0 or 1 SR configuration, and each BWP of each LCH can be configured with 0 or 1 PUCCH resources. When there are no available PUCCH resources, or when the priority of the service type is low, or when the data arrival period of the service type is long, in order to save air interface resources, the network device can choose not to indicate the SR configuration to the LCH carrying the data of the service type, that is, not to configure PUCCH resources.

[0110] Exemplary, assumption 1: Assume that the terminal device has logical channel LCH#4 and logical channel LCH#5. Logical channel LCH#4 belongs to logical channel group LCG#1, and logical channel LCH#4 is used to carry data of eMBB services, but the network device does not indicate SR configuration for logical channel LCH#4, then logical channel LCH#4 has no PUCCH resources available for SR. In addition, assuming that logical channel LCH#5 belongs to logical channel group LCG#2, and logical channel LCH#5 is used to carry data of URLLC services, and the network device indicates SR configuration (PUCCH resource #2) for logical channel LCH#5, then logical channel LCH#5 has PUCCH resources available for SR (PUCCH resource #2).

[0111] When data of different service types arrives, the terminal device can determine whether there is a corresponding SR configuration according to the LCH corresponding to the data of the service type, and perform SR according to the SR configuration, so that the network device can know the service type of the data to be sent by the terminal device.

[0112] Exemplarily, according to the assumptions described above, when the terminal device has data for a URLLC service to be sent, the terminal device can determine that the PUCCH resource available for the SR is PUCCH resource #2 through the SR configuration of the logical channel LCH #5, that is, the SR can be transmitted through PUCCH resource #2. After the network device detects the SR on PUCCH resource #2, it can be learned that the service type of the data to be sent by the terminal device is a URLLC service, so that uplink resources suitable for the URLLC service can be scheduled, such as scheduling uplink resources with a shorter duration, or scheduling more reliable uplink resources, thereby meeting the transmission requirements of the URLLC service, namely low latency and high reliability.

[0113] SR sending mechanism - first event and second event:

[0114] When the terminal device triggers SR and there are available PUCCH resources, SR can be transmitted on the PUCCH resources, and the count value of the SR counter (SR Counter) will be iteratively increased by 1 each time SR is transmitted.

[0115] When the number of SR transmissions (the count value of the SR counter) does not reach the maximum number of SR transmissions (SR TransMax) configured by the radio resource control (RFC), the medium access control (MAC) entity of the terminal device will perform the following actions:

[0116] ——The count value of the SR counter will be iteratively increased by 1.

[0117] - Notify the physical layer to transmit SR on the PUCCH resources available for SR. Start the SR prohibit timer.

[0118] When the first event occurs (the number of SR transmissions (the count value of the SR counter) reaches the maximum number of SR transmissions (SR TransMax) configured by the radio resource control (RRC)), this situation is also called SR failure. The MAC entity of the terminal device performs the following actions:

[0119] ——Notify RRC to release PUCCH resources of all serving cells.

[0120] ——Notify RRC to release the sounding reference signal (SRS) of all serving cells.

[0121] ——Clear the physical uplink shared channel (PUSCH) resources used for semi-persistent channel state information (SP-CSI) reporting.

[0122] ——Clear all configured uplink grants (CG).

[0123] ——Clear all configured downlink assignments (CDA).

[0124] ——Trigger RA and cancel all pending SRs.

[0125] When the second event occurs (no PUCCH resources are available for a triggered and pending SR), the MAC entity of the terminal device performs the following actions:

[0126] ——Trigger RA, cancel the pending SR that triggered the second event.

[0127] Random access (RA):

[0128] In LTE, a terminal device can achieve the following goals through RA: obtain uplink synchronization and obtain a unique cell radio network temporary identifier (C-RNTI). In LTE, RA is usually triggered by one of the following six events: Figure 6-Figure 14 That is, it revolves around the first and second events in the fifth category of events:

[0129] The first type of event is establishing a wireless connection during initial access.

[0130] The second type of event: RRC connection reestablishment process.

[0131] The third type of event: switching process.

[0132] In the fourth event, in the RRC connected (RRC_CONNECTED) state, when downlink data arrives, the uplink is in an out-of-sync state.

[0133] The fifth type of event, in the RRC connected (RRC_CONNECTED) state, when uplink data arrives, the uplink is in a state of desynchronization, causing the number of SR transmissions (the count value of the SR counter) to reach the maximum number of SR transmissions (i.e., the first event), or, for the SR that has been triggered and is in a suspended state, there are no available PUCCH resources (i.e., the second event).

[0134] The sixth type of event, in the RRC connected (RRC_CONNECTED) state, locates the terminal device.

[0135] In the NR system, system information (SI) includes the minimum system information (MSI) and other system information (OSI) for the terminal device to access the network. MSI is broadcast periodically by the network, while OSI is triggered by the network side or by the request of the terminal device. That is, in the NR system, requesting OSI can also trigger the random access process.

[0136] In addition, the NR system can also support beamforming technology, that is, the sender weights the uplink and downlink signals to form a narrow beam aimed at the receiver, and aligns the transmission energy to the receiver, thereby improving the demodulation signal-to-noise ratio of the receiver, thereby improving the system coverage and transmission success rate. When the channel quality of the current service beam deteriorates, beam failure recovery (BFR) can also be requested through the random access process.

[0137] RA includes contention based RA (CBRA) and non-contention based RA (NCBRA or CFRA).

[0138] Take the four-step CBRA of the NR system as an example. Figure 4 As shown, the four-step random access process between the terminal device and the network device is as follows:

[0139] S401. The terminal device sends a random access preamble.

[0140] This message may be referred to as message 1 (MSG1) for short, and its function is to inform the network device that there is a random access request and enable the network device to estimate the transmission delay between itself and the terminal device so as to calibrate the uplink timing.

[0141] The random access preamble is transmitted on the physical random access channel (PRACH). The network device can inform the terminal device of the PRACH time-frequency resource set that can be used to transmit the random access preamble in the current cell through a system message. When initiating RA, for CBRA, the terminal device can select the PRACH resource to transmit the random access preamble by itself. For CFRA, the terminal device can use the PRACH resource specified by the network device to transmit the random access preamble.

[0142] Each cell has 64 available random access preambles. When initiating RA, for CBRA, the terminal device can select the random access preamble by itself. For CFRA, the terminal device can use the random access preamble specified by the network device.

[0143] S402. The network device sends a random access response (RA response, RAR) message corresponding to the received random access preamble.

[0144] This message can be referred to as message 2 (MSG 2). Figure 5 The figure shows a format of a RAR message. The RAR message is carried in a MAC control element (CE). The MAC CE includes a MAC header and at least one MAC RAR.

[0145] The MAC header includes the E / T / RAPID MAC subheader, where E represents the extension field, indicating whether there is a subsequent MAC subheader, 1 represents a subsequent MAC subheader, and 0 represents no MAC subheader. T represents the type field, indicating whether the following data is a backoff indication (BI) or a random access preamble identifier (RAPID).

[0146] In MAC RAR, R represents a reserved bit. The timing advance command (TAC) occupies 11 bits and is used to indicate the timing advance (TA) for uplink synchronization of the terminal device, that is, the transmission delay between the network device and the terminal device. The uplink grant (UL grant) information occupies 20 bits and is used to indicate the resources for the terminal device to subsequently transmit message 3 (MSG 3), including parameters such as time-frequency position, frequency hopping, and power control. The temporary C-RNTI occupies 16 bits and is used for scrambling when the terminal device subsequently transmits MSG3.

[0147] For CBRA, after receiving the RAR message, the terminal device determines whether the identifier of the random access preamble therein is the same as the random access preamble sent in step S401. If they are the same, it is considered that the RAR message is received successfully. Otherwise, it is considered that the RAR message is received unsuccessfully and the terminal device can re-initiate RA.

[0148] For CFRA, since the random access preamble is dedicated to the terminal device, there is no conflict; and since the terminal device already has a unique identifier C-RNTI in the access cell, the network device does not need to allocate C-RNTI. Therefore, only CBRA requires steps S403 and S404.

[0149] S403: The terminal device sends uplink data.

[0150] The terminal device sends uplink data through a physical uplink shared channel (PUSCH) on the corresponding uplink transmission resource according to the uplink grant information of the RAR message. This message can be referred to as message 3 (MSG3).

[0151] The uplink data may include RRC messages and identification information of the terminal device, such as C-RNTI, resume ID or inactive RNTI (I-RNTI). The resume ID or I-RNTI is assigned to the terminal device by the network side, and the terminal device reports the ID for the network device to identify the terminal device and related context information. The RRC message can be sent to the network device after completing the processing of each layer of the protocol stack through the signaling radio bearer (SRB).

[0152] S404: The network device sends a conflict resolution message.

[0153] This message may be referred to as message 4 (MSG 4). Since the terminal device sent the identification information of the terminal device in step S403, the network device will carry the identification information of the terminal device in step S404 in the conflict resolution mechanism to specify the terminal device that won the conflict elimination, and other UEs that did not win the conflict elimination will re-initiate RA.

[0154] After the terminal device completes the random access process, for the terminal device in the idle (IDLE) state, after completing a series of processes such as air interface security activation, it obtains the data bearer required for data transmission and establishes the corresponding configuration before it can communicate data with the network device. For the terminal device in the inactive (INACTIVE) state or the connected (CONNECTED) state, it can communicate data with the network device after the random access process is successful.

[0155] It should be noted that the NR system also introduces a two-step random access process, that is, the terminal device merges step S401 and step S403, and carries the contents of the original MSG 1 (optional) and MSG 3 through message A (MSG A), and the network device merges step S402 and step S404, and carries the contents of the original MSG 2 and MSG 4 through message B (MSG B).

[0156] UL LBT failure:

[0157] In an unlicensed spectrum cell, the terminal device needs to perform the LBT process before data transmission. LBT is a channel access mechanism that enables wireless LANs to effectively share the same spectrum resources. Because the availability of channels in unlicensed frequency bands cannot be guaranteed at all times, LBT requires monitoring the channel before data transmission, performing idle channel assessment, and then performing data transmission when the channel is guaranteed to be idle.

[0158] If LBT succeeds, the data transmission can proceed. If LBT fails, the data transmission is abandoned and resources are needed for retransmission.

[0159] The NR system introduces a mechanism for uplink LBT failure. For example, the terminal device uses a timer and a counter to detect whether an uplink LBT failure occurs. Specifically, each time an uplink LBT failure is determined, the counter is iteratively incremented by 1 and the timer is started. When the timer times out, the counter is reset. If the number of uplink LBT failures (the count value of the counter) reaches the maximum preset number, it is determined that the third event has occurred.

[0160] Buffer status report (BSR)

[0161] In the above-mentioned step S403, when there are remaining resources after the identification information of the terminal device carried in message 3 (MSG 3), the MAC CE of BSR may also be included in message 3 to indicate the amount of data to be sent by the LCG of the terminal device.

[0162] Exemplary assumption 2: Assume that the BSR contains the amount of data to be sent of the logical channel group LCG#1 and the amount of data to be sent of the logical channel group LCG#2 mentioned above, wherein the logical channel group LCG#1 includes the logical channel LCH#4 for carrying data of eMBB services, and the logical channel group LCG#2 includes the logical channel LCH#5 for carrying data of URLLC services.

[0163] According to the assumption 1 mentioned above, the network device does not indicate SR configuration for logical channel LCH#4, so logical channel LCH#4 has no PUCCH resources available for SR. The network device indicates SR configuration (PUCCH resource #2) for logical channel LCH#5, so logical channel LCH#5 has PUCCH resources available for SR (PUCCH resource #2). The values ​​of the amount of data to be sent for logical channel group LCG#1 and the amount of data to be sent for logical channel group LCG#2 in the BSR are as follows:

[0164] Case 1: The amount of data to be sent of logical channel group LCG#1 is not 0, while the amount of data to be sent of logical channel group LCG#2 is 0. This indicates that the logical channel LCH#4 used to carry the data of the eMBB service has data to be transmitted, but because the network device does not indicate SR configuration for the logical channel LCH#4 (there are no available PUCCH resources, that is, the second event has occurred), the terminal device requests uplink resources through RA. At this time, the network device does not need to reconfigure resources such as PUCCH, sounding reference signal (SRS), and configured uplink grant (CG).

[0165] Case 2: The amount of data to be sent of logical channel group LCG#2 is not 0, while the amount of data to be sent of logical channel group LCG#1 is 0. This indicates that the logical channel LCH#5 used to carry data of the URLLC service has data to be transmitted, but because the number of SR transmissions has reached the maximum number of SR transmissions (that is, the first event has occurred), the terminal device requests uplink resources through RA. At this time, the network device needs to reconfigure resources such as PUCCH, SRS, and CG.

[0166] Case 3: The amount of data to be sent of logical channel group LCG#1 and the amount of data to be sent of logical channel group LCG#2 are not 0. At this time, the network device cannot determine whether the random access process is triggered by the first event or the second event, because it may be triggered by the first event, but eMBB service data must be sent before sending the message (MSG 3); or, it may be triggered by the second event, but URLLC service data must be sent before sending message 3 (MSG3).

[0167] Case 4: Due to the limitation of the remaining resource size, message 3 (MSG 3) cannot carry the MAC CE of the long BSR, nor is it enough to carry the MAC CE of the truncated BSR, that is, it cannot carry the BSR MAC CE. At this time, since the BSR has not been transmitted, the network device cannot determine whether the subsequent BSR to be transmitted still indicates that there is data for other services to be sent based on the existing BSR. Therefore, the network device cannot determine whether the random access process is triggered by the first event or the second event.

[0168] From the above situations three and four, the network device cannot determine whether the random access process is triggered by the first event or the second event. If the RA is triggered by the first event, the network device will reconfigure PUCCH, SRS, CG and other resources. If the RA is triggered by the second event, the network device does not need to reconfigure PUCCH, SRS, CG and other resources. Therefore, when the RA is actually triggered by the second event, and the network device understands it as a RA triggered by the first event, it will still reconfigure PUCCH, SRS, CG and other resources, wasting air interface signaling overhead. When the RA is actually triggered by the first event, and the network device understands it as a RA triggered by the second event, the network device cannot reconfigure PUCCH, SRS, CG and other resources in time, causing the terminal device to be unable to reacquire the above resources in time and execute related processes, affecting system performance.

[0169] The embodiment of the present application provides an event processing method, when a first event or a second event occurs, the terminal device sends a first indication information to the network device, the first indication information indicates the RA triggered by the first event or the second event, and specifically, the terminal device can send the first indication information through the RRC layer, the MAC layer and the physical layer. This solves the problem that the network device misunderstands the occurrence of the first event or the second event, resulting in waste of air interface signaling overhead, or the terminal device cannot timely reacquire the above resources, thereby affecting system performance.

[0170] Specifically, Figure 6 As shown, an event processing method provided in an embodiment of the present application includes:

[0171] S601. The terminal device determines first indication information.

[0172] The first indication information is used to indicate the RA triggered by the first event or the second event.

[0173] As mentioned above, the first event refers to that the number of SR transmissions (the count value of the SR counter) reaches the maximum number of SR transmissions. The second event refers to that there is no available PUCCH resource for the triggered and suspended SR.

[0174] Optionally, in another description, the first event may also be described as an RA event that triggers reconfiguration of at least one of the following resources, and the second event may also be described as an RA event that does not require reconfiguration of at least one of the following resources. The at least one resource includes:

[0175] PUCCH resources - PUCCH resources of at least one serving cell including this cell.

[0176] SRS resources - SRS resources of at least one serving cell including this cell.

[0177] PUSCH resources used for SP-CSI reporting - PUSCH resources used for SP-CSI reporting of at least one serving cell including this cell.

[0178] Configured uplink grant (CG) - CG resources of at least one serving cell including this cell.

[0179] Configured downlink assignment (CDA) - CDA resources of at least one serving cell including this cell.

[0180] Optionally, when the first event occurs, the terminal device may release the at least one resource.

[0181] Optionally, when the first event occurs, the terminal device may cancel all pending SRs.

[0182] Optionally, when the second event occurs, the terminal device may cancel the suspended SR that triggers the second event, but may not cancel all suspended SRs.

[0183] S602: The terminal device sends first indication information.

[0184] Correspondingly, the network device receives the first indication information.

[0185] The first indication information may be carried in a first message, and the first message may be message 3 (MSG 3) in the above-mentioned four-step random access process or message B (MSG B) in the two-step random access process.

[0186] Optionally, the first message may also carry identification information of the terminal device, such as C-RNTI.

[0187] The first indication information can be indicated in the following ways:

[0188] For sending the first indication information through the RRC layer:

[0189] Optionally, in a possible implementation manner, the first indication information may be indicated by an information element (IE) or a cause value of an RRC message:

[0190] Exemplarily, taking the RRC establishment request message as an example, as shown in the structure of the RRC establishment request message below, an enumeration value can be added to the IE information element (RRCSetupRequest-IEs) of the RRC establishment request message as the first indication information, and different values ​​of the enumeration value respectively indicate the RA triggered by the first event or the second event. Alternatively, a cause value can be added to the establishment cause (EstablishmentCause) information element as the first indication information, and different values ​​of the cause value respectively indicate the RA triggered by the first event or the second event.

[0191] The following is a structure of an RRC establishment request message:

[0192]

[0193]

[0194] In another possible implementation, the first indication information may include second indication information or third indication information, and the second indication information or the third indication information is used to determine the RA triggered by the first event or the second event. The third indication information is used to indicate the arrival of high priority data (e.g., URLLC type data), and the fourth indication information is used to indicate the arrival of low priority data (e.g., eMBB type data). Alternatively, the third indication information is used to indicate the arrival of low priority data (e.g., eMBB type data), and the fourth indication information is used to indicate the arrival of high priority data (e.g., URLLC type data).

[0195] The network device may determine the RA triggered by the first event or the second event in combination with the second indication information or the third indication information and other information, such as the BSR.

[0196] Optionally, the network device can configure the arrival of high-priority data or low-priority data. For example, the network device can configure the arrival of data on the logical channel LCH#4 as low-priority data through an RRC message, and configure the arrival of data on the logical channel LCH#5 as high-priority data through an RRC message. Alternatively, the network device can configure the threshold value of the logical channel priority through an RRC message, and the arrival of data on the logical channel with a priority higher than the threshold value is high-priority data, and the arrival of data on the logical channel with a priority lower than the threshold value is low-priority data.

[0197] According to the assumption one described above: the network device does not indicate SR configuration for logical channel LCH#4, then logical channel LCH#4 has no PUCCH resources available for SR. The network device indicates SR configuration (PUCCH resource #2) for logical channel LCH#5, then logical channel LCH#5 has PUCCH resources available for SR (PUCCH resource #2). In case three: the amount of data to be sent in logical channel group LCG#1 and the amount of data to be sent in logical channel group LCG#2 are not 0. If the second indication information indicates the arrival of high priority data, the network device can determine the RA triggered by the first event; if the third indication information indicates the arrival of low priority data, the network device can determine the RA triggered by the second event. This implementation method implicitly indicates the first indication information.

[0198] Exemplarily, taking the RRC establishment request message as an example, as shown in the structure of the RRC establishment request message below, an enumeration value can be added to the IE information element (RRCSetupRequest-IEs) of the RRC establishment request message as the first indication information, and different values ​​of the enumeration value respectively indicate the second indication information or the third indication information. Alternatively, a cause value can be added to the establishment cause (EstablishmentCause) information element as the first indication information, and different values ​​of the cause value respectively indicate the second indication information or the third indication information.

[0199] The following is a structure of an RRC establishment request message:

[0200]

[0201] For sending the first indication information through the MAC layer:

[0202] In a possible implementation, Figure 7As shown, it is a schematic diagram of the structure of a MAC CE, wherein the MAC CE includes a MAC CE subheader and a payload, and the MAC CE subheader includes a reserved bit (R) and a logical channel identification (LCID). The first indication information can be indicated by the LCID, the reserved bit R or the payload in the MAC CE.

[0203] Optionally, when the first indication information is indicated by LCID, two different values ​​of LCID can be used to indicate the RA triggered by the first event or the second event. Figure 8 As shown in Table 1, the value A of LCID can be two values ​​from 33 to 51 that are not currently used. For example, when the value A of LCID is 33, it indicates the RA triggered by the first event, and when the value A of LCID is 34, it indicates the RA triggered by the second event.

[0204] Optionally, the RA triggered by the first event or the second event can be indicated by whether there is first indication information in the MAC CE. For example, when there is no first indication information in the MAC CE, the first event is indicated, and when there is the first indication information, the second event is indicated; or, when there is first indication information in the MAC CE, the first event is indicated, and when there is no first indication information, the second event is indicated.

[0205] Optionally, when the first indication information is indicated by LCID, the RA triggered by the first event or the second event may be indicated according to whether the first message includes a preset MAC CE. For example, when the first message includes a preset MAC CE, the RA triggered by the first event is indicated; when the first message does not include a preset MAC CE, the RA triggered by the second event is indicated. Alternatively, when the first message includes a preset MAC CE, the RA triggered by the second event is indicated; when the first message does not include a preset MAC CE, the RA triggered by the first event is indicated. Fig. 9 As shown in Table 1, the preset MAC CE refers to a MAC CE including an LCID with a value of B. The value B may be a value from 33 to 51 which is not currently used.

[0206] Table 1

[0207]

[0208]

[0209] It should be noted that, when the first indication information is indicated through LCID, the MAC CE may only include the MAC subheader part but not the payload part.

[0210] Optionally, when the first indication information is indicated by the load in the MAC CE, the RA triggered by the first event or the second event may be indicated by two different values ​​of the load. Fig.10 As shown in Table 1, the value B of LCID can be a value from 33 to 51 which is not currently used. The value C of load can be any two values ​​within the range of numbers that can be represented by load.

[0211] Optionally, when the first indication information is indicated by LCID, or when the first indication information is indicated by a load in a MAC CE, the first indication information can also be used to indicate that the load in the MAC CE is the first C-RNTI.

[0212] like Fig.11 As shown in Table 2, the LCID value D can be a value from 33 to 51 that is not currently used, and the corresponding load is the first C-RNTI. The existing LCID value is 58 and the corresponding load is the second C-RNTI.

[0213] The network device can determine the RA triggered by the first event or the second event based on the LCID value of D or 58. For example, when the LCID value is D, it indicates the RA triggered by the first event, and when the LCID value is 58, it indicates the RA triggered by the second event; or, when the LCID value is D, it indicates the RA triggered by the second event, and when the LCID value is 58, it indicates the RA triggered by the first event.

[0214] Alternatively, the network device may also determine the RA triggered by the first event or the second event according to whether the load is the first C-RNTI or the second C-RNTI. For example, when the load is the first C-RNTI, the RA triggered by the first event is indicated, and when the load is the second C-RNTI, the RA triggered by the second event is indicated; or, when the load is the first C-RNTI, the RA triggered by the second event is indicated, and when the load is the second C-RNTI, the RA triggered by the first event is indicated.

[0215] Table 2

[0216]

[0217]

[0218] Optionally, when the first indication information is indicated by a reserved bit R, the RA triggered by the first event or the second event can be indicated according to different values ​​of one of the reserved bits. For example, when the value of one of the reserved bits is 0, it indicates the RA triggered by the first event, and when the reserved bit is 1, it indicates the RA triggered by the second event; or, when the value of the reserved bit is 1, it indicates the RA triggered by the first event, and when the reserved bit is 0, it indicates the RA triggered by the second event. The reserved bit can be the first reserved bit or the second reserved bit.

[0219] In addition, if Fig.12 As shown, when the first indication information is indicated by the reserved bit R, the LCID value can be 58, that is, the load can be C-RNTI.

[0220] It should be noted that two reserved bits can also be used to indicate RA triggered by the first event or the second event. For example, the two reserved bits are set to "01" to indicate RA triggered by the first event, and "10" to indicate RA triggered by the second event. This application does not limit this.

[0221] In another possible implementation, the first indication information may be indicated by a BSR in a RA, specifically, by a message 3 (MSG 3) in a four-step random access process, or by a message B (MSG B) in a two-step random access process.

[0222] Among the amounts of data to be sent of all LCGs of the BSR, when the RA is triggered by the first event, the amount of data to be sent of the LCG corresponding to at least one LCH without available PUCCH resources is set to 0. Alternatively, when the RA is triggered by the second event, the amount of data to be sent of the LCG corresponding to at least one LCH with available PUCCH resources is set to 0. That is, by forcibly setting the amount of data to be sent of the LCG corresponding to the LCH that does not trigger the RA to 0 and retaining the amount of data to be sent of the LCG corresponding to the LCH that triggers the RA, the network device can determine the RA triggered by the first event or the second event in combination with the uplink resource parameters configured for the corresponding LCH.

[0223] For sending the first indication information through the physical layer:

[0224] In another possible implementation, the first indication information may be indicated by different random access channel (RACH) resources. The terminal device selects different RACH resources to perform a random access process according to the first event or the second event that triggers the RA, thereby indicating the RA triggered by the first event or the second event.

[0225] The RACH resource may include at least one of the following resources:

[0226] Random access preamble - Different values ​​of the random access preamble can indicate the RA triggered by the first event or the second event. Optionally, the random access preamble can be divided into two groups, and the RA triggered by the first event or the second event can be indicated by the random access preambles belonging to different groups. For example, the random access preambles in the first group indicate the RA triggered by the first event, and the random access preambles in the second group indicate the RA triggered by the second event; or, the random access preambles in the first group indicate the RA triggered by the second event, and the random access preambles in the second group indicate the RA triggered by the first event.

[0227] RACH timeslots - RAs triggered by the first event or the second event can be indicated by different RACH timeslots.

[0228] In yet another possible implementation manner, the first indication information is indicated by uplink control information (uplink control information, UCI) in a PUCCH resource.

[0229] The network device may configure at least one PUCCH resource for the terminal device for transmitting the above-mentioned UCI.

[0230] Optionally, the RA triggered by the first event or the second event may be indicated according to different values ​​of UCI in the PUCCH resource. For example, when the UCI takes the first value, the RA triggered by the first event is indicated, and when the UCI takes the second value, the RA triggered by the second event is indicated; or, when the UCI takes the second value, the RA triggered by the first event is indicated, and when the UCI takes the first value, the RA triggered by the second event is indicated.

[0231] Optionally, the RA triggered by the first event or the second event may be indicated according to different resources occupied by UCI in the PUCCH resources. For example, when the UCI occupies the first resource in the PUCCH resources, the RA triggered by the first event is indicated, and when the UCI occupies the second resource in the PUCCH resources, the RA triggered by the second event is indicated; or, when the UCI occupies the second resource in the PUCCH resources, the RA triggered by the first event is indicated, and when the UCI occupies the first resource in the PUCCH resources, the RA triggered by the second event is indicated.

[0232] Optionally, the RA triggered by the first event or the second event may be indicated according to whether the UCI is present in the PUCCH resource. For example, when there is no UCI in the PUCCH resource, the RA triggered by the first event is indicated, and when there is UCI, the RA triggered by the second event is indicated; or, when there is UCI in the PUCCH resource, the RA triggered by the first event is indicated, and when there is no UCI, the RA triggered by the second event is indicated.

[0233] S603: The network device determines, according to the first indication information, an RA triggered by the first event or the second event.

[0234] The process of the network device determining the RA triggered by the first event or the second event according to the first indication information is the reverse process of how the terminal device indicates the first indication information in step S602, which will not be repeated here.

[0235] In the event processing method provided in the embodiment of the present application, the terminal device sends a first indication information to the network device, and the first indication information is used to indicate the RA triggered by the first event or the second event, so as to prevent the network device from misunderstanding the occurrence of the first event or the second event, adopting an incorrect processing method for uplink resources, wasting air interface signaling overhead or affecting system performance.

[0236] The embodiment of the present application provides another event processing method, in which the network device configures multiple PUCCH resources available for SR for the terminal device, and when the terminal device has a first event on the first PUCCH resource, the second PUCCH resource can be used to send the SR. The RA triggered by the first event can be avoided, and the RA triggered by the second event can be allowed, so as to prevent the network device from misunderstanding the occurrence of the first event or the second event, and adopting an incorrect processing method for the uplink resources, thereby wasting air interface signaling overhead or affecting system performance.

[0237] Specifically, Fig.13 As shown, an event processing method provided in an embodiment of the present application includes:

[0238] S1301. The terminal device determines a first event.

[0239] The first event refers to that the number of transmissions of the first SR reaches the maximum number of transmissions of the SR. The first SR is carried on the first PUCCH resource.

[0240] S1302. The terminal device sends a second SR on a second PUCCH resource.

[0241] Accordingly, the network device receives a second SR on a second PUCCH resource.

[0242] The timing advances of serving cells belonging to the same timing alignment group (TAG) are the same, and the timing advances of serving cells belonging to different TAGs may be different.

[0243] The cell to which the second PUCCH resource belongs and the cell to which the first PUCCH resource belongs may belong to different TAGs. For example, the first PUCCH resource is a PUCCH resource of at least one cell associated with TAG1, and the second PUCCH resource is a PUCCH resource of at least one cell associated with TAG2, and TAG1 and TAG2 are different TAGs.

[0244] Alternatively, the cell to which the second PUCCH resource belongs and the primary serving cell belong to a different TAG (eg, a secondary TAG).

[0245] If the terminal device fails to send SR in the cell to which the first PUCCH resource belongs or the primary service cell, it means that there is a problem with the uplink timing of the cell to which the first PUCCH resource belongs or the primary service cell, but it does not mean that there is a problem with the uplink timing of the cells in other TAGs. Therefore, you can try to send SR through the PUCCH resources of cells in other TAGs.

[0246] Optionally, the second PUCCH resource may be associated with one or more LCHs, or may not be associated with any LCH.

[0247] Optionally, when the first event occurs, the terminal device may release the uplink resources of at least one serving cell belonging to the first TAG and / or configure downlink resource allocation, where the first TAG refers to the TAG of the cell to which the first PUCCH resource belongs. Specifically, the uplink resources include at least one of the following resources: PUCCH resources, SRS resources, PUSCH resources for SP-CSI reporting, and configuration of uplink authorization. Configuring downlink resource allocation is often associated with semi-static scheduling. Among them:

[0248] PUCCH resources - including PUCCH resources of at least one serving cell associated with the first TAG corresponding to the first PUCCH resource. At this time, it is assumed that the first PUCCH resource and the second PUCCH resource belong to cells of different TAGs.

[0249] SRS resources—including SRS resources of at least one serving cell associated with the first TAG corresponding to the first PUCCH resource.

[0250] PUSCH resources used for SP-CSI reporting - including PUSCH resources of at least one serving cell associated with the first TAG corresponding to the first PUCCH resource.

[0251] Configure uplink grant—including configured uplink grant resources of at least one serving cell associated with the first TAG corresponding to the first PUCCH resource.

[0252] Configuring downlink resource allocation—including configuring downlink resource allocation of at least one serving cell associated with the first TAG corresponding to the first PUCCH resource.

[0253] The event processing method provided in the embodiment of the present application is that when the terminal device determines that a first event occurs on a first PUCCH resource, a second SR is sent on a second PUCCH resource, which can avoid the RA triggered by the first event and allow the RA triggered by the second event, thereby preventing the network device from misunderstanding the occurrence of the first event or the second event, and adopting an incorrect processing method for the uplink resources, thereby wasting air interface signaling overhead or affecting system performance.

[0254] The embodiment of the present application provides another event processing method, when the first event triggers RA, the suspended SR that triggers the first event is canceled. When the second event triggers RA, the suspended SR that triggers the second event is canceled after the RA is completed. Through the above optimization of canceling SR when the RA is triggered by the first event or the second event, it is prevented that the RAs triggered by the concurrent first event or the second event affect each other, and it is also prevented that the services of other cells where the first event does not occur are affected.

[0255] Specifically, Fig.14 As shown, an event processing method provided by an embodiment of the present application includes:

[0256] S1401. The terminal device determines that a first event or a second event triggers RA.

[0257] The first event refers to that the number of SR transmissions reaches the maximum number of SR transmissions. The second event refers to that there is no available PUCCH resource for the triggered and suspended SR.

[0258] S1402: When a first event triggers an RA, the SR in a suspended state that triggers the first event is canceled, and uplink resources of all serving cells are not released and / or downlink resource allocation is not configured.

[0259] Among them, the uplink resources include at least one of the following resources: PUCCH resources, SRS resources, PUSCH resources for SP-CSI reporting, and configuration of uplink grants. Configuring downlink resource allocation is often associated with semi-static scheduling. Among them:

[0260] PUCCH resources - PUCCH resources of at least one serving cell including this cell.

[0261] SRS resources - SRS resources of at least one serving cell including this cell.

[0262] PUSCH resources used for SP-CSI reporting - PUSCH resources used for SP-CSI reporting of at least one serving cell including this cell.

[0263] Configure uplink authorization - configure uplink authorization resources for at least one serving cell including this cell.

[0264] Configuring downlink resource allocation - configuring downlink resource allocation for at least one serving cell including the current cell.

[0265] Optionally, when the first event triggers RA, uplink resources of at least one serving cell belonging to the first timing advance group TAG are released and / or downlink resource allocation is configured, and the first TAG refers to the TAG of the cell corresponding to the LCH that triggers the first event.

[0266] In the prior art, when the first event triggers RA, all suspended SRs are canceled. In the present application, only the suspended SR that triggers the first event is canceled, so that the SR triggered by the second event still has a chance to be transmitted, and will not be canceled due to the RA triggered by the first event, so that the network equipment can obtain more information and perform better scheduling. In addition, the above resources of other cells where the first event did not occur are still valid, and data of high-priority (such as URLLC) services can be sent in time, avoiding the impact of the SR failure of the current cell on the transmission of other cells.

[0267] S1403: When the second event triggers RA, cancel the suspended SR that triggers the second event after RA is completed.

[0268] When the second event triggers RA, the terminal device may not cancel the suspended SR that triggers the second event, and cancel the suspended SR that triggers the second event after RA is completed, so as to avoid the RA triggered by the second event from being interrupted by other RAs, thereby giving the RA triggered by the second event more transmission opportunities.

[0269] The event processing method provided in the embodiment of the present application cancels the suspended SR that triggers the first event when the first event triggers the RA, and does not release the uplink resources of all service cells and / or configure the downlink resource allocation, so that the SR triggered by the second event still has the opportunity to be transmitted, and will not be canceled due to the RA triggered by the first event. When the second event triggers the RA, the suspended SR that triggers the second event is canceled after the RA is completed, so as to avoid the RA triggered by the second event being interrupted by other RAs, thereby giving the RA triggered by the second event more transmission opportunities. By optimizing the cancellation of the SR when the RA is triggered by the first event or the second event, it is prevented that the RAs triggered by the concurrent first event or the second event affect each other, and it is also possible to prevent the services of other cells where the first event has not occurred from being affected.

[0270] When a third event occurs in a cell or at least one BWP of a cell (i.e., the number of uplink LBT failures reaches the maximum preset number), RA is also triggered. The network device cannot determine whether the RA is triggered by the third event, and cannot determine the specific cell or BWP where the third event occurs. An embodiment of the present application provides another event processing method. When the third event triggers RA, the terminal device indicates to the network device the cell where the third event occurs, and further, can also indicate to the network device the BWP where the third event occurs.

[0271] like Fig.15 As shown, an event processing method provided in an embodiment of the present application includes:

[0272] S1501. The terminal device determines fourth indication information.

[0273] The fourth indication information is used to indicate the cell where the third event occurs, and the third event refers to the number of uplink LBT failures reaching a maximum preset number.

[0274] Optionally, the terminal device may also determine fifth indication information, where the fifth indication information is used to indicate the BWP at which the third event occurs.

[0275] A cell may correspond to one or more BWPs, and the cell may activate one of the BWPs. At this time, the terminal device indicates to the network device the cell where the third event occurs, which is equivalent to indicating the BWP where the third event occurs. If the cell activates multiple BWPs, at this time, in addition to indicating to the network device the cell where the third event occurs, the terminal device also indicates to the network device the BWP where the third event occurs, so that the network device can determine the BWP where the third event occurs.

[0276] S1502. The terminal device sends fourth indication information.

[0277] Correspondingly, the network device receives fourth indication information.

[0278] For example, if the third event occurs in the secondary cell (SCell), since the uplink condition of the primary cell (PCell) may be better, the terminal device can send the fourth indication information to the network device, thereby not triggering RA. This step can also be called the terminal device sending an uplink LBT failure (UL LBT failure) report.

[0279] Optionally, the fourth indication information may be indicated by a MAC CE. Specifically, the fourth indication information may be carried in the payload of the MAC CE or in the MAC CE subheader, which is not limited in this application. This application takes carrying in the payload of the MAC CE as an example, but is not intended to be limited thereto.

[0280] Optionally, the fourth indication information may be an identifier of a cell where the third event occurs. That is, the fourth indication information explicitly indicates the cell where the third event occurs. Fig.16 As shown, in a possible structure of the load of the MAC CE, a reserved bit R and an identifier of a cell where the third event occurs are included, and the identifier of the cell where the third event occurs is the fourth indication information.

[0281] Optionally, the fourth indication information may be a bitmap, and the cell where the first event occurs corresponds to a bit in the bitmap, so that the network device can determine the cell where the third event occurs according to the setting of the bit in the bitmap. Fig.17 As shown, in a possible structure of the load of the MAC CE, a reserved bit R and a bitmap are included, and the bitmap includes seven bits C1-C7, each bit corresponding to a cell. For example, by default, all bits in the bitmap are set to 0, and when one of the bits is set to 1, it indicates that the third event occurs in the corresponding cell, and the third event does not occur in the corresponding cell of the bit that is not set to 1. Alternatively, by default, all bits in the bitmap are set to 1, and when one of the bits is set to 0, it indicates that the third event occurs in the corresponding cell, and the third event does not occur in the corresponding cell of the bit that is not set to 0.

[0282] Optionally, the terminal device may further send fifth indication information. The fifth indication information may also be indicated by a MAC CE. Specifically, the fifth indication information may also be carried in a payload of a MAC CE or in a MAC CE subheader, which is not limited in this application. This application takes carrying in a payload of a MAC CE as an example, but is not intended to be limited thereto.

[0283] Optionally, the fifth indication information may be an identifier of the BWP where the third event occurs. That is, the fifth indication information explicitly indicates the BWP where the third event occurs. Fig.18 As shown, in a possible structure of the MAC CE load, a reserved bit R, an identifier of the BWP where the third event occurs, and an identifier of the cell where the third event occurs are included. Fig.19As shown in, in a possible structure of the load of MAC CE, the bit R, the identifier of the BWP where the third event occurs, and the bitmap corresponding to the fourth indication information are reserved. The identifiers of the BWPs can be arranged in ascending or descending order according to the positions of the cells to which they belong. For example, the BWP corresponding to the BWP identifier 7 belongs to the cell corresponding to the bit C7, the BWP corresponding to the BWP identifier 6 belongs to the cell corresponding to the bit C6, the BWP corresponding to the BWP identifier 5 belongs to the cell corresponding to the bit C5, the BWP corresponding to the BWP identifier 4 belongs to the cell corresponding to the bit C4, the BWP corresponding to the BWP identifier 3 belongs to the cell corresponding to the bit C3, the BWP corresponding to the BWP identifier 2 belongs to the cell corresponding to the bit C2, and the BWP corresponding to the BWP identifier 1 belongs to the cell corresponding to the bit C1. Alternatively, the BWP corresponding to BWP identifier 7 belongs to the cell corresponding to bit position C1, the BWP corresponding to BWP identifier 6 belongs to the cell corresponding to bit position C2, the BWP corresponding to BWP identifier 5 belongs to the cell corresponding to bit position C3, the BWP corresponding to BWP identifier 4 belongs to the cell corresponding to bit position C4, the BWP corresponding to BWP identifier 3 belongs to the cell corresponding to bit position C5, the BWP corresponding to BWP identifier 2 belongs to the cell corresponding to bit position C6, and the BWP corresponding to BWP identifier 1 belongs to the cell corresponding to bit position C7.

[0284] Optionally, after the third event occurs, the terminal device may perform at least one of the following operations in addition to sending the fourth indication information and the fifth indication information:

[0285] The transmission of at least one signaling radio bearer (SRB) and a data radio bearer (DRB) of the cell where the third event occurs is suspended.

[0286] The transmission of at least one SRB and DRB of the BWP where the third event occurs is suspended.

[0287] The cell where the third event occurs is deactivated.

[0288] Deactivate the BWP where the third event occurs.

[0289] Optionally, after the third event occurs, the terminal device may further perform at least one of the following operations:

[0290] It is determined not to transmit the UL-SCH through the cell where the third event occurs or the BWP where the third event occurs.

[0291] It is determined not to send the RA through the cell where the third event occurs or the BWP where the third event occurs.

[0292] It is determined not to send the PUCCH through the cell where the third event occurs or the BWP where the third event occurs.

[0293] It is determined not to send the SRS through the cell where the third event occurs or the BWP where the third event occurs.

[0294] It is determined not to send the CSI through the cell where the third event occurs or the BWP where the third event occurs.

[0295] Stop the SCell deactivation timer (SCell deactivation timer) of the cell where the third event occurs.

[0296] The BWP inactivitiy timer of the BWP where the third event occurs is stopped.

[0297] The configured uplink grant of the cell where the third event occurs or the BWP where the third event occurs is cleared.

[0298] Suspend the configured uplink grant of the cell where the third event occurs or the BWP where the third event occurs.

[0299] The BWP where the third event occurs is switched to the initial BWP or the default BWP, wherein the initial BWP refers to the BWP that the network device configures the terminal device to initiate initial access in the idle state or the inactive state through system messages. When the terminal device enters the connected state, the network device can configure a dedicated BWP for data communication, and the initial BWP and the dedicated BWP may be different. The default BWP refers to the BWP configured by the network device for the terminal device, which is used to switch from the dedicated BWP to the default BWP when the BWP inactivity timer (BWP inactivity timer) times out (i.e., no downlink control information (DCI) scheduled by the network device is received for a long time), so that the network device and the terminal device can complete the BWP alignment again, thereby performing data communication on the default BWP, and the default BWP and the dedicated BWP may be the same or different.

[0300] Optionally, the terminal device may also determine not to send data through the cell where the third event occurs or the uplink authorization of the BWP of the cell where the third event occurs. The data includes at least one of the following:

[0301] The MAC CE includes at least one of the following: a BSR MAC CE, a power headroom report (power headroom report, PHR) MAC CE, and an uplink failure (UL failure) MAC CE.

[0302] The SRB data includes at least one of the following: SRB0, SRB1, SRB2, and SRB3.

[0303] DRB data includes at least one of the following: all DRB data, high priority data, and DRB data corresponding to a specified LCH or LCG.

[0304] A control protocol data unit (PDU) includes at least one of the following: a service data adaptation protocol (SDAP) control PDU, a radio link control (RLC) status report or a packet data convergence protocol (PDCP) status report.

[0305] It should be noted that the network device can pre-configure whether the MAC CE, SRB, DRB or control PDU can be transmitted through the cell where the third event occurs. The terminal device can determine whether to send the MAC CE, SRB, DRB or control PDU on the cell where the third event occurs according to the configuration of the network device.

[0306] In addition, if the terminal device has available uplink transmission resources and the transmission resources can transmit MAC CE, the packetization process can be performed and the triggered uplink LBT failure can be canceled. The triggered uplink LBT failure includes the uplink LBT failure of one or more cells.

[0307] If the terminal has no available uplink transmission resources, the terminal device may send indication information to the network device to request the network device to allocate uplink transmission resources. This indication information may be a reuse SR or other indication information.

[0308] S1503. The network device determines a cell where a third event occurs according to the fourth indication information.

[0309] The process of the network device determining the cell where the third event occurs according to the fourth indication information is the reverse process of how the terminal device indicates the fourth indication information in step S1502, which will not be repeated here.

[0310] Optionally, the network device determines not to receive data from the uplink grant of the cell where the third event occurs or the BWP where the third event occurs.

[0311] In the event processing method provided in the embodiment of the present application, the terminal device sends a fourth indication information to the network device, and the fourth indication information is used to indicate the cell where the third event occurs, and the third event refers to the number of uplink LBT failures reaching a maximum preset number, so that the network device is informed of the cell where the third event occurs.

[0312] It can be understood that in the above embodiments, the methods and / or steps implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used for the terminal device, and the methods and / or steps implemented by the network device can also be implemented by components that can be used for the network device.

[0313] The above mainly introduces the scheme provided by the embodiment of the present application from the perspective of interaction between various network elements. Accordingly, the embodiment of the present application also provides a communication device, which is used to implement the above various methods. The communication device can be a terminal device in the above method embodiment, or a device including the above terminal device, or a chip or functional module in the terminal device; or, the communication device can be a network device in the above method embodiment, or a device including the above network device, or a chip or functional module in the network device. It can be understood that in order to implement the above functions, the communication device includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0314] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0315] For example, take the communication device as the terminal device in the above method embodiment. Fig. 202 shows a schematic diagram of the structure of a communication device 200. The communication device 200 includes a processing module 2001 and a transceiver module 2002. The communication device 200 can be Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The processing module 2001 may also be referred to as a processing unit, which is used to implement the processing function of the terminal device in the above method embodiment. Figure 6 Step S601 in Fig.13 In step S1301, Fig.14 Steps S1401-S1403 in Fig.15 The transceiver module 2002, which may also be referred to as a transceiver unit, is used to implement the transceiver function of the terminal device in the above method embodiment. Figure 4 Steps S401-S404 in Figure 6 In step S602, Fig.13 In step S1302, Fig.15 The transceiver module 2002 may be referred to as a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0316] Exemplarily, the processing module 2001 is used to determine the first indication information, wherein the first indication information is used to indicate the random access RA triggered by the first event or the second event, the first event refers to the number of transmissions of the scheduling request SR reaching the maximum number of SR transmissions, and the second event refers to the fact that there are no available physical uplink control channel PUCCH resources for the SR that has been triggered and is in a suspended state.

[0317] The transceiver module 2002 is used to send first indication information.

[0318] In a possible implementation manner, the first indication information is indicated by an information element IE or a cause value of a radio resource control RRC message.

[0319] In a possible implementation manner, the first indication information includes second indication information indicating the arrival of high priority data or third indication information indicating the arrival of low priority data, and the second indication information or the third indication information is used to determine the first event or the second event.

[0320] In a possible implementation manner, the first indication information is indicated by a logical channel identifier LCID, a reserved bit, or a load in a media access control control element MAC CE.

[0321] In a possible implementation, when the first indication information is indicated by LCID, or when the first indication information is indicated by a load in a MAC CE, the first indication information is also used to indicate that the load in the MAC CE is a first cell radio network temporary identifier C-RNTI.

[0322] In a possible implementation, the first indication information is indicated by the BSR in the RA, wherein, among the amount of data to be sent of all logical channel groups of the BSR, when the RA is triggered by the first event, the amount of data to be sent of the LCG corresponding to at least one logical channel without available PUCCH resources is set to 0; or, when the RA is triggered by the second event, the amount of data to be sent of the LCG corresponding to at least one LCH with available PUCCH resources is set to 0.

[0323] In a possible implementation manner, the first indication information is indicated by using different random access channel RACH resources.

[0324] In a possible implementation manner, the first indication information is indicated by uplink control information UCI in the PUCCH resource.

[0325] In addition, the processing module 2001 is further used to determine first indication information, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to the number of uplink listen-before-talk (LBT) failures reaching a maximum preset number.

[0326] The transceiver module 2002 is further configured to send first indication information.

[0327] In a possible implementation manner, the transceiver module 2002 is further configured to send second indication information, where the second indication information is used to indicate the bandwidth part BWP where the first event occurs.

[0328] In a possible implementation manner, the first indication information is indicated by a medium access control control element MAC CE.

[0329] In a possible implementation manner, the first indication information is an identifier of a cell where the first event occurs.

[0330] In a possible implementation manner, the first indication information is a bitmap, and the cell where the first event occurs corresponds to a bit in the bitmap.

[0331] In a possible implementation manner, the processing module 2001 is further configured to determine not to send data through the uplink authorization of the cell where the first event occurs or the BWP where the first event occurs.

[0332] In addition, the processing module 2001 is further used to determine a first event, wherein the first event refers to that the number of transmissions of the first scheduling request SR reaches the maximum number of SR transmissions, and the first SR is carried on the first physical uplink control channel PUCCH resource.

[0333] The transceiver module 2002 is further configured to send a second SR on a second PUCCH resource, wherein the cell to which the second PUCCH resource belongs and the cell to which the first PUCCH resource belongs belong to different timing advance groups TAGs, or the cell to which the second PUCCH resource belongs and the primary serving cell belong to different TAGs.

[0334] In a possible implementation, the processing module 2001 is further configured to release uplink resources of at least one serving cell belonging to a first TAG and / or configure downlink resource allocation, where the first TAG refers to a TAG of a cell to which the first PUCCH resource belongs.

[0335] In addition, the processing module 2001 is also used to determine whether a first event or a second event triggers a random access RA, wherein the first event refers to that the number of transmissions of the scheduling request SR reaches the maximum number of SR transmissions, and the second event refers to that for the triggered and suspended SR, there are no available physical uplink control channel PUCCH resources.

[0336] The processing module 2001 is further configured to, when the first event triggers the RA, cancel the SR in the suspended state that triggers the first event, and not release the uplink resources of all serving cells and / or configure downlink resource allocation.

[0337] The processing module 2001 is further configured to, when the second event triggers the RA, cancel the suspended SR that triggers the second event after the RA is completed.

[0338] In a possible implementation, the processing module 2001 is also used to release uplink resources of at least one service cell belonging to the first timing advance group TAG and / or configure downlink resource allocation when the first event triggers RA. The first TAG refers to the TAG of the cell corresponding to the logical channel LCH that triggers the first event.

[0339] In this embodiment, the communication device 200 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to a specific ASIC, a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 200 can be used Figure 2 The form of the terminal device 105 is shown.

[0340] for example, Figure 2The processor 180 in the terminal device 105 shown can call the computer execution instructions stored in the memory 120 to enable the terminal device 105 to execute the method in the above method embodiment.

[0341] Specifically, Fig. 20 The function / implementation process of the processing module 2001 in Figure 2 The processor 180 in the terminal device 105 shown calls the computer execution instructions stored in the memory 120 to implement. Or, Fig. 20 The function / implementation process of the transceiver module 2002 can be achieved by Figure 2 It is implemented by the RF circuit 110 in the terminal device 105 shown in FIG.

[0342] Since the communication device 200 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0343] For example, the communication device is taken as the network device in the above method embodiment. Fig.21 2 shows a schematic diagram of the structure of a communication device 210. The communication device 210 includes a processing module 2101 and a transceiver module 2102. The communication device 200 can be Figure 4 , Figure 6 , Fig.13 , Fig.15 The processing module 2101 may also be referred to as a processing unit, which is used to implement the processing function of the network device in the above method embodiment. Figure 6 Step S603 in Fig.15 The transceiver module 2102, which may also be referred to as a transceiver unit, is used to implement the transceiver function of the network device in the above method embodiment. Figure 4 Steps S401-S404 in Figure 6 In step S602, Fig.13 In step S1302, Fig.15 The transceiver module 2102 may be referred to as a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0344] Exemplarily, the transceiver module 2102 is used to receive first indication information, wherein the first indication information is used to indicate a random access RA triggered by a first event or a second event, the first event refers to the number of transmissions of the scheduling request SR reaching the maximum number of SR transmissions, and the second event refers to the absence of available physical uplink control channel PUCCH resources for the triggered and suspended SR.

[0345] The processing module 2101 is configured to trigger an RA according to a first event or a second event of first indication information.

[0346] In a possible implementation manner, the first indication information is indicated by an information element IE or a cause value of a radio resource control RRC message.

[0347] In a possible implementation manner, the first indication information includes second indication information indicating the arrival of high priority data or third indication information indicating the arrival of low priority data, and the second indication information or the third indication information is used to determine the first event or the second event.

[0348] In a possible implementation manner, the first indication information is indicated by a logical channel identifier LCID, a reserved bit, or a load in a media access control control element MAC CE.

[0349] In a possible implementation, when the first indication information is indicated by LCID, or when the first indication information is indicated by a load in a MAC CE, the first indication information is also used to indicate that the load in the MAC CE is a first cell radio network temporary identifier C-RNTI.

[0350] In a possible implementation, the first indication information is indicated by the BSR in the RA, wherein, among the amount of data to be sent of all logical channel groups of the BSR, when the RA is triggered by the first event, the amount of data to be sent of the LCG corresponding to at least one logical channel without available PUCCH resources is set to 0; or, when the RA is triggered by the second event, the amount of data to be sent of the LCG corresponding to at least one LCH with available PUCCH resources is set to 0.

[0351] In a possible implementation manner, the first indication information is indicated by using different random access channel RACH resources.

[0352] In a possible implementation manner, the first indication information is indicated by uplink control information UCI in the PUCCH resource.

[0353] In addition, the transceiver module 2102 is also used to receive first indication information, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to the uplink listen-before-talk LBT failure number reaching a maximum preset number.

[0354] The processing module 2101 is further configured to determine a cell where the first event occurs according to the first indication information.

[0355] In a possible implementation manner, the transceiver module 2102 is further configured to receive second indication information, where the second indication information is used to indicate the bandwidth part BWP where the first event occurs.

[0356] In a possible implementation manner, the first indication information is indicated by a medium access control control element MAC CE.

[0357] In a possible implementation manner, the first indication information is an identifier of a cell where the first event occurs.

[0358] In a possible implementation manner, the first indication information is a bitmap, and the cell where the first event occurs corresponds to a bit in the bitmap.

[0359] In a possible implementation manner, the processing module 2101 is further configured to determine not to receive data from the uplink authorization of the cell where the first event occurs or the BWP where the first event occurs.

[0360] In this embodiment, the communication device 210 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to a specific ASIC, a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the communication device 210 can be used Figure 3 The form of the network device 300 is shown.

[0361] for example, Figure 3 The processor 301 in the network device 300 shown can call the computer execution instructions stored in the memory 302 to enable the network device 300 to execute the method in the above method embodiment.

[0362] Specifically, Fig.21 The function / implementation process of the processing module 2101 in can be Figure 3 The processor 321 in the network device 300 shown calls the computer execution instructions stored in the memory 322 to implement. Or, Fig.21 The function / implementation process of the transceiver module 2102 can be achieved by Figure 3 The RF circuit 312 in the network device 300 shown in FIG.

[0363] Since the communication device 210 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0364] The embodiment of the present application further provides a communication device, which includes a processor, a memory, and a transceiver. The processor is coupled to the memory. When the processor executes a computer program or instruction in the memory, Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the terminal device is executed.

[0365] The embodiment of the present application further provides a communication device, which includes a processor, a memory, and a transceiver. The processor is coupled to the memory. When the processor executes a computer program or instruction in the memory, Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the network device is executed.

[0366] The embodiment of the present application also provides a chip, including: a processor and an interface, for calling and running a computer program stored in the memory from the memory, and executing the following Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the terminal device or network device in the embodiment.

[0367] The present application also provides a computer-readable storage medium in which instructions are stored. When the instructions are executed on a computer or a processor, the computer or the processor executes Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the terminal device or network device in the embodiment.

[0368] The present application also provides a computer program product including instructions, which, when executed on a computer or processor, causes the computer or processor to execute Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the terminal device or network device in the embodiment.

[0369] The present application provides a chip system, which includes a processor for executing a communication device. Figure 4 , Figure 6 , Fig.13 , Fig.14 , Fig.15 The method corresponding to the terminal device or network device in the embodiment.

[0370] In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for the terminal device. The chip system may include a chip, an integrated circuit, or a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0371] Among them, the communication device, chip, computer storage medium, computer program product or chip system provided in this application is used to execute the method described above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the implementation methods provided above and will not be repeated here.

[0372] The processor involved in the embodiments of the present application may be a chip. For example, it may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0373] The memory involved in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0374] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0375] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0376] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0377] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0378] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0380] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An event processing method, characterized in that: The method is applied to a terminal device, and the method comprises: Determine first indication information, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to that the number of uplink listen-before-talk (LBT) failures reaches a maximum preset number; wherein the first indication information is a bitmap, and each cell where the first event occurs corresponds to a bit in the bitmap; Sending the first indication information to the network device; The method further comprises: If the terminal device has available uplink transmission resources, the packetization process is performed and the triggered uplink LBT failure is canceled, and the triggered uplink LBT failure includes the uplink LBT failure of one or more cells.

2. The method according to claim 1, characterized in that The first indication information is indicated by a media access control control element MAC CE.

3. The method according to claim 1 or 2, characterized in that: Also includes: Determine not to send data through the uplink grant of the cell where the first event occurs.

4. The method according to claim 1 or 2, characterized in that: Also includes: If the terminal device has no available uplink transmission resources, a scheduling request is sent to the network device, where the scheduling request is used to request uplink resources.

5. An event processing method, characterized in that: The method is applied to a network device, comprising: Receive first indication information from a terminal device, wherein the first indication information is used to indicate a cell where a first event occurs, and the first event refers to that the number of uplink listen-before-talk LBT failures reaches a maximum preset number; the first indication information is a bitmap, and each cell where the first event occurs corresponds to a bit in the bitmap; the terminal device is used to perform a packetization process and cancel a triggered uplink LBT failure when it has available uplink transmission resources, and the triggered uplink LBT failure includes an uplink LBT failure of one or more cells; A cell where a first event occurs is determined according to the first indication information.

6. The method according to claim 5, characterized in that The first indication information is indicated by a media access control control element MAC CE.

7. The method according to claim 5 or 6, characterized in that: Also includes: Determine not to receive data from the uplink grant of the cell where the first event occurs.

8. A communication device, characterized in that: It comprises a processing module and a transceiver module, wherein the processing module is used to control the transceiver module to execute the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer or a processor, the computer or the processor executes the method according to any one of claims 1 to 7.

Images