Scheduling request processing method and apparatus

Abstract

The scheduling request processing method and apparatus are applicable to non-terrestrial NTN scenarios. The method includes a first entity determining that there is a first scheduling request SR in a pending state. When the first condition is satisfied, the first entity instructs the second entity to transmit the first SR. The first condition includes that the first entity has an SR transmission occasion on a valid physical uplink control channel PUCCH resource for the scheduled SR, and that the first entity has not received an uplink synchronization loss instruction. Based on this solution, in order for the first entity to instruct the second entity to transmit the first SR when it has an SR transmission occasion on a valid physical uplink control channel PUCCH resource for the scheduled SR, at least the condition that the first entity has not received an uplink synchronization loss instruction must be satisfied. In other words, terminal devices are restricted from transmitting SRs when uplink synchronization is lost, reducing power waste on terminal devices and reducing the waste of resources occupied for SR transmission.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and in particular to a scheduling request processing method and apparatus.

Background Art

[0002] A scheduling request (SR) is mainly used to request uplink resources for new transmissions. The SR can be triggered in scenarios such as beam failure recovery, preemptive buffer status reporting, or consistent listen before talk failure recovery.

[0003] After the SR is triggered, the SR can be considered to be in a pending state. For a pending SR, if there is no available physical uplink control channel (PUCCH) resource, the terminal device starts a random access procedure and cancels the SR. If there is an available PUCCH resource and the maximum number of transmissions of the SR has not been reached, the terminal device uses the PUCCH resource to transmit the SR.

[0004] However, in some scenarios, the terminal device may be in an out-of-synchronization state or an uplink synchronization state. Therefore, in scenarios where it is considered whether the terminal device is synchronized, how to process a pending SR is an urgent problem to be solved currently.

Summary of the Invention

[0005] The present application provides a scheduling request processing method and apparatus. In a scenario where the synchronization state of the terminal device is considered, in order to transmit a pending SR, at least the condition that the first entity has not received an uplink synchronization loss indication needs to be satisfied.

[0006] A scheduling request processing method is provided according to the first aspect. The method may be performed by a terminal device, or by a component of the terminal device, such as the processor, chip, or chip system of the terminal device, or by a logic module or software capable of implementing all or part of the functionality of the terminal device. The method includes a first entity determining that there is a first scheduling request SR in a pending state. When the first condition is satisfied, the first entity instructs a second entity to transmit the first SR. The first condition includes the first entity having an SR transmission occasion on a valid physical uplink control channel PUCCH resource for the configured SR, and the first entity has not received an uplink synchronization loss instruction.

[0007] Based on this solution, when the first entity has an SR transmission occasion on a valid physical uplink control channel PUCCH resource for a configured SR, at least the condition that the first entity has not received an uplink synchronization loss instruction must be satisfied in order for the first entity to instruct the second entity to transmit the first SR. In other words, even if the first entity has an SR transmission occasion on a valid PUCCH resource for a configured SR, if the first entity has received an uplink synchronization loss instruction (i.e., the terminal device is in an uplink synchronization out state), the first entity cannot instruct the second entity to transmit the first SR.

[0008] In other words, based on the restriction of the first condition, it may be possible to prevent a terminal device from sending an SR when uplink synchronization is lost. Even if a terminal device were to send an SR when uplink synchronization is lost, the access network device would fail to receive the SR because the terminal device's uplink synchronization is lost. Therefore, terminal devices are restricted from sending SRs when uplink synchronization is lost. This reduces power consumption by the terminal device and reduces the waste of resources occupied by sending SRs.

[0009] In a possible design, the first entity not receiving an uplink loss of synchronization instruction includes the first entity not receiving an uplink loss of synchronization instruction prior to the SR transmission occasion.

[0010] In a possible design, the first entity not receiving an uplink loss of synchronization instruction prior to an SR transmission occasion includes the first entity not receiving an uplink loss of synchronization instruction after the first SR is triggered and prior to an SR transmission occasion.

[0011] In a possible design, the fact that the first entity has not received an uplink synchronization loss instruction includes the fact that the most recent instruction received by the first entity is an uplink synchronization instruction.

[0012] A scheduling request processing method is provided according to the second aspect. The method may be performed 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 functionality of the terminal device. The method includes a first entity determining that there is a first scheduling request SR in a pending state. When the second condition is satisfied, a random access procedure is initiated and the first SR is canceled. When the third condition is satisfied, the first entity decides to send a random access preamble instruction to the second entity, or the first entity decides not to send a random access preamble instruction to the second entity. The second condition includes that the first entity does not have a valid physical uplink control channel PUCCH resource and the first entity has not received an uplink loss of synchronization instruction. The third condition includes that the first entity does not have a valid PUCCH resource and the first entity has received an uplink loss of synchronization instruction. The random access preamble instruction instructs the second entity to send a random access preamble. A valid PUCCH resource corresponds to the first SR.

[0013] Based on this solution, in order for the first entity to initiate a random access procedure and cancel the first SR when it does not have a valid PUCCH resource, at least the condition that the first entity has not received an uplink loss of synchronization instruction must be satisfied. In other words, even if the first entity does not have a valid PUCCH resource, if the first entity receives an uplink loss of synchronization instruction (i.e., the terminal device is in an uplink out-of-sync state), the first entity cannot initiate a random access procedure. In other words, based on the restriction of the second condition, it is possible to prevent the terminal device from initiating random access while in an uplink out-of-sync state, thereby reducing power waste on the terminal device and reducing the waste of resources occupied for random access.

[0014] Furthermore, if the first entity receives an uplink synchronization loss instruction, that is, if the terminal device is in an uplink synchronization out state, the first entity does not send a random access preamble instruction to the second entity, that is, does not initiate random access. In other words, based on the restriction of the third condition, it is possible to prevent the terminal device from initiating random access while in an uplink synchronization out state, thereby reducing power waste on the terminal device and reducing the waste of resources occupied for random access.

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

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

[0017] Based on the two possible implementations described above, the transmission of the random access preamble may be canceled after uplink synchronization is restored. In this case, if a valid PUCCH resource exists, the first entity can instruct the second entity to transmit the first SR on the PUCCH resource, thereby reducing the latency caused by the execution of random access. In other words, the latency in transmitting the first SR may be reduced compared to a solution in which the random access preamble is still transmitted.

[0018] In a possible design, when the third condition is satisfied, the method further includes activating the first timer. The first entity receiving an uplink synchronization instruction includes the first entity receiving the uplink synchronization instruction before the first timer terminates.

[0019] In a possible design, the method further includes initiating a second timer when the third condition is satisfied. The first entity's decision not to send a random access preamble instruction to the second entity includes the first entity deciding not to send a random access preamble instruction to the second entity before the second timer terminates.

[0020] A communication device is provided that is configured to carry out various methods according to the third aspect. The communication device may be a terminal device 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 corresponding modules, units, or means for carrying out the methods. The modules, units, or means may be carried out by hardware, software, or hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to a function.

[0021] In some possible designs, the communication device may include a processing module and a communication module. The processing module may be configured to implement processing functions in any one of the above aspects and any possible implementation thereof. The communication module may be configured to implement transmitting and / or receiving functions in any one of the above aspects and any possible implementation thereof. The communication module may include transceiver circuits, transceiver machines, transceivers, or communication interfaces.

