Changing communication priority at node in communication network

Abstract

Methods, apparatuses, and systems for changing communication priority at a node are disclosed. The method includes associating a first priority with a first communication; associating the second priority with the second communication; changing at least one of the first priority or the second priority based on one or more conditions; determining whether the first communication or the second communication has a higher priority after the change; and processing at least one of the first communication or the second communication based on the determined higher priority.

Description

Cross Reference to Related Applications

[0001] This application claims the priority benefit of U.S. Provisional Patent Application No. 63 / 457,263, filed April 5, 2023, entitled “SCHEMES FOR COEXISTENCE BETWEEN CHANNELS, OR RADIO ACCESS TECHNOLOGIES,” the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] Apparatuses and methods consistent with the present disclosure relate generally to communications, and more particularly, to methods, systems, and devices for changing a communication priority of one or more communications at a node in a communication network. BACKGROUND

[0003] Sidelink (SL) communication is used in 3GPP radio interfaces to allow two or more wireless devices or User Equipments (UEs) to communicate directly between them. This can happen within 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 within the coverage of the network. Direct device-to-device communication uses the PC5 interface.

[0004] Sidelink communication is used for Vehicle-to-Everything (V2X) applications, also known as V2X. SL devices can transmit and receive using various Radio Access Technologies (RATs) such as Long Term Evolution (LTE) SL, Next Radio (NR) SL, or both. When LTE SL modules and NR SL modules coexist in the same device, this can present implementation challenges. For example, if a close frequency separation is used, then using two Radio Frequency (RF) chains (e.g., separate hardware for transmitting and receiving on two frequencies) would result in additional hardware cost and battery consumption for the device. Therefore, in 3GPP Release 16, the concept of In-Device Coexistence (IDC) between LTE-V2X and NR-V2X sidelinks was introduced. If a close enough frequency separation between the two RATs is deployed, then one implementation choice is to implement a single RF chain in the UE under the assumption that the UE does not need to transmit and receive on the sidelinks simultaneously.

[0005] If a single RF chain is implemented in the UE, interference between two RAT receptions can occur in the UE if the frequencies of the two RATs are close and if the time resource pools configured or pre-configured for the two sidelink RATs overlap. Also, due to the half duplex constraint (e.g., cannot transmit and receive in the same frequency simultaneously), one RAT cannot receive / transmit while the other RAT does the opposite. Also, due to the single power budget of the UE, simultaneous transmission on both RATs can not be possible. This is why in Rel-16, the concept of inter-RAT priority for transmission and reception of LTE SL and NR SL was introduced for in-device coexistence. The concept applies to all signals, i.e., Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Feedback Channel (PSFCH) for transmission and reception of LTE SL and NR SL (PSFCH is specific to NR SL). For the case of transmission / transmission overlap, if both priorities are known, the RAT with higher priority is selected. The same principle applies for the case of transmission / reception overlap between two RATs, if both priorities are known. This requires aligning the subframe boundaries of the two channels / signals. Other cases of reception / reception overlap, equal priority, and unknown priority are left to device implementation. SUMMARY

[0006] According to some embodiments of the present disclosure, a method for changing a communication priority at a node is provided. 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 priority or the second priority based on one or more conditions, determining whether the first communication or the second communication has a higher priority after the change, and processing at least one of the first communication or the 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 configured to store instructions and a processor configured to execute the instructions stored in the memory to associate a first priority with a first communication, associate a second priority with a second communication, change at least one of the first priority or the second priority based on one or more conditions, determine whether the first communication or the second communication has a higher priority after the change, and process at least one of the first communication or the second communication based on the determined higher priority.

[0008] According to some embodiments of the present disclosure, a non-transitory computer-readable medium storing instructions executable by one or more processors of a node to perform a method is provided. 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 priority or the second priority based on one or more conditions, determining whether the first communication or the second communication has a higher priority after the change, and processing at least one of the first communication or the second communication based on the determined higher priority. BRIEF DESCRIPTION OF DRAWINGS

[0009] [ Figure 1 ] Figure 1 is a schematic diagram illustrating a device type for dynamic coexistence of a first sidelink communication and a second sidelink communication in accordance with some embodiments of the present disclosure. [ Figure 2 ] Figure 2 is a schematic diagram illustrating information transfer from a LTE sidelink module to a NR sidelink module in a node in accordance with some embodiments of the present disclosure. [ Figure 3 ] Figure 3 is a schematic diagram illustrating enhanced In-Device Coexistence (eIDC) using additional information and / or interfaces in accordance with some embodiments of the present disclosure. [ Figure 4 ] Figure 4 is a flowchart of an example method for changing a priority of a communication at a node in accordance with some embodiments of the present disclosure. [ Figure 5 ] Figure 5 is a flowchart of another example method for changing a priority of a communication at a node in accordance with some embodiments of the present disclosure. [ Figure 6 ] Figure 6 is a flowchart of another example method for changing a priority of a communication at a node in accordance with some embodiments of the present disclosure. [ Figure 7 ] Figure 7 is a block diagram illustrating a node that is in compliance with some embodiments of the present disclosure. DETAILED DESCRIPTION

[0010] Reference will now be made in detail to the example embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers represent the same or similar elements between the several figures. The implementation set forth in the following description of example embodiments is not meant to be

[0011] Dynamic co-existence of Release 18 LTE sidelink and NR sidelink

[0012] As part of the work of 3GPP, one objective is the co-existence of LTE sidelink and NR sidelink. It has been considered that if necessary, study and specify mechanisms for co-existence of LTE sidelink and NR sidelink, including performance, necessity, feasibility, and potential specification impact, if any. It is also recommended to reuse the in-device co-existence framework defined in Release 16 as much as possible.

[0013] While semi-static frequency division multiplexing (FDM) or time division multiplexing (TDM) can achieve co-existence in theory, it can be inefficient because the allocated time and frequency resources can not change fast enough and thus can not be efficient enough to exploit changing situations (e.g., when the proportion of LTE SL and NR SL devices changes). In addition, for the case where all LTE SL resources are allocated by regulation or technical specification, semi-static time and frequency resource allocation can not be possible. This is why more flexible, more dynamic resource allocation is considered. This dynamic resource allocation uses a pool of time and frequency resources that potentially can be used by LTE SL and NR SL, with some additional rules being used to avoid one RAT interfering with the other.

