A method and apparatus for scheduling request processing

Abstract

A scheduling request processing method and apparatus are disclosed, applicable to non-terrestrial network (NTN) scenarios. The method includes: a first entity determining the existence of a first scheduling request (SR) in a waiting state. When a first condition is met, the first entity instructs a second entity to send the first SR. The first condition includes: the first entity has a configured SR transmission opportunity on valid Physical Uplink Control Channel (PUCCH) resources, and the first entity has not received an uplink synchronization loss indication. Based on this scheme, if the first entity has a configured SR transmission opportunity on valid PUCCH resources, instructing the second entity to send the first SR requires at least that the first entity has not received an uplink synchronization loss indication. In other words, it can restrict terminal devices from sending SRs when uplink synchronization is lost, thereby reducing power consumption waste of terminal devices and reducing resource waste occupied by SR transmission.

Description

[0001] This application is a divisional application. The original application, application number 202211347424.6, was filed on October 31, 2022. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a scheduling request processing method and apparatus. Background Technology

[0003] Scheduling requests (SRs) are primarily used to request new uplink resources. SRs can be triggered in scenarios such as beam fault recovery, preemptive buffer status reporting, or consistent Listen Before Talk failure recovery.

[0004] Once a Service Request (SR) is triggered, it can be considered to be in a pending state. For a pending SR, if there is no valid Physical Uplink Control Channel (PUCCH) resource, the terminal device initiates a random access procedure and cancels the SR. If a valid PUCCH resource exists and the maximum number of SR transmissions has not been reached, the terminal device uses that PUCCH resource to send the SR.

[0005] However, in some scenarios, the terminal device may be in an uplink out-of-sync state or an uplink synchronization state. Therefore, how to handle SRs in a waiting state when considering whether the terminal device is synchronized is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a scheduling request processing method and apparatus. In a scenario considering the synchronization state of terminal devices, if an SR in a waiting state is to be sent, at least the first entity must not have received an uplink synchronization loss indication.

[0007] Firstly, a scheduling request processing method is provided. This method can be executed by a terminal device, or by a component of the terminal device, such as the terminal device's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: a first entity determining that a first scheduling request (SR) exists in a waiting state; and when a first condition is met, the first entity instructs a second entity to send the first SR. The first condition includes: the first entity has a configured SR transmission opportunity on a valid Physical Uplink Control Channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication.

[0008] Based on this scheme, if the first entity has a configured SR transmission opportunity on valid PUCCH resources, it must at least ensure that the first entity has not received an uplink synchronization loss indication before instructing the second entity to send the first SR. In other words, even if the first entity has a configured SR transmission opportunity on valid PUCCH resources, if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink synchronization failure state), then the first entity cannot instruct the second entity to send the first SR.

[0009] In other words, based on the aforementioned first condition, it is possible to prevent terminal devices from sending SRs when uplink synchronization is lost. Even if a terminal device sends an SR when uplink synchronization is lost, the access network device will be unable to successfully receive the SR due to the loss of uplink synchronization. Therefore, restricting terminal devices from sending SRs when uplink synchronization is lost can reduce power consumption waste of the terminal device and reduce resource waste associated with SR transmission.

[0010] In one possible design, the first entity does not receive an uplink synchronization loss indication, including: the first entity does not receive an uplink synchronization loss indication before the SR transmission timing.

[0011] In one possible design, the first entity does not receive an uplink synchronization loss indication before the SR transmission timing, including: after the first SR is triggered, but before the SR transmission timing, the first entity does not receive an uplink synchronization loss indication.

[0012] In one possible design, the first entity does not receive an uplink synchronization loss indication, including: the most recently received indication by the first entity is an uplink synchronization indication.

[0013] Secondly, a scheduling request processing method is provided. This method can be executed by a terminal device, a component of the terminal device (such as its processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: a first entity determining that a first scheduling request (SR) exists in a waiting state. When a second condition is met, a random access procedure is initiated, and the first SR is cancelled. When a third condition is met, the first entity sends a random access preamble indication to a second entity, or the first entity determines not to send a random access preamble indication to the second entity. The second condition includes: the first entity does not have a valid Physical Uplink Control Channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication. The third condition includes: the first entity does not have a valid PUCCH resource, and the first entity has received an uplink synchronization loss indication; the random access preamble indication is used to instruct the second entity to send a random access preamble. The valid PUCCH resource corresponds to the first SR.

[0014] Based on this scheme, if the first entity does not have valid PUCCH resources, in order to initiate a random access procedure and cancel the first SR, it must at least meet the condition that the first entity has not received an uplink synchronization loss indication. In other words, even if the first entity does not have valid PUCCH resources, if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink out-of-synchronization state), then the first entity cannot initiate a random access procedure. That is to say, based on the constraint of the second condition, the terminal device can be prevented from initiating random access in an uplink out-of-synchronization state, thereby reducing the power consumption waste of the terminal device and the resource waste occupied by random access.

[0015] Furthermore, if the first entity receives an uplink synchronization loss indication, meaning the terminal device is in an uplink synchronization failure state, the first entity will not send a random access preamble indication to the second entity, i.e., it will not initiate random access. In other words, based on the constraint of the third condition, it is possible to prevent the terminal device from initiating random access in an uplink synchronization failure state, thereby reducing the power consumption waste of the terminal device and the resource waste occupied by random access.

[0016] In one possible design, after the first entity sends a random access preamble indication to the second entity, the method further includes: if the first entity receives an uplink synchronization indication, the first entity sends indication information to the second entity, the indication information being used to cancel the transmission of the random access preamble.

[0017] In one possible design, the method further includes: the first entity instructing the second entity to send a first SR on a valid PUCCH resource.