[0022] In some possible designs, the communication module includes a transmitting module and / or a receiving module, each configured to implement a transmitting function or a receiving function in any one of the aspects described above and any possible implementation of the aspects described above.

[0023] In accordance with the fourth aspect, a communication device including a processor and a communication interface is provided. The communication interface is configured to communicate with a module outside the communication device, and the processor is configured to execute computer programs or instructions to cause the communication device to perform the method in either aspect. The communication device may be a terminal device in the first or second aspect, or a device included in a terminal device, such as a chip, a chip system, or a module.

[0024] A communication device is provided that includes at least one processor according to the fifth aspect. The processor is configured to execute computer programs or instructions stored in memory to cause the communication device to perform the method in either aspect. The memory may be coupled to the processor, or it may be independent of the processor. For example, the memory and the processor are two independent modules. The memory may be located outside the communication device, or it may be located inside the communication device. The communication device may be a terminal device in the first or second aspect, or a device included in a terminal device, such as a chip, a chip system, or a module.

[0025] According to a sixth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed on a communication device, the communication device is caused to execute the method in any one of the aspects.

[0026] According to a seventh aspect, a computer program product including instructions is provided. When the computer program product is executed on a communication device, the communication device is caused to execute the method in any of the aspects.

[0027] It can be understood that when the communication device provided in any one of the third to seventh aspects is a chip, the transmission operation / function can be understood as the output of information, and the reception operation / function can be understood as the input of information.

[0028] It can be understood that when the communication device provided in any one of the third to seventh aspects is a chip system, the communication device may include a chip, or may include a chip and other discrete components.

[0029] Regarding the technical effects brought about by any of the design methods in the third to seventh aspects, refer to the technical effects brought about by various design methods in the first or second aspect. Details are not described here again.

Brief Description of Drawings

[0030] [Figure 1] It is a diagram of the structure of the communication system according to the present application. [Figure 2] It is a diagram of the structure of the non-terrestrial network according to the present application. [Figure 3] It is a diagram of another structure of the non-terrestrial network according to the present application. [Figure 4] It is a diagram of yet another structure of the non-terrestrial network according to the present application. [Figure 5] It is a diagram of yet another structure of the non-terrestrial network according to the present application. [Figure 6a] This is a diagram showing the structure of the communication device relating to the present invention. [Figure 6b] This is a diagram showing the structure of the terminal device relating to the present invention. [Figure 7] This is a schematic flowchart of the scheduling request processing method related to the present invention. [Figure 8] This is a timeline diagram relating to the present application. [Figure 9] This is a schematic flowchart of another scheduling request processing method related to the present invention. [Figure 10a] This is a schematic flowchart of yet another scheduling request processing method relating to the present invention. [Figure 10b] This is another timeline diagram relating to the present application. [Figure 11] This is a diagram showing another structure of the terminal device relating to the present invention. [Figure 12] This is a diagram showing another structure of the communication device relating to the present invention. [Modes for carrying out the invention]

[0031] In the specification of this application, unless otherwise indicated, " / " indicates that the related objects are in an "or" relationship. For example, A / B may represent A or B. In this application, "and / or" indicates only the related relationship described for the related objects, and indicates that three relationships may exist. For example, A and / or B may represent that only A exists, both A and B exist, or only B exists, in the following three cases, where A and B may be singular or plural.

[0032] In the specification of this application, unless otherwise indicated, “multiple” means two or more. “At least one of the following items (parts)” or similar expressions refer to any combination of these items, including a single item (part) or any combination of multiple items (parts). For example, at least one item (part) of a, b, or c could be a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, and c may be singular or plural.

[0033] Furthermore, in order to clearly describe the technical solutions in the embodiments of this application, terms such as "first" and "second" are used in the embodiments of this application to distinguish between the same or similar items that provide essentially the same function or purpose. Those skilled in the art will understand that terms such as "first" and "second" do not limit the number or order of execution, and that terms such as "first" and "second" do not indicate a clear difference.

[0034] In embodiments of this application, terms such as “example” or “for example” are used to indicate that an example, illustration, or description is being given. No embodiment or design method described as “example” or “for example” in embodiments of this application should be described as being preferable or having more advantages than another embodiment or design method. Specifically, the use of terms such as “example” or “for example” is intended to present relevant concepts in a particular way for the sake of ease of understanding.

[0035] It should be understood that the “embodiments” described throughout this specification mean that certain features, structures, or characteristics relating to these embodiments are included in at least one embodiment of the present application. Therefore, embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. It should be understood that process sequence numbers do not imply execution order in the various embodiments of the present application. The execution order of processes should be determined based on the function and internal logic of the processes and should not be construed as any limitation to the implementation processes of the embodiments of the present application.

[0036] In this application, it can be understood that "case" and "when" refer to situations in which the corresponding process is performed under objective circumstances, is not intended to limit time, does not require a decision-making action during the process, and do not imply any other limitations.

[0037] In some scenarios, it may be understood that some optional features in embodiments of the present application can be implemented independently of other features, such as the solution on which the optional feature currently rests, in order to solve the corresponding technical problem and achieve the corresponding effect. Alternatively, in some scenarios, any feature may be combined with another feature on a case-by-case basis. Accordingly, the apparatus provided in embodiments of the present application may also implement these features or functions accordingly. Details are not described.

[0038] In this Application, unless otherwise indicated, identical or similar parts in the embodiments should be referenced to one another. In the various embodiments of this Application, unless otherwise stated or unless there is a logical contradiction, the terminology and / or descriptions in different embodiments are consistent and mutually referential, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments. Subsequent implementation of this Application is not intended to limit the scope of protection of this Application.

[0039] To facilitate understanding of the technical solutions in the embodiments of this application, the relevant technology of this application will first be briefly described below.

[0040] 1. Scheduling request (SR)

[0041] SR is primarily used to request new uplink (UL) resources for transmission, such as uplink shared channel (UL-SCH) resources.

[0042] Generally, when a Scheduling Request (SR) is configured on a network, a Scheduling Request Resource (SR resource) is configured for the SR. This SR resource is located on a physical uplink control channel (PUCCH) resource. For example, a base station can configure an SR transmission occasion on a PUCCH resource and configure a frequency domain resource location as the SR resource. Therefore, an SR configured on a network can also be considered to have a corresponding (configured) PUCCH resource.

[0043] For example, possible SR resource configuration methods can be shown as follows: SR Resource Configuration (SchedulingRequestResourceConfig)::= SEQUENCE{ SR resource identifier (schedulingRequestResourceId); SR identifier (schedulingRequestID); Period and offset; resource; }

[0044] The SR resource identifier identifies the SR resource in PUCCH. The SR identifier identifies the SR or SR setting. The period and offset indicate the SR period and the number of offset symbols or slots. The resource includes the identifier of the PUCCH resource, and the PUCCH resource is the PUCCH resource in which the SR resource is located, that is, in other words, the PUCCH resource corresponding to the SR.

