Communication method and device

Abstract

A communication method and apparatus, the method comprising: a network device sending first configuration information and second configuration information, the first configuration information being used for configuring a first priority of a first LCH, the second configuration information being used for configuring a second priority or a first parameter of the first LCH, the second priority being higher than the first priority; the terminal device determines a first uplink grant, the first uplink grant being used for indicating a first resource, the first resource being used for transmitting first data, and the first data being data of a first LCH; and if the first data is the first type of data, the terminal device determines the priority of the first uplink grant according to the second priority or the first parameter, and sends the first data according to the priority of the first uplink grant. Therefore, even if the first data in the first LCH is multiplexed to the MAC PDU, the priority of the first LCH is the second priority, the first type of data can be preferentially sent as much as possible, and the delay requirement is met.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] The priority of an uplink grant can be determined based on the priority of at least one logical channel (LCH) corresponding to that uplink grant. If the LCH includes delay-critical data, the network device can configure a higher priority for that LCH. In this case, the LCH priority includes an old priority and a new priority, with the new priority being higher. Delay-critical data can be understood as more urgent data to be transmitted, such as data with a low remaining transmission delay budget.

[0003] When multiple uplink grants conflict, the priority of the conflicting uplink grants determines which Media Access Control (MAC) Protocol Data Unit (PDU) corresponding to that uplink grant will be transmitted first. When the LCH has two priorities, there is currently no specific solution for determining the uplink grant. If the uplink grant priority is determined according to the old priority of the LCH, it may result in data that needs to be transmitted first not being transmitted first, or even failing to be transmitted at all. Summary of the Invention

[0004] This application provides a communication method and apparatus to prioritize the transmission of low-latency data to meet latency requirements.

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

[0006] Firstly, a communication method is provided, which can be applied to a terminal-side device (also called a terminal device). For example, the terminal device can be a terminal equipment, or it can be a module or unit that performs some functions of the terminal equipment (e.g., a circuit or chip / chip system in the terminal equipment (e.g., a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) or other functional module), or the terminal device can be a logical node, logical module, or software module that implements all or part of the functions of the terminal equipment. For ease of description, the following example uses the application of this method to a terminal device.

[0007] The communication method includes: a terminal device determining a first uplink grant, the first uplink grant being used to indicate a first resource, wherein the first resource is used to transmit first data, the first data originating from a first LCH; the terminal device receiving first configuration information and second configuration information, wherein the first configuration information is used to configure a first priority of the first LCH, the second configuration information is used to configure a second priority of the first LCH, the second priority being higher than the first priority, or the second configuration information is used to configure a first parameter of the first LCH; if the first data is first type data, the terminal device determining the priority of the first uplink grant according to the first priority, the second priority, or the first parameter; and the terminal device sending the first data according to the priority of a first uplink candidate.

[0008] The first data originating from the first LCH includes: first data cached in the first LCH, or first data already multiplexed into a MAC PDU in the first LCH. The first type of data can be data that needs to be sent with priority, such as low-latency data. In this method, a second priority or a first parameter can be configured for the first LCH to achieve fast transmission of low-latency data. The first parameter can limit the number of LCHs that can be carried on the first resource, thereby allowing the first LCH to be preferentially multiplexed into the MAC PDU of the first uplink grant. When determining the priority of the first uplink grant, the priority of the first LCH can be determined based on the first priority, the second priority, or the first parameter, and then the priority of the first uplink grant can be determined based on the priority of the first LCH. Thus, even if the first data in the first LCH has already been multiplexed into a MAC PDU, if the first LCH has a second priority, the priority of the first uplink grant will not decrease due to the first priority of the first LCH, thereby ensuring that the first type of data is sent with priority and meeting the actual latency requirements of the first type of data.

[0009] In one implementation, defining the first data as first type data includes: the first data being first type data at a first moment, where the first moment is the transmission moment of the MAC PDU including the first data. As long as the first data is first type data before being transmitted based on the first uplink grant instruction and the first resource, then the priority of the first LCH is the second priority, or the first LCH is configured with the first parameter. By determining the first moment, misjudgment of the first LCH priority can be reduced, thereby ensuring that first type data is transmitted with priority as much as possible.

[0010] In one implementation, the first LCH is configured with a first parameter, and the priority of the first LCH is the second priority.

[0011] If the first LCH is configured with the first parameter, the priority of the first LCH can be defaulted to the second priority.

[0012] In one implementation, the priority of the first uplink grant is not determined based on the first priority. When the first data is of the first type and the priority of the first LCH is the second priority, the terminal device may ignore the first priority of the first LCH or not determine the priority of the first uplink grant based on the first priority when determining the priority of the first uplink grant.

[0013] In one implementation, before determining the priority of the first uplink grant, the terminal device is further configured with signaling for conflict handling in resource overlap scenarios. For example, the terminal device is configured with logical channel-based prioritization (lch-based priority). The terminal device configuration includes the configuration of a specific entity of the terminal device (e.g., a MAC entity). The signaling for conflict handling in resource overlap scenarios can be used to handle: overlaps between uplink grants, and / or overlaps between uplink grants and scheduling requests (SRs). For example, in a scenario where uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize which uplink grant. As another example, in a scenario where SRs and uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize either the SR or the uplink grant.

[0014] In one implementation, if the first data is of the first type, the priority of the first LCH is the second priority.

[0015] In one implementation, the second configuration information is used to configure the first parameter of the first LCH, and the first uplink grant is the preferred uplink grant.

[0016] When the first LCH is configured with the first parameter, the first data that is multiplexed to or can be multiplexed to the MAC PDU corresponding to the first uplink grant can be considered as the first type of data and needs to be sent first. Therefore, the first uplink grant can be defaulted as the priority uplink grant to ensure that the first data is sent as early as possible.

[0017] In one implementation, the second priority is the highest priority.

[0018] In one implementation, the method further includes: the terminal device determining a second uplink grant, the second uplink grant being used to indicate a second resource; wherein, if the second resource partially or completely overlaps with the first resource, the second uplink grant is a downgraded uplink grant.

[0019] When the first data is of the first type and the first uplink authorization is the preferred uplink authorization, if the resources indicated by the second uplink authorization overlap with the resources indicated by the first uplink authorization, the second uplink authorization can be defaulted to a lower-priority uplink authorization.

[0020] In one implementation, the second uplink grant does not include the first type of data. When the first uplink grant is the preferred uplink grant because the first data is of the first type, if the resource indicated by the second uplink grant overlaps with the resource indicated by the first uplink grant, and the second uplink grant does not include the first type of data, the second uplink grant can be regarded as a downgraded uplink grant.

[0021] In one implementation, the second uplink grant includes the first type of data. When the first uplink grant is the preferred uplink grant because the first data is of the first type, if the resource indicated by the second uplink grant overlaps with the resource indicated by the first uplink grant, and the second uplink grant does not include the first type of data, the second uplink grant can be regarded as a downgraded uplink grant.

[0022] In one implementation, the first data is classified as first type data if it satisfies at least one of the following: at a first moment, the first data has not been discarded; or, at a first moment, the remaining transmission delay budget of the first data is less than or equal to a first threshold. Optionally, the first data has not been transmitted, for example, the first data has not been transmitted via any MAC PDU.

[0023] In one implementation, the method further includes: a terminal device receiving third configuration information, the third configuration information being used to configure a first threshold.

[0024] Secondly, a communication method is provided, which can be applied to a terminal device (also known as a terminal device). For ease of description, the following example uses the application of this method to a terminal device. For the specific implementation of the terminal device, please refer to the relevant description in the first aspect above, which will not be repeated here.

[0025] The communication method includes: a terminal device triggering a Service Response (SR) at a second time, the SR being triggered by a first Data Chain Receiver (LCH); if the first LCH includes first type data at a third time, the terminal device determines the SR as a priority SR. The third time is either the time the SR is transmitted or the time the first data is transmitted, and the first data is data in the first LCH.

[0026] The first type of data can be data that needs to be sent with priority, such as low-latency data. In this method, when the first data corresponding to the first LCH is first type data, the SR triggered by the first LCH can be regarded as a priority SR. In this way, the network device can prioritize allocating resources for transmitting the first data to the terminal device according to the SR, thereby ensuring that the first type of data is sent with priority and meeting the actual latency requirements of the first type of data.

[0027] In one implementation, the priority of the SR is determined based on the priority of the first LCH at the third time step.

[0028] In one implementation, the priority of the first LCH includes a third priority and a fourth priority, with the fourth priority being higher than the third priority, and the priority of the first LCH is the fourth priority.

[0029] The third priority can be seen as the priority when the first LCH does not include data of the first type, and the fourth priority can be seen as the priority when the first LCH includes data of the first type. In this scheme, when the first data from the first LCH is data of the first type, then the priority of the first LCH is the fourth priority, so as to ensure that data of the first type is sent first as much as possible.

[0030] In one implementation, the method further includes: a terminal device receiving second configuration information, the second configuration information being used to configure first parameters of a first LCH. The first parameters can indirectly indicate a higher priority for the first LCH. For example, if the first LCH is configured with the first parameters, the priority of the first LCH is fourth priority.

[0031] In one implementation, before determining the priority of the first uplink grant, the terminal device is further configured with signaling for conflict handling in resource overlap scenarios. For example, the terminal device is configured with logical channel-based prioritization (lch-based priority). The terminal device configuration includes the configuration of a specific entity of the terminal device (e.g., a MAC entity). The signaling for conflict handling in resource overlap scenarios can be used to handle: overlaps between uplink grants, and / or overlaps between uplink grants and scheduling requests (SRs). For example, in a scenario where uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize which uplink grant. As another example, in a scenario where SRs and uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize either the SR or the uplink grant.

[0032] In one implementation, when the resources of the SR and the fourth resources of the fourth uplink grant indication partially or completely overlap, the fourth resources are used to transmit uplink data, the SR is the preferred SR, and the fourth uplink grant is the down-priority uplink grant.

[0033] In one implementation, the fourth uplink grant does not include the first type of data, or the fourth uplink grant is not configured with the second configuration information.

[0034] In one implementation, the priority of the SR is higher than that of the fourth uplink grant.

[0035] In one implementation, the first data is of the first type at the third time when at least one of the following conditions is met: at the third time, the first data has not been discarded; or, at the third time, the remaining transmission delay budget of the first data is less than or equal to a first threshold.

[0036] In one implementation, the interval between the third time point and the second time point is greater than or equal to the first time period.

[0037] In one implementation, the method further includes: the terminal device receiving fifth configuration information, the fifth configuration information being used to configure a first duration.

[0038] Regarding the beneficial effects of the second aspect and its various implementation methods, please refer to the aforementioned beneficial effects of the first aspect and its various implementation methods, which will not be repeated here.

[0039] Thirdly, embodiments of this application provide a communication device that has the functionality to implement the behavior in any of the method examples of the first or second aspect described above. The beneficial effects can be found in the relevant descriptions of the first or second aspect, and will not be repeated here. For example, the communication device may be a terminal device as described in the first or second aspect, or it may be a device capable of supporting the terminal device in implementing the functions required by the method provided in the first or second aspect. For example, the communication device may be a chip or chip system in the terminal device.

[0040] In one possible design, the communication device includes a baseband device and a radio frequency device.

[0041] In one possible design, the communication device includes corresponding means or modules for performing the methods of the first or second aspect. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit is capable of performing both transmitting and receiving functions. When the transceiver unit performs the transmitting function, it may be called a transmitting unit (sometimes also called a transmitting module), and when it performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit may be the same functional unit, referred to as the transceiver unit, which performs both transmitting and receiving functions; or, the transmitting unit and the receiving unit may be different functional units, with "transceiver unit" being a collective term for these functional units. These units (modules) can perform the corresponding functions in the method examples of the first or second aspect described above, as detailed in the method examples, and will not be repeated here.