[0018] Based on the two possible implementations described above, the transmission of the random access preamble can be cancelled after uplink synchronization is restored. At this point, if a valid PUCCH resource exists, the first entity can instruct the second entity to transmit the first SR on that PUCCH resource, reducing the latency caused by the execution of random access. That is, compared to the scheme that still transmits the random access preamble, the transmission latency of the first SR can be reduced.

[0019] In one possible design, when the third condition is met, the method further includes: starting a first timer; the first entity receiving an uplink synchronization indication, including: the first entity receiving the uplink synchronization indication before the first timer expires.

[0020] In one possible design, when the third condition is met, the method further includes: starting a second timer; the first entity determines not to send a random access preamble indication to the second entity, including: the first entity determines not to send a random access preamble indication to the second entity before the second timer expires.

[0021] Thirdly, a communication device is provided for implementing various methods. This communication device can be a terminal device as described in the first or second aspect, or a device included in a terminal device, such as a chip, chip system, or module. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0022] In some possible designs, the communication device may include a processing module and a communication module. The processing module can be used to implement the processing functions in any of the above aspects and their possible implementations. The communication module is used to implement the sending and / or receiving functions in any of the above aspects and their possible implementations. The communication module may consist of transceiver circuitry, a transceiver, a transceiver unit, or a communication interface.

[0023] In some possible designs, the communication module includes a sending module and / or a receiving module, which are used to implement the sending or receiving functions in any of the above aspects and any possible implementations.

[0024] Fourthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the methods described in any of the aspects. The communication device may be a terminal device as described in the first or second aspect, or a device included in a terminal device, such as a chip, chip system, or module.

[0025] Fifthly, a communication device is provided, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods described in any of the aspects. The memory may be coupled to the processor, or the memory may exist independently of the processor, for example, the memory and the processor are two separate modules. The memory may be located outside or within the communication device. The communication device may be a terminal device as described in the first or second aspect, or a device included in a terminal device, such as a chip or chip system or module.

[0026] In a sixth aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in either aspect.

[0027] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the method described in either aspect.

[0028] It is understandable that when the communication device provided by any of the third to seventh aspects is a chip, the sending action / function can be understood as output information, and the receiving action / function can be understood as input information.

[0029] It is understandable that when the communication device provided by any of the third to seventh aspects is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0030] The technical effects of any of the design methods in aspects three through seven can be found in the technical effects of different design methods in aspects one or two, and will not be repeated here. Attached Figure Description

[0031] Figure 1 A schematic diagram of the structure of a communication system provided in this application;

[0032] Figure 2 A schematic diagram of a non-terrestrial network structure is provided in this application;

[0033] Figure 3 A schematic diagram of another non-terrestrial network structure provided in this application;

[0034] Figure 4 A schematic diagram of another non-terrestrial network provided in this application;

[0035] Figure 5 This application provides a schematic diagram of another non-terrestrial network structure.

[0036] Figure 6a A schematic diagram of the structure of a communication device provided in this application;

[0037] Figure 6b A schematic diagram of the structure of a terminal device provided in this application;

[0038] Figure 7 A flowchart illustrating a scheduling request processing method provided in this application;

[0039] Figure 8 A timing diagram provided for this application;

[0040] Figure 9 A flowchart illustrating another scheduling request processing method provided in this application;

[0041] Figure 10a A flowchart illustrating another scheduling request processing method provided in this application;

[0042] Figure 10b Another timing diagram provided for this application;

[0043] Figure 11 A schematic diagram of another terminal device provided in this application;

[0044] Figure 12 A schematic diagram of another communication device provided in this application. Detailed Implementation

[0045] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0046] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0047] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0048] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0049] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply 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 this application.

[0050] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0051] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0052] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0053] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0054] 1. Scheduling request (SR):

[0055] SR is mainly used to request uplink (UL) resources for new transmissions, such as uplink shared channel (UL-SCH) resources.

[0056] Typically, when configuring a Scheduled Request Resource (SR) in a network, an SR resource is configured for it. This SR resource resides in the Physical Uplink Control Channel (PUCCH) resource. For example, a base station can configure the SR transmission timing and frequency domain resource location on the PUCCH resource as the SR resource. Therefore, it can also be considered that the SR configured by the network has a corresponding (configured) PUCCH resource.

[0057] For example, one possible way to configure SR resources is as follows:

[0058] SR resource configuration (SchedulingRequestResourceConfig)::=SEQUENCE{

[0059] SR resource identifier (schedulingRequestResourceId);

[0060] SR identifier (schedulingRequestID);

[0061] Period and Offset;

[0062] Resources;

[0063] }

[0064] The SR resource identifier is used to identify the SR resource in the PUCCH. The SR identifier is used to identify the SR or SR configuration. The period and offset are used to indicate the number of symbols or time slots of the SR period and offset. The resource includes the identifier of the PUCCH resource, which is the PUCCH resource where the SR resource is located, or in other words, the PUCCH resource corresponding to the SR.

[0065] Once an SR (Signal Request) is triggered, it can be considered to be in a pending state until it is sent or canceled. In other words, an SR in a pending state can be understood as an SR that has been triggered but has not yet been sent or canceled. Regarding SRs in a pending state:

[0066] If the media access control (MAC) entity does not have a valid PUCCH resource, the terminal device initiates a random access procedure and cancels the waiting state SR.

[0067] If the MAC entity has a valid PUCCH resource and has not reached the maximum number of SR transmissions (sr-TransMax), the terminal device can use the PUCCH resource to send an SR.

[0068] It should be noted that the "waiting state" in the embodiments of this application can also be called the "pending send state", and the two can be used interchangeably.

[0069] 2. Non-terrestrial network (NTN):

