Communication method, terminal device, and communication system

Abstract

Embodiments of the present application relate to the technical field of communications, and provide a communication method, a terminal device, and a communication system. In the method, by appropriately relaxing logic channel (LCH) mapping for delay-critical data, more resources can be obtained during the transmission of the delay-critical data, thereby improving the probability of successfully sending the delay-critical data. The method may comprise: receiving first LCH mapping information, the first LCH mapping information being used for determining an uplink grant of a first LCH; and sending first data by means of a first uplink grant on the basis of the first LCH mapping information, wherein the first data is data in the first LCH, the first LCH mapping information comprises a first mapping restriction and / or a second mapping restriction, the first mapping restriction is used for restricting an available uplink grant of the first LCH, and the second mapping restriction is used for restricting an available uplink grant when the first LCH is a delay-critical LCH.

Description

A communication method, terminal device, and communication system

[0001] This application claims priority to Chinese Patent Application No. 202410932746.X, filed on July 11, 2024, entitled "A Communication Method, Terminal Equipment and Communication System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, terminal device and communication system. Background Technology

[0003] Terminal devices can map the uplink data to be transmitted to the uplink grant according to the configured logical channel (LCH) mapping, so as to send the uplink data through the uplink resources of the uplink grant.

[0004] Within the terminal device, during the process of the PDCP entity transmitting uplink data to the RLC entity, if the data takes a long time to process within the PDCP entity and the remaining time is less than the corresponding threshold, this data can be called latency-critical data.

[0005] The current logical channel mapping applies to all LCHs, which may prevent critical delay data from being mapped to the uplink grant for transmission in a timely manner. This could lead to transmission failures of critical delay data. Summary of the Invention

[0006] This application provides a communication method, terminal device, and communication system that, by reasonably relaxing the logical channel (LCH) mapping of delay-critical PDCP SDU, enables the acquisition of more resources when transmitting delay-critical data, thereby increasing the probability of successful transmission of delay-critical data.

[0007] To achieve the above technical objectives, this application adopts the following technical solution:

[0008] A first aspect provides a communication method applied to a terminal device. The method includes: receiving first logical channel (LCH) mapping information, the first LCH mapping information being used to determine uplink grant for the first LCH; and transmitting first data via the first uplink grant according to the first LCH mapping information. The first data is data within the first LCH. The first LCH mapping information includes a first mapping restriction, and the terminal device determines the first uplink grant based on the first mapping restriction and a preset rule. The preset rule is used to restrict whether at least one configuration item in the first mapping restriction is applied. Alternatively, the first LCH mapping information includes a first mapping restriction and a second mapping restriction, the first mapping restriction being used to determine the uplink grant for the first LCH, and the second mapping restriction being used to determine the uplink grant when the first LCH is a delay-critical LCH. Alternatively, the first LCH mapping information includes a third mapping restriction, the third restriction being used to determine the uplink grant when the first LCH is a delay-critical LCH.

[0009] Based on this scheme, the terminal device can determine whether to perform corresponding mapping relaxation when the first LCH is a latency-critical LCH, according to the first LCH mapping information and / or the second LCH mapping information. For example, when the first LCH is a latency-critical LCH, partial mapping restrictions of the first LCH may not be applied, or mapping may be performed using additional resources or resources different from those configured for the first LCH.

[0010] Optionally, the data in the delay-critical LCH includes delay-critical data, or the LCH group to which the delay-critical LCH belongs includes at least one LCH containing the delay-critical data. Wherein, the remaining time of the delay-critical data is less than a corresponding threshold value. This scheme provides a specific limitation on delay-critical LCHs. Based on this, the terminal device can accurately determine whether the first LCH is a delay-critical LCH.

[0011] Optionally, before sending the first data, the method further includes: mapping the first LCH to the first uplink grant.

[0012] Optionally, the first mapping restriction includes at least one of the following configuration items: subcarrier spacing (SCS) configuration, physical uplink shared channel (PUSCH) configuration, configuration related to allocation grants, serving cell related configuration, and dynamic allocation related configuration. Specifically, the SCS configuration indicates the subcarrier spacing for mapping the LCH to the uplink grant. The PUSCH configuration indicates the maximum PUCSH duration for mapping the LCH to the uplink grant. The configuration related to allocation grants indicates the grant type and / or available allocation grants for mapping the LCH to the uplink grant. The serving cell related configuration indicates the serving cell for mapping the LCH to the uplink grant. The dynamic allocation related configuration indicates the priority index of the dynamic allocation for mapping the LCH to the uplink grant.

[0013] In some embodiments of this application, the terminal device can negotiate and determine preset rules with the network in advance, for example, by specifying the preset rules through a mutually recognized protocol. In this way, after receiving the first LCH mapping information, the terminal device can determine whether to apply some or all of the configuration items in the first LCH based on whether the first LCH is a delay-critical LCH, according to the preset rules.

[0014] Optionally, this preset rule corresponds to the first configuration item in the first mapping restriction. This preset rule is used to restrict whether the first configuration item is applied.

[0015] Optionally, the preset rule includes: if the first LCH is a delay-critical LCH, the first configuration item is not applied; and / or, if the first LCH is not a delay-critical LCH, the first configuration item is applied.

[0016] Optionally, the first configuration item includes the relevant configuration of the serving cell. The preset rule includes: if the first LCH is a delay-critical LCH and PDCP replication is not configured, the first configuration item is not applied, and the first LCH can be mapped to the uplink grant of any serving cell. And / or, if PDCP replication is configured, and the first LCH is a delay-critical LCH or a non-delay-critical LCH, the first configuration item is applied, and the first LCH can be mapped to the uplink grant of the serving cell indicated by the relevant configuration of the serving cell.

[0017] Optionally, the first configuration item includes the configuration related to the dynamic authorization. The preset rule includes: if the first LCH is a delayed critical LCH and the priority index indicated by the dynamic authorization configuration is a second value, the first configuration item is not applied, and the first LCH can be mapped to any dynamic authorization. And / or, if the priority index indicated by the dynamic authorization configuration is a first value, and the first LCH is a delayed critical LCH or a non-delayed critical LCH, the first LCH can be mapped to the dynamic authorization corresponding to the priority indicated by the dynamic authorization configuration. Wherein, the priority when the priority index is a second value is lower than the priority when the priority index is a first value.

[0018] Optionally, the preset rule includes: if the first LCH is a delayed critical LCH, the available uplink grants for the first LCH include uplink grants of type 1. And / or, if the first LCH is not a delayed critical LCH, the available uplink grants for the first LCH do not include uplink grants of type 1.

[0019] In some embodiments of this application, the terminal device can obtain a first LCH mapping restriction and a second LCH mapping restriction under network configuration. The first LCH mapping restriction may include a configuration item for a Legacy mapping restriction, and the second LCH mapping restriction may include a configuration item for an Enhanced mapping restriction.

[0020] In this way, the terminal device can perform mapping when the first LCH is not a delay-critical LCH based on the first LCH mapping. The terminal device can also perform mapping when the first LCH is a delay-critical LCH based on the second mapping constraint and the first LCH mapping constraint.

[0021] The following examples provide several specific examples of different delayed critical LCH mappings that combine the second mapping constraint with the first mapping constraint.

[0022] Optionally, the first LCH mapping information includes a first mapping restriction and a second mapping restriction. The second mapping restriction includes at least one of the following: deactivation restriction configuration, additional resource configuration, negation configuration, and delay key activation configuration. The deactivation restriction configuration indicates whether the configuration items in the first mapping restriction are applied when the first LCH is a delay key LCH. The additional resource configuration indicates additional configuration items that can be used when the first mapping restriction is applied, given that the first LCH is a delay key LCH. The negation configuration indicates configuration items that are not applied when the first LCH is a delay key LCH. The delay key activation configuration indicates the configuration items that are available when the first LCH is a delay key LCH.

[0023] Optionally, the second mapping restriction includes at least one of the following configuration items: SCS-related configuration, used to indicate whether to apply / not apply the SCS configuration in the first mapping restriction, or to restrict the application of SCS configuration when the first LCH is a delay-critical LCH, or to configure additional SCS configuration when the first LCH is a delay-critical LCH, or to configure the SCS configuration when the first LCH is a delay-critical LCH. PUSCH-related configuration, used to indicate whether to apply / not apply the PUSCH configuration in the first mapping restriction, or to configure additional PUSCH configuration when the first LCH is a delay-critical LCH, or to configure the PUSCH configuration when the first LCH is a delay-critical LCH. Serving cell-related configuration, used to indicate whether to apply / not apply the serving cell-related configuration in the first mapping restriction, or to configure additional serving cell-related configuration when the first LCH is a delay-critical LCH, or to configure the serving cell-related configuration when the first LCH is a delay-critical LCH. The configuration for available configuration authorization is used to indicate the available configuration authorization indicated in the relevant configuration for applying / not applying the configuration authorization in the first mapping restriction, or to configure additional available configuration authorization when the first LCH is a delay-critical LCH, or to configure the available configuration authorization when the first LCH is a delay-critical LCH. The configuration for the type of available configuration authorization is used to indicate the type of available configuration authorization indicated in the relevant configuration for applying / not applying the configuration authorization in the first mapping restriction, or to configure the type of available configuration authorization when the first LCH is a delay-critical LCH. The configuration for dynamic authorization is used to indicate the configuration for applying / not applying dynamic authorization in the first mapping restriction, or to configure the configuration for dynamic authorization when the first LCH is a delay-critical LCH.

[0024] Optionally, the second mapping restriction includes a second configuration item, which corresponds to the first configuration item in the first mapping restriction. When the second configuration item is a first value, it is not applied if the first LCH is a delay-critical LCH. When the second configuration item is a second value, it is applied if the first LCH is a delay-critical LCH. Alternatively, it is not applied if the first LCH is a delay-critical LCH. Alternatively, it is applied if the first LCH is not a delay-critical LCH.

[0025] In this example, the second mapping restriction can include configuration items corresponding to the first mapping restriction. Therefore, by using configuration items with fields such as Disable, Additional, and not, the mapping of configuration items already configured in the first mapping restriction can be relaxed.

[0026] Optionally, the first configuration item includes the SCS configuration. If the first configuration item is not applied, it includes the following: the first LCH can be mapped to any SCS-related uplink grant.

[0027] Optionally, the first configuration item includes the PUSCH configuration. If the first configuration item is not applied, it includes the following: the first LCH can be mapped to an uplink grant of any PUSCH duration.

[0028] Optionally, the first configuration item includes configuration related to the configuration authorization, which indicates the available configuration authorization. If the first configuration item is not applied, it includes the following: the first LCH can be mapped to any uplink authorization.

[0029] Optionally, the first configuration item includes the relevant configuration for the serving cell. If the first configuration item is not applied, it includes the following: the first LCH can be mapped to the uplink grant of any serving cell.

[0030] Optionally, the second mapping restriction includes the relevant configuration of the serving cell, indicating that the relevant configuration of the serving cell in the first mapping restriction is not applied; the first LCH can be mapped to the uplink grant of any serving cell, including: when PDCP replication is not configured, the first LCH can be mapped to the uplink grant of any serving cell.

[0031] Optionally, the first configuration item includes the relevant configuration of the serving cell, and the second mapping restriction includes the relevant configuration of the serving cell in the first mapping restriction not to be applied. When PDCP replication is configured, the first LCH can be mapped to the uplink grant corresponding to the serving cell indicated by the first configuration item.

[0032] Optionally, the first configuration item includes the configuration related to the dynamic license. If the first configuration item is not applied, it includes: the first LCH can be mapped to any dynamic license.

[0033] Optionally, the second mapping restriction includes dynamic licensing configuration to indicate that the dynamic licensing configuration in the first mapping restriction is not applied. The first LCH can be mapped to the uplink license of any serving cell, including: when the priority index indicated by the dynamic licensing configuration in the first mapping restriction is a second value, the first LCH can be mapped to the uplink license of any serving cell. The priority when the priority index is the second value is lower than the priority when the priority index is the first value.

[0034] Optionally, the first configuration item includes the dynamic authorization-related configuration, used to indicate that the dynamic authorization-related configuration in the first mapping restriction is not applied. In the first mapping restriction, if the priority index indicated by the dynamic authorization-related configuration is a first value, the first LCH can be mapped to the uplink authorization with the priority index of the first value.

[0035] Optionally, the first configuration item includes configuration related to the configuration authorization, and the available uplink authorization for the first LCH does not include uplink authorization of type 1. The second mapping restriction includes configuration of the type of available configuration authorization, used to indicate that when the first LCH is a delayed critical LCH, uplink authorization of type 1 can be used. The first LCH can be mapped to uplink authorization of type 1.

[0036] Optionally, the first configuration item includes SCS configuration, and the second mapping restriction includes additional SCS configuration for configuring when the first LCH is a delay-critical LCH. The first LCH can be mapped to an uplink grant associated with the first SCS. The first SCS configuration is included in the set of SCS configurations indicated by the first and second configuration items.

[0037] Optionally, the first configuration item includes the relevant configuration of the serving cell, and the second mapping restriction includes the relevant configuration for configuring additional serving cells when the first LCH is a delay-critical LCH. The first LCH can be mapped to the uplink grant corresponding to the first serving cell. The first serving cell is included in the configuration set of serving cells indicated by the first configuration item and the second configuration item.

[0038] Optionally, the PUSCH configuration included in the first configuration item indicates a first duration, and the second mapping restriction includes an additional PUSCH configuration for configuring an additional PUSCH when the first LCH is a delay-critical LCH. This additional PUSCH configuration indicates a second duration, and the first duration is less than the second duration. The first LCH can be mapped to the uplink grant corresponding to the first PUSCH configuration. The duration of the first PUSCH configuration is less than the second duration.

[0039] Optionally, the second mapping restriction includes the availability of Type 1 authorization types when the first LCH is a delayed critical LCH. The first LCH can be mapped to an uplink authorization of type Type 1.

