Resource determination method, communication node and storage medium

Abstract

The invention provides a resource determination method, a communication node and a storage medium. The method comprises: determining resource configuration information, the resource configuration information comprising an indication granularity of a timing advance of a target frame and / or a priority of collision-occurring resource type transmission, the timing advance being indicated to a service node by a communication node through a timing advance domain in a timing advance report; and determining a transmission resource with the service node according to the resource configuration information.

Description

Technical Field

[0001] This application relates to the field of wireless communication technologies, and for example, relates 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 (NTNs). 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. 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 pre-compensation value of the UE, 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 and affecting the reliability of uplink and downlink transmissions. Summary of the Invention

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

[0004] An embodiment of this application provides a resource determination method applied to a communication node, including:

[0005] Determine resource configuration information, where the resource configuration information includes the indication granularity of the timing advance amount of a target frame and / or the priority of transmissions of resource types that collide, 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;

[0006] Determine transmission resources with the serving node according to the resource configuration information.

[0007] An embodiment of this application also provides a resource determination method applied to a serving node, including:

[0008] Determine resource configuration information, where the resource configuration information includes the indication granularity of the timing advance amount of a target frame and / or the priority of transmissions of resource types that collide, 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;

[0009] Determine transmission resources with the communication node according to the resource configuration information.

[0010] An embodiment of this application also provides a communication node, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the program, the above-mentioned resource determination method is implemented.

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

[0012] 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

[0013] Figure 1 A schematic diagram of an NTN communication provided for an embodiment;

[0014] Figure 2 A schematic diagram of a timing advance report based on MAC CE provided for an embodiment;

[0015] Figure 3 A flowchart of a resource determination method provided for an embodiment;

[0016] Figure 4 A schematic diagram of resource collision provided for an embodiment;

[0017] Figure 5 Another schematic diagram of resource collision provided for an embodiment;

[0018] Figure 6 Another schematic diagram of resource collision provided for an embodiment;

[0019] Figure 7 Another schematic diagram of resource collision provided for an embodiment;

[0020] Figure 8 Another schematic diagram of resource collision provided for an embodiment;

[0021] Figure 9 Another schematic diagram of resource collision provided for an embodiment;

[0022] Figure 10 Another schematic diagram of resource collision provided for an embodiment;

[0023] Figure 11 Another schematic diagram of resource collision provided for an embodiment;

[0024] Figure 12 Another schematic diagram of resource collision provided for an embodiment;

[0025] Figure 13 A flowchart of another resource determination method provided for an embodiment;

[0026] Figure 14 Structural schematic diagram of a resource determination device provided for an embodiment;

[0027] Figure 15 Structural schematic diagram of another resource determination device provided for an embodiment;

[0028] Figure 16 Hardware structural schematic diagram of a communication node provided for an embodiment;

[0029] Figure 17 Hardware structural schematic diagram of a service node provided for an embodiment. Detailed implementation manners

[0030] The present application will be described below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present application, rather than limiting the present application. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. Additionally, it should be noted that, for the sake of description, only the parts related to the present application rather than all the structures are shown in the drawings.

[0031] Figure 1 Schematic diagram of an NTN communication provided for an embodiment. As Figure 1 shown, in the NTN communication system, the link between the communication node (also referred to as the user-side device, such as a UE) and the satellite is the service link, and the link between the service node (also referred to as the access network device or network-side device, such as a base station, access point or gateway station, etc.) and the satellite is the feeder link, and it is common for all UEs (such as Figure 1 the UE1 and UEx shown) in the same cell. In the embodiments of the present application, the communication node can be taken as an example of a UE, and the service node can be taken as an example of a base station for illustration.

[0032] In NTN, the UE can perform TA pre-compensation based on information such as satellite position, its own position, and common TA. Since the position of the UE is usually unknown at the network node, the base station may not know the TA value at the UE. In order to enable the network node to perform more reliable and efficient scheduling, the UE can report the TA value.

[0033] In one scenario, the basic granularity of the Timing Advance Report (TAR) can be 1 time slot corresponding to a 15 kHz subcarrier spacing, that is, 1 ms. Therefore, there is an uncertain TA deviation of about 1 ms between the base station and the UE. It can be seen that the base station does not know the actual position of the TA within 1 ms. In order to avoid collisions between downlink reception and uplink transmission, the base station often needs to adopt a very conservative scheduling, reserving sufficient bandwidth, resulting in waste of time-frequency resources.

[0034] In one scenario, the common TA from the satellite to the reference point RP is an integer ranging from 0 to 66485757, with the unit of 4.072×10-3 μs, which corresponds to 0 to 270.73 ms. Converted to symbols corresponding to 15 kHz, it is approximately: 270 * 12 = 3780 symbols. Therefore, the maximum round-trip time (RTT) from the UE to the reference point RP (corresponding to a geostationary earth orbit (GEO) satellite) is approximately 540 ms. Converted to symbols corresponding to 15 kHz, it is approximately: 540 * 14 = 7560 symbols. Therefore, the maximum value of TA is approximately: 7560 symbols.

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

[0036] On this basis, the embodiment 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 overly coarse NTN TAR granularity (currently 1 time slot of 15 kHz, that is, 1 ms), and providing corresponding solutions in the case of conflicts or collisions in uplink and downlink resources.

[0037] Figure 3 A flowchart of a resource determination method provided for an embodiment. This method can be applied to a communication node, and the communication node can be a user-side device, such as a UE, which can be a reduced capability (RedCap) UE. As Figure 3 shown, the method provided in this embodiment includes step 110 and step 120.

[0038] In step 110, determine resource configuration information, where the resource configuration information includes the indication granularity of the timing advance amount of the target frame and / or the priority of the transmission of the resource type that has a collision, and the timing advance amount is indicated by the communication node to the serving node through the timing advance field in the timing advance report.

[0039] In step 120, determine the transmission resources with the serving node according to the resource configuration information.

[0040] In this embodiment, the communication node may determine the indication granularity of the timing advance (which may also be referred to as the granularity of TAR) according to the configuration or indication of the serving node, may also autonomously determine the granularity of TAR, or may uniquely determine the granularity of TAR according to the standard protocol (for example, a symbol). In this case, multiple TAR granularities may coexist, 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. The communication node may report the TA based on one of the TAR granularities, improving the flexibility and accuracy of TA reporting, so that the serving node can more accurately know the actual location of the communication node and perform more accurate timing alignment, aiming to avoid resource collisions. In addition, in the case of resource collisions, the resources to be transmitted and the resources not to be transmitted may also be determined according to the transmission priorities of the resource types where the collisions occur, resolving the collisions and improving the reliability of communication.

[0041] In one embodiment, the indication granularity is determined according to the indication received from the serving node; the indication of 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, downlink control information (DCI).

[0042] In this embodiment, the serving node may indicate the granularity of 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 TAR. The indication of the subcarrier spacing is mainly for the case where the granularity of TAR is a logical time unit such as a time slot, symbol, and / or subframe. For the case where the granularity of TAR is an absolute time unit, it is usually not necessary to notify the subcarrier spacing.

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

[0044] In this embodiment, the UE may determine or select the granularity of TAR by itself. For example, in the MAC CE, the reserved bit field (as Figure 2 shown, labeled as R) is used to indicate the granularity of TAR. Assume that this reserved bit field R is relabeled as G. G = 0 may indicate that the TAR granularity is a time slot, that is, the number of time slots reported by TAR; G = 1 may indicate that the TAR granularity is a symbol, that is, the number of symbols reported by TAR. Or, G = 0 may indicate that the TAR granularity is a symbol, and G = 1 indicates that the TAR granularity is a time slot, etc.

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

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