[0070] With the development of communication demands, 5G networks and their future evolution must not only meet diverse service requirements but also provide broader service coverage. Among these, NTN (Network Networking Technology) is less affected by geographical conditions and can achieve global coverage, making it an important direction for future communication development.

[0071] Compared to traditional terrestrial networks, NTN uses typical flying platforms (such as airplanes or drones) or satellites for network deployment. For example, base stations or some base station functions are deployed on flying platforms or satellites to provide coverage for terminals, or flying platforms or satellites are used as relays to forward signals from terrestrial base stations to provide coverage for terminals.

[0072] In NTN (Network Networking), satellite ephemeris information or flight platform information (such as platform position, speed, and trajectory) plays a crucial role in communication. Taking satellite communication as an example, terminal devices can determine the end-to-end latency from the terminal device to the base station using satellite ephemeris information, their own position, and the latency information from the satellite to the satellite gateway. This allows for pre-compensation for timing advance based on the end-to-end latency. Furthermore, it enables the network to know the timing advance of terminal devices and perform more rational data scheduling.

[0073] However, satellite ephemeris information is time-sensitive. Therefore, a validity timer is introduced in NTN. After receiving satellite ephemeris information, the terminal device's radio resource control (RRC) entity can start the validity timer. Before the validity timer expires, the ephemeris information is accurate and valid, and the terminal device is in uplink synchronization state. After the validity timer expires, the ephemeris information becomes invalid, and the terminal device is in uplink out-of-synchronization state, or in other words, uplink synchronization is lost. Upon receiving ephemeris information again, the terminal device restores uplink synchronization.

[0074] Furthermore, upon receiving ephemeris information, the RRC entity can send an uplink synchronization indication to the MAC entity to indicate that the terminal device is in a synchronized state. When the valid timer expires, the RRC entity can send an uplink synchronization loss indication to the MAC entity to indicate that the terminal device has lost uplink synchronization or that the terminal device is in an uplink out-of-synchronization state.

[0075] When a terminal device is in an uplink out-of-synchronization state, it will clear its Hybrid Automatic Repeat Request (HARQ) buffer and stop sending uplink signals, such as MAC control elements (MAC CE) or RRC messages. In this state, the base station cannot correctly receive the terminal device's uplink signals.

[0076] As mentioned above, current SR handling methods require the terminal device to initiate a random access procedure or send an SR when the SR is in a waiting state. However, in NTN, if the terminal device is in an uplink out-of-synchronization state, it is required to stop sending uplink signals. Therefore, how to handle SRs in a waiting state in scenarios considering whether the terminal device is synchronized is a problem that urgently needs to be solved.

[0077] Based on this, this application provides an SR processing method. In this method, to send an SR that is in a waiting state, there must be valid PUCCH resources, and the terminal device must be in uplink synchronization state. Therefore, it can avoid the terminal device sending an SR when uplink synchronization is lost, thereby reducing power consumption waste and resource waste of the terminal device.

[0078] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems such as long-term evolution (LTE) systems, new radio (NR) systems, 5G systems, satellite communication systems, NTN systems, vehicle-to-everything (V2X) systems, LTE and 5G hybrid networking systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, and future evolution communication systems. The communication system can also be a non-3GPP communication system; there is no limitation.

[0079] The technical solutions of this application can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), D2D, V2X, and IoT communication scenarios.

[0080] The communication systems and scenarios applicable to this application mentioned above are merely illustrative examples. The communication systems and scenarios applicable to this application are not limited thereto. The communication systems and scenarios provided in this application do not impose any limitations on the solutions of this application. This is hereby stated uniformly and will not be repeated below.

[0081] See Figure 1 This application provides a communication system 10 suitable for the scheme described in this application. The communication system 10 includes at least one terminal device 101 and at least one access network device 102. It should be understood that... Figure 1 The number of terminal devices and access network devices mentioned is just an example; there could be more or fewer.

[0082] Optionally, the terminal device 101 in this embodiment can be a user-side device for implementing wireless communication functions, such as a terminal or a chip that can be used in the terminal. The terminal can be a user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent, or terminal apparatus in a 5G network or a public land mobile network (PLMN) evolved from 5G. Access terminals can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Alternatively, terminals can be communication-enabled terminals in the Internet of Things (IoT), such as terminals in V2X (e.g., vehicle-to-everything (V2X) communication, terminals in D2D communication, or terminals in M2M communication, etc. Terminals can be mobile or fixed.

[0083] Optionally, the access network device 102 in this application embodiment is a device that connects the terminal device 101 to the wireless network. The access network device 102 can be called a node in the radio access network (RAN), a base station, or a radio access network node (or device).

[0084] For example, access network equipment may include evolved NodeBs (NodeBs, eNBs, or e-NodeBs) in LTE or LTE-A systems, such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios. Alternatively, it may include next-generation node Bs (gNBs) in NR systems. It may also include transmission reception points (TRPs), home base stations (e.g., home evolved NodeBs, or home Node Bs, HNBs), base band units (BBUs), base band pools, or wireless fidelity (WiFi) access points (APs). Alternatively, it may include base stations in an NTN, which can be deployed on flight platforms or satellites. In an NTN, access network equipment can act as a Layer 1 (L1) relay, a base station, or an integrated access and backhaul (IAB) node. Alternatively, the access network device can be a device that implements base station functions in IoT, such as V2X, D2D, or machine-to-machine (M2M) devices that implement base station functions.

[0085] Access network equipment can also be modules or units capable of implementing some of the functions of a base station. For example, access network equipment can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. Alternatively, access network equipment can be access network equipment or modules of access network equipment in an Open Radio Access Network (ORAN) system. In an ORAN system, CU can also be called open (O)-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU.

[0086] Optionally, CU and DU can be divided according to the protocol layer of the wireless network: for example, the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the RRC layer and the Service Data Adaptation Protocol (SDAP) layer) are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the MAC layer, or the Physical (PHY) layer) are set in the DU; or, for example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without restriction.