[0014] Some embodiments of the present disclosure propose enhancements to the Release 16 in-device co-existence (IDC) scheme to achieve Release 18 dynamic LTE / NR sidelink co-existence.

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

[0016] As part of the 3GPP discussions, Device Type A is defined as a device that includes both an LTE SL module and an NR SL module, where the NR SL module is able to receive information from the LTE SL module. To study the feasibility of dynamic resource sharing as a possible solution for coexistence on the same channel, for 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 illustrating device types for dynamic coexistence of a first sidelink (SL) communication and a second SL communication, consistent with some embodiments of the present disclosure. Referring to Figure 1 At least three types of devices (Type A, Type B, and Type C) are considered in the present disclosure. Type A devices include a module for a first SL communication and a module for a second SL communication. Type B devices include only a module for the first SL communication. Type C devices include only a module for the second SL communication. For example, in one embodiment, Type A devices include both an LTE SL module and an NR SL module; Type B devices include only an NR SL module; and Type C devices include only an LTE SL module.

[0018] In some embodiments of the present disclosure, regarding intra-device coexistence (IDC) using priority as described above, not all co-priority events have the same outcome when dropping transmission or reception of one RAT. For example, dropping a single PSCCH / PSSCH retransmission can have little or no consequence. As another example, dropping an initial PSCCH / PSSCH transmission can cause a slight delay. As another example, dropping a PSFCH transmission / reception of NR SL can significantly degrade the reliability of NR SL communication.

[0019] The priority described in the present disclosure can be a 5QI priority (e.g., a 5G Quality of Service Identifier), a Quality of Service Class Indicator (QCI) priority (used in LTE), a Proximity based Services (ProSe) Per-Packet Priority (PPPP), an L1 / L2 priority, or any other priority related to Quality of Service or application priority.

[0020] Symmetrically, treating co-priorities similarly as done with current IDC can not always be efficient. For example, some co-priorities should not be treated similarly, such as blind retransmissions / repetitions, as their importance decreases in each transmission (as they provide less new mutual information / energy). Thus, some embodiments of the present disclosure improve the current 3GPP solution by proposing a more efficient in-device coexistence solution. For example, embodiments of the present disclosure allow the NR SL module to “force” the LTE SL module not to use certain resources.

[0021] In some embodiments of the present disclosure, the priority can be changed when transmitting and / or receiving data, data packets, signals, or messages to use a different priority. It should be noted that the term “communication” or “event” can be used herein to include data, data packets, signals, or messages. For example, if the priority change is performed by the NR SL module, the NR SL module can change its priority to be lower or higher than the initial priority of the communication. For example, if the NR SL priority is changed to a higher priority than the LTE SL priority, this allows the LTE SL module to be “forced” not to use certain resources. This functionality can be referred to herein as an enhanced IDC (eIDC) functionality.

[0022] Figure 2 An exemplary system diagram of a node 200 with Release 16 IDC and Release 18 information transfer from the LTE SL module to the NR SL module is shown, where the eIDC functionality described above resides in the NR SL module. As used herein, the term “node” can 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 with an eIDC component 208. The eIDC component 208 implements the eIDC functionality and can 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 Figure 2 In the illustrated embodiment, the NR SL module 206 can change its NR priority and send the changed NR priority to the device RAT controller 202 via the IDC interface 212.

[0025] In another example embodiment, the eIDC component 208 can be located in the device RAT controller 202 Figure 2 In this embodiment, the legacy Release 16 IDC interface can also be used.

[0026] In another example embodiment, the eIDC component 208 can be located in the LTE SL module 204 Figure 2 In this embodiment, the legacy Release 16 IDC interface can also be used.

[0027] Note that regardless of the location of the eIDC component 208 in the node 200, the eIDC component 208 will operate in a similar manner. It is also contemplated that, in some embodiments, changing the priority can be performed by the entity receiving the priority, rather than the entity sending the priority.

[0028] In another embodiment, the eIDC component 208 can estimate the cost of dropping a communication and use the estimated cost in the decision process. As an example, the cost of dropping for each entity (e.g., each RAT, such as LTE SL and NR SL) can be compared and used in the decision process. Dropping a communication can be considered part of increasing the priority or decreasing the priority. In some embodiments, whether a priority can be increased or decreased can depend on the RAT. For example, in some embodiments, it can not be possible to change the LTE SL priority; in this case, the communication will be dropped, rather than having its priority changed.

[0029] As another example, the cost function can associate events with weights. Some examples of events can be first retransmission, second retransmission, first repetition, second repetition, LTE event, NR event, LTE PC5 Interface Quality of Service Identifier (PQI), or NR PQI. If the weight of one event is higher than the weight of another event, this can result in an increase or decrease in priority. In some embodiments, the weights can be applied in case of equal original priority of the communication. In some embodiments, different types of weights can also be combined, e.g., LTE / NR (first type of weight) and first repetition / non-first repetition (second type of weight). In this example, the combination of different types of weights can be additive, weighted average, or other mathematical combination or comparison.

[0030] In another embodiment, in case of an upcoming conflict between LTE SL and NR SL time and / or frequency resources, the eIDC component 208 can decide whether it should increase the NR SL priority to avoid NR dropping. As described above, this can be combined with the use of a cost function.

[0031] In another embodiment, in case of an upcoming conflict between LTE SL and NR SL time and / or frequency resources, the eIDC component 208 can decide whether it should decrease the LTE SL priority to avoid NR dropping. As described above, this can be combined with the use of a cost function.

[0032] In another embodiment, in case of an upcoming conflict between LTE SL and NR SL time and / or frequency resources, the eIDC component 208 can decide whether it should increase the LTE SL priority to avoid LTE dropping. As described above, this can be combined with the use of a cost function.