[0040] Optionally, the second mapping restriction includes a second SCS configuration for restricting the first LCH from being applied when it is a latency-critical LCH. Mapping the first LCH to the first uplink grant includes mapping the first LCH to an uplink grant associated with a third SCS configuration, which is different from the second SCS configuration.

[0041] Optionally, this first configuration item includes a first SCS configuration. This first SCS configuration is not applied.

[0042] In other embodiments of this application, the network can configure a third mapping restriction for the terminal device. This third mapping restriction may correspond to the Enhance-related configuration directly applied when the first LCH is a latency-critical LCH.

[0043] Optionally, the first LCH mapping information includes a third mapping restriction, which is used to determine uplink grants when the first LCH is a delay-critical LCH. The third mapping restriction includes at least one of the following configuration items: Delay-critical SCS configuration, used to indicate the SCS configuration of uplink grants that can be mapped when the first LCH is a delay-critical LCH; Delay-critical PUSCH configuration, used to indicate the PUSCH configuration of uplink grants that can be mapped when the first LCH is a delay-critical LCH; Delay-critical grant type configuration, used to indicate the grant type of uplink grants that can be mapped when the first LCH is a delay-critical LCH; Delay-critical available configuration grant, used to indicate the configuration grants that can be mapped when the first LCH is a delay-critical LCH; Delay-critical serving cell configuration, used to indicate the serving cell corresponding to the uplink grants that can be mapped when the first LCH is a delay-critical LCH; and Delay-critical dynamic grant configuration, used to indicate the priority of dynamic grants that can be mapped when the first LCH is a delay-critical LCH.

[0044] Secondly, a communication method is provided, applied to a terminal device, the method comprising: sending first data via a first uplink grant. The first data is data in a first LCH (Local Link Chance). The first uplink grant is determined according to a preset rule. The preset rule includes: when the first LCH is a delay-critical LCH, the first LCH can be mapped to an uplink grant of type 1.

[0045] This example demonstrates how a mapping restriction can be applied to a latency-critical LCH regardless of whether the first LCH mapping is configured with a certain restriction. This default rule can be negotiated in advance between the end device and the network device. For example, the default rule could be related to the mapping types available for the latency-critical LCH. In other implementations, the default rule can also be used to indicate other restrictions that are in effect by default for the latency-critical LCH.

[0046] Thirdly, a terminal device is provided for performing the methods provided in the first aspect and any possible design thereof, or for performing the methods provided in the second aspect.

[0047] Fourthly, a communication system is provided, comprising a terminal device as provided in the third aspect, and a network device. The network device is further configured to receive first data via a first uplink grant. The first data is data in a first LCH. The first uplink grant is determined based on first LCH mapping information, or the first uplink grant is determined based on preset rules. The first LCH mapping information includes a first mapping restriction, which is used by the terminal device to determine the first uplink grant based on the first mapping restriction and the preset rules. The preset rules are used to restrict whether at least one configuration item in the first mapping restriction is applied. Alternatively, the first LCH mapping information includes a first mapping restriction and a second mapping restriction, the first mapping restriction being used to determine the uplink grant of the first LCH, and the second mapping restriction being used to determine the uplink grant when the first LCH is a delay-critical LCH. Alternatively, the first LCH mapping information includes a third mapping restriction, which is used to determine the uplink grant when the first LCH is a delay-critical LCH.

[0048] Optionally, the network device is further configured to send first LCH mapping information to the terminal device, the first LCH mapping information being used to determine the uplink authorization of the first LCH.

[0049] Optionally, the network equipment in the communication system may include a base station.

[0050] Fifthly, this application also provides a chip system applied to a terminal device; the chip system may include one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines, and the interface circuits are used to receive signals from the terminal device's memory and send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the aforementioned computer instructions, the terminal device executes the technical solutions provided in the first aspect and any possible implementation thereof, or executes the solutions provided in the second aspect.

[0051] Sixthly, this application also provides a chip system applied to a network device; the chip system may include one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines, and the interface circuits are used to receive signals from the network device's memory and send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the aforementioned computer instructions, the network device performs the functions corresponding to the network device in the communication system provided in the fourth aspect.

[0052] In a seventh aspect, this application also provides a computer-readable storage medium including computer instructions that, when executed on a terminal device, cause the terminal device to perform the technical solutions provided in the first aspect and any possible implementation thereof, or to perform the solutions provided in the second aspect.

[0053] Eighthly, this application also provides a computer program product that, when run on a computer, causes the computer to execute the technical solutions provided in the first aspect and any possible implementation thereof, or to execute the solutions provided in the second aspect. Optionally, the computer may be a terminal device.

[0054] It is understood that the solutions provided in the second to eighth aspects of this application can be respectively associated with the first aspect and any of its possible designs, and therefore the beneficial effects achieved are similar, which will not be elaborated here. Attached Figure Description

[0055] Figure 1 is a schematic diagram of the composition of a terminal device;

[0056] Figure 2 is a logical diagram of data transmission within a terminal device;

[0057] Figure 3 is a logical diagram of a communication process;

[0058] Figure 4 is a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0059] Figure 5 is a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0060] Figure 6 is a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0061] Figure 7 is a schematic diagram of the composition of a terminal device provided in an embodiment of this application;

[0062] Figure 8 is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0063] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0064] The wireless interface of a terminal device (such as user equipment (UE)) can be configured with three protocol layers, thereby enabling communication between the UE and the network (such as a base station (BS)). These three protocol layers may include: the physical layer (i.e., Layer 1, L1), the data link layer (i.e., Layer 2, L2), and the network layer (i.e., Layer 3, L3).

[0065] For example, referring to Figure 1, a schematic diagram of the logical composition of a UE is provided. Figure 1 shows three protocol layers and the specific configuration of each protocol layer.

[0066] As shown in Figure 1, L3, L2 and L1 can be configured from top to bottom in the UE.

[0067] L3 can include the Radio Resource Control (RRC) layer. The RRC layer is a higher layer of the control plane, mainly responsible for controlling L1 / L2 to complete air interface resource transmission and providing information transmission services for the Non-Access Stratum (NAS) layer.

[0068] L1 may include the Physical Layer (PHY). The PHY may be configured with wireless physical channels that provide transmission for higher-layer services. In this application, the time-domain and / or frequency-domain characteristics of the wireless physical channels configured in the PHY can be referred to as the resources configured in the PHY.

[0069] L2 may include the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer.

[0070] In some implementations, a Service Data Adaptation Protocol (SDAP) layer may also be included between the RRC layer and the PDCP layer.

[0071] A PDCP layer may include one or more PDCP entities. As shown in Figure 2, taking a PDCP layer containing four PDCP entities as an example, such as PDCP1, PDCP2, PDCP3, and PDCP4.

[0072] During UE-network communication, data packets can be transmitted down to different PDCP entities. Taking PDCP1 as an example, data packets input to PDCP1 may include PDCP SDU 1. Data output from PDCP1 may include PDCP PDU 1.

[0073] Similarly, an RLC layer can include one or more RLC entities. For example, an RLC layer can include four RLC entities: RLC1, RLC2, RLC3, and RLC4.

[0074] Taking data transmission between PDCP1 and RLC1 as an example, PDCP1 can transmit PDCP PDU 1 to RLC1. Data transmission between other PDCP entities and RLC entities is similar.

[0075] It should be noted that after data enters the PDCP layer, if the remaining time is less than the corresponding threshold, this data can be called Delay-critical Data. In the PDCP layer, this Delay-critical Data can correspond to the Delay-critical PDCP SDU received by the PDCP layer entity.

[0076] For example, PDCP1 can start timing after receiving PDCP SDU 1. If the remaining time of the data is less than the corresponding threshold value, PDCP1 can determine that PDCP SDU 1 as a Delay-critical PDCP SDU.

[0077] When PDU-setDiscard is configured, the delay critical packet belongs to a PDU set and at least one packet in that PDU set has a remaining time less than a threshold value.

[0078] When the PDCP layer submits delay-critical data to the RLC layer, the PDCP layer can notify the RLC layer that the data packet is delay-critical. Correspondingly, the RLC layer can determine that the received data is delay-critical.

[0079] For example, consider PDCP SDU 1 as latency-critical data, which has already been submitted to RLC1. PDCP1 can notify the RLC1 layer that the data corresponding to PDCP SDU 1 is latency-critical data. In this way, RLC1 can determine that the data received from PDCP1 is latency-critical data.

[0080] After receiving data at the RLC layer, the data can be transmitted to available resources in the PHY through the MAC layer.

[0081] The RLC layer can transmit data to the MAC layer through the Logic Channel (LCH).

[0082] For example, in the example shown in Figure 2, RLC1 and the MAC layer may include LCH1. RLC2 and the MAC layer may include LCH2. RLC3 and the MAC layer may include LCH3. RLC4 and the MAC layer may include LCH4.

[0083] In some embodiments, where the data transmitted in the LCH includes delay-critical data, and further, the delay-critical data has not yet been transmitted, the LCH may be referred to as a delay-critical LCH.

[0084] In other embodiments, one or more LCHs can form an LCH group (LCG). A delay-critical LCH may correspond to an LCG to which the LCH belongs containing at least one LCH with delay-critical data that has not yet been transmitted.

[0085] The MAC layer can include mapping constraints for each logical channel configured by RRC, used to control the LCP process. The set of mapping constraints for each logical channel in this MAC layer can be called the LCH mapping constraints.

[0086] For example, consider a PHY resource comprising resource block 1 and resource block 2. It is understood that PHY resources can be used for uplink resource transmission between the UE and the base station. These PHY resources may include uplink resources and also correspond to uplink grants (UL grants).

[0087] The configured rules in the MAC layer can include LCH mapping restrictions. These LCH mapping restrictions can provide one or more filtering conditions, allowing the MAC layer to place data transmitted on different LCHs into the corresponding resources in the PHY based on these conditions. For example, the MAC layer can, based on the LCH mapping restrictions, place data from LCH1 and LCH3 into resource block 1, and data from LCH2 and LCH4 into resource block 2.

[0088] In some implementations, the LCH mapping restriction can be configured by the network device (such as a base station) to the UE and stored in the UE's MAC layer.

[0089] For example, referring to Figure 3, the base station can send LCH mapping information A to the terminal device. The LCH mapping information A may include LCH mapping restrictions.

[0090] Correspondingly, the MAC layer of the terminal device can, based on the received LCH mapping restriction A, put the data transmitted in the LCH into the PHY resources and send it to the base station.

[0091] In some embodiments, LCH mapping restriction A may include at least one of the following:

[0092] Subcarrier space (SCS) configuration; Physical uplink shared channel (PUSCH) configuration; Configuration grant related configuration; Serving cell related configuration; Dynamic grant related configuration; Hybrid Automatic Repeat reQuest (HARQ) mode related configuration.

[0093] The LCH mapping information A can include corresponding fields to implement the configuration of the LCH mapping restrictions mentioned above.

[0094] For example, LCH mapping restrictions include fields related to SCS configuration, PUSCH configuration, configuration authorization, serving cell, and dynamic authorization.

[0095] The following is an example of a field related to LCH mapping restrictions in LCH mapping information A.

[0096] LCH mapping information A:

[0097] Legacy mapping restriction:

[0098] {

[0099] allowedServingCells

[0100] allowedSCS-List

[0101] maxPUSCH-Duration

[0102] allowedPHY-PriorityIndex

[0103] configuredGrantType1Allowed

[0104] allowedCG-List

[0105] }

[0106] In this example of LCH mapping information A, the SCS configuration includes the allowedSCS-List field, the PUSCH configuration includes the maxPUSCH-Duration field, the configuration related to authorization includes the configuredGrantType1Allowed field and / or the allowedCG-List field, the configuration related to serving cells includes the allowedServingCells field, and the configuration related to dynamic authorization includes the configuredGrantType1Allowed field.

[0107] The allowedServingCells field is used to configure the allowed cells(s) for transmission.

[0108] The allowedSCS-List field is used to set the allowed subcarrier spacing(s) for transmission. In some implementations, the allowedSCS-List field may include a list of SCSs that restrict the LCH from selecting uplink grants. The LCH can only map to an uplink grant if the allowedSCS-List configured for the LCH includes an uplink grant SCS.

[0109] In some embodiments, the allowedServingCells field may include information about one or more serving cells.

[0110] The `maxPUSCH-Duration` field sets the maximum PUSCH duration allowed for transmission. In some implementations, the `allowedSCS-List` field may include the PUSCH duration that limits the uplink grant available for the LCH. When the uplink grant PUSCH duration is less than `maxPUSCH-Duration`, the LCH can be mapped to that uplink grant.

[0111] The `allowedPHY-PriorityIndex` field is used to restrict the dynamic grants that the LCH can use (the `allowedPHY-PriorityIndex` sets the allowed PHY priority index(es) of a dynamic grant for transmission). In some embodiments, `allowedPHY-PriorityIndex` can be configured with a first value or a second value. For example, if the first value is 1 and the second value is 0: When `allowedPHY-PriorityIndex` is configured to 1, the dynamic grants that the LCH can use have a high priority; that is, the LCH can only be mapped to dynamic grants indicated as 1. When `allowedPHY-PriorityIndex` is configured to 0, the dynamic grants that the LCH can use have a low priority; that is, the LCH can only be mapped to dynamic grants indicated as 0.

[0112] The allowedCG-List field can include information about one or more configuration grants. This field is used to restrict the configuration grants that LCH data can use (allowedCG-List, which sets the allowed configured grant(s) for transmission).

[0113] Furthermore, in this example of LCH mapping information A, the base station can send configuration authorization-related configurations to the UE via configuredGrantType1Allowed.

[0114] In this application, the configuration grant granted by the base station to the UE may include at least two types: configuration grant type 1 (hereinafter referred to as Type 1) and configuration grant type 2 (hereinafter referred to as Type 2).

[0115] Taking the base station configuring Type 1 for the UE as an example, when the UE uses PUSCH for data transmission, the uplink grant is provided by the Resource Management Layer (RRC). The UE stores this configuration and uses it as the grant configuration (configured grant Type 1 where an uplink grant is provided by RRC, and stored as configured uplink grant). Thus, after receiving the Type 1 configuration grant sent by the RRC, the configuration grant takes effect, and the UE can use this configuration grant for data transmission.