[0047] In one embodiment, the timing advance field includes at least two parts, and each part is used to indicate the corresponding timing advance according to a corresponding one of the granularities.

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

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

[0050] In this embodiment, if any of the following events is satisfied, the TAR can be triggered:

[0051] Event 1: Trigger a TA report based on a high-layer indication;

[0052] Event 2: When the UE does not report the TA value to the current serving cell under the condition of the high-layer configured TA deviation threshold (offsetThresholdTA);

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

[0054] The value of the TA deviation threshold (offsetThresholdTA) in the existing protocol ranges from 0.5 ms to 15 ms, and this value range matches the previous TA reporting based on a 1 ms granularity. In this embodiment, the TA deviation threshold range is adjusted accordingly to adapt to a finer-grained TA reporting.

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

[0056] 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 serving node is the configuration value in the existing protocol above, or a value in units of ms, then when the communication node reports the TA, the granularity used can be a time slot; if the TA deviation threshold configuration value configured by the serving node is a newly introduced configuration value, or a value in units of symbols, then when the communication node reports the TA, the granularity used can be a symbol.

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

[0058] In one embodiment, the indicated 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.

[0059] 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:

[0060] Case1: Collision between dynamically scheduled downlink (DL) reception and semi-statically configured uplink (UL) transmission;

[0061] Case2: Collision between semi-statically configured DL reception and dynamically scheduled UL transmission;

[0062] Case3: Collision between semi-statically configured DL reception and semi-statically configured UL transmission;

[0063] Case4: Collision between dynamically scheduled DL reception and dynamically scheduled UL transmission;

[0064] Case5: Collision between configured SSB and dynamically scheduled / semi-statically configured UL transmission;

[0065] Case6: Collision between dynamic or semi-static downlink and valid random access occasion (RO).

[0066] The dynamic scheduling in the above cases refers to the reception or transmission scheduled or indicated by DCI. For example, DL can be the physical downlink shared channel (PDSCH), such as SIB19 or the channel state information-reference signal (CSI-RS), and UL can be the physical uplink shared channel (PUSCH), the physical uplink control channel (PUCCH), the physical random access channel (PRACH), or the sounding reference signal (SRS); the semi-static configuration refers to the reception or transmission configured by high-layer parameters. For example, DL can be the PDCCH, PDSCH, SSB, CSI-RS, or DL-PRS, and UL can be the PUCCH, PUSCH, or SRS.

[0067] The collisions in the above cases include: two types of signals (e.g., DL reception and UL transmission) collide due to overlapping time-frequency resources, and / or, although the time-frequency resources of the two types of signals do not overlap, but there is not enough up-down link switching time between them, resulting in collisions. For example, after DL reception, at least N Rx-Tx ·T c intervals are required to avoid collisions before UL transmission; after UL transmission, at least N Tx-Rx ·T c intervals are required to avoid collisions before DL reception. Wherein, T c is the basic time unit of the access technology, and N Rx-Tx 、N Tx-Rx are the number of basic time units required to switch from reception to transmission and from transmission to reception respectively.

[0068] For Case3 and Case4, the communication node does not expect to perform semi-statically configured DL reception and semi-statically configured UL transmission simultaneously, or does not expect to perform dynamically scheduled DL reception and dynamically scheduled UL transmission simultaneously. Accordingly, the serving node will not perform such configuration or scheduling. For HD-FDD or TDD UE, Case3 or Case4 can be enhanced accordingly.

[0069] In one embodiment, the transmission priorities of the resource types that collide satisfy at least one of the following conditions:

[0070] 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;

[0071] 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;

[0072] 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;

[0073] 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.

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

[0075] 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, then the transmission priority of the resource type that has a collision satisfies at least one of the following conditions:

[0076] Condition 1: The priority of DL reception with semi-static configuration is higher than the priority of UL transmission with semi-static configuration;

[0077] Condition 2: The priority of DL reception with dynamic scheduling is higher than the priority of UL transmission with dynamic scheduling;

[0078] Condition 3: The priority of UL transmission with semi-static configuration is higher than the priority of DL reception with semi-static configuration;

[0079] Condition 4: The priority of UL transmission with dynamic scheduling is higher than the priority of DL reception with dynamic scheduling.

[0080] In one embodiment, the transmission priority of the resource type that has a collision satisfies Condition 1 or Condition 2, but 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: PRACH; Message A Physical Uplink Shared Channel (MsgA PUSCH); PUCCH.

[0081] 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 transmission priority of the resource type that has a collision satisfies Condition 1 or Condition 2, with DL having priority, and the coverage and performance of DL are preferentially guaranteed.

[0082] Condition 1: The priority of DL reception with semi-static configuration is higher than the priority of UL transmission with semi-static configuration, but there are exceptions for some special semi-static configured UL signals, such as PRACH or MsgA PUSCH triggered by a higher layer, or PUCCH (e.g., carrying HARQ or other special UL control information). Taking the PRACH triggered by a higher layer 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, and in this case, whether to receive DL or transmit UL depends on the UE implementation.

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

[0084] In one embodiment, the priority of the transmission of the resource type where a collision occurs satisfies the above Condition 3 or Condition 4, but the priority of the second specified resource type is higher than that 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: PDCCH configured by a common search space set; CSI-RS; synchronization signal block SSB; SIB.

[0085] 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 where a collision occurs satisfies Condition 3 or Condition 4, with uplink priority to ensure the coverage and performance of the uplink first.

[0086] Condition 3: The priority of UL transmission with semi-static configuration is higher than that of DL reception with semi-static configuration, except for some special DL signals with semi-static configuration, such as PDCCH configured by a common search space set (at least one of Type-0 / 0A / 0B / 1 / 2-PDCCH), CSI-RS, and / or SSB, etc. For example, when the reception of semi-statically configured PDSCH and CSI-RS collides with the transmission of semi-statically configured PUSCH and SRS, the UE preferentially transmits PUSCH and SRS and does not receive PDSCH and CSI-RS. However, when the reception of semi-statically configured Type-0 PDCCH collides with the transmission of semi-statically configured PUSCH and SRS, the UE preferentially receives Type-0 PDCCH and abandons the transmission of PUSCH and SRS.

[0087] Condition 4: The priority of UL transmission with dynamic scheduling is higher than that of DL reception with dynamic scheduling, except for some DL signals with dynamic scheduling, such as CSI-RS and / or SIB1 / 2 / .. / 19, etc. For example, when the reception of dynamically scheduled PDSCH (non-SIB) collides with the transmission of dynamically scheduled PUSCH, the UE preferentially transmits PUSCH and does not receive PDSCH. However, when the reception of SIB1 / 2 / ... / 19 collides with the transmission of PUSCH, the UE preferentially receives SIB and abandons the transmission of PUSCH.

[0088] In one embodiment, the transmission priority of the resource type in which a collision occurs is configured or indicated by at least one of the received system information, RRC signaling, MAC CE signaling, or DCI.

[0089] 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.

[0090] In one embodiment, the transmission priority of the resource type in which a collision occurs, which is configured or indicated, includes at least one of the following:

[0091] 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;

[0092] 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;

[0093] 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;

[0094] 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.

[0095] In one embodiment, when the communication node does not receive the configuration or indication of the transmission priority of the resource type in which a collision occurs, or when the serving node does not configure or indicate the transmission priority of the resource type in which a collision occurs, the transmission priority of the resource type in which a collision occurs is the default priority.

[0096] In this embodiment, when the serving node does not configure or indicate the above priorities, or when the communication node does not receive the configuration or indication from the serving node, the communication node may operate according to the default priority. The default priority may be at least one of Condition 1 to Condition 4, and the specified exception (or special) signals in these four conditions may be enabled or not, that is, for any one condition, there may or may not be an exception signal.

