Changing the communication priority of nodes within a communication network

Abstract

A method, apparatus, and system for changing communication priority at a node are disclosed. The method includes associating a first priority with a first communication; associating a second priority with a second communication; changing at least one of the first or second priority based on one or more conditions; determining which of the first or second communication has a higher priority with respect to the changed priority; and processing at least one of the first or second communication based on the determined higher priority.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 457,263, filed on April 5, 2023, entitled "SCHEMES FOR COEXISTENCE BETWEEN CHANNELS, OR RADIO ACCESS TECHNOLOGIES", which is hereby incorporated by reference in its entirety.

[0002] The apparatus and methods according to the present disclosure generally relate to communications, and more particularly, to methods, systems, and devices for changing the communication priority of one or more communications at a node within a communication network.

Background Art

[0003] Sidelink (SL) communication is used on the 3GPP radio interface to enable two or more wireless devices or user equipment (UE) to communicate directly with each other. This can occur under the coverage of a cellular network, outside the coverage of a cellular network, or even within a partial coverage of a cellular network where only one of the two UEs is under network coverage. Direct device - to - device communication uses the PC5 interface.

[0004] Sidelink communication, also known as V2X, is used in vehicle-to-everything applications. SL devices can use various radio access technologies (RATs) for transmission and reception, such as Long-Term Evolution (LTE) SL, Next Radio (NR) SL, or both. When both LTE SL and NR SL modules coexist in the same device, this can present implementation challenges. For example, when close frequency spacings are used, using two radio frequency (RF) chains (e.g., separate hardware for transmission and reception on both frequencies) results in additional hardware costs and battery consumption for the device. Therefore, 3GPP Release 16 introduced the concept of Intra-Device Coexistence (IDC) between LTE-V2X sidelink and NR-V2X sidelink. When sufficiently close frequency spacings are deployed between the two RATs, one implementation option is to implement a single RF chain in the UE, assuming the UE does not require simultaneous transmission and reception on the sidelink.

[0005] When a single RF chain is implemented in the UE, interference between two RAT receivers can occur in the UE if the frequencies of the two RATs are close together and the configured or pre-configured time resource pools overlap for the two sidelink RATs. Furthermore, due to half-duplex constraints (e.g., the inability to transmit and receive simultaneously on the same frequency), one RAT may be unable to receive / transmit while the other RAT is doing the opposite. Additionally, the UE's single power loss calculation may prevent simultaneous transmission on both RATs. These are the reasons why, in Release 16, In-Device Coexistence introduced the concept of inter-RAT transmission and reception priority for LTE SL and NR SL. This concept applies to all transmit and receive signals for LTE SL and NR SL, namely the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), and Physical Sidelink Feedback Channel (PSFCH) (PSFCH is NR SL specific). In the case of send / send overlap, both priorities are already If known, the RAT with the higher priority is selected. The same principle applies to transmit / receive overlap between two RATs if both priorities are known. This requires aligning the subframe boundaries of the two channels / signals. For other cases, such as receive / receive overlap, equal priorities, and unknown priorities, the decision is left to the device implementation. [Overview of the project]

[0006] According to some embodiments of the present disclosure, a method is provided for changing communication priorities at a node. The method includes associating a first priority with a first communication; associating a second priority with a second communication; changing at least one of the first or second priorities based on one or more conditions; determining which of the first or second communication has a higher priority with respect to the changed priorities; and processing at least one of the first or second communication based on the determined higher priority.

[0007] According to some embodiments of the present disclosure, a node is provided. The node includes a memory for storing instructions and a processor configured to execute the instructions stored in the memory for: associating a first priority with a first communication; associating a second priority with a second communication; changing at least one of the first or second priorities based on one or more conditions; determining which of the first or second communication has a higher priority with respect to the changed priorities; and processing at least one of the first or second communication based on the determined higher priority.

[0008] According to some embodiments of the present disclosure, a non-temporary computer-readable medium is provided for storing instructions that can be executed by one or more processors of a node to perform a method. The method includes associating a first priority with a first communication; associating a second priority with a second communication; changing at least one of the first or second priority based on one or more conditions; determining which of the first or second communication has a higher priority with respect to the changed priority; and processing at least one of the first or second communication based on the determined higher priority. [Brief explanation of the drawing]

[0009] [Figure 1]This is a schematic diagram showing device types for dynamic same-channel coexistence of first and second sidelink communications according to some embodiments of the present disclosure. [Figure 2] This is a schematic diagram illustrating information transfer from an LTE sidelink module to an NR sidelink module at a node, according to some embodiments of this disclosure. [Figure 3] This is a schematic diagram illustrating an extended in-device coexistence (eIDC) component that uses additional information and / or interfaces according to some embodiments of this disclosure. [Figure 4] This is a flowchart of an example of a method for changing the communication priority at a node, according to some embodiments of this disclosure. [Figure 5] This is a flowchart illustrating an example of another method for changing communication priority at a node, according to some embodiments of this disclosure. [Figure 6] This is a flowchart illustrating an example of another method for changing communication priority at a node, according to some embodiments of this disclosure. [Figure 7] This is a block diagram of a node according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0010] Herein, exemplary embodiments are referenced in detail, and examples of exemplary embodiments are shown in the accompanying drawings. In the following description, reference is made to the accompanying drawings, where the same number in different drawings represents the same or similar elements unless otherwise indicated. The examples based on the exemplary embodiments shown in the following description do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of systems, apparatuses, and methods relating to the embodiments of the present disclosure enumerated in the accompanying claims.

[0011] Dynamic same-channel coexistence of LTE sidelink and NR sidelink in Release 18

[0012] As part of 3GPP work, one of the objectives is same-channel coexistence of LTE sidelinks and NR sidelinks. If necessary, the mechanism for same-channel coexistence of LTE sidelinks and NR sidelinks is being considered for study and specification, including performance, necessity, feasibility, and potential impact on specifications, if any. It has also been proposed to reuse the in-device coexistence framework defined in Release 16 as much as possible.

[0013] Quasi-static frequency division multiplexing (FDM) or time division multiplexing (TDM) can theoretically achieve coexistence, but this can be inefficient because allocated time and frequency resources may not change rapidly enough, and therefore may be inefficient in utilizing changing circumstances (e.g., when the ratio of LTE SL to NR SL devices changes). In addition, if all LTE SL resources are allocated by regulation or technical specifications, quasi-static time and frequency resource allocation may not be possible. This is why more flexible dynamic resource allocation is being considered. This dynamic resource allocation uses a pool of time and frequency resources that could potentially be used by LTE SL and NR SL, with several additional rules used to avoid interference between one RAT and another.

