Resource determination methods, communication node and storage medium

Abstract

Provided in the present application are resource determination methods, a communication node and a storage medium. A resource determination method comprises: determining resource configuration information, wherein the resource configuration information comprises an indication granularity of a timing advance of a target frame and / or the priority of transmission of resource types between which a collision has occurred, and the timing advance is indicated to a service node by a communication node by means of a timing advance field in a timing advance report; and on the basis of the resource configuration information, determining a transmission resource with respect to the service node.

Description

Resource determination method, communication node and storage medium Technical Field

[0001] The present application relates to the field of wireless communication technology, for example, to a resource determination method, a communication node, and a storage medium. Background Art

[0002] Wireless communication systems support scenarios with large transmission delays or high mobility, such as non-terrestrial networks (NTN). Due to the existence of large transmission delays, the timing advance (TA) at the user equipment (UE) may be very large, resulting in misalignment of uplink and downlink subframes. In order to cope with large transmission delays or high mobility, the UE may perform time synchronization through uplink pre-compensation. However, the network-side node may not know the UE's pre-compensation value, or the timing advance reported by the UE is inaccurate, making it impossible to accurately determine the deviation of the uplink and downlink subframes at the UE, resulting in conflicts between uplink and downlink resources, affecting the reliability of uplink and downlink transmission. Summary of the Invention

[0003] This application provides a resource determination method, a communication node, and a storage medium.

[0004] An embodiment of the present application provides a resource determination method, applied to a communication node, comprising:

[0005] Determine resource configuration information, the resource configuration information including an indication granularity of a timing advance of a target frame and / or a priority of transmission of a resource type in which a collision occurs, the timing advance being indicated to a service node by the communication node via a timing advance field in a timing advance report; and determine transmission resources with the service node based on the resource configuration information.

[0006] The embodiment of the present application further provides a resource determination method, which is applied to a service node and includes:

[0007] Determine resource configuration information, the resource configuration information including the indication granularity of the timing advance of the target frame and / or the priority of the transmission of the resource type in which the collision occurs, the timing advance being indicated to the service node by the communication node via the timing advance field in the timing advance report; determine the transmission resources with the communication node based on the resource configuration information.

[0008] An embodiment of the present application further provides a communication node, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned resource determination method when executing the program.

[0009] An embodiment of the present application further provides a service node, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned resource determination method when executing the program.

[0010] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the above-mentioned resource determination method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG1 is a schematic diagram of NTN communication provided by an embodiment;

[0012] FIG2 is a schematic diagram of a timing advance report based on MAC CE provided by an embodiment;

[0013] FIG3 is a flow chart of a resource determination method provided by an embodiment;

[0014] FIG4 is a schematic diagram of a resource collision provided by an embodiment;

[0015] FIG5 is a schematic diagram of another resource collision provided by an embodiment;

[0016] FIG6 is a schematic diagram of another resource collision provided by an embodiment;

[0017] FIG7 is a schematic diagram of another resource collision provided by an embodiment;

[0018] FIG8 is a schematic diagram of another resource collision provided by an embodiment;

[0019] FIG9 is a schematic diagram of another resource collision provided by an embodiment;

[0020] FIG10 is a schematic diagram of another resource collision provided by an embodiment;

[0021] FIG11 is a schematic diagram of another resource collision provided by an embodiment;

[0022] FIG12 is a schematic diagram of another resource collision provided by an embodiment;

[0023] FIG13 is a flowchart of another resource determination method provided by an embodiment;

[0024] FIG14 is a schematic structural diagram of a resource determination device provided by an embodiment;

[0025] FIG15 is a schematic structural diagram of another resource determination device provided by an embodiment;

[0026] FIG16 is a schematic diagram of the hardware structure of a communication node provided by an embodiment;

[0027] FIG17 is a schematic diagram of the hardware structure of a service node provided by an embodiment. DETAILED DESCRIPTION

[0028] The present application is described below in conjunction with the accompanying drawings and embodiments. The specific embodiments described herein are merely for illustrative purposes. Unless otherwise specified, the embodiments and features of the embodiments in this application may be combined with one another in any manner. For ease of description, only portions relevant to this application are shown in the accompanying drawings.

[0029] Figure 1 is a schematic diagram of NTN communications according to one embodiment. As shown in Figure 1 , in an NTN communication system, the link between a communication node (also known as a user-side device, such as a UE) and a satellite is a service link, while the link between a service node (also known as an access network device or network-side device, such as a base station, access point, or gateway) and the satellite is a feeder link. These links are common to all UEs within the same cell (e.g., UE1 and UEx shown in Figure 1 ). In this embodiment, the communication node can be a UE, and the service node can be a base station.

[0030] In an NTN, a UE can pre-compensate for its TA based on information such as satellite position, its own location, and the public TA. Since the UE's location is often unknown at the network node, the base station may not know the TA value at the UE. To enable more reliable and efficient scheduling at the network node, the UE can report its TA value.

[0031] In one scenario, the basic granularity of a Timing Advance Report (TAR) can be one time slot corresponding to a 15kHz subcarrier spacing, or 1ms. Therefore, there is an uncertain TA offset of approximately 1ms between the base station and the UE. Clearly, the base station has no idea of ​​the actual TA position within 1ms. To avoid collisions between downlink reception and uplink transmission, the base station often needs to adopt very conservative scheduling and reserve sufficient bandwidth, resulting in a waste of time and frequency resources.

[0032] In one scenario, the common TA from the satellite to the reference point (RP) is an integer between 0 and 66485757, with units of 4.072 × 10-3 μs, corresponding to 0 to 270.73 ms. Converted to 15 kHz symbols, this is approximately 270 * 12 = 3780 symbols. Therefore, the maximum round-trip time (RTT) from the UE to the reference point (RP) (for geostationary Earth Orbit (GEO) satellites) is approximately 540 ms. Converted to 15 kHz symbols, this is approximately 540 * 14 = 7560 symbols. Therefore, the maximum TA is approximately 7560 symbols.

[0033] Figure 2 is a schematic diagram of a timing advance report based on MAC CE provided by an embodiment. As shown in Figure 2, the number of bits used in the TA field in the TAR MAC CE is 14 bits, which is used to represent the duration of the TA, that is, the minimum number of slots greater than or equal to the TA value. If used to represent the number of symbols, the maximum representation is: 2 14 -1=16383 symbols, which is greater than 7560 symbols.

[0034] On this basis, the embodiments of the present application can further enhance the granularity of TAR, thereby solving the problem of timing misalignment between the base station side and the UE side caused by the coarse granularity of NTN TAR (for example, 1 time slot of 15kHz, that is, 1ms), and provide corresponding solutions when there is a conflict or collision between uplink and downlink resources.

[0035] FIG3 is a flowchart of a resource determination method provided by an embodiment. The method can be applied to a communication node, which can be a user-side device, such as a UE, or a lightweight (Reduced Capability, RedCap) UE. As shown in FIG3 , the method provided by this embodiment includes 110 and 120.

[0036] In 110, resource configuration information is determined, the resource configuration information including the indication granularity of the timing advance of the target frame and / or the priority of the colliding resource type transmission, the timing advance is indicated by the communication node to the service node via the timing advance field in the timing advance report.

[0037] In 120, transmission resources with the service node are determined according to the resource configuration information.

[0038] In this embodiment, the communication node can determine the indication granularity of the timing advance (also referred to as the granularity of TAR) based on the configuration or indication of the service node, or can determine the granularity of TAR independently, or can uniquely determine the granularity of TAR (for example, symbol) based on a standard protocol. In this case, multiple TAR granularities can coexist, including logical time units such as symbols, time slots, and / or subframes, and absolute time units such as microseconds, milliseconds and / or seconds. The communication node can report TA based on one of the TAR granularities to improve the flexibility and accuracy of TA reporting, so that the service node can more accurately know the actual location of the communication node and perform more accurate timing alignment, in order to avoid resource collisions. In addition, in the event of a resource collision, the resources to be transmitted and the resources not to be transmitted can also be determined based on the transmission priority of the resource type in which the collision occurred, so as to resolve the collision and improve the reliability of communication.

[0039] In one embodiment, the indication granularity is determined based on an indication received from a serving node; the indication from the serving node includes at least one of the following: system information, radio resource control (RRC) signaling, media access control control element (MAC CE) signaling, and downlink control information (DCI).

[0040] In this embodiment, the service node may indicate the granularity of the TAR through system information (such as system information block 19, System Information Block 19), RRC signaling, MAC CE and / or DCI signaling. In some scenarios, it may also indicate the subcarrier spacing corresponding to the granularity of the TAR. Indicating the subcarrier spacing is mainly for the case where the granularity of the TAR is a logical time unit such as a time slot, a symbol and / or a subframe. When the granularity of the TAR is an absolute time unit, it is usually not necessary to notify the subcarrier spacing.

[0041] In one embodiment, the indication granularity is indicated by a reserved bit field in the timing advance report.

[0042] In this embodiment, the UE can independently determine or select the TAR granularity. For example, in the MAC CE, a reserved bit field (as shown in FIG2 , marked as R) is used to indicate the TAR granularity. Assuming that the reserved bit field R is re-marked as G, G=0 can indicate that the TAR granularity is time slots, that is, the TAR reports the number of time slots; G=1 can indicate that the TAR granularity is symbols, that is, the TAR reports the number of symbols. Alternatively, G=0 can indicate that the TAR granularity is symbols, G=1 can indicate that the TAR granularity is time slots, and so on.

[0043] In one embodiment, the indication granularity includes at least two granularities; and the timing advance is the sum of the timing advances corresponding to each granularity.

[0044] In this embodiment, the granularity of the TAR reported by the communication node UE can be a combination of multiple granularities (for example, including time slots and symbols). When the communication node operates at a high frequency (for example, the FR2 band), in order to report a finer-grained TA, the communication node supports a higher subcarrier spacing, such as 60kHz. The number of 60kHz symbols corresponding to the maximum TA duration of 540ms is 30240. In this case, the 14-bit TA field is not sufficient to indicate the number of symbols occupied by the TA. In this case, the reserved bit field can be used to indicate the TA, the number of bits in the TA field can be further increased (for example, adding another byte), and a combination of multiple granularities can be used to notify the TA. For example, X bits in the TA field represent the number of TA symbols, and Y bits represent the number of TA time slots.

