A method for processing multi-resource conflicts and terminal equipment

Abstract

The embodiment of the present invention provides a method and terminal device for processing multiple resource conflicts, which are used to avoid unnecessary resource transmission blocking and ensure priority resource transmission. It can include: when the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization; the uplink authorization is compared with the compared resource.

Description

[0001] This application is a divisional application of an application with an application date of April 21, 2020, application number 2020800998007 (international application number PCT / CN2020 / 085997), and invention name “A method and terminal device for handling multi-resource conflicts”. Technical Field

[0002] The present invention relates to the field of communications, and in particular to a method for processing multiple resource conflicts and a terminal device. Background Art

[0003] 5G IIoT (Industrial interest of Things, Industrial Internet) requires support for the transmission of services such as industrial automation (Factory automation), transport automation (Transport Industry), and smart power (Electrical Power Distribution) in 5G systems. Based on its transmission requirements for latency and reliability, IIoT introduces the concept of time sensitive network (TSN) or time sensitive communication (TSC). Therefore, the probability of conflict in time between resources configured for the same user is a problem that needs to be solved. The conflict includes conflicts between data channels, conflicts between data channels and control channels (or uplink control information (UCI)), and conflicts between control channels (or UCI) and control channels (or UCI). UCI can be at least one of the following: Scheduling request (SR), Hybrid Automatic Repeat reQuest (HARQ) feedback, and Channel State Information Reference signal (CSI-RS).

[0004] In the resource conflict scenario, there are multiple resource conflicts. For example, resource A conflicts with resource B, and resource B conflicts with resource C. The resource can be a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH), without specific limitation. Figure 1 As shown in FIG. 1 , a schematic diagram of a resource conflict scenario in the prior art is shown. Figure 1As shown, in terms of priority, L1>L2>L3. In the prior art, if the subsequent L2 resource has higher priority data, the resource priority becomes higher, such as higher than L1 and L3, but because the previous priority of L2 is low, the L2 resource can no longer be transmitted as a high priority resource. Summary of the invention

[0005] The embodiment of the present invention provides a method for processing multiple resource conflicts and a terminal device, which are used to avoid unnecessary resource transmission blocking and ensure priority resource transmission.

[0006] In view of this, the first aspect of an embodiment of the present invention provides a method for handling multiple resource conflicts, which may include: when the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization; performing a priority comparison between the uplink authorization and the compared resource.

[0007] Optionally, in some embodiments of the present invention, before performing priority comparison on the uplink authorization and the compared resources, the method further includes: initializing the uplink authorization as a specific type of uplink resource.

[0008] Optionally, in some embodiments of the present invention, the uplink authorization is compared with the compared resources in priority, including: when the uplink authorization is compared with the compared resources in priority, the uplink authorization is considered to be a specific type of uplink resource.

[0009] Optionally, in some embodiments of the present invention, when a priority comparison is performed between the uplink authorization and the compared resource, the uplink authorization is considered to be the specific type of uplink resource, including: before a priority comparison is performed between the uplink authorization and the compared resource, the uplink authorization is considered to be the specific type of uplink resource; or after a priority comparison is performed between the uplink authorization and the compared resource, the uplink authorization is considered to be the specific type of uplink resource.

[0010] Optionally, in some embodiments of the present invention, the specific type of uplink resource is a priority uplink resource or a low priority uplink resource.

[0011] Optionally, in some embodiments of the present invention, the compared resource is not or is not yet a low-priority uplink resource.

[0012] Optionally, in some embodiments of the present invention, performing a priority comparison between the uplink grant and the compared resource includes:

[0013] If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant;

[0014] If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and,

[0015] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0016] The uplink authorization is a priority uplink authorization;

[0017] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0018] Optionally, in some embodiments of the present invention, at least one of the first configured uplink grant, the SR, and the PUCCH resource is not or is not yet a low-priority uplink resource.

[0019] Optionally, in some embodiments of the present invention, performing a priority comparison between the uplink grant and the compared resource includes:

[0020] If the uplink authorization is a configuration uplink authorization;

[0021] If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and,

[0022] If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and,

[0023] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0024] The uplink authorization is a priority uplink authorization;

[0025] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0026] Optionally, in some embodiments of the present invention, at least one of the second configured uplink grant, the first target uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0027] Optionally, in some embodiments of the present invention, the method further includes:

[0028] If the SR or the PUCCH resource for transmitting the SR is configured as the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR meets at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource;

[0029] No overlap with other uplink resources;

[0030] Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is higher than the priority of other uplink resources;

[0031] Overlapping with other uplink resources, and the priority of the PUCCH resource transmitting the SR is higher than the priority of other uplink resources;

[0032] Overlapping with other uplink resources, the priority of the logical channel triggering the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources;

[0033] And, overlapping with other uplink resources, the priority of the PUCCH resource transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources.

[0034] Optionally, in some embodiments of the present invention, the method further includes:

[0035] If the SR or the PUCCH resource for transmitting the SR is configured as the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a low-priority uplink resource;

[0036] Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources;

[0037] Overlapping with other uplink resources, and the priority of the PUCCH resource transmitting the SR is lower than or equal to the priority of other uplink resources;

[0038] Overlapping with other uplink resources, the priority of the logical channel triggering the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not considered to be low-priority uplink resources;

[0039] Also, overlapping with other uplink resources, the priority of the PUCCH resource for transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not yet low-priority uplink resources.

[0040] Optionally, in some embodiments of the present invention,

[0041] The uplink authorization includes: not being or not yet being a low-priority uplink authorization; or,

[0042] The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or,

[0043] The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

[0044] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource.

[0045] Optionally, in some embodiments of the present invention, the method further includes: performing uplink transmission according to the specific type of uplink resource.

[0046] Optionally, in some embodiments of the present invention, the uplink transmission is performed based on the specific type of uplink resource, including: if the specific type of uplink resource is a priority uplink resource, transmitting the specific type of uplink resource; and / or, if the specific type of uplink resource is a low-priority uplink resource, not transmitting the specific type of uplink resource.

[0047] Optionally, in some embodiments of the present invention, the target priority comparison method includes: a logical channel priority comparison method.

[0048] A second aspect of an embodiment of the present invention provides a terminal device having a function of avoiding unnecessary resource transmission blocking and ensuring priority resource transmission. 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 above functions.

[0049] Another aspect of an embodiment of the present invention provides a terminal device, comprising: a memory storing executable program code; a processor coupled to the memory; the processor calls the executable program code stored in the memory to execute the method described in the first aspect of the embodiment of the present invention.

[0050] Another aspect of an embodiment of the present invention provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enables the computer to execute the method as described in the first aspect of the present invention.

[0051] Yet another aspect of an embodiment of the present invention provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method as described in the first aspect of the present invention.

[0052] Another aspect of an embodiment of the present invention provides a chip, which is coupled to a memory in the terminal device, so that the chip calls program instructions stored in the memory during operation, so that the terminal device executes the method described in the first aspect of the present invention.

[0053] The technical solution provided by the embodiment of the present invention has the following beneficial effects:

[0054] In the embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison mode, for each uplink authorization, the uplink authorization is compared with the compared resource to avoid unnecessary resource transmission blocking and ensure priority resource transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A schematic diagram of a resource conflict scenario in the prior art;

[0056] Figure 2 A system architecture diagram for use in an embodiment of the present invention;

[0057] Figure 3A A schematic diagram of an embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention;

[0058] Figure 3B A schematic diagram of another embodiment of a method for handling multi-resource conflicts in an embodiment of the present invention;

[0059] Figure 4 A schematic diagram of another embodiment of a method for handling multi-resource conflicts in an embodiment of the present invention;

[0060] Figure 5 A schematic diagram of another embodiment of a method for handling multi-resource conflicts in an embodiment of the present invention;

[0061] Figure 6 A schematic diagram of another embodiment of a method for handling multi-resource conflicts in an embodiment of the present invention;

[0062] Figure 7 A schematic diagram of another embodiment of a method for handling multi-resource conflicts in an embodiment of the present invention;

[0063] Figure 8A schematic diagram of an embodiment of a terminal device in an embodiment of the present invention;

[0064] Fig. 9 FIG. 2 is a schematic diagram of another embodiment of a terminal device in an embodiment of the present invention. DETAILED DESCRIPTION

[0065] The technical solutions in the embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0066] It should be noted that according to the conclusion of RAN (Radio Access Network) 2#109e meeting, resources that are considered to be low priority (such as SR or uplink authorization) cannot be deprioritized. Figure 1 As shown in FIG. 1 , if according to this conclusion, L2 has a lower priority than L1, L2 will be considered as a low priority resource, and L2 should not deprioritize L3 resources. Then, according to this priority judgment processing result, in the end, L3 and L1 resources will be transmitted.

[0067] In the prior art, the current RAN2 38.321 protocol is written as follows to determine whether a resource is a deprioritized resource, but it cannot reflect the above conclusion (agreement).

[0068] When the Media Access Control (MAC) entity is configured with lch-basedPrioritization, for each uplink grant that has not been considered as low priority:

[0069] 1> If this uplink grant is scrambled by CS-RNTI (Configured Scheduling Radio Network Temporary Identifier) ​​and NDI (New data indication) = 1, or an uplink grant scrambled by C-RNTI (Cell Radio Network Temporary Identifier):

[0070] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same bandwidth part (Bandwidth Part, BWP) with a higher priority than this uplink grant; and,

[0071] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0072] 3>This uplink authorization is the priority uplink authorization;

[0073] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0074] 1> If the uplink authorization is a configuration uplink authorization:

[0075] 2> If there is no overlap with the PUSCH duration of another configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0076] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant; and,

[0077] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0078] 3>This uplink authorization is the priority uplink authorization;

[0079] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0080] Understandably, the corresponding English translation is:

[0081] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant which is not already a de-prioritized uplink grant:

[0082] 1>if this uplink grant is addressed to CS-RNTI with NDI=1or C-RNTI:

[0083] 2>if there is no overlapping PUSCH duration of a configured uplinkgrant,in the same BWP whose priority is higher than the priority of theuplink grant;and

[0084] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0085] 3>this uplink grant is a prioritized uplink grant;

[0086] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0087] 1>else if this uplink grant is a configured uplink grant:

[0088] 2>if there is no overlapping PUSCH duration of another configureduplink grant,in the same BWP,whose priority is higher than the priority ofthe uplink grant;and

[0089] 2>if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI=1or C-RNTI,in the same BWP,whose priority is higher than or equal to the priority of the uplink grant; and

[0090] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0091] 3>this uplink grant is a prioritized uplink grant;

[0092] 3>the other overlapping uplink grant(s), if any, is a de-prioritized uplink grant.

[0093] Combining RAN2 38.321 protocol and the above Figure 1 As shown, for the case of partial resource conflict, such as case 2, some resources are not given / identified as priority resources, such as L3. The terminal device cannot group L3 resources for transmission. Moreover, even if L2 resources are given low priority, according to the conditions in the existing protocol, even if they are considered low priority resources, the low priority resources will still be used for comparison, and other resources (such as L3) will be deprioritized.

[0094] like Figure 2As shown, it is a system architecture diagram applied in an embodiment of the present invention. The system architecture may include network equipment and terminal equipment. Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0095] The terminal equipment can be referred to as user equipment (UE), mobile station (MS), mobile terminal, intelligent terminal equipment, etc. The terminal equipment can communicate with one or more core networks via a radio access network (RAN). For example, the terminal equipment can be a mobile phone (or "cellular" phone), a computer with a mobile terminal equipment, etc. The terminal equipment can also be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device and a terminal equipment in the future NR network, which exchanges voice or data with the radio access network. Description of the terminal equipment: In the present invention, the terminal equipment can also include a relay, and any terminal equipment that can communicate data with the base station can be regarded as a terminal equipment.

[0096] In the embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison mode, for each uplink authorization, the uplink authorization is compared with the compared resource to avoid unnecessary resource transmission blocking and ensure priority resource transmission.

[0097] like Figure 3A FIG. 1 is a schematic diagram of an embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention, which may include:

[0098] 301A. When the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization.

[0099] Wherein, step 301A can be replaced by step 301B, and step 301B is: when the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization that is not or is not yet a low priority, or for each uplink authorization, the priority after the update is higher than the priority before the update, or for each uplink authorization that is not or is not yet a low priority and the priority after the update is higher than the priority before the update. Figure 3B FIG. 1 is a schematic diagram of an embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention.

[0100] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource. It should be noted that the target uplink resource can be one or more, and there is no specific limitation.

[0101] It is understandable that the "is not or is not yet" that appears in the embodiments of the present invention can also be expressed as "is not considered to be or is not considered to be yet". The target priority comparison method can be based on the logical channel priority comparison method (Logical Channel-based Prioritization, LCH-based Prioritization), or it can be based on the physical channel priority comparison method, which is not limited here. The following is an example of a MAC entity configured with LCH-based Prioritization.

[0102] 302. Perform a priority comparison between the uplink grant and the compared resources.

[0103] It can be understood that the compared resource is an uplink resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict. The compared resource is not or is not yet a low-priority uplink resource.

[0104] Optionally, before step 301A (or 301B) or 302, the terminal device may initialize the uplink authorization to a specific type of uplink resource.

[0105] Optionally, the terminal device performs a priority comparison between the uplink authorization and the compared resources, which may include: when the priority comparison between the uplink authorization and the compared resources is performed, considering the uplink authorization to be a specific type of uplink resource.

[0106] Further, in the case where the uplink grant is compared with the compared resource in priority, the uplink grant is considered to be the specific type of uplink resource, which may include but is not limited to the following implementations:

[0107] (1) before the uplink grant is compared with the compared resource, the uplink grant is considered to be the specific type of uplink resource; or

[0108] (2) After the uplink grant is compared with the compared resource, the uplink grant is considered to be the specific type of uplink resource. Based on this, after the uplink grant is compared with the compared resource, if the uplink grant is not given or is not considered or has not been given a type, the uplink grant is considered to be the specific type of uplink resource.