[0014] Some embodiments of this disclosure propose extending the in-device coexistence (IDC) solution of Release 16 to achieve dynamic LTE / NR sidelink same-channel coexistence of Release 18.

[0015] Interface between LTE SL module and NR SL module

[0016] As part of the 3GPP discussions, device type A is defined as LTE SL module and NR Defined as a device containing both SL modules, the NR SL module can receive information from the LTE SL module. To study the feasibility of dynamic resource sharing as a possible solution for same-channel coexistence, in the case of device type A, the NR SL module uses sensing and resource reservation information shared by the LTE SL module.

[0017] Figure 1 is a schematic diagram showing device types for dynamic same-channel coexistence of first sidelink (SL) communication and second SL communication according to some embodiments of the present disclosure. Referring to Figure 1, at least three types of devices (Type A, Type B, and Type C) are conceivable in the present disclosure. A Type A device includes a module for first SL communication and a module for second SL communication. A Type B device includes only the module for first SL communication. A Type C device includes only the module for second SL communication. For example, in embodiments, a Type A device includes both an LTE SL module and an NR SL module, a Type B device includes only an NR SL module, and a Type C device includes only an LTE SL module.

[0018] In some embodiments of this disclosure, in-device coexistence (I) using the above-described priority is used. Regarding DCs, not all events of equivalent priority will have the same effect when dropping a single RAT transmission or reception. For example, dropping a single PSCCH / PSSCH retransmission may have little to no impact. Another example is dropping an initial PSCCH / PSSCH transmission, which may cause a slight delay. Another example is dropping a PSFCH transmission / reception of an NR SL, which may significantly reduce the reliability of the NR SL communication.

[0019] The priorities described in this disclosure may be 5QI priorities (e.g., 5G service quality identifiers), Quality of Service Class Indicator (QCI) priorities (used in LTE), per-packet priorities for Proximity-based Services (PPPP), L1 / L2 priorities, or any other priority related to service quality or application priority.

[0020] Symmetrically, handling equivalent priorities in the same way as currently done in the IDC may not always be efficient. For example, some equivalent priority events such as blind retransmission / iteration should not be treated equally because their importance decreases with each transmission (since they provide little new mutual information / energy). Thus, some embodiments of this disclosure improve the current 3GPP solutions by proposing a more efficient in-device coexistence scheme. Embodiments of this disclosure may, for example, NR enable the NR SL module to "force" the LTE SL module not to use certain resources.

[0021] In some embodiments of this disclosure, the priority may be changed when data, packets, signals, or messages are transmitted and / or received, and different priorities may be used. Note that the terms "communication" or "event" are used herein to include data, packets, signals, or messages. For example, if the priority change is performed by the NR SL module, the NR SL module may change its priority to be lower or higher than the initial priority of the communication. For example, when the NR SL priority is changed to a higher priority than the LTE SL priority, the LTE SL module can be "forced" not to use certain resources. This function is referred to herein as the enhanced IDC (eIDC) function.

[0022] FIG. 2 is a diagram showing an example of a system of node 200 using the IDC of Release 16, and an example of information transfer from the LTE SL module of Release 18 to the NR SL module having the eIDC function described above. As used herein, the term "node" may include a user equipment (UE), an evolved Node B (eNB), a next-generation Node B (gNB), a roadside unit (RSU), a mobility management entity (MME), or an access and mobility management function (AMF).

[0023] Node 200 includes a device RAT controller 202, an LTE SL module 204, and an NR SL module 206 having an eIDC component 208. The eIDC component 208 implements the eIDC function and may include hardware, software, or a combination thereof. The LTE SL module 204 communicates with the device RAT controller 202 via an IDC interface 210. The NR SL module 206 communicates with the device RAT controller 202 via an IDC interface 212. The LTE SL module 204 communicates with the NR SL module 206 via a direct interface 214 (e.g., a PC5 interface).

[0024] In the embodiment shown in FIG. 2, the NR SL module 206 may change its NR priority and transmit the changed NR priority to the device RAT controller 202 via the IDC interface 212. controller 202.

[0025] In another exemplary embodiment, the eIDC component 208 may be located in the device RAT controller 202 (not shown in FIG. 2). In this embodiment, it is also possible to use the IDC interface of legacy Release 16.

[0026] In another exemplary embodiment, the eIDC component 208 may be located in the LTE SL module 204 (not shown in Figure 2). In this embodiment, it is also possible to use the legacy release 16 IDC interface.

[0027] It should be noted that the eIDC component 208 functions in a similar manner regardless of its location within node 200. In some embodiments, it is also conceivable that changing the priority may be performed by the entity receiving the priority rather than the entity sending the priority.

[0028] In another embodiment, the eIDC component 208 may estimate the cost of discarding a communication and use the estimated cost in the decision process. For example, the cost of discarding each entity (e.g., each RAT such as LTE SL and NR SL) may be compared and used in the decision process. Discarding a communication may be considered part of increasing or decreasing its priority. In some embodiments, whether a RAT can be increased or decreased in priority may depend on the RAT. For example, in some embodiments, it may not be possible to change the priority of an LTE SL, and in such situations, the communication is discarded instead of changing its priority.

[0029] As another example, the cost function may associate events with weights. Some examples of events may be a first retransmission, a second retransmission, a first consecutive transmission, a second consecutive transmission, an LTE event, an NR event, an LTE PC5 interface quality of service identifier (PQI), or an NR PQI. If the weight of one event is higher than the weights of other events, this may result in an increase or decrease in priority. In some embodiments, weights may be applied when the original priority of communications is equal. In some embodiments, it may also be possible to combine different types of weights, e.g., LTE / NR (first type of weight) and first consecutive transmission / not first consecutive transmission (second type of weight). In this example, the combination of different types of weights may be addition, weighted average, or other mathematical combination, or comparison.

[0030] In another embodiment, if a time and / or frequency resource collision between LTE SL and NR SL is imminent, the eIDC component 208 may determine whether to increase the priority of NR SL to avoid NR discarding. This may be combined with the use of a cost function, as described above.

[0031] In another embodiment, if a time and / or frequency resource collision between LTE SL and NR SL is imminent, the eIDC component 208 may determine whether or not to reduce the priority of LTE SL to avoid an NR outage. This may be combined with the use of a cost function, as described above.