[0045] In one embodiment, the timing advance field includes at least two parts, each part is used to indicate a corresponding timing advance amount according to a corresponding granularity.

[0046] In this embodiment, the TA domain can be split into at least two domains. Taking the split into two domains as an example, the first TA domain represents the number of TA symbols, and the second TA domain represents the number of TA time slots. For example, the timing advance domain in Figure 2 is divided into a first timing advance domain (TA1 domain) and a second timing advance domain (TA2 domain). The subcarrier spacing of the time slots and symbols can be the same, for example, both are 15kHz; or the subcarrier spacing of the time slots and symbols can be different, for example, the time slots are 15kHz and the symbols are 30kHz. The reported TA duration is equal to the sum of the above two durations. In addition, the reported TA duration must be greater than or equal to the actually determined TA duration.

[0047] In one embodiment, the indication granularity is determined according to a configured timing advance deviation threshold value; the timing advance deviation threshold is used to determine whether to trigger a timing advance report.

[0048] In this embodiment, TAR may be triggered if any of the following events are met:

[0049] Event 1: TA reporting is triggered based on the instruction of the higher layer.

[0050] Event 2: When the higher layer configures the TA offset threshold (offsetThresholdTA), the UE does not report the TA value to the serving cell.

[0051] Event 3: If the difference between the current TA and the last reported TA is equal to or greater than the TA deviation threshold (offsetThresholdTA).

[0052] In existing protocols, the TA offset threshold (offsetThresholdTA) ranges from 0.5ms to 15ms, which matches the previous TA reporting based on 1ms granularity. This embodiment adjusts the TA offset threshold range accordingly to accommodate finer-grained TA reporting.

[0053] For example, new TA deviation threshold configuration values ​​can be introduced. Smaller TA deviation threshold configuration values ​​(<0.5ms) in ms or us can be introduced, such as 0.05ms, 0.1ms, 0.2ms, 0.3ms, etc.; another example, TA deviation threshold configuration values ​​in symbols can be introduced, such as 1 symbol, 2 symbols, 3 symbols, etc. The number of these symbols can be less than or equal to X*14, that is, less than or equal to Xms, where X is an integer greater than or equal to 1; another example, more new TA deviation threshold configuration values ​​can be inserted into the TA deviation threshold configuration value to make the threshold configuration more precise and accurate, such as adding 0.1ms, 0.2ms, 0.3ms, 1.5ms, 2.5ms, 3.5ms, etc.

[0054] The granularity of the TAR can also be indicated based on the TA deviation threshold configuration value. If the TA deviation threshold configuration value configured by the service node is a value in the above-mentioned existing protocol or a value in milliseconds, the granularity used when the communication node reports the TA can be timeslots. If the TA deviation threshold configuration value configured by the service node is a newly introduced configuration value or a value in symbols, the granularity used when the communication node reports the TA can be symbols.

[0055] The configured value of the TA deviation threshold must be greater than or equal to the granularity of the TAR.

[0056] In one embodiment, the indication granularity includes at least one of the following: one or more time units; one or more symbols; one or more time slots; one or more subframes or frames; a combination of one or more subcarrier spacings and one or more time units; a combination of one or more subcarrier spacings and one or more symbols; a combination of one or more subcarrier spacings and one or more time slots; a combination of one or more subcarrier spacings and one or more subframes or frames.

[0057] For half-duplex-frequency division duplex (HD-FDD) and time division duplex (TDD) communication nodes, the following resource type collisions (i.e., partial or complete overlap of two resources) may occur due to TA mismatch:

[0058] Case 1: Collision between dynamically scheduled downlink (DL) reception and semi-statically configured uplink (UL) transmission; Case 2: Collision between semi-statically configured DL reception and dynamically scheduled UL transmission; Case 3: Collision between semi-statically configured DL reception and semi-statically configured UL transmission; Case 4: Collision between dynamically scheduled DL reception and dynamically scheduled UL transmission; Case 5: Collision between configured SSB and dynamically scheduled / semi-statically configured UL transmission; Case 6: Collision between dynamic or semi-static downlink and a valid random access opportunity (RACH Occasion, RO).

[0059] Dynamic scheduling in the above case refers to the reception or transmission of scheduling or indication through DCI. For example, DL can be Physical Downink Shared Channel (PDSCH), such as SIB19 or Channel Status Information-Reference Signal (CSI-RS), and UL can be Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) or Sounding Reference Signal (SRS); semi-static configuration refers to the reception or transmission configured by higher-layer parameters. For example, DL can be PDCCH, PDSCH, SSB, CSI-RS or DL-PRS, and UL can be PUCCH, PUSCH or SRS.

[0060] The collision in the above case includes: the collision of two types of signals (such as DL reception and UL transmission) due to overlapping time-frequency resources, and / or the collision of two types of signals due to insufficient uplink and downlink switching time between them, even though the time-frequency resources do not overlap. For example, after DL reception, there must be at least N Rx-Tx ·T c After UL transmission, there must be at least N intervals before DL reception. Tx-Rx ·T c The interval will avoid collision. c is the basic time unit of access technology, N Rx-Tx 、N Tx-Rx The number of basic time units required to switch from receiving to sending and from sending to receiving respectively.

[0061] For Case 3 and Case 4, the communication node does not expect to simultaneously perform semi-statically configured DL reception and semi-statically configured UL transmission, or does not expect to simultaneously perform dynamically scheduled DL reception and dynamically scheduled UL transmission. Accordingly, the serving node does not perform such configuration or scheduling. For HD-FDD or TDD UEs, Case 3 or Case 4 can be enhanced accordingly.

[0062] In one embodiment, the priority of the transmission of the colliding resource types satisfies at least one of the following conditions:

[0063] Condition 1: The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; Condition 2: The priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; Condition 3: The priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; Condition 4: The priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0064] The priority of resource type A is higher than the priority of resource type B, which may mean that: when resource type A exists on the same resource, the UE does not receive or send resource type B; or, when resource type A does not exist on the resource, the UE can receive or send resource type B on the resource.

[0065] For example, if the first configuration type is semi-static configuration, the second configuration type is dynamic scheduling, the first transmission direction is DL, and the second transmission direction is UL, the priority of the transmission of the resource type in which the collision occurs satisfies at least one of the following conditions:

[0066] Condition 1: The priority of semi-statically configured DL reception is higher than the priority of semi-statically configured UL transmission; Condition 2: The priority of dynamically scheduled DL reception is higher than the priority of dynamically scheduled UL transmission; Condition 3: The priority of semi-statically configured UL transmission is higher than the priority of semi-statically configured DL reception; Condition 4: The priority of dynamically scheduled UL transmission is higher than the priority of dynamically scheduled DL reception.

[0067] In one embodiment, the priority of the transmission of the resource type in which the collision occurs satisfies the condition one or the condition two, but the priority of the first designated resource type is higher than the priority of the resource of the first transmission direction of the first configuration type or the second configuration type; the first designated resource type includes at least one of the following: PRACH; Message A Physical Uplink Shared Channel (MsgA PUSCH); PUCCH.

[0068] For example, the first configuration type is semi-static configuration, the second configuration type is dynamic scheduling, the first transmission direction is DL, and the second transmission direction is UL. In this embodiment, the priority of the transmission of the resource type that collides meets condition one or condition two, and the downlink is prioritized to ensure downlink coverage and performance.

[0069] Condition 1: The priority of semi-statically configured DL reception is higher than the priority of semi-statically configured UL transmission. However, some special semi-statically configured UL signals are exceptions, such as PRACH or MsgA PUSCH, or PUCCH (e.g., carrying HARQ or other special UL control information) triggered by higher layers. Taking PRACH triggered by higher layers as an example, its priority is not necessarily lower than the priority of DL reception. For example, it can be set to be greater than the DL reception priority. It can also be equal to the DL reception priority. In this case, whether to receive DL or transmit UL depends on the UE implementation.

[0070] Condition 2: The priority of dynamically scheduled DL reception is higher than the priority of dynamically scheduled UL transmission, with the exception of some special dynamically scheduled UL signals, such as PRACH or PUCCH (e.g., carrying HARQ or other special UL control information). Taking dynamically scheduled PRACH or PUCCH as an example, the priority of dynamically scheduled PRACH or PUCCH is not necessarily lower than the priority of DL reception. For example, it can be set to be greater than the DL reception priority. It can also be equal to the DL reception priority. In this case, whether to receive DL or transmit PRACH or PUCCH depends on the UE implementation.

[0071] In one embodiment, the priority of the transmission of the resource type in which the collision occurs satisfies the condition three or the condition four, but the priority of the second designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the second designated resource type includes at least one of the following: PDCCH configured in a common search space set; CSI-RS; synchronization signal block SSB; SIB.

[0072] For example, the first configuration type is semi-static configuration, the second configuration type is dynamic scheduling, the first transmission direction is DL, and the second transmission direction is UL. In this embodiment, the priority of the transmission of the resource type that collides meets condition three or condition four, with uplink priority, to prioritize uplink coverage and performance.

[0073] Condition 3: The priority of semi-statically configured UL transmission is higher than the priority of semi-statically configured DL reception, but some special semi-statically configured DL signals are exceptions, such as PDCCH (at least one of Type-0 / 0A / 0B / 1 / 2-PDCCH), CSI-RS and / or SSB configured in the common search space set. For example, when the semi-statically configured PDSCH and CSI-RS reception collides with the semi-statically configured PUSCH and SRS, the UE gives priority to sending PUSCH and SRS and does not receive PDSCH and CSI-RS. However, when the semi-statically configured Type-0 PDCCH reception collides with the semi-statically configured PUSCH and SRS, the UE gives priority to receiving Type-0 PDCCH and gives up sending PUSCH and SRS.