[0033] In another embodiment, in case of an upcoming conflict between LTE SL and NR SL time and / or frequency resources, the eIDC component 208 can decide whether it should decrease the NR SL priority to avoid LTE dropping. As described above, this can be combined with the use of a cost function.

[0034] In another embodiment, the eIDC function can be performed by a module or entity that sends the 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. Thus, the provided priority can be increased or decreased, e.g., to avoid a conflict with NR SL resources or with another RAT or system.

[0035] In another embodiment, the eIDC functionality can be configured or preconfigured to always drop transmissions that overlap with one or more particular time and / or frequency resources. In another embodiment, the eIDC functionality can be configured to never drop transmissions that overlap with one or more particular time and / or frequency resources. For example, the eIDC functionality can be configured to always drop LTE transmissions that overlap with particular NR slots. In another embodiment, the eIDC functionality can be configured to never drop LTE transmissions that overlap with particular NR slots.

[0036] In another embodiment, some additional criteria can be used in the decision process, e.g., some measurements from one or more RATs, such as Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Signal to interference plus noise ratio (SINR), energy measurements, etc. One or more thresholds can be used for these criteria.

[0037] In another embodiment, the concept of availability or the degree of busyness / congestion of one or both signals in the signal can be used. For example, determining congestion can use Channel Busy Ratio (CBR). In one embodiment, the NR SL priority can be increased if the CBR determined by the NR SL module is lower than the CBR determined by the LTE SL module. In other embodiments, the priority associated can be increased or decreased if the CBR of a particular Radio Access Technology (RAT) is below or exceeds a threshold. In other embodiments, the priority associated can be increased or decreased if the CBR of a particular channel is below or exceeds a threshold.

[0038] In another embodiment, the Packet Delay Budget (PDB) can be used to determine whether to increase and / or decrease the priority. For example, the NR SL priority can be increased if the remaining PDB (in time) for NR SL transmissions is low (e.g., based on a threshold time interval or number of symbols before the budget expires).

[0039] In another embodiment, priority increase and / or decrease can be considered in case of transmission carrying Medium Access Control (MAC) Control Element (CE). For example, if the NR SL transmission includes SL Channel State Information (CSI) reporting MAC CE, the priority of the NR SL transmission can be increased. In another embodiment, if the NR SL transmission includes Inter-UE Coordination (IUC) information, the priority of the NR SL transmission can be increased and / or decreased.

[0040] In another embodiment, priority increase or decrease can be determined based on the cast type of the transmission. For example, if the transmission is at least one of unicast, groupcast and / or broadcast, priority increase can be performed on the module. In one embodiment, the cast types that should be converted to priority increase or decrease can be configured or pre-configured. In another example embodiment, if the NR SL transmission is a groupcast transmission for a group size higher than a configured threshold, the NR SL transmission can be prioritized.

[0041] In another embodiment, the eIDC function can be LTE RAT and / or NR RAT configuration aware. In another embodiment, the eIDC function can use LTE SL sensing information and / or LTE SL Resource Pool (RP) configuration information or pre-configuration information. In another embodiment, the eIDC function can use NR SL sensing information and / or NR SL Resource Pool (RP) configuration information or pre-configuration information. In case of eIDC using Release 16 IDC interface, the last three embodiments can give the example depicted in Figure 3

[0042] Figure 3 is a schematic diagram showing eIDC component 300 using additional information and / or interfaces in line with some embodiments of the present disclosure. The eIDC component 300 can communicate with other entities (e.g., LTE SL module, NR SL module or RAT controller) using IDC interface 302. The eIDC component 302 can receive LTE SL sensing information and LTE SL Resource Pool configuration information from LTE SL module 304. The eIDC component 302 can receive NR SL sensing information and NR SL Resource Pool configuration information from NR SL module 306.

[0043] ​In another embodiment, the eIDC function can decide which priority to change in case of equal priority events. As used herein, the term "equal priority events" indicates that the initial, un-changed priority of each event is the same. In another embodiment, the eIDC function can decide which priority to override in case of conflicting events. In another embodiment, the eIDC function can decide which priority to override based on the transmission block, e.g., data unit submitted by Layer 2. Examples of criteria used in the evaluation can be whether the transmission or reception is a repetition. Another example of criteria used in the evaluation can be whether the transmission or reception is a blind retransmission.

[0044] Some examples of criteria that can be used in the evaluation can be whether the transmission and / or reception applies to a specific channel, e.g., Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH). Some examples of criteria that can be used in the evaluation can be whether the transmission and / or reception applies to a repetition or a blind retransmission. Some examples of criteria that can be used in the evaluation can be whether the transmission and / or reception is an initial transmission, whether it is a PSCCH / PSSCH transmission that requires PSFCH Hybrid Automatic Repeat Request (HARQ) feedback, or whether it is a broadcast, groupcast or unicast transmission.

[0045] In another embodiment, it can be considered whether the transmission and / or reception will overlap with some configured or pre-configured resources or some protected resources. The protected resources can be, for example, a subset of the resources that can be configured or pre-configured. This can be indicated, for example, via Semi-Persistent Scheduling (SPS). In another embodiment, the protected resources can be considered protected only for some priorities, e.g., up to a certain priority. In one example, the criterion can be whether the LTE SL transmission overlaps with protected and configured or pre-configured NR SL slots. In another embodiment, any of the example schemes described in this disclosure can apply only for some priorities.

[0046] Example method for changing communication priority at a node

[0047] Figure 4 is a flowchart illustrating an example method 400 for changing communication priority at a node, consistent with some embodiments of the present disclosure. The method 400 can be performed by a node in a communication system, e.g., by a UE in a sidelink communication.

[0048] The method 400 includes a step 402 of associating a first priority with a first communication. For example, the first priority can 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 can be indicated as part of the first communication. As another example, the first priority can be received at the node separately from the first communication or can be generated by the node separately from the first communication.

[0049] The method 400 includes a step 404 of associating a second priority with a second communication. The second priority can be associated with the second communication in a similar manner as the first priority is associated with the second communication.

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

