Scheduling request processing method and device

Abstract

The invention discloses a scheduling request processing method and device, which can be applied to a non-terrestrial network (NTN) scene. The method includes a first entity determining that there is a first scheduling request (SR) in a waiting state. And when the first condition is satisfied, the first entity instructs the second entity to send the first SR. Wherein the first condition comprises that the first entity has a configured SR transmission opportunity on an effective physical uplink control channel (PUCCH) resource, and the first entity does not receive an uplink synchronization loss indication. Based on the scheme, under the condition that the first entity has the configured SR transmission opportunity on the effective PUCCH resource, if the first entity needs to indicate the second entity to send the first SR, at least the condition that the first entity does not receive the uplink synchronization loss indication needs to be met. That is to say, the terminal equipment can be limited not to send the SR when the uplink synchronization is lost, so that the power consumption waste of the terminal equipment is reduced, and meanwhile, the resource waste occupied by SR sending is reduced.

Description

[0001] This application is a divisional application. The application number of the original application is 202211347424.6, the filing date of the original application is October 31, 2022, and the entire content of the original application is incorporated herein by reference. Technical Field

[0002] Embodiments of this application relate to the field of communications, and in particular, to a scheduling request processing method and apparatus. Background Art

[0003] A scheduling request (SR) is mainly used to request new uplink resources. The SR can be triggered in scenarios such as beam failure recovery, preemptive buffer status reporting, or consistent Listen Before Talk failure recovery.

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

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

[0006] This application provides a scheduling request processing method and apparatus. In a scenario considering the synchronization state of the terminal device, if a pending SR is to be sent, it is at least required that a first entity has not received an uplink synchronization loss indication.

[0007] In a first aspect, a scheduling request processing method is provided. This method can be executed by a terminal device, or by components of the terminal device, such as a processor, a chip, or a chip system of the terminal device, or can also be implemented by a logic module or software capable of implementing all or part of the functions of the terminal device. The method includes: a first entity determines that there is a first scheduling request SR in a pending state; when a first condition is satisfied, the first entity instructs a second entity to send the first SR. Wherein, the first condition includes: the first entity has a configured SR transmission opportunity on an available physical uplink control channel PUCCH resource, and the first entity has not received an uplink synchronization loss indication.

[0008] Based on this solution, when the first entity has a configured SR transmission opportunity on a valid PUCCH resource, if it wants to instruct the second entity to send the first SR, it is at least necessary to satisfy that the first entity has not received an uplink synchronization loss indication. In other words, even if the first entity has a configured SR transmission opportunity on a valid PUCCH resource, but if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink out-of-sync state), then the first entity cannot instruct the second entity to send the first SR.

[0009] That is to say, based on the limitation of the above first condition, it is possible to avoid the terminal device from sending an SR when the uplink is out of synchronization. Even if the terminal device sends an SR when the uplink is out of synchronization, the access network device will not be able to successfully receive the SR because of the uplink synchronization loss of the terminal device. Therefore, restricting the terminal device from not sending an SR when the uplink is out of synchronization can reduce the power consumption waste of the terminal device and at the same time reduce the resource waste occupied by the SR transmission.

[0010] In a possible design, that the first entity has not received an uplink synchronization loss indication includes: before the SR transmission opportunity, the first entity has not received an uplink synchronization loss indication.

[0011] In a possible design, before the SR transmission opportunity, that the first entity has not received an uplink synchronization loss indication includes: after the first SR is triggered and before the SR transmission opportunity, the first entity has not received an uplink synchronization loss indication.

[0012] In a possible design, that the first entity has not received an uplink synchronization loss indication includes: the latest indication received by the first entity is an uplink synchronization indication.

[0013] In a second aspect, a scheduling request processing method is provided. This method can be executed by a terminal device, or by components of the terminal device, such as the processor, chip, or chip system of the terminal device, etc., and can also be implemented by a logic module or software that can implement all or part of the functions of the terminal device. The method includes: the first entity determines that there is a first scheduling request SR in a waiting state. When a second condition is satisfied, a random access process is started and the first SR is cancelled. When a third condition is satisfied, the first entity sends a random access preamble indication to the second entity, or the first entity determines not to send a random access preamble indication to the second entity. Among them, 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. Among them, the valid PUCCH resource corresponds to the first SR.

[0014] Based on this solution, when there is no valid PUCCH resource, if the first entity wants to initiate a random access procedure and cancel the first SR, it needs to 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 has no valid PUCCH resource, but if the first entity receives an uplink synchronization loss indication (i.e., the terminal device is in an uplink out-of-sync state), then the first entity cannot initiate a random access procedure. That is to say, based on the limitation of the second condition, it is possible to prevent the terminal device from initiating a random access in the uplink out-of-sync state, thereby reducing the power consumption waste of the terminal device and at the same time reducing the resource waste occupied by the random access.

[0015] In addition, when the first entity receives an uplink synchronization loss indication, that is, when the terminal device is in an uplink out-of-sync state, the first entity does not send a random access preamble indication to the second entity, that is, does not initiate a random access. That is to say, based on the limitation of the third condition, it is possible to prevent the terminal device from initiating a random access in the uplink out-of-sync state, thereby reducing the power consumption waste of the terminal device and at the same time reducing the resource waste occupied by the random access.