[0045] After an SR (Service 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. For an SR in a pending state:

[0046] If a media access control (MAC) entity does not have a valid PUCCH, the terminal device initiates a random access procedure and cancels any pending SRs.

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

[0048] Please note that the "pending state" in the embodiments of this application may also be called the "state to be transmitted," and that "pending state" and "state to be transmitted" are synonymous.

[0049] 2. Non-terrestrial network (NTN)

[0050] As communication requirements evolve, fifth-generation (5G) networks and future advanced networks need to not only meet multiple service requirements but also provide broader service coverage. NTN is less affected by geographical conditions and can achieve the goal of global coverage. Therefore, NTN is an important direction for future communication development.

[0051] Compared to conventional terrestrial networks, NTN uses typical flight platforms (e.g., airplanes or unmanned aerial vehicles) or satellites to participate in network deployment. For example, a base station or part of a base station's functions may be located on a flight platform or satellite to provide coverage for terminals, or the flight platform or satellite may be used as a relay to forward signals from ground base stations to provide coverage for terminals.

[0052] At NTN, satellite orbit information or flight platform flight information (e.g., flight platform position, velocity, and flight path) plays a crucial role in communications. Satellite communications are used as an example. A terminal device can determine the end-to-end latency from the terminal device to the base station by using satellite orbit information, the terminal device's position, and information about the latency from the satellite to the satellite gateway. In this way, pre-compensation for timing advance is performed based on the end-to-end latency. Furthermore, the network can understand the timing advance of the terminal device to perform more appropriate data scheduling.

[0053] However, satellite orbit information is time-sensitive. Therefore, NTN has implemented a validity timer. After receiving satellite orbit information, the radio resource control (RRC) entity of the terminal device may activate the validity timer. Before the validity timer expires, the orbit information is accurate and valid, and the terminal device is uplink synchronized. After the validity timer expires, the orbit information becomes invalid, and the terminal device is out of uplink synchronized state; in other words, uplink synchronization is lost. After receiving orbit information again, the terminal device recovers uplink synchronized state.

[0054] Furthermore, after receiving orbital information, the RRC entity may send an uplink synchronization instruction to the MAC entity to indicate that the terminal device is in a synchronized state. When the validity timer expires, the RRC entity may send an uplink synchronization loss instruction to the MAC entity to indicate that the uplink synchronization of the terminal device has been lost, or that the terminal device is in an uplink synchronization out state.

[0055] When a terminal device is out of uplink sync, it clears its hybrid automatic repeat request (HARQ) buffer and stops sending uplink signals, such as MAC control element (MAC CE) or RRC messages. In an out-of-uplink state, the base station cannot properly receive uplink signals from the terminal device.

[0056] As mentioned above, the current SR processing method requires terminal devices to initiate a random access procedure or transmit an SR when an SR is in a pending state. However, NTN requires terminal devices to stop transmitting uplink signals when they are out of uplink synchronization. Therefore, how to handle pending SRs in scenarios where terminal device synchronization is a consideration is an urgent issue that needs to be resolved now.

[0057] In light of this, the present invention provides an SR processing method. In this method, in order to transmit an SR in a pending state, a valid PUCCH resource must be available, and the terminal device must be in an uplink synchronized state. Therefore, the terminal device is prevented from transmitting an SR when uplink synchronization is lost, thereby reducing power consumption and resource waste of the terminal device.

[0058] The technical solutions in the embodiments of this application can be applied to a variety of communication systems. These communication systems may include third-generation partnership project (3GPP) communication systems, 5G systems such as long-term evolution (LTE) systems or new radio (NR) 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, the Internet of Things (IoT), or future advanced communication systems. Alternatively, the communication system may be a non-3GPP communication system. This is not limited to these.

[0059] The technical solutions in the embodiments of the present invention can be applied to various communication scenarios, for example, one or more of the following: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), D2D, V2X, and IoT.

[0060] The above-mentioned communication systems and scenarios applicable to this application are merely examples for illustrative purposes, and the communication systems and scenarios applicable to this application are not limited to them. The communication systems and scenarios applicable to this application do not constitute any limitation to the scenarios of this application. This is described uniformly here. Further details are not described below.

[0061] Figure 1 shows a communication system 10 applicable to the solution of the present application provided herein. The communication system 10 includes at least one terminal device 101 and at least one access network device 102. The number of terminal devices and access network devices in Figure 1 is merely an example, and there may be more or fewer terminal devices and access network devices.

[0062] Optionally, the terminal device 101 in the embodiments of the present invention may be a user-side device configured to implement wireless communication functionality, such as a terminal or a chip that can be used in a terminal. The terminal may be user equipment (UE), access terminal, terminal unit, terminal station, mobile station, remote station, remote terminal, mobile device, or a wireless communication device, terminal agent, terminal device in a 5G network or a 5G or later evolved public land mobile network (PLMN). Access terminals may include 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 wireless modems, 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, and the like. Alternatively, the terminal may be a terminal with IoT communication capabilities, such as a V2X terminal (e.g., Internet of Vehicle Device), a D2D communication terminal, or a M2M communication terminal. The terminal may be mobile or fixed.

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

[0064] For example, access network devices may include evolved base stations (NodeB, eNB, or e-NodeB, evolved NodeB) in LTE or LTE-A systems, such as conventional macro base station eNBs and micro base station eNBs in heterogeneous network scenarios. Alternatively, access network devices may include next-generation NodeBs (gNBs) in NR systems. Alternatively, access network devices may include transmission reception points (TRPs), home evolved NodeBs (e.g., home evolved NodeBs, or home NodeBs, HNBs), baseband units (BBUs), baseband pools (BBU pools), or wireless fidelity (Wi-Fi) access points (APs). Alternatively, access network devices may include base stations in NTN, i.e., they may be located on flight platforms or satellites. NTN states that access network devices may be used as Layer 1 (L1) relays, base stations, or integrated access and backhaul (IAB) nodes. Alternatively, access network devices may be devices that implement base station functions in IoT, such as devices that implement base station functions in V2X, D2D, or machine-to-machine (M2M) networks.

[0065] Alternatively, an access network device may be a module or unit capable of implementing some of the functions of a base station. For example, an access network device may be a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), a radio unit (RU), etc. Alternatively, an access network device may be an access network device in an open radio access network (open RAN, ORAN) system, or a module of an access network device. In an ORAN system, a CU may also be called an open (O)-CU, a DU may also be called an O-DU, a CU-CP may also be called an O-CU-CP, a CU-UP may also be called an O-CU-UP, and a RU may also be called an O-RU.

[0066] CU and DU can be arbitrarily divided into the protocol layers of a wireless network. For example, the functions of the packet data convergence protocol (PDCP) layer and the protocol layers above the PDCP layer (e.g., the RRC layer and the service data adaptation protocol (SDAP) layer) are set in the CU, while the functions of the protocol layers below the PDCP layer (e.g., the radio link control (RLC) layer, MAC layer, or physical (PHY) layer) are set in the DU. Alternatively, the functions of the protocol layers above the PDCP layer are set in the CU, while the functions of the PDCP layer and the protocol layers below the PDCP layer are set in the DU. This is not limited to this.

[0067] The above division of CU and DU processing functions based on protocol layers is merely an example and can be done in other ways. For example, a CU or DU may have more protocol layer functions. Another example is that a CU or DU may have only a portion of the protocol layer processing functions. For example, some of the RLC layer functions and the functions of protocol layers above the RLC layer may be set in the CU, while the remaining RLC layer functions and the functions of protocol layers below the RLC layer may be set in the DU. Another example is that the functions of a CU or DU may be divided based on service type or other system requirements, for example, based on latency. Functions whose processing time must meet latency requirements may be set in the DU, while functions whose processing time does not need to meet latency requirements may be set in the CU.