[0074] Condition 4: Dynamically scheduled UL transmission has a higher priority than dynamically scheduled DL reception, but some dynamically scheduled DL signals are exceptions, such as CSI-RS and / or SIB1 / 2 / ... / 19. For example, when dynamically scheduled PDSCH reception (non-SIB) collides with dynamically scheduled PUSCH, the UE prioritizes PUSCH transmission and does not receive PDSCH. However, when SIB1 / 2 / ... / 19 reception collides with PUSCH, the UE prioritizes SIB reception and abandons PUSCH transmission.

[0075] In one embodiment, the priority of the transmission of the resource type that collides is configured or indicated by at least one of received system information, RRC signaling, MAC CE signaling, or DCI.

[0076] In this embodiment, the serving node may configure or indicate the priority of semi-statically configured DL reception and UL transmission, and / or configure or indicate the priority of dynamically scheduled DL reception and UL transmission through system information (such as SIB 19), RRC signaling, MAC CE and / or DCI signaling.

[0077] In one embodiment, the configured or indicated priority of the transmission of the colliding resource type includes at least one of the following:

[0078] The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; the priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; the priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; the priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0079] In one embodiment, when the communication node does not receive the configuration or indication of the priority of the colliding resource type transmission, or the service node does not configure or indicate the priority of the colliding resource type transmission, the priority of the colliding resource type transmission is the default priority.

[0080] In this embodiment, if the service node does not configure or indicate the above-mentioned priority, or the communication node does not receive the configuration or indication from the service node, the communication node may operate according to the default priority. The default priority may be at least one of conditions one to four. The designated exception (or special) signals in these four conditions may be enabled or disabled. That is, for any condition, the exception signal may or may not exist.

[0081] In one embodiment, the service node configures or indicates the priority of the two types of signals in at least one of case 1 to case 6 through system information (such as SIB 19), RRC signaling, MAC CE and / or DCI signaling. Optionally, the priority indicated above does not apply to signals of some exceptional specified resource types, and the exceptional signals can refer to the various methods mentioned above. Optionally, when the service node does not configure or indicate the above priority, or the communication node does not receive the above indication from the service node, the communication node operates according to the default priority. The default priority includes the priority of at least one of semi-statically configured DL reception, semi-statically configured UL transmission, dynamically scheduled DL reception, dynamically scheduled UL transmission, SSB or valid RO. For example, considering the downlink coverage or performance (such as SIB), DL reception can be prioritized; considering that the RedCap communication node mainly performs UL business, UL transmission can be prioritized.

[0082] In one embodiment, the priority of transmission of the resource type in which the collision occurs is determined based on the received configuration or indication, but the priority of the third designated resource type is higher than the priority of the resource of the first transmission direction of the first configuration type or the second configuration type; the third designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0083] In this embodiment, the service node may configure or indicate the priority of semi-statically configured DL reception and UL transmission, and / or configure or indicate the priority of dynamically scheduled DL reception and UL transmission through system information (such as SIB 19), RRC signaling, MAC CE and / or DCI signaling, but with the exception of signals of some specified resource types, such as SIB PDSCH, PDCCH configured in a common search space set (at least one of Type-0 / 0A / 0B / 1 / 2-PDCCH), CSI-RS, SSB, PRACH / MsgA PUSCH, and / or PUCCH, etc.

[0084] For example, the serving node may configure priorities according to condition 1 and / or condition 2, but with the exception of signals of specified resource types in condition 1 and / or condition 2. For example, although the serving node configures the DL priority of semi-persistent / dynamic scheduling to be higher than the UL priority of semi-persistent / dynamic scheduling, the PRACH / MsgA PUSCH and / or PUCCH shall be higher than the UL priority of semi-persistent / dynamic scheduling.

[0085] In one embodiment, the priority of the transmission of the resource type in which the collision occurs is determined based on the received configuration or indication, but the priority of the transmission of the fourth designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the fourth designated resource type includes at least one of the following: PDCCH configured with a common search space set; CSI-RS; SSB; SIB.

[0086] The serving node may configure priorities according to conditions 3 and / or 4, except for signals of specified resource types in conditions 3 and / or 4. For example, although the priority of DL configured by the serving node for semi-persistent / dynamic scheduling is lower than the priority of UL configured by semi-persistent / dynamic scheduling, the priority of SIB PDSCH, PDCCH configured in the common search space set, CSI-RS, and / or SSB is higher than the priority of UL configured by semi-persistent / dynamic scheduling.

[0087] When the above-mentioned DL exception signal collides with the UL exception signal, the DL exception signal can be received first to ensure downlink coverage and performance; or, the UL exception signal can be sent first to ensure uplink access and performance; or, the communication node can decide whether to receive the DL exception signal or send the UL exception signal.

[0088] In the case where a UL transmission collides with multiple DL receptions, if the multiple DL receptions are of the same type, for example, all are semi-statically configured DL receptions, or all are dynamically scheduled DL receptions, and only one priority comparison is involved, the collision between the multiple transmissions can be resolved by the methods in the above embodiments. Similarly, in the case where a DL reception collides with multiple UL transmissions, if the multiple UL transmissions are of the same type, only one priority comparison is involved, and the collision between the multiple transmissions can be resolved by the methods in the above embodiments. However, in the case where a UL transmission collides with multiple DL receptions of different configuration types, or a DL reception collides with multiple UL transmissions of different configuration types, the use of multiple different priority mechanisms may be involved, and there may be conflicts between different priorities. The embodiments of the present application also provide solutions to resource collisions of different priorities.

[0089] In the embodiments of the present application, one or more DL receptions may be equivalent to the reception of one or more DL signals, and one or more UL transmissions may be equivalent to the transmission of one or more UL signals. In other words, the number of resource transmissions may be equivalent to the number of signal transmissions.

[0090] In one embodiment, resources in multiple first transmission directions are equivalent to resources in one first transmission direction. The transmission type of the resources in the first transmission direction after the resources in the multiple first transmission directions are equivalent is determined by at least one of the following: a transmission type with the highest transmission type priority among the resources in the multiple first transmission directions; or a transmission type with the largest total number of resources occupied among the resources in the multiple first transmission directions; wherein the occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0091] In one embodiment, the method further includes: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, determining whether to transmit or not transmit each resource that collides according to the time sequence of the resources.

[0092] Figure 4 is a schematic diagram of a resource collision provided by an embodiment. As shown in Figure 4, the first transmission direction is UL and the second transmission direction is DL. Dynamically scheduling DL can first resolve the collision between dynamic DL and dynamic UL before semi-statically configuring DL. If the dynamic DL priority is higher than the dynamic UL, the communication node does not send the dynamic UL. In this case, there is no collision between the semi-static DL and dynamic UL, and no resolution is required. If the dynamic DL priority is lower than the dynamic UL, the communication node does not receive the dynamic DL. In this case, the dynamic UL priority is also higher than the semi-static DL. Therefore, neither DL transmission is received, and the communication node only performs UL transmission.

[0093] In one embodiment, the method further includes: in the event that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determining whether each resource of the same configuration type that collided is transmitted or not, and then determining whether each resource of the different configuration types that collided is transmitted or not.

[0094] In this embodiment, the collision between the same type of DL reception and UL transmission (for example, both are semi-statically configured; or both are dynamically scheduled) can be resolved first, and then the collision between different types of DL reception and UL transmission (for example, the former is dynamically scheduled, and the latter is semi-statically configured; or vice versa) can be resolved.

[0095] For example, the collision between semi-statically configured DL reception and semi-statically configured UL transmission can be resolved first, followed by the collision between dynamically scheduled DL reception and semi-statically configured UL transmission. This means that Case 3 is resolved first, followed by Case 1. Figure 5 is a schematic diagram of another resource collision provided by an embodiment. As shown in Figure 5, the time order can be disregarded. That is, even though the semi-static DL is scheduled after the dynamic DL, the collision between the semi-static DL and the semi-static UL is still prioritized, followed by the collision between the dynamic DL and the semi-static UL.

[0096] For another example, the collision between the semi-statically configured DL reception and the semi-statically configured UL transmission may be resolved first, and then the collision between the dynamically scheduled UL transmission and the semi-statically configured DL reception may be resolved, that is, Case 3 may be resolved first, and then Case 2. For another example, the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission may be resolved first, and then the collision between the dynamically scheduled DL reception and the semi-statically configured UL transmission may be resolved, that is, Case 4 may be resolved first, and then Case 1. For another example, the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission may be resolved first, and then the collision between the dynamically scheduled UL transmission and the semi-statically configured DL reception may be resolved, that is, Case 4 may be resolved first, and then Case 2.

[0097] In one embodiment, the method further includes: in the event that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determining whether each resource of the different configuration types that collide is transmitted or not, and then determining whether each resource of the same configuration type that collide is transmitted or not.

[0098] In this embodiment, the collision between different types of DL reception and UL transmission (for example, the former is dynamically scheduled and the latter is semi-statically configured; or vice versa) can be resolved first, and then the collision between the same type of DL reception and UL transmission (for example, both are semi-statically configured; or both are dynamically scheduled) can be resolved.

[0099] For example, the collision between the dynamically scheduled DL reception and the semi-statically configured UL transmission may be resolved first, and then the collision between the semi-statically configured DL reception and the semi-statically configured UL transmission may be resolved, that is, Case 1 may be resolved first, and then Case 3 may be resolved; for another example, the collision between the dynamically scheduled UL transmission and the semi-statically configured DL reception may be resolved first, and then the collision between the semi-statically configured DL reception and the semi-statically configured UL transmission may be resolved, that is, Case 2 may be resolved first, and then Case 3 may be resolved; for another example, the collision between the dynamically scheduled DL reception and the semi-statically configured UL transmission may be resolved first, and then the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission may be resolved, that is, Case 1 may be resolved first, and then Case 4 may be resolved; for another example, the collision between the dynamically scheduled UL transmission and the semi-statically configured DL reception may be resolved first, and then the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission may be resolved, that is, Case 2 may be resolved first, and then Case 4 may be resolved.

[0100] In one embodiment, the method further includes: in the event that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determining whether each resource of the first configuration type that collided is transmitted or not, and then determining whether each resource of the second configuration type that collided is transmitted or not.