[0116] Taking a base station configuring Type 2 for the UE as an example, when the UE uses PUSCH for data transmission, the uplink grant is provided by the Physical Downlink Control Channel (PDCCH), and the configuration is stored or cleared based on L1 signaling indicating the activation or deactivation of the configured uplink grant. Thus, after obtaining a Type 2 configuration grant, the UE can use it for data transmission upon receiving an activation indication from the PDCCH. Conversely, upon receiving a deactivation indication from the PDCCH, the configuration grant becomes invalid, and the UE will no longer use it for data transmission.

[0117] In the example of LCH mapping information A, the base station instructs the LCH to use a Type 1 configuration grant for uplink data transmission by configuring the `configuredGrantType1Allowed` field to the UE. Correspondingly, upon receiving this field, the LCH can store it as an uplink configuration grant and perform uplink data transmission based on that grant.

[0118] It is understandable that the various LCH mapping restrictions corresponding to the LCH mapping information A can restrict the mapping of data transmitted in the LCH to data blocks in the PHY from different perspectives, thereby achieving control over data transmission in the LCH.

[0119] Based on the above explanation regarding delay-critical LCHs and delay-critical data, taking an example where the UE is configured with LCH mapping restrictions corresponding to LCH mapping information A, the MAC layer does not distinguish between delay-critical data and non-delay-critical data when placing data from each LCH into the PHY data block. This prevents delay-critical data from quickly accessing transmission resources in the PHY. For delay-critical LCHs containing delay-critical data, since the data in the LCH is discarded within a short period, this mapping restriction on delay-critical LCHs may lead to data loss.

[0120] Based on this, the technical solution provided in this application embodiment enables data of the delayed critical LCH to obtain more transmission resources and avoid data loss.

[0121] In the solution provided in this application embodiment, a network device (such as a base station) can configure LCH mapping restriction information for any one or more LCHs used by the UE. For example, the LCH mapping restriction information may include at least one of the following:

[0122] Legacy mapping restriction; Enhanced mapping restriction. In some implementations, the configuration of the legacy mapping restriction can be set with reference to the LCH mapping information A above.

[0123] In the information related to LCH mapping restrictions, the mapping enhancement restrictions are configured to take effect for latency-critical LCHs.

[0124] In some embodiments, enhancing mapping restrictions may include a deactivation restriction configuration. This deactivation restriction configuration may include a "disable" flag. This deactivation restriction configuration is used to relax mapping for latency-critical LCHs based on legacy mapping restrictions. This allows latency-critical LCHs to obtain more resources when relevant conditions are met.

[0125] In some embodiments of this application, deactivation can be replaced by not applying or canceling. Correspondingly, activation can be replaced by applying or not canceling.

[0126] In other embodiments, enhanced mapping constraints may include additional resource configuration. This additional resource configuration may include an "additional" flag. This additional configuration is used to expand the available resources for delayed critical LCHs based on legacy mapping constraints. This allows delayed critical LCHs to have a greater probability of acquiring resources when relevant conditions are met.

[0127] In other embodiments, enhanced mapping restrictions may include a negative configuration. This negative configuration may include a "not" flag. This negative configuration is used to further restrict mapping based on current communication conditions, building upon legacy mapping restrictions.

[0128] In other embodiments, enhanced mapping constraints may include a delay key activation configuration. This delay key activation configuration may be independent of the legacy mapping constraint configuration. For example, the configuration items for the delay key activation configuration may include one or more of the legacy mapping constraint configuration items, or the delay key activation configuration items may include configuration items not included in the legacy mapping constraints. The delay key activation configuration may take effect when the LCH is a delay key LCH. When the delay key activation configuration is in effect, legacy mapping constraints may not be in effect.

[0129] In other embodiments, enhanced mapping restrictions may include any two or more of deactivation restriction configurations, additional resource configurations, and negation configurations. This allows the UE to comprehensively determine the rules to be followed during the delay-critical LCH mapping process based on the configuration of the enhanced mapping restrictions.

[0130] In the embodiments of this application, the mechanism for the activation of the enhanced mapping restriction may be pre-configured in the UE and / or network device; or configured by the network device for the UE; or negotiated in advance between the UE and the network device.

[0131] It should be noted that, in conjunction with the example of LCH mapping information A above, this enhanced mapping restriction may specifically include at least one of the following:

[0132] Subcarrier space (SCS) configuration, such as SCSlist configuration;

[0133] Physical uplink shared channel (PUSCH) configuration, such as the configuration of maxPUSCH-Duration;

[0134] Configure related settings for granted permissions, such as the configuration of configuredGrantType1Allowed, and the configuration of allowedCG-List;

[0135] Configuration related to Serving Cells, such as the configuration of allowedServingCells;

[0136] Configuration related to Dynamic Grant, such as the configuration of allowedPHY-PriorityIndex;

[0137] Configuration related to Hybrid Automatic Repeat reQuest (HARQ) mode.

[0138] When any one of the configuration items is active, the UE can determine the uplink authorization of the LCH based on that configuration item. Conversely, when the configuration item is inactive, the UE does not determine the uplink authorization of the LCH based on that configuration item. In some embodiments, the activation of a configuration item can also be referred to as the application of the configuration item. The inactivation of a configuration item can also be referred to as the non-application of the configuration item.

[0139] It's understandable that this SCS configuration (such as the SCSlist configuration) is intended to prevent some LCHs from using unconfigured SCSs. This parameter was introduced to ensure that latency-sensitive services transmit with shorter transmission time intervals (TTIs). Using longer TTIs might cause the transmission to fail to meet latency requirements. If the LCH contains latency-critical data, relaxing this restriction may not guarantee successful UE transmission and will not meet latency requirements. Therefore, regarding the allowedSCS-List mapping restriction, when the LCH contains latency-critical data, this restriction should not be removed. Alternatively, the network should configure whether the restriction can be removed for that LCH based on the current channel environment and the LCH's QoS. Removing the restriction can be considered as relaxing it.

[0140] This PUSCH configuration (such as the maxPUSCH-Duration configuration) is specifically configured for latency-sensitive services and can meet their latency requirements. Because if a license is configured, the LCH will not meet latency requirements when using a long TTI license for transmission, especially when the remaining time for LCH packets is low. Therefore, for maxPUSCH-Duration, this restriction should not be removed when the LCH contains latency-critical data. Alternatively, the network should configure whether the restriction can be removed based on the current channel environment and the LCH's QoS. Removing the restriction would be equivalent to relaxing it.

[0141] In the configured Grant (CG) configuration, taking the configuredGrantType1Allowed configuration as an example, this configuration field allows the LCH to use a Type 1 configuration grant. If this restriction is removed, a Type 1 configuration grant cannot be used. This restriction is primarily for reliability assurance. Although a Type 1 configuration grant is shared by multiple UEs, if the LCH has latency-sensitive services, delay-critical data may lead to packet loss if not transmitted quickly. Therefore, this restriction is added when the LCH does not have this setting configured, meaning that the LCH can use a Type 1 configuration grant when latency-sensitive data is present. In other words, if the network does not configure this parameter, Type 1 CG will be used by default when latency-sensitive services are present.

[0142] In the configuration of the Configured Grant (CG), taking the allowedCG-List configuration as an example, this field applies to configuration grant scenarios. If configured, the LCH can only use the configuration grant corresponding to this field (if there is no list, no configuration can be used for grant collection). If not configured, the LCH can use all configuration grants corresponding to this field. If configuredGrantType1Allowed is configured, the LCH can only use type 1 configuration grants in this field; if configuredGrantType1Allowed is not configured, this field should not include type 1 configuration grants. According to the meeting discussion, this CG-list was set up to allow TSN services to meet the needs of a single service flow through multiple CGs, avoiding the mismatch between TSN service cycles and CG cycles. Also, when two service cycles are multiples of each other, they can be transmitted through a single CG. Generally, this configuration can perfectly match the service cycle and service size. However, there are situations where a sudden increase in service volume can cause LCH data to fail to transmit, leading to an impending timeout. Therefore, when there is a delay in critical data transmission in the LCH, this field can be removed, and there is no need to restrict the list of CGs that the LCH can use. When configuredGrantType1Allowed is configured, the CG-list that LCH can use will not be restricted if there is delayed critical data in LCH; when configuredGrantType1Allowed is not configured, the CG-list that LCH can use will not be restricted if there is delayed critical data in LCH.

[0143] In the configuration of Serving Cells (SC for short), let's take the configuration of allowedServingCells as an example. This parameter is related to PDCP replication and is used to restrict the transmission of duplicate content in different cells (transmission on different carriers). At the same time, allowedServingCells is also used to restrict the serving cells that logical channels can be used in.

[0144] When PDCP replication is configured, the UE's PDCP entity can send the same PDCP PDU to two RLC entities. These two RLC entities can then transmit the received identical PDCP PDU through two different LCHs.

[0145] This field is mandatory when PDCP replication is configured; it is optional when PDCP replication is not configured. Therefore, if PDCP replication is configured and the LCH contains delayed critical data, this field cannot be removed; if PDCP replication is not configured and the LCH contains delayed critical data, this field can be removed.

[0146] In the configuration of Dynamic Grant (DG or dynamic grant for short), taking the allowedPHY-PriorityIndex configuration as an example: If this field exists and the dynamic grant has a corresponding PHY priority index, then UL MAC SDUs from this logical channel can only be mapped to the dynamic grant indicating that the PHY priority index is equal to the value configured in this field. If this field exists and the dynamic grant does not have a PHY priority index (i.e., corresponding to priority index 0), then if the value of this field is p0, then UL MAC SDUs from this logical channel can only be mapped to this dynamic grant. If this field does not exist, then UL MAC SDUs from this logical channel can be mapped to any dynamic grant.

[0147] The introduction of this field is to ensure priority scheduling. This field can be configured with different values, such as 1 or 0. When the resource has a high priority (1), it is transmitted first. When a low-priority resource conflicts with a high-priority resource, the low-priority resource is discarded. At the same time, this method can ensure the reliability of data within the LCH so that it can be transmitted on resources with lower MCS. Therefore, when there is delay-sensitive data in the LCH and the PHY priority is configured to 1, this configuration should not be canceled to prevent the LCH data from being transmitted to a low-priority license and thus discarded. When there is delay-sensitive data in the LCH and the PHY priority is configured to 0, this configuration can be canceled so that the LCH data can be transmitted to any license. Alternatively, this restriction should not be canceled and should be configured by the network device to cancel it when there is delay-sensitive data in the LCH.

[0148] Based on the above explanation, the following provides several specific configuration methods, illustrating the specific implementation of network devices configuring LCH mapping restrictions to UEs.

[0149] For example, referring to Figure 4, a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application is shown. In this example, the relevant information of LCH mapping restrictions may include LCH mapping information B. Specifically, LCH mapping information B includes legacy mapping restrictions and enhanced mapping restrictions, with enhanced mapping restrictions including deactivation restriction configuration, as an example.

[0150] As shown in Figure 4, the scheme may include:

[0151] S401. The network device sends LCH mapping information B to the UE. The network device may include a base station.

[0152] In some embodiments, the network device may send an RRC message to the UE, which may carry the LCH mapping information B.

[0153] The network device can configure corresponding LCH mapping information for any one or more LCHs used by the UE. For example, the network device can configure corresponding LCH mapping information for each LCH used by the UE. When the UE uses multiple LCHs, the LCH mapping information for different LCHs can be the same or different. In this way, the UE can determine the uplink authorization mapping for the current LCH based on the LCH mapping information (such as LCH mapping information B).

[0154] As an example, a specific example of LCH mapping information B is provided below. It is understood that this example is merely illustrative, and in other embodiments, the content or fields in LCH mapping information B may be more or fewer.

[0155] LCH mapping information B:

[0156] Legacy mapping restriction:

[0157] {

[0158] allowedServingCells

[0159] allowedSCS-List

[0160] maxPUSCH-Duration

[0161] allowedPHY-PriorityIndex

[0162] configuredGrantType1Allowed

[0163] allowedCG-List

[0164] }

[0165] Enhanced mapping restriction:

[0166] {

[0167] allowedServingCells-disabled

[0168] allowedSCS-List-disabled

[0169] maxPUSCH-Duration-disabled

[0170] configuredGrantType1Allowed-delayLCH

[0171] allowedPHY-PriorityIndex-disabled

[0172] allowedCG-List-disabled

[0173] }

[0174] In this example, the functions of each field in the Legacy mapping restriction can be found in Figure 3, and will not be repeated here.

[0175] The following provides a detailed explanation of the information in each field of the Enhanced mapping restriction shown in the LCH mapping information B above.

[0176] Take the allowedServingCells-disabled field as an example.

[0177] The allowedServingCells-disabled field can be used to indicate whether the allowedServingCells mapping restriction is applied or whether the restriction is removed.

[0178] In some embodiments, if the network device configures the allowedServingCells-disabled field for the LCH, it indicates that the UE can remove the configured allowedServingCells mapping restrictions for the delay-critical LCH. For example, the allowedServingCells-disabled field can be used to indicate that data in the delay-critical LCH can be mapped to the uplink grant of any serving cell for transmission.

[0179] For example, taking `allowedServingCells` as including serving cell 1 and serving cell 2, for a delay-critical LCH, the UE can, based on the received `allowedServingCells-disabled` field, no longer be limited to mapping the LCH to the uplink grant of serving cell 1 or serving cell 2. Correspondingly, the LCH can be mapped to the uplink grant of either serving cell.

[0180] Correspondingly, in other embodiments, the network device configures the allowedServingCells field for the LCH in the Legacy mapping restriction, and this allowedServingCells field is not cancelled. The network device can use this configuration to instruct the UE to map the LCH to the uplink grant of allowedServingCells.

[0181] The following conditions may be met: allowedServingCells not being cancelled: the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedServingCells cannot be cancelled, or the network device is not configured with an indication that allowedServingCells can be cancelled (such as allowedServingCells-disabled), or the current conditions do not meet the conditions for allowingServingCells cancellation.