[0087] The above division of CU and DU processing functions according to protocol layers is merely an example; other methods can also be used. For instance, CUs or DUs can be divided into those with more protocol layer functions, or they can be divided into those with partial protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of CUs or DUs can be divided according to service type or other system requirements, such as by latency. Functions that need to meet latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0088] Optionally, the base station in this application embodiment may include various forms of base stations, such as: macro base station, micro base station (also known as small station), relay station, access point, home base station, TRP, transmitting point (TP), mobile switching center, etc. This application embodiment does not specifically limit these.

[0089] As one possible implementation, such as Figure 2 As shown, the access network device 102 can be deployed on the ground as part of the terrestrial network, communicating with the data network through the core network. In this case, the communication system 10 provided in this application may also include relay equipment deployed on a flight platform or satellite, which acts as a Layer 1 relay, regenerating physical layer signals and forwarding them to terminal devices or access network devices.

[0090] As another possible implementation, such as Figure 3 As shown, the access network device 102 can be deployed on a flight platform or satellite to realize the function of a ground station, communicate directly with the core network, and further communicate with the data network through the core network.

[0091] As another possible implementation, such as Figure 4 As shown, the access network device 102 can be deployed on a flight platform or satellite to realize the functions of a ground station, communicating directly with the core network, and further communicating with the data network through the core network. In addition, there are inter-satellite links (ISLs) between access network devices mounted on different flight platforms or satellites, and the access network devices can communicate with each other through these ISLs.

[0092] As another possible implementation, such as Figure 5 As shown, the access network device 102 may include a DU deployed on a flight platform or satellite and a CU deployed on the ground. The DU deployed on the flight platform or satellite communicates with the CU deployed on the ground via a FI interface. The CU deployed on the ground communicates with the core network, and further, communicates with the data network through the core network.

[0093] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0094] Optionally, the relevant functions of the terminal equipment or access network equipment involved in this application can be achieved through... Figure 6a This is achieved through the communication device 60. See also Figure 6a The communication device 60 includes one or more processors 601. Furthermore, the communication device 60 may also include a communication bus 602 and at least one communication interface. Figure 6a (The above is merely an example, illustrating a communication device 60 including a communication interface 604 and a processor 601.) Optionally, the communication device 60 may also include a memory 603.

[0095] Processor 601 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application, or a processing core for processing data (e.g., computer program instructions). The processor can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.

[0096] In a specific implementation, as one embodiment, the processor 601 may include one or more CPUs, for example... Figure 6aCPU0 and CPU1 in the CPU.

[0097] The communication bus 602 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6a The bus is represented by only one thick line, but this does not mean that there is only one bus or one type of bus. The communication bus 602 is used to connect different components in the communication device 60, so that different components in the communication device 60 can communicate and interact with each other.

[0098] The communication interface 604 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), or wireless local area network (WLAN). For example, the communication interface 604 can be a transceiver or similar device. Alternatively, the communication interface 604 can also be a transceiver circuit located within the processor 601, used to implement signal input and signal output for the processor.

[0099] The memory 603 can be a device with storage functionality. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via the communication bus 602. The memory can also be integrated with the processor.

[0100] The memory 603 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the computer execution instructions stored in the memory 603 to implement the method provided in the embodiments of this application.

[0101] Alternatively, in this embodiment, the processor 601 may execute the processing-related functions of the method provided in the following embodiments of this application, and the communication interface 604 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0102] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0103] In a specific implementation, as one embodiment, the communication device 60 may further include an output device 605 and an input device 606. The output device 605 communicates with the processor 601 and can display information in various ways. For example, the output device 605 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 606 communicates with the processor 601 and can receive user input in various ways. For example, the input device 606 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0104] It should be noted that, Figure 6a The structural composition shown does not constitute a limitation on the communication device, except... Figure 6a In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0105] like Figure 6b The diagram shown is a structural schematic of another terminal device provided in an embodiment of this application. See also... Figure 6b The terminal device may include a first entity and a second entity. Optionally, the terminal device may also include a third entity. The first entity is located above the second entity, or in other words, the first entity is an upper-level entity of the second entity. Furthermore, the first entity is located below the third entity, or in other words, the first entity is a lower-level entity of the third entity.

[0106] For example, the first entity can be a MAC entity. The second entity can be a PHY entity. The third entity can be an RRC entity.

[0107] It should be noted that, Figure 6bThe structure shown does not constitute a limitation on the terminal device, except Figure 6b In addition to the entities shown, the terminal device may include more or fewer entities than those shown in the figure. For example, the terminal device may also include RLC entities, PDCP entities, etc. This application does not make specific limitations in this regard.

[0108] The scheduling request processing method provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings. It is understood that in the embodiments of this application, the terminal device may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0109] As an example, the following embodiments can be applied to NTN scenarios, such as satellite communication scenarios, or other scenarios in NTN, such as low altitude platform (LAP) subnetwork and high altitude platform (HAP) subnetwork scenarios, without being specifically limited thereto.

[0110] Furthermore, the following embodiments can also be applied to other possible communication scenarios or communication systems, such as long-distance communication scenarios involving a long distance between the terminal device and the access network device, or a relatively high moving speed, or communication scenarios involving the terminal device possibly being in a synchronized state or out-of-synchronization state. The scheduling request can be processed by the method provided in the embodiments of this application.