[0109] It can be understood that the specific type of uplink resource is a priority uplink resource or a low priority uplink resource. Among them, the preferred method is considered to be the priority uplink resource.

[0110] Further, the uplink grant is compared with the compared resource in priority, which may include but is not limited to the following situations:

[0111] (1) If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant;

[0112] If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and,

[0113] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0114] The uplink authorization is a priority uplink authorization;

[0115] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0116] Optionally, in this case, at least one of the first configured uplink authorization, the SR, and the PUCCH resources is not or is not yet a low-priority uplink resource.

[0117] (2) If the uplink grant is a configuration uplink grant;

[0118] If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and,

[0119] If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and,

[0120] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0121] The uplink authorization is a priority uplink authorization;

[0122] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0123] Optionally, in this case, at least one of the second configured uplink grant, the first target uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0124] Exemplarily, when the MAC entity is configured with LCH-basedPrioritization, for each uplink grant; or, when the MAC entity is configured with LCH-basedPrioritization, for each uplink grant that has not been considered as a low priority, or, the priority of each uplink grant becomes higher than the priority of the uplink grant that overlaps with it, or, for each uplink grant that has not been considered as a low priority and the priority of the uplink grant becomes higher than the priority of the uplink grant that overlaps with it:

[0125] 1> If the uplink grant is CS-RNTI scrambled and NDI = 1, or C-RNTI scrambled:

[0126] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0127] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0128] 3>This uplink authorization is the priority uplink authorization;

[0129] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0130] 1> If the uplink authorization is a configuration uplink authorization:

[0131] 2> If there is no overlap with the PUSCH duration of another configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0132] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant; and,

[0133] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0134] 3>This uplink authorization is the priority uplink authorization;

[0135] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0136] Understandably, the corresponding English translation is:

[0137] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant, or, or each uplink grant which is not already a de-prioritized uplink grant or whose priority is changed higher than theoverlapping uplink grant(s):

[0138] 1>if this uplink grant is addressed to CS-RNTI with NDI=1or C-RNTI:

[0139] 2>if there is no overlapping PUSCH duration of a configured uplink grant,in the same BWP whose priority is higher than the priority of the uplink grant; and

[0140] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0141] 3>this uplink grant is a prioritized uplink grant;

[0142] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0143] 1>else if this uplink grant is a configured uplink grant:

[0144] 2>if there is no overlapping PUSCH duration of another configureduplink grant,in the same BWP,whose priority is higher than the priority ofthe uplink grant;and

[0145] 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI=1or C-RNTI,in the same BWP,whose priority ishigher than or equal to the priority of the uplink grant;and

[0146] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0147] 3>this uplink grant is a prioritized uplink grant;

[0148] 3>the other overlapping uplink grant(s), if any, is a de-prioritized uplink grant.

[0149] Optionally, in some embodiments of the present invention, the following is an explanation of whether the terminal device considers the SR or the PUCCH resource transmitting the SR as a priority uplink resource or a low priority uplink resource. As shown below:

[0150] (1) The terminal device considers the SR or the PUCCH resource transmitting the SR as a priority uplink resource.

[0151] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource;

[0152] Condition 1: no overlap with other uplink resources; Condition 2: overlap with other uplink resources, and the priority of the logical channel triggering the SR is higher than the priority of other uplink resources; Condition 3: overlap with other uplink resources, and the priority of the PUCCH resources transmitting the SR is higher than the priority of other uplink resources; Condition 4: overlap with other uplink resources, the priority of the logical channel triggering the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources; and, Condition 5: overlap with other uplink resources, the priority of the PUCCH resources transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources.

[0153] (2) The terminal device considers the SR or the PUCCH resource transmitting the SR as a low-priority uplink resource.

[0154] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a low priority uplink resource;

[0155] Condition 1: Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources; Condition 2: Overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources; Condition 3: Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not considered to be low-priority uplink resources; and, Condition 4: Overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not yet low-priority uplink resources.

[0156] Optionally, the SR or the PUCCH resource for transmitting the SR is configured as the target priority comparison method, wherein the target priority comparison method may be based on a logical channel priority comparison method.

[0157] 303. Perform uplink transmission according to the specific type of uplink resource.

[0158] The terminal device performs uplink transmission according to the specific type of uplink resource, which may include but is not limited to the following transmission methods: if the specific type of uplink resource is a priority uplink resource, the specific type of uplink resource is transmitted; and / or, if the specific type of uplink resource is a low priority uplink resource, the specific type of uplink resource is not transmitted. It should be noted that step 303 is an optional step.

[0159] In an embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison mode, for each uplink authorization, the uplink authorization is compared with the compared resource. That is, the conditions for the compared resource to enter the comparison judgment are removed, or the conditions for the compared resource to enter the comparison judgment are added to ensure that the subsequent priority of the compared resource changes, such as becoming higher (for example, due to the arrival of data of a higher priority LCH in the LCH that can be carried on the compared resource K, resulting in a higher priority of K, higher than other conflicting resources), resulting in a change in the resource comparison result, so as to ensure that after the priority of the compared resource K becomes higher, higher priority data can be transmitted.

[0160] like Figure 4FIG. 2 is a schematic diagram of another embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention, which may include:

[0161] 401. When the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization.

[0162] Optionally, in some embodiments of the present invention, the uplink grant is not or is not yet a low-priority uplink grant; or,

[0163] The priority of the uplink grant after the update is higher than the priority before the update; or,

[0164] The uplink grant is not or is not yet a low-priority uplink grant, and the priority of the uplink grant after updating is higher than the priority before updating.

[0165] It is understandable that the "is not or is not yet" that appears in the embodiments of the present invention can also be expressed as "is not considered to be or is not considered to be yet". The target priority comparison method can be LCH-based Prioritization, or it can be based on the physical channel priority comparison method, which is not limited here. The following is an example of a MAC entity configured with LCH-based Prioritization.

[0166] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource. It should be noted that the target uplink resource can be one or more, and there is no specific limitation.

[0167] 402. Consider the uplink grant as a specific type of uplink resource.

[0168] Before the terminal device compares the uplink authorization with the compared resource, the terminal device considers the uplink authorization to be the specific type of uplink resource. It is understandable that the specific type of uplink resource is a priority uplink resource or a low priority uplink resource. Among them, the preferred method is to consider the priority uplink resource.

[0169] 403. Perform a priority comparison between the uplink grant and the compared resources.

[0170] It can be understood that the compared resource is an uplink resource that overlaps or partially overlaps or has a transmission conflict with the uplink grant. Further, the compared resource is not or is not yet a low-priority uplink resource.

[0171] Further, the uplink grant is compared with the compared resource in priority, which can be referred to Figure 3Aor Figure 3B The description in step 302 is not repeated here.

[0172] For example, each uplink grant that has not been considered as a low priority is used as an example for explanation:

[0173] When the MAC entity is configured with LCH-basedPrioritization, for each uplink grant that has not yet been considered as low priority:

[0174] The uplink authorization is considered to be a priority uplink resource;