[0182] For example, consider a scenario where allowedServingCells includes both serving cell 1 and serving cell 2. For non-delay-critical LCHs, the UE can determine that allowedServingCells has not been cancelled. Correspondingly, this LCH can be mapped to the uplink grant of serving cell 1 or serving cell 2.

[0183] Take the allowedSCS-List-disabled field as an example.

[0184] The allowedSCS-List-disabled field can be used to indicate whether the allowedSCS-List mapping restriction is applied or whether the restriction is removed.

[0185] In some embodiments, if the network device configures the allowedSCS-List-disabled field for the LCH, it indicates that the UE can remove the configured allowedSCS-List mapping restrictions for the delay-critical LCH. For example, the allowedSCS-List-disabled field can be used to indicate that data in the delay-critical LCH can be mapped to any SCS-related uplink grant for transmission.

[0186] For example, taking the allowedSCS-List as including service SCS configuration 1 and SCS configuration 2, for a delay-critical LCH, the UE can, based on the received allowedSCS-List-disabled field, no longer be limited to mapping the LCH to the uplink grant associated with SCS configuration 1 or SCS configuration 2. Correspondingly, the LCH can be mapped to the uplink grant associated with any SCS.

[0187] Correspondingly, in other embodiments, the network device configures the allowedSCS-List field for the LCH in the Legacy mapping restriction, and this allowedSCS-List is not canceled. The network device can use this configuration to instruct the UE to map the LCH to the uplink grant associated with the SCS configured in the allowedSCS-List.

[0188] The fact that allowedSCS-List is not canceled can include: the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedSCS-List cannot be canceled, or the network device is not configured with an indication that allowedSCS-List can be canceled (such as allowedSCS-List-disabled).

[0189] For example, consider an allowedSCS-List that includes SCS configuration 1 and SCS configuration 2. For non-delay-critical LCHs, the UE can determine that the allowedSCS-List has not been cancelled. Correspondingly, the UE can map this LCH to the uplink grant associated with SCS configuration 1 or SCS configuration 2.

[0190] Take the maxPUSCH-Duration-disabled field as an example.

[0191] The maxPUSCH-Duration-disabled field can be used to indicate whether the maxPUSCH-Duration mapping limit is applied or whether the limit is disabled.

[0192] In some embodiments, if the network device configures the maxPUSCH-Duration-disabled field for the LCH, it indicates that the UE can cancel the configured maxPUSCH-Duration mapping restriction for the delay-critical LCH. For example, the maxPUSCH-Duration-disabled field can be used to indicate that data in the delay-critical LCH can be mapped to uplink grants for any PUSCH duration for transmission.

[0193] For example, taking a maxPUSCH-Duration value including a duration of 1 as an example. For a delayed critical LCH, the UE can, based on the received maxPUSCH-Duration-disabled field, no longer be limited to mapping the LCH to a PUSCH with a duration less than 1. Correspondingly, the UE can map the LCH to an uplink grant of any PUSCH duration for transmission.

[0194] Correspondingly, in other embodiments, the network device configures a maxPUSCH-Duration field for the LCH in the Legacy mapping restriction, and this maxPUSCH-Duration is not canceled. The network device can use this configuration to instruct the UE to map the LCH to an uplink grant associated with a PUSCH duration that is shorter than the PUSCH duration configured in maxPUSCH-Duration.

[0195] The fact that maxPUSCH-Duration is not canceled can include: the LCH is not a latency-critical LCH, or the network device is configured with an indication that maxPUSCH-Duration cannot be canceled, or the network device is not configured with an indication that maxPUSCH-Duration can be canceled (such as maxPUSCH-Duration-disabled).

[0196] For example, consider a maxPUSCH-Duration that includes a duration of 1. For non-delay-critical LCHs, the UE can determine that the maxPUSCH-Duration has not been canceled. Correspondingly, the UE can associate uplink grants with PUSCHs whose duration is less than 1.

[0197] Take the configuredGrantType1Allowed-delayLCH field as an example.

[0198] In some embodiments, if the network device configures the configuredGrantType1Allowed-delayLCH field for the LCH, it means that for a delay-critical LCH, regardless of whether the network device configures the configuredGrantType1Allowed field for the LCH, the UE can map the LCH to the type1 configured grant uplink grant for data transmission.

[0199] In other embodiments, the mapping of delay-critical LCHs using Type 1 configuration grants can be pre-agreed upon by the UE and the network device. Thus, regardless of whether the network device configures the `configuredGrantType1Allowed` field and / or the `configuredGrantType1Allowed-delayLCH` field for the LCH, the UE can map the delay-critical LCH to a Type 1 configuration grant uplink grant for data transmission.

[0200] Take the allowedPHY-PriorityIndex-disabled field as an example.

[0201] In some embodiments, if the network device configures the allowedPHY-PriorityIndex-disabled field for the LCH, it means that the UE can remove the configured allowedPHY-PriorityIndex mapping restriction for the delay-critical LCH. For example, the allowedPHY-PriorityIndex-disabled field is used to indicate that data in the delay-critical LCH can be mapped to any dynamic license for transmission.

[0202] Correspondingly, in other embodiments, the network device configures the allowedPHY-PriorityIndex field for the LCH in LegacymappingRestriction, and this allowedPHY-PriorityIndex is not canceled. The network device can use this configuration to instruct the UE to map the LCH to the uplink grant corresponding to the priority of allowedPHY-PriorityIndex.

[0203] The condition that allowedPHY-PriorityIndex is not cancelled may include: the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedPHY-PriorityIndex cannot be cancelled, or the network device is not configured with an indication that allowedPHY-PriorityIndex can be cancelled (such as allowedPHY-PriorityIndex-disabled), or the current condition does not meet the conditions for allowedPHY-PriorityIndex cancellation (such as when the UE and the network device agree that allowedPHY-PriorityIndex is configured as P1 with higher priority, allowedPHY-PriorityIndex will not be cancelled).

[0204] Take the allowedCG-List-disabled field as an example.

[0205] In some embodiments, if the network device configures the allowedCG-List-disabled field for the LCH, it indicates that the UE can remove the configured allowedCG-List mapping restrictions for the delay-critical LCH. For example, the allowedCG-List-disabled field can be used to indicate that data in the delay-critical LCH can be mapped to any uplink grant for transmission.

[0206] For example, taking an allowedCG-List that includes CG1 and CG2 as an example. For a delayed critical LCH, the UE can, based on the received allowedCG-List-disabled field, no longer be limited to mapping the LCH to the uplink grants of CG1 and CG2. Correspondingly, the UE can map the LCH to any uplink grant, including CG1 and CG2.

[0207] Correspondingly, in other embodiments, the network device configures the allowedCG-List field for the LCH in the Legacymapping restriction, and this allowedCG-List is not canceled. The network device can use this configuration to instruct the UE to map the LCH to the uplink grant corresponding to the allowedCG-List.

[0208] The fact that allowedCG-List is not canceled can include: the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedCG-List cannot be canceled, or the network device is not configured with an indication that allowedCG-List can be canceled (such as allowedCG-List-disabled).

[0209] For example, consider an allowedCG-List that includes CG1 and CG2. For non-delay-critical LCHs, the UE can determine that the allowedCG-List has not been cancelled. Correspondingly, the UE can map this LCH to the uplink grant corresponding to CG1 or CG2.

[0210] Correspondingly, the UE can map the LCH (such as delay-critical LCH or non-delay-critical LCH) to the corresponding PHY transmission resources according to the configuration in LCH mapping information B, and then send the data to the network device.

[0211] In other embodiments, the fields configured in the LCH mapping information B described above can also be combined with other conditions to configure mapping restrictions to the LCH. These other conditions can be pre-agreed upon by the UE and the network device, or configured by the network device for the UE.

[0212] For example, in some embodiments, taking S401 as an example, the network device configures allowedServingCells and allowedServingCells-disabled in the LCH mapping information B to the LCH.

[0213] This other condition may include whether PDCP replication is configured.

[0214] If PDCP replication is configured, the cancellation of allowedServingCells will not be executed regardless of whether allowedServingCells-disabled is received.

[0215] In this example, the UE can copy the configured LCH according to PDCP without canceling the configured allowedServingCells for that LCH. That is, the LCH (such as a delayed critical LCH or a non-delayed critical LCH) can be mapped to the uplink grant of the serving cell indicated by allowedServingCells for data transmission.

[0216] Correspondingly, if PDCP replication is not configured, the UE can cancel the configuration of allowedServingCells for that LCH based on the received allowedServingCells-disabled message. For example, this LCH (such as a delay-critical LCH) can be mapped to the uplink grant of any serving cell for data transmission.

[0217] In some embodiments, taking S401 as an example, the network device configures allowedPHY-PriorityIndex and allowedPHY-PriorityIndex-disabled in the LCH mapping information B.

[0218] This other condition may include whether allowedPHY-PriorityIndex indicates a high-priority mapping. For example, allowedPHY-PriorityIndex of 1 corresponds to high priority, and allowedPHY-PriorityIndex of 0 corresponds to low priority.

[0219] In some embodiments, for delayed critical LCHs, when allowedPHY-PriorityIndex is 1, the UE will not cancel allowedPHY-PriorityIndex regardless of whether it receives allowedPHY-PriorityIndex-disabled. This allows the UE to map the delayed critical LCH to a high-priority resource for data transmission based on the allowedPHY-PriorityIndex configuration. Similarly, since allowedPHY-PriorityIndex cancellation is not performed, the UE can also map non-delay critical LCHs according to the allowedPHY-PriorityIndex configuration.

[0220] Correspondingly, for a delay-critical LCH, if allowedPHY-PriorityIndex is 0, the UE can remove the mapping restriction of allowedPHY-PriorityIndex based on receiving allowedPHY-PriorityIndex-disabled. Therefore, the UE can map this delay-critical LCH to any dynamic license for data transmission.

[0221] In other embodiments, for delay-critical LCHs, if allowedPHY-PriorityIndex is 0, the cancellation of allowedPHY-PriorityIndex is not performed. If allowedPHY-PriorityIndex is 1, the UE can cancel the allowedPHY-PriorityIndex mapping restriction based on receiving allowedPHY-PriorityIndex-disabled. This situation indicates that the network device prioritizes relaxing restrictions on high-priority services, allowing high-priority services to obtain more resources for transmission.

[0222] The specific implementation of the two embodiments described above can be flexibly selected based on the negotiation between the network device and the UE.

[0223] In some embodiments, taking S401 as an example, the network device configures allowedCG-List and allowedCG-List-disabled to the UE in the LCH mapping information B.

[0224] This other condition may include: whether the LCH currently being processed is a delayed critical LCH.

[0225] If the currently processed LCH is a delay-critical LCH, the UE will not cancel the allowedCG-List. In this way, the UE can map the delay-critical LCH to the corresponding uplink grant in the allowedCG-List based on its configuration.

[0226] Correspondingly, if the currently processed LCH is not a delay-critical LCH (i.e., the currently processed LCH is a non-delay-critical LCH), the UE can cancel the allowedCG-List configuration based on the received allowedCG-List-disabled. The UE can then map the LCH to any uplink grant for transmission.

[0227] In summary, when determining whether to cancel a configured mapping restriction, the UE may refer to at least one of the following conditions: whether PDCP replication is configured, whether allowedPHY-PriorityIndex indicates a high-priority mapping, and whether the currently processed LCH is a delay-critical LCH.

[0228] In other embodiments, other conditions that may be referenced may also include conditions corresponding to other configured mapping restrictions.

[0229] It should be noted that the above example illustrates how the UE cancels the configured mapping restriction based on the received deactivation restriction configuration when other conditions are met. In other embodiments, the UE may, under the condition that the above other conditions are met, not apply the configured mapping restriction based on the received deactivation restriction configuration.

[0230] S402. The UE allocates PHY transmission resources for uplink data transmission based on LCH mapping information B. This LCH mapping information B can be the LCH mapping information configured by the network device for the LCH currently used by the UE.

[0231] For example, the LCH mapping information B received by the UE includes the field configuration shown in S401 above.

[0232] In some embodiments, the LCH mapping information includes configurations related to allowedSCS-List as an example.

[0233] When allowedSCS-List is configured and an indication that allowedSCS-List can be disabled is configured (such as the allowedSCS-List-disabled field), when LCH is a delayed key LCH, that is, the LCH can be mapped to any uplink authorization related to SCS.

[0234] When an allowedSCS-List is configured and it is not cancelled (i.e., the LCH is not a delay-critical LCH, or the network device is configured with an indication that the allowedSCS-List cannot be cancelled, or the network is not configured with an indication that the allowedSCS-List can be cancelled), then the LCH needs to be mapped to the uplink authorization associated with the SCS configured in the allowedSCS-List.

[0235] In some embodiments, the LCH mapping information includes configurations related to maxPUSCH-Duration as an example.

[0236] When maxPUSCH-Duration is configured and an indication that maxPUSCH-Duration can be disabled is configured (such as the maxPUSCH-Duration-disabled field), maxPUSCH-Duration may not be applied when the LCH is a delay-critical LCH. That is, the LCH can be mapped to uplink grants for any PUSCH duration.

[0237] When maxPUSCH-Duration is configured and it is not cancelled (i.e., the LCH is not a latency-critical LCH, or the network device is configured with an indication that maxPUSCH-Duration cannot be cancelled, or the network is not configured with an indication that maxPUSCH-Duration can be cancelled), then the LCH needs to be mapped to an uplink grant associated with a PUSCH duration that is less than the PUSCH duration configured in maxPUSCH-Duration.

[0238] In some embodiments, the LCH mapping information includes configurations related to configuredGrantType1Allowed as an example.

[0239] If the network is not configured with configuredGrantType1Allowed, but the configuredGrantType1Allowed-delayLCH field is configured, then when the LCH is a delay-critical LCH, the LCH can be mapped to the type1 configured authorization.

[0240] When configuredGrantType1Allowed is configured, the LCH can be mapped to the type1 configuration license.