[0051] The method 400 includes a step 408 of determining which communication has a higher priority after the change is complete (i.e., identifying the communication that has a higher priority than the priority of one of the one or more other communications). After one or both of the priorities is changed, one of the communications can have a higher priority than the other communication(s).

[0052] The method 400 includes a step 410 of processing at least one of the communications based on the determined higher priority, i.e., processing the communication with the higher priority first. For example, a transceiver in the node can transmit the higher priority communication first.

[0053] Figure 5 is a flowchart illustrating an example method 500 for changing a priority of a communication at a node, consistent with some embodiments of the present disclosure. The method 500 can be performed by a node in a communication system, e.g., by a UE in a sidelink communication.

[0054] The method 500 includes a step 502 of associating a first priority with a first communication. For example, the first priority can 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 can be indicated as part of the first communication. As another example, the first priority can be received at the node separately from the first communication or can be generated by the node separately from the first communication.

[0055] The method 500 includes a step 504 of associating a second priority with a second communication. The second priority can be associated with the second communication in a similar manner as the first priority is associated with the first communication.

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

[0057] In some embodiments, each condition can have a ranking associated with the condition that can be used to determine in what order the multiple conditions are to be evaluated. In some embodiments, all applicable conditions are to be evaluated, and a condition to be evaluated can be selected randomly. In some embodiments, more than one potential condition can apply to the first communication. In some embodiments, more than one potential condition can apply to the second communication.

[0058] The method 500 includes a step 508 of changing the priority of the communication based on the applied condition. Changing the priority can 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 any combination of the two priorities. The change in priority can be applied in a relative manner or an absolute manner as compared to the initial priority. In the second case, a new priority is selected as compared to the initial priority without an arithmetic addition or subtraction. How the priority is changed (i.e., increased or decreased) can be associated with the particular condition that is considered when the priority is changed.

[0059] The method 500 includes a step 510 of determining whether other conditions are to be applied to the communication. As described above, multiple conditions can be applied to the first communication and the second communication. In some embodiments, more than one condition can be evaluated before a final determination is made as to whether one communication has a higher priority than the other communication. If other conditions are to be applied to the communication (step 510, “yes” branch), the method 500 returns to step 506 to select the next applicable condition to apply. If no other conditions are to be applied to the communication (step 510, “no” branch), the method 500 proceeds to step 512.

[0060] The method 500 includes a step 512 of determining which communication has a higher priority after the change is complete. After one or both of the priorities is changed, one of the communications can have a higher priority than the other communication(s).

[0061] The method 500 includes a step 514 of processing at least one of the communications based on the determined higher priority, i.e., the communication with the higher priority is processed first. For example, the transceiver in the node can transmit the higher priority communication first.

[0062] Figure 6 is a flowchart illustrating an exemplary method 600 for changing communication priorities at a node, consistent with some embodiments of the present disclosure. The method 600 can be performed by a node in a communication system, e.g., by a UE in a sidelink communication. For purposes of illustration, assume that the method 600 is performed in a node that includes an LTE SL module and an NR SL module.

[0063] The method 600 includes a step 602 of obtaining sensing information from the NR SL module and the LTE SL module. For example, the eIDC component can reside in the NR SL module, the LTE SL module, or the RAT controller of the node, as described elsewhere in the present disclosure, and can receive the sensing information from the NR SL module and the LTE SL module.

[0064] The method 600 includes a step 604 of predicting whether there will be any in-device coexistence conflicts. Based on the received sensing information, it can be predicted whether there will be any in-device coexistence conflicts, e.g., via transmissions of both the NR SL module and the LTE SL module.

[0065] The method 600 includes a step 606 of estimating whether the NR communication or the LTE communication is a PSSCH repetition or a blind retransmission. The estimation can be made based on information contained in the communication, e.g., a channel type associated with the communication or a transmission type associated with the communication.

[0066] The method 600 includes a step 608 of determining a cost of dropping the NR communication and the LTE communication. The cost associated with the NR communication and the LTE communication can include a numerical value associated with the communication, and utilize a weight as described elsewhere in the present disclosure.

[0067] The method 600 includes a step 610 of determining whether the LTE communication priority is higher than the NR communication priority. For example, the LTE communication priority and the NR communication priority can be represented as numerical values, and the determination can include comparing the values to determine which numerical value is higher. Note that other representations of priority and comparison can be applied. If the LTE communication priority is higher than the NR communication priority (step 610, “yes” branch), the method 600 continues with a step 612. If the LTE communication priority is not higher than the NR communication priority (step 610, “no” branch), the method 600 continues with a step 616.

[0068] The method 600 includes a step 612 of determining whether the cost of dropping the NR communication is higher than the cost of dropping the LTE communication. If the cost of dropping the NR communication is higher than the cost of dropping the LTE communication (step 612, “yes” branch), the method 600 continues with a step 614. If the cost of dropping the NR communication is not higher than the cost of dropping the LTE communication (step 612, “no” branch), the method 600 continues with a step 616.

[0069] The method 600 includes a step 614 of increasing the NR communication priority and signaling the increased priority using the IDC interface. For example, the increased priority can be signaled to a transceiver in the node to transmit or receive the NR communication. The increased priority can be used by the receiving node for potential transmission or reception.

[0070] The method 600 includes a step 616 of determining whether the LTE communication overlaps with a protected and configured or preconfigured NR time slot. If the LTE communication overlaps with the protected and configured or preconfigured NR time slot (step 616, “yes” branch), the method 600 continues with the step 614. If the LTE communication does not overlap with the protected and configured or preconfigured NR time slot (step 616, “no” branch), the method 600 continues with a step 618.

[0071] The method 600 includes a step 618 of not adjusting any communication priority. Then, the priorities of the LTE communication and the NR communication can be compared prior to potential transmission or reception.