[0101] For example, the collision between the semi-statically configured DL reception and the semi-statically configured UL transmission can be resolved first, and then the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission can be resolved, that is, Case 3 can be resolved first, and then Case 4 can be resolved; for another example, the collision between the dynamically scheduled DL reception and the dynamically scheduled UL transmission can be resolved first, and then the collision between the semi-statically configured DL reception and the semi-statically configured UL transmission can be resolved, that is, Case 4 can be resolved first, and then Case 3 can be resolved.

[0102] In one embodiment, the method further includes: in the event that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determining whether the resources of the first transmission direction of the first configuration type that collided and each resource of the second transmission direction of the second configuration type are transmitted or not, and then determining whether the resources of the first transmission direction of the second configuration type that collided and each resource of the second transmission direction of the first configuration type are transmitted or not.

[0103] For example, the collision between dynamically scheduled DL reception and semi-statically configured UL transmission can be resolved first, and then the collision between semi-statically configured DL reception and dynamically scheduled UL transmission can be resolved, that is, Case 1 can be resolved first, and then Case 2 can be resolved. For another example, the collision between semi-statically configured DL reception and dynamically scheduled UL transmission can be resolved first, and then the collision between dynamically scheduled DL reception and semi-statically configured UL transmission can be resolved, that is, Case 2 can be resolved first, and then Case 1 can be resolved.

[0104] In one embodiment, the method further includes: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, transmitting the resources of the first transmission direction one or more times and not transmitting the resources of the second transmission direction multiple times.

[0105] For example, if a signal A (or a transmission) collides with multiple signals (or multiple transmissions), signal A is sent or received first, and the multiple signals are not received or sent.

[0106] Signal A is a DL receive signal, and multiple signals are UL transmit signals; alternatively, signal A is a UL transmit signal, and multiple signals are DL receive signals. Multiple signals can be of the same type or different types. The same type means that all signals are dynamically scheduled or configured or instructed by higher layers. Different types means that some signals are dynamically scheduled, while others are configured or instructed to be transmitted by higher layers.

[0107] In one embodiment, the method further includes: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, transmitting the resources of the second transmission direction multiple times and not transmitting the resources of the first transmission direction one or more times.

[0108] For example, if a signal A (or a transmission) collides with multiple signals (or multiple transmissions), the multiple signals are sent or received first, and signal A is not received or sent.

[0109] Signal A is a DL receive signal, and multiple signals are UL transmit signals. Alternatively, signal A is a UL transmit signal, and multiple signals are DL receive signals. Multiple signals can be of the same or different types. The same type means that all signals are dynamically scheduled or configured or instructed by a higher layer. Different types means that some signals are dynamically scheduled, while others are configured or instructed to be transmitted by a higher layer.

[0110] In each embodiment of the present application, the semi-statically configured DL reception may include SSB or may not include SSB; the semi-statically configured UL transmission may include PRACH / MsgA PUSCH or may not include PRACH / MsgA PUSCH.

[0111] In one embodiment, the method further includes: in the event that one or more resources in the first transmission direction collide with one or more resources in the second transmission direction, determining whether to transmit the resources in the first transmission direction or the resources in the second transmission direction based on the number of transmissions of the resources in the first transmission direction and the number of transmissions of the resources in the second transmission direction.

[0112] In this embodiment, when one or more DL signals (or one or more DL transmissions) collide with one or more UL signals (or one or more UL transmissions), priority is determined based on the number of colliding DL signals and UL signals or the number of transmissions. For example, if three DL signals (i.e., three transmissions) collide and two UL signals (i.e., two transmissions) collide, the DL receive priority is higher than the UL transmit priority.

[0113] This method is applicable to the collision of one DL signal with one UL signal, the collision of one DL signal with multiple UL signals, the collision of one UL signal with multiple DL signals, and the collision of multiple DL signals with multiple UL signals.

[0114] In one embodiment, the method further includes: in the event that resources of the first transmission direction collide one or more times with resources of the second transmission direction one or more times, determining whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the total resources occupied by the resources of the first transmission direction and the total resources occupied by the resources of the second transmission direction.

[0115] In this embodiment, when one or more DL signals (or one or more DL transmissions) collide with one or more UL signals (or one or more UL transmissions), priority is determined based on the sum of the resources (e.g., time domain or frequency domain resources) occupied by the colliding DL and UL signal transmissions. For example, if the sum of the resources occupied by the DL transmissions is greater than the sum of the resources occupied by the UL transmissions, the DL reception priority is higher than the UL transmission priority.

[0116] This method is applicable to the collision of one DL signal with one UL signal, the collision of one DL signal with multiple UL signals, the collision of one UL signal with multiple DL signals, and the collision of multiple DL signals with multiple UL signals.

[0117] In one embodiment, the method further includes: when a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resource in the first transmission direction and the resource in the multiple second transmission directions have the same transmission priority, determining whether to transmit or not transmit the colliding resource by using one of the following:

[0118] Determine whether to transmit or not each resource that collides according to the time sequence of the resources; or, transmit the resources in the first transmission direction, and do not transmit the resources in the second transmission direction multiple times; or, transmit the resources in the second transmission direction multiple times, and do not transmit the resources in the first transmission direction; or, uniformly determine whether to transmit or not for each resource in the second transmission direction.

[0119] For example, when the above-mentioned modes do not include SSB, PRACH and / or MsgA PUSCH, the collision problem between these signals and signals in different directions may be considered separately.

[0120] Figure 6 is a schematic diagram of another resource collision provided by an embodiment. As shown in Figure 6, when an SSB collides with a semi-static UL or dynamic UL, since no processing between different priorities is involved, the communication node can preferentially receive the SSB, and both the semi-static UL and dynamic UL transmissions must be abandoned (not transmitted).

[0121] Figures 7, 8, and 9 are schematic diagrams of another resource collision provided by an embodiment of the present application. Similarly, as shown in Figures 7, 8, and 9, when PRACH (which can also be replaced by MsgA PUSCH) collides with semi-static DL or dynamic DL, there is no processing between different priorities, and each resource that collides can be determined to be transmitted or not according to the time order of the resources; the resources of the first transmission direction can also be transmitted without transmitting the resources of the second transmission direction multiple times (i.e., sending PRACH and not receiving dynamic DL / semi-static DL / SSB); the resources of the second transmission direction can also be transmitted multiple times without transmitting the resources of the first transmission direction (i.e., receiving dynamic DL / semi-static DL / SSB and not sending PRACH); the communication node can also implement the selection of receiving DL or sending UL, wherein the multiple DL signals that collide with PRACH need to make a unified decision, that is, either all of the multiple DL signals are received and PRACH is not sent, or none of the multiple DL signals are received and PRACH is sent.

[0122] In one embodiment, the method further includes: when a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resources in the multiple second transmission directions include resources having the same transmission priority as the resources in the first transmission direction and resources having different transmission priorities as the resources in the first transmission direction, determining whether to transmit or not transmit the colliding resources by using one of the following:

[0123] Determine whether to transmit or not for each resource that collides according to the time sequence of the resources; or, transmit the resources in the first transmission direction, and do not transmit the resources in the second transmission direction multiple times; or, transmit the resources in the second transmission direction multiple times, and do not transmit the resources in the first transmission direction; or, uniformly determine whether to transmit or not for each resource in the second transmission direction; or, first determine whether to transmit or not for each resource that has the same transmission priority as the resources in the first transmission direction, and then determine whether to transmit or not for each resource that has a different transmission priority from the resources in the first transmission direction.

[0124] As shown in Figures 10 and 11, when SSB collides with PRACH (can also be replaced by MsgA PUSCH) and other ULs at the same time, SSB and PRACH have the same priority, and SSB has a higher priority than other ULs, so two different priority levels are involved. It is possible to determine whether to transmit or not each resource that collides according to the time sequence of the resources; it is also possible to transmit the resources of the first transmission direction without transmitting the resources of the second transmission direction multiple times (that is, receiving SSB, not sending PRACH and other ULs); it is also possible to transmit the resources of the second transmission direction multiple times without transmitting the resources of the first transmission direction (that is, sending PRACH and other ULs, not receiving SSB); it can also be solved by a communication node, wherein multiple UL signals that collide with SSB need to make the same decision; it is also possible to process the collision between SSB and PRACH first, and then process the collision between SSB and other ULs. Even if, as shown in Figure 11, PRACH is located behind other ULs, for the collision between SSB and PRACH / MsgA PUSCH, if the UE prioritizes receiving SSB, then PRACH and other ULs are not sent; if the UE prioritizes sending PRACH and does not receive SSB, then the collision between SSB and other ULs does not exist, and other ULs can be sent normally.

[0125] The reason for handling collisions in this order is that if the SSB collision with other UL signals is handled first, the other UL signals will be abandoned. If the SSB collision with PRACH is then handled, and if PRACH is prioritized or handled by the UE, the previously abandoned UL signals will be meaningless. "Other DL" refers to DL signals other than SSB, and "other UL" refers to UL signals other than PRACH / MsgA PUSCH.

[0126] In one embodiment, a situation where multiple uplink transmissions (or multiple uplink signals) collide with multiple downlink transmissions (or multiple downlink signals) is shown in FIG12 below. The collision can be resolved in any of the following ways:

[0127] Method 1: Multiple consecutive collision resource intervals are divided into collisions of one transmission with multiple (or one) transmissions in chronological order. The collisions are then handled according to the aforementioned collisions of one transmission with multiple (or one) transmissions. For example, a collision of U1-D1-U2 is handled first. If D1 is transmitted but U1 and U2 are not, only the collision of D2-U3 is handled. If U1 and U2 are transmitted but D1 is not, then the collision of U2-D2-U3 must be handled.

[0128] Method 2: For multiple consecutive colliding resource intervals, processing is performed based on the relative size of the number of downlink transmissions and the number of uplink transmissions that collided. If the number of downlink transmissions and the number of uplink transmissions that collided are different, then:

[0129] Method 2-1: For the transmission direction with a small number of transmissions (downlink or uplink), if the transmission types are the same, the "single transmission" handling method described in "Collision between a single transmission and multiple transmissions" is used. For the transmission direction with a large number of transmissions (uplink or downlink), the "multiple transmissions" handling method described in "Collision between a single transmission and multiple transmissions" is used. For example, in Figure 12, the downlink direction has a small number of transmissions. For D1 and D2, the decision to transmit or not is made uniformly. For U1, U2, and U3, the decision to transmit or not is made based on the handling method for a collision between a single downlink and multiple uplinks.

[0130] Method 2-2: For the transmission direction (uplink or downlink) with a small number of transmissions, if the transmission types are different, then:

[0131] Method 2-2-1: They are still processed uniformly without considering their transmission type (semi-static, dynamic or periodic), that is, the transmission direction with a small number of transmissions is uniformly decided to be transmitted, and the transmission direction with a large number of transmissions is uniformly decided not to be transmitted; or the transmission direction with a small number of transmissions is uniformly decided not to be transmitted, and the transmission direction with a large number of transmissions is uniformly decided to be transmitted.

[0132] Method 2-2-2: Still treat them uniformly, but treat them as the same transmission type, and then follow the method of situation 2-1. There are at least the following methods to treat them as the same transmission type:

[0133] Method 2-2-2-1: Sort by transmission type priority: dynamic > semi-static > periodic, and regard them all as the transmission type with the highest priority.

[0134] Method 2-2-2-2: Determine based on the total amount of resources occupied by the transmission type (at least one or more of the time domain, frequency domain, code domain, and spatial domain resources). If the occupied resources are different, they are considered the transmission type with the larger number of resources. For example, in Figure 12, D2 occupies more time domain resources, so D1 and D2 can be treated as the same type of D2. If the occupied resources are the same, then process according to method 2-2-2-1.

[0135] Method 2-2-3: Do not handle them uniformly, and handle them according to Method 1.

[0136] Method 3: For multiple consecutive colliding resource intervals, based on the relative magnitude of the number of downlink transmissions and the number of uplink transmissions that collided, if the number of downlink transmissions and the number of uplink transmissions that collided are the same, then:

[0137] Method 3-1: Follow Method 1.

[0138] Method 3-2: The base station determines which transmission direction is considered as the one with fewer transmission times based on its implementation method, and then processes it according to Method 2.

[0139] Method 3-3: The collision is determined based on the total amount of resources (e.g., time domain resources) occupied by the colliding uplink and downlink transmissions. The transmission with the smaller number of occupied resources is considered the one with the smaller number of transmissions, and the collision is handled according to Method 2. If the occupied resources are the same, the collision is handled according to Method 3-1 or 3-2.

[0140] In one embodiment, the resource configuration type includes dynamic scheduling and semi-static configuration; the resource transmission direction includes uplink transmission and downlink reception.

[0141] Figure 13 is a flowchart of a resource determination method provided by one embodiment. This method can be applied to a service node, which can be a network-side node. For technical details not fully described in this embodiment, please refer to any of the above embodiments. As shown in Figure 13, the method provided by this embodiment includes 210 and 220.

[0142] In 210, resource configuration information is determined, the resource configuration information including the indication granularity of the timing advance of the target frame and / or the priority of the colliding resource type transmission, the timing advance is indicated by the communication node to the serving node via the timing advance field in the timing advance report.

[0143] In 220, transmission resources with the communication node are determined according to the resource configuration information.

[0144] In this embodiment, the service node can uniquely determine the TAR granularity based on the protocol, or it can determine the TAR granularity autonomously. Alternatively, the communication node can determine the TAR granularity and report it to the service node. The TAR granularity supports the coexistence of multiple granularities, including logical time units such as symbols, time slots, and / or subframes, as well as absolute time units such as microseconds, milliseconds, and / or seconds. On this basis, the service node can more accurately determine the actual location of the communication node and perform more accurate timing alignment to avoid resource collisions. In addition, in the event of a resource collision, the resources to be transmitted and those not to be transmitted can be determined based on the transmission priority of the colliding resource type, thereby resolving the collision and improving communication reliability.

[0145] In one embodiment, the indication granularity is determined by the serving node and indicated to the communication node through at least one of the following: system information, RRC signaling, MAC CE signaling, and DCI.

[0146] In one embodiment, the priority of the transmission of the colliding resource type is determined by the serving node and configured or indicated through at least one of system information, RRC signaling, MAC CE signaling and DCI.

[0147] In one embodiment, the indication granularity is determined according to an indication received from the serving node; the indication includes at least one of the following: system information, RRC signaling, MAC CE signaling, and DCI.

[0148] In one embodiment, the indication granularity is indicated by a reserved bit field in the timing advance report.

[0149] In one embodiment, the indication granularity includes at least two granularities; and the timing advance is the sum of the timing advances corresponding to each granularity.

[0150] In one embodiment, the timing advance field includes at least two parts, each part is used to indicate a corresponding timing advance amount according to a corresponding granularity.

[0151] In one embodiment, the indication granularity is determined according to a configured timing advance deviation threshold value; wherein the timing advance deviation threshold is used to determine whether to trigger a timing advance report.

[0152] In one embodiment, the indication granularity includes at least one of the following:

[0153] One or more time units; one or more symbols; one or more time slots; one or more subframes or frames; a combination of one or more subcarrier spacings and one or more time units; a combination of one or more subcarrier spacings and one or more symbols; a combination of one or more subcarrier spacings and one or more time slots; a combination of one or more subcarrier spacings and one or more subframes or frames.

[0154] In one embodiment, the priority of the transmission of the colliding resource type satisfies at least one of the following conditions:

[0155] Condition 1: The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; Condition 2: The priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; Condition 3: The priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; Condition 4: The priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0156] In one embodiment, the priority of the transmission of the resource type that collides meets the condition one or the condition two, but the priority of the first specified resource type is higher than the priority of the resource of the first transmission direction of the first configuration type or the second configuration type; in one embodiment, PRACH; MsgA PUSCH; PUCCH.

[0157] In one embodiment, the priority of the transmission of the resource type that collides meets the condition three or the condition four, but the priority of the second designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the second designated resource type includes at least one of the following: physical downlink control channel PDCCH configured in a common search space set; channel state information reference signal CSI-RS; synchronization signal block SSB; system information block.

[0158] In one embodiment, the priority of the transmission of the colliding resource type is configured or indicated by at least one of received system information, RRC signaling, MAC CE signaling or DCI.

[0159] In one embodiment, the configured or indicated priority of the transmission of the colliding resource type includes at least one of the following:

[0160] The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; the priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; the priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; the priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0161] In one embodiment, when the communication node does not receive the configuration or indication of the priority of the colliding resource type transmission, or the service node does not configure or indicate the priority of the colliding resource type transmission, the priority of the colliding resource type transmission is the default priority.

[0162] In one embodiment, the priority of the transmission of the resource type in which the collision occurs is determined according to the received configuration or indication, but the priority of the third designated resource type is higher than the priority of the resources of the first transmission direction of the first configuration type or the second configuration type; the third designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0163] In one embodiment, the priority of the transmission of the resource type that collides is determined according to the received configuration or indication, but the priority of the transmission of the fourth designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the fourth designated resource type includes at least one of the following: physical downlink control channel PDCCH configured in a common search space set; channel state information reference signal CSI-RS; synchronization signal block SSB; system information block.

[0164] In one embodiment, the method further comprises:

[0165] In the case that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, whether to transmit or not transmit each resource that collides is determined according to the time sequence of the resources.

[0166] In one embodiment, the method further comprises:

[0167] In the event of a collision, first determine whether each resource of the same configuration type that collided is transmitted or not, and then determine whether each resource of the different configuration types that collided is transmitted or not.

[0168] In one embodiment, the method further comprises:

[0169] When one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the colliding different configuration types is transmitted or not, and then determine whether each resource of the colliding same configuration type is transmitted or not.

[0170] In one embodiment, the method further comprises:

[0171] When one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the colliding first configuration type is transmitted or not, and then determine whether each resource of the colliding second configuration type is transmitted or not.

[0172] In one embodiment, the method further comprises:

[0173] In the event that one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, first determine whether the resources in the first transmission direction of the first configuration type that collided and each resource in the second transmission direction of the second configuration type are transmitted or not, and then determine whether the resources in the first transmission direction of the second configuration type that collided and each resource in the second transmission direction of the first configuration type are transmitted or not.

[0174] In one embodiment, the method further comprises:

[0175] In the case that one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, the one or more resources in the first transmission direction are transmitted, and the multiple resources in the second transmission direction are not transmitted.

[0176] In one embodiment, the method further comprises:

[0177] In the case that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, the resources of the multiple second transmission directions are transmitted, and the one or more resources of the first transmission direction are not transmitted.

[0178] In one embodiment, the method further includes: in the event that one or more resources in the first transmission direction collide with one or more resources in the second transmission direction, determining whether to transmit the resources in the first transmission direction or the resources in the second transmission direction based on the number of transmissions of the resources in the first transmission direction and the number of transmissions of the resources in the second transmission direction.

[0179] In one embodiment, the method further includes: in the event that resources of the first transmission direction collide one or more times with resources of the second transmission direction one or more times, determining whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the total resources occupied by the resources of the first transmission direction and the total resources occupied by the resources of the second transmission direction.

[0180] In one embodiment, the method further comprises:

[0181] In the event that a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resource in the first transmission direction and the resources in the multiple second transmission directions have the same transmission priority, one of the following is used to determine whether to transmit the colliding resource:

[0182] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction.

[0183] In one embodiment, the method further comprises:

[0184] In the case where a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resources in the multiple second transmission directions include resources having the same transmission priority as the resources in the first transmission direction and resources having different transmission priorities from the resources in the first transmission direction, one of the following is used to determine whether to transmit the colliding resources:

[0185] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction; or, first determine whether to transmit or not transmit each resource that has the same transmission priority as the resources of the first transmission direction, and then determine whether to transmit or not transmit each resource that has a different transmission priority from the resources of the first transmission direction.