[0241] In other embodiments, the LCH mapping information includes configurations related to allowedServingCells as an example.

[0242] In some implementations, when network devices are configured with indications that allowedServingCells can be disabled (such as the allowedServingCells-disabled field), allowedServingCells may not be applied when the LCH is a delay-critical LCH, meaning that the LCH can be mapped to the uplink grant of any serving cell.

[0243] In some implementations, when the network device is configured with an indication that allowedServingCells can be cancelled, allowedServingCells cannot be left unapplied when PDCP is replicated. That is, the LCH can only be mapped to the uplink authorization of the serving cell indicated by allowedServingCells.

[0244] When network devices are configured with an indication that allowedServingCells can be cancelled, allowedServingCells can be left unapplied if PDCP replication is not configured. In other words, the LCH can be mapped to the uplink grant of any serving cell.

[0245] When allowedServingCells is configured and it is not cancelled (i.e., the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedServingCells cannot be cancelled, or the network is not configured with an indication that allowedServingCells can be cancelled, or PDCP replication is configured), then the LCH can be mapped to the uplink authorization of the serving cell indicated by allowedServingCells.

[0246] In other embodiments, the LCH mapping information includes configurations related to allowedCG-List as an example.

[0247] When a network device is configured with an indication that allowedCG-List can be disabled (such as the allowedCG-List-disabled field), allowedCG-List may not be applied when the LCH is a delay-critical LCH, meaning that the LCH can be mapped to any uplink grant.

[0248] When an allowedCG-List is configured and it is not cancelled (i.e., the LCH is not a delay-critical LCH, or the network device is configured with an indication that the allowedCG-List cannot be cancelled, or the network is not configured with an indication that the allowedCG-List can be cancelled), the LCH can be mapped to the uplink authorization indicated by the allowedCG-List.

[0249] In other embodiments, the LCH mapping information includes configurations related to allowedPHY-PriorityIndex as an example.

[0250] In some implementations, when the network device is configured with an indication that allowedPHY-PriorityIndex can be cancelled, and the LCH is a latency-critical LCH, allowedPHY-PriorityIndex may not be applied, meaning that the LCH can be mapped to any dynamic license.

[0251] When allowedPHY-PriorityIndex is configured and it is not cancelled (i.e., the LCH is not a latency-critical LCH, or the network device is configured with an indication that allowedPHY-PriorityIndex cannot be cancelled, or the network is not configured with an indication that allowedPHY-PriorityIndex can be cancelled), then the LCH can be mapped to the uplink grant of the priority corresponding to allowedPHY-PriorityIndex.

[0252] In some implementations, when the network device is configured with the allowedPHY-PriorityIndex indication to be disabled (configured as allowedPHY-PriorityIndex-disabled), and the allowedPHY-PriorityIndex indicates a high priority (e.g., P1), allowedPHY-PriorityIndex cannot be left unapplied. That is, the LCH can only be mapped to the dynamic authorization with a priority of P1.

[0253] When a network device is configured with an indication that allowedPHY-PriorityIndex can be cancelled, if allowedPHY-PriorityIndex is P0, allowedPHY-PriorityIndex can be ignored, meaning that the LCH can only be mapped to dynamic licenses with a priority of P0.

[0254] In some implementations, when the network device is configured with the allowedPHY-PriorityIndex indication to be disabled (configured as allowedPHY-PriorityIndex-disabled), and the allowedPHY-PriorityIndex indicates a low priority (e.g., P0), allowedPHY-PriorityIndex cannot be left unapplied. That is, the LCH can only be mapped to the dynamic license with a priority of P0.

[0255] When a network device is configured with an indication that allowedPHY-PriorityIndex can be cancelled, if allowedPHY-PriorityIndex is P1, allowedPHY-PriorityIndex can be ignored, meaning that the LCH can only be mapped to dynamic licenses with a priority of P1.

[0256] Understandably, based on this implementation, the UE can prioritize relaxing restrictions on high-priority services, so that high-priority services can obtain more resources for transmission.

[0257] In this way, the UE can map the LCH to the uplink grant corresponding to the resource based on the LCH configuration information B configured for the current LCH. It can be understood that, based on the above explanation, when the current LCH is a delay-critical LCH, the mapping restrictions of the LCH can be effectively relaxed, thereby making it more likely that the delay-critical LCH can be mapped to the uplink grant.

[0258] S403, the UE sends uplink data to the network device.

[0259] For example, a UE can send data (such as critical latency data) mapped to an uplink grant to a network device through the resources corresponding to the uplink grant.

[0260] It is understandable that by configuring this LCH mapping information B, the UE can relax the corresponding mapping restrictions when performing the mapping of delay critical LCH to resource blocks, provided that the above conditions are met.

[0261] This allows the Delay Criterion Channel (LCH) to obtain more resources, thereby improving the data transmission success rate in the Delay Criterion Channel.

[0262] In the example in Figure 4 above, when configuring mapping information for LCH, the network device can relax the mapping of latency-critical LCHs by configuring the deactivation restriction in Legacy mapping restriction and Enhanced mapping restriction.

[0263] In the example above, if the configuration item corresponding to the Legacy mapping restriction is configured in the Enhanced mapping restriction, then the deactivation function has been configured.

[0264] For example, as explained above, if the allowedServingCells field is configured in the Legacy mapping restriction and the corresponding allowedServingCells-disabled field is configured in the Enhanced mapping restriction, the UE can choose not to apply allowedServingCells when the LCH is a delay-critical LCH.

[0265] In other examples, the fields of the configuration items corresponding to the Legacy mapping restriction configured in the Enhanced mapping restriction can be configured with specific values.

[0266] Taking the example where the Legacy mapping restriction includes the first configuration item, and the configuration item in the Enhanced mapping restriction corresponding to the first configuration item is the second configuration item.

[0267] When the field of the second configuration item is the first value (such as 1), it means that the first configuration item will not be applied when the LCH is a delayed critical LCH.

[0268] When the field of the second configuration item is the second value (such as 0), it means that the first configuration item is applied when the LCH is a delayed critical LCH.

[0269] For example, the first configuration item is allowedServingCells, and the second configuration item is allowedServingCells-disabled.

[0270] Thus, when allowedServingCells-disabled is configured to the first value, the UE can prevent allowedServingCells from being applied when the LCH is a delay-critical LCH.

[0271] When allowedServingCells-disabled is configured to the second value, the UE can apply allowedServingCells when the LCH is a delay-critical LCH.

[0272] Other configuration items are similar. They will not be elaborated upon further.

[0273] In other embodiments, the configuration item corresponding to the Legacy mapping restriction configured in the Enhanced mapping restriction can also be used to indicate that the configuration item corresponding to the Legacy mapping restriction is applied when the LCH is not a delay critical LCH.

[0274] This application also provides a scheme in which the mapping relaxation for delay-critical LCHs can be negotiated in advance between the UE and the network device. In some embodiments, the rules for this negotiation may include a configuration that allows cancellation of delay-critical LCHs.

[0275] In this example, the network device can configure a legacy mapping restriction for the LCH, which can be applied to non-delay-critical LCHs. If the LCH is a delay-critical LCH, the UE can, according to pre-negotiated preset rules, not apply some or all of the mapping restrictions in the legacy mapping restriction.

[0276] For example, consider a first configuration item included in the legacy mapping restriction. In some embodiments, the preset rule may include: the first configuration item is not applied when the LCH is a latency-critical LCH, and the first configuration item is applied when the LCH is a non-latency-critical LCH.

[0277] In this way, the UE can determine whether an LCH is a delay-critical LCH before granting uplink authorization for that LCH. If the LCH is a delay-critical LCH, then according to the preset rule, the mapping restriction corresponding to the first configuration item is not applied, and the UE can determine the uplink authorization for that LCH based on other mapping restrictions (if they exist), or it can map that LCH to any uplink authorization. If the LCH is not a delay-critical LCH, then according to the preset rule, the mapping restriction corresponding to the first configuration item is applied, and the UE can determine the uplink authorization for that LCH based on the first configuration item and other applied mapping restrictions (if they exist).

[0278] In some embodiments of this application, the preset rule may include an indication of whether a configuration (such as a first configuration item) is applied when the LCH is a delay-critical LCH and / or whether it is applied when the LCH is not a delay-critical LCH. In other embodiments, the preset rule may include sub-specifications for multiple configuration items, each sub-specification corresponding to one configuration item, and each sub-specification indicating whether the corresponding configuration item is applied when the LCH is a delay-critical LCH and / or whether it is applied when the LCH is not a delay-critical LCH.

[0279] Taking the mapping restriction information configured for LCH by a network device as an example, which includes the following fields:

[0280] Legacy mapping restriction:

[0281] {

[0282] allowedServingCells

[0283] allowedSCS-List

[0284] maxPUSCH-Duration

[0285] allowedPHY-PriorityIndex

[0286] allowedCG-List

[0287] }

[0288] If the LCH is not a delay-critical LCH, then all mapping configurations in this Legacy mapping restriction can take effect.

[0289] Correspondingly, if the LCH is a delay-critical LCH, then the Legacy mapping restriction may include one or more mapping configurations that are ineffective. The specific implementation can be determined based on the results of prior negotiation between the UE and the network device.

[0290] In some embodiments, for the delay critical LCH, all mapping configurations in the Legacy mapping restriction are ineffective.

[0291] The UE can perform LCH mapping according to the following strategies:

[0292] Taking the network device configured with allowedServingCells as an example, when the LCH is not a delay-critical LCH, the UE can map the LCH to the uplink grant of the serving cell indicated by allowedServingCells.

[0293] In some implementations, when the LCH is a delay-critical LCH, the UE can map the LCH to the uplink grant of any serving cell.

[0294] In other implementations, when network devices are configured with allowedServingCells, and the LCH is a delay-critical LCH, allowedServingCells may not be applied if PDCP replication is not configured, meaning the LCH can be mapped to the uplink grant of any serving cell; however, if PDCP replication is configured, allowedServingCells must be applied, meaning the LCH can be mapped to the uplink grant of the serving cell indicated by allowedServingCells.

[0295] Taking a network device configured with an allowedSCS-List as an example: When the LCH is not a delay-critical LCH, the UE can map the LCH to the uplink grant associated with the SCS indicated in the SCS-List. When the LCH is a delay-critical LCH, the UE can map the LCH to the uplink grant associated with any SCS.

[0296] Taking a network device configured with maxPUSCH-Duration as an example: When the LCH is not a delay-critical LCH, the UE can map this LCH to an uplink grant for a PUSCH with a duration shorter than that indicated by maxPUSCH-Duration. When the LCH is a delay-critical LCH, the UE can map this LCH to an uplink grant for a PUSCH of any duration.

[0297] Taking a network device configured with allowedPHY-PriorityIndex as an example, when the LCH is not a delay-critical LCH, the UE can map the LCH to the dynamic authorization of the priority indicated by allowedPHY-PriorityIndex.

[0298] In some implementations, when the LCH is a delay-critical LCH, the UE can map the LCH to any dynamic license.

[0299] In other implementations, when the network device is configured with allowedPHY-PriorityIndex, and the LCH is a latency-critical LCH, if allowedPHY-PriorityIndex is the first value (e.g., corresponding to P1), allowedPHY-PriorityIndex cannot be omitted, meaning the LCH can be mapped to a dynamic license with priority P1; if allowedPHY-PriorityIndex is P0, allowedPHY-PriorityIndex can be omitted, meaning the LCH can be mapped to any dynamic license.

[0300] In other embodiments, when the network device is configured with allowedPHY-PriorityIndex, when the LCH is a latency-critical LCH, if allowedPHY-PriorityIndex is P0, allowedPHY-PriorityIndex cannot be omitted, meaning the LCH can be mapped to a dynamic grant with priority P0; if allowedPHY-PriorityIndex is P1, allowedPHY-PriorityIndex can be omitted, meaning the LCH can be mapped to any dynamic grant.

[0301] Taking a network device configured with an allowedCG-List as an example: When the LCH is not a delay-critical LCH, the UE can map the LCH to the uplink grant indicated by the allowedCG-List. When the LCH is not a delay-critical LCH, the UE can map the LCH to any uplink grant.

[0302] The example above illustrates how a preset rule instructs configured items not to apply when the LCH is a delay-critical LCH. In other embodiments, the preset rule may also define mapping restrictions that can be applied to delay-critical LCHs. Regardless of whether such mapping restrictions are configured in the Legacy mapping restriction, they can take effect for delay-critical LCHs.

[0303] In some embodiments, the preset rule may include mapping the LCH to a type 1 configured grant uplink grant when the LCH is a delay-critical LCH. Thus, for the UE, whether the network has configured `configuredGrantType1Allowed` configured or not, when the LCH is a delay-critical LCH, the UE can map the LCH to an uplink grant using type 1.

[0304] In this way, the network device can configure the legacy mapping restriction of LCH to the UE. When performing LCH mapping, the UE can relax the mapping of the delay-critical LCH based on whether the LCH is a delay-critical LCH and the rules pre-negotiated between the UE and the network device.

[0305] This application also provides a communication method. In this method, the network device can configure additional resource settings for the UE, which can be applied to the delay-critical LCH. This allows the UE to extend the mapping of delay-critical LCHs with more resources based on the already configured mapping restrictions, thereby increasing the probability of successfully transmitting the delay-critical LCH by acquiring resources.

[0306] For example, referring to Figure 5, a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application is shown. In this example, the relevant information of LCH mapping restrictions may include LCH mapping information C. For example, LCH mapping information C includes legacy mapping restrictions and enhanced mapping restrictions, with enhanced mapping restrictions including additional resource configuration.

[0307] As shown in Figure 5, the scheme may include:

[0308] S501, The network device sends LCH mapping information C to the UE. The network device may include a base station.

[0309] In some embodiments, the network device may send an RRC message to the UE, which may carry the LCH mapping information C.

