EP4691100A1

EP4691100A1 - Altering communication priority at a node in a communication network

Info

Publication number: EP4691100A1
Application number: EP24712602.2A
Authority: EP
Inventors: Thomas Jacobsen; Claude Arzelier; Torsten WILDSCHEK; Takayuki Shimizu; Kai-Erik Sunell; Renato BARBOSA ABREU
Original assignee: Toyota Motor Corp
Current assignee: Toyota Motor Corp
Priority date: 2023-04-05
Filing date: 2024-02-27
Publication date: 2026-02-11
Also published as: CN121014249A; WO2024209840A1

Abstract

Disclosed are methods, apparatuses, and systems for altering communication priority at a node. The method includes associating a first priority to a first communication; associating a second priority to a second communication; based on one or more conditions, altering 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 altering; and processing at least one of the first communication or the second communication based on the determined higher priority.

Description

ALTERING COMMUNICATION PRIORITY AT A NODE IN A COMMUNICATION NETWORK

CROSS-Reference to Related Application

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,” the entirety of which is incorporated by reference herein.

Field

Apparatuses and methods consistent with the present disclosure relate generally to communications, more specifically, to methods, systems, and devices for altering the communication priority of one or more communications at a node in a communication network.

Background

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 may happen under the coverage of a cellular network, out of coverage of the cellular network, or even in partial coverage of the cellular network where only one of the two UEs is under the network coverage. Direct device-to-device communication uses the PC5 interface.

Sidelink communication is used by vehicle-to-everything applications, also known as V2X. An SL device may use various radio access technologies (RATs) such as Long Term Evolution (LTE) SL, Next Radio (NR) SL, or both, for transmission and reception. When both LTE SL and NR SL modules coexist in the same device, this may raise implementation challenges. For example, if a close frequency spacing is used, using two radio frequency (RF) chains (e.g., separate hardware for transmission and reception on both frequencies) would result in extra 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 sidelink was introduced. If a sufficiently close frequency spacing between the two RATs is deployed, one implementation choice is that a single RF chain is implemented in the UE, with the assumption that the UE is not required to simultaneously transmit and receive on sidelink.

If a single RF chain is implemented in the UE, then it is possible that interference between the two RAT receptions may happen in the UE if the frequencies for the two RATs are close and if the configured or preconfigured time resource pools overlap for the two sidelink RATs. In addition, one RAT cannot be received/transmitted while the other RAT is doing the opposite due to a half-duplex constraint (e.g., the inability to transmit and receive in the same frequency at the same time). Further, simultaneous transmission on both RATs may not be possible due to the UE’s single power budget. These are the reasons why in Release 16, the in-device coexistence introduced the concept of inter-RAT priorities of transmissions and receptions for LTE SL and NR SL. This concept is applied for 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 transmissions and receptions of LTE SL and NR SL (PSFCH is specific to NR SL). For the case of transmit/transmit overlap, the RAT with higher priority is selected if both priorities are known. The same principle is applied for the case of transmit/receive overlap between the two RATs if both priorities are known. This requires subframe boundaries of the two channels/signals to be aligned. Other cases of receive/receive overlap, equal priorities, and unknown priorities are left to device implementation.

Summary

According to some embodiments of the present disclosure, there is provided a method for altering communication priority at a node. The method includes associating a first priority to a first communication; associating a second priority to a second communication; based on one or more conditions, altering 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 altering; and processing at least one of the first communication or the second communication based on the determined higher priority.

According to some embodiments of the present disclosure, there is provided a node. The node includes a memory storing an instruction; and a processor configured to execute the instruction stored in the memory to: associate a first priority to a first communication; associate a second priority to a second communication; based on one or more conditions, alter at least one of the first priority or the second priority; determine whether the first communication or the second communication has a higher priority after the altering; and process at least one of the first communication or the second communication based on the determined higher priority.

According to some embodiments of the present disclosure, there is provided a non-transitory computer-readable medium storing instructions that are executable by one or more processors of a node to perform a method. The method includes associating a first priority to a first communication; associating a second priority to a second communication; based on one or more conditions, altering 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 altering; and processing at least one of the first communication or the second communication based on the determined higher priority.