[0016] In a 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, and the indication information is used to cancel the sending of the random access preamble.

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

[0018] Based on the above two possible implementations, after the uplink synchronization is restored, the sending of the random access preamble can be cancelled. At this time, if there is a valid PUCCH resource, the first entity can instruct the second entity to send the first SR on this PUCCH resource, reducing the delay caused by the execution of the random access, that is, compared with the solution that still sends the random access preamble, the sending delay of the first SR can be reduced.

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

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

[0021] In a third aspect, a communication device is provided for implementing various methods. The communication device may be the terminal device in the first aspect or the second aspect, or a device included in the terminal device, such as a chip, a chip system, or a module. The communication device includes corresponding modules, units, or means for implementing the method, and the modules, units, or means may be implemented by hardware, by 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 may be used to implement the processing functions in any of the above aspects and any possible implementation manners thereof. The communication module is used to implement the sending and / or receiving functions in any of the above aspects and any possible implementation manners thereof. The communication module may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

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

[0024] In a fourth aspect, a communication device is provided, including: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instruction, so that the communication device executes the method described in any of the above aspects. The communication device may be the terminal device in the first aspect or the second aspect, or a device included in the terminal device, such as a chip, a chip system, or a module.

[0025] In a fifth aspect, a communication device is provided, including: at least one processor; the processor is used to execute a computer program or instruction stored in a memory, so that the communication device executes the method described in any of the above 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 independent modules. The memory may be located outside the communication device or inside the communication device. The communication device may be the terminal device in the first aspect or the second aspect, or a device included in the terminal device, such as a chip, a chip system, or a module.

[0026] In a sixth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When it runs on a communication device, the communication device can execute the method described in any of the above aspects.

[0027] In a seventh aspect, a computer program product including instructions is provided. When it runs on a communication device, the communication device can execute the method described in any of the above aspects.

[0028] It can be understood that when the communication device provided in any one of the third aspect to the seventh aspect is a chip, the sending action / function can be understood as outputting information, and the receiving action / function can be understood as inputting information.

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

[0030] Among them, for the technical effects brought by any one of the design manners in the third aspect to the seventh aspect, reference may be made to the technical effects brought by different design manners in the first aspect or the second aspect, which will not be elaborated herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a schematic structural diagram of a communication system provided by the present application;

[0032] Figure 2 It is a schematic structural diagram of a non-terrestrial network provided by the present application;

[0033] Figure 3 It is another schematic structural diagram of a non-terrestrial network provided by the present application;

[0034] Figure 4 It is yet another schematic structural diagram of a non-terrestrial network provided by the present application;

[0035] Figure 5 It is still another schematic structural diagram of a non-terrestrial network provided by the present application;

[0036] Figure 6a It is a schematic structural diagram of a communication device provided by the present application;

[0037] Figure 6b It is a schematic structural diagram of a terminal device provided by the present application;

[0038] Figure 7 It is a schematic flowchart of a scheduling request processing method provided by the present application;

[0039] Figure 8 It is a schematic timing diagram provided by the present application;

[0040] Figure 9 It is another schematic flowchart of a scheduling request processing method provided by the present application;

[0041] Figure 10a It is yet another schematic flowchart of a scheduling request processing method provided by the present application;

[0042] Figure 10b It is yet another schematic timing diagram provided by the present application;

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

[0044] Figure 12 A schematic structural diagram of another communication device provided for this application. Specific embodiments

[0045] In the description of this application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B; "and / or" in this application is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B can be singular or plural.

[0046] In the description of this application, unless otherwise specified, "a plurality of" means two or more than two. "At least one (item)" or similar expressions thereof refer to any combination of these items, including any combination of single item (s) or plural items (s). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0047] In addition, in order to clearly describe the technical solutions of the embodiments of this application, in the embodiments of this application, terms such as "first" and "second" are used to distinguish identical items or similar items with basically the same functions and effects. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily limit to be different.

[0048] In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific way for easy understanding.

[0049] It can be understood that the "embodiments" mentioned throughout the specification mean that specific features, structures, or characteristics related to the embodiments are included in at least one embodiment of the present application. Therefore, the embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in one or more embodiments in any suitable manner. It can be understood that in various embodiments of the present application, the magnitude of the serial numbers of the various processes does not mean the order of execution, and the order of execution of the various processes should be determined by their functions and internal logics, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0050] It can be understood that in the present application, both "when..." and "if" refer to corresponding processing being performed under certain objective circumstances, not to limit time, and do not require a judgment action during implementation, nor do they imply other limitations.

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

[0052] In the present application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be mutually referenced, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships. The embodiments of the present application described below do not constitute a limitation to the protection scope of the present application.

[0053] To facilitate the understanding of the technical solutions of the embodiments of the present application, a brief introduction to the related technologies of the present application is first given as follows.

[0054] 1. Scheduling Request (SR):

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

[0056] Generally, when configuring SR for a network, SR resources (Scheduling Request Resource) are configured for the SR. The SR resources are located in the physical uplink control channel (PUCCH) resources. For example, the base station can configure the SR transmission opportunity on the PUCCH resources and configure the frequency domain resource location as the SR resources. Therefore, it can also be considered that the SR configured by the network has corresponding (configured) PUCCH resources.