[0032] In another embodiment, if a time and / or frequency resource collision between LTE SL and NR SL is imminent, the eIDC component 208 may determine whether to increase the priority of LTE SL to avoid LTE abandonment. This may be combined with the use of a cost function, as described above.

[0033] In another embodiment, if a time and / or frequency resource collision between LTE SL and NR SL is imminent, the eIDC component 208 may determine whether to de-prioritize NR SL to avoid LTE abandonment. This may be combined with the use of a cost function, as described above.

[0034] In another embodiment, the eIDC function may be performed by a module or entity that transmits a priority, such as the LTE SL module 204 in the example of Figure 2 (if the LTE SL module 204 includes the eIDC component 208). The priority provided may then be increased or decreased, for example, to avoid conflicts with NR SL resources or other RATs or systems.

[0035] In another embodiment, the eIDC function may be configured or pre-configured to always discard transmissions that overlap with one or more specific time and / or frequency resources. In another embodiment, the eIDC function may be configured not to ever discard transmissions that overlap with one or more specific time and / or frequency resources. For example, the eIDC function may be configured to always discard LTE transmissions that overlap with a particular NR slot. In another embodiment, the eIDC function may be configured not to ever discard LTE transmissions that overlap with a particular NR slot.

[0036] In another embodiment, the decision process may use several additional criteria, such as several measurements from one or more RATs, including reference signal received power (RSRP), received signal strength index (RSSI), signal-to-interference noise ratio (SINR), and energy measurements. One or more thresholds may be used as these criteria.

[0037] In another embodiment, the concept of availability, or the degree of busyness / congestion of one or two signals, may be used. For example, congestion may be determined using the channel busy rate (CBR). In an embodiment, if the CBR determined by the NR SL module is lower than the CBR determined by the LTE SL module, the NR SL priority may be increased. In another embodiment, if the CBR of a particular radio access technology (RAT) is below or above a threshold, the associated priority may be increased or decreased. In another embodiment, if the CBR of a particular channel is below or above a threshold, the associated priority may be increased or decreased.

[0038] In another embodiment, a packet delay budget (PDB) may be used to determine whether to increase and / or decrease priority. For example, if the remaining PDB (time) for NR SL transmission is small (for example, based on a threshold period or number of symbols until the budget runs out), the NR SL priority may be increased.

[0039] In another embodiment, priority increases and / or decreases may be considered when the transmission carries a Media Access Control (MAC) control element (CE). For example, the priority of an NR SL transmission may be increased if it includes an SL Channel Status Information (CSI) report MAC CE. In another embodiment, priority may be increased and / or decreased for an NR SL transmission if it includes Inter-UE Coordination (IUC) information.

[0040] In another embodiment, priority increases or decreases may be determined based on the cast type of the transmission. For example, priority increases may be performed on a module if the transmission is at least one of unicast, groupcast, and / or broadcast. In one embodiment, the cast types to be converted to priority increases or decreases may be configured or preconfigured. In another exemplary embodiment, NR SL transmission This may be preferred if it is a groupcast transmission for a group size larger than the configured threshold.

[0041] In another embodiment, the eIDC function may support LTE RAT and / or NR RAT configuration. In another embodiment, the eIDC function may use LTE SL sensing information and / or LTE SL resource pool (RP) configuration information or pre-configuration information. In another embodiment, the eIDC function may use NR SL sensing information and / or NR SL resource pool (RP) configuration information or pre-configuration information. When the eIDC uses the Release 16 IDC interface, these last three embodiments described above provide an example shown in Figure 3.

[0042] Figure 3 is a schematic diagram showing an eIDC component 300 using additional information and / or interfaces according to some embodiments of this disclosure. The eIDC component 300 may communicate with other entities (e.g., an LTE SL module, an NR SL module, or a RAT controller) using the IDC interface 302. The eIDC component 302 may receive LTE SL sensing information and LTE SL resource pool configuration information from an LTE SL module 304. The eIDC component 302 may receive NR SL sensing information and NR SL resource pool configuration information from an NR SL module 306.

[0043] In another embodiment, the eIDC function may determine which priority to change in the case of equivalent priority events. As used herein, the term "equivalent priority events" means that the initial unchanged priorities of each event are identical. In another embodiment, the eIDC function may determine which priority to override in the case of a collision event. In another embodiment, the eIDC function may determine which priority to override on a transport block basis (e.g., a data unit submitted by Layer 2). An example of a criterion used for evaluation may be whether the transmit or receive is a continuous transmission. Another example of a criterion used for evaluation may be whether the transmit or receive is a blind retransmission.

[0044] An example of a criterion used for evaluation may be whether the transmission and / or reception applies to a specific channel, such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH). An example of a criterion used for evaluation may be whether the transmission and / or reception applies to continuous transmission or blind retransmission. An example of a criterion used for evaluation may be whether the transmission and / or reception is an initial transmission, a PSCCH / PSSCH transmission requesting PSFCH Hybrid Automatic Retransmission Request (HARQ) feedback, or a broadcast, groupcast, or unicast transmission.

[0045] In another embodiment, it may be considered whether the transmit and / or receive overlaps with some configured or preconfigured resources, or some protected resources. Protected resources may be, for example, a subset of resources that are configured or preconfigured. This may be indicated, for example, via semi-persistent scheduling (SPS). In another embodiment, protected resources may be considered protected only for certain priorities, for example, up to a certain priority. For example, the criterion may be whether the LTE SL transmit overlaps with a protected, configured or preconfigured NR SL slot. In another embodiment, any of the exemplary schemes described herein may be applied only for certain priorities.

[0046] An example of how to change communication priority on a node.

[0047] Figure 4 is a flowchart of an exemplary method 400 for changing communication priority at a node, according to some embodiments of the present disclosure. Method 400 may be performed by a node in a communication system, for example, by a UE in sidelink communication.

[0048] Method 400 includes step 402 of associating a first priority with a first communication. For example, the first priority may be associated with the first communication when the first communication is received at the node or generated by the node. As another example, the first priority may be shown as part of the first communication. As yet another example, the first priority may be received at the node separately from the first communication or generated by the node separately from the first communication.

[0049] Method 400 includes step 404 of associating a second priority with a second communication. The second priority may be associated with the second communication in a similar manner to how the first priority is associated with the second communication.