[0111] like Figure 7 The image shows a scheduling request processing method provided in this application, which is applied to a terminal device. See also... Figure 7 The scheduling request processing method includes the following steps:

[0112] S701, The first entity determines that there is a first SR in a waiting state.

[0113] Optionally, the first SR can be triggered by one or more of the following events: beam failure recovery, preemptive buffer status reporting, timing advance reporting, or consistent listen before talk failure recovery. Once the first SR is triggered, the first entity can perceive the existence of the first SR in a waiting state, that is, the first entity can determine that there is a first SR in a waiting state.

[0114] S702. When the first condition is met, the first entity instructs the second entity to send the first SR.

[0115] The first condition includes: the first entity has an SR transmission occasion on the valid PUCCH resource for SR configured, and the first entity has not received an uplink synchronization loss indication.

[0116] Optionally, the first entity has a configured SR transmission opportunity on a valid PUCCH resource, which can also be understood as: the first entity has at least one valid PUCCH resource for the configured SR.

[0117] Optionally, a valid PUCCH resource can also be understood as an available PUCCH resource. In other words, a valid PUCCH resource can also be understood as a PUCCH resource being available, or a PUCCH resource configuration being activated.

[0118] Optionally, the uplink synchronization loss indication can be used to indicate that the terminal device has lost uplink synchronization, or that the terminal device is in an uplink out-of-synchronization state, or that the terminal device has lost uplink synchronization with the serving cell.

[0119] Optionally, the uplink synchronization loss indication can be generated by a third entity and sent to the first entity. For example, the third entity can maintain a timer associated with the synchronization state (e.g., a validity timer) and send the uplink synchronization loss indication or uplink synchronization indication to the first entity based on the timer's running state.

[0120] For example, a third entity can start a valid timer upon receiving ephemeris information from a satellite or flight information from a flight platform (such as the platform's position, speed, and flight trajectory), and send an uplink synchronization indication to the first entity to indicate that the terminal device is in uplink synchronization mode or synchronized with the serving cell. Furthermore, when the timer expires, an uplink synchronization loss indication is sent to the first entity. The duration of this timer can be understood as the effective duration of the ephemeris information or flight information.

[0121] Therefore, in this scenario, the first entity not receiving an uplink synchronization loss indication may include: the first entity not receiving an uplink synchronization loss indication from the third entity.

[0122] Optionally, the first SR may be triggered before the effective timer expires, or it may be triggered after the effective timer expires; this application does not specifically limit this.

[0123] As one possible implementation, the first entity not receiving an uplink synchronization loss indication may include: the most recent (or most recent) indication received by the first entity is the uplink synchronization loss indication. For example, the most recent (or most recent) indication can be understood as the last indication received before the current time, where the current time could be, for example, the time when the first conditional judgment was executed.

[0124] For example, such as Figure 8 As shown in (a), with the current time as time t1, if the first entity receives an uplink synchronization loss indication at time t2 and then receives another uplink synchronization indication at time t3, then the latest (or most recent) indication received by the first entity is the uplink synchronization indication, which belongs to the scenario where the first entity did not receive an uplink synchronization loss indication.

[0125] like Figure 8 As shown in (b), with the current time as time t1, if the first entity receives an uplink synchronization indication at time t2 and then receives an uplink synchronization loss indication at time t3, then the latest (or most recent) indication received by the first entity is an uplink synchronization loss indication, which belongs to the scenario where the first entity receives an uplink synchronization loss indication.

[0126] As another possible implementation, the first entity not receiving an uplink synchronization loss indication may include: the first entity not receiving an uplink synchronization loss indication before the SR transmission timing. Further, it may include: the first entity not receiving an uplink synchronization loss indication after the first SR is triggered, but before the SR transmission timing. Here, the SR transmission timing is the SR transmission timing configured on a valid PUCCH resource.

[0127] For example, such as Figure 8 As shown in (c), assuming the first SR is triggered at time t4 and the SR transmission occurs at time t5, then if the first entity does not receive an uplink synchronization loss indication between time t4 and time t5, it falls under the scenario where the first entity did not receive an uplink synchronization loss indication. If the first entity receives an uplink synchronization loss indication between time t4 and time t5, it falls under the scenario where the first entity received an uplink synchronization loss indication.

[0128] Optionally, the first condition may also include: the number of transmissions of the first SR is less than the maximum number of transmissions of the SR. This maximum number of transmissions of the SR may be configured by the access network device. Of course, the first condition may also include other limiting conditions, which are not specifically limited in this application.

[0129] Optionally, the first entity instructing the second entity to send the first SR may include: the first entity sending indication information a to the second entity, the indication information a being used to instruct the second entity to send the first SR. Upon receiving the indication information a, the second entity may send the first SR during the SR transmission.

[0130] Based on the above scheme, if the first entity has a configured SR transmission opportunity on valid PUCCH resources, in order to instruct the second entity to send the first SR, at least the first entity must not have received an uplink synchronization loss indication. In other words, even if the first entity has a configured SR transmission opportunity on valid PUCCH resources, if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink synchronization failure state), then the first entity cannot instruct the second entity to send the first SR.

[0131] In other words, based on the aforementioned first condition, it is possible to prevent terminal devices from sending SRs when uplink synchronization is lost. Even if a terminal device sends an SR when uplink synchronization is lost, the access network device will be unable to successfully receive the SR due to the loss of uplink synchronization. Therefore, restricting terminal devices from sending SRs when uplink synchronization is lost can reduce power consumption waste of the terminal device and reduce resource waste associated with SR transmission.

[0132] like Figure 9 The image shows another scheduling request processing method provided in this application, which is applied to a terminal device. See also... Figure 9 The scheduling request processing method includes the following steps:

[0133] S901. The first entity determines that there is a first SR in a waiting state. The implementation of step S901 can be referred to the relevant description in step S701 above, and will not be repeated here.

[0134] After step S901, the following steps S902a, S902b, or S902c may be executed.

[0135] S902a. When the second condition is met, the random access procedure is initiated and the first SR is cancelled.

[0136] The second condition includes: the first entity does not have a valid PUCCH resource, and the first entity has not received an uplink synchronization loss indication. The valid PUCCH resource corresponds to the first SR, or in other words, the PUCCH resource is the PUCCH resource configured for the first SR.

[0137] Optionally, the absence of valid PUCCH resources for the first entity may include: the PUCCH resource configured for the first SR being occupied by other services; or, the frequency domain resources corresponding to the SR transmission timing on the PUCCH resource configured for the first SR being occupied by other services.

[0138] The explanation of the uplink synchronization loss indication and the fact that the first entity did not receive the uplink synchronization loss indication can be found in the relevant description in step S702 above, and will not be repeated here.

[0139] Based on step S902a, if the first entity wants to initiate a random access procedure and cancel the first SR in the absence of valid PUCCH resources, it must at least satisfy the condition that the first entity has not received an uplink synchronization loss indication. In other words, even if the first entity does not have valid PUCCH resources, if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink out-of-synchronization state), then the first entity cannot initiate a random access procedure. That is to say, based on the restriction of the second condition, the terminal device can be prevented from initiating random access in an uplink out-of-synchronization state, thereby reducing the power consumption waste of the terminal device and the resource waste occupied by random access.

[0140] S902b, When the third condition is met, the first entity sends a random access preamble indication to the second entity. The random access preamble indication is used to instruct the second entity to send a random access preamble.

[0141] The third condition includes: the first entity does not have a valid PUCCH resource, and the first entity receives an uplink synchronization loss indication.

[0142] Optionally, the first entity receiving an uplink synchronization loss indication may include: the most recently received indication by the first entity being an uplink synchronization loss indication; or, the first entity receiving the uplink synchronization loss indication after the first SR is triggered but before the configured SR transmission timing of the first SR.

[0143] As one possible implementation, the first entity may not have a valid PUCCH resource, which could include: the PUCCH resource configured for the first SR being occupied by other services. Alternatively, the frequency domain resource corresponding to the SR transmission timing on the PUCCH resource configured for the first SR may be occupied by other services.

[0144] As another possible implementation, the first entity does not have a valid PUCCH resource, which may include: the first entity actually has a configured SR transmission opportunity on a valid PUCCH resource, but because the first entity received an uplink synchronization loss indication, the first entity considers the PUCCH resource invalid.

[0145] Combining the two possible implementations above, that is, if the first entity receives an uplink synchronization loss indication, regardless of whether the PUCCH resource corresponding to the first SR is occupied, or regardless of whether the PUCCH resource corresponding to the first SR exists, the first entity considers the PUCCH resource invalid.

[0146] Optionally, after receiving the random access preamble indication, the second entity may send the random access preamble at the configured random access time.

[0147] Optionally, the first entity may also send indication information b to the second entity, which may indicate a duration (denoted as duration 1). In this scenario, the random access preamble indication and the indication information b can jointly instruct the second entity to send the random access preamble at a random access timing after duration 1. For example, the start time of duration 1 may be the time when the second entity receives the indication information b and parses out duration 1.

[0148] Optionally, after the first entity sends a random access preamble indication to the second entity, the first entity may receive an uplink synchronization indication. For example, if the third entity receives satellite ephemeris information or flight information from the flight platform again after sending an uplink synchronization loss indication to the first entity, then the third entity can send an uplink synchronization indication to the first entity to indicate that uplink synchronization has been restored.

[0149] In this scenario, such as Figure 10a As shown, after step S902b, the scheduling request processing method provided in this embodiment may further include: the first entity sending indication information c to the second entity. This indication information c is used to cancel the transmission of the random access preamble. Alternatively, the indication information c is used to instruct the second entity to cancel the transmission of the random access preamble.

[0150] Optionally, after receiving the indication information c, if the second entity has not yet sent the random access preamble, it can cancel the transmission of the random access preamble. For example, the reason why the second entity has not yet sent the random access preamble may be that the random access opportunity has not yet arrived, or that the second entity received the indication information c within a specified time period (for example, the starting time is the time when the second entity receives the indication information b and parses out the duration of 1, and the duration is 1).

[0151] For example, such as Figure 10b As shown, taking the example where the second entity receives the random access preamble instruction at time t1, and the random access opportunity occurs at time t2. If the second entity receives the instruction information c at time t3, then the second entity will cancel the transmission of the random access preamble.

[0152] Optional, such as Figure 10aAs shown, after receiving the uplink synchronization instruction, the first entity can also instruct the second entity to send the first SR on a valid PUCCH resource. Accordingly, the second entity can send the first SR according to the instruction of the first entity.

[0153] Based on this possible implementation, the transmission of the random access preamble can be cancelled after uplink synchronization is restored. At this time, if a valid PUCCH resource exists, the first entity can instruct the second entity to transmit the first SR on that PUCCH resource, reducing the latency caused by the execution of random access. That is, compared with the scheme of still transmitting the random access preamble, the transmission latency of the first SR can be reduced.

[0154] Optionally, when the third condition is met, the first entity may also start the first timer. If the first entity receives an uplink synchronization indication before the first timer expires, the first entity may send the aforementioned indication information c to the second entity.

[0155] S902c, When the third condition is met, the first entity determines not to send a random access preamble indication to the second entity. The explanations of the third condition and the random access preamble can be found in the relevant descriptions in step S902b above, and will not be repeated here.