[0057] Exemplarily, a possible SR resource configuration method can be as follows:

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

[0059] SR resource identifier (schedulingRequestResourceId);

[0060] SR identifier (schedulingRequestID);

[0061] Periodicity and offset (periodicityAndOffset);

[0062] Resource (resource);

[0063] }

[0064] Among them, 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 periodicity 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, and this PUCCH resource is the PUCCH resource where the SR resource is located, or in other words, the PUCCH resource corresponding to the SR.

[0065] After the SR is triggered, it can be considered to be in a pending state until the SR is sent or cancelled. That is to say, the SR in the waiting state can be understood as: the SR that has been triggered but not sent or cancelled. For the SR in the waiting state:

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

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

[0068] It should be noted that the "waiting state" in the embodiments of this application can also be referred to as the "pending transmission state", and the two can be replaced with each other.

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

[0070] With the development of communication requirements, the fifth-generation (5G) network and future evolved networks not only need to meet various service requirements but also provide a wider service coverage. Among them, NTN is less affected by geographical conditions and can achieve the goal of global coverage, which is an important direction for future communication development.

[0071] Compared with traditional terrestrial networks, NTN typically uses flying platforms (such as airplanes or drones) or satellites to participate in network deployment. For example, a base station or some base station functions are deployed on the flying platform or satellite to provide coverage for terminals, or the flying platform or satellite is used as a relay to forward the signals of terrestrial base stations to provide coverage for terminals.

[0072] In NTN, the ephemeris information of satellites or the flight information of flying platforms (such as the position, speed, flight orbit, etc. of the flying platform) plays a very important role in communication. Taking satellite communication as an example, the terminal device can determine the end-to-end delay from the terminal device to the base station through the ephemeris information of the satellite, its own position, and the delay information from the satellite to the satellite gateway. Then, pre-compensation for the timing advance can be performed according to the end-to-end delay. In addition, the network can be made to know the timing advance of the terminal device for more reasonable data scheduling.

[0073] However, the ephemeris information of satellites has timeliness. Therefore, a validity timer is introduced in NTN. After receiving the ephemeris information of the satellite, the radio resource control (RRC) entity of the terminal device can start the validity timer. Before the validity timer expires, the ephemeris information is accurate and valid, and the terminal device is in the uplink synchronization state. After the validity timer expires, the ephemeris information becomes invalid, and the terminal device is in the uplink out-of-sync state, or rather, the uplink synchronization is lost. After receiving the ephemeris information again later, the terminal device resumes the uplink synchronization state.

[0074] In addition, after receiving ephemeris information, the RRC entity may 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 may send an uplink synchronization loss indication to the MAC entity to indicate that the uplink synchronization of the terminal device is lost, or to indicate that the terminal device is in an uplink out-of-synchronization state.

[0075] When the terminal device is in an uplink out-of-synchronization state, the terminal device will clear the hybrid automatic repeat request (HARQ) buffer and stop sending uplink signals, such as media access control control element (MAC CE) or RRC messages. In the uplink out-of-synchronization state, the base station cannot correctly receive the uplink signals of the terminal device.

[0076] As described above, in the current SR processing method, for the SR in the waiting state, the terminal device is required to initiate a random access procedure or send an SR. However, in NTN, if the terminal device is in an uplink out-of-synchronization state, the terminal device is required to stop sending uplink signals. Therefore, in the scenario of considering whether the terminal device is synchronized, how to process the SR in the waiting state is an urgent problem to be solved currently.

[0077] Based on this, the present application provides an SR processing method. In this method, if an SR in the waiting state needs to be sent, there needs to be an effective PUCCH resource and the terminal device is in an uplink synchronized state. Therefore, it is possible to avoid the terminal device sending an SR when the uplink synchronization is lost, thereby reducing the power consumption waste of the terminal device and reducing the resource waste.

[0078] The technical solution of the embodiment of the present application can be used in various communication systems. The communication system can be a third generation partnership project (3GPP) communication system, for example, a 5G system such as a long term evolution (LTE) system, a new radio (NR) system, a satellite communication system, an NTN system, a vehicle to everything (V2X) system, or a system with a hybrid network of LTE and 5G, or a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT), and a future evolved communication system. The communication system can also be a non-3GPP communication system, without limitation.

[0079] The technical solutions of the embodiments of the present application can be applied to various communication scenarios. For example, they can be applied to 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 and other communication scenarios.

[0080] Among them, the above-mentioned communication systems and communication scenarios applicable to the present application are only examples. The communication systems and communication scenarios applicable to the present application are not limited thereto. The communication systems and communication scenarios provided by the present application do not impose any limitations on the solutions of the present application. This is explained uniformly here and will not be repeated hereinafter.

[0081] See Figure 1 , a communication system 10 applicable to the solution of the present application is provided for the present 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 numbers of the terminal device and the access network device in

[0082] Optionally, the terminal device 101 in the embodiments of the present application may be a user-side device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal. Among them, the terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile phone, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, or a terminal device in a 5G network or a public land mobile network (PLMN) evolved after 5G. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication functions, a computing device, or other processing devices connected to a wireless modem, an in-vehicle device, or a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Alternatively, the terminal may be a terminal with communication functions in the IoT, such as a terminal in V2X (such as a vehicle-to-everything device), a terminal in D2D communication, or a terminal in M2M communication. The terminal may be mobile or fixed.