[0186] In one embodiment, the resources of multiple first transmission directions are equivalent to the resources of the one first transmission direction.

[0187] In one embodiment, the transmission type of resources in a first transmission direction after the resources in multiple first transmission directions are equivalent is determined by at least one of the following: the transmission type with the highest transmission type priority among the resources in the multiple first transmission directions; or the transmission type with the largest total number of occupied resources among the resources in the multiple first transmission directions; wherein the occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0188] In one embodiment, the resource configuration type includes dynamic scheduling and semi-static configuration; the resource transmission direction includes uplink transmission and downlink reception.

[0189] The present application also provides a resource determination device. FIG14 is a schematic diagram of the structure of a resource determination device provided by an embodiment. As shown in FIG14, the resource determination device is applied to a communication node and includes:

[0190] The information determination module 310 is configured to determine resource configuration information, wherein the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the transmission of the resource type in which the collision occurs, and the timing advance is indicated to the service node by the communication node through the timing advance field in the timing advance report; the resource determination module 320 is configured to determine the transmission resources with the service node based on the resource configuration information.

[0191] In one embodiment, the indication granularity is determined according to an indication received from the serving node; the indication includes at least one of the following: system information, RRC signaling, MAC CE signaling, and DCI.

[0192] In one embodiment, the indication granularity is indicated by a reserved bit field in a timing advance report.

[0193] In one embodiment, the indication granularity includes at least two granularities; and the timing advance is the sum of the timing advances corresponding to each granularity.

[0194] In one embodiment, the timing advance field includes at least two parts, each part is used to indicate a corresponding timing advance amount according to a corresponding granularity.

[0195] In one embodiment, the indication granularity is determined according to a configured timing advance deviation threshold value; wherein the timing advance deviation threshold is used to determine whether to trigger a timing advance report.

[0196] In one embodiment, the indication granularity includes at least one of the following: one or more time units; one or more symbols; one or more time slots; one or more subframes or frames; a combination of one or more subcarrier spacings and one or more time units; a combination of one or more subcarrier spacings and one or more symbols; a combination of one or more subcarrier spacings and one or more time slots; a combination of one or more subcarrier spacings and one or more subframes or frames.

[0197] In one embodiment, the priority of the transmission of the colliding resource types satisfies at least one of the following conditions:

[0198] Condition 1: The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; Condition 2: The priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; Condition 3: The priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; Condition 4: The priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0199] In one embodiment, the priority of the transmission of the resource type that collides meets the condition one or the condition two, but the priority of the first designated resource type is higher than the priority of the resources of the first transmission direction of the first configuration type or the second configuration type; the first designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0200] In one embodiment, the priority of transmission of the resource type in which the collision occurs satisfies the condition three or the condition four, but the priority of the second designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the second designated resource type includes at least one of the following: a physical downlink control channel PDCCH configured in a common search space set; a channel state information reference signal CSI-RS; a synchronization signal block SSB; and a system information block.

[0201] In one embodiment, the priority of the transmission of the resource type that collides is configured or indicated by at least one of received system information, RRC signaling, MAC CE signaling, or DCI.

[0202] In one embodiment, the configured or indicated priority of the transmission of the colliding resource type includes at least one of the following:

[0203] The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; the priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; the priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; the priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0204] In one embodiment, when the communication node does not receive the configuration or indication of the priority of the colliding resource type transmission, or the service node does not configure or indicate the priority of the colliding resource type transmission, the priority of the colliding resource type transmission is the default priority.

[0205] In one embodiment, the priority of the transmission of the resource type in which the collision occurs is determined according to the received configuration or indication, but the priority of the third designated resource type is higher than the priority of the resources of the first transmission direction of the first configuration type or the second configuration type; the third designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0206] In one embodiment, the priority of the transmission of the resource type that collides is determined according to the received configuration or indication, but the priority of the transmission of the fourth designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the fourth designated resource type includes at least one of the following: physical downlink control channel PDCCH configured in a common search space set; channel state information reference signal CSI-RS; synchronization signal block SSB; system information block.

[0207] In one embodiment, the apparatus further includes: a transmission module configured to:

[0208] In the case that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, whether to transmit or not transmit each resource that collides is determined according to the time sequence of the resources.

[0209] In one embodiment, the apparatus further includes: a transmission module configured to:

[0210] When one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the same configuration type that collided is transmitted or not, and then determine whether each resource of the different configuration types that collided is transmitted or not.

[0211] In one embodiment, the apparatus further includes: a transmission module configured to:

[0212] When one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the colliding different configuration types is transmitted or not, and then determine whether each resource of the colliding same configuration type is transmitted or not.

[0213] In one embodiment, the apparatus further includes: a transmission module configured to:

[0214] When one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the colliding first configuration type is transmitted or not, and then determine whether each resource of the colliding second configuration type is transmitted or not.

[0215] In one embodiment, the apparatus further includes: a transmission module configured to:

[0216] In the event that one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, first determine whether the resources in the first transmission direction of the first configuration type that collided and each resource in the second transmission direction of the second configuration type are transmitted or not, and then determine whether the resources in the first transmission direction of the second configuration type that collided and each resource in the second transmission direction of the first configuration type are transmitted or not.

[0217] In one embodiment, the apparatus further includes: a transmission module configured to:

[0218] In the case that one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, the one or more resources in the first transmission direction are transmitted, and the multiple resources in the second transmission direction are not transmitted.

[0219] In one embodiment, the apparatus further includes: a transmission module configured to:

[0220] In the case that one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, the resources of the multiple second transmission directions are transmitted, and the one or more resources of the first transmission direction are not transmitted.

[0221] In one embodiment, the device also includes: a transmission module, which is configured to determine whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the number of transmissions of the resources of the first transmission direction and the number of transmissions of the resources of the second transmission direction when one or more resources of the first transmission direction collide with one or more resources of the second transmission direction.

[0222] In one embodiment, the device also includes: a transmission module, which is configured to determine whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the total resources occupied by the resources of the first transmission direction and the total resources occupied by the resources of the second transmission direction when one or more resources of the first transmission direction collide with one or more resources of the second transmission direction.

[0223] In one embodiment, the apparatus further includes: a transmission module configured to:

[0224] In the event that a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resource in the first transmission direction and the resources in the multiple second transmission directions have the same transmission priority, one of the following is used to determine whether to transmit the colliding resource:

[0225] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction.

[0226] In one embodiment, the apparatus further includes: a transmission module configured to:

[0227] In the case where a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resources in the multiple second transmission directions include resources having the same transmission priority as the resources in the first transmission direction and resources having different transmission priorities from the resources in the first transmission direction, one of the following is used to determine whether to transmit the colliding resources:

[0228] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction; or, first determine whether to transmit or not transmit each resource that has the same transmission priority as the resources of the first transmission direction, and then determine whether to transmit or not transmit each resource that has a different transmission priority from the resources of the first transmission direction.

[0229] In one embodiment, the resource configuration type includes dynamic scheduling and semi-static configuration; the resource transmission direction includes uplink transmission and downlink reception.

[0230] The resource determination device proposed in this embodiment and the resource determination method applied to the communication node proposed in the above embodiment belong to the same concept. The technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same effect as executing the resource determination method.

[0231] The present application also provides a resource determination device. FIG15 is a schematic diagram of the structure of a resource determination device provided by an embodiment. As shown in FIG15, the resource determination device is applied to a service node and includes:

[0232] The information determination module 410 is configured to determine resource configuration information, wherein the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the transmission of the resource type in which the collision occurs, and the timing advance is indicated to the service node by the communication node through the timing advance field in the timing advance report; the resource determination module 420 is configured to determine the transmission resources with the communication node based on the resource configuration information.

[0233] In one embodiment, the indication granularity is determined by the serving node and indicated to the communication node through at least one of the following: system information, RRC signaling, MAC CE signaling, and DCI.

[0234] In one embodiment, the priority of the transmission of the colliding resource type is determined by the serving node and configured or indicated through at least one of system information, RRC signaling, MAC CE signaling and DCI.

[0235] In one embodiment, the indication granularity is indicated by a reserved bit field in a timing advance report.

[0236] In one embodiment, the indication granularity includes at least two granularities; and the timing advance is the sum of the timing advances corresponding to each granularity.

[0237] In one embodiment, the timing advance field includes at least two parts, each part is used to indicate a corresponding timing advance amount according to a corresponding granularity.

[0238] In one embodiment, the indication granularity is determined according to a configured timing advance deviation threshold value; wherein the timing advance deviation threshold is used to determine whether to trigger a timing advance report.

[0239] In one embodiment, the indication granularity includes at least one of the following: one or more time units; one or more symbols; one or more time slots; one or more subframes or frames; a combination of one or more subcarrier spacings and one or more time units; a combination of one or more subcarrier spacings and one or more symbols; a combination of one or more subcarrier spacings and one or more time slots; a combination of one or more subcarrier spacings and one or more subframes or frames.

[0240] In one embodiment, the priority of the transmission of the colliding resource type satisfies at least one of the following conditions:

[0241] Condition 1: The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; Condition 2: The priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; Condition 3: The priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; Condition 4: The priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0242] In one embodiment, the priority of the transmission of the resource type in which the collision occurs satisfies the condition one or the condition two, but the priority of the first designated resource type is higher than the priority of the resources of the first transmission direction of the first configuration type or the second configuration type; the first designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0243] In one embodiment, the priority of transmission of the resource type in which the collision occurs satisfies the condition three or the condition four, but the priority of the second designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the second designated resource type includes at least one of the following: a physical downlink control channel PDCCH configured in a common search space set; a channel state information reference signal CSI-RS; a synchronization signal block SSB; and a system information block.

[0244] In one embodiment, the priority of the transmission of the resource type that collides is configured or indicated by at least one of received system information, RRC signaling, MAC CE signaling, or DCI.

[0245] In one embodiment, the configured or indicated priority of the transmission of the colliding resource type includes at least one of the following:

[0246] The priority of the resource type of the first transmission direction of the first configuration type is higher than the priority of the resource type of the second transmission direction of the first configuration type; the priority of the resource type of the first transmission direction of the second configuration type is higher than the priority of the resource type of the second transmission direction of the second configuration type; the priority of the resource type of the second transmission direction of the first configuration type is higher than the priority of the resource type of the first transmission direction of the first configuration type; the priority of the resource type of the second transmission direction of the second configuration type is higher than the priority of the resource type of the first transmission direction of the second configuration type.

[0247] In one embodiment, when the communication node does not receive the configuration or indication of the priority of the colliding resource type transmission, or the service node does not configure or indicate the priority of the colliding resource type transmission, the priority of the colliding resource type transmission is the default priority.

[0248] In one embodiment, the priority of the transmission of the resource type in which the collision occurs is determined according to the received configuration or indication, but the priority of the third designated resource type is higher than the priority of the resources of the first transmission direction of the first configuration type or the second configuration type; the third designated resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0249] In one embodiment, the priority of the transmission of the resource type that collides is determined according to the received configuration or indication, but the priority of the transmission of the fourth designated resource type is higher than the priority of the resources of the second transmission direction of the first configuration type or the second configuration type; the fourth designated resource type includes at least one of the following: physical downlink control channel PDCCH configured in a common search space set; channel state information reference signal CSI-RS; synchronization signal block SSB; system information block.

[0250] In one embodiment, the device further includes: a transmission module configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources.

[0251] In one embodiment, the device also includes: a transmission module, which is configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the same configuration type that collided is transmitted or not, and then determine whether each resource of the different configuration types that collided is transmitted or not.

[0252] In one embodiment, the device also includes: a transmission module, which is configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the different configuration types that collided is transmitted or not, and then determine whether each resource of the same configuration type that collided is transmitted or not.

[0253] In one embodiment, the device also includes: a transmission module, which is configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, first determine whether each resource of the first configuration type that collides is transmitted or not, and then determine whether each resource of the second configuration type that collides is transmitted or not.

[0254] In one embodiment, the device also includes: a transmission module, which is configured to: in the event that resources in the first transmission direction collide with resources in the second transmission direction multiple times, first determine whether the resources in the first transmission direction of the first configuration type that collided and each resource in the second transmission direction of the second configuration type are transmitted or not, and then determine whether the resources in the first transmission direction of the second configuration type that collided and each resource in the second transmission direction of the first configuration type are transmitted or not.

[0255] In one embodiment, the device further includes: a transmission module configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, transmit the one or more resources of the first transmission direction and not transmit the multiple resources of the second transmission direction.

[0256] In one embodiment, the device also includes: a transmission module, configured to: when one or more resources of the first transmission direction collide with multiple resources of the second transmission direction, transmit the multiple resources of the second transmission direction and not transmit the one or more resources of the first transmission direction.

[0257] In one embodiment, the device also includes: a transmission module, which is configured to determine whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the number of transmissions of the resources of the first transmission direction and the number of transmissions of the resources of the second transmission direction when one or more resources of the first transmission direction collide with one or more resources of the second transmission direction.

[0258] In one embodiment, the method also includes: a transmission module, configured to determine whether to transmit the resources of the first transmission direction or the resources of the second transmission direction based on the total resources occupied by the resources of the first transmission direction and the total resources occupied by the resources of the second transmission direction when one or more resources of the first transmission direction collide with one or more resources of the second transmission direction.

[0259] In one embodiment, the apparatus further includes: a transmission module configured to, when a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resource in the first transmission direction and the resource in the multiple second transmission directions have the same transmission priority, determine whether to transmit or not transmit the colliding resource by using one of the following:

[0260] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction.

[0261] In one embodiment, the apparatus further includes: a transmission module configured to: when a resource in a first transmission direction collides with resources in multiple second transmission directions, and the resources in the multiple second transmission directions include resources having the same transmission priority as the resource in the first transmission direction and resources having different transmission priorities as the resource in the first transmission direction, determine whether to transmit or not transmit the colliding resource by using one of the following:

[0262] Determine whether to transmit or not transmit each resource that collides according to the time sequence of the resources; or, transmit the resources of the first transmission direction, and do not transmit the resources of the multiple second transmission directions; or, transmit the resources of the multiple second transmission directions, and do not transmit the resources of the first transmission direction; or, uniformly determine whether to transmit or not transmit each resource of the second transmission direction; or, first determine whether to transmit or not transmit each resource that has the same transmission priority as the resources of the first transmission direction, and then determine whether to transmit or not transmit each resource that has a different transmission priority from the resources of the first transmission direction.

[0263] In one embodiment, the resources of multiple first transmission directions are equivalent to the resources of the one first transmission direction.

[0264] In one embodiment, the transmission type of resources in a first transmission direction after the resources in multiple first transmission directions are equivalent is determined by at least one of the following: the transmission type with the highest transmission type priority among the resources in the multiple first transmission directions; or the transmission type with the largest total number of occupied resources among the resources in the multiple first transmission directions; wherein the occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0265] In one embodiment, the resource configuration type includes dynamic scheduling and semi-static configuration; the resource transmission direction includes uplink transmission and downlink reception.

[0266] The resource determination device proposed in this embodiment and the resource determination method applied to the service node proposed in the above embodiment belong to the same concept. The technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same effect as executing the resource determination method.

[0267] An embodiment of the present application also provides a communication node. Figure 16 is a schematic diagram of the hardware structure of a communication node provided by an embodiment. As shown in Figure 16, the communication node provided by the present application includes a processor 510 and a memory 520; the processor 510 in the communication node can be one or more, and Figure 16 takes one processor 510 as an example; the memory 520 is configured to store one or more programs; the one or more programs are executed by the one or more processors 510, so that the one or more processors 510 implement the resource determination method as described in the embodiment of the present application.

[0268] The communication node further includes: a communication device 530 , an input device 540 and an output device 550 .

[0269] The processor 510, memory 520, communication device 530, input device 540 and output device 550 in the communication node may be connected via a bus or other means. FIG16 takes the bus connection as an example.

[0270] The input device 540 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the communication node. The output device 550 may include a display device such as a display screen.

[0271] The communication device 530 may include a receiver and a transmitter. The communication device 530 is configured to perform information transmission and reception communication according to the control of the processor 510.

[0272] The memory 520, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the resource determination method described in the embodiments of the present application (for example, the information determination module 310 and the resource determination module 320 in the resource determination device). The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; and the data storage area may store data created according to the use of the communication node, etc. In addition, the memory 520 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include a memory remotely located relative to the processor 510, and these remote memories may be connected to the communication node via a network. Examples of the above-mentioned network include the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0273] An embodiment of the present application also provides a service node. Figure 17 is a schematic diagram of the hardware structure of a service node provided by an embodiment. As shown in Figure 17, the service node provided by the present application includes a processor 610 and a memory 620; the processor 610 in the service node can be one or more, and Figure 17 takes one processor 610 as an example; the memory 620 is configured to store one or more programs; the one or more programs are executed by the one or more processors 610, so that the one or more processors 610 implement the resource determination method as described in the embodiment of the present application.

[0274] The service node further includes: a communication device 630 , an input device 640 and an output device 650 .

[0275] The processor 610, memory 620, communication device 630, input device 640 and output device 650 in the service node may be connected via a bus or other means. FIG17 takes the bus connection as an example.

[0276] The input device 640 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the service node. The output device 650 may include a display device such as a display screen.

[0277] The communication device 630 may include a receiver and a transmitter. The communication device 630 is configured to perform information transmission and reception communication according to the control of the processor 610.

[0278] The memory 620, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the resource determination method described in the embodiments of the present application (for example, the information determination module 410 and the resource determination module 420 in the resource determination device). The memory 620 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the service node, etc. In addition, the memory 620 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 620 may further include a memory remotely located relative to the processor 610, and these remote memories may be connected to the service node via a network. Examples of the above-mentioned network include the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0279] An embodiment of the present application also provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, it implements any resource determination method described in the embodiment of the present application. The method includes: determining resource configuration information, wherein the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the transmission of the resource type that collides, and the timing advance is indicated by the communication node to the service node through the timing advance field in the timing advance report; determining the transmission resources with the service node based on the resource configuration information. Alternatively, the method includes: determining resource configuration information, wherein the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the transmission of the resource type that collides, and the timing advance is indicated by the communication node to the service node through the timing advance field in the timing advance report; determining the transmission resources with the communication node based on the resource configuration information.

[0280] The embodiment of the present application also provides a computer program product, including a computer program / instruction, which implements the resource determination method described in any one of the embodiments of the present application when executed by a processor. The method includes: determining resource configuration information, the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the resource type transmission that collides, the timing advance is indicated by the communication node to the service node through the timing advance field in the timing advance report; determining the transmission resources with the service node based on the resource configuration information. Alternatively, the method includes: determining resource configuration information, the resource configuration information includes the indication granularity of the timing advance of the target frame and / or the priority of the resource type transmission that collides, the timing advance is indicated by the communication node to the service node through the timing advance field in the timing advance report; determining the transmission resources with the communication node based on the resource configuration information.

[0281] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media.Computer-readable media can be computer-readable signal media or computer-readable storage media.Computer-readable storage media can be, for example: electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or components, or any combination of the above.More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM), flash memories, optical fibers, portable CD-ROMs, optical storage devices, magnetic storage devices, or any suitable combination of the above.Computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0282] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. This propagated data signal may take a variety of forms, including electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0283] The program code contained on the computer-readable medium can be transmitted using any appropriate medium, including wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.

[0284] The computer program code for performing the operations of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and also conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect via the Internet).

[0285] An embodiment of the present application further provides a computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the video encoding method as described in any of the above embodiments.

[0286] The above description is merely an exemplary embodiment of the present application and is not intended to limit the scope of protection of the present application.

[0287] It will be understood by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processor, a portable web browser or a vehicle-mounted mobile station.