[0175] 1> If the uplink grant is CS-RNTI scrambled and NDI = 1, or C-RNTI scrambled:

[0176] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0177] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0178] 3>This uplink authorization is the priority uplink authorization;

[0179] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0180] 1> If the uplink authorization is a configuration uplink authorization:

[0181] 2> If there is no overlap with the PUSCH duration of another configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0182] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant; and,

[0183] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0184] 3>This uplink authorization is the priority uplink authorization;

[0185] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0186] Understandably, the corresponding English translation is:

[0187] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant which is not already a de-prioritized uplink grant:

[0188] consider this uplink grant is a prioritized uplink grant;

[0189] 1>if this uplink grant is addressed to CS-RNTI with NDI=1or C-RNTI:

[0190] 2>if there is no overlapping PUSCH duration of a configured uplinkgrant,in the same BWP whose priority is higher than the priority of theuplink grant;and

[0191] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0192] 3>this uplink grant is a prioritized uplink grant;

[0193] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0194] 1>else if this uplink grant is a configured uplink grant:

[0195] 2>if there is no overlapping PUSCH duration of another configured uplink grant,in the same BWP,whose priority is higher than the priority of the uplink grant; and

[0196] 2>if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI=1or C-RNTI,in the same BWP,whose priority is higher than or equal to the priority of the uplink grant; and

[0197] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0198] 3>this uplink grant is a prioritized uplink grant;

[0199] 3>the other overlapping uplink grant(s), if any, is a de-prioritized uplink grant.

[0200] Optionally, in some embodiments of the present invention, for a description of whether the terminal device considers the SR or the PUCCH resource for transmitting the SR as a priority uplink resource or a low priority uplink resource, refer to Figure 3A or Figure 3B The description in step 302 is not repeated here.

[0201] 404. Perform uplink transmission according to the specific type of uplink resource.

[0202] It should be noted that step 404 can refer to Figure 3A or Figure 3B Step 303 described in the above will not be repeated here, and step 404 is an optional step.

[0203] In an embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison method, for each uplink grant, the uplink grant is considered to be a specific type of uplink resource; and the uplink grant is compared with the compared resource in priority. That is, for each uplink grant, before making a resource priority comparison, it is considered to be a specific type of uplink resource. Furthermore, the specific type of uplink resource can be a prioritized uplink resource or a deprioritized uplink resource.

[0204] like Figure 5 FIG. 2 is a schematic diagram of another embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention, which may include:

[0205] 501. Initialize the uplink grant to a specific type of uplink resource.

[0206] When the media access control MAC entity is configured with a target priority comparison mode, for each uplink grant, it is considered that the uplink grant is initialized as a specific type of uplink resource.

[0207] Optionally, the uplink authorization is not or is not yet a low-priority uplink authorization; or,

[0208] The priority of the uplink grant after the update is higher than the priority before the update; or,

[0209] The uplink grant is not or is not yet a low-priority uplink grant, and the priority of the uplink grant after updating is higher than the priority before updating.

[0210] It can be understood that the “is not or is not yet” that appears in the embodiments of the present invention can also be expressed as “is not considered to be or is not considered to be yet”.

[0211] 502. When the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization.

[0212] The target priority comparison method may be LCH-based Prioritization or may be based on a physical channel priority comparison method, which is not limited here. The following description is made by taking the MAC entity configured with LCH-based Prioritization as an example.

[0213] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource. It should be noted that the target uplink resource can be one or more, and there is no specific limitation.

[0214] 503. Perform a priority comparison between the uplink grant and the compared resources.

[0215] It can be understood that the compared resource is an uplink resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict. Further, the compared resource is not or is not yet a low-priority uplink resource.

[0216] Further, the uplink grant is compared with the compared resource in priority, which can be referred to Figure 3A or Figure 3B The description in step 302 is not repeated here.

[0217] For example, each uplink grant that has not been considered as a low priority is used as an example for explanation:

[0218] When the MAC entity is configured with LCH-based Prioritization, for each uplink grant, this uplink grant is initially considered as a prioritized uplink grant;

[0219] When the MAC entity is configured with LCH-basedPrioritization, for each uplink grant that has not yet been considered as low priority:

[0220] 1> If the uplink grant is CS-RNTI scrambled and NDI = 1, or C-RNTI scrambled:

[0221] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0222] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0223] 3>This uplink authorization is the priority uplink authorization;

[0224] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0225] 1> If the uplink authorization is a configuration uplink authorization:

[0226] 2> If there is no overlap with the PUSCH duration of another configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0227] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant; and,

[0228] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0229] 3>This uplink authorization is the priority uplink authorization;

[0230] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0231] Understandably, the corresponding English translation is:

[0232] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant, the uplink grant is initialized considered as a prioritizeduplink grant.

[0233] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant which is not already a de-prioritized uplink grant:

[0234] 1>if this uplink grant is addressed to CS-RNTI with NDI=1or C-RNTI:

[0235] 2>if there is no overlapping PUSCH duration of a configured uplink grant,in the same BWP whose priority is higher than the priority of the uplink grant; and

[0236] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0237] 3>this uplink grant is a prioritized uplink grant;

[0238] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0239] 1>else if this uplink grant is a configured uplink grant:

[0240] 2>if there is no overlapping PUSCH duration of another configureduplink grant,in the same BWP,whose priority is higher than the priority ofthe uplink grant;and

[0241] 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI=1or C-RNTI,in the same BWP,whose priority ishigher than or equal to the priority of the uplink grant;and

[0242] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0243] 3>this uplink grant is a prioritized uplink grant;

[0244] 3>the other overlapping uplink grant(s), if any, is a de-prioritized uplink grant.

[0245] Optionally, in some embodiments of the present invention, for a description of whether the terminal device considers the SR or the PUCCH resource for transmitting the SR as a priority uplink resource or a low priority uplink resource, refer to Figure 3A or Figure 3B The description in step 302 is not repeated here.

[0246] 504. Perform uplink transmission according to the specific type of uplink resource.

[0247] It should be noted that step 504 can refer to Figure 3A or Figure 3B Step 303 described in the above will not be repeated here, and step 504 is an optional step.

[0248] In an embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison method, for each uplink grant, the uplink grant is considered to be a specific type of uplink resource; and the uplink grant is compared with the compared resource in priority. That is, for each uplink grant, before making a resource priority comparison, it is considered to be a specific type of uplink resource. Furthermore, the specific type of uplink resource can be a prioritized uplink resource or a deprioritized uplink resource.

[0249] like Figure 6 FIG. 2 is a schematic diagram of another embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention, which may include:

[0250] 601. When the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization.

[0251] Optionally, in some embodiments of the present invention, the uplink grant is not or is not yet a low-priority uplink grant; or,

[0252] The priority of the uplink grant after the update is higher than the priority before the update; or,

[0253] The uplink grant is not or is not yet a low-priority uplink grant, and the priority of the uplink grant after updating is higher than the priority before updating.