[0068] Optionally, the base stations in the embodiments of the present invention may include various types of base stations, such as macro base stations, micro base stations (which may also be called small cells), relay stations, access points, home base stations, TRPs, transmitting points (TPs), and mobile switching centers. This is not particularly limited in the embodiments of the present invention.

[0069] In possible implementations, as shown in Figure 2, the access network device 102 may be located on the ground as part of the terrestrial network and communicate with the data network via the core network. In this case, the communication system 10 provided herein may further include relay devices located on a flight platform or satellite. The relay devices function as Layer 1 relays (L1 relays), reproducing physical layer signals and forwarding them to terminal devices or access network devices.

[0070] In another possible implementation, as shown in Figure 3, the access network device 102 may be located on a flight platform or satellite, implementing the functions of a ground station, communicating directly with the core network, and further communicating with the data network via the core network.

[0071] In yet another possible implementation, as shown in Figure 4, the access network device 102 may be located on a flight platform or satellite, implement ground station functions, communicate directly with the core network, and further communicate with the data network via the core network. Furthermore, inter-satellite links (ISLs) may exist between access network devices carried on different flight platforms or satellites, and the access network devices may communicate with each other via the ISLs.

[0072] In yet another possible implementation, as shown in Figure 5, the access network device 102 may include a DU located on a flight platform or satellite and a CU located on the ground. The DU located on the flight platform or satellite communicates with the CU located on the ground via an FI interface. The CU located on the ground communicates with the core network and further communicates with the data network via the core network.

[0073] It should be noted that the communication systems described in the embodiments of this application are intended to provide a clearer description of the technical solutions in the embodiments of this application and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will recognize that, with advancements in network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical challenges.

[0074] Optionally, the relevant functions of the terminal device or access network device in this application may be implemented by the communication device 60 shown in Figure 6a. Please refer to Figure 6a. The communication device 60 includes one or more processors 601. Furthermore, the communication device 60 may further include a communication bus 602 and at least one interface (Figure 6a is merely an example, and an example in which the communication device 60 includes a communication interface 604 and one processor 601 is used for illustrative purposes). Optionally, the communication device 60 may further include a memory 603.

[0075] The processor 601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), one or more integrated circuits configured to control program execution in the solution of the present invention, or a processing core configured to process data (e.g., computer program instructions). The processor may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.

[0076] In a specific implementation, the processor 601 may include one or more CPUs, for example, CPU0 and CPU1 shown in Figure 6a.

[0077] The communication bus 602 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. Buses can be classified into address buses, data buses, control buses, etc. For ease of representation, only one thick line is used in Figure 6a for representation; however, this does not indicate that only one bus or only one type of extension exists. The communication bus 602 is configured to connect different components within the communication device 60, thereby enabling these components to communicate and interact with one another.

[0078] The communication interface 604 may be a transceiver module and is configured to communicate with other devices or a communication network. The communication network may be, for example, Ethernet, a radio access network (RAN), a wireless local area network (WLAN), etc. For example, the communication interface 604 may be a device such as a transceiver or a transceiver machine. Alternatively, the communication interface 604 may be a transceiver circuit located on the processor 601 and is configured to perform signal input and signal output for the processor.