[0083] Optionally, the access network device 102 in the embodiments of the present application is a device that connects the terminal device 101 to a wireless network. The access network device 102 may be referred to as a node in a radio access network (RAN), and may also be referred to as a base station, or a wireless access network node (or device).

[0084] For example, the access network device may include an evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in an LTE system or an LTE-A system, such as a traditional macro eNB and a micro eNB in a heterogeneous network scenario. Alternatively, it may include a next generation node B (gNB) in an NR system. Alternatively, it may include a transmission reception point (TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), a BBU pool, or a wireless fidelity (WiFi) access point (AP), etc. Alternatively, it may include a base station in NTN, that is, it can be deployed on an airborne platform or a satellite. In NTN, the access network device can act as a layer 1 (L1) relay, or can act as a base station, or can act as an integrated access and backhaul (IAB) node. Alternatively, the access network device can be a device in IoT that implements the base station function, such as a device that implements the base station function in V2X, D2D, or machine to machine (M2M).

[0085] The access network device can also be a module or unit that can implement some functions of the base station. For example, the access network device 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, the access network device can be an access network device or a module of an access network device in an open radio access network (ORAN) system. In the ORAN system, the CU can also be called an open (O)-CU, the DU can also be called an O-DU, the CU-CP can also be called an O-CU-CP, the CU-UP can also be called an O-CU-UP, and the RU can also be called an O-RU.

[0086] Optionally, the CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the packet data convergence protocol (PDCP) layer and the protocol layers above it (such as the RRC layer and the service data adaptation protocol (SDAP) layer, etc.) 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, etc.) are set in the DU; or, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the PDCP layer and the protocol layers below it are set in the DU, without limitation.

[0087] The above division of the processing functions of the CU and DU according to the protocol layers is only an example, and they can also be divided in other ways. For example, the CU or DU can be divided into functions with more protocol layers, or the CU or DU can be divided into partial processing functions of the protocol layers. For example, some functions of the RLC layer and the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the protocol layers below the RLC layer are set in the DU. Another example is that the functions of the CU or DU can be divided according to the service type or other system requirements, such as dividing by latency. The functions that need to meet the latency requirements are set in the DU, and the functions that do not need to meet the latency requirements are set in the CU.

[0088] Optionally, the base station in the embodiments of the present application can include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, home base stations, TRPs, transmitting points (TPs), mobile switching centers, etc. The embodiments of the present application do not make specific limitations on this.

[0089] As a possible implementation, as Figure 2 shown, the access network device 102 can be deployed on the ground and serve as a part of the ground network to communicate with the data network through the core network. At this time, the communication system 10 provided by the present application can further include a relay device deployed on a flying platform or a satellite. This relay device serves as a layer 1 relay (L1 relay), regenerates the physical layer signal and forwards it to the terminal device or the access network device.

[0090] As another possible implementation, as Figure 3 shown, the access network device 102 can be deployed on a flying platform or a satellite to implement the functions 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, as shown in Figure 4 Figure 2, the access network device 102 can be deployed on a flying platform or a satellite to implement the functions of a ground station, communicate directly with the core network, and further communicate with the data network through the core network. In addition, there is an inter-satellite link (ISL) between access network devices carried on different flying platforms or satellites, and the access network devices can communicate through this ISL.

[0092] As another possible implementation, as shown in Figure 5 Figure 3, the access network device 102 can include a DU deployed on a flying platform or a satellite and a CU deployed on the ground. The DU deployed on the flying platform or satellite communicates with the CU deployed on the ground through the 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 the present application is for more clearly explaining the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0094] Optionally, the related functions of the terminal device or access network device involved in the present application can be implemented by the Figure 6a communication device 60 in Figure 4. Referring to Figure 6a Figure 4, the communication device 60 includes one or more processors 601. Further, the communication device 60 may further include a communication bus 602 and at least one communication interface ( Figure 6a only exemplary in Figure 4, taking the communication device 60 including a communication interface 604 and one processor 601 as an example for illustration). Optionally, the communication device 60 may further include a memory 603.

[0095] The processor 601 may 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 the programs of the present application scheme, or a processing core for processing data (such as computer program instructions). The processor may be a single-CPU processor or a multi-CPU processor.

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

[0097] The communication bus 602 can be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. This bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 6a only a thick line is used to represent it in the figure, but it 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 with each other.

[0098] The communication interface 604 can be a transceiver module for communicating with other devices or communication networks. Such a communication network can be, for example, Ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc. For example, the communication interface 604 can be a device such as a transceiver or a transceiver. Alternatively, the communication interface 604 can also be a transceiver circuit located within the processor 601 to implement signal input and signal output of the processor.

[0099] The memory 603 can be a device with a storage function. For example, it can be a Read-Only Memory (ROM) or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and instructions, or it can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but not limited thereto. The memory can exist independently and be connected to the processor through the communication bus 602. The memory can also be integrated with the processor.