[0310] As an example, the following provides a specific example of LCH mapping information C. Specifically, the LCH mapping information C includes additional resource configurations such as the configuration of SCSlist, maxPUSCH-Duration, and allowedServingCells. It is understood that this example is merely illustrative, and in other embodiments, the content or fields in the LCH mapping information C may be more or fewer.

[0311] LCH mapping information C:

[0312] Legacy mapping restriction:

[0313] {

[0314] allowedServingCells

[0315] allowedSCS-List

[0316] maxPUSCH-Duration

[0317] allowedPHY-PriorityIndex

[0318] configuredGrantType1Allowed

[0319] allowedCG-List

[0320] }

[0321] Enhanced mapping restrictions:

[0322] {

[0323] Additional-allowedServingCells

[0324] Additional-allowedSCS-List

[0325] Additional-maxPUSCH-Duration

[0326] Additional-allowedCG-List

[0327] }

[0328] In this example, the functions of each field in the Legacy mapping restriction can be found in Figure 3, and will not be repeated here.

[0329] The following provides a detailed explanation of the information in each field of the Enhanced mapping restriction shown in the LCH mapping information C above.

[0330] Take the additional-allowedServingCells field as an example.

[0331] The additional-allowedServingCells field can be used to configure additional allowedServingCells resources for the UE. In some embodiments, the additional-allowedServingCells field may include at least one cell identifier that is not included in allowedServingCells.

[0332] In some embodiments, if the network device configures the additional-allowedServingCells field for the LCH, it means that the UE can map the delay-critical LCH based on the serving cell indicated by the configured allowedServingCells and additional-allowedServingCells. For example, the UE can map the delay-critical LCH to the uplink grants of allowedServingCells and additional-allowedServingCells for data transmission.

[0333] For example, consider cases where `allowedServingCells` includes serving cell 1 and serving cell 2, and `additional-allowedServingCells` includes serving cell 3. For a delayed critical LCH, the UE can, based on the received `additional-allowedServingCells` field, no longer be limited to mapping the LCH to the uplink grant of serving cell 1 or serving cell 2. Correspondingly, combined with the serving cell 3 indicated by `additional-allowedServingCells`, the UE can map the LCH to an uplink grant that includes serving cell 1, serving cell 2, or serving cell 3.

[0334] Correspondingly, in other embodiments, if the network device configures the allowedServingCells field for the LCH and additional-allowedServingCells is not applied, the UE can map the delay key LCH to the uplink grant of allowedServingCells for data transmission.

[0335] The cases where additional-allowedServingCells are not applied include:

[0336] The LCH currently being processed is not a latency-critical LCH, or the network device is not configured with additional-allowedServingCells.

[0337] For example, assuming allowedServingCells includes serving cell 1 and serving cell 2. For non-delay-critical LCHs, even if additional-allowedServingCells are not applied, the UE can continue to apply mapping restrictions based on serving cell 1 and serving cell 2 as indicated by allowedServingCells. For example, the UE can map the current LCH to the uplink grant of serving cell 1 or serving cell 2.

[0338] Take the Additional-allowedSCS-List field as an example.

[0339] The additional-allowedSCS-List field can be used to configure additional allowedSCS-List resources for the UE. In some embodiments, the additional-allowedSCS-List field may include at least one SCS configuration not included in the allowedSCS-List.

[0340] In some embodiments, if the network device configures the additional-allowedSCS-List field for the LCH, it means that the UE can map the delay-critical LCH based on the configured allowedSCS-List and the SCS configuration indicated by the additional-allowedSCS-List. For example, the UE can map the delay-critical LCH to the uplink grant associated with the SCS configured in the allowedSCS-List and additional-allowedSCS-List for data transmission.

[0341] For example, consider an allowedSCS-List including SCS configuration 1 and SCS configuration 2, and an additional-allowedSCS-List including SCS configuration 3. For a delayed critical LCH, the UE can, based on the received additional-allowedSCS-List field, no longer be limited to mapping the LCH to the uplink grant associated with SCS configuration 1 or SCS configuration 2. Correspondingly, combined with the service sub-3 indicated by the additional-allowedSCS-List, the UE can map the LCH to the uplink grant associated with SCS configuration 1, SCS configuration 2, or SCS configuration 3.

[0342] Correspondingly, in some other embodiments, if the network device configures the allowedSCS-List field for the LCH and the additional-allowedSCS-List is not applied, the UE can map the delay key LCH to the uplink grant associated with the SCS configured in the allowedSCS-List for data transmission.

[0343] The cases where additional-allowedSCS-List is not applied include:

[0344] The LCH currently being processed is not a latency-critical LCH, or the network device has not configured an additional-allowedSCS-List for the LCH.

[0345] For example, consider an allowedSCS-List that includes SCS configuration 1 and SCS configuration 2. For non-delay-critical LCHs, even if the additional-allowedSCS-List is not applied, the UE can continue to apply mapping restrictions based on SCS configuration 1 and SCS configuration 2 indicated by the allowedSCS-List. For example, the UE can map the current LCH to the uplink grant of either SCS configuration 1 or SCS configuration 2.

[0346] Take the Additional-maxPUSCH-Duration field as an example.

[0347] The additional-maxPUSCH-Duration field can be used to configure additional maxPUSCH-Duration limits for the UE. In some embodiments, the maximum PUSCH duration indicated by additional-maxPUSCH-Duration can be greater than the maximum PUSCH duration of the configured maxPUSCH-Duration standard.

[0348] In some embodiments, if the network device configures the additional-maxPUSCH-Duration field for the LCH, it means that the UE can map the delay-critical LCH based on the maximum PUSCH duration indicated by additional-maxPUSCH-Duration. For example, the UE can map the delay-critical LCH to a PUSCH with a duration shorter than the maximum PUSCH duration configured by additional-maxPUSCH-Duration for data transmission.

[0349] For example, consider a case where `maxPUSCH-Duration` includes a duration of 1, `additional-maxPUSCH-Duration` includes a duration of 2, and duration 2 is greater than duration 1. For a delayed critical LCH, the UE can, based on the received `additional-maxPUSCH-Duration` field, no longer be limited to mapping the LCH to a PUSCH with a duration less than 1. Correspondingly, based on the duration 2 indicated by `additional-maxPUSCH-Duration`, the UE can map the LCH to the uplink grant corresponding to any PUSCH with a duration less than 2.

[0350] Correspondingly, in other embodiments, if the network device configures the maxPUSCH-Duration field for the LCH and additional-maxPUSCH-Duration is not applied, the UE can map the delay key LCH to a PUSCH with a duration less than the maximum PUSCH duration configured by maxPUSCH-Duration for data transmission.

[0351] Among the cases where additional-maxPUSCH-Duration is not applied are:

[0352] The LCH currently being processed is not a latency-critical LCH, or the network device has not configured additional-maxPUSCH-Duration for the LCH.

[0353] For example, assuming maxPUSCH-Duration includes a duration of 1. For non-delay-critical LCHs, the UE may continue to apply mapping restrictions based on the duration of 1 indicated by maxPUSCH-Duration even if additional-maxPUSCH-Duration is not applied. For instance, the UE can map the current LCH to the uplink grant corresponding to a PUSCH with a duration less than 1.

[0354] Take the additional-allowedCG-List field as an example.

[0355] The additional-allowedCG-List field can be used to configure additional allowedCG-List resources for the UE. In some embodiments, the additional-allowedCG-List field may include at least one uplink authorization not included in the allowedCG-List.

[0356] In some embodiments, if the network device configures the additional-allowedCG-List field for the LCH, it means that the UE can map the delay key LCH based on the configured allowedCG-List and the uplink grants indicated by the additional-allowedCG-List. For example, the UE can map the delay key LCH to any uplink grant indicated by the allowedCG-List and the additional-allowedCG-List for data transmission.

[0357] Correspondingly, in other embodiments, if the network device configures the allowedCG-List field for the LCH and the additional-allowedCG-List is not applied, the UE can map the delay key LCH to the uplink grant of the allowedCG-List for data transmission.

[0358] The cases where additional-allowedCG-List is not applied include:

[0359] The LCH currently being processed is not a latency-critical LCH, or the network device is not configured with an additional-allowedCG-List.

[0360] S502, the UE allocates PHY transmission resources for uplink transmission data according to the LCH mapping information C.

[0361] For example, the LCH mapping information C received by the UE includes the field configuration shown in S501 above.

[0362] In some embodiments, the LCH mapping information includes configurations related to the additional-allowedSCS-List as an example.

[0363] Network devices are configured with an additional-allowedSCS-List. When the LCH is a delay-critical LCH, the LCH uses the configured SCS lists in the allowedSCS-List and additional-allowedSCS-List. The LCH can be mapped to uplink authorizations associated with SCSs in the SCS sets indicated by the allowedSCS-List and additional-allowedSCS-List.

[0364] When allowedSCS-List is configured and additional-allowedSCS-List is not applied (i.e., LCH is not a latency-critical LCH, or the network is not configured with additional-allowedSCS-List), then the LCH needs to be mapped to the uplink authorization associated with the SCS configured in allowedSCS-List.

[0365] In some embodiments, the LCH mapping information includes configurations related to additional-maxPUSCH-Duration as an example.

[0366] When a network device is configured with an additional-maxPUSCH-Duration, and the LCH is a latency-critical LCH, the LCH uses the PUSCH duration configured in additional-maxPUSCH-Duration. In this case, the duration of the PUSCH mapped to the LCH can be less than the larger of the durations indicated by additional-maxPUSCH-Duration and additional-maxPUSCH-Duration.

[0367] When maxPUSCH-Duration is configured and additional-maxPUSCH-Duration is not applied (i.e., the LCH is not a latency-critical LCH, or the network does not configure additional-maxPUSCH-Duration), the LCH needs to be mapped to an uplink grant associated with a PUSCH duration that is less than the PUSCH duration configured in maxPUSCH-Duration.

[0368] In some embodiments, the LCH mapping information includes configurations related to additional-allowedServingCells as an example.

[0369] When a network device is configured with additional-allowedServingCells, and the LCH is a delay-critical LCH, the LCH uses additional-allowedServingCells and allowedServingCells. In this case, the LCH can be mapped to the uplink authorization of any of the serving cells in the set of serving cells indicated by additional-allowedServingCells and allowedServingCells.

[0370] When allowedServingCells is configured and additional-allowedServingCells is not applied (i.e., the LCH is not a delay-critical LCH, or the network does not have additional-allowedServingCells configured), the LCH needs to be mapped to the uplink authorization of the serving cell indicated by allowedServingCells.

[0371] In some embodiments, the LCH mapping information includes configurations related to additional-allowedCG-List as an example.

[0372] If a network device is configured with an additional-allowedCG-List, and the LCH is a latency-critical LCH, and the LCH uses the additional-allowedCG-List and allowedCG-List, then the LCH can be mapped to the uplink authorization of the additional-allowedCG-List and allowedCG-List.

[0373] When allowedCG-List is configured and additional-allowedCG-List is not applied (i.e., LCH is not a latency-critical LCH, or the network is not configured with additional-allowedServingCells), then the LCH needs to be mapped to the uplink authorization of allowedCG-List.

[0374] Thus, based on the LCH configuration information C configured for the current LCH, the UE can map this LCH to the uplink grant corresponding to the resource. It is understandable that, based on the above explanation, when the current LCH is a delay-critical LCH, the mapping restrictions for this LCH have more available resources, and it has a higher probability of being mapped to an uplink grant.

[0375] S503, the UE sends uplink data to the network device.

[0376] For example, a UE can use resources to send data (such as critical latency data) mapped to the uplink grant of a resource to a network device.

[0377] Therefore, when mapping a delay-critical LCH, the UE can map to the PHY using resources that are richer than those with legacy mapping restrictions, based on the legacy mapping restrictions in the LCH mapping information C and the additional resource configuration. This allows the delay-critical LCH to acquire resources with a higher probability, thereby improving the data transmission success rate in the delay-critical LCH.

[0378] In other embodiments of this application, enhanced mapping restrictions may include negative configurations.

[0379] For example, referring to Figure 6, a schematic diagram of the interaction flow of a communication method provided in an embodiment of this application is shown. In this example, the relevant information of LCH mapping restrictions may include LCH mapping information D. Specifically, the LCH mapping information D includes legacy mapping restrictions and enhanced mapping restrictions, with the enhanced mapping restrictions including negative configuration, as an example.

[0380] As shown in Figure 6, the scheme may include:

[0381] S601, The network device sends LCH mapping information D to the UE. The network device may include a base station.

[0382] In some embodiments, the network device may send an RRC message to the UE, which may carry the LCH mapping information D.

[0383] As an example, the following provides a specific example of LCH mapping information D. Specifically, it uses the example of a negative configuration including SCSlist in LCH mapping information D. It is understood that this example is merely illustrative, and in other embodiments, the content or fields in LCH mapping information D may be more or fewer.

[0384] LCH mapping information D:

[0385] Legacy mapping restriction:

[0386] {

[0387] allowedServingCells

[0388] allowedSCS-List

[0389] maxPUSCH-Duration

[0390] allowedPHY-PriorityIndex

[0391] configuredGrantType1Allowed

[0392] allowedCG-List

[0393] }

[0394] Enhanced mapping restrictions:

[0395] {

[0396] not-allowedSCS-list

[0397] }

[0398] In this example, the functions of each field in the Legacy mapping restriction can be found in Figure 3, and will not be repeated here.

[0399] In this example, in the configuration of enhanced mapping restrictions, the not-allowedSCS-list field can be used to redefine the scope of the SCS configuration when delaying critical LCH mapping. In some embodiments, the not-allowedSCS-list field may include an identifier of at least one SCS configuration.

[0400] In some embodiments, if the network device configures both the allowedSCS-list and not-allowedSCS-list fields for the LCH, it means that the UE will no longer refer to the SCS configuration indicated by the allowedSCS-list for mapping the delay-critical LCH. Correspondingly, the UE can map the delay-critical LCH to any uplink grant associated with any SCS other than the SCS configuration indicated by the not-allowedSCS-list for transmission.