[0079] Memory 603 may be a device having a storage function. For example, memory 603 may 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 compact disc storage, optical disc storage (compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray optical disc, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing expected program code in the form of instructions or data structures and accessible by a computer. This is not limited to these. Memory may exist independently and be connected to the processor via communication bus 602. Alternatively, memory may be integrated with the processor.

[0080] Memory 603 is configured to store computer-executable instructions for performing the solution of the present invention, and the processor 601 controls the execution. The processor 601 is configured to execute the computer-executable instructions stored in memory 603 to implement the method provided in the embodiments of the present invention.

[0081] Alternatively, optionally, in embodiments of the present application, the processor 601 may perform processing-related functions in the manner provided in subsequent embodiments of the present application, and the communication interface 604 may engage in communication with other devices or communication networks. This is not particularly limited in embodiments of the present application.

[0082] Optionally, computer executable instructions in embodiments of the present invention may also be called application program code. This is not particularly limited in embodiments of the present invention.

[0083] In specific implementations, 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 multiple 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, a projector, etc. The input device 606 communicates with the processor 601 and can receive user input in multiple ways. For example, the input device 606 may be a mouse, a keyboard, a touchscreen device, a sensing device, etc.

[0084] It should be noted that the configuration shown in Figure 6a does not constitute a limitation on the communication device. In addition to the components shown in Figure 6a, the communication device may include more or fewer components than shown in the figure, or it may combine several components, or it may have a different arrangement of components.

[0085] Figure 6b is a diagram of another structure of a terminal device according to an embodiment of the present application. Please refer to Figure 6b. The terminal device may include a first entity and a second entity. Optionally, the terminal device may further include a third entity. The first entity is located above the second entity. In other words, the first entity is a superstructure entity of the second entity. Furthermore, the first entity is located below the third entity. In other words, the first entity is a substructure entity of the third entity.

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

[0087] It should be noted that the structure shown in Figure 6b does not constitute a limitation on terminal devices. In addition to the entities shown in Figure 6b, terminal devices may include more or fewer entities than those shown. For example, terminal devices may further include RLC entities, PDCP entities, etc. This is not particularly limited in this application.

[0088] The following describes in detail the scheduling request processing method provided in the embodiments of the present application with reference to the attached drawings. In the embodiments of the present application, it can be understood that a terminal device may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples. In the embodiments of the present application, other operations and various variations of operations may be performed further. Furthermore, the steps may be performed in an order different from the order presented in the embodiments of the present application, and it is not necessary for all operations in the embodiments of the present application to be performed.

[0089] In the example, the subsequent embodiments may be applied to NTN scenarios, such as satellite communications scenarios, or other scenarios in NTN, such as low-altitude platform (LAP) subnetwork scenarios or high-altitude platform (HAP) subnetwork scenarios. This is not particularly limited.

[0090] Furthermore, subsequent embodiments may be applied to alternative possible communication scenarios or communication systems. For example, in long-distance communication scenarios where the distance between the terminal device and the access network device is long or the relative travel speed is fast, or in communication scenarios where the terminal device may be in a synchronized or out-of-sync state, scheduling requests may be handled by using the method provided in the embodiments of the present application.

[0091] Figure 7 shows the scheduling request processing method according to the present invention. The scheduling request processing method is applied to a terminal device. Please refer to Figure 7. The scheduling request processing method includes the following steps.

[0092] S701: The first entity determines that there is a first SR in a pending state.

[0093] Optionally, the first SR may be triggered by one or more of the following events: beam failure recovery, preemptive buffer state report, timing advance report, or consistent listen before talk failure recovery. After the first SR is triggered, the first entity may become aware that there are first SRs in a pending state. In other words, the first entity may determine that there are first SRs in a pending state.

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

[0095] The first condition includes the first entity having an SR transmission occasion on the valid PUCCH resource for SR configured, and the first entity not having received an uplink synchronization loss instruction.

[0096] Optionally, the first entity having an SR transmission occasion on a valid PUCCH resource for a configured SR may be understood as the first entity having at least one valid PUCCH resource for a configured SR.

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

[0098] Optionally, an uplink synchronization loss indicator may indicate that a terminal device has lost uplink synchronization, is in an uplink synchronization out state, or has lost uplink synchronization with a serving cell.

[0099] Optionally, an uplink synchronization loss instruction may be generated by a third entity and sent to the first entity. For example, the third entity may maintain a timer related to the synchronization state (e.g., a validity timer) and send an uplink synchronization loss instruction or an uplink synchronization instruction to the first entity based on the execution state of the timer.

[0100] For example, when a third entity receives satellite orbit information or flight platform flight information (e.g., the position, velocity, or flight path of the flight platform), it may activate a validity timer and send an uplink synchronization instruction to the first entity to indicate that the terminal device is in an uplink synchronized state or synchronized with the serving cell. Furthermore, when the timer expires, an uplink synchronization loss instruction is sent to the first entity. The timer duration can be understood as the validity period of the activation information or flight information.

[0101] Therefore, in this scenario, the fact that the first entity has not received an uplink synchronization loss instruction may include the fact that the first entity has not received an uplink synchronization loss instruction from the third entity.

[0102] Optionally, the first SR may be triggered before the validity timer terminates or after the validity timer terminates. This is not particularly limited in this application.

[0103] In possible implementations, the fact that the first entity has not received an uplink synchronization loss instruction may include the most recent (or last) instruction received by the first entity being an uplink synchronization loss instruction. For example, the most recent (or last) received instruction may be understood as the last received instruction prior to the present moment, which may be, for example, the time when the determination of the first condition is made.

[0104] For example, as shown in Figure 8(a), the current time is denoted as time t1. If the first entity receives an uplink synchronization loss instruction at time t2 and an uplink synchronization instruction at time t3, the most recent (or last) instruction received by the first entity is the uplink synchronization instruction. This is the scenario where the first entity has not received an uplink synchronization loss instruction.

[0105] As shown in Figure 8(b), the current time is denoted as time t1. If the first entity receives an uplink synchronization instruction at time t2 and an uplink synchronization loss instruction at time t3, the most recent (or last) instruction received by the first entity is the uplink synchronization loss instruction. This is the scenario in which the first entity receives an uplink synchronization loss instruction.

[0106] In another possible implementation, the first entity not receiving an uplink loss of synchronization instruction may include the first entity not receiving an uplink loss of synchronization instruction prior to an SR transmission occasion. Furthermore, the method may include the first entity not receiving an uplink loss of synchronization instruction after the first SR is triggered and prior to an SR transmission occasion. An SR transmission occasion is an SR transmission occasion set up on a valid PUCCH resource.

[0107] For example, as shown in Figure 8(c), assume that the first SR is triggered at time t4 and the SR transmission occasion is at time t5. If the first entity does not receive an uplink sync loss instruction between time t4 and time t5, this is the scenario where the first entity does not receive an uplink sync loss instruction. If the first entity does receive an uplink sync loss instruction between time t4 and time t5, this is the scenario where the first entity receives an uplink sync loss instruction.

[0108] Optionally, the first condition may further include that the number of transmissions of the first SR is less than the maximum number of transmissions of the SR. The maximum number of transmissions of the SR may be set by the access network device. Certainly, the first condition may further include other limiting conditions, which are not particularly limited in this application.

[0109] Optionally, the first entity instructing the second entity to transmit a first SR may include the first entity transmitting instruction information a to the second entity. Instruction information a instructs the second entity to transmit the first SR. Upon receiving instruction information a, the second entity may transmit the first SR on an SR transmission occasion.

[0110] Based on the above solution, if the first entity has an SR transmission occasion on a valid PUCCH resource for the configured SR, at least the condition that the first entity has not received an uplink sync loss instruction must be satisfied in order for the first entity to instruct the second entity to transmit the first SR. In other words, even if the first entity has an SR transmission occasion on a valid PUCCH resource for the configured SR, if the first entity has received an uplink sync loss instruction (i.e., the terminal device is in an uplink sync loss state), the first entity cannot instruct the second entity to transmit the first SR.

[0111] In other words, based on the restriction of the first condition, it may be possible to prevent a terminal device from sending an SR when uplink synchronization is lost. Even if a terminal device were to send an SR when uplink synchronization is lost, the access network device would fail to receive the SR because the terminal device's uplink synchronization is lost. Therefore, terminal devices are restricted from sending SRs when uplink synchronization is lost. This reduces power consumption by the terminal device and reduces the waste of resources occupied by sending SRs.

[0112] Figure 9 shows another scheduling request processing method according to the present invention. This scheduling request processing method is applied to a terminal device. Please refer to Figure 9. The scheduling request processing method includes the following steps.

[0113] S901: The first entity determines that there is a first SR in a pending state. For details on performing step S901, please refer to the relevant description in step S701. Further details are not provided here.

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

[0115] S902a: When the second condition is met, start the random access procedure and cancel the first SR.

[0116] The second condition includes that the first entity does not have a valid PUCCH resource and that the first entity has not received an uplink synchronization loss instruction. A valid PUCCH resource corresponds to the first SR. In other words, the PUCCH resource is the PUCCH resource set up for the first SR.

[0117] Optionally, the absence of a valid PUCCH resource for the first entity may include the PUCCH resource configured for the first SR being occupied by another service. In other words, the frequency domain resource configured for the first SR and corresponding to the SR transmission occasions on the PUCCH resource is occupied by another service.

[0118] For an explanation of the uplink synchronization loss instruction and why the first entity has not received the uplink synchronization loss instruction, please refer to the relevant description in step S702. Further details are not provided here.

[0119] If the first entity does not have a valid PUCCH resource based on step S902a, in order to initiate a random access procedure and cancel the first SR, at least the condition that the first entity has not received an uplink loss of synchronization instruction must be satisfied. In other words, even if the first entity does not have a valid PUCCH resource, if the first entity receives an uplink loss of synchronization instruction (i.e., the terminal device is in an uplink out-of-sync state), the first entity cannot initiate a random access procedure. In other words, based on the restriction of the second condition, it is possible to prevent the terminal device from initiating random access while in an uplink out-of-sync state, thereby reducing power waste on the terminal device and reducing the waste of resources occupied for random access.

[0120] S902b: When the third condition is met, the first entity sends a random access preamble instruction to the second entity. The random access preamble instruction instructs the second entity to send a random access preamble.

[0121] The third condition includes that the first entity does not have a valid PUCCH resource and that the first entity has received an uplink synchronization loss instruction.

[0122] Optionally, the fact that a first entity has received an uplink loss of synchronization instruction may include the most recent instruction received by the first entity being an uplink loss of synchronization instruction, or the first entity receiving an uplink loss of synchronization instruction after the first SR has been triggered and before the SR transmission occasion set for the first SR.

[0123] In possible implementations, the absence of a valid PUCCH resource for the first entity may include the PUCCH resource configured for the first SR being occupied by another service. In other words, the frequency domain resource configured for the first SR and corresponding to the SR transmission occasions on the PUCCH resource is occupied by another service.

[0124] In another possible implementation, the absence of a valid PUCCH resource by the first entity may actually include the first entity having an SR transmission occasion on a valid PUCCH resource for a configured SR, but the first entity considers the PUCCH resource invalid because it has received an uplink synchronization loss instruction.

[0125] According to the two possible implementations described above, if the first entity receives an uplink synchronization loss instruction, the first entity considers the PUCCH resource invalid, regardless of whether the PUCCH resource corresponding to the first SR is occupied or whether a PUCCH resource corresponding to the first SR exists.

[0126] Optionally, after receiving a random access preamble instruction, the second entity may send a random access preamble on a configured random access occasion.

[0127] Optionally, the first entity may further transmit instruction information b to the second entity. Instruction information b may indicate a period (denoted as Lifetime 1). In this scenario, the random access preamble instruction and instruction information b together may instruct the second entity to transmit a random access preamble on a random access occasion after Lifetime 1. For example, the start of Lifetime 1 may be the point at which the second entity receives the instruction information and marks the end of Lifetime 1.

[0128] Optionally, after the first entity sends a random access preamble instruction to the second entity, the first entity may receive an uplink synchronization instruction. For example, if the third entity sends an uplink synchronization loss instruction to the first entity and then receives satellite orbit information or flight platform flight information again, the third entity may send an uplink synchronization instruction to the first entity to indicate uplink synchronization recovery.

[0129] In this scenario, as shown in Figure 10a, after step S902b, the scheduling request processing method provided in this embodiment of the Application may further include the first entity sending instruction information c to the second entity. The instruction information c is used to cancel the transmission of the random access preamble. In other words, the instruction information c instructs the second entity to cancel the transmission of the random access preamble.

[0130] Optionally, if the second entity has not sent a random access preamble after receiving instruction information c, the second entity may cancel sending the random access preamble. For example, the reason the second entity has not sent a random access preamble may be that a random access occasion has not occurred, or that the second entity received instruction information c within the specified period (for example, the start time is when the second entity receives instruction information b and marks the end of life period 1, and the life period is life period 1).

[0131] For example, as shown in Figure 10b, an example is used where the second entity receives a random access preamble instruction at time t1 and the random access occasion is at time t2. If the second entity receives instruction information c at time t3, the second entity cancels sending the random access preamble.

[0132] Optionally, as shown in Figure 10a, after the first entity receives an uplink synchronization instruction, the first entity may further instruct the second entity to transmit a first SR on a valid PUCCH resource. Correspondingly, the second entity may transmit the first SR in accordance with the instructions of the first entity.

[0133] Based on feasible implementations, the transmission of the random access preamble may be canceled after uplink synchronization is restored. In this case, if a valid PUCCH resource exists, the first entity can instruct the second entity to transmit the first SR on the PUCCH resource, thereby reducing the latency caused by the execution of random access. In other words, the latency in transmitting the first SR may be reduced compared to a solution in which the random access preamble is still transmitted.

[0134] Optionally, when the third condition is satisfied, the first entity may further activate the first timer. If the first entity receives an uplink synchronization instruction before the first timer terminates, the first entity may send instruction information c to the second entity.

[0135] S902c: When the third condition is satisfied, the first entity decides not to send a random access preamble instruction to the second entity. For a description of the third condition and the random access preamble, see the relevant description in step S902b. Further details are not provided here.

[0136] Optionally, after step S902c, if the first entity receives an uplink synchronization instruction and has a valid PUCCH resource, the first entity may instruct the second entity to send the first SR on the PUCCH resource. If the first entity receives an uplink synchronization instruction but does not have a valid PUCCH resource, the first entity may initiate a random access procedure and cancel the first SR.

[0137] Optionally, when the third condition is satisfied, the first entity may further activate the second timer. Furthermore, step S903 may include the first entity deciding not to send a random access preamble instruction to the second entity before the second timer terminates.

[0138] Based on step S902c, if the first entity receives an uplink synchronization loss instruction, i.e., if the terminal device is in an uplink synchronization out state, the first entity does not send a random access preamble instruction to the second entity, i.e., does not initiate random access. In other words, based on the restriction of the third condition, it is possible to prevent the terminal device from initiating random access while in an uplink synchronization out state, thereby reducing power waste on the terminal device and reducing the waste of resources occupied for random access.

[0139] In some implementation scenarios, if the access network device configures a PUCCH resource for SR when it is considered whether the terminal device is uplink synchronized, then when the first entity receives an uplink synchronization instruction, the PUCCH resource can be considered valid. Furthermore, uplink transmission can be considered permitted within the serving cell. Once the PUCCH resource is considered valid, the scheduling request may be processed according to the method shown in Figure 7.

[0140] If an access network device configures a PUCCH resource for SR, and the first entity receives an uplink synchronization loss instruction, the PUCCH resource can be considered invalid, meaning the first entity does not have a valid PUCCH resource. Furthermore, the first entity clears its HARQ buffer and ceases any uplink transmissions within the serving cell.

[0141] In the embodiments described above, it can be understood that methods and / or steps performed by the terminal device may, alternatively, be performed by components that can be used in the terminal device (e.g., a processor, chip, chip system, circuit, logic module, or software such as a chip or circuit).

[0142] The above primarily describes the solution provided in this application. Accordingly, this application further provides a communication device. The communication device is configured to carry out the above method. The communication device may be a terminal device in an embodiment of the above method, or a device including the above terminal device, or a component that can be used in the terminal device, such as a chip or a chip system.

[0143] It can be understood that, in order to perform the functions described above, the communication device includes corresponding hardware structures and / or software modules for performing the functions. Those skilled in the art will readily realize, by referring to the units and algorithmic steps in the examples described in the embodiments disclosed herein, that the application can be implemented in hardware form or in combination of hardware and computer software. Whether the functions are performed in hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the described functions using different methods for each specific application, but implementation should not be considered to extend beyond the scope of the application.

[0144] In embodiments of the present application, the communication device may be divided into functional modules based on embodiments of the method described above. For example, each functional module may be obtained through division based on each corresponding function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. It should be noted that in embodiments of the present application, module division is merely an example and represents only a logical functional division. In actual implementation, other division methods may be used.

[0145] Optionally, an example is used in which the communication device is the terminal device in the embodiment of the above method. Figure 11 is a diagram of the structure of the terminal device 110. The terminal device 110 includes a processing module 1101 and a communication module 1102.

[0146] In some embodiments, the terminal device 110 may further include a storage module (not shown in Figure 11) configured to store program instructions and data.

[0147] In some embodiments, the communication module 1102 may also be called a transceiver unit and is configured to implement transmitting and / or receiving functions. The communication module 1102 may include a transceiver circuit, a transceiver machine, a transceiver, or a communication interface.

[0148] In some embodiments, the communication module 1102 may include a receiving module and a transmitting module, each configured to perform the receiving and transmitting steps that were performed by the terminal device in the embodiments of the above method, and / or to support another process of the technology described herein. The processing module 1101 may be configured to perform processing (e.g., determination and generation) steps that were performed by the terminal device in the embodiments of the above method, and / or to support another process of the technology described herein.

[0149] In possible implementations:

[0150] Processing module 1101 is used by the first entity to determine if there is a first scheduling request SR in a pending state. When the first condition is satisfied, communication module 1102 is used by the first entity to instruct the second entity to transmit the first SR. The first condition includes that the first entity has an SR transmission occasion on a valid PUCCH resource for the configured SR and that the first entity has not received an uplink synchronization loss instruction.

[0151] Optionally, the fact that the first entity has not received an uplink sync loss instruction includes the fact that the first entity has not received an uplink sync loss instruction prior to the SR transmission occasion.

[0152] Optionally, the first entity not having received an uplink loss of synchronization instruction prior to an SR transmission occasion includes the first entity not having received an uplink loss of synchronization instruction after the first SR is triggered and prior to an SR transmission occasion.

[0153] Optionally, the fact that the first entity has not received an uplink synchronization loss instruction includes the most recent instruction received by the first entity being an uplink synchronization instruction.

[0154] In another possible implementation:

[0155] Processing module 1101 is used by the first entity to determine if there is a first scheduling request SR in a pending state. When the second condition is satisfied, processing module 1101 is further configured to initiate a random access procedure and cancel the first SR. The second condition includes that the first entity does not have a valid physical uplink control channel PUCCH resource and that the first entity has not received an uplink loss of synchronization instruction. A valid PUCCH resource corresponds to the first SR. Alternatively, when the third condition is satisfied, communication module 1102 is used by the first entity to send a random access preamble instruction to the second entity, or processing module 1101 is used by the first entity to determine not to send a random access preamble instruction to the second entity. The third condition includes that the first entity does not have a valid PUCCH resource and that the first entity has received an uplink loss of synchronization instruction. The random access preamble instruction instructs the second entity to send a random access preamble.

[0156] Optionally, if the first entity receives an uplink synchronization instruction, the communication module 1102 is further used by the first entity to send instruction information to the second entity. The instruction information is used to cancel the transmission of a random access preamble.

[0157] Optionally, the communication module 1102 may be further used by the first entity to instruct the second entity to transmit a first SR over a valid PUCCH resource.

[0158] Optionally, when the third condition is satisfied, the processing module 1101 is further configured to start the first timer. The first entity receiving an uplink synchronization instruction includes the first entity receiving the uplink synchronization instruction before the first timer terminates.

[0159] Optionally, when the third condition is satisfied, the processing module 1101 is further configured to start a second timer. The use of the processing module 1101 by the first entity to decide not to send a random access preamble instruction to the second entity includes the use of the processing module 1101 by the first entity to decide not to send a random access preamble instruction to the second entity for the second timer to terminate.

[0160] All relevant details of the steps in the embodiments of the above method may be described in the functional description of the corresponding functional module. Further details are not provided here.

[0161] In this application, the terminal device 110 is provided in a form in which functional modules are divided and integrated. The “module” in this application may be one or more software or firmware components, integrated logic circuits, and / or other components that can provide the above functions, application-specific integrated circuits (ASICs), circuits, processors, and memories that perform these functions.

[0162] In some embodiments, a person skilled in the art may conceive that, in hardware implementation, the terminal device 110 may take the form of the communication device 60 shown in Figure 6a.

[0163] For example, the function / implementation process of the processing module 1101 in Figure 11 may be performed by the processor 601 of the communication device 60 shown in Figure 6a by calling computer executable instructions stored in memory 603. The function / implementation process of the communication module 1102 in Figure 11 may be performed by the communication interface 604 of the communication device 60 shown in Figure 6a.

[0164] In some embodiments, when the terminal device 110 in Figure 11 is a chip or chip system, the functions / implementation processes of the communication module 1102 may be implemented by using the input / output interface (or communication interface) of the chip or chip system, and the functions / implementation processes of the processing module 1101 may be implemented by using the processor (or processing circuit) of the chip or chip system.

[0165] The terminal device 110 provided in this embodiment can perform the above method, but for the technical effects that can be achieved by the terminal device 110, please refer to the embodiments of the method described above. Details are not described again here.

[0166] As possible product forms, the terminal device in this embodiment of the present application may alternatively be implemented by one or more field programmable data arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, logic gates, discrete hardware components, any other suitable circuitry, or any combination of circuits capable of performing the various functions described herein.

[0167] As another possible product form, the terminal device in this embodiment of this specification may be implemented by using a general-purpose bus architecture. For ease of description, Figure 12 is a diagram of the structure of a communication device 1200 according to an embodiment of the present application. The communication device 1200 includes a processor 1201 and a transceiver 1202. The communication device 1200 may be a terminal device, or a chip or module within a terminal device. Figure 12 does not show the main components of the communication device 1200. In addition to the processor 1201 and the transceiver 1202, the communication device may further include a memory 1203.

[0168] Optionally, the processor 1201 is configured primarily to process communication protocols and data, control the entire communication device, execute software programs, and process data for the software programs. The memory 1203 is configured primarily to store software programs and data. The transceiver 1202 may include a radio frequency circuit and an antenna. The radio frequency circuit is configured primarily to perform conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is configured primarily to receive and transmit radio frequency signals in the form of electromagnetic waves.

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

[0170] After 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. If the data needs to be transmitted wirelessly, the processor 1201 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. After performing radio frequency processing on the baseband signal, the radio frequency circuit transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When the data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency 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.

[0171] In another implementation, the radio frequency circuit and antenna may be located independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna may be located remotely, independently of the communication equipment.

[0172] In some embodiments, embodiments of the present application further provide a communication device. The communication device includes a processor configured to carry out the method in any one of the embodiments of the method described above.

[0173] In possible implementations, the communication device further includes memory. The memory is configured to store necessary computer programs and necessary data. The computer programs may include instructions, and the processor may call instructions in the computer programs stored in memory and instruct the communication device to perform the method in any one of the embodiments of the method described above. Certainly, the memory does not have to be in the communication device.

[0174] In another possible implementation, the communication device further includes an interface circuit. The interface circuit is a code / data read / write interface circuit, which is configured to receive computer executable instructions (which are stored in memory and may be read directly from memory or through another component) and to send the computer executable instructions to the processor.

[0175] In yet another implementation, the communication device further includes a communication interface, which is configured to communicate with modules outside the communication device.

[0176] It can be understood that a communication device may be a chip or a chip system. If the communication device is a chip system, it may include a chip, or it may include a chip and other discrete components. This is not particularly limited in the embodiments of the present application.

[0177] The present invention further provides a computer-readable storage medium that stores computer programs or instructions. When the computer programs or instructions are executed by a computer, the functions of any one embodiment of the above-described method are performed.

[0178] The present invention further provides a computer program product. When the computer program product is executed by a computer, the functions of any one embodiment of the above-described embodiment of the method are performed.

[0179] Those skilled in the art will understand that, for convenience and for the sake of concise description, the detailed operating processes of the above systems, apparatus, and units should be referred to by the corresponding processes in the embodiments of the above methods. Further details are not described here again.

[0180] It can be understood that the systems, apparatus, and methods described herein may be implemented in alternative ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and in actual implementation, other divisions may be used. For example, multiple units or components may be combined or integrated with other systems, or some functions may be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection indicated or discussed may be implemented through some interface. Indirect coupling or communication connection between apparatus or units may be implemented in an electrical, mechanical, or other form.

[0181] Units described as separate parts may or may not be physically separated; that is, they may be located together in the same place or distributed across multiple network units. Parts shown as units may or may not be physical units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solution of the embodiment.

[0182] Furthermore, the functional units in the embodiments of the present invention may be integrated into a single processing unit, or each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0183] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. When a software program is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When a computer program instruction is loaded into a computer and executed, all or part of the procedure (or function) described in the embodiments of this application is performed. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired method (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or by a wireless method (e.g., infrared, radio waves, or microwaves). The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server or data center that incorporates one or more available media. The usable media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), semiconductor media (e.g., solid-state drives (SSDs)), etc. In embodiments of the present invention, a computer may include the above-mentioned devices.