[0254] It is understandable that the "is not or is not yet" that appears in the embodiments of the present invention can also be expressed as "is not considered to be or is not considered to be yet". The target priority comparison method can be LCH-based Prioritization, or it can be based on the physical channel priority comparison method, which is not limited here. The following is an example of a MAC entity configured with LCH-based Prioritization.

[0255] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource. It should be noted that the target uplink resource can be one or more, and there is no specific limitation.

[0256] 602. Perform a priority comparison between the uplink grant and the compared resources.

[0257] It can be understood that the compared resource is an uplink resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict. Further, the compared resource is not or is not yet a low-priority uplink resource.

[0258] Further, the uplink grant is compared with the compared resource in priority, which can be referred to Figure 3A or Figure 3B The description in step 302 is not repeated here.

[0259] 603. Consider the uplink grant as a specific type of uplink resource.

[0260] Based on this, after the terminal device compares the priority of the uplink authorization with the compared resource, if the uplink authorization is not given or is not considered or has not been given a type, the uplink authorization is considered to be the specific type of uplink resource. It can be understood that the specific type of uplink resource is a priority uplink resource or a low priority uplink resource. Among them, the preferred method is considered to be a priority uplink resource.

[0261] For example, each uplink grant that has not been considered as a low priority is used as an example for explanation:

[0262] When the MAC entity is configured with LCH-basedPrioritization, for each uplink grant that has not yet been considered as low priority:

[0263] 1> If the uplink grant is CS-RNTI scrambled and NDI = 1, or C-RNTI scrambled:

[0264] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0265] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0266] 3>This uplink authorization is the priority uplink authorization;

[0267] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0268] 1> If the uplink authorization is a configuration uplink authorization:

[0269] 2> If there is no overlap with the PUSCH duration of another configured uplink grant on the same BWP with a higher priority than this uplink grant; and,

[0270] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant; and,

[0271] 2> If there is no overlap with the PUCCH resources of an SR transmission, the priority of the logical channel triggering the SR is higher than the priority of this uplink grant:

[0272] 3>This uplink authorization is the priority uplink authorization;

[0273] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0274] When the MAC entity is configured with LCH-based Prioritization, for each uplink grant, if it has not been considered as a priority resource or a low priority resource, the uplink grant is considered as a priority uplink resource.

[0275] It can be understood that the corresponding English translation is:

[0276] 当MAC实体配置了基于lch的优先级时,对于每个尚未被降优先级的上行链路授权:

[0277] 1>如果此上行链路授权是针对NDI=1的CS-RNTI或C-RNTI:

[0278] 2>如果在优先级高于该上行链路授权的同一BWP中,不存在配置的上行链路授权的重叠PUSCH持续时间;并且

[0279] 2>如果不存在与触发SR的逻辑信道优先级高于该上行链路授权的SR传输的重叠PUCCH资源:

[0280] 3>此上行链路授权是一个优先级上行链路授权;

[0281] 3>其他重叠的上行链路授权(如果有)是降优先级的上行链路授权。

[0282] 1>否则,如果此上行链路授权是配置的上行链路授权:

[0283] 2>if there is no overlapping PUSCH duration of another configureduplink grant,in the same BWP,whose priority is higher than the priority ofthe uplink grant;and

[0284] 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI=1or C-RNTI,in the same BWP,whose priority ishigher than or equal to the priority of the uplink grant;and

[0285] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant:

[0286] 3>this uplink grant is a prioritized uplink grant;

[0287] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0288] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant,the uplink grant is considered as a prioritized uplinkgrant if it has not been prioritized or deprioritized.

[0289] Optionally, in some embodiments of the present invention, for a description of whether the terminal device considers the SR or the PUCCH resource for transmitting the SR as a priority uplink resource or a low priority uplink resource, refer to Figure 3A or Figure 3B The description in step 302 is not repeated here.

[0290] 604. Perform uplink transmission according to the specific type of uplink resource.

[0291] It should be noted that step 604 can refer to Figure 3A or Figure 3B Step 303 described in the above will not be repeated here, and step 604 is an optional step.

[0292] In an embodiment of the present invention, when the media access control MAC entity is configured with a target priority comparison method, for each uplink grant, the uplink grant is considered to be a specific type of uplink resource; and the uplink grant is compared with the compared resource in priority. That is, for each uplink grant, after making a resource priority comparison, if the resource is not considered to be a prioritized uplink resource or a deprioritized uplink resource, the resource is considered to be a specific type of uplink resource. Furthermore, the specific type of uplink resource can be a prioritized uplink resource or a deprioritized uplink resource.

[0293] like Figure 7 FIG. 2 is a schematic diagram of another embodiment of a method for handling multiple resource conflicts in an embodiment of the present invention, which may include:

[0294] 701. When the media access control MAC entity is configured with a target priority comparison method, for each uplink authorization.

[0295] Optionally, in some embodiments of the present invention, the uplink grant is not or is not yet a low-priority uplink grant; or,

[0296] The priority of the uplink grant after the update is higher than the priority before the update; or,

[0297] The uplink grant is not or is not yet a low-priority uplink grant, and the priority of the uplink grant after updating is higher than the priority before updating.

[0298] It is understandable that the "is not or is not yet" that appears in the embodiments of the present invention can also be expressed as "is not considered to be or is not considered to be yet". The target priority comparison method can be LCH-based Prioritization, or it can be based on the physical channel priority comparison method, which is not limited here. The following is an example of a MAC entity configured with LCH-based Prioritization.

[0299] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource. It should be noted that the target uplink resource can be one or more, and there is no specific limitation.

[0300] 702. Perform a priority comparison between the uplink grant and the compared resource, where the compared resource is not or is not yet a low-priority uplink resource.

[0301] It can be understood that the compared resources are uplink resources that overlap or partially overlap with the uplink grant or have transmission conflicts.

[0302] Optionally, before step 701 or 702, the terminal device may initialize the uplink authorization to a specific type of uplink resource.

[0303] Optionally, the terminal device performs a priority comparison between the uplink authorization and the compared resources, which may include: when the priority comparison between the uplink authorization and the compared resources is performed, considering the uplink authorization to be a specific type of uplink resource.

[0304] Further, in the case where the uplink grant is compared with the compared resource in priority, the uplink grant is considered to be the specific type of uplink resource, which may include but is not limited to the following implementations:

[0305] (1) before the uplink grant is compared with the compared resource, the uplink grant is considered to be the specific type of uplink resource; or

[0306] (2) After comparing the priorities of the uplink grant and the compared resources, the uplink grant is considered to be the specific type of uplink resource.

[0307] It can be understood that the specific type of uplink resource is a priority uplink resource or a low priority uplink resource. Among them, the preferred method is considered to be the priority uplink resource.

[0308] Further, the uplink grant is compared with the compared resource in priority, which may include but is not limited to the following situations:

[0309] (1) If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant;

[0310] If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and,

[0311] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0312] The uplink authorization is a priority uplink authorization;

[0313] If there is an overlapping uplink authorization, the overlapping uplink authorization is a low priority uplink authorization;

[0314] Among them, at least one of the first configured uplink grant, the SR, and the PUCCH resource is not or is not yet a low-priority uplink resource.