[0042] Fourthly, embodiments of this application provide a communication device, which can be the communication device described in the third aspect of the above embodiments, or a chip or chip system disposed in the communication device described in the third aspect. The communication device includes a communication interface and a processor, and optionally, a memory. The memory is used to store computer programs, instructions, or data, and the processor is coupled to the memory and the communication interface. When the processor reads the computer program, instructions, or data, it causes the communication device to execute the method performed by the terminal device in the above method embodiments. For example, the communication device can be a terminal device or a functional module in a terminal device, such as a baseband chip and a radio frequency chip.

[0043] Fifthly, embodiments of this application provide a chip system including a processor and a communication interface for implementing the methods described in the first or second aspect. Optionally, the chip system further includes a memory. The memory stores computer programs (also referred to as code or instructions). The processor retrieves and executes the computer program from the memory, causing a device equipped with the chip system to perform the methods of the first or second aspect and any implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0044] Sixthly, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, pins, or related circuits, etc. The logic circuitry is used to execute the methods described in the first or second aspect.

[0045] In practical implementation, the aforementioned communication device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, and various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0046] In one implementation, when the communication device is a wireless communication device, the wireless communication device can be a terminal device such as a mobile phone. The interface circuit can be a radio frequency processing chip in the wireless communication device, and the processing circuit can be a baseband processing chip in the wireless communication device.

[0047] In a seventh aspect, embodiments of this application provide a communication system, which includes a terminal device and a network device, wherein the terminal device is used to implement the functions described in the first or second aspect.

[0048] Eighthly, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, cause the methods described in the first or second aspect and any of their implementations to be implemented.

[0049] Ninthly, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the methods described in the first or second aspect and any of their implementations to be implemented.

[0050] The beneficial effects of the third to ninth aspects and their implementation methods mentioned above can be referenced to the beneficial effects of the first to second aspects and any one of their implementation methods. Attached Figure Description

[0051] Figure 1 This is a schematic diagram of the network architecture of the communication system provided in the embodiments of this application;

[0052] Figure 2 A schematic diagram illustrating the multiplexing of data from multiple logical channels to a MAC PDU, as provided in an embodiment of this application;

[0053] Figure 3 A flowchart illustrating the communication method 300 provided in an embodiment of this application;

[0054] Figure 4 A flowchart illustrating the communication method 400 provided in an embodiment of this application;

[0055] Figure 5 A schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0056] Figure 6 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0057] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as Long Term Evolution (LTE) communication systems, 5th Generation (5G) mobile communication systems / New Radio (NR) communication systems, or future mobile communication systems, or other similar communication systems. Other similar communication systems may include Wireless Fidelity (WIFI), Vehicle-to-Everything (V2X), Internet of Things (IoT) systems, and so on.

[0058] Please see Figure 1 This illustration shows a communication system applicable to embodiments of this application. The communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system may also include the Internet. Figure 1 (Using this as an example).

[0059] The wireless access network 100 may include at least one network device and at least one terminal device. For example, the wireless access network 100 includes two network devices, 110a and 110b, and terminal devices, such as 120a to 120j. Figure 1 The network architecture shown is merely illustrative; the number of terminal devices and / or network devices may be fewer or more. The communication system described in the embodiments of this application is intended to more clearly illustrate the technical solutions of the embodiments of this application and does not constitute a limitation on the communication system to which the embodiments of this application apply. For example, the communication system may also include other devices, such as wireless relay devices and wireless backhaul devices, etc. Figure 1 Not shown in the diagram. Those skilled in the art will recognize that, with the evolution of network architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. When applying the technical solutions of the embodiments of this application to other communication systems, the devices, components, modules, etc., in the embodiments can be replaced with corresponding devices, components, modules in other communication systems, without limitation.

[0060] In this embodiment, network equipment refers to (radio)access network ((R)AN) equipment / RAN node. In this embodiment, (R)AN and RAN are interchangeable. RAN can be a cellular system related to the 3rd generation partnership project (3GPP), such as a 5G / NR mobile communication system or a future-oriented evolution system. RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized RAN (vRAN), a non-terrestrial network (NTN), etc. RAN can also be a communication system that integrates two or more of the above systems. RAN equipment can also be called a RAN node, RAN entity, or access node, etc.

[0061] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), or a base station in a future mobile communication system. RAN nodes can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or radio controllers. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU).

[0062] In another possible scenario, a RAN node can be a module or unit that performs some of the functions of a base station; or multiple RAN nodes can collaborate to assist terminal devices in achieving wireless access, with different RAN nodes performing some of the functions of a base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The function of a CU can be implemented by a single entity or by different entities. For example, the function of a CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0063] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0064] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the MAC layer, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0065] The above division of the processing functions of CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not limit this. For example, in one design, CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are located in the DU.

[0066] In another possible design, the DU and RU collaborate to implement the PHY layer functionality, or, more specifically, a portion of the PHY layer functionality of the DU can be moved to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions. Alternatively, the DU may be configured to implement higher-level functions in the PHY layer, and the RU may be configured to implement lower-level functions in the PHY layer, or both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functionality closer to the MAC layer, and lower-level functions may include another portion of the physical layer's functionality closer to the mid-RF side. This application does not limit the specific functions of the DU and RU. The interface between the DU and RU can be called a fronthaul interface. In one design, the CU may not have a PDCP layer; for example, the CU may only include an RRC layer. The CU-CP may not have PDCP-C. The CU-UP may not have PDCP-U, or may not have a CU-UP. In one design, the DU may not have an RLC layer; for example, the DU may only have a MAC and a higher PHY layer.

[0067] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRTRIC) or a near-real-time RAN intelligent controller (RIC / nRT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0068] In this application embodiment, anything capable of data communication with a base station can be considered a terminal device. Terminal devices are also called terminals, terminal equipment, user equipment (UE), mobile stations, or mobile terminals, etc. Terminal devices can be widely used in various scenarios. For example, terminal devices can be: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, helicopters, airplanes, ships, or smart home devices (such as televisions, air conditioners, robot vacuums, speakers, set-top boxes), relays, customer premises equipment (CPE), etc.

[0069] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system, such as a water meter or electricity meter. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technology, thereby realizing an intelligent network that enables human-machine interconnection and object-to-object interconnection.

[0070] When the terminal device is applied to V2X, it can also be called a V2X device, such as a smart car, an unmanned car, a driverless car, a pilotless car, or an automobile, or a roadside unit (RSU). All the terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit. In-vehicle terminal devices can be vehicle equipment, in-vehicle modules, vehicles, in-vehicle units (on-board units, OBUs), RSUs, in-vehicle infotainment systems (or in-vehicle transmission units) (telematics boxes, T-boxes), chips, or SoCs, etc. The aforementioned chips or SoCs can be installed in the vehicle, OBU, RSU, or T-box.

[0071] Taking a network device as a base station and a terminal device as a UE as an example, the base station and UE can be fixed or mobile. The base station and UE can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the base station and UE.

[0072] The communication system applicable to the embodiments of this application has been described above. To facilitate understanding of the technical solutions provided by the embodiments of this application, the relevant technical features and technical terms involved in the embodiments of this application will be explained below.

[0073] (1) Logical channel prioritization (LCP) process

[0074] Communication between network devices and terminal devices follows a specific protocol layer structure. For example, data sent from a network device to a terminal device must pass through the user plane protocol layer. The user plane protocol layer structure includes the SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The functions of one or more of these protocol layers can be implemented by one or more nodes / entities of the network device or terminal device.

[0075] During uplink transmission, after the PDCP layer obtains data from the upper layer, it transmits the data to the RLC and MAC layers. The MAC layer then generates a transport block (TB), which is then wirelessly transmitted through the physical layer. Data is encapsulated at each layer. Data received by a layer from its upper layer is considered a service data unit (SDU) for that layer. The protocol stack header of the current layer is added to the SDU, and after encapsulation, it becomes a PDU, which is then passed to the next layer. The RLC and MAC layers correspond via the LCH. It should be noted that in this embodiment, uplink transmission refers to transmission from the terminal device to the network device.

[0076] In some scenarios, multiple service data items may need to be sent from a terminal device to a network device simultaneously. Correspondingly, the terminal device's MAC entity may correspond to multiple LCHs. The process of multiplexing (or mapping) the data from these multiple LCHs to a single MAC PDU is called the LCP process. Specifically, the terminal device follows certain multiplexing criteria to multiplex at least one LCH to a single MAC PDU. These criteria include the terminal device selecting at least one LCH that can be multiplexed to a single MAC PDU, and then multiplexing the data from that LCH to a single MAC PDU based on its priority. In some scenarios, the data in an LCH can be understood as data from some or all of the entities corresponding to that LCH. For example, the data in an LCH could be data from the RLC entity corresponding to that LCH, or data from the PDCP entity corresponding to that LCH. The PDCP entity can be the PDCP entity corresponding to the RLC entity corresponding to the LCH.

[0077] Network devices configure certain parameters for each LCH (Local Channel Gateway) to allow terminal devices to filter at least one LCH that can be multiplexed onto a single MAC PDU. For ease of description, these parameters are collectively referred to as second parameters in this embodiment. The second parameters indicate the conditions that the resources mapped to the data in the LCH must meet. Data in the LCH can only be transmitted on the MAC PDU corresponding to the uplink grant if the resources corresponding to that uplink grant meet certain conditions. Possible second parameters for the LCH are listed below.

[0078] (1-1) List of allowed sub-carrier spacings (SCS)

[0079] The allowedSCS-List typically contains a list of SCSs. If the LCH is configured with the allowedSCS-List, then the LCH data can only be mapped to the resources with uplink authorization for the SCSs included in the allowedSCS-List.

[0080] (1-2) Maximum Physical Uplink Shared Channel (PUSCH) Duration

[0081] When an LCH is configured with `maxPUSCH-Duration`, its data can only be mapped to resources with a time domain resource shorter than or equal to `maxPUSCH-Duration`, or it can only be transmitted via PUSCHs with a time domain resource shorter than `maxPUSCH-Duration`. When not configured, the LCH's data can be transmitted via any PUSCH.

[0082] (1-3) Allowed to configure authorization types (Configured Grant Type 1 Allowed)

[0083] When an LCH is configured with a Grant Type 1 Allowed, its data can be transferred via a type 1 configured grant (CG); otherwise, the LCH data may not be able to be transferred via a type 1 CG.

[0084] (1-4) List of allowed Serving Cells

[0085] The `allowedServingCells` list includes a list of serving cells (SCs). When the LCH is configured with `allowedServingCells`, data from that LCH can only be transmitted using resources from the cells indicated in the SC list. When this parameter is not configured, data from that LCH can be transmitted by any configured serving cell.

[0086] (1-5) Allowed CG-List

[0087] The `allowedCG-List` contains a list of CGs that restrict uplink authorization to CGs only. Uplink authorization as a CG can also be understood as uplink authorization being dynamically specified. When an LCH is configured with `allowedCG-List`, if the uplink authorization is a CG and the configured authorization index is within the CG list included in `allowedCG-List`, it means that the LCH's data can be transferred on resources of that CG. If the CG list is empty, it means that the LCH's data cannot be transferred on resources of any CG. If the LCH is not configured with `allowedCG-List`, it means that the LCH's data can be transferred on resources of any CG. If the LCH is also configured with the parameter "configuredGrantType1Allowed", only type 1 CGs in the LCH's CG list can transfer resources of that LCH.

[0088] (1-6) Allowed PHY-PriorityIndex