[0184] While this application is described with reference to embodiments, a person skilled in the art will be able to understand and implement other modifications of the disclosed embodiments by looking at the accompanying drawings, the disclosed content and the accompanying claims in the course of implementing the application for which protection is claimed. In the claims, “comprising” does not exclude other components or other steps, and “one” or “one” does not exclude multiple cases. A single processor or other unit may perform some of the functions enumerated in the claims. Some means are recorded in separate claims that are different from each other, but this does not mean that those means cannot be combined to produce a superior effect.

[0185] While this application is described with reference to specific features and embodiments thereof, it is evident that various modifications may be made to them without departing from the spirit and scope of this application. Accordingly, the specification and accompanying drawings are merely illustrative descriptions of this application as defined by the accompanying claims and shall be considered any or all modifications, variations, combinations, or equivalents covering the scope of this application. It is evident to those skilled in the art that various modifications and variations can be made to this application without departing from the spirit and scope of this application. Thus, this application is intended to cover such modifications and variations of this application, provided that they fall within the scope of the claims and the equivalent art thereof.

[0186] This application claims priority to Chinese Patent Application No. 202211347424.6, filed with the China National Intellectual Property Administration on October 31, 2022, with the title of the invention being "SCHEDULING REQUEST PROCESSING METHOD AND APPARATUS," which is incorporated herein by reference in its entirety.