[0401] For example, consider an allowedSCS-list that includes SCS configuration 1 and SCS configuration 2, and a not-allowedSCS-list that includes SCS configuration 4. For a delayed critical LCH, the UE can receive the not-allowedSCS-list field and no longer map the LCH based on the allowedSCS-list. Correspondingly, the UE can map the LCH to any uplink grant other than the one associated with SCS configuration 4.

[0402] Correspondingly, in other embodiments, the network device configures the allowedSCS-list field for the LCH in the Legacy mapping restriction, and this allowedSCS-list is not canceled. The network device can use this configuration to instruct the UE to map the LCH to any uplink grant associated with the SCS indicated by the allowedSCS-list.

[0403] The fact that allowedSCS-list has not been cancelled may include: the LCH is not a delay-critical LCH, or the network device is configured with an indication that allowedServingCells cannot be cancelled, or the network is not configured with not-allowedSCS-list.

[0404] For example, consider an allowedSCS-list that includes SCS configuration 1 and SCS configuration 2. For non-delay-critical LCHs, the allowedSCS-list is not removed. Thus, the UE can map the LCH based on SCS configuration 1 and SCS configuration 2 configured in the allowedSCS-list field. For instance, the UE can map the LCH to the uplink grant associated with either SCS configuration 1 or SCS configuration 2.

[0405] S602, The UE allocates PHY transmission resources for uplink transmission data according to the LCH mapping information D.

[0406] Taking the configuration received by the UE as shown in the LCH mapping information D above as an example, when mapping the LCH corresponding to this LCH mapping information D, the UE can perform the LCH mapping according to the following strategy:

[0407] When a network device is configured with a not-allowedSCS-list, and the LCH is a delay-critical LCH, the LCH cannot use the SCS list configured in the not-allowedSCS-list. Instead, the LCH can be mapped to uplink authorizations associated with SCSs other than those configured in the not-allowedSCS-list.

[0408] In this example, due to the configuration of not-allowedSCS-list, the configured allowedSCS-list does not take effect for LCH, which is a delayed critical LCH.

[0409] When a network device is configured with an allowedSCS-List and the not-allowedSCS-List is not applied (i.e., the LCH is not a latency-critical LCH, or the network is not configured with a not-allowedSCS-List), the LCH needs to be mapped to the uplink authorization associated with the SCS configured in the allowedSCS-List.

[0410] S603, the UE sends uplink data to the network device.

[0411] Therefore, through this negative configuration, network devices can configure corresponding SCS mapping resources for latency-critical LCHs. This configuration method does not affect the network device's configuration of mapping restrictions for other LCHs. This improves the flexibility of network devices in configuring latency-critical LCH mapping restrictions for UEs.

[0412] It is understood that in the implementation of the scheme provided in Figure 4 above, the enhanced mapping restriction includes deactivation restriction configuration; in the implementation of the scheme provided in Figure 5 above, the enhanced mapping restriction includes additional resource configuration; and in the implementation of the scheme provided in Figure 6 above, the enhanced mapping restriction includes negative configuration. In some embodiments, the enhanced mapping restriction may include any two or three of the above-mentioned deactivation restriction configuration, additional resource configuration, and negative configuration. In this way, the UE can flexibly determine the resource configuration in the delayed critical LCH mapping process based on the actually received enhanced mapping restriction configuration and the configuration of legacy mapping restrictions. For details, please refer to the above description, which will not be repeated here.

[0413] In the scheme examples shown in Figures 4 to 6 above, the LCH mapping configured by the network device for the LCH can include a Legacy mapping restriction, or a Legacy mapping restriction and an Enhanced mapping restriction. Thus, when the LCH is a delay-critical LCH, the UE can perform the delay-critical LCH mapping based on pre-negotiated rules or adjustments to whether the Legacy mapping restriction is canceled according to the Enhanced mapping restriction, and ultimately based on the adjusted Legacy mapping restriction configuration. In these examples, the Enhanced mapping restriction can be related to the Legacy mapping restriction. For example, the configuration items corresponding to fields in the Enhanced mapping restriction can be included in the Legacy mapping restriction configuration items. This allows adjustments to the already configured mappings of the Legacy mapping restriction through the fields of the Enhanced mapping restriction.

[0414] This application also provides a communication method. In this example, the network device can configure a Legacy mapping restriction and an Enhanced mapping restriction for the UE. The Enhanced mapping restriction may include a delay key activation configuration. In this example, the delay key activation configuration and the Legacy mapping restriction configuration items are independent of each other. Specifically, the Legacy mapping restriction is used to restrict mapping when the LCH is not a delay key LCH, and the delay key activation configuration in the Enhanced mapping restriction is used to restrict mapping when the LCH is a delay key LCH.

[0415] For example, in this example, the network device can send LCH mapping information E to the UE. An example of LCH mapping information E is provided below.

[0416] LCH mapping information E:

[0417] Legacy mapping restriction:

[0418] {

[0419] allowedServingCells

[0420] allowedSCS-List

[0421] maxPUSCH-Duration

[0422] allowedPHY-PriorityIndex

[0423] allowedCG-List

[0424] }

[0425] Enhanced mapping restrictions:

[0426] {

[0427] allowedServingCells

[0428] allowedSCS-List

[0429] maxPUSCH-Duration

[0430] allowedPHY-PriorityIndex

[0431] configuredGrantType1Allowed

[0432] allowedCG-List

[0433] }

[0434] In this example, the legacy mapping restriction limits mapping when the LCH is not a delay-critical LCH. The enhanced mapping restriction limits mapping when the LCH is a delay-critical LCH. This rule can be pre-negotiated between the UE and the network device, or instructed to the UE by the network device.

[0435] Thus, when the LCH is not a delayed critical LCH, the Legacy mapping restriction takes effect, while the Enhanced mapping restriction does not; when the LCH is a delayed critical LCH, the Legacy mapping restriction does not take effect, while the Enhanced mapping restriction takes effect.

[0436] Correspondingly, the UE can perform the mapping of the corresponding LCH based on the received LCH mapping information E.

[0437] In some embodiments, the network configures allowedServingCells in the Legacy mapping restriction to indicate that the available serving cells include serving cell set 1; and configures allowedServingCells in the Enhanced mapping restriction to indicate that the available serving cells include serving cell set 2.

[0438] When the LCH is not a delay-critical LCH, it can be mapped to the uplink grant of the serving cell in serving cell set 1; when the LCH is a delay-critical LCH, it can be mapped to the uplink grant of the serving cell in serving cell set 2.

[0439] In other embodiments, the network configures an allowedSCS-List in the Legacy mapping restriction, indicating that the available SCSs include SCS set 1; and configures an allowedSCS-List in the Enhanced mapping restriction, indicating that the available SCSs include SCS set 2.

[0440] When the LCH is not a delay key LCH, the LCH can be mapped to the uplink grant associated with the SCS in SCS set 1; when the LCH is a delay key LCH, the LCH can be mapped to the uplink grant associated with the SCS in SCS set 2.

[0441] In other embodiments, the network configures `maxPUSCH-Duration` in the Legacy mapping restriction, indicating a maximum PUSCH duration of 1; and configures `maxPUSCH-Duration` in the Enhanced mapping restriction, indicating a maximum PUSCH duration of 2. In some implementations, duration 2 is greater than duration 1.

[0442] When the LCH is not a delay-critical LCH, it can be mapped to the uplink grant of a PUSCH with a maximum duration of less than 1; when the LCH is a delay-critical LCH, it can be mapped to the uplink grant of a PUSCH with a maximum duration of less than 2.

[0443] In other embodiments, the network configures allowedPHY-PriorityIndex in the Legacy mapping restriction to indicate priority A; and configures allowedPHY-PriorityIndex in the Enhanced mapping restriction to indicate priority B.

[0444] When the LCH is not a delay-critical LCH, it can be mapped to the dynamic license corresponding to priority A; when the LCH is a delay-critical LCH, it can be mapped to the dynamic license corresponding to priority B.

[0445] In other embodiments, the network configures an allowedCG-List in the Legacy mapping restriction to indicate that uplink authorization is available for CG set 1; and configures an allowedCG-List in the Enhanced mapping restriction to indicate that uplink authorization is available for CG set 2.

[0446] When the LCH is not a delayed key LCH, it can be mapped to the uplink grant in CG set 1; or the dynamic grant corresponding to priority A; when the LCH is a delayed key LCH, it can be mapped to the uplink grant in CG set 2.

[0447] In other embodiments, the network does not configure an authorization type field in the Legacy mapping restriction, but configureGrantType1Allowed is configured in the Enhanced mapping restriction.

[0448] When the LCH is not a delayed critical LCH, the LCH cannot use uplink grant of type 1; when the LCH is a delayed critical LCH, the LCH can use uplink grant of type 1.

[0449] In this way, the network can configure the LCH to be targeted at the delay key LCH through the delay key effective configuration, so that the delay key LCH can be mapped more efficiently.

[0450] Understandably, the UE can map the corresponding LCH to the uplink grant according to the above mechanism, and then transmit the data in the LCH to the network through the resources corresponding to the uplink grant.

[0451] In the example of LCH mapping information E above, the network configures a Legacy mapping restriction so that, when the LCH is not a delay-critical LCH, the UE can determine the uplink grant for that LCH based on the configuration items in the Legacy mapping restriction. Furthermore, the network can also configure an Enhanced mapping restriction so that, when the LCH is a delay-critical LCH, the UE can determine the uplink grant for that LCH based on the configuration items in the Enhanced mapping restriction.

[0452] In other embodiments, the network may configure enhanced mapping restrictions only for the UE. That is, no mapping restrictions are configured for non-delay-critical LCHs. For delay-critical LCHs, the UE can determine the uplink grant based on the configuration of the enhanced mapping restrictions.

[0453] For example, in this example, the LCH mapping information F configured by the network for the UE may include:

[0454] LCH mapping information F:

[0455] Enhanced mapping restrictions:

[0456] {

[0457] configuredGrantType1Allowed

[0458] }

[0459] In this example, the network configures an enhanced mapping restriction for the UE via LCH mapping information F, which includes LCH mapping information configuredGrantType1Allowed. This enhanced mapping restriction can be applied when the LCH is a delay-critical LCH.

[0460] In this way, when the LCH is a delay-critical LCH, the UE can use the Type 1 type to grant uplink authorization for the LCH if the LCH is configured with the above LCH mapping information F in the network.

[0461] Correspondingly, if the network is configured with the aforementioned LCH mapping information F, the Enhanced mapping restriction will not take effect when the LCH is not a delay-critical LCH. Therefore, the UE will not use Type 1 for uplink authorization of this LCH.

[0462] It is understood that the Legacy mapping restriction and / or Enhanced mapping restriction provided in the above embodiments are merely examples. In other embodiments, the field names of the Legacy mapping restriction and / or Enhanced mapping restriction, the configuration item content they include, and the field names of the configuration items may differ from the examples above.

[0463] For example, a legacy mapping restriction can also be called a first mapping restriction. An enhanced mapping restriction can also be called a second mapping restriction, and so on.

[0464] For example, the configuration items in any of the LCH mapping information A to LCH mapping information F may be more or fewer than those given in the examples above. This application does not impose any limitations on this.

[0465] It should be noted that the terminal device in this application embodiment may include at least one of the following: mobile phone, foldable electronic device, tablet computer, desktop computer, laptop computer, handheld computer, laptop, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device, or smart city device. This application embodiment does not impose any special limitation on the specific type of terminal device.

[0466] In some embodiments, the terminal device may have the configuration shown in FIG1. ​​In other embodiments, the terminal device may also have other configurations.

[0467] For example, Figure 7 shows a schematic diagram of the composition of a terminal device 700. As shown in Figure 7, the terminal device 700 may include a processor 701 and a memory 702. The memory 702 is used to store computer execution instructions. For example, in some embodiments, when the processor 701 executes the instructions stored in the memory 702, the terminal device 700 may perform any of the methods shown in the above embodiments.

[0468] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0469] Figure 8 shows a schematic diagram of a chip system 800. The chip system 800 may include a processor 801 and a communication interface 802, used to support related devices in implementing the functions involved in the above embodiments. In one possible design, the chip system also includes a memory for storing necessary program instructions and data for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices. It should be noted that in some implementations of this application, the communication interface 802 may also be referred to as an interface circuit. The chip system may be a modem, or a system-on-a-chip (SoC) including a modem; the above methods can be implemented by a modem.

[0470] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0471] In other embodiments of this application, the chip system includes a processing circuit, a receiving pin, and a transmitting pin. The receiving pin, the transmitting pin, and the processing circuit communicate with each other via internal interconnection paths. The processing circuit executes the communication method provided in any of the above embodiments to control the receiving pin to receive signals and to control the transmitting pin to transmit signals.

[0472] Furthermore, this application provides a terminal device that has the function of implementing the behavior of the terminal device in any of the above method embodiments. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the various sub-functions described above. Specifically, the terminal device can be a user device, such as a mobile phone.

[0473] This application also provides a network device. This network device can be used to implement the functions of the network devices involved in any of the above embodiments. In some embodiments, the network device can be a base station.

[0474] This application also provides a communication system, which includes the network device and terminal device described in any of the above embodiments.

[0475] This application also provides a computer-readable storage medium storing a computer program thereon. When executed by a computer, the computer program implements the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer can be the aforementioned terminal device.

[0476] This application also provides a computer-readable storage medium storing a computer program thereon. When executed by a computer, the computer program implements the method flow related to the network device in any of the above method embodiments. Specifically, the computer can be the aforementioned network device.

[0477] This application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, will cause the computer to implement the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer can be the aforementioned terminal device.

[0478] This application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, causes the computer to implement the method flow related to the network device in any of the above method embodiments. Specifically, the computer can be the aforementioned network device.

[0479] This application also provides an apparatus for use in a terminal device. The apparatus is coupled to a memory and is used to read and execute instructions stored in the memory, enabling the terminal device to execute method flows related to the terminal device in any of the above method embodiments. The memory may be integrated into the processor or may be independent of the processor. The apparatus may be a chip on the terminal device. In some implementations, the chip may be a System on a Chip (SoC).