[0156] Optionally, after step S902c, if the first entity receives an uplink synchronization instruction and there is a valid PUCCH resource, the first entity may instruct the second entity to send a first SR on the PUCCH resource; if the first entity receives an uplink synchronization instruction but there is no valid PUCCH resource, the first entity may initiate a random access procedure and cancel the first SR.

[0157] Optionally, when the third condition is met, the first entity may also start a second timer. Further, step S903 may include: the first entity determining not to send a random access preamble indication to the second entity before the second timer expires.

[0158] Based on step S902c, when the first entity receives an uplink synchronization loss indication, i.e., the terminal device is in an uplink synchronization loss state, the first entity does not send a random access preamble indication to the second entity, i.e., it does not initiate random access. In other words, based on the constraint of the third condition, the terminal device can be prevented from initiating random access in the uplink synchronization loss state, thereby reducing the power consumption waste of the terminal device and the resource waste occupied by random access.

[0159] In some implementation scenarios, considering whether the terminal device is uplink synchronized: if the access network device has configured PUCCH resources for the SR, then when the first entity receives the uplink synchronization indication, the PUCCH resource can be considered valid. Furthermore, it can be assumed that uplink transmission within the serving cell is permitted. When the PUCCH resource is considered valid, the above can be applied. Figure 7 The method shown processes scheduling requests.

[0160] If the access network device has configured PUCCH resources for the SR, then when the first entity receives an uplink synchronization loss indication, it can be considered that the PUCCH resource is invalid, or in other words, the first entity does not have valid PUCCH resources. Furthermore, the first entity can clear its HARQ buffer and not perform any uplink transmissions in the serving cell.

[0161] It is understood that the methods and / or steps implemented by the terminal device in the above embodiments can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software such as chips or circuits) that can be used in the terminal device.

[0162] The foregoing mainly describes the solutions provided in this application. Accordingly, this application also provides a communication device for implementing the various methods described above. This communication device can be a terminal device as described in the above method embodiments, or a device containing the aforementioned terminal device, or a component that can be used in a terminal device, such as a chip or chip system.

[0163] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0164] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0165] Optionally, taking the terminal device in the above method embodiments as an example, the communication device is... Figure 11 A schematic diagram of a terminal device 110 is shown. The terminal device 110 includes a processing module 1101 and a communication module 1102.

[0166] In some embodiments, the terminal device 110 may further include a storage module. Figure 11 (Not shown in the image) is used to store program instructions and data.

[0167] In some embodiments, the communication module 1102, also known as a transceiver unit, is used to implement sending and / or receiving functions. The communication module 1102 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0168] In some embodiments, the communication module 1102 may include a receiving module and a sending module, respectively used to perform the receiving and sending steps performed by the terminal device in the above method embodiments, and / or other processes used to support the technology described herein; the processing module 1101 may be used to perform the processing steps (e.g., determining, generating, etc.) performed by the terminal device in the above method embodiments, and / or other processes used to support the technology described herein.

[0169] In one possible implementation:

[0170] Processing module 1101 is used by the first entity to determine that there is a first scheduling request (SR) in a waiting state. When a first condition is met, communication module 1102 is used by the first entity to instruct the second entity to send the first SR; the first condition includes: the first entity has a configured SR transmission opportunity on a valid physical uplink control channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication.

[0171] Optionally, the first entity not receiving an uplink synchronization loss indication includes: the first entity not receiving an uplink synchronization loss indication before the SR transmission timing.

[0172] Optionally, the first entity did not receive an uplink synchronization loss indication before the SR transmission timing, including: after the first SR was triggered, but before the SR transmission timing, the first entity did not receive an uplink synchronization loss indication.

[0173] Optionally, the first entity does not receive an uplink synchronization loss indication, including: the most recently received indication by the first entity is an uplink synchronization indication.

[0174] In another possible implementation:

[0175] Processing module 1101 is used to determine that a first scheduling request (SR) exists in a waiting state; when a second condition is met, processing module 1101 is further used to initiate a random access procedure and cancel the first SR; the second condition includes: the first entity does not have a valid physical uplink control channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication, wherein the valid PUCCH resource corresponds to the first SR. Alternatively,

[0176] When the third condition is met, the communication module 1102 is used to send a random access preamble indication to the second entity, or the processing module 1101 is used to determine that the first entity will not send a random access preamble indication to the second entity; the third condition includes: the first entity does not have a valid PUCCH resource, and the first entity receives an uplink synchronization loss indication; the random access preamble indication is used to instruct the second entity to send a random access preamble.

[0177] Optionally, if the first entity receives an uplink synchronization indication, the communication module 1102 is also used to send indication information from the first entity to the second entity, the indication information being used to cancel the transmission of the random access preamble.

[0178] Optionally, the communication module 1102 is also used for the first entity to instruct the second entity to send a first SR on a valid PUCCH resource.

[0179] Optionally, when the third condition is met, the processing module 1101 is further configured to start the first timer; the first entity receives the uplink synchronization indication, including: the first entity receives the uplink synchronization indication before the first timer expires.

[0180] Optionally, when the third condition is met, the processing module 1101 is further configured to start the second timer; the processing module 1101 is configured to determine that the first entity will not send a random access preamble indication to the second entity, including: the processing module 1101 is configured to determine that the first entity will not send a random access preamble indication to the second entity before the second timer expires.

[0181] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0182] In this application, the terminal device 110 is presented in an integrated manner, divided into various functional modules. Here, "module" may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0183] In some embodiments, those skilled in the art will recognize that the terminal device 110 can be implemented using the following hardware methods: Figure 6a The communication device 60 shown is in the form of [example device].