[0050] Method 400 includes step 406 of changing at least a first priority or a second priority based on one or more conditions. Changing the first or second priority may include any one or more of the following: increasing the first priority, decreasing the first priority, increasing the second priority, decreasing the second priority, or changing both priorities. How the priority is changed (i.e., increased or decreased) may be associated with a particular condition being considered when changing the priority. For example, if the condition is whether the transmission is an initial transmission, the priority may be increased if the transmission is an initial transmission.

[0051] Method 400 includes step 408 of determining which communication has a higher priority after the changes are complete (i.e., identifying a communication that has a higher priority than one or more other communications). After one or both of the priorities have been changed, one of the communications may have a higher priority than the others.

[0052] Method 400 includes step 410 of processing at least one of the communications based on the determined higher priority, i.e., processing communications with higher priority first. For example, the transceiver of the node may transmit communications with higher priority first.

[0053] Figure 5 is a flowchart of an exemplary method 500 for changing communication priority at a node, according to some embodiments of the present disclosure. Method 500 may be performed by a node in a communication system, for example, by a UE in sidelink communication.

[0054] Method 500 includes step 502 of associating a first priority with a first communication. For example, the first priority may be associated with the first communication when the first communication is received at the node or generated by the node. As another example, the first priority may be shown as part of the first communication. As yet another example, the first priority may be received at the node separately from the first communication or generated by the node separately from the first communication.

[0055] Method 500 includes step 504 of associating a second priority with a second communication. The second priority may be associated with the second communication in a similar manner to how the first priority is associated with the first communication.

[0056] Method 500 includes step 506 of selecting and applying applicable conditions. In some embodiments, multiple conditions may be applied simultaneously to the first and second communications. For example, if the first communication has two applicable conditions (e.g., the first communication is on a specific channel and the first communication is an initial communication), the priority may be increased for the specific channel and also for being an initial transmission. In such an example, the priority of the first communication may be increased twice (in the “relative” solution) or once (in the “absolute” solution).

[0057] In some embodiments, each condition may have a ranking associated with it, which may be used to determine the order in which multiple conditions are evaluated. In some embodiments, all applicable conditions may be evaluated, and the conditions to be evaluated may be randomly selected. In some embodiments, more than one latent condition may be applied to the first communication. In some embodiments, more than one latent condition may be applied to the second communication.

[0058] Method 500 includes step 508 of changing the priority of communications based on applied conditions. Changing the priority may include one or more of the following: increasing the priority of a first priority, decreasing the priority of a first priority, increasing the priority of a second priority, decreasing the priority of a second priority, or changing both priorities. Changing the priority may be applied relative or absolutely with respect to the initial priority, since in the second case the new priority is selected without arithmetic addition or subtraction with respect to the initial priority. How the priority is changed (i.e., increased or decreased) may be associated with specific conditions being considered when changing the priority.

[0059] Method 500 includes a step 510 to determine whether to apply other conditions to the communication. As described above, multiple conditions may apply to the first and second communications. In some embodiments, one or more conditions may be evaluated before making a final determination as to whether one communication has a higher priority than the other. If other conditions apply to the communication (step 510, branch to "yes"), Method 500 returns to step 506 to select and apply the next applicable condition. If no other conditions apply to the communication (step 510, branch to "no"), Method 500 proceeds to step 512.

[0060] Method 500 includes a step 512 for determining which communication has a higher priority after the changes are complete. After one or both of the priorities have been changed, one of the communications may have a higher priority than the others.

[0061] Method 500 includes step 514 of processing at least one of the communications based on the determined higher priority, i.e., processing communications with higher priority first. For example, the transceiver of the node may transmit communications with higher priority first.

[0062] Figure 6 is a flowchart of an exemplary method 600 for changing communication priority at a node, according to some embodiments of the present disclosure. Method 600 may be performed by a node in a communication system, for example, by a UE in sidelink communication. For illustrative purposes, it is assumed that Method 600 is performed at a node containing an LTE SL module and an NR SL module.

[0063] Method 600 involves sensing information from the NR SL module and the LTE SL module. The procedure includes step 602 of obtaining information. For example, the eIDC component may reside in the node's NR SL module, LTE SL module, or RAT controller, as described elsewhere in this disclosure, and may receive sensing information from the NR SL module and LTE SL module.

[0064] Method 600 includes step 604 of predicting whether or not there is an in-device coexistence collision. Based on the received sensing information, it is possible to predict whether or not there is an in-device coexistence collision, for example, by transmission by both the NR SL module and the LTE SL module.

[0065] Method 600 includes step 606 of estimating whether an NR or LTE communication is a PSSCH retransmission or a blind retransmission. This estimation may be based on information contained in the communication (e.g., the channel type associated with the communication or the transmission type associated with the communication).

[0066] Method 600 includes a step 608 for determining the cost of discarding NR and LTE communications. The costs associated with NR and LTE communications may include numerical values ​​associated with the communications and may utilize weights as described elsewhere in this disclosure.

[0067] Method 600 includes step 610, which determines whether the LTE communication priority is higher than the NR communication priority. For example, the LTE communication priority and the NR communication priority may be expressed as numerical values, and the determination may include comparing the values ​​to determine which value is higher. Note that other representations of priority and comparison may be applied. If the LTE communication priority is higher than the NR communication priority (step 610, branch to "yes"), Method 600 proceeds to step 612. If the LTE communication priority is not higher than the NR communication priority (step 610, branch to "no"), Method 600 proceeds to step 616.

[0068] Method 600 includes step 612, which determines whether the cost of discarding NR communication is higher than the cost of discarding LTE communication. If the cost of discarding NR communication is higher than the cost of discarding LTE communication (step 612, "yes" branch), method 600 proceeds to step 614. If the cost of discarding NR communication is not higher than the cost of discarding LTE communication (step 612, "no" branch), method 600 proceeds to step 616.

[0069] Method 600 includes step 614 of increasing the NR communication priority and signaling the increased priority using the IDC interface. For example, the increased priority may be signaled to the transceiver of the node transmitting or receiving NR communication. The increased priority may also be used by the receiving node in the case of potential transmission or reception.

[0070] Method 600 includes step 616 for determining whether the LTE communication overlaps with a protected, configured, or pre-configured NR slot. If the LTE communication overlaps with a protected, configured, or pre-configured NR slot (branch to "yes" in step 616), Method 600 proceeds to step 614. If the LTE communication does not overlap with a protected, configured, or pre-configured NR slot (branch to "no" in step 616), Method 600 proceeds to step 618.