[0315] (2) If the uplink grant is a configuration uplink grant;

[0316] If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and,

[0317] If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and,

[0318] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0319] The uplink authorization is a priority uplink authorization;

[0320] If there is an overlapping uplink authorization, the overlapping uplink authorization is a low priority uplink authorization;

[0321] Among them, at least one of the second configured uplink grant, the first target uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0322] For example, each uplink grant that has not been considered as a low priority is used as an example for explanation:

[0323] When the MAC entity is configured with lch-basedPrioritization, for each uplink grant that has not been considered as low priority:

[0324] 1> If the uplink grant is CS-RNTI scrambled and NDI = 1, or C-RNTI scrambled:

[0325] 2> If there is no overlap with the PUSCH duration of a configured uplink grant on the same BWP with a higher priority than this uplink grant, and this configured grant is not a low priority uplink resource; and,

[0326] 2> If there is no overlap with the PUCCH resource of an SR transmission, where the priority of the logical channel triggering the SR is higher than the priority of the uplink grant, and the PUCCH resource is not a low priority resource:

[0327] 3>This uplink authorization is the priority uplink authorization;

[0328] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0329] 1> If the uplink authorization is a configuration uplink authorization:

[0330] 2> If there is no PUSCH duration overlap with another configured uplink grant on the same BWP with a higher priority than this uplink grant, and the other configured grant is not a low priority uplink resource; and,

[0331] 2> If there is no PUSCH duration overlap with a CS-RNTI scrambled uplink grant with NDI=1 or C-RNTI scrambled uplink grant on the same BWP with a higher priority than or equal to this uplink grant, and the overlapping uplink resource is not a low priority uplink resource; and,

[0332] 2> If there is no overlap with the PUCCH resource of an SR transmission, where the priority of the logical channel triggering the SR is higher than the priority of the uplink grant, and the PUCCH resource is not a low-priority resource:

[0333] 3>This uplink authorization is the priority uplink authorization;

[0334] 3> If there are overlapping uplink authorizations, the overlapping uplink authorizations shall be the lower priority uplink authorizations.

[0335] Understandably, the corresponding English translation is:

[0336] When the MAC entity is configured,with lch-basedPrioritization,foreach uplink grant which is not already a de-prioritized uplink grant:

[0337] 1>if this uplink grant is addressed to CS-RNTI with NDI=1or C-RNTI:

[0338] 2>if there is no overlapping PUSCH duration of a configured uplink grant which is not adeprioritized uplink grant,in the same BWP,and the priority of the overlapping configured uplink grant is higher than the priority of the uplink grant; and

[0339] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant,and the overlapping PUCCH resource withan SR transmission is not deprioritized:

[0340] 3>this uplink grant is a prioritized uplink grant;

[0341] 3>the other overlapping uplink grant(s),if any,is a de-prioritizeduplink grant.

[0342] 1>else if this uplink grant is a configured uplink grant:

[0343] 2>if there is no overlapping PUSCH duration of another configureduplink grant which is not a deprioritized uplink grant,in the same BWP,andthe priority of the overlapping configured uplink grant is higher than thepriority of the uplink grant;and

[0344] 2>if there is no overlapping PUSCH duration of an uplink grantaddressed to CS-RNTI with NDI=1or C-RNTI,which is not a deprioritized uplinkgrant in the same BWP,and the priority of the overlapping uplink grant ishigher than or equal to the priority of the uplink grant;and

[0345] 2>if there is no overlapping PUCCH resource with an SR transmissionwhere the priority of the logical channel that triggered the SR is higherthan the priority of the uplink grant,and the overlapping PUCCH resource withan SR transmission is not deprioritized:

[0346] 3>this uplink grant is a prioritized uplink grant;

[0347] 3>the other overlapping uplink grant(s), if any, is a de-prioritized uplink grant.

[0348] Optionally, in some embodiments of the present invention, the following is an explanation of whether the terminal device considers the SR or the PUCCH resource transmitting the SR as a priority uplink resource or a low priority uplink resource. As shown below:

[0349] (1) The terminal device considers the SR or the PUCCH resource transmitting the SR as a priority uplink resource.

[0350] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource;

[0351] Condition 1: no overlap with other uplink resources; Condition 2: overlap with other uplink resources, and the priority of the logical channel triggering the SR is higher than the priority of other uplink resources; Condition 3: overlap with other uplink resources, and the priority of the PUCCH resources transmitting the SR is higher than the priority of other uplink resources; Condition 4: overlap with other uplink resources, the priority of the logical channel triggering the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources; and, Condition 5: overlap with other uplink resources, the priority of the PUCCH resources transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources.

[0352] (2) The terminal device considers the SR or the PUCCH resource transmitting the SR as a low-priority uplink resource.

[0353] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a low priority uplink resource;

[0354] Condition 1: Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources; Condition 2: Overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources; Condition 3: Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not considered to be low-priority uplink resources; and, Condition 4: Overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not yet low-priority uplink resources.

[0355] Optionally, the SR or the PUCCH resource for transmitting the SR is configured as the target priority comparison method, wherein the target priority comparison method may be based on a logical channel priority comparison method.

[0356] 703. Perform uplink transmission according to the specific type of uplink resource.

[0357] It should be noted that step 703 can refer to Figure 3A or Figure 3B Step 303 described in the above will not be repeated here, and step 703 is an optional step.

[0358] In the embodiment of the present invention, when comparing resource priorities, the compared resources are only compared with resources that have not been considered as deprioritized. The compared resources include UL resources. For example, if resource A does not overlap with a resource that has a higher priority than resource A and has not been considered as deprioritized, resource A is a prioritized resource, and other resources that overlap with it are deprioritized resources.

[0359] like Figure 8 FIG. 1 is a schematic diagram of an embodiment of a terminal device in an embodiment of the present invention, which may include:

[0360] Processing module 801 is used to compare the priority of the uplink authorization with the compared resource for each uplink authorization when the media access control MAC entity is configured with a target priority comparison mode.

[0361] Optionally, in some embodiments of the present invention, the processing module 801 is further configured to initialize the uplink grant to a specific type of uplink resource.

[0362] Optionally, in some embodiments of the present invention, the processing module 801 is specifically configured to consider the uplink authorization as a specific type of uplink resource when a priority comparison is performed between the uplink authorization and the compared resource.

[0363] Optionally, in some embodiments of the present invention,

[0364] The processing module 801 is specifically configured to consider the uplink grant as the specific type of uplink resource before performing a priority comparison between the uplink grant and the compared resource; or

[0365] The processing module 801 is specifically configured to consider the uplink grant as the specific type of uplink resource after performing a priority comparison between the uplink grant and the compared resource.

[0366] Optionally, in some embodiments of the present invention, the specific type of uplink resource is a priority uplink resource or a low priority uplink resource.

[0367] Optionally, in some embodiments of the present invention, the compared resource is not or is not yet a low-priority uplink resource.

[0368] Optionally, in some embodiments of the present invention, the processing module 801 is specifically configured to:

[0369] If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant;