[0097] In one embodiment, the serving node configures or indicates the priority of 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 indicated priority does not apply to signals of some exceptional specified resource types, and the exceptional signals can refer to the above various methods. Optionally, when the serving node does not configure or indicate the above priority, or the communication node does not receive the above indication from the serving 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 downlink coverage or performance (such as SIB), DL reception can be prioritized; considering that the UL service of the RedCap communication node is dominant, UL transmission can be prioritized.

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

[0099] In this embodiment, the serving node can configure or indicate the priority of semi-statically configured DL reception and UL transmission through system information (such as SIB 19), RRC signaling, MAC CE, and / or DCI signaling, and / or configure or indicate the priority of dynamically scheduled DL reception and UL transmission, but signals of some specified resource types are exceptions, such as SIB PDSCH, PDCCH configured in the 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.

[0100] For example, the serving node can configure the priority according to Condition 1 and / or Condition 2, but signals of the specified resource types in Condition 1 and / or Condition 2 are exceptions. For instance, although the serving node configures the priority of semi-statically / dynamically scheduled DL to be higher than that of semi-statically / dynamically scheduled UL, the priority of PRACH / MsgA PUSCH and / or PUCCH is higher than that of semi-statically / dynamically scheduled UL.

[0101] In one embodiment, the priority of the resource type transmission in case of a collision is determined according to the received configuration or indication, but the priority of the fourth specified resource type transmission is higher than the priority of the resources in the second transmission direction of the first configured type or the second configured type; the fourth specified resource type includes at least one of the following: PDCCH configured for a common search space set; CSI-RS; SSB; SIB.

[0102] The serving node may perform priority configuration according to Condition 3 and / or Condition 4, but the signals of the specified resource types in Condition 3 and / or Condition 4 are exceptions. For example, although the priority of the DL configured for semi-static / dynamic scheduling is lower than the priority of the UL configured for semi-static / dynamic scheduling, the priority of SIB PDSCH, PDCCH configured for a common search space set, CSI-RS, and / or SSB is higher than the priority of the UL configured for semi-static / dynamic scheduling.

[0103] When the above DL exception signals collide with the UL exception signals, the DL exception signals can be preferentially received to ensure downlink coverage and performance; or, the UL exception signals can be preferentially sent to ensure uplink access and performance; or, it is determined by the communication node implementation whether to receive the DL exception signals or send the UL exception signals.

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

[0105] In the embodiments of the present application, one or multiple DL receptions can be equivalent to the reception of one or multiple DL signals, and one or multiple UL transmissions can be equivalent to the transmission of one or multiple UL signals. That is, the number of resource transmissions can be equivalent to the number of signal transmissions.

[0106] In one embodiment, the resources in multiple first transmission directions are equivalent to the resources in one first transmission direction. The transmission type of the resources in one first transmission direction after the equivalence of the resources in multiple first transmission directions is determined by at least one of the following: the transmission type with the highest priority among the transmission types of the resources in multiple first transmission directions; or the transmission type with the largest total number of occupied resources among the resources in 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.

[0107] In one embodiment, the method further includes: in the case where the resources in one or more first transmission directions collide with the resources in multiple second transmission directions, determining whether each collided resource is transmitted or not according to the time sequence of the resources.

[0108] Figure 4 A schematic diagram of resource collision provided for one embodiment is as Figure 4 shown. The first transmission direction is UL, and the second transmission direction is DL. Before the semi-static configuration of DL in dynamic scheduling, the collision between dynamic DL and dynamic UL can be resolved first, and then the collision between semi-static DL and dynamic UL can be resolved. If the priority of dynamic DL is higher than that of dynamic UL, then the communication node does not send dynamic UL, so there is no collision between semi-static DL and dynamic UL, and thus there is no need to resolve it accordingly; if the priority of dynamic DL is lower than that of dynamic UL, then the communication node does not receive dynamic DL. At this time, the priority of dynamic UL is also higher than that of semi-static DL. Therefore, the communication node does not receive both DL transmissions and only performs UL transmissions.

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

[0110] In this embodiment, the collision between DL reception and UL transmission of the same type (for example, both are semi-static configurations; or both are dynamic scheduling) can be resolved first, and then the collision between DL reception and UL transmission of different types (for example, the former is dynamic scheduling and the latter is semi-static configuration; or vice versa) can be resolved.

[0111] For example, the collision between semi-static configured DL reception and semi-static configured UL transmission can be resolved first, and then the collision between dynamically scheduled DL reception and semi-static configured UL transmission can be resolved, that is, Case 3 is resolved first and then Case 1. Figure 5 Another schematic diagram of resource collision provided for one embodiment. As Figure 5As shown, the time sequence may not be considered. That is, although the semi-static DL is located after the dynamic DL, the collision between the semi-static DL and the semi-static UL is still preferentially resolved, and then the collision between the dynamic DL and the semi-static UL is resolved.

[0112] For another example, the collision between the DL reception with semi-static configuration and the UL transmission with semi-static configuration can be resolved first, and then the collision between the UL transmission with dynamic scheduling and the DL reception with semi-static configuration can be resolved, that is, Case 3 is resolved first, and then Case 2 is resolved;

[0113] For another example, the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved first, and then the collision between the DL reception with dynamic scheduling and the UL transmission with semi-static configuration can be resolved, that is, Case 4 is resolved first, and then Case 1 is resolved;

[0114] For another example, the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved first, and then the collision between the UL transmission with dynamic scheduling and the DL reception with semi-static configuration can be resolved, that is, Case 4 is resolved first, and then Case 2 is resolved.

[0115] In one embodiment, the method further includes: in the case where the resources in one or more first transmission directions collide with the resources in multiple second transmission directions, first determine whether each resource of different configuration types that collide is transmitted or not, and then determine whether each resource of the same configuration type that collides is transmitted or not.

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

[0117] For example, the collision between the DL reception with dynamic scheduling and the UL transmission with semi-static configuration can be resolved first, and then the collision between the DL reception with semi-static configuration and the UL transmission with semi-static configuration can be resolved, that is, Case 1 is resolved first, and then Case 3 is resolved;

[0118] For another example, the collision between the UL transmission with dynamic scheduling and the DL reception with semi-static configuration can be resolved first, and then the collision between the DL reception with semi-static configuration and the UL transmission with semi-static configuration can be resolved, that is, Case 2 is resolved first, and then Case 3 is resolved;

[0119] For another example, the collision between the DL reception with dynamic scheduling and the UL transmission with semi-static configuration can be resolved first, and then the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved, that is, Case 1 is resolved first, and then Case 4 is resolved;

[0120] For another example, the collision between the UL transmission with dynamic scheduling and the DL reception with semi-static configuration can be resolved first, and then the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved, that is, resolve Case 2 first and then resolve Case 4;

[0121] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, 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.

[0122] For example, the collision between the DL reception with semi-static configuration and the UL transmission with semi-static configuration can be resolved first, and then the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved, that is, resolve Case 3 first and then resolve Case 4;

[0123] For another example, the collision between the DL reception with dynamic scheduling and the UL transmission with dynamic scheduling can be resolved first, and then the collision between the DL reception with semi-static configuration and the UL transmission with semi-static configuration can be resolved, that is, resolve Case 4 first and then resolve Case 3.

[0124] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether the resources in the first transmission direction of the first configuration type that collide 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 collide and each resource in the second transmission direction of the first configuration type are transmitted or not.

[0125] For example, the collision between the DL reception with dynamic scheduling and the UL transmission with semi-static configuration can be resolved first, and then the collision between the DL reception with semi-static configuration and the UL transmission with dynamic scheduling can be resolved, that is, resolve Case 1 first and then resolve Case 2;