[0072] In some embodiments, changing the priority can be performed only at certain times and / or following certain criteria / criteria. For example, a device history can be used. For example, if one RAT is in disadvantage compared to another RAT (i.e., one RAT has more transmission or reception than another RAT), a change of priority can be performed to favor the RAT in disadvantage. This can be based on channel busy ratio (CBR) and / or some measurements (e.g., RSRP, RSSI, SINR, energy measurement). The evaluation can be performed on a previous time period basis. This can use thresholds in the decision process. For example, if one RAT and / or the CBR of the measurement is above a certain threshold, the priority can be changed to favor the RAT in disadvantage. Alternatively or additionally, if one RAT has been in advantage for more than a certain duration, the priority can be changed to favor the RAT in disadvantage. Alternatively or additionally, the condition to favor the RAT in disadvantage can be that one or more conditions are considered below respective thresholds associated with those conditions.

[0073] Embodiments of the present disclosure can include Release 18 NR sidelink and LTE sidelink radios and software incorporated in, for example, vehicles. Moreover, embodiments described in the present disclosure can be used for future 3GPP sidelink technologies using similar sidelink mechanisms (e.g., between NR and 6G sidelink).

[0074] Any information, parameters, and / or thresholds described in the present disclosure can be provided to a device via configuration or pre-configuration. This can use, for example, a transmission from a network (e.g., using a Radio Resource Control (RRC) protocol, e.g., as described in 3GPP TS 38.331), or can use configuration information via a SIM / USIM (e.g., via a SIM toolkit).

[0075] Although exemplary embodiments of in-device coexistence (IDC) are described in the present disclosure, embodiments of the present disclosure are not limited to IDC. In one embodiment, a device can forward and change a priority received from a device to another (third) device. In another embodiment, a device can change a priority received from and / or transmitted to a network node (e.g., a 5G node B (gNodeB)) by the device. In another embodiment, changing a priority of transmission and / or reception can be performed by another entity other than a device, e.g., it can be performed by a network node (e.g., an evolved node B (eNodeB), a gNodeB, a road side 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 consistent with some embodiments of the present disclosure. The node 700 can be a Type-A, Type-B, Type-C, or any other type of UE. The node 700 can be installed in a mobile vehicle or in a fixed location. The node 700 can take any form including but not limited to a vehicle, a component installed in a vehicle, a road-side unit, a laptop computer, a wireless terminal including a cell phone, a wireless handheld device, or a wireless personal device, or any other form. In the foregoing description, any reference to a UE performing certain functions can be replaced with a node performing the same functions without changing the operation or functionality of any element described herein.

[0078] Referring to Figure 7 , the node 700 can include an antenna 702 that can be used to transmit electromagnetic signals to and receive electromagnetic signals from a base station or other UEs. The antenna 702 can include one or more antenna elements and can enable different input-output antenna configurations, such as Multiple Input Multiple Output (MIMO) configurations, Multiple Input Single Output (MISO) configurations, and Single Input Multiple Output (SIMO) configurations. In some embodiments, the antenna 702 can include a plurality of (e.g., tens or hundreds of) antenna elements and can enable multi-antenna functionality such as beamforming. In some embodiments, the antenna 702 is a single antenna.

[0079] The node 700 can include a transceiver 704 coupled to the antenna 702. The transceiver 704 can be a wireless transceiver at the node 700 and can communicate bi-directionally with base stations or other UEs. For example, the transceiver 704 can receive / send wireless signals from / to base stations via downlink / uplink communications. The transceiver 704 can also receive / send wireless signals from / to other UEs or RSUs via sidelink communications. The transceiver 704 can include a modem to modulate the packets and provide the modulated packets to the antenna 702 for transmission, and to demodulate packets received from the antenna 702.

[0080] The node 700 can include a memory 706. The memory 706 can be any type of computer-readable storage media including volatile or non-volatile storage devices, or a combination thereof. Computer-readable storage media includes, but is not limited to, non-transitory computer-readable media. Non-transitory storage media can be accessed by a general purpose or special purpose computer. Examples of non-transitory storage media include, but are not limited to, portable, compact fixed and removable media such as portable, compact disc read only memories (CD-ROMs), digital versatile disks (DVDs), flash memories, memory sticks, and the like. Non-transitory media can also include a data distribution system that is any entity or physical medium that enables access to the software, e.g., the Internet, home intranet, etc. In some examples, software / software code can be transmitted using a transitory medium, e.g., an electromagnetic signal such as a sound wave, radio wave, microwave, optical pixel, etc. In such examples, a transitory medium is en compassed by the definition of computer-readable medium. The memory 706 can store software / code 708 that can include computer program instructions that, when executed by the processor 702, implement the present disclosure, for example, as described herein. The software / code 708 can include, among other things, instructions for performing the operations described herein. The software / code 708 can be written in any combination of one or more computer languages. In some examples, the software / code 708 can be stored on and / or transmitted using computer-readable media.

[0081] Memory 706 can store information related to the identification of node 700 as well as signals and / or data received by antenna 702. Memory 706 can also store post-processed signals and / or data. Memory 706 can also store computer-readable program instructions, mathematical models, and algorithms used in signal processing in transceiver 704 and computations in processor 708. Memory 706 can also store computer-readable program instructions for execution by processor 708 to operate node 700 to perform various functions described in the present disclosure. In some examples, memory 706 can include a Basic Input / Output System (BIOS) that can control basic hardware or software operation such as the interaction with peripheral components or devices. In some embodiments, node 700 is a Type A UE and memory 706 includes both an LTE SL module and an NR SL module. In some embodiments, node 700 is a Type B UE and memory 706 includes only an NR SL module. In some embodiments, node 700 is a Type C UE and memory 706 includes only an LTE SL module.

[0082] The computer-readable program instructions of the present disclosure can be assembly instructions, Instruction-Set-Architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or any combination of source code or object code written in any combination of one or more programming languages, including an object oriented programming language and a conventional procedural programming language. The computer-readable program instructions can execute entirely on a computing device, or a portion of the computer-readable program instructions can execute on a first computing device, and another portion of the computer-readable program instructions can execute on a second computing device remote from the first computing device. In the latter scenario, the second computing device can 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] The node 700 can include a processor 708, which can include a hardware device that has processing capability. The processor 708 can include at least one of 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 a general-purpose processor 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 can be implemented using a combination of devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The processor 708 can receive a downlink signal or a sidelink signal from the transceiver 704 and further process the signal. The processor 708 can also receive data packets from the transceiver 704 and further process the data packets. In some embodiments, the processor 708 can be configured to operate memory using a memory controller. In some embodiments, the memory controller can be integrated into the processor 708. The processor 708 can be configured to execute computer-readable instructions stored in memory (e.g., the memory 706) to cause the node 700 to perform various functions.