Claims

1. A scheduling request processing method, The first entity determines that there is a first scheduling request SR in a pending state, When the first condition is satisfied, the first entity instructs the second entity to transmit the first SR. It has, The first condition includes that the first entity has an SR transmission occasion on a physical uplink control channel PUCCH resource that is valid for the configured SR, and that the first entity has not received an uplink synchronization loss instruction. method.

2. The fact that the first entity has not received an uplink synchronization loss instruction means that The first entity has not received an uplink synchronization loss instruction prior to the SR transmission occasion, The method according to claim 1.

3. The first entity has not received an uplink synchronization loss instruction prior to the SR transmission occasion. The first entity has not received an uplink synchronization loss instruction after the first SR has been triggered and before the SR transmission occasion, The method according to claim 2.

4. The fact that the first entity has not received an uplink synchronization loss instruction means that The most recent instruction received by the first entity is an uplink synchronization instruction, The method according to claim 1.

5. A scheduling request processing method, The first entity determines that there is a first scheduling request SR in a pending state, When the second condition is satisfied, initiate a random access procedure and cancel the first SR, the second condition includes the first entity not having a valid physical uplink control channel PUCCH resource and the first entity not having received an uplink synchronization loss instruction, or When the third condition is satisfied, the first entity decides to either transmit a random access preamble instruction to the second entity or not transmit a random access preamble instruction to the second entity, the third condition includes the first entity not having a valid PUCCH resource and the first entity receiving an uplink synchronization loss instruction, and the random access preamble instruction instructs the second entity to transmit a random access preamble. The effective PUCCH resource corresponds to the first SR, method.