[0126] For another example, the collision between the DL reception with semi-static configuration and the UL transmission with dynamic scheduling can be resolved first, and then the collision between the DL reception with dynamic scheduling and the UL transmission with semi-static configuration can be resolved, that is, resolve Case 2 first and then resolve Case 1

[0127] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit resources in one or more first transmission directions and do not transmit resources in multiple second transmission directions.

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

[0129] Among them, signal A is a DL receiving signal, and the multiple signals are UL transmitting signals; or, signal A is a UL transmitting signal, and the multiple signals are DL receiving signals. The multiple signals are signals of the same type or different types. The same type means that these signals are all dynamically scheduled signals or are all signals configured or indicated by a higher layer. Different types mean that some signals are dynamically scheduled signals, and some are signals configured or indicated by a higher layer for transmission.

[0130] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, the resources in the multiple second transmission directions are transmitted, and the resources in one or more first transmission directions are not transmitted.

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

[0132] Among them, signal A is a DL receiving signal, and the multiple signals are UL transmitting signals. Or, signal A is a UL transmitting signal, and the multiple signals are DL receiving signals. The multiple signals are signals of the same type or different types. The same type means that these signals are all dynamically scheduled signals or are all signals configured or indicated by a higher layer. Different types mean that some signals are dynamically scheduled signals, and some are signals configured or indicated by a higher layer for transmission.

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

[0134] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with 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.

[0135] 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), the priority is determined according to the number of colliding DL signals and UL signals or the number of transmissions. For example, if there are 3 colliding DL signals (i.e., 3 transmissions) and 2 colliding UL signals (i.e., 2 transmissions), then the DL reception priority is higher than the UL transmission priority.

[0136] This method is applicable to the collision between one DL signal and one UL signal, the collision between one DL signal and multiple UL signals, the collision between one UL signal and multiple DL signals, and the collision between multiple DL signals and multiple UL signals.

[0137] In one embodiment, the method further includes: when resources in one or more first transmission directions collide with resources in one or more second transmission directions, determining whether to transmit the resources in the first transmission direction or the resources in the second transmission direction according to the total occupied resources of the resources in the first transmission direction and the total occupied resources of the resources in the second transmission direction.

[0138] 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), the priority is determined according to the total quantity of the resources (such as time domain or frequency domain resources) occupied by the colliding DL signals and UL signal transmissions. For example, if the total occupied resources of DL transmissions are greater than the total occupied resources of UL transmissions, then the DL reception priority is higher than the UL transmission priority.

[0139] This method is applicable to the collision between one DL signal and one UL signal, the collision between one DL signal and multiple UL signals, the collision between one UL signal and multiple DL signals, and the collision between multiple DL signals and multiple UL signals.

[0140] In one embodiment, the method further includes: when resources in one first transmission direction collide with resources in multiple second transmission directions and the resources in the first transmission direction and the resources in multiple second transmission directions have the same transmission priority, one of the following is used to determine whether the colliding resources are transmitted or not:

[0141] Determining whether each colliding resource is transmitted or not according to the time sequence of the resources; or,

[0142] Transmitting the resources in the first transmission direction and not transmitting the resources in multiple second transmission directions; or,

[0143] Transmitting the resources in multiple second transmission directions and not transmitting the resources in the first transmission direction; or,

[0144] Uniformly determine whether each resource in the second transmission direction is transmitted or not.

[0145] For example, when the above-mentioned various methods do not include SSB, PRACH, and / or MsgA PUSCH, the collision problems of these signals with signals in different directions can be considered separately.

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

[0147] Figure 7 、 Figure 8 and Figure 9 are respectively schematic diagrams of another resource collision provided for the embodiments of the present application. Similarly, as Figure 7 、 Figure 8 and Figure 9 shown, in the case where PRACH (which can also be replaced by MsgA PUSCH) collides with semi-static DL or dynamic DL, without dealing with different priorities, it is possible to determine whether each colliding resource is transmitted or not according to the time sequence of the resources; it is also possible to transmit the resources in the first transmission direction and not transmit the resources in the second transmission direction multiple times (i.e., send PRACH and do not receive dynamic DL / semi-static DL / SSB); it is also possible to transmit the resources in the second transmission direction multiple times and not transmit the resources in the first transmission direction (i.e., receive dynamic DL / semi-static DL / SSB and do not send PRACH); it is also possible for the communication node to implement a selection of receiving DL or sending UL, where a unified decision needs to be made for multiple DL signals colliding with PRACH, that is, either receive all the multiple DL signals and do not send PRACH, or do not receive all the multiple DL signals and send PRACH.

[0148] In one embodiment, the method further includes: when a resource in the first transmission direction collides with resources in the second transmission direction multiple times, and the resources in the second transmission direction multiple times include 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 colliding resources are transmitted or not:

[0149] Determine whether each colliding resource is transmitted or not according to the time sequence of the resources; or,

[0150] Transmit the resources in the first transmission direction and do not transmit the resources in the second transmission direction multiple times; or,

[0151] Transmit resources in the second transmission direction multiple times and do not transmit resources in the first transmission direction; or,

[0152] Uniformly determine whether each resource in the second transmission direction is transmitted or not; or,

[0153] 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.

[0154] As Figure 10 and Figure 11 shown, when an SSB collides with a PRACH (which can also be replaced by a MsgA PUSCH) and other ULs simultaneously, the SSB and the PRACH have the same priority, and the SSB priority is higher than that of other ULs. Therefore, two different priorities need to be processed. It is possible to determine whether each colliding resource is transmitted or not according to the time sequence of the resources; it is also possible to transmit the resources in the first transmission direction and not transmit the resources in the second transmission direction multiple times (i.e., receive the SSB and do not send the PRACH and other ULs); it is also possible to transmit the resources in the second transmission direction multiple times and not transmit the resources in the first transmission direction (i.e., send the PRACH and other ULs and do not receive the SSB); it can also be solved through the implementation of a communication node, where multiple UL signals colliding with the SSB need to make the same decision; it is also possible to first handle the collision between the SSB and the PRACH, and then handle the collision between the SSB and other ULs. Even as Figure 11 shown, the PRACH is located behind other ULs. For the collision between the SSB and the PRACH / MsgA PUSCH, if the UE preferentially receives the SSB, then it does not send the PRACH and does not send other ULs either; if the UE preferentially sends the PRACH and does not receive the SSB, then there is no collision between the SSB and other ULs, and other ULs can be normally sent.

[0155] The reason for handling the collision in the above order is that if the collision between the SSB and other ULs is handled first, other ULs will be abandoned. At this time, when handling the collision between the SSB and the PRACH, if the PRACH is given priority or implemented by the UE again, the previously abandoned other ULs will be meaningless. Among them, other DLs can refer to DL signals other than the SSB; other ULs can refer to UL signals other than the PRACH / MsgA PUSCH.

[0156] In one embodiment, the situation where multiple uplink transmissions (or multiple uplink signals) collide with multiple downlink transmissions (or multiple downlink signals) is as follows Figure 12 shown, the way to solve the collision can be any of the following ways:

[0157] Method 1: Divide multiple consecutively colliding resource intervals into several single-transmission and multi-(or single-) transmission collisions in chronological order, and then process them according to the aforementioned single-transmission and multi-(or single-) transmission collisions. For example, first process the collision of U1-D1-U2. If D1 is transmitted and U1 and U2 are not transmitted, then only process the collision of D2-U3 later; if U1 and U2 are transmitted and D1 is not transmitted, then it is necessary to process the collision of U2-D2-U3 later.