[0089] The value of allowedPHY-PriorityIndex can be either p0 or p1. allowedPHY-PriorityIndex only restricts uplink grants to dynamically scheduled cases. If the LCH is configured with allowedPHY-PriorityIndex and the uplink grant also has a PHY-priority index, the LCH data can only be mapped / reused to a dynamically scheduled grant with the same value. In other words, when the value configured with allowedPHY-PriorityIndex is the same as the PHY-priority index indicated by the downlink control information (DCI) scheduling uplink resources, the LCH data can be transmitted by the resource indicated by the DCI. If the LCH is configured with allowedPHY-PriorityIndex, but the dynamically scheduled grant does not indicate physical layer priority information (phy-priority index), then the dynamically scheduled resource can only transmit LCH data with an allowedPHY-PriorityIndex value of a specific value (such as p0). If allowedPHY-PriorityIndex is not configured, the LCH data can be mapped to a dynamic license.

[0090] (1-7) Allowed HARQ mode

[0091] HARQ modes include modeA and modeB, with modeB essentially meaning no HARQ retransmission. Allowed HARQ-mode indicates the HARQ modes that the LCH is allowed to use. If the LCH is not configured with allowed HARQ-mode, its data can be mapped to any HARQ mode (or transmitted through any HARQ process).

[0092] The second parameter mentioned above can be used alone or in combination. For example, when an LCH is configured with both (1-3) allowing the configuration of the grant type and (1-6) allowing the physical layer priority index, the data in that LCH can only be multiplexed into the transmission resource if both conditions (1-3) and (1-6) are met. Based on the second parameter, the terminal device can filter at least one LCH that can be multiplexed into a MAC PDU corresponding to the uplink grant. Then, according to the priority of the at least one LCH, the data in the at least one LCH is multiplexed into a MAC PDU.

[0093] Network devices configure priority, prioritized bit rate (PBR), and bucket size (BSD) for each LCH. For any LCH j, when the LCH is established, Bj (which can be understood as the number of tokens in LCH j) is initialized to 0. Before each LCP process, the MAC entity should increment Bj (Bj = PBR multiplied by T), where T is the time elapsed since the last increment of Bj. When Bj is greater than the bucket size (PBR multiplied by BSD), Bj is set to the bucket size.

[0094] For LCHs selected based on the above parameters, those with Bj > 0 are sorted in descending order of LCP. If an LCH's PBR is set to infinity, the MAC entity should allocate resources for all available (or pending) data of that LCH before allocating resources for data with lower priority than that LCH. After allocating resources for LCH j, the amount of data corresponding to the resources mapped to MAC PDUs (such as MAC SDUs) should be removed from Bj of that LCH. When all selected LCHs have been mapped, and there are still resources remaining in the MAC PDUs, the selected LCHs can be remapped according to descending priority of LCP. In this case, the value of Bj can be disregarded. For example, if the data of a high-priority LCH is large enough to fill the entire remaining MAC PDU, the remaining MAC PDUs can only transmit the data of this LCH.

[0095] For easier understanding, please refer to Figure 2 This diagram illustrates the multiplexing of multiple LCHs into a single MAC PDU. Figure 2 Taking multiple LCHs (LCH1, LCH2, and LCH3) as an example, LCH1 has a higher priority than LCH2, and LCH2 has a higher priority than LCH1. LCH1 corresponds to token number B1, LCH2 to token number B2, and LCH3 to token number B3. When multiplexing LCH1 to LCH3 to a MAC PDU, firstly, B1 data points from LCH1 are mapped to the MAC PDU, and B1 is updated. If the MAC PDU has remaining resources, then B2 data points from LCH2 are mapped to the MAC PDU, and B2 is updated. If the MAC PDU has remaining resources, then B3 data points from LCH3 are mapped to the MAC PDU, and B3 is updated. When all data in LCH1 to LCH3 has been mapped, and the MAC PDU still has remaining resources, then the data in LCH1 is filled first, regardless of the size of B1, until the MAC PDU is completely filled.

[0096] Figure 1 In the LCP process shown, multiple LCHs are multiplexed into a single MAC PDU according to their priority. This may result in data requiring priority transmission (e.g., low-latency data) not being transmitted first, or even failing to complete transmission on time. Taking LCH1 and LCH2 as an example, assuming LCH1 has a higher priority than LCH2, but the remaining latency budget for data in LCH1 is greater than that for data in LCH2, meaning that data in LCH2 needs to be transmitted first. Figure 1 The method involves mapping LCH1 data to the MAC PDU first, and then mapping LCH2 data to the MAC PDU. This results in LCH1 data being sent before LCH2 data, and LCH2 data not being transmitted first.

[0097] To address this, it is proposed that if data in the LCH requires priority transmission, a higher priority can be configured for that LCH. Essentially, an LCH has two priorities, for example, priority A and priority B, where priority B is higher than priority A. In this case, if the data in the LCH requires priority transmission, then the LCH has the higher priority (priority B); if the data in the LCH does not require priority transmission, then the LCH has the lower priority (priority A). Relatively speaking, priority A can be called the old priority, and priority B can be called the new priority. It is understandable that the new priority applies to data in the LCH that requires priority transmission (e.g., low-latency data).

[0098] Data with insufficient remaining transmission delay budget is considered invalid. In this case, the LCH corresponding to the data does not adopt a new priority. Data invalidation can be defined as the remaining transmission delay budget being below a delay threshold. For example, if the delay threshold is zero, the remaining transmission delay budget is zero, indicating invalid data. When the remaining transmission delay budget is determined by a packet loss timer, the data is considered invalid when the corresponding packet loss timer expires. Typically, when the corresponding packet loss timer expires, if the data has already been delivered to a lower layer by the PDCP layer, the PDCP layer will send a packet loss indication message to the lower layer. Therefore, when a lower layer (e.g., the MAC layer) receives the packet loss indication message, it considers the data invalid. "Receiving a packet loss indication message" can also be understood as the data being discarded.

[0099] If data that has already been transmitted is no longer considered low-latency data, the corresponding LCH (Local Chronicle) may not adopt the new priority. For example, if the remaining transmission delay budget of data in an LCH is below a certain threshold (i.e., the data in the LCH has a low-latency budget), the LCH can adopt the new priority. If, after this data is transmitted, there is no low-latency data in the LCH, then the LCH can adopt the old priority. If low-latency data in an LCH is never transmitted and its remaining transmission delay budget is insufficient, and the MAC layer receives a packet loss indication, it considers the LCH to retain the old priority.

[0100] (2) Uplink transmission when uplink resources overlap

[0101] In this embodiment, overlap can also be understood as collision. Uplink resource overlap includes resource overlap of uplink grant indications, also known as uplink grant overlap. Uplink grant overlap refers to partial or complete overlap of resources among multiple uplink grant indications. For example, multiple uplink grants include uplink grant #1 and uplink grant #2. The overlap of uplink grant #1 and uplink grant #2 can be understood as the overlap of resources corresponding to uplink grant #1 and resources corresponding to uplink grant #2. These resources can be time-domain resources, frequency-domain resources, or time-frequency-domain resources. Among them, frequency-domain resource overlap can also be understood as uplink grant #1 and uplink grant #2 being located in the same bandwidth part (BWP).

[0102] If two uplink grants (e.g., a first uplink grant and a second uplink grant) overlap, only the first uplink grant or the second uplink grant can be transmitted at any given time. In one implementation, the transmission of the first uplink grant or the second uplink grant can be determined based on their priority. If the priority of the first uplink grant is higher than that of the second uplink grant, then the first uplink grant is transmitted, and the transmission of the second uplink grant is abandoned.

[0103] The priority of any uplink grant is the highest priority LCH among the multiple LCHs that can be multiplexed to the MAC PDU corresponding to that uplink grant. For example, for uplink grant #1, the LCHs that can be multiplexed to the MAC PDU of uplink grant #1 include LCH1 to LCH3, where LCH3 has the highest priority. Therefore, the priority of uplink grant #1 is the priority of LCH3. MAC PDUs that can be multiplexed to the uplink grant include MAC PDUs that have not yet been generated or have not yet been stored in the HARQ cache. In some scenarios, for multiple LCHs that can be multiplexed to the MAC PDU corresponding to that uplink grant, these LCHs need to contain data that can be transmitted when considering priority. For example, for uplink grant #1, the LCHs of the MAC PDU that can be reused to uplink grant #1 include LCH1 to LCH3. Among them, LCH3 has the highest priority, LCH2 has the next highest priority, and LCH1 has the lowest priority. If there is no data to be transmitted in LCH3 at this time, then the priority of uplink grant #1 is the priority of LCH2.

[0104] Alternatively, the priority of any uplink grant is the highest priority LCH among the multiple LCHs multiplexed to the MAC PDU corresponding to that uplink grant. For example, for uplink grant #2, the LCHs multiplexed to the MAC PDU for uplink grant #2 include LCH1 to LCH3, where LCH3 has the highest priority. Therefore, the priority of uplink grant #2 is the priority of LCH3. MAC PDUs multiplexed to the uplink grant include already generated MAC PDUs or MAC PDUs already stored in the HARQ cache.

[0105] For uplink grant #1, if there is no uplink grant #2 that meets the following conditions, uplink grant #1 can be considered a prioritized uplink grant, and uplink grant #2 a deprioritized uplink grant: Condition 1, overlapping PUSCHs; Condition 2, not deprioritized; Condition 3, on the same BWP; Condition 4, uplink grant #2 has a higher priority. It should be noted that in this embodiment, overlap includes time-domain overlap, frequency-domain overlap, or time-frequency domain overlap.

[0106] Uplink grant #1 can be either a dynamically scheduled uplink grant or a semi-statically scheduled uplink grant. For dynamically scheduled uplink grants, the grant can be indicated by a DCI scrambled with either the cell radio network temporary indenter (C-RNTI) or the configured scheduling radio network temporary identifier (CS-RNTI). Optionally, when the uplink grant's DCI is CS-RNTI scrambled, the uplink grant can be used for retransmissions in semi-static transmissions, for example, if the new data indicator (NDI) in the DCI is '1'. In some scenarios, the DCI can also be used to indicate the activation or deactivation of a semi-static uplink grant, such as when the NDI in the DCI is '0'.

[0107] Uplink resource overlap also includes the overlap of resources in the SR and the uplink grant indication (which can be simply referred to as SR and uplink grant overlap). For example, if the resource used to send the SR is resource #1 and the uplink grant indication is resource #2, and resources #1 and resource #2 partially or completely overlap, then the SR and uplink grant overlap.

[0108] When a Service Request (SR) and an uplink grant overlap, the priority of transmitting the SR or the corresponding MAC PDU can be determined based on their respective priorities. Specifically, if the SR's priority is higher than the uplink grant's priority, the SR is considered the higher-priority SR, and the uplink grant is considered a lower-priority uplink grant; the SR is then transmitted first. Conversely, if the SR's priority is lower than or equal to the uplink grant's priority, the SR is considered a lower-priority SR, and this SR will not be transmitted on resources overlapping with the uplink grant. The SR's priority depends on the priority of the LCH that triggered it.

[0109] (3) Triggering SR

[0110] There are several ways / conditions to trigger SR (Residual Response) messages. For example, triggering based on a Delay Status Report (DSR) will trigger SR; similarly, triggering based on a Buffer Status Report (BSR) will also trigger SR. Of course, SR can also be triggered independently under specific conditions. Network devices can configure a remainingTimeThreshold for a logical channel group (LCG). When the remaining transmission delay budget of any data within the LCG (which can be understood as any LCH within the LCG) falls below this threshold, a DSR can be triggered to notify the network device of the LCG's delay information.