[0084] The node 700 can include a global positioning system (GPS) 710. The GPS 710 can be used to enable location-based services or other services based on a geographic location of the node 700, and / or synchronization between UEs. The GPS 710 can receive global navigation satellite system (GNSS) signals from a single satellite or multiple satellite signals via the antenna 702 and provide a geographic location (e.g., coordinates) of the node 700.

[0085] The node 700 can include an input / output (I / O) device 712 that can be used to communicate signals and computational results to a user or other devices. The I / O device 712 can include a user interface comprising a display and input devices, such as a keyboard and a pointing device, for communicating user commands to the processor 708. The display can be configured to display the status of signal reception at the node 700, data stored at the memory 706, the status of signal processing, and results of computations, among other things. The display can include, but is not limited to, a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), a Light-Emitting Diode (LED), a plasma gas display, a touchscreen, or other image projection device for displaying information to a user. The input devices can be any type of computer hardware device for receiving data and control signals from a user. The input devices can include, but are not limited to, a keyboard, a mouse, a scanner, a digital camera, a joystick, a trackball, cursor direction keys, a touchscreen monitor, or an audio / video commander, among others.

[0086] The node 700 can also include a machine interface 714, such as an electrical bus connecting the transceiver 704, the memory 706, the processor 708, the GPS 710, and the I / O device 712.

[0087] In some embodiments, the node 700 can be configured or programmed for sidelink communications. The processor 708 can be configured to execute instructions stored in the memory 706 to perform a background channel sensing. The processor 708 can be configured to execute instructions to collect at least one of sidelink sensing information or resource reservation information for a first sidelink communication, and to collect at least one of sidelink sensing information or resource reservation information for a second sidelink communication. The processor 708 can 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 can be configured to execute instructions to select one or more resources among the one or more candidate resources, to check resource availability for at least one data packet that arrives after the resource selection based on a reevaluation of the selected one or more resources or preemption of the selected one or more resources, and to determine whether a resource reselection is needed. If the processor 708 determines that the resource reselection is not needed, the processor 708 can be configured to execute instructions to transmit the one or more data packets using the selected one or more resources. If the processor 708 determines that the resource reselection is needed, the processor 708 can be configured to iteratively perform the method starting from collecting at least one of the sidelink sensing information or the resource reservation information for the first sidelink communication.

[0088] In some embodiments, the node 700 can be configured or programmed for sidelink communications. The processor 708 can be configured to execute instructions stored in the memory 706 to perform a method for changing a communication priority at a node, such as the method 400 described in connection with Figure 4 the method 500 described in connection with Figure 5 the method 600 described in connection with Figure 6 .

[0089] In embodiments where the node 700 is a Type A UE, the node 700 can include a first radio access technology (RAT 1) module 720 in communication with the bus 714 and a second radio access technology (RAT 2) module 722 in communication with the bus 714. In some embodiments, the RAT 1 module 720 can be configured to implement a first RAT, e.g., LTE. In some embodiments, the RAT 2 module 722 can be configured to implement a second RAT different from the first RAT, e.g., NR. Note that the types of RATs implemented by the RAT modules 720, 722 are not limited to LTE and NR. The RAT modules 720, 722 can implement any type of RATs without changing the principles of operation of the embodiments described herein.

[0090] In embodiments in which the node 700 is a Type B UE or a Type C UE, the node 700 can include only one RAT module (e.g., RAT 1 module 720). The RAT 1 module 720 can implement any type of RAT, such as LTE, NR, or other types of RATs. In Figure 7 In some embodiments, the RAT 2 module 722 can not be included.

[0091] Any of the embodiments described herein can be used simultaneously or in combination. The combination of various embodiments can be controlled by one or more parameters using the same embodiments described herein with respect to providing these parameters to a UE. In another embodiment, any of the embodiments described herein can be conditionally applied to a UE in a sidelink coexistence setting.

[0092] Any of the embodiments described herein can be conditionally applied to a UE operating on the same resource pool or carrier frequency as the detected.

[0093] Any of the embodiments described in this disclosure can be applied to 3GPP sidelink. For example, this can be applied to Release 18 NR sidelink and / or Release 18 LTE-NR sidelink coexistence (e.g., sidelink for unlicensed access). However, the embodiments described in this disclosure are not limited to such technologies, but can also be applied to other wireless communication technologies, such as and not limited to Digital Enhanced Cordless Telecommunications / Digital European Cordless Telecommunications (DECT) or IEEE 802.11, e.g., Wi-Fi.

[0094] As used in this disclosure, the use of the term “or” in a list of items indicates an inclusive list. The list of items can be prefixed with a phrase such as “at least one of” or “one or more of.” For example, a list 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 and B and C). Furthermore, as used in this disclosure, a phrase referring to “based on” should not be construed to mean “based only on” a set of conditions, but rather “based at least in part on” the set of conditions. For example, a result described as “based on condition A” can be based on both condition A and condition B without departing from the scope of this disclosure.

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

[0096] The present disclosure describes example configurations that are not representative of all examples that can be implemented or all configurations within the scope of the present disclosure, in conjunction with the accompanying drawings. The term "exemplary" is not to be construed as "preferred" or "advantageous over other examples," but rather as "illustrative, example, or exemplary." Those of ordinary skill in the art, having the benefit of the description including the embodiments and drawings, will appreciate that the technology disclosed herein can be implemented using alternative embodiments. Those of ordinary skill in the art will appreciate that embodiments described herein or certain features of embodiments can be combined to obtain other embodiments for practicing the technology described in this disclosure. Accordingly, the present disclosure is not limited to the examples and designs described herein, but rather is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0097] The flow diagrams and the block diagrams in the drawings are examples of architectures, functionality, and operations that might be implemented in systems, methods, and apparatuses according to various embodiments. It should be noted that in some alternative implementations, the functions noted in the blocks might occur out of the order noted in the figures. For example, two blocks noted in succession might actually be executed substantially concurrently or the blocks might sometimes be executed in the reverse order, depending upon the functionality involved. As will be understood by those of skill in the art, such methods might be implemented in software, hardware, or a combination thereof.