[0158] Method 2: For multiple consecutively colliding resource intervals, process them according to the relative magnitudes of the number of downlink transmissions and the number of uplink transmissions that occur. If the number of downlink transmissions and the number of uplink transmissions that occur are different, then:

[0159] Method 2-1: For the transmission direction (downlink or uplink) with fewer transmission times, if the transmission types are the same, then corresponding to the processing method for "single transmission" in the aforementioned "single-transmission and multi-transmission collision", and for the transmission direction (uplink or downlink) with more transmission times, corresponding to the processing method for "multi-transmission" in the "single-transmission and multi-transmission collision". For example, Figure 12 in, the downlink is the direction with fewer transmission times, then for D1 and D2, uniformly decide whether to transmit or not, and for U1, U2, U3, decide whether to transmit or not according to the processing method for a single downlink and multiple uplink collisions.

[0160] Method 2-2: For the transmission direction (uplink or downlink) with fewer transmission times, if the transmission types are different, then:

[0161] Method 2-2-1: Still process them uniformly without considering their transmission types (semi-static or dynamic or periodic), that is, uniformly decide to transmit for the transmission direction with fewer transmission times and uniformly decide not to transmit for the transmission direction with more transmission times; or uniformly decide not to transmit for the transmission direction with fewer transmission times and uniformly decide to transmit for the transmission direction with more transmission times.

[0162] Method 2-2-2: Still process them uniformly, but uniformly regard them as the same transmission type for processing, and then the method of case 2-1 can be followed for processing. There can be at least the following methods for uniformly regarding them as which transmission type:

[0163] Method 2-2-2-1: Sort according to the priority of the transmission types: dynamic > semi-static > periodic, and uniformly regard them as the transmission type with the highest priority.

[0164] Method 2-2-2-2: Judge according to the total amount of resources (at least one or more of time domain, frequency domain, code domain, and spatial domain resources) occupied by the transmission types. If the amounts of resources occupied are different, regard them as the transmission type that occupies more resources. For example, Figure 12If D2 occupies more time-domain resources, D1 and D2 can be uniformly regarded as the type of D2 for processing. If the occupied resource quantities are the same, process according to Method 2-2-2-1.

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

[0166] Method 3: For multiple continuously colliding resource intervals, according to the relative magnitudes of the number of downlink transmissions and the number of uplink transmissions that occur in the collision, if the number of downlink transmissions and the number of uplink transmissions that occur in the collision are the same, then:

[0167] Method 3-1: Process according to Method 1.

[0168] Method 3-2: Determine which transmission direction is regarded as the party with fewer transmission times according to the implementation method of the base station, and then process according to Method 2.

[0169] Method 3-3: Judge according to the total amount of resources (such as time-domain resources) occupied by the colliding uplink and downlink transmissions. The party with fewer occupied resources is regarded as the party with fewer transmission times, and then process according to Method 2. If the occupied resource quantities are the same, then process according to 3-1 or 3-2.

[0170] In one embodiment, the configuration types of resources include dynamic scheduling and semi-static configuration; the transmission directions of resources include uplink transmission and downlink reception.

[0171] Figure 13 The flowchart of a resource determination method provided for one embodiment. This method can be applied to a service node, and the service node can be a network-side node. It should be noted that the technical details not described in detail in this embodiment can be referred to any of the above embodiments. As Figure 13 shown, the method provided in this embodiment includes Step 210 and Step 220.

[0172] In Step 210, determine the resource configuration information, where 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.

[0173] In Step 220, determine the transmission resources with the communication node according to the resource configuration information.

[0174] In this embodiment, the serving node can uniquely determine the granularity of the TAR according to the protocol, can also determine the granularity of the TAR independently, or the communication node can determine the granularity of the TAR and report it to the serving node. The granularity of the TAR 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, etc. On this basis, the serving node can more accurately obtain the actual location of the communication node and perform more accurate timing alignment, aiming to avoid resource collisions. In addition, in the case of resource collisions, the resources to be transmitted and the resources not to be transmitted can also be determined according to the transmission priorities of the collided resource types, so as to resolve the collisions and improve the reliability of communication.

[0175] In one embodiment, the indicated 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, DCI.

[0176] In one embodiment, the transmission priorities of the collided resource types are determined by the serving node and configured or indicated through at least one of system information, RRC signaling, MAC CE signaling, and DCI.

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

[0178] In one embodiment, the indicated granularity is indicated through a reserved bit field in the timing advance report.

[0179] In one embodiment, the indicated granularity includes at least two granularities;

[0180] The timing advance amount is the sum of the timing advance amounts corresponding to each granularity.

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

[0182] In one embodiment, the indicated granularity is determined according to the value of the configured timing advance amount deviation threshold;

[0183] wherein, the timing advance amount deviation threshold is used to determine whether to trigger a timing advance report.

[0184] In one embodiment, the indicated granularity includes at least one of the following:

[0185] One or more time units; one or more symbols; one or more time slots; one or more sub - frames or frames; a combination of one or more sub - carrier intervals and one or more time units; a combination of one or more sub - carrier intervals and one or more symbols; a combination of one or more sub - carrier intervals and one or more time slots; a combination of one or more sub - carrier intervals and one or more sub - frames or frames.

[0186] In one embodiment, the transmission priorities of the resource types where collisions occur satisfy at least one of the following conditions:

[0187] 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;

[0188] 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;

[0189] 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;

[0190] 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.

[0191] In one embodiment, the transmission priorities of the resource types where collisions occur satisfy Condition 1 or Condition 2, but 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;

[0192] In one embodiment, PRACH; MsgA PUSCH; PUCCH.

[0193] In one embodiment, the transmission priorities of the resource types where collisions occur satisfy Condition 3 or Condition 4, but 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;

[0194] The second specified resource type includes at least one of the following: the physical downlink control channel PDCCH configured by the common search space set; the channel state information reference signal CSI - RS; the synchronization signal block SSB; the system information block.

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

[0196] In one embodiment, the transmission priority of the resource type configured or indicated to have a collision includes at least one of the following:

[0197] 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;

[0198] 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;

[0199] 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;

[0200] 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.

[0201] In one embodiment, in the case where the communication node does not receive the configuration or indication of the transmission priority of the resource type having a collision, or the serving node does not configure or indicate the transmission priority of the resource type having a collision, the transmission priority of the resource type having a collision is the default priority.

[0202] In one embodiment, the transmission priority of the resource type having a collision is determined according to the received configuration or indication, but 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;

[0203] The third specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0204] In one embodiment, the transmission priority of the resource type having a collision is determined according to the received configuration or indication, but the transmission priority of the fourth 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;

[0205] The fourth specified resource type includes at least one of the following: the physical downlink control channel PDCCH configured by the common search space set; the channel state information reference signal CSI-RS; the synchronization signal block SSB; the system information block.

[0206] In one embodiment, the method further includes:

[0207] In the case where the resources in the first transmission direction collide with the resources in the second transmission direction one or more times, determine whether each collided resource is transmitted or not according to the time sequence of the resources.

[0208] In one embodiment, the method further includes:

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

[0210] In one embodiment, the method further includes:

[0211] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each resource of different configuration types that has collided is transmitted or not, and then determine whether each resource of the same configuration type that has collided is transmitted or not.

[0212] In one embodiment, the method further includes:

[0213] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each resource of the first configuration type that has collided is transmitted or not, and then determine whether each resource of the second configuration type that has collided is transmitted or not.

[0214] In one embodiment, the method further includes:

[0215] In the case where resources in one or more first transmission directions collide with 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 have collided are 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 have collided are transmitted or not.

[0216] In one embodiment, the method further includes:

[0217] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in the one or more first transmission directions and do not transmit the resources in the multiple second transmission directions.

[0218] In one embodiment, the method further includes:

[0219] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in the multiple second transmission directions and do not transmit the resources in the one or more first transmission directions.

[0220] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in one or more second transmission directions, determining whether to transmit resources in the first transmission direction or resources in the second transmission direction according to the number of transmissions of resources in the first transmission direction and the number of transmissions of resources in the second transmission direction.

[0221] In one embodiment, the method further includes: in the case where resources in one or more first transmission directions collide with resources in one or more second transmission directions, determining whether to transmit resources in the first transmission direction or resources in the second transmission direction according to the total sum of resources occupied by resources in the first transmission direction and the total sum of resources occupied by resources in the second transmission direction.

[0222] In one embodiment, the method further includes:

[0223] In the case where a resource in the first transmission direction collides with multiple resources in the second transmission direction and the resource in the first transmission direction and the multiple resources in the second transmission direction have the same transmission priority, one of the following is used to determine whether the collided resources are transmitted or not:

[0224] Determining whether each collided resource is transmitted or not according to the chronological order of the resources; or,

[0225] Transmitting the resource in the first transmission direction and not transmitting the multiple resources in the second transmission direction; or,

[0226] Transmitting the multiple resources in the second transmission direction and not transmitting the resource in the first transmission direction; or,

[0227] Uniformly determining whether each resource in the second transmission direction is transmitted or not.

[0228] In one embodiment, the method further includes:

[0229] In the case where a resource in the first transmission direction collides with multiple resources in the second transmission direction and the multiple resources in the second transmission direction include resources having the same transmission priority as the resource in the first transmission direction and resources having a different transmission priority from the resource in the first transmission direction, one of the following is used to determine whether the collided resources are transmitted or not:

[0230] Determining whether each collided resource is transmitted or not according to the chronological order of the resources; or,

[0231] Transmitting the resource in the first transmission direction and not transmitting the multiple resources in the second transmission direction; or,

[0232] Transmitting the multiple resources in the second transmission direction and not transmitting the resource in the first transmission direction; or,

[0233] Uniformly determine whether each resource in the second transmission direction is transmitted or not; or,

[0234] 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.

[0235] In one embodiment, the resources in the first transmission direction multiple times are equivalent to the resources in the first transmission direction once.

[0236] In one embodiment, the transmission type of the resources in the first transmission direction once after being equivalent to 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 type 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; where the occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, spatial domain resources.

[0237] In one embodiment, 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.

[0238] The embodiments of the present application further provide a resource determination device. Figure 14 A structural schematic diagram of a resource determination device provided for one embodiment. As Figure 14 shown, the resource determination device includes:

[0239] An information determination module 310, configured to determine resource configuration information, where 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 types that collide, and the timing advance is indicated by the communication node to the serving node through the timing advance field in the timing advance report;

[0240] A resource determination module 320, configured to determine the transmission resources with the serving node according to the resource configuration information.

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

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

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

[0244] In one embodiment, 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 granularity.

[0245] In one embodiment, the indicated granularity is determined according to the value of the configured timing advance amount deviation threshold;

[0246] wherein, the timing advance amount deviation threshold is used to determine whether to trigger a timing advance report.

[0247] In one embodiment, the indicated 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 sub - frames or frames; a combination of one or more sub - carrier intervals and one or more time units; a combination of one or more sub - carrier intervals and one or more symbols; a combination of one or more sub - carrier intervals and one or more time slots; a combination of one or more sub - carrier intervals and one or more sub - frames or frames.

[0248] In one embodiment, the transmission priorities of the resource types that collide satisfy at least one of the following conditions:

[0249] 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;

[0250] 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;

[0251] 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;

[0252] 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.

[0253] In one embodiment, the transmission priorities of the resource types that collide satisfy Condition 1 or Condition 2, but 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;

[0254] The first specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0255] In one embodiment, the transmission priorities of the resource types that collide satisfy Condition 3 or Condition 4, but 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;

[0256] 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.

[0257] In one embodiment, 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.

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

[0259] 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;

[0260] 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;

[0261] 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;

[0262] 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.

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

[0264] In one embodiment, the transmission priority of the collided resource type is determined according to the received configuration or indication, but 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;

[0265] The third specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0266] In one embodiment, the transmission priority of the collided resource type is determined according to the received configuration or indication, but the transmission priority of the fourth 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;

[0267] The fourth specified resource type includes at least one of the following: the physical downlink control channel PDCCH configured for a common search space set; the channel state information reference signal CSI-RS; the synchronization signal block SSB; the system information block.

[0268] In one embodiment, the device further includes: a transmission module configured to:

[0269] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, determine whether each colliding resource is transmitted or not in chronological order of the resources.

[0270] In one embodiment, the device further includes: a transmission module configured to:

[0271] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each colliding resource of the same configuration type is transmitted or not, and then determine whether each colliding resource of different configuration types is transmitted or not.

[0272] In one embodiment, the device further includes: a transmission module configured to:

[0273] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each colliding resource of different configuration types is transmitted or not, and then determine whether each colliding resource of the same configuration type is transmitted or not.

[0274] In one embodiment, the device further includes: a transmission module configured to:

[0275] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each colliding resource of the first configuration type is transmitted or not, and then determine whether each colliding resource of the second configuration type is transmitted or not.

[0276] In one embodiment, the device further includes: a transmission module configured to:

[0277] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether each resource in the first transmission direction of the first configuration type and each resource in the second transmission direction of the second configuration type are transmitted or not, and then determine whether each resource in the first transmission direction of the second configuration type and each resource in the second transmission direction of the first configuration type are transmitted or not.

[0278] In one embodiment, the device further includes: a transmission module configured to:

[0279] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in the one or more first transmission directions and do not transmit the resources in the multiple second transmission directions.

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

[0281] In the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in the multiple second transmission directions and do not transmit the resources in the one or more first transmission directions.

[0282] In one embodiment, the apparatus further includes: a transmission module configured to, in the case where resources in one or more first transmission directions collide with 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.

[0283] In one embodiment, the apparatus further includes: a transmission module configured to, in the case where resources in one or more first transmission directions collide with 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.

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

[0285] In the case where 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 or not transmit the colliding resources:

[0286] Determine whether to transmit or not transmit each colliding resource according to the time sequence of the resources; or,

[0287] Transmit the resource in the first transmission direction and do not transmit the resources in the multiple second transmission directions; or,

[0288] Transmit the resources in the multiple second transmission directions and do not transmit the resource in the first transmission direction; or,

[0289] Uniformly determine whether to transmit or not transmit each resource in the second transmission direction.

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

[0291] In a case where resources in a first transmission direction collide with resources in multiple second transmission directions, and the resources in the multiple second transmission directions include 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 adopted to determine whether the collided resources are transmitted or not:

[0292] Determine whether each collided resource is transmitted or not according to the time sequence of the resources; or,

[0293] Transmit the resources in the first transmission direction and do not transmit the resources in the multiple second transmission directions; or,

[0294] Transmit the resources in the multiple second transmission directions and do not transmit the resources in the first transmission direction; or,

[0295] Uniformly determine whether each resource in the second transmission direction is transmitted or not; or,

[0296] 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.

[0297] In an embodiment, the configuration type of resources includes dynamic scheduling and semi-static configuration; the transmission direction of resources includes uplink transmission and downlink reception.

[0298] The resource determination device proposed in this embodiment and the resource determination method proposed in the above embodiment belong to the same inventive concept. For technical details not described in detail in this embodiment, reference can be made to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the resource determination method.