FIG. 1 is a schematic diagram illustrating device types for dynamic co-channel coexistence of a first sidelink communication and a second sidelink communication, consistent with some embodiments of the present disclosure. FIG. 2 is a schematic diagram illustrating information transfer in a node from an LTE sidelink module to an NR sidelink module, consistent with some embodiments of the present disclosure. FIG. 3 is a schematic diagram illustrating an enhanced in-device coexistence (eIDC) component using additional information and/or interfaces, consistent with some embodiments of the present disclosure. FIG. 4 is a flowchart of an exemplary method for altering communication priority at a node, consistent with some embodiments of the present disclosure. FIG. 5 is a flowchart of another exemplary method for altering communication priority at a node, consistent with some embodiments of the present disclosure. FIG. 6 is a flowchart of another exemplary method for altering communication priority at a node, consistent with some embodiments of the present disclosure. FIG. 7 is a block diagram of a node, consistent with some embodiments of the present disclosure.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise represented. The implementations set forth in the following description of exemplary embodiments do not represent all implementations consistent with the present disclosure. Instead, they are merely examples of systems, apparatuses, and methods consistent with aspects related to the present disclosure as recited in the appended claims.
Release 18 dynamic co-channel coexistence of LTE Sidelink and NR Sidelink
As part of the 3GPP work, one objective is the co-channel coexistence for LTE Sidelink and NR Sidelink. The following has been considered: studying and specifying, if necessary, mechanisms for co-channel coexistence for LTE sidelink and NR sidelink including performance, necessity, feasibility, and potential specification impact if any. It is also proposed to reuse the in-device coexistence framework defined in Release 16 as much as possible.
While semi-static Frequency Division Multiplexing (FDM) or Time Division Multiplexing (TDM) may in theory achieve coexistence, this may be inefficient as the time and frequency resources allocated may not change quickly enough and hence may be inefficient to take advantage of the changing situation (for example, when the proportion of LTE SL and NR SL devices are changed). In addition, for the cases where all LTE SL resources are allocated by regulations or by technical specifications, a semi-static time and frequency resource allocation may not be possible. This is a reason why a more flexible, dynamic resource allocation has been considered. This dynamic resource allocation uses time and frequency resource pools that can potentially be used by LTE SL and NR SL, with some additional rules used to avoid one RAT interfering with the other RAT.
Some embodiments of the present disclosure propose to enhance the Release 16 in-device coexistence (IDC) solution to fulfill the Release 18 dynamic LTE/NR sidelink co-channel coexistence.
Interface between LTE SL module and NR SL module
As part of the 3GPP discussions, a 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 can receive information from the LTE SL module. For studying the feasibility of dynamic resource sharing as a possible solution for co-channel coexistence, for device Type A, the NR SL module uses the sensing and resource reservation information shared by the LTE SL module.
FIG. 1 is a schematic diagram illustrating device types for dynamic co-channel coexistence of a first sidelink (SL) communication and a second SL communication, consistent with some embodiments of the present disclosure. Referring to FIG. 1, at least three types (Type A, Type B, and Type C) of devices are considered in this disclosure. A Type A device includes a module for the first SL communication and a module for the second SL communication. A Type B device only includes a module for the first SL communication. A Type C device only include a module for the second SL communication. For example, in an embodiment, a Type A device includes both LTE SL and NR SL modules; a Type B device only includes an NR SL module; and a Type C device only includes an LTE SL module.
In some embodiments of the present disclosure, with regards to the in-device coexistence (IDC) using priorities as described above, not all equal priority events have the same consequence when dropping one RAT’s transmission or reception. For example, dropping a single PSCCH/PSSCH retransmission may have little or no consequence. As another example, dropping an initial PSCCH/PSSCH transmission may cause a slight delay. As another example, dropping the NR SL’s PSFCH transmission/reception may significantly degrade the reliability of the NR SL communication.
The priority described in the present disclosure may be the 5QI priority (e.g., the 5G quality of service identifier), the 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.
Symmetrically, treating equal priorities similarly as is done with the current IDC may not always be efficient. For example, some equal priority events should not be treated similarly, such as blind retransmissions/repetitions, because their importance decreases per transmission (as they provide less new mutual information/energy). Therefore, some embodiments of the present disclosure improve the current 3GPP solutions by proposing a more efficient in-device coexistence scheme. Embodiments of the present disclosure allow, for example, an NR SL module to “force” an LTE SL module to not use particular resources.
In some embodiments of the present disclosure, a priority may be altered when a data, packet, signal, or message is sent and/or received, to use a different priority. It is noted that the terms “communication” or “event” may be used herein to include data, a packet, a signal, or a message. For example, if priority altering is performed by the NR SL module, the NR SL module may alter its priority to be lower or higher than the initial priority of the communication. For example, if the NR SL priority is altered to a higher priority than the LTE SL priority, this allows the LTE SL module to be “forced” not to use particular resources. This functionality may be referred to herein as enhanced IDC (eIDC) functionality.
FIG. 2 illustrates an exemplary system diagram of a node 200 with the Release 16 IDC, together with the Release 18 information transfer from the LTE SL module to the NR SL module, where the eIDC functionality described above resides in the NR SL module. 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).
The 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 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., the PC5 interface).
In the embodiment shown in FIG. 2, the NR SL module 206 may alter its NR priority and send the altered NR priority to the device RAT controller 202 via the IDC interface 212.
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 legacy Release 16 IDC interface.
In another exemplary embodiment, the eIDC component 208 may be located in the LTE SL module 204 (not shown in FIG. 2). In this embodiment, it is also possible to use the legacy Release 16 IDC interface.
It is noted that the eIDC component 208 will function in a similar manner regardless of the location of the eIDC component 208 in the node 200. It is also contemplated that, in some embodiments, altering the priority may be performed by the entity receiving the priority, rather than the entity sending the priority.
In another embodiment, the eIDC component 208 may estimate the cost of dropping a communication and use the estimated cost in the decision process. As an example, the cost of a drop of each entity (for example, each RAT, such as LTE SL and NR SL) may be compared and used in the decision process. Dropping a communication may be considered as part of increasing the priority or decreasing the priority. In some embodiments, whether the priority can be increased or decreased may depend on the RAT. For example, in some embodiments, it may not be possible to alter the LTE SL priority; in such circumstances, the communication would be dropped instead of having its priority altered.
As another example, a cost function may associate events with weights. Some examples of events may be a first retransmission, a second retransmission, a first repetition, a second repetition, an LTE event, an 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 may lead to a priority increase or decrease. In some embodiments, the weights may be applied in a case of equal original priority of the communications. In some embodiments, it may also be possible to combine different types of weights, for example LTE/NR (a first type of weight) and first repetition/not first repetition (a second type of weight). In this example, the combination of the different types of weights may be an addition, a weighted average, or other mathematical combination or comparison.
In another embodiment, in case of an upcoming collision between LTE SL and NR SL time and/or frequency resources, the eIDC component 208 may decide if it should increase the NR SL priority to avoid an NR drop or not. This may be combined with using a cost function, as described above.
In another embodiment, in case of an upcoming collision between LTE SL and NR SL time and/or frequency resources, the eIDC component 208 may decide if it should decrease the LTE SL priority to avoid an NR drop or not. This may be combined with using a cost function, as described above.
In another embodiment, in case of an upcoming collision between LTE SL and NR SL time and/or frequency resources, the eIDC component 208 may decide if it should increase the LTE SL priority to avoid an LTE drop or not. This may be combined with using a cost function, as described above.
In another embodiment, in case of an upcoming collision between LTE SL and NR SL time and/or frequency resources, the eIDC component 208 may decide if it should decrease the NR SL priority to avoid an LTE drop or not. This may be combined with using a cost function, as described above.
In another embodiment, the eIDC functionality may be performed by the module or entity sending the priority, such as the LTE SL module 204 in the example of FIG. 2 (if the LTE SL module 204 includes the eIDC component 208). The priority provided may therefore be increased or decreased, for example to avoid a collision with an NR SL resource or with another RAT or system.
In another embodiment, the eIDC functionality may be configured or preconfigured to always drop a transmission that overlaps one or more specific time and/or frequency resources. In another embodiment, the eIDC functionality may be configured to never drop a transmission that overlaps one or more specific time and/or frequency resources. For example, the eIDC functionality may be configured to always drop LTE transmissions that overlap particular NR slots. In another embodiment, the eIDC functionality may be configured to never drop LTE transmissions that overlap particular NR slots.
In another embodiment, some additional criteria may be used in the decision process, for example 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 measurement etc. One or multiple thresholds may be used for these criteria.
In another embodiment, the notion of availability or how busy/congested is one or two of the signals may be used. For example, determining congestion may use a channel busy ratio (CBR). In an embodiment, if the CBR determined by the NR SL module is lower than the CBR determined by the LTE SL module, then the NR SL priority may be increased. In other embodiments, if the CBR of a specific Radio Access Technology (RAT) is below a threshold or exceeds a threshold, then the associated priority may be increased or decreased. In other embodiments, if the CBR of a specific channel is below a threshold or exceeds a threshold, then the associated priority may be increased or decreased.
In another embodiment, a packet delay budget (PDB) may be used to determine whether to increase and/or decrease the priority. For example, if the remaining PDB (in time) for the NR SL transmission is low (e.g., based on a threshold time interval or number of symbols before the budget expires), then the NR SL priority may be increased.
In another embodiment, a priority increase and/or decrease may be considered in case the transmission carries a medium access control (MAC) control element (CE). For example, the NR SL transmission priority may be increased if it includes a SL channel state information (CSI) reporting MAC CE. In another embodiment, the priority may be increased and/or decreased for the NR SL transmission if it includes inter-UE coordination (IUC) information.
In another embodiment, a priority increase or decrease may be determined based on the cast type of the transmission. For example, a priority increase may be performed for the module if the transmission is of at least one of unicast, groupcast, and/or broadcast. In an embodiment, the cast type which should translate to a priority increase or decrease may be configured or preconfigured. In another exemplary embodiment, the NR SL transmission may be prioritized if it is a groupcast transmission for a group size higher than a configured threshold.
In another embodiment, the eIDC functionality may be LTE RAT and/or NR RAT configuration aware. In another embodiment, the eIDC functionality may use LTE SL sensing information and/or LTE SL resource pool (RP) configuration information or preconfiguration information. In another embodiment, the eIDC functionality may use NR SL sensing information and/or NR SL resource pool (RP) configuration information or preconfiguration information. In case the eIDC uses the Release 16 IDC interface, these last three embodiments above may give the example depicted in FIG. 3.
FIG. 3 is a schematic diagram illustrating an eIDC component 300 using additional information and/or interfaces, consistent with some embodiments of the present 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 an 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.
In another embodiment, the eIDC functionality may decide which priority to alter in case of equal priority events. As used herein, the term “equal priority events” indicates that the initial unaltered priority of each event is the same. In another embodiment, the eIDC functionality may decide which priority to overwrite in case of collision events. In another embodiment, the eIDC functionality may decide which priority to overwrite on a transport block basis (e.g., a data unit submitted by Layer 2). An example of a criterion used in the assessment may be whether or not the transmission or reception is a repetition. Another example of a criterion used in the assessment may be whether or not the transmission or reception is a blind retransmission.
Some example of criteria that may be used in the assessment may be whether or not the transmission and/or reception applies to a specific channel, for example physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and/or physical sidelink feedback channel (PSFCH). Some examples of criteria that may be used in the assessment may be whether or not the transmission and/or reception applies to a repetition or to a blind retransmission. Some examples of criteria that may be used in the assessment may be whether or not the transmission and/or reception is an initial transmission, is a PSCCH/PSSCH transmission that requires PSFCH hybrid automatic repeat request (HARQ) feedback, or is a broadcast, a groupcast, or a unicast transmission.
In another embodiment, whether a transmission and/or reception would overlap some configured or preconfigured resources or some protected resources may be considered. Protected resources may be, for example, a sub-set of resources that may be configured or preconfigured. This may be indicated, for example, via semi-persistent scheduling (SPS). In another embodiment, the protected resources may be considered protected only for some priorities, for example up to a certain priority. In an example, the criterion may be whether an LTE SL transmission overlaps protected and configured or preconfigured NR SL slots. In another embodiment, any of the exemplary schemes described in this disclosure may apply only for some priorities.
Exemplary methods for altering communication priority at a node
FIG. 4 is a flowchart of an exemplary method 400 for altering communication priority at a node, consistent with some embodiments of the present disclosure. The method 400 may be performed by a node in a communication system, for example, by a UE in a sidelink communication.
The method 400 includes a step 402 of associating a first priority to 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 indicated as part of the first communication. As another example, the first priority may be received at the node separately from the first communication or may be generated by the node separately from the first communication.
The method 400 includes a step 404 of associating a second priority to a second communication. The second priority may be associated with the second communication in a similar manner as the first priority is associated with the second communication.
The method 400 includes a step 406 of altering at least the first priority or the second priority, based on one or more conditions. Altering the first priority or the second priority may include any one or more of: increasing the first priority, decreasing the first priority, increasing the second priority, decreasing the second priority, or any combination of altering both priorities. How the priority is altered (i.e., increased or decreased) may be associated with the specific condition being considered when altering the priority. For example, if the condition is whether a transmission is an initial transmission, then the priority may be increased if the transmission is an initial transmission.
The method 400 includes a step 408 of determining which communication has a higher priority after the altering is completed (i.e., identifying the communication that has a priority higher than the priority of one of one or more other communications). After one or both of the priorities have been altered, one of the communications may have a higher priority than the other communication(s).
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 may transmit the higher priority communication first.
FIG. 5 is a flowchart of an exemplary method 500 for altering communication priority at a node, consistent with some embodiments of the present disclosure. The method 500 may be performed by a node in a communication system, for example, by a UE in a sidelink communication.
The method 500 includes a step 502 of associating a first priority to 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 indicated as part of the first communication. As another example, the first priority may be received at the node separately from the first communication or may be generated by the node separately from the first communication.
The method 500 includes a step 504 of associating a second priority to a second communication. The second priority may be associated with the second communication in a similar manner as the first priority is associated with the first communication.
The method 500 includes a step 506 of selecting an applicable condition to apply. In some embodiments, multiple conditions may apply to the first communication and the second communication at the same time. 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 transmission), the priority may be increased for the specific channel and may also be increased for being an initial transmission. In such an example, the priority for the first communication may be increased twice (in a “relative” solution) or the priority for the first communication may be increased once (in an “absolute” solution).
In some embodiments, each condition may have a ranking associated with the condition, which may be used to determine in which order the multiple conditions will be evaluated. In some embodiments, all of the applicable conditions will be evaluated and a condition to be evaluated may be selected at random. In some embodiments, more than one potential condition may apply to the first communication. In some embodiments, more than one potential condition may apply to the second communication.
The method 500 includes a step 508 of altering the priorities of the communications based on the applied condition. Altering the priorities may include any one or more of: increasing the first priority, decreasing the first priority, increasing the second priority, decreasing the second priority, or any combination of altering both priorities. Altering the priorities may apply in a relative way or in an absolute way, compared to the initial priorities. In the second case, as new priority is selected without arithmetic addition or subtraction compared to the initial priority. How the priority is altered (i.e., increased or decreased) may be associated with the specific condition being considered when altering the priority.
The method 500 includes a step 510 of determining whether to apply other conditions to the communications. As noted above, multiple conditions may apply to the first communication and the second communication. In some embodiments, more than one condition may be evaluated before making a final determination whether one communication has a higher priority than the other communication. If other conditions are to be applied to the communications (step 510, “yes” branch), then the method 500 returns to step 506 to select a next applicable condition to apply. If other conditions are not going to be applied to the communications (step 510, “no” branch), then the method 500 proceeds to step 512.
The method 500 includes the step 512 of determining which communication has a higher priority after the altering is completed. After one or both of the priorities have been altered, one of the communications may have a higher priority than the other communication(s).
The method 500 includes a step 514 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 may transmit the higher priority communication first.
FIG. 6 is a flowchart of an exemplary method 600 for altering communication priority at a node, consistent with some embodiments of the present disclosure. The method 600 may be performed by a node in a communication system, for example, by a UE in a sidelink communication. For the purposes of explanation, it is assumed that the method 600 is performed in a node that includes an LTE SL module and an NR SL module.
The method 600 includes a step 602 of obtaining sensing information from the NR SL module and the LTE SL module. For example, an eIDC component may reside in the NR SL module, the LTE SL module, or a RAT controller of the node, as described elsewhere in the present disclosure, and may receive the sensing information from the NR SL module and the LTE SL module.
The method 600 includes a step 604 of predicting whether there will be any in-device coexistence collisions. Based on the received sensing information, it may be possible to predict whether there will be any in-device coexistence collisions, for example, via a transmission by both the NR SL module and the LTE SL module.
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. This estimation may be based on information contained in the communication (e.g., a channel type associated with the communication or a transmission type associated with the communication).
The method 600 includes a step 608 of determining the costs of dropping the NR communication and the LTE communication. The costs associated with the NR communication and the LTE communication may include a numerical value associated with the communication and utilize weights as described elsewhere in the present disclosure.
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 may be represented as numerical values and the determination may include comparing the values to determine which numerical value is higher. It is noted that other representations of the priority and comparisons may be applied. If the LTE communication priority is higher than the NR communication priority (step 610, “yes” branch), then the method 600 continues with step 612. If the LTE communication priority is not higher than the NR communication priority (step 610, “no” branch), then the method 600 continues with step 616.
The method 600 includes the 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), then the method 600 continues with 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), then the method 600 continues with step 616.
The method 600 includes the step 614 of increasing the NR communication priority and signaling the increased priority using an IDC interface. For example, the increased priority may be signaled to a transceiver in the node to transmit or receive the NR communication. The increased priority may be used by a receiving node for potential transmission or reception.
The method 600 includes the step 616 of determining whether the LTE communication overlaps protected and configured or preconfigured NR slots. If the LTE communication overlaps protected and configured or preconfigured NR slots (step 616, “yes” branch), then the method 600 continues with the step 614. If the LTE communication does not overlap protected and configured or preconfigured NR slots (step 616, “no” branch), then the method 600 continues with step 618.
The method 600 includes the step 618 of not adjusting any communication priority. The priorities of the LTE communication and the NR communication may then be compared before a potential transmission or reception.
In some embodiments, altering the priority may be performed only at specific times and/or following specific criterion/criteria. For example, the device history may be used. For example, if one RAT has been disadvantaged compared to another RAT (i.e., one RAT has more transmissions or receptions than the other RAT), altering the priority may be performed to favor back the RAT that was disadvantaged. This may be based on channel busy ratio (CBR), and/or some measurements (e.g. RSRP, RSSI, SINR, energy measurement). The assessment may be performed on a previous time period basis. This may use thresholds in the decision process. For example, if the CBR of one RAT and/or measurement is higher than a specific threshold, then the priority may be altered to favor the disadvantaged RAT. Alternatively or additionally, if one RAT has been advantaged for more than a specific time duration, then the priority may be altered to favor the disadvantaged RAT. Alternatively or additionally, the condition for favoring the disadvantaged RAT may be to consider whether one or more conditions are lower than respective thresholds associated with those conditions.
Embodiments of the present disclosure may include Release 18 NR sidelink and LTE sidelink radios and software incorporated in, for example, a vehicle. Also, the embodiments described in the present disclosure may be used for future 3GPP sidelink technologies using similar sidelink mechanisms (e.g., between NR and 6G sidelink).
Any of the information, parameters, and/or thresholds described in this disclosure may be provided to the device via configuration or preconfiguration. This may use, for example, a transmission from the network (for example, using the Radio Resource Control (RRC) Protocol, for example as described in 3GPP TS 38.331), or may use configuration information via SIM/USIM, for example via SIM Toolkit.
Although exemplary embodiments of in-device coexistence (IDC) are described in the present disclosure, embodiments of the present disclosure are not restricted to the IDC. In one embodiment, a device may forward and alter the priority received from a device to another (third) device. In another embodiment, the device may alter the priority received from and/or sent to a network node (e.g., a 5G Node B (gNodeB)). In another embodiment, altering the priority sent and/or received may be performed by another entity than a device, for example it may be performed by 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)).
Node
FIG. 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. Node 700 may be mounted in a moving vehicle or in a fixed position. Node 700 may take any form, including but not limited to, a vehicle, a component mounted in a vehicle, a roadside unit, a laptop computer, a wireless terminal including a mobile phone, a wireless handheld device, or wireless personal device, or any other form. In the preceding description, any mention of a UE performing certain functionality may be replaced with a node performing the same functionality without changing the operation or functionality of any of the elements described herein.
Referring to FIG. 7, the node 700 may include antenna 702 that may be used for transmission or reception of electromagnetic signals to/from a base station or other UEs. The antenna 702 may include one or more antenna elements and may enable different input-output antenna configurations, for example, multiple input multiple output (MIMO) configuration, multiple input single output (MISO) configuration, and single input multiple output (SIMO) configuration. In some embodiments, the antenna 702 may include multiple (e.g., tens or hundreds) antenna elements and may enable multi-antenna functions such as beamforming. In some embodiments, the antenna 702 is a single antenna.
The node 700 may include a transceiver 704 that is coupled to the antenna 702. The transceiver 704 may be a wireless transceiver at the node 700 and may communicate bi-directionally with a base station or other UEs. For example, the transceiver 704 may receive/transmit wireless signals from/to a base station via downlink/uplink communication. The transceiver 704 may also receive/transmit wireless signals from/to another UE or RSU via sidelink communication. The transceiver 704 may 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.
The node 700 may include a memory 706. The memory 706 may be any type of computer-readable storage medium including volatile or non-volatile memory devices, or a combination thereof. The computer-readable storage medium includes, but is not limited to, non-transitory computer storage media. A non-transitory storage medium may be accessed by a general purpose or special purpose computer. Examples of non-transitory storage medium include, but are not limited to, a portable computer diskette, a hard disk, random access memory (RAM), read-only memory (ROM), an erasable programmable read-only memory (EPROM), electrically erasable programmable ROM (EEPROM), a digital versatile disk (DVD), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, etc. A non-transitory 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 special-purpose computer, or a general-purpose or special-purpose processor. In some examples, the software/program code may be transmitted from a remote source (e.g., a website, a server, etc.) using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are within the scope of the definition of medium. Combinations of the above examples are also within the scope of computer-readable medium.
The memory 706 may store information related to identities of node 700 and the signals and/or data received by antenna 702. The memory 706 may also store post-processing signals and/or data. The memory 706 may also store computer-readable program instructions, mathematical models, and algorithms that are used in signal processing in transceiver 704 and computations in processor 708. The memory 706 may further store computer-readable program instructions for execution by processor 708 to operate node 700 to perform various functions described in this disclosure. In some examples, the memory 706 may include a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some embodiments, the node 700 is a Type A UE and the memory 706 includes both LTE SL and NR SL modules. In some embodiments, the node 700 is a Type B UE and the memory 706 includes an NR SL module only. In some embodiments, the node 700 is a Type C UE and the memory 706 includes an LTE SL module only.
The computer-readable program instructions of the present 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 an object-oriented programming language, and conventional procedural programming languages. The computer-readable program instructions may execute entirely on a computing device as a stand-alone software package, or partly on a first computing device and partly on a second computing device remote from the first 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).
The node 700 may include a processor 708 that may include a hardware device with processing capabilities. The processor 708 may 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 the 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 may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The processor 708 may receive, from transceiver 704, downlink signals or sidelink signals and further process the signals. The processor 708 may also receive, from transceiver 704, data packets and further process the packets. In some embodiments, the processor 708 may be configured to operate a memory using a memory controller. In some embodiments, a memory controller may be integrated into the processor 708. The processor 708 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 706) to cause the node 700 to perform various functions.
The node 700 may include a global positioning system (GPS) 710. The GPS 710 may be used for enabling location-based services or other services based on a geographical position of the node 700 and/or synchronization among UEs. The GPS 710 may receive global navigation satellite systems (GNSS) signals from a single satellite or a plurality of satellite signals via the antenna 702 and provide a geographical position of the node 700 (e.g., coordinates of the node 700).
The node 700 may include an input/output (I/O) device 712 that may be used to communicate a result of signal processing and computation to a user or another device. The I/O device 712 may include a user interface including a display and an input device to transmit a user command to processor 708. The display may be configured to display a status of signal reception at the node 700, the data stored at memory 706, a status of signal processing, and a result of computation, etc. The display may include, but is not limited to, a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), a gas plasma display, a touch screen, or other image projection devices for displaying information to a user. The input device may be any type of computer hardware equipment used to receive data and control signals from a user. The input device may include, but is not limited to, a keyboard, a mouse, a scanner, a digital camera, a joystick, a trackball, cursor direction keys, a touchscreen monitor, or audio/video commanders, etc.
The node 700 may further include a machine interface 714, such as an electrical bus that connects the transceiver 704, the memory 706, the processor 708, the GPS 710, and the I/O device 712.
In some embodiments, the node 700 may be configured to or programmed for sidelink communications. The processor 708 may be configured to execute the instructions stored in the memory 706 to perform a background channel sensing. The processor 708 may be configured to execute the instructions to collect at least one of sidelink sensing information or resource reservation information of a first sidelink communication, and collect at least one of sidelink sensing information or resource reservation information of a second sidelink communication. The processor 708 may be configured to execute the instructions to determine one or more candidate resources based on at least one of: the sidelink sensing information of the first sidelink communication, the resource reservation information of the first sidelink communication, the sidelink sensing information of the second sidelink communication, or the resource reservation information of the second sidelink communication. The processor 708 may be configured to execute the instructions to select one or more resources among the one or more candidate resources, check resource availability for the at least one packet that arrives after the resource selection based on a reevaluation of the one or more selected resources or a preemption of the one or more selected resources, and determine whether a resource reselection is needed. If the processor 708 determines that the resource reselection is not needed, the processor 708 may be configured to execute the instructions to transmit, using the one or more selected resources, one or more packets. If the processor 708 determines that the resource reselection is needed, the processor 708 may be configured to iterate the method from the collecting at least one of the sidelink resource sensing information or the resource reservation information of the first sidelink communication.
In some embodiments, the node 700 may be configured to or programmed for sidelink communications. The processor 708 may be configured to execute the instructions stored in the memory 706 to perform a method for altering communication priority at a node, such as the method 400 described in connection with FIG. 4, the method 500 described in connection with FIG. 5, or the method 600 described in connection with FIG. 6.
In an embodiment where the node 700 is a Type A UE, the node 700 may 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, RAT 1 module 720 may be configured to implement a first RAT, for example, LTE. In some embodiments, RAT 2 module 722 may be configured to implement a second RAT, different from the first RAT, for example, NR. It is noted that the types of RATs implemented by the RAT modules 720, 722 are not limited to LTE and NR. The RAT modules 720, 722 may implement any type of RAT without changing the principles of operation of the embodiments described herein.
In an embodiment where the node 700 is a Type B UE or a Type C UE, the node 700 may include only one RAT module (e.g., RAT 1 module 720). RAT 1 module 720 may implement any type of RAT, e.g., LTE, NR, or other type of RAT. In Fig. 7, RAT 2 module 722 is shown in dashed outline to indicate that it may not be included in some embodiments.
Any of the embodiments described herein may be used simultaneously or in combination. The combination of various embodiments may be controlled by one or more parameters with the same embodiments as described herein with regards to providing those parameters to the UE. In another embodiment, any embodiment described herein may apply conditionally to the UE being in a sidelink co-existence setting.
Any embodiment described herein may apply conditionally to the UE operating in the same resource pool or carrier frequency as the one being detected.
Any of the embodiments described in this disclosure may apply to 3GPP sidelink. This may, for example, apply to Release 18 NR Sidelink and/or Release 18 LTE-NR Sidelink co-existence (for example, for sidelink in unlicensed access). However, the embodiments described in the present disclosure are not restricted to this technology and may apply to other wireless communication technologies, for example and not limited to, Digital Enhanced Cordless Telecommunications / Digital European Cordless Telecommunications (DECT) or IEEE 802.11, for example, Wi-Fi.
As used in this disclosure, use of the term “or” in a list of items indicates an inclusive list. The list of items may be prefaced by a phrase such as “at least one of” or “one or more of.” For example, a list of 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 and B and C). Also, as used in this disclosure, prefacing a list of conditions with the phrase “based on” shall not be construed as “based only on” the set of conditions and rather shall be construed as “based at least in part on” the set of conditions. For example, an outcome described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of this disclosure.
In this specification, the terms “comprise,” “include,” or “contain” may be used interchangeably and have the same meaning and are to be construed as inclusive and open-ended. The terms “comprise,” “include,” or “contain” may be used before a list of elements and indicate that at least all of the listed elements within the list exist but other elements that are not in the list may also be present. For example, if A comprises B and C, both {B, C} and {B, C, D} are within the scope of A.
The present disclosure, in connection with the accompanied drawings, describes example configurations that are not representative of all the examples that may be implemented or all configurations that are within the scope of this disclosure. The term “exemplary” should not be construed as “preferred” or “advantageous compared to other examples” but rather “an illustration, an instance or an example.” By reading this disclosure, including the description of the embodiments and the drawings, it will be appreciated by a person of ordinary skills in the art that the technology disclosed herein may be implemented using alternative embodiments. The person of ordinary skill in the art would appreciate that the embodiments, or certain features of the embodiments described herein, may be combined to arrive at yet other embodiments for practicing the technology described in the present disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
The flowcharts and block diagrams in the figures illustrate examples of the architecture, functionality, and operation of possible implementations of systems, methods, and devices according to various embodiments. It should be noted that, in some alternative implementations, the functions noted in blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Likewise, additional steps may be included in such methods, and certain steps may be omitted or combined, in methods consistent with various embodiments.
It is understood that the described embodiments are not mutually exclusive, and elements, components, materials, or steps described in connection with one example embodiment may be combined with, or eliminated from, other embodiments in suitable ways to accomplish desired design objectives.
Reference herein to “some embodiments” or “some exemplary embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment. The appearance of the phrases “one embodiment” “some embodiments” or “another embodiment” in various places in the present disclosure do not all necessarily refer to the same embodiment, nor are separate or alternative embodiments necessarily mutually exclusive of other embodiments.
Additionally, the articles “a” and “an” as used in the present 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.
Unless explicitly stated otherwise, each numerical value and range should be interpreted as being approximate as if the word “about” or “approximately” preceded the value of the value or range.
Although the elements in the following method claims, if any, are recited in a particular sequence, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those elements, those elements are not necessarily intended to be limited to being implemented in that particular sequence.
It is appreciated that certain features of the present disclosure, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the specification, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination or as suitable in any other described embodiment of the specification. Certain features described in the context of various embodiments are not essential features of those embodiments, unless noted as such.
It will be further understood that various modifications, alternatives, and variations in the details, materials, and arrangements of the parts which have been described and illustrated in order to explain the nature of described embodiments may be made by those skilled in the art without departing from the scope. Accordingly, the following claims embrace all such alternatives, modifications, and variations that fall within the terms of the claims.
Clause 1: A method for altering communication priority at a node, the method comprising:
associating a first priority to a first communication;
associating a second priority to a second communication;
based on one or more conditions, altering 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 altering; and
processing at least one of the first communication or the second communication based on the determined higher priority.
Clause 2: The method of clause 1, wherein the first priority and the second priority are stored by the node prior to the processing.
Clause 3: The method of clause 1, wherein the first priority and the second priority are received by the node prior to the processing.
Clause 4: The method of clause 3, wherein the first priority and the second priority are received by the node from an other node.
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.
Clause 6: The method of clause 1, wherein the node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
Clause 7: The method of clause 1, wherein each of the first priority and the second priority includes any one of: a 5G quality of service identifier, a quality of service class indicator, a PC5 interface quality of service identifier, a proximity based services per-packet priority, a layer 1/layer 2 priority, a quality of service priority, or an application priority.
Clause 8: The method of clause 1, wherein the altering includes at least one of increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority.
Clause 9: The method of clause 1, wherein the one or more conditions include 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 includes 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 cast type of the first communication or the second communication, wherein a cast type includes one of unicast, groupcast, or broadcast;
whether the first communication or the second communication relates to a specific channel; or
whether one or more of the first communication or the second communication relates to one or more of a specific Radio Access Technology (RAT).
Clause 10: The method of clause 9, wherein the specific channel includes one of: a physical sidelink shared channel, a physical sidelink control channel, or a physical sidelink feedback channel.
Clause 11: The method of clause 1, wherein the altering occurs on a transport block basis.
Clause 12: The method of clause 1, wherein each of the first communication and second communication includes one or more radio access technologies (RATs) including one or more of: a next generation radio, a next generation radio sidelink, a long term evolution, a long term evolution sidelink, a 5G, a New Radio, or an IEEE 802.11.
Clause 13: The method of clause 1, wherein the processing includes one of: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication.
Clause 14: The method of clause 1, further comprising:
sending the altered first priority or the altered second priority to an other node.
Clause 15: The method of clause 14, wherein the other node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
Clause 16: The method of clause 1, wherein the altering is applied only to one or more of initial priorities.
Clause 17: A node for altering communication priority, the node comprising:
a memory configured to store instructions; and
a processor configured to execute the instructions stored in the memory to:
associate a first priority to a first communication;
associate a second priority to a second communication;
based on one or more conditions, alter at least one of the first priority or the second priority;
determine whether the first communication or the second communication has a higher priority after the altering; and
process at least one of the first communication or the second communication based on the determined higher priority.
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.
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.
Clause 20: The node of clause 19, wherein the processor is further configured to:
receive the first priority and the second priority from an other node.
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.
Clause 22: The node of clause 17, wherein the node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
Clause 23: The node of clause 17, wherein each of the first priority and the second priority includes any one of: a 5G quality of service identifier, a quality of service class indicator, a PC5 interface quality of service identifier, a proximity based services per-packet priority, a layer 1/layer 2 priority, a quality of service priority, or an application priority.
Clause 24: The node of clause 17, wherein the processor is configured to alter 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.
Clause 25: The node of clause 17, wherein the one or more conditions include 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 includes 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 cast type of the first communication or the second communication, wherein a cast type includes one of unicast, groupcast, or broadcast;
whether the first communication or the second communication relates to a specific channel; or
whether one or more of the first communication or the second communication relates to one or more of a specific Radio Access Technology (RAT).
Clause 26: The node of clause 25, wherein the specific channel includes one of: a physical sidelink shared channel, a physical sidelink control channel, or a physical sidelink feedback channel.
Clause 27: The node of clause 17, wherein the processor is configured to perform the altering on a transport block basis.
Clause 28: The node of clause 17, wherein each of the first communication and second communication includes one or more radio access technologies (RATs) including one or more of: a next generation radio, a next generation radio sidelink, a long term evolution, a long term evolution sidelink, a 5G, a New Radio, or an IEEE 802.11.
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.
Clause 30: The node of clause 17, wherein the processor is further configured to:
send the altered first priority or the altered second priority to an other node.
Clause 31: The node of clause 30, wherein the other node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
Clause 32: The node of clause 17, wherein the processor is configured perform the altering only on one or more of initial priorities.
Clause 33: A non-transitory computer-readable medium storing instructions that are executable by one or more processors of a node to perform a method, the method comprising:
associating a first priority to a first communication;
associating a second priority to a second communication;
based on one or more conditions, altering 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 altering; and
processing at least one of the first communication or the second communication based on the determined higher priority.