[0370] If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and,

[0371] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0372] The uplink authorization is a priority uplink authorization;

[0373] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0374] Optionally, in some embodiments of the present invention, at least one of the first configured uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0375] Optionally, in some embodiments of the present invention, the processing module 801 is specifically configured to:

[0376] If the uplink authorization is a configuration uplink authorization;

[0377] If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and,

[0378] If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and,

[0379] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0380] The uplink authorization is a priority uplink authorization;

[0381] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0382] Optionally, in some embodiments of the present invention, at least one of the second configured uplink grant, the first target uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0383] Optionally, in some embodiments of the present invention, the processing module 801 is further configured to:

[0384] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource;

[0385] No overlap with other uplink resources; overlap with other uplink resources, and the priority of the logical channel triggering the SR is higher than the priority of other uplink resources; overlap with other uplink resources, and the priority of the PUCCH resources transmitting the SR is higher than the priority of other uplink resources; overlap with other uplink resources, the priority of the logical channel triggering the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources; and overlap with other uplink resources, the priority of the PUCCH resources transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources.

[0386] Optionally, in some embodiments of the present invention, the processing module 801 is further configured to:

[0387] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a low priority uplink resource;

[0388] Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources; overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources; overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not considered to be low-priority uplink resources; and overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not yet low-priority uplink resources.

[0389] Optionally, in some embodiments of the present invention,

[0390] The uplink authorization includes: an uplink authorization that is not or is not yet a low priority; or,

[0391] The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or,

[0392] The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

[0393] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource.

[0394] Optionally, in some embodiments of the present invention, the processing module 801 is further configured to perform uplink transmission according to the specific type of uplink resource.

[0395] Optionally, in some embodiments of the present invention,

[0396] The processing module 801 is specifically configured to transmit the uplink resource of the specific type if the uplink resource of the specific type is a priority uplink resource; and / or,

[0397] The processing module 801 is specifically configured to not transmit the specific type of uplink resource if the specific type of uplink resource is a low priority uplink resource.

[0398] Optionally, in some embodiments of the present invention, the target priority comparison method includes: a logical channel priority comparison method.

[0399] like Fig. 9 As shown, it is a schematic diagram of another embodiment of the terminal device in the embodiment of the present invention, taking a mobile phone as an example for explanation, which may include: radio frequency (RF) circuit 910, memory 920, input unit 930, display unit 940, sensor 950, audio circuit 960, wireless fidelity (WiFi) module 970, processor 980, and power supply 990 and other components. Among them, the RF circuit 910 includes a receiver 914 and a transmitter 912. Those skilled in the art can understand that Fig. 9 The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0400] Combine the following Fig. 9 A detailed introduction to the various components of the mobile phone:

[0401] The RF circuit 910 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 980 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 910 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF circuit 910 can also communicate with the network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to the global system of mobile communication (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), long term evolution (LTE), email, short messaging service (SMS), etc.

[0402] The memory 920 can be used to store software programs and modules. The processor 980 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 920. The memory 920 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 920 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0403] The input unit 930 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 930 may include a touch panel 931 and other input devices 932. The touch panel 931, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 931 or near the touch panel 931 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 931 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 980, and can receive and execute commands sent by the processor 980. In addition, the touch panel 931 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 931, the input unit 930 may further include other input devices 932. Specifically, the other input devices 932 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc.

[0404] The display unit 940 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 940 may include a display panel 941. Optionally, the display panel 941 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 931 may cover the display panel 941. When the touch panel 931 detects a touch operation on or near it, it is transmitted to the processor 980 to determine the type of touch event. Subsequently, the processor 980 provides a corresponding visual output on the display panel 941 according to the type of touch event. Although in Fig. 9 In the embodiment, the touch panel 931 and the display panel 941 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 931 and the display panel 941 can be integrated to realize the input and output functions of the mobile phone.

[0405] The mobile phone may also include at least one sensor 950, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 941 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 941 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0406] The audio circuit 960, the speaker 961, and the microphone 962 can provide an audio interface between the user and the mobile phone. The audio circuit 960 can transmit the received audio data to the speaker 961 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 962 converts the collected sound signal into an electrical signal, which is received by the audio circuit 960 and converted into audio data, and then the audio data is output to the processor 980 for processing, and then sent to another mobile phone through the RF circuit 910, or the audio data is output to the memory 920 for further processing.

[0407] WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the WiFi module 970. It provides users with wireless broadband Internet access. Fig. 9 A WiFi module 970 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0408] The processor 980 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 920, and calling data stored in the memory 920, it executes various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 980.

[0409] The mobile phone also includes a power supply 990 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 980 through a power management system, so that the power management system can manage charging, discharging, and power consumption management. Although not shown, the mobile phone can also include a camera, a Bluetooth module, etc., which will not be repeated here.

[0410] In the embodiment of the present invention, the processor 980 is used to compare the priority of the uplink authorization with the compared resource for each uplink authorization when the media access control MAC entity is configured with a target priority comparison mode.

[0411] Optionally, in some embodiments of the present invention, the processor 980 is further configured to initialize the uplink grant to a specific type of uplink resource.

[0412] Optionally, in some embodiments of the present invention, the processor 980 is specifically configured to consider the uplink authorization as a specific type of uplink resource when a priority comparison is performed between the uplink authorization and the compared resources.

[0413] Optionally, in some embodiments of the present invention,

[0414] The processor 980 is specifically configured to consider the uplink grant as the specific type of uplink resource before performing a priority comparison between the uplink grant and the compared resource; or,

[0415] The processor 980 is specifically configured to consider the uplink grant as the specific type of uplink resource after performing a priority comparison between the uplink grant and the compared resource.

[0416] Optionally, in some embodiments of the present invention, the specific type of uplink resource is a priority uplink resource or a low priority uplink resource.

[0417] Optionally, in some embodiments of the present invention, the compared resource is not or is not yet a low-priority uplink resource.

[0418] Optionally, in some embodiments of the present invention, the processor 980 is specifically configured to:

[0419] If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant;

[0420] If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and,

[0421] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0422] The uplink authorization is a priority uplink authorization;

[0423] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0424] Optionally, in some embodiments of the present invention, at least one of the first configured uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0425] Optionally, in some embodiments of the present invention, the processor 980 is specifically configured to:

[0426] If the uplink authorization is a configuration uplink authorization;

[0427] If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and,

[0428] If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and,

[0429] If the uplink grant does not overlap with the PUCCH resource of the SR transmission, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant;

[0430] The uplink authorization is a priority uplink authorization;

[0431] If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

[0432] Optionally, in some embodiments of the present invention, at least one of the second configured uplink grant, the first target uplink grant, the SR, and the PUCCH resource is not or is not yet a low priority uplink resource.

[0433] Optionally, in some embodiments of the present invention, the processor 980 is further configured to:

[0434] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource;

[0435] Does not overlap with other uplink resources; overlaps with other uplink resources, and the priority of the logical channel that triggers the SR is higher than the priority of other uplink resources; overlaps with other uplink resources, and the priority of the PUCCH resource that transmits the SR is higher than the priority of other uplink resources; overlaps with other uplink resources, the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources;