[0111] The DSR can indicate the latency information of the data with the shortest remaining transmission latency budget in the LCG, such as the absolute value of the remaining transmission latency budget. Optionally, the DSR can carry the amount of latency data for that LCG, such as the amount of data whose remaining transmission latency budget is below a latency threshold. It should be understood that the latency information of the data with the shortest remaining transmission latency budget may not correspond one-to-one with the amount of data reported in the DSR.

[0112] When a DSR is triggered, if there is no SR to be transmitted triggered by the LCH that triggered the DSR, then the SR can be triggered. It's easy to understand that each LCH is associated with an SR configuration, such as using an SR identifier (identity, ID) to determine the SR configuration corresponding to that LCH. In other words, based on the LCH that triggered the SR and the SR ID corresponding to that LCH, the configuration of that SR, such as its transmission resources, can be determined.

[0113] The remaining transmission delay budget can be determined based on the remaining value of the data's packet loss timer, the data's packet delay budget (PDB), or the PDU set delay budget (PSDB). The packet loss timer is typically started when data arrives at the Packet Data Convergence Protocol (PDCP) layer, and its value (or duration) can be configured by the network device via higher-layer signaling. When the packet loss timer expires, if the data has not yet been mapped to a MAC PDU or has not yet been transmitted, the data can be discarded.

[0114] Alternatively, the remaining transmission delay budget can be the timeout of the packet delay budget (PDB) corresponding to the data to be transmitted. PDB can be understood as the latency requirement from the terminal device to the network device or to the user plane function (UPF) element. For example, PDB is the time elapsed from when a PDU arrives at the terminal device until that PDU is successfully received by the network device or UPF element. Typically, PDB is configured by the core network (CN) through a 5G Quality of Service (QoS) identifier (5QI).

[0115] (4) In the embodiments of this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns", that is, "one or more". "At least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A / B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and / or c means the following combination: a exists alone, b exists alone, c exists alone, a and b exist simultaneously, a and c exist simultaneously, b and c exist simultaneously, or a, b and c exist simultaneously, where a, b, and c can be single or multiple.

[0116] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

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

[0118] In this application, the ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first priority" and "second priority" refer to two different priorities, and do not indicate a difference in priority or importance between the two priorities.

[0119] In the embodiments of this application, the solutions in each embodiment can be used in a reasonable combination, and the explanations or descriptions of various terms, similar operations, or steps appearing in the embodiments can be referenced or explained to each other in the embodiments, without limitation.

[0120] As mentioned earlier, when uplink grants overlap, the priority of the overlapping uplink grants determines which uplink grant's corresponding MAC PDU is transmitted first. When each LCH has only one priority, the uplink grant priority can be determined based on the priorities of these LCHs. However, when new priorities are introduced into the LCH, there is no clear solution for how to determine the uplink grant priority, i.e., how to determine which LCH priority should be referenced for the uplink grant priority.

[0121] If we continue to use the current method of determining LCH priority based on the presence of low-latency data in the LCH, it may result in data that needs to be transmitted first not being transmitted first, or even failing to be transmitted at all. Figure 2For example, suppose LCH1's priority includes both old and new priorities. At time #1, LCH1 includes low-latency data, so its priority is the new priority. Assume LCH1's priority is higher than LCH2's, and LCH2's priority is higher than LCH3's. The uplink grant corresponds to LCH1 through LCH3, and its priority is LCH1's priority. LCH1 through LCH3 are multiplexed into a single MAC PDU (or the data from LCH1 through LCH3 generates a MAC PDU). At time #2, the low-latency data in LCH1 has been multiplexed into the MAC PDU, and LCH1 no longer contains low-latency data; therefore, LCH1's priority reverts to the old priority. Thus, at time #2, the uplink grant priority is the highest priority among LCH1 through LCH3. Since LCH1's priority changes from the new to the old priority, LCH1's priority may be lower than LCH2 or LCH3's priority. Assuming LCH1's old priority is lower than LCH2's priority, then at time #2, the uplink grant priority is LCH2's priority. In reality, although LCH1 doesn't include low-latency data at time #2, the low-latency data from LCH1 multiplexed to the MAC PDU hasn't been sent yet and should be prioritized. However, at time #2, the uplink grant priority is determined based on LCH1's old priority, which might lower the uplink grant priority, preventing it from being transmitted first. Consequently, the low-latency data from LCH1 also won't be prioritized, failing to meet the actual latency requirements of the low-latency data.

[0122] Therefore, the solution provided in this application embodiment is as follows. In this application embodiment, when the LCH of multiplexed or reusable data in a MAC PDU corresponding to an uplink grant contains multiple priorities, the priority of the LCH can be determined according to certain criteria, and the priority of the corresponding uplink grant can be further determined. For example, when determining the priority of the uplink grant, the priority of each LCH is determined based on whether the data of each LCH included in the MAC PDU is first type data, and the priority of the uplink grant is determined based on the priority of each LCH. Here, first type data can be understood as data that needs to be sent first. In this way, even if a certain LCH multiplexes the data that needs to be sent first into the MAC PDU, the priority of the LCH is still the new priority, and the priority of the uplink grant corresponding to the MAC PDU will not decrease due to the priority of the LCH, thereby ensuring that the first type data is sent first and meeting the actual latency requirements of the first type data.

[0123] The communication method provided in the embodiments of this application is described below.

[0124] In the following description, the communication method provided in the embodiments of this application is applied to... Figure 1 Taking the network architecture shown as an example, the communication method provided in this application embodiment can be executed by a network device and a terminal device. The steps executed by the terminal device can be implemented by the terminal device itself, or by components within the terminal device (such as a baseband chip, or other processing units or processor modules). The steps executed by the network device can be implemented by the RAN device itself, or by components within the RAN device (such as a baseband chip, or other processing units or processor modules), or by components that perform some or all of the functions of the RAN device (such as a CU, DU, or RU). The specific form of the network device and the terminal device is not limited; for example, the network device can be a chip, and the terminal device can be a device; or both the network device and the terminal device can be chips or devices. In possible scenarios, the network device can be... Figure 1 The terminal device 120a shown, or it could be Figure 1 The chip (system) in the terminal device 120a; the terminal device can be Figure 1 The network device 110a in the middle, or it could be Figure 1 The chip (system) in network device 110a. In possible scenarios, the network device can be... Figure 1 The terminal device 120b shown, or it could be Figure 1 The chip (system) in the terminal device 120b; the terminal device can be Figure 1 The terminal device 120a, or it could be Figure 1 The chip (system) in the terminal device 120a.

[0125] In this application embodiment, when uplink resources overlap, the behavior of the terminal device includes the following situations:

[0126] Scenario 1: For any overlapping uplink resources, if no authorized MAC PDU has been generated yet, only one MAC PDU will ultimately be generated. This MAC PDU is determined based on the priority of the overlapping uplink resources. For example, if the overlapping uplink resources are uplink-authorized resources, then the MAC PDU is generated based on the priority of the overlapping uplink authorizations. If the overlapping uplink resources are both uplink-authorized resources and SR resources, then the MAC PDU is generated based on the priority of the SR and the priority of the uplink authorization. If the uplink authorization priority corresponding to the MAC PDU is lower than the priority of the SR, then no MAC PDU may be generated for that uplink authorization.

[0127] Case 2: For any overlapping uplink resources, if a MAC PDU for one resource has already been generated and the other resource has a lower priority, then the MAC layer entity will not generate a MAC PDU for the other resource.

[0128] Scenario 3: For any overlapping uplink resources, if a MAC PDU for one resource has already been generated, and the other resource has a higher priority, then the MAC layer entity generates a MAC PDU for the other resource. It can be understood that the MAC PDU for the already generated resource is a lower-priority MAC PDU. Alternatively, the MAC PDU for the other resource has a higher priority than the already generated MAC PDU, representing a higher-priority uplink grant.

[0129] In this application embodiment, the first type of data can be understood as data that needs to be transmitted with priority, or data that urgently needs to be transmitted. For example, the first type of data can be regarded as low-latency data (delay-critical data), or data of low-latency type services. For example, the first type of data can be extended reality (XR) service data. The communication method provided in this application embodiment is applicable to low-latency service scenarios and meets the low-latency requirements of service data.

[0130] In this embodiment, the configuration information sent by the network device to the terminal device can be carried in one or more of RRC, DCI, or MAC control element (CE). For example, the first configuration information, the second configuration information, or the third configuration information can be carried in one or more of RRC, DCI, or MAC CE.

[0131] Please see Figure 3 , Figure 3 This is a flowchart illustrating the communication method 300 provided in an embodiment of this application. Figure 3 This method is introduced from the perspective of interaction between terminal devices and network devices. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication capabilities. Furthermore, the processing performed by a single execution entity can be divided into multiple execution entities, which can be logically and / or physically separated. For example, the processing performed by the terminal device can be divided into execution by at least one of the following: RLC layer entity, MCA layer entity, etc. Figure 3 As shown, the communication method 300 includes the following steps.

[0132] S301. The network device sends first configuration information, which is used to configure the first priority of the first LCH.

[0133] Accordingly, the terminal device receives first configuration information from the network device, which can be used to configure the priority of the first LCH, such as a first priority. As mentioned above, the network device can configure the priority for each LCH via higher-layer signaling. For the first LCH, the network device can configure a first priority for the first LCH using the first configuration information.

[0134] S302. The network device sends second configuration information, which is used to configure the second priority of the first LCH, or the second configuration information can be used to configure the first parameter of the first LCH.

[0135] Accordingly, the terminal device receives second configuration information from the network device. To prioritize data transmission in the first LCH, the network device can configure a higher priority for the first LCH, such as a second priority; alternatively, the network device can configure a first parameter for the first LCH. These cases are described below.

[0136] Scenario 1: To quickly transmit data with a low remaining transmission latency budget for a certain LCH, a higher priority can be configured for that LCH to prioritize its data transmission. For example, assuming the transmission latency budget for the first data in the first LCH is tight, the network device can configure a second priority for the first LCH using second configuration information. Optionally, the second priority is higher than the first priority. This is equivalent to the network device configuring both a first and a second priority for the first LCH. The first data in the first LCH can be multiplexed to the first MAC PDU according to either the first or second priority. For example, if the remaining transmission latency budget for the first data is low, then the first data in the first LCH is multiplexed to the first MAC PDU according to the second priority; if the remaining transmission latency budget for the first data is high, then the first data in the first LCH is multiplexed to the first MAC PDU according to the first priority.

[0137] Scenario 2: When the remaining transmission delay budget for a certain LCH is low, it is desirable to prioritize the transmission of data in that LCH. To address this, network devices can configure parameters for that LCH to limit the amount of LCH data that uplink resources can carry, thereby ensuring that data in that LCH is transmitted preferentially. For example, by restricting certain uplink licensed resources to only transmit data from specific LCHs, priority can be given to transmitting data from those specific LCHs.

[0138] For example, a network device can configure a first parameter of the first LCH using second configuration information to restrict the resources of the first uplink grant to preferentially transmit the first data in the first LCH. When the first LCH is configured with the first parameter, it may implicitly indicate one or more of the following:

[0139] (1) When the first LCH is configured with the first parameter, the priority of the first LCH is the second priority. In this way, by changing or increasing the priority of the first LCH, the first data in the first LCH can be preferentially multiplexed to the first MAC PDU, thereby ensuring that the first data is transmitted with priority as much as possible.

[0140] (2) When the first LCH is configured with the first parameter, the data of the first LCH can be sent in the resource corresponding to the first uplink grant. In this way, by limiting the LCHs that the first uplink grant can carry, such as excluding or prohibiting the transmission of LCHs configured with the first parameter in the first uplink grant, the transmission of LCHs configured with the first parameter in the first uplink grant can be guaranteed to be prioritized for transmission.