[0100] Among them, the memory 603 is used to store computer-executable instructions for executing the solution of this application, and is controlled by the processor 601 for execution. The processor 601 is used to execute the computer-executable instructions stored in the memory 603, so as to implement the method provided in the embodiments of this application.

[0101] Alternatively, optionally, in the embodiments of this application, it may also be that the processor 601 executes the functions related to processing in the method provided in the following embodiments of this application, and the communication interface 604 is responsible for communicating with other devices or communication networks. The embodiments of this application do not make specific limitations in this regard.

[0102] Optionally, the computer-executable instructions in the embodiments of this application may also be referred to as application code. The embodiments of this application do not make specific limitations in this regard.

[0103] In a specific implementation, as an 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, a keyboard, a touch screen device, or a sensing device, etc.

[0104] It should be noted that Figure 6a the shown component structure does not constitute a limitation on the communication device. Except Figure 6a for the components shown, the communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0105] As Figure 6b shown, it is a schematic structural diagram of another terminal device provided by the embodiments of this application. 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. Among them, the first entity is located above the second entity, or in other words, the first entity is the upper-layer entity of the second entity. In addition, the first entity is located below the third entity, or in other words, the first entity is the lower-layer entity of the third entity.

[0106] Exemplarily, the first entity may be a MAC entity. The second entity may be a PHY entity. The third entity may 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 for 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., which are not specifically limited in this application.

[0108] Next, the scheduling request processing method provided in the embodiments of the present application will be described in detail with reference to the accompanying drawings. It can be understood that in the embodiments of the present application, the terminal device may execute some or all of the steps in the embodiments of the present application. These steps or operations are only examples, and the embodiments of the present application may also execute other operations or various deformations of the operations. In addition, each step may be executed in a different order presented in the embodiments of the present application, and it is possible that not all of the operations in the embodiments of the present application need to be executed.

[0109] As an example, the following embodiments can be applied to the NTN scenario, such as the satellite communication scenario, or other scenarios in NTN, such as the low altitude platform (LAP) subnetwork, high altitude platform (HAP) subnetwork scenario, which are not specifically limited in this regard.

[0110] In addition, the following embodiments can also be applied to other possible communication scenarios or communication systems. For example, in a long-distance communication scenario where the distance between the terminal device and the access network device is relatively far or the relative moving speed is relatively large, or in a communication scenario where the terminal device may be in a synchronous state or an out-of-sync state, the scheduling request can be processed by the method provided in the embodiments of the present application.

[0111] As Figure 7 shown, a scheduling request processing method provided by the present application is applied to a terminal device. Refer to Figure 7 , the scheduling request processing method includes the following steps:

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

[0113] Optionally, the first SR may be triggered by one or more of the following events: beam failure recovery, preemptive buffer status report, timing advance report (Tming advance Report), or consistent listen before talk failure recovery. After the first SR is triggered, the first entity can sense the existence of the first SR in the waiting state, that is, the first entity can determine that there is a first SR in the waiting state.

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

[0115] Wherein, 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 an SR transmission occasion on the 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, the valid PUCCH resource can also be understood as the available PUCCH resource. In other words, the PUCCH resource is valid can also be understood as the PUCCH resource is available, or the PUCCH resource configuration is activated.

[0118] Optionally, the uplink synchronization loss indication can be used to indicate that the terminal device has lost uplink synchronization, or the terminal device is in an uplink out-of-sync state, or 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. Exemplarily, the third entity can maintain a timer related to the synchronization state (such as a validity timer), and send an uplink synchronization loss indication or an uplink synchronization indication to the first entity according to the running state of the timer.

[0120] For example, the third entity can start the validity timer when receiving the ephemeris information of the satellite or the flight information of the flying platform (such as the position, speed, flight orbit, etc. of the flying platform), and send an uplink synchronization indication to the first entity to indicate that the terminal device is in an uplink synchronization state or the terminal device is synchronized with the serving cell. In addition, when the timer expires, an uplink synchronization loss indication is sent to the first entity. Wherein, the duration of the timer can be understood as the valid duration of the ephemeris information or the flight information.

[0121] Thus, in this scenario, the first entity has not received an uplink synchronization loss indication can include: the first entity has not received an uplink synchronization loss indication from the third entity.

[0122] Optionally, the first SR can be triggered before the validity timer expires, or can be triggered after the validity timer expires. This application does not make specific limitations on this.

[0123] As a possible implementation, that the first entity does not receive an uplink synchronization loss indication may include: the indication received by the first entity most recently (or the last time) is an uplink synchronization loss indication. Exemplarily, the indication received most recently (or the last time) can be understood as the indication received the last time before the current moment, and the current moment can be, for example, the moment when the first condition is judged.

[0124] Exemplarily, as Figure 8 shown in (a) of [], taking the current moment as moment t1, if the first entity receives an uplink synchronization loss indication at moment t2 and then receives an uplink synchronization indication at moment t3, then the indication received by the first entity most recently (or the last time) is an uplink synchronization indication, belonging to the scenario where the first entity does not receive an uplink synchronization loss indication.

[0125] As Figure 8 shown in (b) of [], taking the current moment as moment t1, if the first entity receives an uplink synchronization indication at moment t2 and then receives an uplink synchronization loss indication at moment t3, then the indication received by the first entity most recently (or the last time) is an uplink synchronization loss indication, belonging to the scenario where the first entity receives an uplink synchronization loss indication.