[0071] Method 600 includes step 618, in which no communication priority is adjusted. The priorities of LTE and NR communications may then be compared before any potential transmission or reception.

[0072] In some embodiments, the priority change is limited to a specific time and / or one time. Alternatively, this may be done according to several specific criteria. For example, device history may be used. For example, if one RAT is at a disadvantage compared to other RATs (i.e., one RAT has more transmits or receives than other RATs), the priority may be changed to bring the disadvantaged RAT back to a favorable position. This may be based on the channel busy rate (CBR) and / or several measurements (e.g., RSRP, RSSI, SINR, energy measurements). The evaluation may be based on previous periods. This may use thresholds in the decision process. For example, if the CBR and / or measurements of one RAT are higher than a certain threshold, the priority may be changed to bring the disadvantaged RAT back to a favorable position. Alternatively or additionally, if one RAT has been favorable for a longer duration than a certain period, the priority may be changed to bring the disadvantaged RAT back to a favorable position. Alternatively or additionally, the conditions for bringing a disadvantaged RAT back to a favorable position may be considering whether one or more conditions are lower than the respective thresholds associated with those conditions.

[0073] Embodiments of this disclosure may include NR sidelink and LTE sidelink radio equipment of Release 18, and software incorporated, for example, in a vehicle. Furthermore, embodiments described herein may be used for future 3GPP sidelink technologies using similar sidelink mechanisms (e.g., between NR and 6G sidelink).

[0074] Any of the information, parameters, and / or thresholds described in this disclosure may be provided to the device by configuration or pre-configuration. This may be done, for example, by using transmission from a network (e.g., using a Radio Resource Control (RRC) protocol, as described in 3GPP TS38.331), or by using configuration information by a SIM / USIM, such as a SIM toolkit.

[0075] While exemplary embodiments of Intra-Device Coexistence (IDC) are described in this disclosure, embodiments of this disclosure are not limited to IDC. In one embodiment, a device may forward and modify received priorities from one device to another (third) device. In another embodiment, a device may modify priorities received from and / or transmitted to a network node (e.g., a 5G node B (gNodeB)). In yet another embodiment, modifying transmitted and / or received priorities may be performed by an entity other than a device, for example, a network node (e.g., an evolved node B (eNodeB), a gNodeB, a roadside unit (RSU), a mobility management entity (MME), or an access and mobility management function (AMF)).

[0076] node

[0077] Figure 7 is a block diagram of a node 700 according to some embodiments of the present disclosure. The node 700 may be of type A, type B, type C, or any other type of UE. The node 700 may be mounted on a moving vehicle or in a fixed position. The node 700 may take any form, including but not limited to a vehicle, a component mounted on a vehicle, a roadside unit, a laptop computer, a mobile phone, a wireless handheld device, or a wireless personal device, or any other form. Any reference in the foregoing description to a UE performing a certain function may be replaced with a node performing the same function without changing the operation or function of any of the elements described herein.

[0078] Referring to Figure 7, node 700 includes antenna 702 used to transmit or receive electromagnetic signals to / from a base station or other UE. Antenna 702 consists of one or more Antenna elements may be included, and different input / output antenna configurations may be enabled, such as a multiple-input multiple-output (MIMO) configuration, a multiple-input single-output (MISO) configuration, and a single-input multiple-output (SIMO) configuration. In some embodiments, antenna 702 may include multiple (e.g., 10 or 100) antenna elements, enabling multi-antenna functions such as beamforming. In some embodiments, antenna 702 is a single antenna.

[0079] Node 700 includes a transceiver 704 connected to antenna 702. Transceiver 704 may also be a wireless transceiver in node 700 and may communicate bidirectionally with a base station or other UE. For example, transceiver 704 may receive / transmit wireless signals to / from a base station via downlink / uplink communication. Transceiver 704 may also receive / transmit wireless signals to / from other UE or RSU via sidelink communication. Transceiver 704 may include a modem that modulates packets, provides the modulated packets to antenna 702 for transmission, and demodulates packets received from antenna 702.

[0080] Device 700 may include memory 706. Memory 706 may be any type of computer-readable storage medium, including volatile or non-volatile memory devices, or a combination thereof. Computer-readable storage medium includes, but is not limited to, non-temporary computer storage medium. Non-temporary storage medium may be accessed by a general-purpose computer or a dedicated computer. Examples of non-temporary storage medium include, but are not limited to, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable ROM (EEPROM), digital multipurpose disks (DVDs), flash memory, compact disk (CD)ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, etc. Non-temporary medium may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by a general-purpose or dedicated computer, or a general-purpose or dedicated processor. In some examples, software / program code may be transmitted from a remote source (e.g., a website, server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave fall within the definition of a medium. Combinations of the above examples also fall within the scope of a computer-readable medium.

[0081] Memory 706 may store an identifier for node 700 and information about signals and / or data received by antenna 702. Memory 706 may also store post-processing signals and / or data. Memory 706 may also store computer-readable program instructions, mathematical models, and algorithms used for signal processing in transceiver 704 and calculations in processor 708. Memory 706 may further store computer-readable program instructions for operating node 700 to perform various functions described in this disclosure by being executed by processor 1408. In some examples, memory 706 may include a basic input / output system (BIOS) that controls basic hardware or software operations, such as interactions with peripheral components or devices. In some embodiments, node 700 is a type A UE and memory 706 includes both LTE SL modules and NR SL modules. In some embodiments, node 700 is a type B UE and memory 706 includes only NR SL modules. In some embodiments, node 700 is a type C This is the UE, and memory 706 includes only the LTE SL module.

[0082] The computer-readable program instructions of this disclosure may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​and conventional procedural programming languages. The computer-readable program instructions may be executed entirely on a computing device as a standalone software package, or remotely from a first computing device, partially on the first computing device and partially on a second computing device. In the latter scenario, the second remote computing device may be connected to the first computing device through any type of network, including a local area network (LAN) or a wide area network (WAN).

[0083] Node 700 may include a processor 708, which includes a hardware device having processing capabilities. The processor 708 may include at least one of the following: a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or other programmable logic device. Examples of general-purpose processors include, but are not limited to, a microprocessor, any conventional processor, a controller, a microcontroller, or a state machine. In some embodiments, the processor 708 may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). The processor 708 may receive downlink or sidelink signals from the transceiver 704 and further process the signals. The processor 708 may also receive data packets from the transceiver 704 and further process the packets. In some embodiments, the processor 708 may be configured to operate memory using a memory controller. In some embodiments, the memory controller may be integrated into the processor 708. The processor 708 may be configured to execute computer-readable instructions stored in memory (e.g., memory 706) in order to cause the node 700 to perform various functions.