[0141] (3) When the first LCH is configured with the first parameter, the first LCH can ignore one or more of the following parameters already configured for the first LCH: allowedSCS-List, maxPUSCH-Duration, configured Grant Type1Allowed, allowed Serving Cells, allowed CG-List, allowedPHY-PriorityIndex, or allowedHARQ-mode. In this way, the first LCH can be enabled to ignore some restrictions, so that the first data in the first LCH is multiplexed to the MAC PDU corresponding to the first uplink grant, thereby ensuring that the first data is sent first as much as possible.

[0142] For example, in a possible scenario, the terminal device receives the first uplink grant, but according to the allowedSCS-List, maxPUSCH-Duration, configured Grant Type1 Allowed, allowed Serving Cells, allowed CG-List, allowedPHY-PriorityIndex, or allowedHARQ-mode configured by the network device for the first LCH, it can be determined that the data in the first LCH cannot be transmitted on the resource corresponding to the first uplink grant. For example, the resource corresponding to the first uplink grant does not meet the conditions corresponding to the allowedSCS-List configured by the first LCH. In this case, the data in the first LCH cannot be transmitted, resulting in wasted resources. By ignoring the above parameters configured by the network device for the first LCH in (3), the restrictions of these parameters on the reuse of the first LCH on the resource corresponding to the first uplink grant can be ignored, enabling the data in the first LCH to be reused on the resource corresponding to the first uplink grant, thereby ensuring the transmission of the data in the first LCH as much as possible and guaranteeing the priority transmission of low-latency data.

[0143] (4) When the first LCH is configured with the first parameter, the first LCH is reused to the first MACPDU using the second set of reuse criteria.

[0144] The first LCH uses the second set of multiplexing criteria to multiplex data to the first MAC PDU. This can also be understood as the first LCH ignoring the first set of multiplexing criteria and using the second set, which differs from the first set. As mentioned earlier, the first set of multiplexing criteria refers to the criteria for multiplexing LCH data to the MAC PDU according to the second parameter. Here, the second set of multiplexing criteria can be understood as the criteria for multiplexing LCH data to the MAC PDU according to the first parameter. The first set of multiplexing criteria can also be understood as the multiplexing criteria used when the LCH does not include low-latency data. For example, for the first LCH, the first set of multiplexing criteria could be that the first LCH multiplexes its data to the first MAC PDU according to the second parameter. Optionally, the network device configures the second set of multiplexing criteria for the first LCH.

[0145] Network devices can configure a first set of multiplexing criteria and a second set of multiplexing criteria for the first LCH. The parameters corresponding to the first set of multiplexing criteria are different from those of the second set. For example, the parameters corresponding to the first set of multiplexing criteria include allowed SCS-List, maxPUSCH-Duration, and allowed Serving Cells; the parameters corresponding to the second set of multiplexing criteria include allowed Serving Cells and allowed CG-List. When low-latency data exists in the first LCH, the second set of multiplexing criteria is used. When low-latency data does not exist in the first LCH, the first set of multiplexing criteria is used. Thus, when low-latency data exists in the first LCH, configuring the first parameter for the first LCH is equivalent to configuring the second set of multiplexing criteria for the first LCH, which can prevent data transmission mismatch caused by the first LCH ignoring the first set of multiplexing criteria.

[0146] Optionally, any of the above (1)-(4) will take effect only when the first LCH is configured with the first parameter and the first LCH contains data of the first type. For example, taking content (1) as an example, when the first LCH is configured with the first parameter, if the first LCH contains data of the first type, the priority of the first LCH is the second priority.

[0147] The specific implementation of the first parameter is not limited in the embodiments of this application. For example, the first parameter can be an indicator that allows for the priority transmission of low-latency data (allowedDelayCriticalDataPrioritization). When an LCH is configured with the first parameter, the data of that LCH can be transmitted with priority. Alternatively, when an LCH is configured with the first parameter and there is first type data in that LCH, the data of that LCH can be transmitted with priority, or the first type of data in that LCH can be transmitted with priority. As another example, the first parameter can also be used to determine a first threshold. Optionally, the first threshold can be the same as the threshold that triggers DSR.

[0148] It should be noted that the execution order of S301 and S302 is not restricted. For example, S302 can be executed after S301 or before S301. Furthermore, the first configuration information and the second configuration information can be carried on different signaling messages or on the same signaling message. It is understood that if the first configuration information and the second configuration information are carried on the same signaling message, then S310 and S302 will be executed simultaneously.

[0149] S303. The terminal device determines a first uplink grant, which instructs a first resource, which is used to transmit first data, and the first data is data of a first LCH.

[0150] The embodiments of this application do not limit the type of the first uplink grant. For example, the first uplink grant can be a dynamically scheduled uplink grant. In this case, the terminal device determines the first uplink grant by receiving the first uplink grant, that is, the first uplink grant is dynamically scheduled to the terminal device by the network device. Alternatively, the type of the first uplink grant can also be a semi-statically scheduled uplink grant. In this case, the terminal device determines the first uplink grant based on the semi-static scheduling configuration.

[0151] The resources corresponding to the first uplink grant can be used to send the MAC PDU corresponding to the first uplink grant (e.g., referred to as the first MAC PDU). The terminal device, receiving the first uplink grant from the network device, can determine the resources used to send the first MAC PDU. The first MAC PDU may include first data. It can be understood that the first uplink grant may indicate the first resources used to send the first data. The first data is data from the first LCH, or the first data comes from the first LCH, or the first data is data from the first LCH that can be multiplexed to the first MAC PDU. The first data being data from the first LCH that can be multiplexed to the first MAC PDU can be understood as the first data not yet being multiplexed into the first MAC PDU.

[0152] S304. The terminal device determines the priority of the first uplink authorization.

[0153] The terminal device determining the priority of the first uplink grant can be done together with the terminal device determining the first uplink grant. Alternatively, S303 and S304 can be a single step, or the terminal device can skip S303 and determine the first uplink grant while performing S304.

[0154] The terminal device determines the first uplink grant and its priority. Optionally, the terminal device may determine the priority of the first uplink grant based on the priority of the first LCH, including the following cases.

[0155] (1) The terminal device can determine the priority of the first uplink authorization based on the first priority.

[0156] For example, when the MAC PDU corresponding to the first uplink grant reuses or can reuse the first data, and the first LCH is configured with a first priority and a second priority, or is configured with a first priority and a first parameter, the priority of the first uplink grant can be determined by referring to the first priority.

[0157] This can also be understood as follows: when the first LCH is configured with both first and second priorities, its priority can be determined as first priority. Alternatively, when the first LCH is configured with both first priority and first parameter, its priority can be determined as first priority. Accordingly, when the first data is multiplexed to / can be multiplexed to the MAC PDU corresponding to the first uplink grant, the first uplink grant's priority is determined based on the priority of the LCH to which the data multiplexed / can be multiplexed by the corresponding MAC PDU belongs. Referring to the first priority of the first LCH will avoid any confusion.

[0158] In one scenario, the first data has been reused to a MAC PDU, which is stored in the HARQ cache. In this scenario, the priority of the first LCH can be first priority. Optionally, the first data can be first type data, or it can be other than first type data.

[0159] (2) The terminal device can determine the priority of the first uplink authorization based on the second priority.

[0160] For example, when the MAC PDU corresponding to the first uplink grant reuses or can reuse the first data, and the first LCH is configured with a first priority and a second priority, the priority of the first uplink grant can be determined by referring to the second priority.

[0161] This can also be understood as follows: when the first LCH is configured with both first and second priorities, the priority of the first LCH can be determined as the second priority. Correspondingly, when the first data is multiplexed to / can be multiplexed to the MAC PDU corresponding to the first uplink grant, the first uplink grant's priority is determined based on the priority of the LCH to which the data multiplexed / can be multiplexed by the corresponding MAC PDU belongs. This can be done by referring to the second priority of the first LCH, thus avoiding any confusion.

[0162] In one scenario, the first data has been reused into a MAC PDU, which has been stored in the HARQ cache. In this scenario, the priority of the first LCH can be the second priority. Optionally, the first data can be data of type 1, or it can be data of type 2.

[0163] (3) The terminal device can determine the priority of the first uplink authorization based on the first parameter.

[0164] For example, when the MAC PDU corresponding to the first uplink grant reuses or can reuse the first data, and the first LCH is configured with the first priority and the first parameter, the priority of the first uplink grant can be determined by referring to the first parameter.

[0165] This can also be understood as follows: when the first LCH is configured with a first priority and a first parameter, the priority of the first LCH can be the second priority. Correspondingly, when the first data is multiplexed / can be multiplexed to the MAC PDU corresponding to the first uplink grant, when determining the priority of the first uplink grant based on the priority of the LCH to which the data multiplexed / can be multiplexed by the corresponding MAC PDU belongs, the second priority or the first parameter of the first LCH can be referenced to avoid confusion.

[0166] In one scenario, the first data has already been reused in a MAC PDU, which may have been stored in a HARQ cache. In this scenario, when the first LCH is configured with a first parameter, the priority of the first LCH can be the second priority. Optionally, the first data can be data of type first, or it can be data of a different type.

[0167] Understandably, the MAC entity of the terminal device determines the first uplink grant at time #1, which instructs the first MAC PDU to be sent on the first resource at time #2. The MAC entity of the terminal device performs the LCP procedure at time #3, between time #1 and time #2, that is, assembling / generating the first MAC PDU at time #3. According to the LCP procedure, the first data in the first LCH is multiplexed into the first MAC PDU. In other words, the first data comes from the first LCH; the first data can be data cached in the first LCH, data already multiplexed into the MAC PDU from the first LCH, or data already stored in the HARQ cache from the first LCH.

[0168] When determining the priority of the first LCH or the priority of the first uplink grant, the terminal device can also determine it based on whether the first data from the first LCH is of the first type.

[0169] In this context, "first-type data" can be understood as data that needs to be transmitted with priority, such as low-latency data. Before the terminal device sends the first MAC PDU, the first data may be in the first LCH or may have already been multiplexed into the first MAC PDU but has not yet been sent out through the resources of the first uplink grant. If the priority of the first LCH is determined based on whether it includes first-type data, then the first LCH will be considered to have the highest priority. Consequently, the priority of the first uplink grant may be determined based on this first priority, potentially lowering the priority of the first uplink grant and causing the first data to not be sent with priority, thus failing to meet the latency requirements of the first data. To maximize the priority of first data transmission, the priority of the first uplink grant can be determined based on whether the first data is first-type data before being sent out through the resources of the first uplink grant. In some scenarios, the first data may no longer be cached in the LCH or may have already been transmitted by any MAC PDU. For example, the first data from the first LCH is transmitted via a MAC PDU at the fifth time, and the first data is retransmitted at a later time (such as the first time) via the first MAC PDU corresponding to the first uplink grant. In this scenario, the terminal device can also determine the priority of the first uplink grant based on whether the first data is of the first type of data.

[0170] For ease of description, the time of transmission of the MAC PDU containing the first data (i.e., the first MAC PDU) is referred to as the first time. The first data being first type data includes the first data being first type data at the first time. The first data is first type data at the first time when it satisfies at least one of the following: (1) at the first time, the remaining transmission delay budget of the first data is less than or equal to a first threshold; (2) at the first time, the first data has not been discarded.