[0126] As another possible implementation, that the first entity does not receive an uplink synchronization loss indication may include: before the SR transmission opportunity, the first entity does not receive an uplink synchronization loss indication. Further, it may include: after the first SR is triggered and before the SR transmission opportunity, the first entity does not receive an uplink synchronization loss indication. Wherein, the SR transmission opportunity is the SR transmission opportunity configured on the valid PUCCH resource.

[0127] Exemplarily, as Figure 8 shown in (c) of [], assuming that the first SR is triggered at moment t4 and the SR transmission opportunity is at moment t5, then, if the first entity does not receive an uplink synchronization loss indication between moment t4 and moment t5, it belongs to the scenario where the first entity does not receive an uplink synchronization loss indication. If the first entity receives an uplink synchronization loss indication between moment t4 and moment t5, it belongs to the scenario where the first entity receives an uplink synchronization loss indication.

[0128] Optionally, the first condition may further include: the transmission count of the first SR is less than the maximum SR transmission count. The maximum SR transmission count may be configured by the access network device. Of course, the first condition may further include other limiting conditions, and the present application does not make specific limitations thereto.

[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, where the indication information a is used to instruct the second entity to send the first SR. When the second entity receives the indication information a, it may send the first SR at the SR transmission opportunity.

[0130] Based on the above solution, when the first entity has a configured SR transmission opportunity on a valid PUCCH resource, if it wants to instruct the second entity to send the first SR, it is at least necessary to satisfy that the first entity has not received an uplink synchronization loss indication. In other words, even if the first entity has a configured SR transmission opportunity on a valid PUCCH resource, but 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 instruct the second entity to send the first SR.

[0131] That is to say, based on the limitation of the above first condition, it is possible to prevent the terminal device from sending an SR when the uplink is out of synchronization. Even if the terminal device sends an SR when the uplink is out of synchronization, the access network device will not be able to successfully receive the SR due to the uplink synchronization loss of the terminal device. Therefore, restricting the terminal device from not sending an SR when the uplink is out of synchronization can reduce the power consumption waste of the terminal device and at the same time reduce the resource waste occupied by the SR transmission.

[0132] As Figure 9 shown, another scheduling request processing method provided by this application is applied to a terminal device. Refer to 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. Among them, the implementation of step S901 can refer to the relevant description in step S701 above and will not be elaborated here.

[0134] Among them, after step S901, the following step S902a or S902b or 902c can be executed.

[0135] S902a. When the second condition is satisfied, start a random access process and cancel the first SR.

[0136] Among them, 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, when there is no valid PUCCH resource for the first entity, it may include: the PUCCH resource configured for the first SR is occupied by other services. Or rather, the frequency-domain resource corresponding to the SR transmission occasion on the PUCCH resource configured for the first SR is occupied by other services.

[0138] For the uplink synchronization loss indication and the description of the situation where the first entity does not receive the uplink synchronization loss indication, reference may be made to the relevant description in step S702 above, which will not be elaborated here.

[0139] Based on step S902a, when the first entity has no valid PUCCH resource, if it wants to initiate a random access procedure and cancel the first SR, it is at least required that the first entity does not receive the uplink synchronization loss indication. In other words, even if the first entity has no valid PUCCH resource, but if the first entity receives the uplink synchronization loss indication (i.e., the terminal device is in the uplink out-of-sync state), then the first entity cannot initiate a random access procedure. That is to say, due to the limitation of the second condition, it is possible to prevent the terminal device from initiating a random access in the uplink out-of-sync state, thereby reducing the power consumption waste of the terminal device and at the same time reducing the resource waste occupied by the random access.

[0140] S902b: When the third condition is satisfied, 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 has no valid PUCCH resource and the first entity receives the uplink synchronization loss indication.

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

[0143] As a possible implementation, the first entity having no valid PUCCH resource may include: the PUCCH resource configured for the first SR is occupied by other services. Or rather, the frequency-domain resource corresponding to the SR transmission occasion on the PUCCH resource configured for the first SR is occupied by other services.

[0144] As another possible implementation, the first entity having no valid PUCCH resource may include: actually, the first entity has a configured SR transmission occasion on a valid PUCCH resource, but since the first entity receives the uplink synchronization loss indication, the first entity considers the PUCCH resource invalid.

[0145] Combining the above two possible implementations, 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 there is a PUCCH resource corresponding to the first SR, the first entity considers that PUCCH resource invalid.

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

[0147] Optionally, the first entity may also send indication information b to the second entity, and the indication information b may indicate a period of time (denoted as duration 1). In this scenario, the random access preamble indication and the indication information b may jointly indicate that the second entity sends a random access preamble at the random access opportunity after duration 1. Exemplarily, the start time of the duration 1 may be the time when the second entity receives the indication information b and parses out the 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, after the third entity sends an uplink synchronization loss indication to the first entity and then receives the ephemeris information of the satellite or the flight information of the flying platform again, the third entity may send an uplink synchronization indication to the first entity to indicate that the uplink synchronization is restored.

[0149] In this scenario, as Figure 10a shown, after step S902b, the scheduling request processing method provided by the embodiments of the present application may further include: the first entity sends indication information c to the second entity. The indication information c is used to cancel the sending of the random access preamble. Or rather, the indication information c is used to instruct the second entity to cancel the sending of the random access preamble.

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

[0151] Exemplarily, as Figure 10b shown, taking the second entity receiving the random access preamble indication at time t1 and the random access opportunity being at time t2 as an example. If the second entity receives the indication information c at time t3, then the second entity will cancel the sending of the random access preamble.

[0152] Optionally, as Figure 10aAs shown, after the first entity receives the uplink synchronization indication, the first entity may further instruct the second entity to send the first SR on a valid PUCCH resource. Correspondingly, the second entity may send the first SR according to the indication of the first entity.

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

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

[0155] S902c. When the third condition is satisfied, the first entity determines not to send the random access preamble indication to the second entity. The description of the third condition and the random access preamble can refer to the relevant description in step S902b above and will not be elaborated here.

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

[0157] Optionally, when the third condition is satisfied, the first entity may further start the second timer. Further, this step S903 may include: the first entity determines not to send the random access preamble indication to the second entity before the second timer expires.

[0158] Based on this step S902c, when the first entity receives the uplink synchronization loss indication, that is, when the terminal device is in the uplink out-of-sync state, the first entity does not send the random access preamble indication to the second entity, that is, does not initiate random access. That is, based on the limitation of the third condition, it is possible to prevent the terminal device from initiating random access in the uplink out-of-sync state, thereby reducing the power consumption waste of the terminal device and at the same time reducing 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 configures PUCCH resources for SR, then when the first entity receives an uplink synchronization indication, it can be considered that the PUCCH resources are valid. In addition, it can be considered that uplink transmission is allowed in the serving cell. When considering the PUCCH resources to be valid, the scheduling request can be processed according to the method described above Figure 7 as shown.

[0160] If the access network device configures PUCCH resources for SR, then when the first entity receives an uplink synchronization loss indication, it can be considered that the PUCCH resources are invalid, or rather, the first entity does not have valid PUCCH resources. In addition, the first entity can clear the HARQ buffer and not perform any uplink transmission in the serving cell.

[0161] It can be understood that in each of the above embodiments, the methods and / or steps implemented by the terminal device can also be implemented by components (such as a processor, a chip, a chip system, a circuit, a logic module, or software such as a chip or a circuit) available for the terminal device.

[0162] The above mainly introduces the solutions provided in this application. Correspondingly, this application also provides a communication device, which is used to implement the above various methods. The communication device can be the terminal device in the above method embodiments, or a device including the above terminal device, or a component available for the terminal device, such as a chip or a chip system.

[0163] It can be understood that in order to implement the above functions, the communication device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

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

[0165] Optionally, taking the communication device as the terminal device in the above method embodiments as an example, Figure 11 FIG. 1 shows a schematic structural diagram of a terminal device 110. 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 FIG. 1) for storing program instructions and data.

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