[0084] Node 700 may include a Global Positioning System (GPS) 710. The GPS 710 may be used to enable location-based services or other services based on the geographical location of Node 700 and / or synchronization between UEs. The GPS 710 may receive Global Navigation System (GNSS) signals from a single satellite or from multiple satellites via antenna 702 and may provide the geographical location of Node 700 (e.g., the coordinates of Node 700).

[0085] Node 700 may include an input / output (I / O) device 712 used to communicate the results of signal processing and calculations to a user or other device. The I / O device 712 may include a user interface, including a display and an input device for sending user commands to the processor 708. The display may be configured to show the status of signal reception at node 700, data stored in memory 706, the status of signal processing, and the results of calculations. The display may include a cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), gas plasma display, touchscreen, or other image projection device for displaying information to the user. However, it is not limited to these. An input device may be any type of computer hardware device used to receive data and control signals from a user. An input device may include, but is not limited to, a keyboard, mouse, scanner, digital camera, joystick, trackball, cursor directional keys, touchscreen monitor, or audio / video commander.

[0086] Node 700 may further include machine interfaces 714 such as an electric bus that connects to a transceiver 704, memory 706, processor 708, GPS 710, and I / O device 712.

[0087] In some embodiments, node 700 may be configured for sidelink communication or may be programmed for sidelink communication. Processor 708 may be configured to perform background channel sensing by executing instructions stored in memory 706. Processor 708 may be configured to execute instructions to collect at least one of sidelink sensing information or resource reservation information for a first sidelink communication, and instructions to collect at least one of sidelink sensing information or resource reservation information for a second sidelink communication. Processor 708 may be configured to execute instructions to determine one or more candidate resources based on at least one of the sidelink sensing information for the first sidelink communication, the resource reservation information for the first sidelink communication, the sidelink sensing information for the second sidelink communication, or the resource reservation information for the second sidelink communication. The processor 708 may be configured to execute instructions for selecting one or more resources from one or more candidate resources, instructions for checking resource availability for at least one packet arriving after resource selection based on re-evaluation of one or more selected resources or preemption of one or more selected resources, and instructions for determining whether resource re-selection is necessary. If the processor 708 determines that resource re-selection is not necessary, the processor 708 may be configured to execute instructions for sending one or more packets using one or more selected resources. If the processor 708 determines that resource re-selection is necessary, the processor 708 may be configured to repeat the method, starting from collecting at least one of sidelink resource sensing information or resource reservation information for the first sidelink communication.

[0088] In some embodiments, node 700 may be configured for sidelink communication or may be programmed for sidelink communication. Processor 708 may be configured to execute instructions stored in memory 706 for performing methods of changing communication priority at a node, such as method 400 as described in conjunction with Figure 4, method 500 as described in conjunction with Figure 5, or method 600 as described in conjunction with Figure 6.

[0089] In embodiments where node 700 is a type A UE, node 700 may include a first radio access technology (RAT1) module 720 communicating with bus 714 and a second radio access technology (RAT2) module 722 communicating with bus 714. In some embodiments, the RAT1 module 720 may be configured as a first RAT, for example, to implement LTE. In some embodiments, the RAT2 module 722 may be configured as a second RAT different from the first RAT, for example, to implement NR. It should be noted that the type of RAT implemented by the RAT modules 720, 722 is not limited to LTE and NR. The RAT modules 720, 722 can implement any type of RAT without changing the operating principle of the embodiments described herein.

[0090] In embodiments where node 700 is a type B UE or a type C UE, node 700 includes only one RAT module (e.g., RAT1 module 720). RAT1 module 720 may implement any type of RAT, e.g., LTE, NR, or other types of RAT. In Figure 7, RAT2 module 722 is shown with a dashed outline to indicate that it may not be included in some embodiments.

[0091] Any of the embodiments described herein may be used simultaneously or in combination. Various combinations of embodiments may be controlled by one or more parameters using the same embodiments described herein with respect to providing those parameters to the UE. In another embodiment, any embodiment described herein may be conditionally applied to a UE that is a sidelink coexistence setting.

[0092] Any embodiment described herein may be conditionally applicable to a UE operating at the same resource pool or carrier frequency as the one being detected.

[0093] Any of the embodiments described herein may be applied to 3GPP sidelinks. This may be applied, for example, to NR sidelinks and / or LTE-NR sidelink coexistences of Release 18 (e.g., in the case of sidelinks with unauthorized access). However, the embodiments described herein are not limited to this technology and may be applied to other wireless communication technologies, such as, but are not limited to, Digital Enhanced Cordless Telecommunications / Digital European Cordless Telecommunications (DECT) or IEEE 802.11, e.g., Wi-Fi.

[0094] Where used in this disclosure, the use of the term "or" within a list of items indicates an inclusive list. A list of items may begin with phrases such as "at least one of" or "one or more of." For example, the list "at least one of A, B, or C" includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A, B, and C). Furthermore, where used in this disclosure, beginning a list of conditions with the phrase "based on" shall not be construed as "based on only" a set of conditions, but rather as "based on at least a portion" of the set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B without exceeding the scope of this disclosure.

[0095] In this specification, the terms “comprise,” “include,” and “contain” may be used interchangeably and may have the same meaning, and shall be interpreted as open-ended. The terms “comprise,” “include,” and “contain” may be used before a list of elements to indicate that at least all of the elements listed in the list are present, but other elements not listed may also be present. For example, if A includes B and C, then both {B,C} and {B,C,D} are within the scope of A.

[0096] This disclosure describes, in relation to the accompanying drawings, all exemplary configurations or configurations within the scope of this disclosure that are not representative of all possible examples. The term “exemplary” should not be interpreted as “preferred” or “advantageous compared to other examples,” but rather as “example, case, or illustration.” By reading this disclosure, including the description of embodiments and drawings, a person skilled in the art will understand that the art disclosed herein may be carried out using alternative embodiments. A person skilled in the art will understand that the embodiments described herein, or certain features of embodiments, may be combined to arrive at other embodiments for practicing the art described herein. Thus, the disclosure is not limited to the examples and designs described herein, but the principles and novelty disclosed herein are not limited to those described herein. The broadest possible range that matches the characteristics should be given.