[0184] As an example, Figure 11 The function / implementation process of the processing module 1101 can be achieved through... Figure 6a The processor 601 in the communication device 60 shown calls computer execution instructions stored in the memory 603 to implement the communication. Figure 11 The function / implementation process of the communication module 1102 can be obtained through Figure 6a This is achieved through the communication interface 604 in the communication device 60 shown.

[0185] In some embodiments, when Figure 11 When the terminal device 110 is a chip or chip system, the function / implementation process of the communication module 1102 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1101 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0186] Since the terminal device 110 provided in this embodiment can execute the above method, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0187] As a possible product form, the terminal device described in the embodiments of this application can also be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0188] As another possible product form, the terminal device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, see [link to documentation]. Figure 12 , Figure 12 This is a schematic diagram of the structure of a communication device 1200 provided in an embodiment of this application. The communication device 1200 includes a processor 1201 and a transceiver 1202. The communication device 1200 can be a terminal device, or a chip or module therein. Figure 12 Only the main components of the communication device 1200 are shown. In addition to the processor 1201 and transceiver 1202, the communication device may further include a memory 1203.

[0189] Optionally, the processor 1201 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1203 is mainly used to store software programs and data. The transceiver 1202 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves.

[0190] Optionally, the processor 1201, transceiver 1202, and memory 1203 can be connected via a communication bus.

[0191] When the communication device is powered on, the processor 1201 can read the software program in the memory 1203, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1201 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1201. The processor 1201 converts the baseband signal into data and processes the data.

[0192] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0193] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0194] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0195] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0196] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0197] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0198] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0199] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0200] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0201] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

[0203] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0204] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes (or functions) described in the embodiments of this application are implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0205] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0206] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A scheduling request processing method, characterized in that, The method is applied to a terminal device, the terminal device including a first entity and a second entity, the first entity being located above the second entity, the method including: The first entity determines that there is a first scheduling request SR that is in a waiting state; When the first condition is met, the first entity instructs the second entity to send the first SR; the first condition includes: the first entity has a configured SR transmission opportunity on a valid physical uplink control channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication.

2. The method according to claim 1, characterized in that, The first entity did not receive an uplink synchronization loss indication, including: Prior to the SR transmission timing, the first entity did not receive the uplink synchronization loss indication.

3. The method according to claim 2, characterized in that, Prior to the SR transmission timing, the first entity did not receive the uplink synchronization loss indication, including: After the first SR is triggered, and before the SR transmission timing, the first entity does not receive the uplink synchronization loss indication.

4. The method of claim 1, wherein, The first entity did not receive an uplink synchronization loss indication, including: The latest instruction received by the first entity is an uplink synchronization instruction.

5. A scheduling request processing method, characterized in that, The method is applied to a terminal device, the terminal device including a first entity and a second entity, the first entity being located above the second entity, the method including: The first entity determines that there is a first scheduling request SR that is in a waiting state; When the second condition is met, a random access procedure is initiated and the first SR is cancelled; the second condition includes: the first entity does not have a valid Physical Uplink Control Channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication, wherein the valid PUCCH resource corresponds to the first SR.

6. The method of claim 5, wherein, After the first entity sends a random access preamble indication to the second entity, the method further includes: If the first entity receives an uplink synchronization instruction, the first entity sends an instruction message to the second entity, the instruction message being used to cancel the transmission of the random access preamble.

7. The method of claim 6, wherein, The method further includes: the first entity instructing the second entity to send the first SR on a valid PUCCH resource.

8. A terminal device, comprising: The terminal device includes: a processing module and a communication module; The processing module is used to determine, by the first entity of the terminal device, the existence of a first scheduling request SR that is in a waiting state. When the first condition is met, the communication module is used to instruct the second entity of the terminal device to send the first SR; the first condition includes: the first entity has a configured SR transmission opportunity on a valid Physical Uplink Control Channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication, and the first entity is located above the second entity.

9. The terminal device according to claim 8, characterized by The first entity did not receive an uplink synchronization loss indication, including: Prior to the SR transmission timing, the first entity did not receive the uplink synchronization loss indication.

10. The terminal device according to claim 9, characterized by Prior to the SR transmission timing, the first entity did not receive the uplink synchronization loss indication, including: After the first SR is triggered, and before the SR transmission timing, the first entity does not receive the uplink synchronization loss indication.

11. The terminal device according to claim 8, characterized by The first entity did not receive an uplink synchronization loss indication, including: The latest instruction received by the first entity is an uplink synchronization instruction.

12. A terminal device, comprising: The terminal device includes: a processing module and a communication module; The processing module is used to determine, by the first entity of the terminal device, the existence of a first scheduling request SR that is in a waiting state. When the second condition is met, the processing module is further configured to initiate a random access procedure and cancel the first SR; the second condition includes: the first entity does not have a valid physical uplink control channel (PUCCH) resource, and the first entity has not received an uplink synchronization loss indication, wherein the valid PUCCH resource corresponds to the first SR.

13. The terminal device according to claim 12, characterized in that, After the first entity sends a random access preamble indication to the second entity of the terminal device... If the first entity receives an uplink synchronization instruction, the communication module is further configured to send instruction information from the first entity to the second entity, the instruction information being used to cancel the transmission of the random access preamble, the first entity being located above the second entity.

14. The terminal device according to claim 13, characterized in that, The communication module is further configured to instruct the second entity to send the first SR on a valid PUCCH resource.

15. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-4, or to cause the communication device to perform the method as described in any one of claims 5-7.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-4 to be performed, or cause the method described in any one of claims 5-7 to be performed.

17. A computer program product, characterised in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, they cause the method as described in any one of claims 1-4 to be performed, or cause the method as described in any one of claims 5-7 to be performed.

Images