[0168] In some embodiments, the communication module 1102 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the terminal device in the above method embodiments, and / or other processes to support the technologies described herein; the processing module 1101 may be used to execute the processing steps (such as determination, generation, etc.) performed by the terminal device in the above method embodiments, and / or other processes to support the technologies described herein.

[0169] In a possible implementation:

[0170] The processing module 1101 is used for the first entity to determine that there is a first scheduling request SR in the waiting state. When the first condition is satisfied, the communication module 1102 is used for 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 has not received an uplink synchronization loss indication, including: before the SR transmission opportunity, the first entity has not received an uplink synchronization loss indication.

[0172] Optionally, before the SR transmission opportunity, the first entity has not received an uplink synchronization loss indication, including: after the first SR is triggered and before the SR transmission opportunity, the first entity has not received an uplink synchronization loss indication.

[0173] Optionally, the first entity has not received an uplink synchronization loss indication, including: the latest indication received by the first entity is an uplink synchronization indication.

[0174] In another possible implementation:

[0175] A processing module 1101 is configured to determine, for a first entity, that there is a first scheduling request SR in a waiting state; when a second condition is satisfied, the processing module 1101 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, where the valid PUCCH resource corresponds to the first SR. Alternatively,

[0176] When a third condition is satisfied, a communication module 1102 is configured to send, for the first entity, a random access preamble indication to a second entity, or a processing module 1101 is configured to determine, for the first entity, not to 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 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.

[0177] Optionally, if the first entity receives an uplink synchronization indication, the communication module 1102 is further configured to send, for the first entity, an indication message to the second entity, where the indication message is used to cancel the sending of the random access preamble.

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

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

[0180] Optionally, when the third condition is satisfied, the processing module 1101 is further configured to start a second timer; the processing module 1101 is configured to determine, for the first entity, not to send a random access preamble indication to the second entity, including: the processing module 1101 is configured to determine, for the first entity, not to 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 cited in the function descriptions of the corresponding functional modules and will not be elaborated here.

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

[0183] In some embodiments, in terms of hardware implementation, those skilled in the art can conceive that the terminal device 110 may adopt the form of the Figure 6a communication device 60 shown.

[0184] As an example, Figure 11 the function / implementation process of the processing module 1101 in Figure 6a can be implemented by the processor 601 in the communication device 60 shown calling computer-executable instructions stored in the memory 603. Figure 11 The function / implementation process of the communication module 1102 in Figure 6a can be implemented by the communication interface 604 in the communication device 60 shown.