[0299] The embodiment of the present application also provides a resource determination device. Figure 15 It is a schematic structural diagram of a resource determination device provided for an embodiment. As Figure 15 shown, the resource determination device includes:

[0300] An information determination module 410, configured to determine resource configuration information, where 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 collided resource type, and the timing advance is indicated by the communication node to the serving node through the timing advance field in the timing advance report;

[0301] A resource determination module 420, configured to determine the transmission resources of the communication node according to the resource configuration information.

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

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

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

[0305] In one embodiment, the indication granularity includes at least two granularities;

[0306] The timing advance amount is the sum of the timing advance amounts corresponding to each granularity.

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

[0308] In one embodiment, the indication granularity is determined according to the value of the configured timing advance amount deviation threshold;

[0309] wherein, the timing advance amount deviation threshold is used to determine whether to trigger a timing advance report.

[0310] 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.

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

[0312] 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;

[0313] 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;

[0314] 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;

[0315] 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.

[0316] In one embodiment, the transmission priority of the colliding resource types satisfies the condition 1 or the condition 2, but 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;

[0317] The first specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0318] In one embodiment, the transmission priority of the colliding resource types satisfies the condition 3 or the condition 4, but 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;

[0319] The second specified resource type includes at least one of the following: the physical downlink control channel PDCCH configured by the common search space set; the channel state information reference signal CSI-RS; the synchronization signal block SSB; the system information block.

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

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

[0322] 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;

[0323] 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;

[0324] 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;

[0325] 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.

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

[0327] In one embodiment, the transmission priority of the collided resource type is determined according to the received configuration or indication, but the priority of the third specified resource type is higher than the priority of the resources in the first transmission direction of the first configured type or the second configured type;

[0328] The third specified resource type includes at least one of the following: PRACH; MsgA PUSCH; PUCCH.

[0329] In one embodiment, the transmission priority of the collided resource type is determined according to the received configuration or indication, but the priority of the fourth specified resource type transmission is higher than the priority of the resources in the second transmission direction of the first configured type or the second configured type;

[0330] The fourth specified resource type includes at least one of the following: the physical downlink control channel PDCCH configured by the common search space set; the channel state information reference signal CSI-RS; the synchronization signal block SSB; the system information block.

[0331] In one embodiment, the device further includes: a transmission module, configured to: in the case where one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, determine whether each collided resource is transmitted or not according to the time sequence of the resources.

[0332] In one embodiment, the device further includes: a transmission module, configured to: in the case where one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, first determine whether each resource of the same configured type that collides is transmitted or not, and then determine whether each resource of different configured types that collides is transmitted or not.

[0333] In one embodiment, the device further includes: a transmission module, configured to: in the case where one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, first determine whether each resource of different configured types that collides is transmitted or not, and then determine whether each resource of the same configured type that collides is transmitted or not.

[0334] In one embodiment, the device further includes: a transmission module, configured to: in the case where one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, first determine whether each resource of the first configured type that collides is transmitted or not, and then determine whether each resource of the second configured type that collides is transmitted or not.

[0335] In one embodiment, the device further includes: a transmission module, configured to: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, first determine whether to transmit or not transmit each resource in the first transmission direction of the first configuration type and the second transmission direction of the second configuration type that have collided, and then determine whether to transmit or not transmit each resource in the first transmission direction of the second configuration type and the second transmission direction of the first configuration type that have collided.

[0336] In one embodiment, the device further includes: a transmission module, configured to: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in one or more first transmission directions and not transmit the resources in multiple second transmission directions.

[0337] In one embodiment, the device further includes: a transmission module, configured to: in the case where resources in one or more first transmission directions collide with resources in multiple second transmission directions, transmit the resources in multiple second transmission directions and not transmit the resources in one or more first transmission directions.

[0338] In one embodiment, the device further includes: a transmission module, configured to, in the case where resources in one or more first transmission directions collide with 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.

[0339] In one embodiment, the method further includes: a transmission module, configured to, in the case where resources in one or more first transmission directions collide with 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.

[0340] In one embodiment, the device further includes: a transmission module, configured to: in the case where a resource in the first transmission direction collides with resources in multiple second transmission directions and the resource in the first transmission direction and the resources in multiple second transmission directions have the same transmission priority, use one of the following to determine whether to transmit or not transmit the collided resources:

[0341] Determine whether to transmit or not transmit each collided resource according to the time sequence of the resources; or,

[0342] Transmit the resource in the first transmission direction and not transmit the resources in multiple second transmission directions; or,

[0343] Transmit the resources in the multiple second transmission directions and do not transmit the resources in the first transmission direction; or,

[0344] Uniformly determine whether each resource in the second transmission direction is transmitted or not.

[0345] In one embodiment, the device further includes: a transmission module, configured to: in the case where the resources in one first transmission direction collide with the 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, determine whether the collided resources are transmitted or not by using one of the following:

[0346] Determine whether each collided resource is transmitted or not according to the time sequence of the resources; or,

[0347] Transmit the resources in the first transmission direction and do not transmit the resources in the multiple second transmission directions; or,

[0348] Transmit the resources in the multiple second transmission directions and do not transmit the resources in the first transmission direction; or,

[0349] Uniformly determine whether each resource in the second transmission direction is transmitted or not; or,

[0350] First determine whether each resource having the same transmission priority as the resources in the first transmission direction is transmitted or not, and then determine whether each resource having different transmission priorities from the resources in the first transmission direction is transmitted or not.

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

[0352] In one embodiment, the transmission type of the resources in the one first transmission direction after the equivalence of the resources in the multiple first transmission directions is determined by at least one of the following: the transmission type with the highest transmission 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; where the occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0353] In one embodiment, 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.

[0354] The resource determination device proposed in this embodiment and the resource determination method proposed in the above embodiment belong to the same inventive concept. For technical details not described in detail in this embodiment, reference can be made to any of the above embodiments, and this embodiment has the same beneficial effects as the execution of the resource determination method.

[0355] An embodiment of the present application further provides a communication node. Figure 16 As shown in the schematic hardware structure diagram of a communication node provided for an embodiment, 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, Figure 16 Taking 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 embodiments of the present application.

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

[0357] The processor 510, memory 520, communication device 530, input device 540, and output device 550 in the communication node can be connected by a bus or other means, Figure 16 Taking connection by bus as an example.

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

[0359] The communication device 530 can include a receiver and a transmitter. The communication device 530 is configured to perform information transceiver communication according to the control of the processor 510.

[0360] The memory 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the 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 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the communication node, etc. In addition, the memory 520 can include high-speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some instances, the memory 520 can further include a memory remotely provided with respect to the processor 510, and these remote memories can be connected to the communication node through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0361] The embodiments of the present application also provide a service node. Figure 17 As shown in the schematic diagram of the hardware structure of a service node provided for an embodiment, 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, Figure 17 and one processor 610 is taken as an example herein; 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 described in the embodiments of the present application.

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

[0363] The processor 610, the memory 620, the communication device 630, the input device 640, and the output device 650 in the service node can be connected through a bus or other means, Figure 17 and taking the connection through a bus as an example herein.

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

[0365] The communication device 630 can include a receiver and a transmitter. The communication device 630 is configured to perform information transceiver communication according to the control of the processor 610.

[0366] The memory 620, being a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the 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 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the service node, etc. In addition, the memory 620 can include high-speed random access memory and can also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some instances, the memory 620 can further include a memory remotely provided with respect to the processor 610, and these remote memories can be connected to the service node through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0367] The embodiments of the present application also provide a storage medium storing a computer program, which when executed by a processor implements any of the resource determination methods in the embodiments of the present application. The method includes: determining resource configuration information, where 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 has a collision, 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 according to the resource configuration information. Or, the method includes: determining resource configuration information, where 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 has a collision, 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 according to the resource configuration information.