[0098] It should be understood that the described embodiments are not mutually exclusive, and elements, components, materials or steps described in connection with one exemplary embodiment can be combined with other embodiments or eliminated from other embodiments in a suitable manner to achieve a desired design purpose.

[0099] Reference herein to "some embodiments" or "some example embodiments" means that a particular feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment. Occurrences of the phrases "one embodiment," "some embodiments," or "another embodiment" throughout the present disclosure are not necessarily all referring to the same embodiment, nor are they necessarily all mutually exclusive or alternative embodiments to the other.

[0100] Also, the articles "a" and "an" as used in the disclosure and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Thus, for example, "a" node can mean one or more nodes.

[0101] Unless specifically stated otherwise, each numerical value and range should be interpreted as approximately as if the word "about" preceded the respective numerical value or range.

[0102] Although the elements in the method claims, if any, are recited in a particular order, this should not be understood as a limitation on the order in which such elements are implemented. Rather, the elements as recited in the claims should be understood to be implemented in whatever order is most convenient for implementation.

[0103] It will be understood that certain features of the disclosure, which are, for clarity, described in the context of separate embodiments, can also be provided in combination in a single embodiment. Conversely, various features of the disclosure, which are, for brevity, described in the context of a single embodiment, can also be provided separately or in any suitable

[0104] It will be further understood that those skilled in the art, and given the benefit of this disclosure, can modify, alter, and / or adapt the details of the described embodiments without departing from the scope of the disclosure. Accordingly, the appended claims are intended to cover all such modifications, alterations, and / or adaptations as fall within the scope of aspects of the claims.

[0105] Clause 1 : A method for changing a communication priority at a node, the method comprising: associating a first priority with a first communication; associating a second priority with a second communication; based on one or more conditions, changing at least one of the first priority or the second priority; determining whether the first communication or the second communication has a higher priority after the change; and processing at least one of the first communication or the second communication based on the determined higher priority.

[0106] Clause 2: The method of clause 1, wherein the first priority and the second priority are stored by the node prior to the processing.

[0107] Clause 3: The method of clause 1, wherein the first priority and the second priority are received by the node prior to the processing.

[0108] Clause 4: The method of clause 3, wherein the first priority and the second priority are received by the node from another node.

[0109] Clause 5: The method of clause 1, wherein 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.

[0110] Clause 6: The method of clause 1, wherein the node comprises any of: a user equipment, an evolved NodeB, a next generation NodeB, a road side unit, a mobility management entity, or an access and mobility management function.

[0111] Clause 7: The method of clause 1, wherein each of the first priority and the second priority comprises any of: a 5G quality of service identifier, a quality of service class indicator, a PC5 interface quality of service identifier, a per-packet priority for proximity-based services, a layer 1 / layer 2 priority, a quality of service priority, or an application priority.

[0112] Clause 8: The method of clause 1, wherein the change comprises at least one of: increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority.

[0113] Clause 9: The method of clause 1, wherein the one or more conditions comprise at least one of: a cost of dropping the first communication or the second communication; whether the first communication or the second communication is a retransmission or a repetition; whether there will be a collision between the first communication and the second communication; a measurement, wherein the measurement comprises at least one of: a reference signal received power, a received signal strength indicator, a signal to interference noise ratio, or an energy measurement; a channel busy ratio; a packet delay budget; whether the first communication or the second communication includes a medium access control (MAC) control element (CE); whether the first communication or the second communication includes inter-user equipment coordination information; The broadcast type of the first communication or the second communication, wherein the broadcast type includes one of unicast, multicast or broadcast; Does the first or second communication involve a specific channel; or Whether one or more of the first or second communication involves one or more specific radio access technologies (RATs).

[0114] Clause 10: The method according to Clause 9, wherein the specific channel includes one of the following: a physical-side crosslink shared channel, a physical-side crosslink control channel, or a physical-side crosslink feedback channel.

[0115] Clause 11: The method described in Clause 1, wherein the change occurs on a transport block basis.

[0116] Clause 12: The method according to Clause 1, wherein each of the first communication and the second communication includes one or more radio access technologies, the one or more radio access technologies including one or more of the following: next-generation radio, next-generation radio sidelink, LTE, LTE sidelink, 5G, new radio, or IEEE 802.11.

[0117] Clause 13: The method according to Clause 1, wherein the processing includes one of: sending the first communication, sending the second communication, receiving the first communication, or receiving the second communication.

[0118] Clause 14: The method described in Clause 1 further includes: Send the changed first priority or the changed second priority to another node.

[0119] Clause 15: The method according to Clause 14, wherein the other node includes any of the following: user equipment, evolved Node B, next-generation Node B, roadside unit, mobility management entity, or access and mobility management function.

[0120] Clause 16: The method described in Clause 1, wherein the change applies only to one or more of the initial priorities.

[0121] Clause 17: Nodes used to change communication priorities, said nodes including: Memory configured to store instructions; and A processor configured to execute the instructions stored in the memory to: Associate the first priority with the first communication; Associate the second priority with the second communication; change at least one of the first priority or the second priority based on one or more conditions; determine whether the first communication or the second communication has a higher priority after the change; and process at least one of the first communication or the second communication based on the determined higher priority.

[0122] Clause 18: The node of Clause 17, wherein the processor is further configured to: store the first priority and the second priority prior to the processing.

[0123] Clause 19: The node of Clause 17, wherein the processor is further configured to: receive the first priority and the second priority prior to the processing.

[0124] Clause 20: The node of Clause 19, wherein the processor is further configured to: receive the first priority and the second priority from another node.