[0097] The flowcharts and block diagrams in the drawings illustrate examples of the architecture, function, and operation of possible embodiments of systems, methods, and devices according to various embodiments. Note that in some alternative embodiments, the functions described in the blocks may occur in an order other than that shown in the drawings. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or blocks may be executed in reverse order depending on the functions involved. Similarly, additional steps may be included in such methods, and certain steps may be omitted or combined in methods according to various embodiments.

[0098] The described embodiments are not mutually exclusive, and it should be understood that elements, components, materials, or steps described in relation to one exemplary embodiment may be combined with other embodiments in an appropriate manner to achieve the desired design objective, or may be removed from other embodiments.

[0099] Any reference in this specification to “some embodiments” or “some exemplary embodiments” means that certain features, structures, or characteristics described in relation to an embodiment may be included in at least one embodiment. Any occurrences of the phrases “one embodiment,” “some embodiments,” or “another embodiment” in various parts of this disclosure do not necessarily refer to the same embodiment, nor do they necessarily represent separate or alternative embodiments that exclude each other.

[0100] Furthermore, unless otherwise specified or the context makes it clear that the subject matter is singular, the articles “a” and “an” used in this disclosure and the attached claims should generally be interpreted as meaning “one or more.”

[0101] Unless explicitly stated otherwise, each number and range should be interpreted as an approximation, as if the words "about" or "approximately" preceded the value or range value.

[0102] The elements of the claims of the following methods are listed in a specific sequence, if any, but unless the enumeration of the claims separately suggests a specific sequence for carrying out some or all of those elements, those elements are not necessarily intended to be limited to being carried out in that specific sequence.

[0103] Certain features of this disclosure are described in the context of separate embodiments for clarity and should be understood to be provided in combination in a single embodiment. Conversely, various features of the specification are described in the context of a single embodiment for brevity and may also be provided separately, in any suitable subcombination, or as appropriate in any other described embodiment of the specification. Certain features described in the context of different embodiments are not essential features of those embodiments unless otherwise stated.

[0104] It should be further understood that various modifications, substitutions, and variations of the details, materials, and arrangement of the parts described and shown to illustrate the nature of the described embodiments can be made by those skilled in the art without departing from the scope. Accordingly, the following claims encompass all such substitutions, modifications, and variations that fall within the scope of the claims.

[0105] Note 1: A method for changing the communication priority at a node, Associating the first priority with the first communication, Associating the second priority with the second communication, Based on one or more conditions, change at least one of the first priority or the second priority, Regarding the priority after the change, it is determined which of the first communication or the second communication has a higher priority, Based on the higher priority determined, process at least one of the first or second communications, including, method.

[0106] Note 2: The first priority and the second priority are stored by the node before the processing. The method described in Appendix 1.

[0107] Note 3: The first priority and the second priority are received by the node before the processing. The method described in Appendix 1.

[0108] Note 4: The first priority and the second priority are received by the node from other nodes. The method described in Appendix 3.

[0109] Note 5: The first priority is received via a first radio access technology (RAT) module included in the node, and the second priority is received via a second radio access technology (RAT) module included in the node. The method described in Appendix 1.

[0110] Note 6: The node includes one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The method described in Appendix 1.

[0111] Note 7: Each of the first and second priorities includes one of the following: 5G quality of service identifier, quality of service class indicator, PC5 interface quality of service identifier, per-packet priority for proximity-based services, Layer 1 / Layer 2 priority, quality of service priority, or application priority. The method described in Appendix 1.

[0112] Note 8: The above change includes at least one of the following: increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority. The method described in Appendix 1.

[0113] Note 9: The one or more conditions mentioned above are, The cost of discarding the first communication or the second communication, Whether the first communication or the second communication is a retransmission or a series of transmissions, Whether or not there is a collision between the first communication and the second communication, A measurement including at least one of the following: reference signal received power, received signal strength index, signal-to-interference noise ratio, or energy measurement; Channel busy rate, Packet delay budget, Whether the first communication or the second communication includes a media access control (MAC) control element (CE), Whether the first communication or the second communication includes user device coordination information, The cast type of the first or second communication includes one of unicast, groupcast, or broadcast, Whether the first communication or the second communication is associated with a specific channel, Whether one or more of the first or second communications are related to one or more of specific radio access technologies (RATs), including at least one of the following: The method described in Appendix 1.

[0114] Note 10: The specific channel includes one of the following: a physical sidelink sharing channel, a physical sidelink control channel, or a physical sidelink feedback channel. The method described in Appendix 9.

[0115] Clause 11: The changes described above occur on a transport block basis. The method described in Appendix 1.

[0116] Note 12: Each of the first and second communications includes one or more radio access technologies (RATs), including one or more of the following: next-generation radio, next-generation radio sidelink, long-term evolution, long-term evolution sidelink, 5G, new radio, or IEEE 802.11. The method described in Appendix 1.

[0117] Note 13: The process includes one of the following: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication. The method described in Appendix 1.

[0118] Note 14: Further includes transmitting the modified first priority or the modified second priority to other nodes. The method described in Appendix 1.

[0119] Note 15: The other nodes include any one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The method described in Appendix 14.

[0120] Note 16: The above changes apply to only one or more of the initial priorities. The method described in Appendix 1.

[0121] Note 17: A node that changes the communication priority, Memory configured to store instructions, Associating the first priority with the first communication, Associating the second priority with the second communication, Based on one or more conditions, change at least one of the first priority or the second priority, Regarding the priority after the change, it is determined which of the first communication or the second communication has a higher priority, Based on the higher priority determined, process at least one of the first or second communications, A processor configured to execute the instructions stored in the memory for performing the following: Equipped with, node.

[0122] Note 18: The aforementioned processor is Prior to the aforementioned processing, the system is further configured to store the first priority and the second priority. The node described in Appendix 17.

[0123] Note 19: The aforementioned processor is The system is further configured to receive the first priority and the second priority before the aforementioned processing. The node described in Appendix 17.

[0124] Note 20: The aforementioned processor is Further configured to receive the first priority and the second priority from other nodes, The node described in Appendix 19.

[0125] Note 21: A first radio access technology (RAT) module configured to receive the first priority, A second radio access technology (RAT) module configured to receive the second priority, Furthermore, The node described in Appendix 17.