[0368] The embodiments of the present application further provide a computer program product, including computer programs / instructions, which when executed by a processor implement any one of the resource determination methods in the embodiments of the present application. The method includes: determining resource configuration information, where 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 where a collision occurs, and the timing advance is indicated by the communication node to the serving node through the timing advance field in the timing advance report; determining the transmission resources with the serving node according to the resource configuration information. Or, the method includes: determining resource configuration information, where 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 where a collision occurs, and the timing advance is indicated by the communication node to the serving node through the timing advance field in the timing advance report; determining the transmission resources with the communication node according to the resource configuration information.

[0369] The computer storage medium of the embodiments of the present application may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the computer-readable storage medium include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0370] The computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0371] The program code contained on a computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wire, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the above.

[0372] The computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed 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 (for example, by using an Internet service provider to connect through the Internet).

[0373] The embodiments of this application also provide a computer program product, including a computer program / instructions, and when the computer program / instructions are executed by a processor, they implement the video encoding method described in any of the above embodiments.

[0374] As described above, it is only an exemplary embodiment of this application and is not used to limit the protection scope of this application.

[0375] Those skilled in the art should understand that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing portable network browser, or an in-vehicle mobile station.

[0376] Generally speaking, the various embodiments of this application can be implemented in hardware or a dedicated circuit, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing devices, although this application is not limited thereto.

[0377] The embodiments of this application can be implemented by a data processor of a mobile device executing computer program instructions, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0378] Any block diagram of a logical process in the accompanying drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. A computer program may be stored in a memory. The memory may have any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical memory devices and systems (such as Digital Video Disc (DVD) or Compact Disk (CD), etc.). The computer-readable medium may include a non-transitory storage medium. The data processor may be any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FGPA), and a processor based on a multi-core processor architecture.

[0379] By way of illustrative and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adaptations of the above embodiments will be apparent to those skilled in the art upon consideration of the accompanying drawings and the claims, without departing from the scope of the present application. Therefore, the proper scope of the present application will be determined in accordance with the claims.

Claims

1. A resource determination method, applied to a communication node, characterized in that: include: 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 by the communication node to the service node via a timing advance field in a timing advance report; Determine the transmission resources with the service node according to the resource configuration information.

2. The method according to claim 1, characterized in that The indication granularity is determined according to the received indication of the service node; the indication includes at least one of the following: system information, radio resource control RRC signaling, medium access control MAC control unit CE signaling, and downlink control information DCI.

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

4. The method according to claim 1, characterized in that: The indicated particle size includes at least two particle sizes; The timing advance is the sum of the timing advances corresponding to each granularity.

5. The method according to claim 1 or 4, characterized in that: 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.

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

7. The method according to claim 1, characterized in that The indicated 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.

8. The method according to claim 1, characterized in that The priority of the transmission of the resource type that collides meets at least one of the following conditions: 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 three: 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 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, characterized in that The priority of 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 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: a physical random access channel PRACH; a message A physical uplink shared channel MsgA PUSCH; and a physical uplink control channel PUCCH.

10. The method according to claim 8, characterized in that 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 resources in 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.

11. The method according to claim 1, characterized in that: The transmission priority of the resource type where the collision occurs is configured or indicated by at least one of received system information, RRC signaling, MAC CE signaling or DCI.

12. The method according to claim 1, characterized in that The configured or indicated transmission priority of the resource type where the collision occurs includes at least one of the following: 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.

13. The method according to claim 1, characterized in that When the communication node does not receive the configuration or indication of the transmission priority of the colliding resource type, or the service node does not configure or indicate the transmission priority of the colliding resource type, the transmission priority of the colliding resource type is the default priority.

14. The method according to claim 11 or 12, characterized in that: The priority of transmission of the resource type in collision 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 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.

15. The method according to claim 11 or 12, characterized in that: 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 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 in a common search space set; CSI-RS; SSB; system information block.

16. The method according to claim 1, characterized in that Also includes: In the case that one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, it is determined whether to transmit or not transmit each resource that collides according to the time sequence of the resources.

17. The method according to claim 1, characterized in that Also includes: 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.

18. The method according to claim 1, characterized in that Also includes: 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.

19. The method according to claim 1, characterized in that Also includes: 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.

20. The method according to claim 1, characterized in that Also includes: In the event that resources in the first transmission direction collide with resources in the second transmission direction one or more 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.

21. The method according to claim 1, characterized in that Also includes: When 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 resources in the second transmission direction are not transmitted.

22. The method according to claim 1, characterized in that Also includes: When one or more resources in the first transmission direction collide with multiple resources in the second transmission direction, the multiple resources in the second transmission directions are transmitted, and the one or more resources in the first transmission direction are not transmitted.

23. The method according to claim 1, characterized in that Also includes: When one or more resources in the first transmission direction collide with one or more resources in the second transmission direction, it is determined 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, characterized in that Also includes: When one or more resources of the first transmission direction collide with one or more resources of the second transmission direction, it is determined 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.

25. The method according to claim 1, characterized in that Also includes: In the case where a resource in a first transmission direction collides with a resource in a second transmission direction multiple times, and the resource in the first transmission direction and the resource in the second transmission direction multiple times have the same transmission priority, one of the following is used to determine whether the colliding resource is transmitted or not: Determine whether each resource that collides transmits or does not transmit 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 for the multiple times; or, Transmit the resources in the second transmission direction for the multiple times, and do not transmit the resources in the first transmission direction; or, It is uniformly determined whether each resource in the second transmission direction is to be transmitted or not.

26. The method according to claim 1, characterized in that Also includes: In the case where a resource of a first transmission direction collides with a resource of multiple second transmission directions, and the resources of the multiple second transmission directions include resources having the same transmission priority as the resources of the first transmission direction and resources having different transmission priorities from the resources of the first transmission direction, one of the following is used to determine whether the colliding resources are transmitted or not: Determine whether each resource that collides transmits or does not transmit 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 for the multiple times; or, Transmit the resources in the second transmission direction for the multiple times, and do not transmit the resources in the first transmission direction; or, uniformly determine whether each resource in the second transmission direction is transmitted or not; or, First, determine whether to transmit or not transmit each resource having the same transmission priority as the resource of the first transmission direction, and then determine whether to transmit or not transmit each resource having a different transmission priority than the resource of the first transmission direction.

27. The method according to any one of claims 16 to 26, characterized in that: The resources of multiple first transmission directions are equivalent to the resources of the one first transmission direction.

28. The method according to claim 27, characterized in that The transmission type of the resources of the first transmission direction after the resources of the 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 of the multiple first transmission directions; or the transmission type with the largest total number of resources among the resources of the multiple first transmission directions; The occupied resources are at least one of the following: time domain resources, frequency domain resources, code domain resources, and space domain resources.

29. The method according to any one of claims 8-13, 16-26, characterized in that: The resource configuration types include dynamic scheduling and semi-static configuration; the resource transmission directions include uplink sending and downlink receiving.

30. A method for determining resources, applied to a service node, characterized in that: include: 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 the service node by the communication node through a timing advance field in a timing advance report; Determine the transmission resources with the communication node according to the resource configuration information.

31. The method according to claim 30, characterized in that The indication granularity is determined by the service 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, and downlink control information DCI.

32. The method according to claim 30, characterized in that The transmission priority of the resource type that collides 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, characterized in that: include: memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the resource determination method according to any one of claims 1 to 29.

34. A service node, characterized in that: include: memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the resource determination method according to any one of claims 30 to 32.

35. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the resource determination method as described in any one of claims 1-32 is implemented.

Images