[0288] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0289] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0290] The block diagram of any logical flow in the drawings of the present application may represent program operations, or may represent interconnected logical circuits, modules and functions, or may represent a combination of program operations and logical circuits, modules and functions. A computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as read-only memory (ROM), random access memory (RAM), optical storage devices and systems (digital versatile discs (DVD) or compact disks (CD), etc.). Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable for the local technical environment, such as a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FPGA), and a processor based on a multi-core processor architecture.

Claims

1. A resource determination method, applied to a communication node, includes: Determine resource configuration information, where the resource configuration information includes at least one of an indication granularity of a timing advance amount of a target frame and a priority of transmission of a resource type that has a collision, and the timing advance amount is indicated by the communication node to a serving node through a timing advance field in a timing advance report; Determine transmission resources with the serving node according to the resource configuration information.

2. The method according to claim 1, wherein, The indication granularity is determined according to an indication received from the serving node; the indication includes at least one of the following: system information, radio resource control (RRC) signaling, medium access control (MAC) control element (CE) signaling, downlink control information (DCI).

3. The method according to claim 1, wherein, The indication granularity is indicated through a reserved bit field in the timing advance report.

4. The method according to claim 1, wherein The indication granularity includes at least two granularities; The timing advance amount is the sum of the timing advance amounts corresponding to each granularity.

5. The method according to claim 1 or 4, wherein The timing advance field includes at least two parts, and each part is used to indicate a corresponding timing advance amount according to a corresponding one of the granularities.

6. The method according to claim 1, wherein, The indication granularity is determined according to a value of a configured timing advance amount deviation threshold; where the timing advance amount deviation threshold is used to determine whether to trigger a timing advance report.

7. The method according to claim 1, wherein The indication granularity includes at least one of the following: At least one time unit; at least one symbol; at least one time slot; at least one subframe or frame; a combination of at least one subcarrier spacing and at least one time unit; a combination of at least one subcarrier spacing and at least one symbol; a combination of at least one subcarrier spacing and at least one time slot; a combination of at least one subcarrier spacing and at least one subframe or frame.

8. The method according to claim 1, wherein, The priority of transmission of the resource type that has a collision satisfies at least one of the following conditions: Condition 1: The priority of the resource type in the first transmission direction of the first configuration type is higher than the priority of the resource type in the second transmission direction of the first configuration type; Condition 2: The priority of the resource type in the first transmission direction of the second configuration type is higher than the priority of the resource type in the second transmission direction of the second configuration type; Condition 3: The priority of the resource type in the second transmission direction of the first configuration type is higher than the priority of the resource type in the first transmission direction of the first configuration type; Condition 4: The priority of the resource type in the second transmission direction of the second configuration type is higher than the priority of the resource type in the first transmission direction of the second configuration type.

9. The method according to claim 8, wherein, The priority of transmission of the resource type that has a collision satisfies Condition 1 or Condition 2, and the priority of the first specified resource type is higher than the priority of the resources in the first transmission direction of the first configuration type or the second configuration type; The first specified resource type includes at least one of the following: physical random access channel (PRACH); message A physical uplink shared channel (MsgA PUSCH); physical uplink control channel (PUCCH).

10. The method according to claim 8, wherein, The priority of transmission of the resource type that has a collision satisfies Condition 3 or Condition 4, and the priority of the second specified resource type is higher than the priority of the resources in the second transmission direction of the first configuration type or the second configuration type; The second specified resource type includes at least one of the following: a physical downlink control channel PDCCH configured for a common search space set; a channel state information reference signal CSI-RS; a synchronization signal block SSB; a system information block.

11. The method according to claim 1, wherein, The transmission priority of the collided resource type is configured or indicated by at least one of the received system information, RRC signaling, MAC CE signaling, or DCI.

12. The method according to claim 1, wherein The configured or indicated transmission priority of the collided resource type includes at least one of the following: The priority of the resource type in the first transmission direction of the first configuration type is higher than the priority of the resource type in the second transmission direction of the first configuration type; The priority of the resource type in the first transmission direction of the second configuration type is higher than the priority of the resource type in the second transmission direction of the second configuration type; The priority of the resource type in the second transmission direction of the first configuration type is higher than the priority of the resource type in the first transmission direction of the first configuration type; The priority of the resource type in the second transmission direction of the second configuration type is higher than the priority of the resource type in the first transmission direction of the second configuration type.

13. The method according to claim 1, wherein In response to the communication node not receiving the configuration or indication of the transmission priority of the collided resource type, or the serving node not configuring or indicating the transmission priority of the collided resource type, the transmission priority of the collided resource type is the default priority.

14. The method according to claim 11 or 12, wherein The transmission priority of the collided resource type is determined according to the received configuration or indication, and the priority of the third specified resource type is higher than the priority of the resources in the first transmission direction of the first configuration type or the second configuration type; The third specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

15. The method according to claim 11 or 12, wherein The transmission priority of the collided resource type is determined according to the received configuration or indication, and the priority of the fourth specified resource type for transmission is higher than the priority of the resources in the second transmission direction of the first configuration type or the second configuration type; The fourth specified resource type includes at least one of the following: a PDCCH configured for a common search space set; CSI-RS; SSB; a system information block.

16. The method according to claim 1, further comprising: In response to at least one resource in the first transmission direction colliding with multiple resources in the second transmission direction, determine whether each collided resource is transmitted or not in chronological order of the resources.

17. The method according to claim 1, further comprising: In response to at least one resource in the first transmission direction colliding with multiple resources in the second transmission direction, first determine whether each collided resource of the same configuration type is transmitted or not, and then determine whether each collided resource of different configuration types is transmitted or not.

18. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in multiple second transmission directions, first determine whether each resource of different configuration types that has collided is to be transmitted or not, and then determine whether each resource of the same configuration type that has collided is to be transmitted or not.

19. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in multiple second transmission directions, first determine whether each resource of the first configuration type that has collided is to be transmitted or not, and then determine whether each resource of the second configuration type that has collided is to be transmitted or not.

20. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in multiple second transmission directions, first determine whether each resource of the first transmission direction of the first configuration type and each resource of the second transmission direction of the second configuration type that has collided is to be transmitted or not, and then determine whether each resource of the first transmission direction of the second configuration type and each resource of the second transmission direction of the first configuration type that has collided is to be transmitted or not.

21. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in multiple second transmission directions, transmit the resources in the at least one first transmission direction and do not transmit the resources in the multiple second transmission directions.

22. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in multiple second transmission directions, transmit the resources in the multiple second transmission directions and do not transmit the resources in the at least one first transmission direction.

23. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in one or more second transmission directions, determine whether to transmit the resources in the first transmission direction or the resources in the second transmission direction according to the number of transmissions of the resources in the first transmission direction and the number of transmissions of the resources in the second transmission direction.

24. The method according to claim 1, further comprising: In response to a collision between resources in at least one first transmission direction and resources in one or more second transmission directions, determine whether to transmit the resources in the first transmission direction or the resources in the second transmission direction according to the total sum of the resources occupied by the resources in the first transmission direction and the total sum of the resources occupied by the resources in the second transmission direction.

25. The method according to claim 1, further comprising: In response to a collision between a resource in one first transmission direction and resources in multiple second transmission directions, and the resource in the first transmission direction and the resources in the multiple second transmission directions having the same transmission priority, use one of the following to determine whether the collided resources are to be transmitted or not: Determine whether each collided resource is to be transmitted or not in chronological order of the resources; Transmit the resource in the first transmission direction and do not transmit the resources in the multiple second transmission directions; Transmit the resources in the multiple second transmission directions and do not transmit the resource in the first transmission direction; Uniformly determine whether each resource in the second transmission direction is to be transmitted or not.

26. The method according to claim 1, further comprising: In response to a collision occurring between resources in a first transmission direction once and resources in a second transmission direction multiple times, and the resources in the second transmission direction multiple times including resources with the same transmission priority as the resources in the first transmission direction and resources with different transmission priorities from the resources in the first transmission direction, one of the following is used to determine whether the collided resources are transmitted or not: Determine whether each collided resource is transmitted or not according to the chronological order of the resources; Transmit the resources in the first transmission direction and do not transmit the resources in the second transmission direction multiple times; Transmit the resources in the second transmission direction multiple times and do not transmit the resources in the first transmission direction; Uniformly determine whether each resource in the second transmission direction is transmitted or not; First determine whether each resource with the same transmission priority as the resources in the first transmission direction is transmitted or not, and then determine whether each resource with a different transmission priority from the resources in the first transmission direction is transmitted or not.

27. The method according to any one of claims 16-26, wherein, Resources in the first transmission direction multiple times are equivalent to resources in the first transmission direction once.

28. The method according to claim 27, wherein, The transmission type of the resources in the first transmission direction once after equivalence of the resources in the first transmission direction multiple times is determined by at least one of the following: the transmission type with the highest transmission priority among the resources in the first transmission direction multiple times; or the transmission type with the largest total number of occupied resources among the resources in the first transmission direction multiple times; The occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, space domain resources.

29. The method according to any one of claims 8 - 13 and 16 - 26, wherein, The configuration type of the resources includes dynamic scheduling and semi-static configuration; the transmission direction of the resources includes uplink transmission and downlink reception.

30. A method for resource determination, applied to a serving node, includes: Determine resource configuration information, where the resource configuration information includes at least one of the indication granularity of the timing advance of the target frame and the transmission priority of the collided resource type, and the timing advance is indicated by a communication node to the serving node through the timing advance field in the timing advance report; Determine the transmission resources with the communication node according to the resource configuration information.

31. The method according to claim 30, wherein, The indication granularity is determined by the serving node and indicated to the communication node through at least one of the following: system information, radio resource control (RRC) signaling, medium access control (MAC) control element (CE) signaling, downlink control information (DCI).

32. The method according to claim 30, wherein, The transmission priority of the collided resource type is determined by the serving node and configured or indicated through at least one of system information, RRC signaling, MAC CE signaling, and DCI.

33. A communication node, comprising: A memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the resource determination method according to any one of claims 1-29.

34. A service node, comprising: A memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the resource determination method according to any one of claims 30-32.

35. A computer-readable storage medium stores a computer program, and when the program is executed by a processor, it implements the resource determination method described in any one of claims 1-32.

Images