[0125] Clause 21: The node of Clause 17, further comprising: a first radio access technology (RAT) module configured to receive the first priority; and a second radio access technology (RAT) module configured to receive the second priority.

[0126] Clause 22: The node of Clause 17, wherein the node comprises any of: a user equipment, an evolved NodeB, a next generation NodeB, a road side unit, a mobility management entity, or an access and mobility management function.

[0127] Clause 23: The node of Clause 17, wherein each of the first priority and the second priority comprises any of: a 5G quality of service identifier, a quality of service class indicator, a PC5 interface quality of service identifier, a per-packet priority for proximity-based services, a layer 1 / layer 2 priority, a quality of service priority, or an application priority.

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

[0129] Clause 25: The node of Clause 17, wherein the one or more conditions comprise at least one of: a cost of dropping the first communication or the second communication; whether the first communication or the second communication is a retransmission or a repetition; whether there will be a collision between the first communication and the second communication; a measurement, wherein the measurement comprises at least one of: a reference signal received power, a received signal strength indicator, a signal to interference noise ratio, or an energy measurement; a channel busy ratio; a packet delay budget; whether the first communication or the second communication includes a medium access control (MAC) control element (CE); whether the first communication or the second communication includes inter-user equipment coordination information; a broadcast type of the first communication or the second communication, wherein the broadcast type comprises one of: unicast, groupcast, or broadcast; whether the first communication or the second communication relates to a particular channel; or whether one or more of the first communication or the second communication relates to one or more particular radio access technologies (RATs).

[0130] Clause 26: The node of Clause 25, wherein the particular channel comprises one of: a physical sidelink shared channel, a physical sidelink control channel, or a physical sidelink feedback channel.

[0131] Clause 27: The node of Clause 17, wherein the processor is configured to perform the changing based on a transport block.

[0132] Clause 28: The node of Clause 17, wherein each of the first communication and the second communication comprises one or more radio access technologies comprising one or more of: a next generation radio, a next generation radio sidelink, a long term evolution, a long term evolution sidelink, 5G, new radio, or IEEE 802.11.

[0133] Clause 29: The node of Clause 17, wherein the processor is configured to process at least one of the first communication or the second communication by performing one of: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication.

[0134] Clause 30: The node of Clause 17, wherein the processor is further configured to: transmit the changed first priority or the changed second priority to another node.

[0135] Clause 31: The node of clause 30, wherein the other node comprises any of: a user equipment, an evolved NodeB, a next generation NodeB, a road side unit, a mobility management entity, or an access and mobility management function.

[0136] Clause 32: The node of clause 17, wherein the processor is configured to perform the change to only one or more of the initial priorities.

[0137] Clause 33: A non-transitory computer-readable medium storing instructions executable by one or more processors of a node to perform a method comprising: associating a first priority with a first communication; associating a second priority with a second communication; based on one or more conditions, changing at least one of the first priority or the second priority; determining whether the first communication or the second communication has a higher priority after the change; and processing at least one of the first communication or the second communication based on the determined higher priority.

Claims

1. A method for changing communication priority at a node, the method comprising: Associate the first priority with the first communication; Associate 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; Determine whether the first or second communication has a higher priority after the change; as well as At least one of the first or second communications is processed based on the determined higher priority.

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

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

4. The method according to claim 3, wherein, The first priority and the second priority are received by the node from another node.

5. The method according to claim 1, wherein, 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.

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

7. The method according to claim 1, wherein, Each of the first priority and the second priority includes any of the following: 5G Quality of Service Identifier, Quality of Service Category Indicator, PC5 Interface Quality of Service Identifier, proximity-based per-packet priority, Layer 1 / Layer 2 priority, Quality of Service priority, or application priority.

8. The method according to claim 1, wherein, The 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.

9. The method according to claim 1, wherein, The one or more conditions include at least one of the following: The cost of discarding the first or second communication; Whether the first or second communication is a retransmission or a duplicate; Will there be any conflict between the first communication and the second communication? The measurement includes at least one of the following: reference signal received power, received signal strength indicator, signal-to-interference-noise ratio, or energy measurement; Channel busy ratio; Package delay budget; Whether the first communication or the second communication includes a Media Access Control (MAC) element (CE); Whether the first or second communication includes coordination information between user equipment; The broadcast type of the first communication or the second communication, wherein the broadcast type includes one of unicast, multicast or broadcast; Does the first or second communication involve a specific channel; or Whether one or more of the first or second communication involves one or more specific radio access technologies (RATs).

10. The method according to claim 9, wherein, The specific channel includes one of the following: physical-side crosslink sharing channel, physical-side crosslink control channel, or physical-side crosslink feedback channel.

11. The method according to claim 1, wherein, The change occurs based on transport blocks.

12. The method according to claim 1, wherein, Each of the first communication and the second communication includes one or more radio access technologies (RATs), which include one or more of the following: next-generation radio, next-generation radio sidelink, LTE, LTE sidelink, 5G, new radio, or IEEE 802.

11.

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

14. The method according to claim 1, further comprising: Send the changed first priority or the changed second priority to another node.

15. The method according to claim 14, wherein, The other node includes any of the following: user equipment, evolved Node B, next-generation Node B, roadside unit, mobility management entity, or access and mobility management function.

16. The method according to claim 1, wherein, The change applies only to one or more of the initial priorities.

17. A node for changing communication priorities, the node comprising: Memory configured to store instructions; as well as A processor configured to execute the instructions stored in the memory to: Associate the first priority with the first communication; Associate 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; Determine whether the first or second communication has a higher priority after the change; as well as At least one of the first or second communications is processed based on the determined higher priority.

18. The node according to claim 17, wherein, The processor is also configured to: The first priority and the second priority are stored before the processing.

19. The node according to claim 17, wherein, The processor is also configured to: The first priority and the second priority are received before the processing.

20. The node according to claim 17, further comprising: A first radio access technology (RAT) module is configured to receive the first priority; as well as The second radio access technology (RAT) module is configured to receive the second priority.

Images