[0171] Wherein, the first data at the first moment is first type data, which can be replaced by any of the following descriptions: the remaining transmission delay budget of the first data at the first moment is less than or equal to a first threshold; or, the first data has not been discarded at the first moment / before the first moment; or, the remaining transmission delay budget of the first data at the first moment is less than or equal to the first threshold, and the first data has not been discarded. The first threshold can be predefined or (pre)configured. For example, the network device can send third configuration information to the terminal device, which can be used to configure the first threshold. Optionally, the first data at the first moment can also be data that has not been sent, such as data that has not been transmitted through any MAC PDU. Optionally, the first parameter can be the first threshold, or the first threshold implicitly indicates the first parameter. In this case, the third configuration information and the second configuration information can be the same configuration information, or the second configuration information can be the third configuration information.

[0172] Optionally, the first time point can also be replaced by any time point between the time point of determining the first uplink grant and the time point of transmitting the first MAC PDU. For example, the first time point can be the time point of receiving the first uplink grant, or the first time point can be the time point of determining the priority of the first uplink grant, or the first time point can be the time point of assembling the first MAC PDU.

[0173] In some scenarios, if the first data is of type 1 at the first moment, the priority of the first LCH is the second priority. When the first data is of type 1 at the first moment, the terminal device can determine the priority of the first uplink grant based on the second priority. Thus, when the terminal device determines the priority of the first uplink grant, the priority of the first uplink grant will not decrease due to the decrease in the priority of the first LCH, allowing the first data to be sent with priority as much as possible. Optionally, in this case, the second priority can be considered the highest priority of the first LCH.

[0174] In this scenario, the terminal device determines the priority of the first uplink grant based on the second priority of the first LCH. This can also be understood as the terminal device ignoring the first priority of the first LCH when determining the priority of the first uplink grant, or the terminal device not determining the priority of the first uplink grant based on the first priority of the first LCH. If the first data is of type 1, determining the priority of the first uplink grant based on the second priority of the first LCH can prioritize the transmission of the first data, thus meeting the latency requirements of the first data.

[0175] Alternatively, if the first data is of type 1 at the first moment, the terminal device can determine the priority of the first uplink grant based on the first parameter. For example, if the first LCH is configured with the first parameter, the priority of the first LCH can be considered as the second priority, or the first uplink grant as the first priority uplink grant. If the first data is of type 1, determining the priority of the first uplink grant based on the first parameter of the first LCH can determine that the first uplink grant is the first priority uplink grant, thus prioritizing the transmission of the first data to meet its latency requirements. Conversely, if the first data is not of type 1 at the first moment, the priority of the first LCH is the first priority.

[0176] In a possible scenario, if the network device also configures a third uplink grant for the terminal device, this third uplink grant indicates a third resource, which is used for the retransmission of the first MAC PDU. The terminal device determines the third uplink grant at the fourth moment. If the first data is of the first type before the retransmission of the first MAC PDU, then the priority of the third uplink grant is determined according to the second priority of the first LCH.

[0177] S305. The terminal device sends the first data according to the priority of the first uplink authorization.

[0178] After determining the priority of the first uplink grant, the terminal device can decide whether to send the first data based on the priority of the first uplink grant. When the first uplink grant is a priority uplink grant, the terminal device sends the MAC PDU corresponding to the first uplink grant. Alternatively, the terminal device can send the first data, which includes the first data, on the resource indicated by the first uplink grant.

[0179] In some scenarios, if there is no uplink grant overlapping with the resources corresponding to the first uplink grant, the first uplink grant can be considered the preferred uplink grant. In possible scenarios, the network device also configures a second uplink grant for the terminal device. This second uplink grant indicates a second resource, which can be used for the transmission of the second MAC PDU of the second uplink grant. The second MAC PDU includes the second data of the second LCH. The terminal device determines the priority of the second uplink grant in the same way as it determines the priority of the first uplink grant, and will not be repeated here. For example, the terminal device can determine the priority of the second uplink grant based on the second priority of the second LCH, if the second data is of type first type data before the second MAC PDU is sent.

[0180] It should be noted that if the remaining transmission delay budget of the first data is lower than or less than the first threshold, the first data is of the first type; if the remaining transmission delay budget of the second data is lower than or less than the second threshold, the second data is of the first type. The first threshold and the second threshold may be the same or different.

[0181] If the first resource of the first uplink grant instruction and the second resource of the second uplink grant instruction partially or completely overlap, the priority of sending the first MAC PDU corresponding to the first uplink grant or the second MAC PDU corresponding to the second uplink grant can be determined based on the priority of the first uplink grant and the second uplink grant. If the priority of the first uplink grant is higher than the priority of the second uplink grant, then the first MAC PDU is sent first; if the priority of the second uplink grant is higher than the priority of the first uplink grant, then the second MAC PDU is sent first. Optionally, the second uplink grant and the first uplink grant are located in the same BWP.

[0182] Where a second uplink grant overlaps with the first uplink grant, the condition for treating the first uplink grant as the priority uplink grant may include at least one of the following: Condition 1, Condition 2, or Condition 3. Condition 1 is that the priority of the second uplink grant is lower than or equal to the priority of the first uplink grant. Condition 2 is that the second uplink grant has not been downgraded in priority. Condition 3 is that the second uplink grant and the first uplink grant are not located in the same BWP.

[0183] Optionally, the first uplink grant can be a dynamic uplink grant or a semi-static uplink grant; the second uplink grant can also be a dynamic uplink grant or a semi-static uplink grant. Details can be found in the preceding description and will not be repeated here. In this case, the above conditions can also be understood as follows: when there is no second uplink grant that has not been downgraded in priority, has a higher priority than the first uplink grant, is located in the same BWP as the first uplink grant, and overlaps with the first uplink grant, the first uplink grant is the preferred uplink grant. In this case, the second uplink grant can be considered a downgraded uplink grant.

[0184] In some possible scenarios, the first uplink grant and the second uplink grant may have the same priority. Optionally, if the first resource indicated by the first uplink grant and the second resource indicated by the second uplink grant partially or completely overlap, and if the priority of the first uplink grant and the priority of the second uplink grant are the same, the terminal device may decide to prioritize sending the first MAC PDU or the second MAC PDU.

[0185] Alternatively, the terminal device may determine whether to prioritize sending the first MAC PDU or the second MAC PDU based on the remaining transmission delay budget of the first data and the remaining transmission delay budget of the second data. If the remaining transmission delay budget of the first data is less than the remaining transmission delay budget of the second data, the first MAC PDU is sent first. If the remaining transmission delay budget of the first data is greater than the remaining transmission delay budget of the second data, the second MAC PDU is sent first.

[0186] The terminal device determines whether to prioritize sending the MAC PDU corresponding to the data based on the remaining transmission delay budget. This can also be understood as the terminal device determining the priority of the LCH corresponding to the data based on the remaining transmission delay budget. For example, a first uplink grant corresponds to a first MAC PDU containing first data from the first LCH, and the remaining transmission delay budget for the first data is the first delay budget; a second uplink grant corresponds to a second MAC PDU containing second data from the second LCH, and the remaining transmission delay budget for the second data is the second budget. When the first resource indicated by the first uplink grant and the second resource indicated by the second uplink grant partially or completely overlap, the priority of the uplink grant can be determined based on the first and second remaining delays. For example, when the first delay budget is less than the second delay budget, the first uplink grant can be the priority uplink grant, and the second uplink grant can be a lower priority uplink grant.

[0187] In possible implementations, when the first MAC PDU corresponding to the first uplink grant includes first data, and the first data is of type first, and when the first resource overlaps with resources indicated by other uplink grants, the first uplink grant can be considered a prioritized uplink grant, and the other uplink grants can be considered deprioritized uplink grants. For example, if the first resource and the second resource partially or completely overlap, and the first data is of type first, then the first uplink grant is a prioritized uplink grant, and the second uplink grant is a deprioritized uplink grant. Optionally, the second uplink grant does not include first type data. The exclusion of first type data from the second uplink grant can also be described as the LCH corresponding to the second uplink grant not including first type data, or the MAC PDU corresponding to the second uplink grant not including first type data.

[0188] Alternatively, when the priorities of the first uplink grant and the second uplink grant are the same, the priority of the first uplink grant or the second uplink grant can be determined without considering their types. For example, if the first uplink grant is dynamically scheduled and the second uplink grant is semi-statically scheduled, but the remaining transmission delay budget for the first data is higher than that for the second data, then the priority of the second uplink grant can be considered higher than that of the first uplink grant. Alternatively, the second uplink grant can be considered a prioritized uplink grant, and the first uplink grant a deprioritized uplink grant.

[0189] When the first uplink grant is a priority uplink grant, the terminal device can send the first uplink grant. In this case, the corresponding MAC PDU may not be sent on the uplink resources corresponding to the second uplink grant. Alternatively, when the first uplink grant is a de-priority uplink grant, the MAC PDU corresponding to the first uplink grant may not be sent. Optionally, when the first uplink grant is a de-priority uplink grant, the MAC PDU corresponding to the first uplink grant may not be sent on the resources where the first and second uplink grants overlap. When the first uplink grant is a priority uplink grant, the corresponding MAC PDU may be sent on the uplink resources corresponding to the first uplink grant. Therefore, step S305 is not a mandatory step. Figure 3 The image is indicated by a dashed line.

[0190] In communication method 300, when the terminal device determines the uplink grant priority, it determines the priority of each LCH based on whether the data in each LCH included in the MAC PDU is first-type data, and then determines the uplink grant priority based on the priority of each LCH. First-type data can be understood as data that needs to be sent with priority. Thus, even if data that needs to be sent with priority by a certain LCH has been multiplexed into the MAC PDU, the priority of that LCH remains the new priority. The priority of that LCH will not cause the uplink grant priority corresponding to the MAC PDU to decrease, thereby ensuring that first-type data is sent with priority and meeting the actual latency requirements of first-type data.

[0191] Optionally, before executing S303 or before receiving the first uplink grant, the terminal device is further configured with signaling for conflict handling in resource overlap scenarios. For example, the terminal device is configured based on logical channel prioritization. The terminal device configuration includes the configuration of a specific entity of the terminal device (e.g., a MAC entity). The signaling for conflict handling in resource overlap scenarios can be used to handle: overlap between uplink grants, and / or overlap between an uplink grant and a SR. For example, in a scenario where uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize which uplink grant. As another example, in a scenario where SR and uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize either SR or the uplink grant.

[0192] Please see Figure 4 , Figure 4 This is a flowchart illustrating the communication method 400 provided in an embodiment of this application. Figure 4 This method is introduced from the perspective of interaction between terminal devices and network devices. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication capabilities. Furthermore, the processing performed by a single execution entity can be divided into multiple execution entities, which can be logically and / or physically separated. For example, the processing performed by the terminal device can be divided into execution by at least one of the following: RLC layer entity, MAC layer entity, etc. Figure 4 As shown, the communication method 400 includes the following steps.

[0193] S401, The terminal device triggers SR at the second moment.

[0194] The terminal device can trigger the SR based on the first LCH, that is, the SR is triggered by the first LCH.

[0195] S402. Determine the priority of the SR based on the first data of the first LCH.

[0196] When a terminal device triggers an SR based on a first LCH, the priority of the SR can be determined according to the first data in the first LCH. The first data refers to the data in the first LCH. As described in the aforementioned communication method 300, before executing S401, the network device can configure two priorities for the first LCH. For example, the priorities of the first LCH may include a third priority and a fourth priority. Optionally, the fourth priority is higher than the third priority. It is understood that the third priority is similar to the aforementioned first priority, and the fourth priority is similar to the aforementioned second priority. Alternatively, the network device can configure a first parameter for the first LCH; for example, the network device sends second configuration information to the terminal device. In this case, the priority of the first LCH can be determined according to the first parameter; for example, when the first LCH is configured with the first parameter, the priority of the first LCH can be considered to be the fourth priority. See the relevant description in communication method 300 for details, which will not be repeated here.