[0480] It should be understood that the processor mentioned in the embodiments of the present invention can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0481] It should also be understood that the memory mentioned in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0482] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0483] The functions, actions, operations, or steps in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software programs, they can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or include one or more data storage devices such as servers and data centers that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

Claims

1. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Receive first logical channel (LCH) mapping information, the first LCH mapping information being used to determine the uplink grant of the first LCH; Based on the first LCH mapping information, first data is sent with a first uplink grant; the first data is data in the first LCH. Wherein, the first LCH mapping information includes a first mapping restriction, and the terminal device determines the first uplink authorization based on the first mapping restriction and a preset rule; the preset rule is used to restrict whether at least one configuration item in the first mapping restriction is applied; or... The first LCH mapping information includes a first mapping restriction and a second mapping restriction. The first mapping restriction is used to determine the uplink grant of the first LCH, and the second mapping restriction is used to determine the uplink grant when the first LCH is a delay-critical LCH; or, The first LCH mapping information includes a third mapping restriction, which is used to determine uplink authorization when the first LCH is a delay-critical LCH.

2. The method according to claim 1, characterized in that, The data in the delay key LCH includes delay key data, or, The LCH group to which the delay key LCH belongs includes at least one LCH containing the delay key data; Wherein, the remaining time of the delayed key data is less than the corresponding threshold value.

3. The method according to claim 1 or 2, characterized in that, Before sending the first data, the method further includes: Map the first LCH to the first uplink grant.

4. The method according to claim 3, characterized in that, The first mapping restriction includes at least one of the following configuration items: Subcarrier spacing (SCS) configuration, physical uplink shared channel (PUSCH) configuration, configuration related to authorization, configuration related to serving cell, and configuration related to dynamic authorization; The SCS configuration indicates the subcarrier spacing for LCH mapping to uplink grant; the PUSCH configuration indicates the maximum PUCSH duration for LCH mapping to uplink grant; the configuration related to the grant is used to indicate the grant type and / or available grants for LCH mapping to uplink grant; the configuration related to the serving cell is used to indicate the serving cell for LCH mapping to uplink grant; and the configuration related to dynamic grant is used to indicate the priority index of dynamic grant for LCH mapping to uplink grant.

5. The method according to claim 4, characterized in that, The preset rule corresponds to the first configuration item in the first mapping restriction; the preset rule is used to restrict whether the first configuration item is applied.

6. The method according to claim 5, characterized in that, The preset rules include: If the first LCH is a delayed critical LCH, the first configuration item is not applied; and / or, If the first LCH is not a delay-critical LCH, the first configuration item is applied.

7. The method according to claim 6, characterized in that, The first configuration item includes the relevant configurations for the serving cell. The preset rules include: If the first LCH is a delay-critical LCH and PDCP replication is not configured, the first configuration item is not applied, and the first LCH can be mapped to the uplink grant of any serving cell; and / or, When PDCP replication is configured, if the first LCH is a delay-critical LCH or a non-delay-critical LCH, the first configuration item is applied, and the first LCH can be mapped to the uplink authorization of the serving cell indicated by the relevant configuration of the serving cell.

8. The method according to claim 6 or 7, characterized in that, The first configuration item includes the configuration related to the dynamic authorization. The preset rules include: If the first LCH is a delayed critical LCH and the priority index of the dynamic authorization configuration indication is a second value, the first configuration item is not applied, and the first LCH can be mapped to any dynamic authorization; and / or, When the priority index of the relevant configuration indication for dynamic authorization is a first value, and the first LCH is a delayed key LCH or a non-delayed key LCH, the first LCH can be mapped to the dynamic authorization corresponding to the priority of the relevant configuration indication for dynamic authorization. Wherein, the priority when the priority index is the second value is lower than the priority when the priority index is the first value.

9. The method according to any one of claims 6-8, characterized in that, The preset rules include: When the first LCH is a delayed critical LCH, the available uplink grants for the first LCH include uplink grants of type 1; and / or, If the first LCH is not a delayed critical LCH, the available uplink grants for the first LCH do not include uplink grants of type 1.

10. The method according to claim 4, characterized in that, The first LCH mapping information includes a first mapping restriction and a second mapping restriction; The second mapping restriction includes at least one of the following: Remove activation restrictions, additional resource configurations, deny configurations, and delay critical activation configurations; The deactivation restriction configuration is used to indicate whether the configuration items in the first mapping restriction are applied when the first LCH is a delayed critical LCH. The additional resource configuration is used to indicate additional configuration items that can be used when the first LCH is a delay-critical LCH and the first mapping restriction is applied. The negative configuration is used to indicate the configuration item that should not be applied when the first LCH is a delayed critical LCH; The delay key activation configuration is used to indicate the available configuration items when the first LCH is a delay key LCH.

11. The method according to claim 10, characterized in that, The second mapping restriction includes at least one of the following configuration items: The relevant SCS configuration is used to indicate whether to apply or not to apply the SCS configuration in the first mapping restriction, or to restrict the SCS configuration not to be applied when the first LCH is a delay-critical LCH, or to configure additional SCS configuration when the first LCH is a delay-critical LCH, or to configure the SCS configuration when the first LCH is a delay-critical LCH. The relevant PUSCH configuration is used to indicate whether to apply / not apply the PUSCH configuration in the first mapping restriction, or to configure additional PUSCH configuration when the first LCH is a delay-critical LCH, or to configure PUSCH configuration when the first LCH is a delay-critical LCH. The relevant configuration of the serving cell is used to indicate whether to apply or not to apply the relevant configuration of the serving cell in the first mapping restriction, or to configure the relevant configuration of the additional serving cell when the first LCH is a delay key LCH, or to configure the relevant configuration of the serving cell when the first LCH is a delay key LCH. The configuration of available configuration authorization is used to indicate the available configuration authorization indicated in the relevant configuration of applying / not applying the configuration authorization in the first mapping restriction, or to configure additional available configuration authorization when the first LCH is a delay key LCH, or to configure available configuration authorization when the first LCH is a delay key LCH. The configuration of the type of available configuration authorization is used to indicate the type of available configuration authorization indicated in the relevant configuration of applying / not applying the configuration authorization in the first mapping restriction, or to configure the type of available configuration authorization when the first LCH is a delayed key LCH; The configuration related to dynamic authorization is used to indicate whether to apply or not to the dynamic authorization configuration in the first mapping restriction, or to configure the dynamic authorization configuration when the first LCH is a delayed critical LCH.

12. The method according to claim 10 or 11, characterized in that, The second mapping restriction includes a second configuration item, which corresponds to the first configuration item in the first mapping restriction. When the second configuration item is a first value, the first configuration item is not applied if the first LCH is a delay-critical LCH; when the second configuration item is a second value, the first configuration item is applied if the first LCH is a delay-critical LCH; or... If the first LCH is a delay-critical LCH, the first configuration item is not applied; or, If the first LCH is not a delay-critical LCH, the first configuration item is applied.

13. The method according to claim 6 or 12, characterized in that, The first configuration item includes the SCS configuration; The first configuration item is not applied, including: The first LCH can be mapped to any SCS-related uplink grant.

14. The method according to claim 6 or 12, characterized in that, The first configuration item includes the PUSCH configuration; The first configuration item is not applied, including: The first LCH can be mapped to an uplink grant of any PUSCH duration.

15. The method according to claim 6 or 12, characterized in that, The first configuration item includes configuration related to the configuration authorization, which is used to indicate the available configuration authorization; The first configuration item is not applied, including: The first LCH can be mapped to any uplink grant.

16. The method according to claim 6 or 12, characterized in that, The first configuration item includes the relevant configuration of the serving cell; The first configuration item is not applied, including: The first LCH can be mapped to the uplink grant of any serving cell.

17. The method according to claim 16, characterized in that, The second mapping restriction includes the serving cell's configuration, indicating that the serving cell's configuration in the first mapping restriction should not be applied; The first LCH can be mapped to the uplink grant of any serving cell, including: Without PDCP replication configured, the first LCH can be mapped to the uplink authorization of any serving cell.

18. The method according to claim 10 or 11, characterized in that, The first configuration item includes the relevant configuration of the serving cell, and the second mapping restriction includes the relevant configuration of the serving cell that indicates not to apply the first mapping restriction; When PDCP replication is configured, the first LCH can be mapped to the uplink grant corresponding to the serving cell indicated by the first configuration item.

19. The method according to claim 6 or 12, characterized in that, The first configuration item includes the configuration related to the dynamic authorization. The first configuration item is not applied, including: The first LCH can be mapped to any dynamic license.

20. The method according to claim 19, characterized in that, The second mapping restriction includes dynamic authorization-related configurations, used to indicate that the dynamic authorization-related configurations in the first mapping restriction are not applied; The first LCH can be mapped to the uplink grant of any serving cell, including: In the first mapping restriction, when the priority index of the dynamic authorization related configuration indication is the second value, the first LCH can be mapped to the uplink authorization of any serving cell; The priority when the priority index is the second value is lower than the priority when the priority index is the first value.

21. The method according to claim 11, characterized in that, The first configuration item includes the configuration related to the dynamic authorization, used to indicate that the configuration related to the dynamic authorization in the first mapping restriction is not applied; In the first mapping restriction, if the priority index of the relevant configuration indication of the dynamic authorization is a first value, the first LCH can be mapped to the uplink authorization with the priority index of the first value.

22. The method according to claim 11, characterized in that, The first configuration item includes configuration related to the configuration authorization. The first configuration item is used to ensure that the available uplink authorization for the first LCH does not include uplink authorization of type 1. The second mapping restriction includes configuration of the type of available configuration authorization, which is used to indicate that when the first LCH is a delayed critical LCH, uplink authorization of type 1 can be used. The first LCH can be mapped to an uplink authorization of type Type 1.

23. The method according to claim 11, characterized in that, The first configuration item includes SCS configuration, and the second mapping restriction includes additional SCS configuration for configuring when the first LCH is a delay-critical LCH; The first LCH can be mapped to the uplink authorization associated with the first SCS; the first SCS configuration is included in the SCS configuration set indicated by the first configuration item and the second configuration item.

24. The method according to claim 11, characterized in that, The first configuration item includes the relevant configuration of the serving cell, and the second mapping restriction includes the relevant configuration for configuring additional serving cells when the first LCH is a delay-critical LCH; The first LCH can be mapped to the uplink grant corresponding to the first serving cell; The first serving cell is included in the configuration set of serving cells indicated by the first configuration item and the second configuration item.

25. The method according to claim 11, characterized in that, The first configuration item includes a PUSCH configuration indicating a first duration, and the second mapping limit includes an additional PUSCH configuration for configuring an additional PUSCH configuration when the first LCH is a delay-critical LCH, the additional PUSCH configuration indicating a second duration, and the first duration being less than the second duration; The first LCH can be mapped to the uplink authorization corresponding to the first PUSCH configuration; the duration of the first PUSCH configuration is less than the second duration.

26. The method according to claim 11, characterized in that, The second mapping restriction includes the availability of Type 1 type for the configuration authorization type when the first LCH is a delayed critical LCH; The first LCH can be mapped to the uplink authorization of the Type 1 type.

27. The method according to claim 11, characterized in that, The second mapping restriction includes a second SCS configuration for restricting the application of a delay-critical LCH when the first LCH is not applied; The step of mapping the first LCH to the first uplink grant includes: The first LCH is mapped to the uplink authorization associated with the third SCS configuration, which is different from the second SCS configuration.

28. The method according to claim 27, characterized in that, The first configuration item includes a first SCS configuration; the first SCS configuration is not applied.

29. The method according to any one of claims 1-28, characterized in that, The first LCH mapping information includes a third mapping restriction, which is used to determine uplink authorization when the first LCH is a delay-critical LCH; The third mapping restriction includes at least one of the following configuration items: Delay-critical SCS configuration, used to indicate the uplink authorization SCS configuration that can be mapped when the first LCH is a delay-critical LCH; Delay-critical PUSCH configuration, used to indicate the uplink authorization PUSCH configuration that can be mapped when the first LCH is a delay-critical LCH; The Delayed Key Authorization Type Configuration is used to indicate the authorization type of uplink authorization that can be mapped when the first LCH is a Delayed Key LCH; Delay key available configuration authorization is used to indicate the configuration authorization that can be mapped when the first LCH is a delay key LCH; Delay-critical serving cell configuration is used to indicate the serving cell corresponding to the uplink grant that can be mapped when the first LCH is a delay-critical LCH; The Delayed Criterion Dynamic Authorization Configuration is used to indicate the priority of dynamic authorization that can be mapped when the first LCH is a Delayed Criterion LCH.

30. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: First data is sent via a first uplink grant; the first data is data in a first LCH; the first uplink grant is determined according to preset rules; The preset rules include: when the first LCH is a delayed critical LCH, the first LCH can be mapped to an uplink grant of type 1.

31. A terminal device, characterized in that, The terminal device is used to perform the method as described in any one of claims 1-29, or the method as described in claim 30.

32. A communication system, characterized in that, The communication system includes the terminal device as described in claim 31, and a network device; The network device is configured to receive first data via a first uplink grant; the first data is data in a first LCH; the first uplink grant is determined based on the first LCH mapping information, or the first uplink grant is determined based on a preset rule; Wherein, the first LCH mapping information includes a first mapping restriction, which is used by the terminal device to determine the first uplink authorization based on the first mapping restriction and a preset rule; the preset rule is used to restrict whether at least one configuration item in the first mapping restriction is applied; or... The first LCH mapping information includes a first mapping restriction and a second mapping restriction. The first mapping restriction is used to determine the uplink grant of the first LCH, and the second mapping restriction is used to determine the uplink grant when the first LCH is a delay-critical LCH; or, The first LCH mapping information includes a third mapping restriction, which is used to determine uplink authorization when the first LCH is a delay-critical LCH.

33. The communication system according to claim 32, characterized in that, The network device is further configured to send first LCH mapping information to the terminal device, the first LCH mapping information being used to determine the uplink authorization of the first LCH.

Images