6. After the first entity transmits a random access preamble instruction to the second entity, the method proceeds as follows: The first entity further transmits instruction information to the second entity when it receives an uplink synchronization instruction, the instruction information is used to cancel the transmission of the random access preamble. The method according to claim 5.

7. The method further comprises the first entity instructing the second entity to transmit the first SR on the valid PUCCH resource. The method according to claim 6.

8. When the third condition is satisfied, the method further comprises starting the first timer, The first entity receiving the uplink synchronization instruction means that The first entity includes receiving the uplink synchronization instruction before the first timer ends, The method according to claim 6 or 7.

9. When the third condition is satisfied, the method further includes activating a second timer. The first entity decides not to send a random access preamble instruction to the second entity. The first entity decides not to send the random access preamble instruction to the second entity before the second timer terminates, The method according to claim 5.

10. It has a processing module and a communication module, The processing module is used by the first entity to determine that there is a first scheduling request SR in a pending state. When the first condition is satisfied, the communication module is used by the first entity to instruct the second entity to transmit the first SR. The first condition includes that the first entity has an SR transmission occasion on a physical uplink control channel PUCCH resource that is valid for the configured SR, and that the first entity has not received an uplink synchronization loss instruction. Communication device.

11. The fact that the first entity has not received an uplink synchronization loss instruction means that The first entity has not received an uplink synchronization loss instruction prior to the SR transmission occasion, The communication device according to claim 10.

12. The first entity has not received an uplink synchronization loss instruction prior to the SR transmission occasion. The first entity has not received an uplink synchronization loss instruction after the first SR has been triggered and before the SR transmission occasion, The communication device according to claim 11.

13. The fact that the first entity has not received an uplink synchronization loss instruction means that The most recent instruction received by the first entity is an uplink synchronization instruction, The communication device according to claim 10.

14. It has a processing module and a communication module, The processing module is used by the first entity to determine that there is a first scheduling request SR in a pending state. When the second condition is satisfied, the processing module is further configured to initiate a random access procedure and cancel the first SR, the second condition including that 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 instruction, or When the third condition is satisfied, the communication module is used by the first entity to transmit a random access preamble instruction to the second entity, or the processing module is used to determine that the first entity does not transmit a random access preamble instruction to the second entity, the third condition includes the first entity not having a valid PUCCH resource and the first entity receiving an uplink synchronization loss instruction, the random access preamble instruction instructs the second entity to transmit a random access preamble, The effective PUCCH resource corresponds to the first SR, Communication device.

15. When the first entity receives an uplink synchronization instruction, the communication module is further used by the first entity to transmit instruction information to the second entity, and the instruction information is used to cancel the transmission of the random access preamble. The communication device according to claim 14.

16. The communication module is further used by the first entity to instruct the second entity to transmit the first SR on the valid PUCCH resource. The communication device according to claim 15.

17. When the third condition is satisfied, the processing module is further configured to activate the first timer. The first entity receiving the uplink synchronization instruction means that The first entity includes receiving the uplink synchronization instruction before the first timer ends, The communication device according to claim 15 or 16.

18. When the third condition is satisfied, the processing module is further configured to activate a second timer. The processing module is used to determine that the first entity does not send a random access preamble instruction to the second entity. The processing module is used by the first entity to determine whether to send the random access preamble instruction to the second entity before the second timer terminates, The communication device according to claim 14.

19. A communication device having a processor, The processor is configured to execute a program or instruction to cause the communication device to perform the method described in any one of claims 1 to 4, or to cause the communication device to perform the method described in any one of claims 5 to 9. Communication device.

20. Stores computer instructions or programs, When the computer instruction or program is executed on a computer, the method described in any one of claims 1 to 4 is executed, or the method described in any one of claims 5 to 9 is executed. Computer-readable storage medium.

21. A computer program product that includes computer instructions, When all or part of the aforementioned computer instruction is executed by a computer, the method described in any one of claims 1 to 4 is executed, or the method described in any one of claims 5 to 9 is executed. Computer program products.

Images