[0197] The terminal device determines the priority of the SR based on the first data of the first LCH, including the following situations.

[0198] (1) The terminal device can determine the priority of SR based on the third priority.

[0199] For example, if the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a fourth priority, the terminal device can determine the priority of the SR based on the third priority. It can be considered that when the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a fourth priority, the priority of the first LCH is the third priority. Alternatively, if the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a first parameter, the terminal device can determine the priority of the SR based on the third priority. It can be considered that when the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a first parameter, the priority of the first LCH is the third priority. Accordingly, when the terminal device determines the priority of the SR based on the priority of the LCH corresponding to the SR, it explicitly uses the third priority when referring to the priority of the first LCH, avoiding any confusion. Optionally, the first data can be first type data, or it can be non-first type data. In other words, the determination of the priority of the SR is unrelated to whether first type data exists in the first LCH.

[0200] (2) The terminal device can determine the priority of SR based on the fourth priority.

[0201] For example, if the terminal device triggers an SR at a second time and the first LCH is configured with both a third and a fourth priority, the terminal device determines the priority of the SR based on the fourth priority. It can be considered that when the terminal device triggers an SR at a second time and the first LCH is configured with both a third and a fourth priority, the priority of the first LCH is the fourth priority. Accordingly, when the terminal device determines the priority of the SR based on the priority of the LCH corresponding to the SR, it explicitly uses the fourth priority when referring to the priority of the first LCH, thus avoiding any confusion. Optionally, the first data may or may not be first-type data. In other words, the determination of the SR's priority may be independent of whether first-type data exists in the first LCH.

[0202] (3) The terminal device can determine the priority of SR based on the first parameter.

[0203] For example, if the terminal device triggers SR at a second time, and the first LCH is configured with the third priority and the first parameter, the priority of SR can be determined by referring to the fourth priority. It can be considered that when the terminal device triggers SR at a second time, and the first LCH is configured with the third priority and the first parameter, the priority of the first LCH is the fourth priority.

[0204] Optionally, when determining the priority of the first LCH or the priority of the SR, the terminal device may also determine it based on whether the data from the first LCH includes the first type of data.

[0205] For example, after the terminal device triggers SR at the second time, if the first LCH includes data of the first type, the terminal device can determine that the priority of the first LCH is the fourth priority. Optionally, after the terminal device triggers SR at the second time, if the first LCH includes data of the first type at the third time, the terminal device determines that the priority of the first LCH is the fourth priority. Similarly, after the terminal device triggers SR at the second time, if the first LCH includes data of the first type, the terminal device can determine that the priority of SR is the fourth priority. Optionally, after the terminal device triggers SR at the second time, if the first LCH includes data of the first type at the third time, the terminal device determines that the priority of SR is the fourth priority. The first LCH including data of the first type at the third time can also be replaced by the first data being data of the first type at the third time.

[0206] In one possible scenario, the third time point is either the time point at which the SR (Send SR) is transmitted, which is later than the second time point, or the time point at which the first data is transmitted. If the first LCH (Local Time Channel) includes first type data at the third time point, then the priority of the SR triggered by the first LCH can be determined based on the priority of the first LCH at the third time point. For example, if the priority of the first LCH at the third time point is the fourth priority, the priority of the SR can be determined based on the fourth priority. As another example, if the first LCH includes first type data at the third time point, and the first LCH can be configured with a first parameter, then the SR can be considered the priority SR.

[0207] The first LCH includes first type data at the third time, which can also be considered as the first data corresponding to the first LCH being first type data at the third time. Specifically, the first data is considered first type data at the third time if it satisfies at least one of the following: (1) the first data has not been discarded at the third time; (2) the remaining transmission delay budget of the first data is less than or equal to the first threshold at the third time. Optionally, the first data at the first time can also be data that has not been sent, such as data that has not been transmitted through any MAC PDU. The definition of first data being first type data at the third time is similar to the definition of first data being first type data at the first time, and will not be repeated here.

[0208] Optionally, a first duration is spaced between the third time point and the second time point. This first duration can be pre-configured, semi-statically configured, or dynamically indicated. For example, the network device sends fifth configuration information to the terminal device, which can be used to configure the first duration.

[0209] Understandably, when the third moment is the transmission time of the first data, the terminal device has difficulty determining the actual transmission time of the first data because the scheduling delay is usually determined by the network device. Therefore, the network device can predict the transmission time of the first data and indicate it to the terminal device. For example, the network device can determine, based on historical information, approximately how long after receiving the SR (Scheduled Response Time) can resources be allocated for the data of the LCH (Local Chronicle) that triggered the SR. The network device can configure a first duration for the terminal device based on this determined duration. After triggering or sending the SR, if the first data is of the first type after the first duration, the terminal device can determine the priority of the SR based on the fourth priority or the first parameter of the first LCH.

[0210] For example, the first LCH triggers an SR at a second time. At the second time, the first LCH contains first data, but the first data is not of the first type. The terminal device can determine the transmission time of the first data (i.e., the third time) based on the second time and the first duration. If the first LCH contains first type data at the third time, the priority of the SR is determined according to the fourth priority or the first parameter of the first LCH.

[0211] Optionally, when the third time point is the time when the first data is transmitted, there is a first time interval between the third time point and the sixth time point. The sixth time point can be the time when the SR is transmitted, which is later than the second time point and earlier than the third time point. In this case, the seventh time point for determining the SR priority can be any time between the second time point and the sixth time point.

[0212] For example, the first LCH triggers an SR at the second time. At the second time, the first LCH contains first data, but the first data is not of the first type. The terminal device can determine the transmission time of the first data (i.e., the third time) based on the sixth time and the first duration. If the first LCH contains first type data at the third time, the priority of the SR is determined according to the fourth priority or the first parameter of the first LCH.

[0213] Optionally, the first duration can be implemented using a first timer. For example, after triggering or sending an SR, the first timer is started, and the first timer terminates at the third time. The time at which the SR priority is determined can be the seventh time, which can be any time between the second and third times, or any time between the second and sixth times.

[0214] In some scenarios, if there is no uplink authorization that overlaps with the resource corresponding to the SR, then the SR can be considered the preferred SR.

[0215] In some scenarios, the resources of the SR (Search Request) may partially or completely overlap with the fourth resources indicated by the fourth uplink grant, which are used for transmitting uplink data. In this case, the priority of sending the SR or the MAC PDU corresponding to the fourth uplink grant can be determined based on the priority of the SR and the priority of the fourth uplink grant.

[0216] Optionally, the resources of the SR partially or completely overlap with the fourth resources of the fourth uplink grant indication. If the first LCH includes first type data at the third time, then the SR is the preferred SR, and the fourth uplink grant is a downgraded uplink grant. Alternatively, the priority of the SR is higher than the priority of the first uplink grant. Optionally, the fourth uplink grant does not include first type data, or the first uplink grant is not configured with second configuration information.

[0217] If the priority of the SR is the same as the priority of the first uplink grant, and if the first LCH that triggers the SR is configured with the first parameter or the fourth priority, then the transmission of the SR can take precedence.

[0218] Optionally, if the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a fourth priority, this SR can be considered a priority SR. Alternatively, if the terminal device triggers an SR at a second time, and the first LCH is configured with a third priority and a first parameter, this SR can be considered a priority SR. Further, if the first LCH is configured with a third priority and a fourth priority, and the first LCH contains first type data at a third time, this SR is a priority SR. Alternatively, if the first LCH is configured with a third priority and a first parameter, and the first LCH contains first type data at a third time, this SR is a priority SR. The fourth uplink grant overlapping with the SR can be a down-priority uplink grant.

[0219] It can be assumed that when a fourth uplink grant overlaps with an SR, the conditions for considering the SR as the preferred SR can include at least one of the following: Condition 1, Condition 2, or Condition 3. Condition 1 is that the priority of the fourth uplink grant is lower than or equal to the priority of the SR. Condition 2 is that the fourth uplink grant has not been downgraded in priority. Condition 3 is that the resources corresponding to the fourth uplink grant and the SR are not located in the same BWP.

[0220] Optionally, the fourth uplink grant can be a dynamic uplink grant or a semi-static uplink grant; details can be found in the previous description and will not be repeated here. In this case, the above condition can also be understood as follows: when there is no fourth uplink grant that has not been downgraded, has a higher priority than SR, is located in the same BWP as the first uplink grant, and overlaps with SR, SR is the preferred SR. In this case, the fourth uplink grant can be a downgraded uplink grant.

[0221] S403, the terminal device sends a scheduling request according to the priority of the scheduling request.

[0222] When the SR is a priority SR, the terminal device can send the SR. In this case, the corresponding MAC PDU may not be sent on the uplink resources corresponding to the fourth uplink grant. Alternatively, when the SR is a lower priority SR, the SR may not be sent. Optionally, when the SR is a lower priority SR, the SR may not be sent on resources where the SR overlaps with the fourth uplink grant. When the fourth uplink grant is a priority uplink grant, the corresponding MAC PDU may be sent on the uplink resources corresponding to the fourth uplink grant. Therefore, S403 is not a mandatory step. Figure 4 The image is indicated by a dashed line.

[0223] Optionally, before determining the priority of the SR, the terminal device is also configured with signaling for conflict handling in resource overlap scenarios. For example, the terminal device is configured for logical channel prioritization. The terminal device configuration includes the configuration of a specific entity of the terminal device (e.g., a MAC entity). The signaling for conflict handling in resource overlap scenarios can be used to handle: overlap between uplink grants, and / or overlap between uplink grants and SRs. For example, in a scenario where uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize which uplink grant. As another example, in a scenario where SRs and uplink grants overlap, the signaling for conflict handling in resource overlap scenarios can be used to prioritize either the SR or the uplink grant.

[0224] In communication method 400, when the resources of the SR overlap with the resources of the uplink grant, if the first LCH contains first type data, the priority of the SR can be determined according to the fourth priority or the first parameter of the first LCH. Communication method 400 can, as far as possible, ensure that first type data is sent first, thus meeting the actual latency requirements of the first type data.

[0225] The methods provided in the embodiments of this application above are described using terminal devices and network devices as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions of the methods provided in the embodiments of this application above, the steps executed by the terminal device / network device can be implemented by different functional entities constituting the terminal device / network device. To achieve the functions of the methods provided in the embodiments of this application above, the terminal device / network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0226] Based on the same inventive concept as the method embodiments, this application provides a communication device. The communication device used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. The content above can be used in subsequent embodiments, and repeated content will not be repeated.

[0227] Figure 5 This is a schematic block diagram of a communication device 500 provided in an embodiment of this application. The communication device 500 can be used to implement the functions of the terminal device or network device in the above embodiments. For example, when the communication device 500 corresponds to implementing the functions or steps implemented by the terminal device in the various method embodiments described above, the communication device 500 can be... Figure 1The communication device 500 can be a terminal device; or, the communication device 500 can be a chip (system) in the terminal device; or, the communication device 500 can be a logical node or software module of the terminal device. For example, when the communication device 500 can correspondingly implement the functions or steps implemented by the network device in the above method embodiments, the communication device 500 can be... Figure 1 The communication device 500 can be a network device; or, the communication device 500 can be a chip (system) within the network device; or, the communication device 500 can be a logical node or software module of the network device. The communication device 500 may include a processing module 510 and a transceiver module 520. Optionally, it may also include a storage module, which can be used to store instructions (code or program) and / or data. This storage module may be, for example, a memory. The processing module 510 and the transceiver module 520 may be coupled to the storage module. For example, the processing module 510 can read instructions (code or program) and / or data from the storage module to implement a corresponding method. When the communication device 500 is a chip in a terminal device or network device, the storage module may be a storage module within the chip, such as a register, cache, etc. For example, the storage module may also be a storage module located outside the chip within the terminal device or network device, such as read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, random access memory (RAM), etc. The above-mentioned units can be set up independently, or they can be partially or fully integrated.