Claims

A method for altering communication priority at a node, the method comprising:
associating a first priority to a first communication;
associating a second priority to a second communication;
based on one or more conditions, altering 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 altering; and
processing at least one of the first communication or the second communication based on the determined higher priority.
The method of claim 1, wherein the first priority and the second priority are stored by the node prior to the processing.
The method of claim 1, wherein the first priority and the second priority are received by the node prior to the processing.
The method of claim 3, wherein the first priority and the second priority are received by the node from an other node.
The method of 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.
The method of claim 1, wherein the node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
The method of claim 1, wherein each of the first priority and the second priority includes any one of: a 5G quality of service identifier, a quality of service class indicator, a PC5 interface quality of service identifier, a proximity based services per-packet priority, a layer 1/layer 2 priority, a quality of service priority, or an application priority.
The method of claim 1, wherein the altering includes at least one of increasing the first priority, decreasing the first priority, increasing the second priority, or decreasing the second priority.
The method of claim 1, wherein the one or more conditions include 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 includes 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 cast type of the first communication or the second communication, wherein a cast type includes one of unicast, groupcast, or broadcast;
whether the first communication or the second communication relates to a specific channel; or
whether one or more of the first communication or the second communication relates to one or more of a specific Radio Access Technology (RAT).
The method of claim 9, wherein the specific channel includes one of: a physical sidelink shared channel, a physical sidelink control channel, or a physical sidelink feedback channel.
The method of claim 1, wherein the altering occurs on a transport block basis.
The method of claim 1, wherein each of the first communication and second communication includes one or more radio access technologies (RATs) including one or more of: a next generation radio, a next generation radio sidelink, a long term evolution, a long term evolution sidelink, a 5G, a New Radio, or an IEEE 802.11.
The method of claim 1, wherein the processing includes one of: transmitting the first communication, transmitting the second communication, receiving the first communication, or receiving the second communication.
The method of claim 1, further comprising:
sending the altered first priority or the altered second priority to an other node.
The method of claim 14, wherein the other node includes any one of: a user equipment, an evolved Node B, a next generation Node B, a roadside unit, a mobility management entity, or an access and mobility management function.
The method of claim 1, wherein the altering is applied only to one or more of initial priorities.
A node for altering communication priority, the node comprising:
a memory configured to store instructions; and
a processor configured to execute the instructions stored in the memory to:
associate a first priority to a first communication;
associate a second priority to a second communication;
based on one or more conditions, alter at least one of the first priority or the second priority;
determine whether the first communication or the second communication has a higher priority after the altering; and
process at least one of the first communication or the second communication based on the determined higher priority.
The node of claim 17, wherein the processor is further configured to:
store the first priority and the second priority prior to the processing.
The node of claim 17, wherein the processor is further configured to:
receive the first priority and the second priority prior to the processing.
The node of claim 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.