[0185] In some embodiments, when Figure 11 the terminal device 110 in

[0186] is a chip or a 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.

[0187] Since the terminal device 110 provided in this embodiment can execute the above method, the technical effects it can obtain can refer to the above method embodiments and will not be elaborated here.

[0187] As a possible product form, the terminal device described in the embodiments of the present 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 the present application.

[0188] As another possible product form, the terminal device described in the embodiments of the present application can be implemented by a general bus architecture. For ease of illustration, refer to Figure 12 , Figure 12 is a schematic structural diagram of a communication device 1200 provided in the embodiments of the present 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 the 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 software programs. The memory 1203 is mainly used to store software programs and data. The transceiver 1202 may include a radio frequency circuit and an antenna. The radio frequency circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals. The antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves.

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

[0191] 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. When data needs to be wirelessly transmitted, the processor 1201 performs baseband processing on the data to be transmitted and then outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal outward in the form of electromagnetic waves through the antenna. When data is sent 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.

[0192] In another implementation, the radio frequency circuit and the antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuit and the antenna may be independent of the communication device and arranged in a remote manner.

[0193] In some embodiments, the embodiments of the present application further provide a communication device, which includes a processor for implementing the method in any one of the above method embodiments.

[0194] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary computer programs and data. The computer program may include instructions, and the processor may call the instructions in the computer program stored in the memory to instruct the communication device to execute the method in any one of the above method embodiments. Of course, the memory may not be in the communication device.

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

[0196] As yet another possible implementation, the communication device further includes a communication interface for communicating with a module outside the communication device.

[0197] It can be 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 can include chips and other discrete devices. The embodiments of the present application do not make specific limitations on this.

[0198] The present application also provides a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, it implements the functions of any of the above method embodiments.

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

[0200] Those of ordinary skill in the art can understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0201] It can be understood that the systems, devices, and methods described in the present application can also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0203] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0204] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The 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 the present application are implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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 a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more integrated media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc. In the embodiments of the present application, the computer can include the devices described above.

[0205] Although the present application has been described in conjunction with various embodiments herein, however, in the process of implementing the claimed present application, those skilled in the art can understand and achieve other variations of the disclosed embodiments by viewing the accompanying drawings, the disclosure content, and the appended claims. 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 recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0206] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the present application. Accordingly, this specification and the accompanying drawings are merely exemplary illustrations of the present application as defined by the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these changes and modifications.

Claims

1. A scheduling request processing method, characterized in that, The method includes: The first entity determines that there is a first scheduling request SR in a waiting state; When a 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, wherein The first entity has not received an uplink synchronization loss indication, including: Before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication.

3. The method according to claim 2, characterized in that, Before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication, including: After the first SR is triggered and before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication.

4. The method according to claim 1, characterized in that The first entity has not received an uplink synchronization loss indication, including: The latest indication received by the first entity is an uplink synchronization indication.

5. A scheduling request processing method, characterized in that, The method includes: The first entity determines that there is a first scheduling request SR in a waiting state; When a second condition is met, start 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, where the valid PUCCH resource corresponds to the first SR.

6. The method according to 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 indication, the first entity sends indication information to the second entity, and the indication information is used to cancel the sending of the random access preamble.

7. The method according to claim 6, characterized in that, The method further includes: the first entity instructs the second entity to send the first SR on a valid PUCCH resource.

8. A communication device, characterized in that, The communication device includes: a processing module and a communication module; The processing module is configured to determine, for the first entity, that there is a first scheduling request SR in a waiting state; When a first condition is met, the communication module is configured to, for the first entity, 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.

9. The communication device according to claim 8, wherein The first entity has not received an uplink synchronization loss indication, including: Before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication.

10. The communication device according to claim 9, characterized in that, Before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication, including: After the first SR is triggered and before the SR transmission opportunity, the first entity has not received the uplink synchronization loss indication.

11. The communication device according to claim 8, wherein The first entity has not received an uplink synchronization loss indication, including: The latest indication received by the first entity is an uplink synchronization indication.

12. A communication device, characterized in that, The communication device includes: a processing module and a communication module; The processing module is configured to determine, for the first entity, that there is a first scheduling request SR in a waiting 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 includes: there is no valid physical uplink control channel (PUCCH) resource for the first entity, and the first entity has not received an uplink synchronization loss indication, where the valid PUCCH resource corresponds to the first SR.

13. The communication device according to claim 12, wherein if the first entity receives an uplink synchronization indication, the communication module is further configured to cause the first entity to send indication information to the second entity, and the indication information is used to cancel the transmission of the random access preamble.

14. The communication device according to claim 13, wherein The communication module is further configured to cause the first entity 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 instruction, so that the communication device executes the method according to any one of claims 1-4, or so that the communication device executes the method according to any one of claims 5-7.

16. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs. When the computer instructions or programs are run on a computer, the method according to any one of claims 1-4 is executed, or the method according to any one of claims 5-7 is executed.

17. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method according to any one of claims 1-4 is executed, or the method according to any one of claims 5-7 is executed.

Images