[0126] Note 22: The node includes one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The node described in Appendix 17.

[0127] Note 23: Each of the first and second priorities includes one of the following: 5G quality of service identifier, quality of service class indicator, PC5 interface quality of service identifier, per-packet priority for proximity-based services, Layer 1 / Layer 2 priority, quality of service priority, or application priority. The node described in Appendix 17.

[0128] Note 24: The processor is configured to change at least one of the first priority or the second priority by performing at least one of the following: increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority. The node described in Appendix 17.

[0129] Note 25: The one or more conditions mentioned above are, The cost of discarding the first communication or the second communication, Whether the first communication or the second communication is a retransmission or a series of transmissions, Whether or not there is a collision between the first communication and the second communication, A measurement including at least one of the following: reference signal received power, received signal strength index, signal-to-interference noise ratio, or energy measurement; Channel busy rate, Packet delay budget, Whether the first communication or the second communication includes a media access control (MAC) control element (CE), Whether the first communication or the second communication includes user device coordination information, The cast type of the first or second communication includes one of unicast, groupcast, or broadcast. Whether the first communication or the second communication is associated with a specific channel, Whether one or more of the first or second communications are related to one or more of specific radio access technologies (RATs), including at least one of the following: The node described in Appendix 17.

[0130] Note 26: The specific channel includes one of the following: a physical sidelink sharing channel, a physical sidelink control channel, or a physical sidelink feedback channel. The node described in Appendix 25.

[0131] Note 27: The processor is configured to perform the above-mentioned changes on a transport block basis. The node described in Appendix 17.

[0132] Note 28: Each of the first and second communications includes one or more radio access technologies (RATs), including one or more of the following: next-generation radio, next-generation radio sidelink, long-term evolution, long-term evolution sidelink, 5G, new radio, or IEEE 802.11. The node described in Appendix 17.

[0133] Note 29: The processor is configured to process at least one of the first or second communications by performing one of the following: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication. The node described in Appendix 17.

[0134] Note 30: The aforementioned processor is Further configured to transmit the modified first priority or the modified second priority to other nodes, The node described in Appendix 17.

[0135] Note 31: The other nodes include any one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The node described in Appendix 30.

[0136] Note 32: The processor is configured to change only one or more of the initial priorities. The node described in Appendix 17.

[0137] Note 33: A non-temporary computer-readable medium for storing instructions that can be executed by one or more processors of a node for performing a method, wherein the method is Associating the first priority with the first communication, Associating the second priority with the second communication, Based on one or more conditions, change at least one of the first priority or the second priority, Regarding the priority after the change, it is determined which of the first communication or the second communication has a higher priority, Based on the higher priority determined, process at least one of the first or second communications, including, Non-temporary computer-readable media.

Claims

1. A method for changing the communication priority at a node, Associating the first priority with the first communication, Associating the second priority with the second communication, Based on one or more conditions, change at least one of the first priority or the second priority, Regarding the priority after the change, it is determined which of the first communication or the second communication has a higher priority, Based on the higher priority determined above, process at least one of the first communication or the second communication, including, method.

2. The first priority and the second priority are stored by the node before the processing. The method according to claim 1.

3. The first priority and the second priority are received by the node before the processing, The method according to claim 1.

4. The first priority and the second priority are received by the node from other nodes. The method according to claim 3.

5. The first priority is received via a first radio access technology (RAT) module included in the node, and the second priority is received via a second radio access technology (RAT) module included in the node. The method according to claim 1.

6. The node includes one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The method according to claim 1.

7. Each of the first and second priorities includes one of the following: 5G quality of service identifier, quality of service class indicator, PC5 interface quality of service identifier, per-packet priority for proximity-based services, Layer 1 / Layer 2 priority, quality of service priority, or application priority. The method according to claim 1.

8. The aforementioned modification includes at least one of the following: increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority. The method according to claim 1.

9. The one or more of the above conditions are, The cost of discarding the first communication or the second communication, Whether the first communication or the second communication is a retransmission or a series of transmissions, Whether or not there is a collision between the first communication and the second communication, A measurement including at least one of the following: reference signal received power, received signal strength index, signal-to-interference noise ratio, or energy measurement; Channel busy rate, Packet delay budget, Whether the first communication or the second communication includes a media access control (MAC) control element (CE), Whether the first communication or the second communication includes user device coordination information, The cast type of the first or second communication includes one of unicast, groupcast, or broadcast, Whether the first communication or the second communication is associated with a specific channel, or Whether one or more of the first or second communications are related to one or more of specific radio access technologies (RATs), Including at least one of the following: The method according to claim 1.

10. The aforementioned specific channel includes one of the following: a physical sidelink sharing channel, a physical sidelink control channel, or a physical sidelink feedback channel. The method according to claim 9.

11. The aforementioned changes occur on a transport block basis. The method according to claim 1.

12. Each of the first and second communications includes one or more radio access technologies (RATs), including one or more of the following: next-generation radio, next-generation radio sidelink, long-term evolution, long-term evolution sidelink, 5G, new radio, or IEEE 802.

11. The method according to claim 1.

13. The process includes one of the following: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication. The method according to claim 1.

14. Further comprising transmitting the modified first priority or the modified second priority to other nodes, The method according to claim 1.

15. The aforementioned other nodes include one of the following: user equipment, evolved node B, next-generation node B, roadside equipment, mobility management entity, or access and mobility management function. The method according to claim 14.

16. The aforementioned changes apply to only one or more of the initial priorities. The method according to claim 1.

17. A node for changing communication priority, Memory configured to store instructions, Associating the first priority with the first communication, Associating the second priority with the second communication, Based on one or more conditions, change at least one of the first priority or the second priority, Regarding the priority after the change, it is determined which of the first communication or the second communication has a higher priority, Based on the higher priority determined above, process at least one of the first communication or the second communication, A processor configured to execute the instructions stored in the memory for performing the following: Equipped with, node.

18. The aforementioned processor, The system is further configured to store the first priority and the second priority before the aforementioned processing. The node according to claim 17.

19. The aforementioned processor, The system is further configured to receive the first priority and the second priority before the aforementioned processing. The node according to claim 17.

20. A first radio access technology (RAT) module configured to receive the first priority, A second radio access technology (RAT) module configured to receive the second priority, Furthermore, The node according to claim 17.

Images