[0228] Processing module 510 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. Transceiver module 520 is a transceiver, interface circuit, bus, pin, or other possible communication interface for receiving signals from other devices. For example, when the device is implemented as a chip, transceiver module 520 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

[0229] In one implementation, the communication device 500 can correspondingly implement the behavior and functions of the terminal device in the above method embodiments. The communication device 500 can be the terminal device, a component (e.g., a chip or circuit) applied in the terminal device, a part of a chip or chipset in the terminal device used to execute related method functions, or a software module capable of implementing the methods executed by the terminal device in the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0230] For example, processing module 510 is used to determine a first uplink grant, which indicates a first resource, wherein the first resource is used to transmit first data, which is data of a first LCH. Transceiver module 520 is used to receive first configuration information and second configuration information, wherein the first configuration information is used to configure a first priority of the first LCH, and the second configuration information is used to configure a second priority of the first LCH, wherein the second priority is higher than the first priority; or, the second configuration information is used to configure a first parameter of the first LCH. Processing module 510 is used to determine the priority of the first uplink grant based on the second priority or the first parameter if the first data is first type data. Transceiver module 520 is also used to send the first data according to the priority of a first uplink candidate.

[0231] As an optional implementation, the first data being first type data includes: the first data being first type data at a first moment, where the first moment is the time when the MAC PDU including the first data is sent.

[0232] As an optional implementation, the first LCH is configured with the first parameter, and the priority of the first LCH is the second priority.

[0233] As an optional implementation, the priority of the first uplink authorization is not determined based on the first priority.

[0234] As an optional implementation, if the first data is of the first type, the priority of the first LCH is the second priority.

[0235] As an optional implementation, the second configuration information is used to configure the first parameter of the first LCH, and the first uplink authorization is the preferred uplink authorization.

[0236] As an optional implementation, the second priority is the highest priority.

[0237] As an optional implementation, the processing module 510 is also used to determine a second uplink grant, which is used to indicate a second resource; wherein, if the second resource partially or completely overlaps with the first resource, the second uplink grant is a downgraded uplink grant.

[0238] As an optional implementation, the second uplink authorization does not include the first type of data.

[0239] As an optional implementation, the first data is of the first type when it satisfies at least one of the following: at the first moment, the first data has not been discarded; or at the first moment, the remaining transmission delay budget of the first data is less than or equal to the first threshold.

[0240] As an optional implementation, the transceiver module 520 is also used to receive third configuration information, which is used to configure the first threshold.

[0241] For example, processing module 510 is used to trigger SR at a second time, which is triggered by the first LCH; if the first LCH includes first type data at a third time, then the SR is determined to be the priority SR. Here, the third time is the time when the SR is sent or the time when the first data is sent, and the first data is the data in the first LCH.

[0242] As an optional implementation, the priority of SR is determined based on the priority of the first LCH at the third time step.

[0243] As an optional implementation, the priority of the first LCH includes the third priority and the fourth priority, with the fourth priority being higher than the third priority. The priority of the first LCH is the fourth priority.

[0244] As an optional implementation, the transceiver module 520 is also used to receive second configuration information, which is used to configure the first parameter of the first LCH.

[0245] As an optional implementation, when the resources of the SR and the fourth resources of the fourth uplink grant indication partially or completely overlap, the fourth resource is used to transmit uplink data, the SR is the preferred SR, and the fourth uplink grant is the down-priority uplink grant.

[0246] As an optional implementation, the first uplink authorization does not include the first type of data, or the fourth uplink authorization is not configured with the second configuration information.

[0247] As an optional implementation, SR has a higher priority than the fourth uplink grant.

[0248] As an optional implementation, the first data is of the first type at the third time when at least one of the following conditions is met: at the third time, the first data has not been discarded; or, at the third time, the remaining transmission delay budget of the first data is less than or equal to the first threshold.

[0249] As an optional implementation, the interval between the third time point and the second time point is greater than or equal to the first time point duration.

[0250] As an optional implementation, the transceiver module 520 is also used to receive fifth configuration information, which is used to configure the first duration.

[0251] When the communication device 500 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0252] Figure 6 This is a schematic block diagram of a communication device 600 provided in an embodiment of this application. The communication device 600 can be a terminal device as described in the above embodiments. For example, the communication device 600 can be... Figure 1 The terminal device or the chip (system) within the terminal device. In the embodiments of this application, the chip system may be composed of chips or may include chips and other discrete devices. For specific functions, please refer to the description in the above method embodiments.

[0253] The communication device 600 includes one or more processors 601, used to implement or support the communication device 600 in implementing the functions of the terminal device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples, which will not be repeated here. The processor 601 can also be called a processing unit or processing module, and can implement certain control functions. The processor 601 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 600 (e.g., a network device or a terminal device), execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0254] In one design, processor 601 may include program 603 (sometimes also referred to as code or instructions), which can be executed on processor 601 to cause communication device 600 to perform the methods described in the embodiments below. In yet another possible design, communication device 600 includes circuitry (…). Figure 6 (Not shown), the circuit is used to implement the functions of the terminal device in the above embodiments.

[0255] In one design, the communication device 600 may include one or more memories 602 storing a program 604 (sometimes referred to as code or instructions), which can be run on the processor 601 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0256] In one design, the processor 601 and / or memory 602 may include AI modules 607 and 608, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​modules may include RIC modules. For instance, the AI ​​modules may be near real-time RICs or non-real-time RICs.

[0257] In one possible design, the processor 601 and / or memory 602 may also store data. The processor and memory may be configured separately or integrated together.

[0258] In one possible design, the communication device 600 may further include a transceiver 605 and / or an antenna 606. The processor 601, sometimes referred to as a processing unit, controls the communication device 600. The transceiver 605, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device 600 through the antenna 606.

[0259] In one possible design, the communication device 600 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 600 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0260] The communication device in the above embodiments can be a terminal device, a circuit, a chip applied in a terminal device, or other combined devices or components having the aforementioned terminal device. Alternatively, the communication device in the above embodiments can be a network device, a circuit, a chip applied in a network device, or other combined devices or components having the aforementioned network device. When the communication device is a terminal device or a network device, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a chip system, the communication device can be an FPGA, a dedicated ASIC, a system-on-chip (SoC), a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0261] This application also provides a communication system, which includes at least one terminal device and at least one network device. The terminal device is a terminal device used to implement the relevant functions of the above-described communication method 300 and / or communication method 400. Alternatively, the terminal device is a terminal device used to implement the relevant functions of the above-described communication method 300 and / or communication method 400.

[0262] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to execute the method executed by the terminal device in the above-described communication method.

[0263] This application also provides a computer program product, including computer program code, which, when executed, causes the computer to perform the method executed by the terminal device in the above-described communication method.

[0264] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the terminal device in the aforementioned communication method. The chip system can be composed of chips or may include chips and other discrete components.

[0265] To achieve the above Figures 5-6 In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the terminal device or network device in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing the computer programs or instructions and data necessary for the communication device.

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

[0267] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

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

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

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

[0271] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0272] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method characterized by comprising: The method comprises: determining a first uplink grant, the first uplink grant being used for indicating a first resource, the first resource being used for transmitting first data, the first data being data of a first logical channel (LCH); receiving first configuration information, the first configuration information being used for configuring a first priority of the first LCH; receiving second configuration information, the second configuration information being used for configuring a second priority of the first LCH, the second priority being higher than the first priority, or the second configuration information being used for configuring a first parameter of the first LCH; if the first data is first type data, determining a priority of the first uplink grant according to the second priority or the first parameter; transmitting the first data according to the priority of the first uplink grant.

2. The method of claim 1, wherein, The first data is first type data, comprising: the first data is the first type data at a first time, the first time being a time of transmitting a medium access control (MAC) protocol data unit (PDU) including the first data.

3. The method of claim 1 or 2, wherein, The first LCH is configured with the first parameter, and a priority of the first LCH is the second priority.

4. The method according to any one of claims 1 to 3, characterized in that, The priority of the first uplink grant is not determined according to the first priority.

5. The method of any one of claims 1-4, wherein, If the first data is the first type data, the priority of the first LCH is the second priority.

6. The method of claim 1, wherein, The second configuration information is used for configuring the first parameter of the first LCH, and the first uplink grant is a priority uplink grant.

7. The method of claim 6, wherein, The second priority is a highest priority.

8. The method of claim 6, wherein, The method further comprises: determining a second uplink grant, the second uplink grant being used for indicating a second resource; wherein, if the second resource partially overlaps or fully overlaps with the first resource, the second uplink grant is a priority down uplink grant.

9. The method of claim 8, wherein, The second uplink grant does not include the first type data.

10. The method of any one of claims 2-9, wherein, The first data is the first type data at a first time when the first data satisfies at least one of the following conditions: at the first time, the first data has not been discarded; or at the first time, a remaining transmission delay budget of the first data is less than or equal to a first threshold.

11. The method of claim 10, wherein, The method further comprises: receiving third configuration information, the third configuration information being used for configuring a first threshold.

12. A communication method characterized by comprising: The method comprises: triggering a scheduling request (SR) at a second time, the SR being triggered by a first logical channel (LCH); if the first LCH includes first type data at a third time, determining that the SR is a priority SR, the third time being a time of transmitting the SR or a time of transmitting first data, the first data being data in the first LCH.

13. The method of claim 12, wherein, A priority of the SR is determined according to a priority of the first LCH at the third time.

14. The method of claim 12 or 13, wherein, The priority of the first LCH includes a third priority and a fourth priority, the fourth priority being higher than the third priority, and the priority of the first LCH being the fourth priority.

15. The method of claim 12 or 13, wherein, The method further comprises: receiving second configuration information, the second configuration information being used for configuring a first parameter of the first LCH.

16. The method of claim 15, wherein, The first LCH is configured with the first parameter, and a priority of the first LCH is a fourth priority.

17. The method of claim 15 or 16, wherein, When a resource of the SR and a fourth resource indicated by a fourth uplink grant partially or entirely overlap, the fourth resource is used for transmission of uplink data, the SR is a priority SR, and the first uplink grant is a priority-reduced uplink grant.

18. The method of claim 17, wherein, The fourth uplink grant does not include the first type of data, or the fourth uplink grant is not configured with the second configuration information.

19. The method of claim 18, wherein, The priority of the SR is higher than a priority of the fourth uplink grant.

20. The method of any one of claims 12-19, wherein, When the first data satisfies at least one of the following at the third time, the first data is the first type of data: The first data is not discarded at the third time; or A remaining transmission delay budget of the first data is less than or equal to a first threshold at the third time.

21. The method of claim 20, wherein, An interval between the third time and the second time is greater than or equal to a first time length.

22. The method of claim 21, wherein, The method further includes: Receiving fifth configuration information, the fifth configuration information being used for configuring the first time length.

23. A communications device, characterized by The method includes a module for performing the method of any one of claims 1-11, or a module for performing the method of any one of claims 12-22.

24. A communications device, characterized by The communication device includes at least one processor configured to cause the method of any one of claims 1-11 to be performed, or the method of any one of claims 12-22 to be performed.

25. A computer readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, when the computer program is run on a computer, causing the method of any one of claims 1-11 to be performed, or the method of any one of claims 12-22 to be performed.

26. A computer program product, characterised in that, The computer program product includes a computer program, when the computer program is run on a computer, causing the method of any one of claims 1-11 to be performed, or the method of any one of claims 12-22 to be performed.

Images