[0436] And, overlapping with other uplink resources, the priority of the PUCCH resource transmitting the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are considered to be low-priority uplink resources.

[0437] Optionally, in some embodiments of the present invention, the processor 980 is further configured to:

[0438] If the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison mode, and the SR or the PUCCH resource for transmitting the SR satisfies at least one of the following conditions, the SR or the PUCCH resource for transmitting the SR is considered to be a low priority uplink resource;

[0439] Overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources; overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources; overlapping with other uplink resources, and the priority of the logical channel that triggers the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not considered to be low-priority uplink resources; and overlapping with other uplink resources, and the priority of the PUCCH resources that transmit the SR is lower than or equal to the priority of other uplink resources, and the other uplink resources are not or are not yet low-priority uplink resources.

[0440] Optionally, in some embodiments of the present invention, the uplink authorization includes: not being or not yet being a low-priority uplink authorization; or,

[0441] The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or,

[0442] The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

[0443] Optionally, in some embodiments of the present invention, the priority of the uplink authorization before updating is lower than the priority of the target uplink resource that conflicts with the uplink authorization, and the priority of the uplink authorization after updating is higher than the priority of the target uplink resource.

[0444] Optionally, in some embodiments of the present invention, the processor 980 is further configured to perform uplink transmission according to the specific type of uplink resource.

[0445] Optionally, in some embodiments of the present invention,

[0446] The processor 980 is specifically configured to transmit the uplink resource of the specific type if the uplink resource of the specific type is a priority uplink resource; and / or,

[0447] The processor 980 is specifically configured to not transmit the specific type of uplink resource if the specific type of uplink resource is a low priority uplink resource.

[0448] Optionally, in some embodiments of the present invention, the target priority comparison method includes: a logical channel priority comparison method.

[0449] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0450] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

Claims

1. A method for handling multi-resource conflicts, characterized in that: include: When the media access control MAC entity is configured with a target priority comparison mode, wherein the target priority comparison mode includes a priority comparison based on a logical channel or a priority comparison based on a physical channel, for each uplink grant: comparing the priority of the uplink grant with the priority of the compared resource, The compared resource is a resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict, and the uplink grant is not or is not yet a low-priority uplink resource, The comparing between the priority of the uplink authorization and the priority of the compared resource includes: After comparing the priority of the uplink grant with the priority of the compared resource, the uplink grant is considered to be a low-priority uplink resource; The method also includes: if the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison method, and the SR or the PUCCH resource for transmitting the SR overlaps with other uplink resources, and the priority of the PUCCH resource for transmitting the SR is higher than the priority of other uplink resources, then the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource.

2. The method according to claim 1, characterized in that The comparing between the priority of the uplink authorization and the priority of the compared resource includes: If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant; If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

3. The method according to claim 1, characterized in that The comparing between the priority of the uplink authorization and the priority of the compared resource includes: If the uplink authorization is a configuration uplink authorization; If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and, If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

4. The method according to claim 1, characterized in that The uplink authorization includes: an uplink authorization that is not or is not yet a low priority; or, The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or, The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

5. A terminal device, characterized in that: include: A processing module, configured to, when a media access control MAC entity is configured with a target priority comparison mode, wherein the target priority comparison mode includes a priority comparison based on a logical channel or based on a physical channel, for each uplink authorization: compare the priority of the uplink authorization with the priority of the compared resource, The compared resource is a resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict, and the uplink grant is not or is not yet a low-priority uplink resource, The processing module is specifically configured to compare the priority of the uplink authorization with the priority of the compared resource and consider the uplink authorization to be a low-priority uplink resource, The processing module is also used for: if the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison method, and the SR or the PUCCH resource for transmitting the SR overlaps with other uplink resources, and the priority of the PUCCH resource for transmitting the SR is higher than the priority of other uplink resources, then the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource.

6. The terminal device according to claim 5, characterized in that: The processing module is specifically used for: If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant; If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

7. The terminal device according to claim 5, characterized in that: The processing module is specifically used for: If the uplink authorization is a configuration uplink authorization; If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and, If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

8. The terminal device according to claim 5, characterized in that: The uplink authorization includes: an uplink authorization that is not or is not yet a low priority; or, The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or, The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

9. A terminal device, characterized in that: include: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory, and is used to, when a media access control MAC entity is configured with a target priority comparison mode, wherein the target priority comparison mode includes a priority comparison based on a logical channel or based on a physical channel, for each uplink authorization: compare the priority of the uplink authorization with the priority of the compared resource, The compared resource is a resource that overlaps or partially overlaps with the uplink grant or has a transmission conflict, and the uplink grant is not or is not yet a low-priority uplink resource, The processor is specifically configured to compare the priority of the uplink authorization with the priority of the compared resource and consider the uplink authorization to be a low-priority uplink resource, The processor is also used for: if the configuration of the SR or the PUCCH resource for transmitting the SR is the target priority comparison method, and the SR or the PUCCH resource for transmitting the SR overlaps with other uplink resources, and the priority of the PUCCH resource for transmitting the SR is higher than the priority of other uplink resources, then the SR or the PUCCH resource for transmitting the SR is considered to be a priority uplink resource.

10. The terminal device according to claim 9, characterized in that: The processor is specifically used for: If the uplink grant is CS-RNTI scrambled and NDI=1, or C-RNTI scrambled uplink grant; If the PUSCH duration of the uplink grant does not overlap with that of the first configured uplink grant, wherein the first configured uplink grant and the uplink grant belong to the same BWP and the priority of the first configured uplink grant is higher than the priority of the uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

11. The terminal device according to claim 9, characterized in that: The processor is specifically used for: If the uplink authorization is a configuration uplink authorization; If the PUSCH duration of the uplink grant does not overlap with that of the second configured uplink grant, wherein the second configured uplink grant and the uplink grant belong to the same BWP and the priority of the second configured uplink grant is higher than the priority of the uplink grant; and, If the PUSCH duration of the uplink grant does not overlap with that of the first target uplink grant, wherein the first target uplink grant and the uplink grant belong to the same BWP, and the priority of the first target uplink grant is higher than or equal to the priority of the uplink grant, and the first target uplink grant is a CS-RNTI scrambled uplink grant with NDI=1, or a C-RNTI scrambled uplink grant; and, If the uplink grant does not overlap with the PUCCH resource for transmitting the SR, wherein the priority of the logical channel triggering the SR is higher than the priority of the uplink grant; The uplink authorization is a priority uplink authorization; If there is an overlapping uplink grant, the overlapping uplink grant is a low-priority uplink grant.

12. The terminal device according to claim 9, characterized in that: The uplink authorization includes: an uplink authorization that is not or is not yet a low priority; or, The uplink authorization includes: the priority of the uplink authorization after updating is higher than the priority before updating; or, The uplink authorization includes: an uplink authorization that is not or is not yet a low priority, and the priority of the uplink authorization after updating is higher than the priority before updating.

13. A computer-readable storage medium comprising instructions, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 4.

Images