Prioritizing uplink and sidelink transmissions

Abstract

To provide a method, a device, and a storage medium for prioritizing vehicle-to-everything (V2X) between a side-link (SL) transmission (Tx) and an uplink (UL) transmission (Tx) in a wireless communication system.SOLUTION: A method is for determining the priority of simultaneous SL transmission and UL transmission of UE in a 5G New Radio (NR) network. The method processes SL control information (SCI) corresponding to at least one of an SL hybrid automatic repeat request (HARQ) or SL schedule request (SR) transmitted by the UE, thereby determining at least one priority value associated with the SL HARQ or SL SR. The method processes the SCI of the SL transmission sent simultaneously by the UE with the UL transmission, thereby determines a priority value associated with the SL transmission, compares the at least one priority value of the SL HARQ or SL SR with the priority value of the SL transmission, and prioritizes the transmissions based on the comparison of the priority values.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] This application generally relates to wireless communication systems, and more specifically, to vehicle-to-everything (V2X) prioritization between sidelink (SL) transmission (Tx) and uplink (UL) transmission (Tx).

Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Examples of wireless communication system standards and protocols include the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly known to industry groups as Worldwide Interoperability for Microwave Access (WiMAX), and the IEEE 802.11 standard for Wireless Local Area Networks (WLAN), commonly known to industry groups as Wi-Fi. In a 3GPP radio access network (RAN) of an LTE system, base stations may include RAN nodes such as Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly called Evolved Node B, Extended Node B, eNodeB, or eNB) and / or E-UTRAN Radio Network Controller (RNC) that communicate with radio communication devices known as user equipment (UE). In fifth-generation (5G) radio RAN, RAN nodes may include 5G nodes, NR nodes, or gNode B (gNB).

[0003] A RAN communicates between RAN nodes and UEs using radio access technology (RAT). Examples of RANs include the Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, all of which provide access to communication services via the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, and E-UTRAN implements the LTE RAT.

[0004] To facilitate the identification of any particular element or action, the most significant digit(s) of the reference number refers to the number of the figure in which that element was first introduced. [Brief explanation of the drawing]

[0005] [Figure 1] This document shows an LTE V2X prioritization scheme at the physical layer according to one embodiment. [Figure 2] This document presents an NR V2X prioritization scheme between SL data and UL data according to one embodiment. [Figure 3] This describes a procedure for prioritizing side links and uplinks according to one embodiment. [Figure 4] A method according to one embodiment is shown. [Figure 5] A method according to one embodiment is shown. [Figure 6] A method according to one embodiment is shown. [Figure 7] This document illustrates an exemplary service-based architecture in a specific embodiment. [Figure 8] This shows a UE according to one embodiment. [Figure 9] A network node according to one embodiment is shown. [Modes for carrying out the invention]

[0006] User equipment (UE) can support both sidelink (SL) and uplink (UL) transmissions. SL transmissions may be on the same or different carriers as UL transmissions. Sometimes, time overlap may occur between SL and UL transmissions. Due to any given UE total transmit power limits, the UE may not be able to provide the transmit power necessary for both its SL and UL transmissions.

[0007] Therefore, power reduction schemes for different carriers and transmit drop schemes for the same carrier may be beneficial. Power reduction or transmit drop may be applied to lower-priority transmits (e.g., SL or UL). Therefore, prioritization between SL and UL is necessary. Figure 1 shows a visual representation of the LTE V2X prioritization scheme 100, which represents the prioritization of sidelink (SL) transmits over uplink (UL) transmits. As partially shown by blocks 102 and 104 and the SL priority threshold 106, if the SL control information (SCI) priority value is higher than the corresponding SL priority threshold, simultaneous UL transmits will be preferred (i.e., lower priority values ​​indicate higher priority), as will be further explained herein. Therefore, if the SCI priority value is lower than the corresponding SL priority threshold, SL transmits will be preferred over simultaneous UL transmits, as will be further explained herein.

[0008] More specifically, in the LTE V2X physical layer, if SL transmission and UL transmission are on the same carrier, and the value of the "priority" field of the SCI corresponding to the SL transmission is smaller than the higher-layer parameter "thresSL-TxPrioritization", the UL transmission is dropped. Otherwise, the SL transmission is dropped. In particular, the lower the value of the SCI's "priority" field, the higher the priority of the corresponding SL data, and conversely, the higher the value of the SCI's "priority" field, the lower the priority of the corresponding SL data.

[0009] In the LTE V2X physical layer, if SL transmission and UL transmission are on different carriers, and the value of the "priority" field of the SCI corresponding to SL transmission is smaller than the higher-layer parameter "thresSL-TxPrioritization", then the UL transmission power is less than the total UE transmission power. CMAX It is adjusted so as not to exceed P. Otherwise, the SL transmit power will be adjusted so that the total UE transmit power does not exceed P. CMAX It will be adjusted so as not to exceed that limit.

[0010] In the LTE V2X physical layer, SL and UL prioritization is based on SL data priority in the SCI. Therefore, UL data priority is not considered when determining such priority (UL data priority is not available in the physical layer).

[0011] In particular, according to the New Radio (NR) V2X Release 16 agreement, in the power-limited case when supporting simultaneous SL and UL transmission when the SL carrier is different from the UL carrier, if SL transmission takes precedence over UL transmission, the UE shall have its total transmit power limited in any overlapping portion. CMAX The UL transmit power can be adjusted before the start of transmission so as not to exceed P. In this case, the calculation of the adjustment for the UL transmit power is not specified. If UL transmission is preferred over SL transmission in such a case, the UE shall control its total transmit power in any overlapping portion P CMAXThe SL transmission power can be adjusted before transmission begins to ensure it does not exceed a certain limit. In this case, the calculation of the adjustment to the SL transmission power is not specified.

[0012] In addition, in the case of simultaneous SL and UL transmission, the total SL transmission power is the same for the symbols used for actual PSCCH / PSSCH transmission in the slot. PSSCH / PSSCH transmission may be dropped in some symbols if there is an uplink transmission with a higher priority, and the UE cannot maintain the same SL transmission power in symbols. The selection of symbols to be dropped depends on the UE implementation, which may include symbols that are being dropped and may overlap.

[0013] If simultaneous transmission of SL and UL exceeds the UE's capacity, one of the less prioritized transmissions may be dropped. Whether and how RF transients are addressed is up to RAN4. In particular, which transmissions to prioritize and when, how to address UE processing time, and whether there are cases where some symbols of uplink transmissions are dropped are issues that may be further investigated.

[0014] Figure 2 shows a visual representation of the NR V2X prioritization scheme 200, which represents the prioritization of SL transmissions over UL transmissions at the MAC layer, as described in the NR V2X RAN2 agreement. As partially shown by blocks 202-206 and priority thresholds 208 and 210, the prioritization of SL and UL is based on the logical channel priority of both SL data and UL data / SR. In particular, between SL-data and UL-data / SRB (Signaling Radio Bearer), SL transmissions are preferred if the highest priority value of the UL LCH(s) with available data is higher than the UL priority threshold, and the highest priority value of the SL LCH(s) with available data is lower than the SL priority threshold. Otherwise, UL transmissions are preferred. Therefore, the lower the logical channel priority value, the higher the priority of the data, and conversely, the higher the logical channel priority value, the lower the priority of the data.

[0015] The following prioritization rules also apply: Between SL-data and UL-SR, UL-SR priority is based on the UL LCH that triggered the UL SR; between SL-data and SL-SR (on the uplink channel), priority is based on a direct comparison between the relevant LCH priorities; between SL-data and UL-TX on a PUSCH for MAC CE, the LTE solution is reused, and Msg1 / 3 for RACH procedures and PUSCH for emergency PDU connections always take precedence over SL transmission.

[0016] In particular, NR V2X Release 16 has the following agreement in RAN1: there is no support for multiplexing of SL Hybrid Automatic Repeat (HARQ) and Radio Interface (Uu) UL Control Information (UCI) on PUCCH or PUSCH (it is open what the UE should do if the SL HARQ report to the gNB has a time overlap with the Uu UCI), and if the report on PUCCH overlaps with the PUSCH transmission, the SL HARQ-ACK is reported on PUSCH (the Release 15 procedure and signaling for multiplexing the DLHARQ-ACK on PUSCH are reused).

[0017] The principles described herein provide solutions to several problems, including: 1. How to determine priority between SL transmissions and UL transmissions, including specific priority levels for specific SL transmissions; whether UL-SL prioritization performed in NR V2X RAN2 can be reused for uplink transmissions with available priority information; or whether LTE V2X prioritization can be reused between SL transmissions and UL transmissions (in particular, NR V2X RAN2 considers data logical channel priority, NR V2X RAN2 does not consider physical layer priority information, and NR V2X RAN2 does not consider UL transmissions including SL HARQ or SL SR); 2. How to prioritize uplink transmissions including SL HARQ and Uu UCI (in particular, if UL transmissions for SL HARQ reporting to gNBs have a time overlap with Uu UCIs, multiplexing is not supported and drops depend on the prioritization between UL transmissions for SL HARQ and Uu UCIs, so one of them must be dropped); 3. How to multiplex SL HARQ reporting to gNBs with UL data (in particular, SL to gNBs) Since HARQ reports can be sent on PUSCH along with UL data transmissions, whether this should apply to all UL data is also answered by the principles described herein, 4. How to prioritize SL authorizations in Mode 1 from gNB. In particular, in Mode 1 resource allocation, SL authorizations can be dynamic authorizations, and Type 1 and Type 2 configuration authorizations, as well as multiple Type 1 or Type 2 configuration authorizations, are supported.

[0018] Regarding the first issue, the following procedure explains the prioritization between SL transmissions and UL transmissions: 1. If the uplink transmission is a PRACH or PUSCH scheduled by RAR UL authorization, the UL transmission takes precedence. 2. If the uplink transmission includes URLLC traffic, the UL transmission takes precedence (the "priority indicator" field (format 1_1, 1_2, 0_1, 0_2) of the scheduling / authorization DCI is equal to 1 or equal to the uplink configuration authorization setting, and the corresponding DL HARQ feedback, CSI, or SRS, uplink data is considered URLLC traffic, and the UL transmission may or may not include SL HARQ or SL SR). 3. If the uplink transmission includes SL HARQ or SL SR, and the "priority" value of the SL HARQ / SR is lower than the "priority" level in the SCI of the SL transmission, the UL transmission takes precedence (the "priority" value of the SL HARQ is equal to the "priority" field in the corresponding SCI, and the SL 1. The "priority" value of an SR is equal to the logical channel priority of the corresponding SL data, and UL transmissions can be either PUCCH or PUSCH, and UL data can be carried by PUSCH (this is a direct comparison between SL priorities without using UL data priority), 4. If PUCCH contains an SL HARQ or SL SR, and the "priority" value of the SL HARQ or SL SR is higher than the "priority" level in the SCI of the SL transmission, the SL transmission takes precedence (Release 16 V2X does not support multiplexing of SL HARQ and Uu UCI over PUCCH / PUSCH, so the priority of the SL HARQ / SR can simply be compared to the priority of the SL transmission, this is a direct comparison between SL priorities without using UL data / Uu UCI priority), 5. If PUSCH contains only an SL HARQ or SL SR and does not contain UL data, and SL HARQ or SL If the SR's "priority" value is higher than the SL transmission's "priority" level in the SCI, the SL transmission takes precedence (this is a direct comparison between SL priorities without using UL data priority), 6.If the value of the "Priority" field in the SCI of an SL transmission is less than the higher-layer parameter "thresSL-TxPrioritization", the SL transmission takes precedence; otherwise, the UL transmission takes precedence (this step applies when a PUSCH includes both a sidelink HARQ or sidelink SR and uplink data, and the "Priority" value of the sidelink HARQ or sidelink SR is higher than the "Priority" level in the SCI of the sidelink transmission; this step applies when a PUCCH or PUSCH includes an eMBB Uu UCI and / or eMBB uplink data; however, it does not apply to any URLLC traffic where the UL transmission has already taken precedence). In particular, in the above procedure, the priority value for SL PSFCH transmissions is indicated by the corresponding SCI, and the priority value for SSB transmissions is configured. If multiple SL transmissions are considered, the highest priority among them (i.e., the lowest priority value of the SCI) is used. When multiple SL HARQ or SL SR signals are considered in an uplink transmission, the highest priority among them (i.e., the lowest priority value of the SCI) is used. The above steps may be in sequential order.

[0019] Figure 3 shows a visual representation of procedure 300, which is described more fully above. Specifically, blocks 302-306 show scenarios where UL is preferred, blocks 308 and 310 show scenarios where SL is preferred, and block 312 shows other scenarios where prioritization depends on SL transmission priority.

[0020] Figure 4 shows a flowchart of a method 400 for determining the priority of simultaneous SL transmission and UL transmission of a UE in a 5G New Radio (NR) network. In block 402, method 400 processes SL control information (SCI) corresponding to at least one of the SL hybrid automatic repeat request (HARQ) or SL schedule request (SR) included in the UL transmission transmitted by the UE, thereby determining a priority value associated with the at least one SL HARQ or SL SR, where the UL transmission does not include a physical random access channel (PRACH), a physical uplink control channel (PUSCH) scheduled by a random access response (RAR) UL grant, or ultra-reliable low-latency communication (URLLC) traffic. In particular, the SL HARQ report in the UL transmission can be an ACK / NACK of the SL transmission. Additionally, the SCI can be transmitted in the SL transmission from the Tx UE to the Re UE rather than being included in the SL HARQ report (in particular, the SCI includes a "priority value" field). In block 404, method 400 processes the SCI of the SL transmission transmitted simultaneously with the UL transmission by the UE, thereby determining a priority value associated with the SL transmission. In block 406, method 400 compares the priority value of the at least one SL HARQ or SL SR with the priority value of the SL transmission. In block 408, method 400 prioritizes the transmissions based on the comparison of the priority values.

[0021] Regarding the second issue, the following procedure describes prioritizing UL submissions by SL HARQ reporting and Uu UCI as a solution to problems that may arise due to time overlap between SL HARQ reporting (i.e., to gNB) and Uu UCI (i.e., ULTx) in the Uu control domain. 1. If a UL transmission is a Uu URLLC UCI transmission on PUCCH / PUSCH (including URLLC downlink HARQ-ACK, CSI report, or Schedule Request (SR)) indicated by DCI format 0_1, 0_2, 1_1, 1_2 with the “Priority Indicator” field equal to 1, the UL transmission (i.e., Uu URLLC UCI) takes precedence and the SL HARQ report is dropped (i.e., Uu URLLC UCI transmissions always take precedence over sidelink HARQ reports). 2. If a UL transmission is an eMBB UCI transmission on PUCCH / PUSCH indicated by a “priorityIndicator-ForDCIformat” not configured by DCI format 0_1, 0_2, 1_1, 1_2 with the “Priority Indicator” field equal to 0, or by DCI format 0_0, 1_0 or periodic / semi-persistent CSI report, prioritization depends on the priority of the SL HARQ report. In particular, if the "priority" value in the SCI corresponding to the SL HARQ report is lower than the threshold (SL-priorityThreshold), the UL transmission (i.e., eMBB UCI) is dropped and the SL HARQ report takes precedence (in particular, the "priority" value in the SCI can be equal to the LCP (Logical Channel Priority) value of the SL data). Conversely, if the "priority" value in the SCI corresponding to the SL HARQ report is higher than the threshold (SL-priorityThreshold), the SL HARQ report is dropped and the UL transmission (i.e., eMBB UCI) takes precedence, and 3. if multiple SL HARQ reports are considered, the lowest "priority" value among all SCIs corresponding to the SL HARQ reports is used.Therefore, the prioritization of SL HARQ reports (i.e., to the gNB) and UL transmissions in Uu UCI (i.e., UL Tx) can consider both the Uu UCI priority (i.e., URLLC UCI or eMBB UCI) and the sidelink HARQ report priority (as indicated in the corresponding SCI), and can drop one of the Uu UCI and the sidelink HARQ report.

[0022] Figure 5 shows a flowchart of a method 500 for determining priorities in simultaneous transmissions of user equipment (UE) within a 5G New Radio (NR) network. At block 502, the method 500 identifies wireless interface (Uu) uplink (UL) control information (UCI) transmissions and sidelink (SL) hybrid automatic repeat request (HARQ) reports transmitted by the UE. At block 504, the method 500 determines a priority value for the Uu UCI transmission. At block 506, the method 500 determines the type of transmission associated with the Uu UCI transmission based at least in part on the determined priority value. At block 508, the method 500 prioritizes the transmissions of the UE based on the determined type of transmission associated with the UL transmission.

[0023] Alternatively, the following procedure may be used to resolve the second issue in MAC (i.e., the time overlap between SL HARQ reporting and Uu UCI solutions): 1. The state indicated by DCI formats 0_1, 0_2, 1_1, 1_2 where the “Priority Indicator” field is equal to 1 can be checked, which is applicable only to UL URLLC UCI. 2.3 The GPP RRC specification agrees to introduce thresholds for UL traffic as part of the MAC layer configuration (i.e., “ul-PrioritizationThres-r16”), so the UE can identify the logical channel to trigger for UL Tx and determine whether the LCH priority of this traffic is lower than the ul-PrioritizationThres threshold. If the LCH priority of this traffic is lower than the threshold, the UE will prioritize sending UCI for this LCH in PUCCH / PUSCH. Conversely, if the LCH priority of this traffic is lower than the threshold, the UE can begin using the previous solution for the second problem, starting with number 2, which is associated with determining that the UL transmission is an eMBB UCI transmission over PUCCH / PUSCH.

[0024] Regarding the third issue, the following procedure describes the prioritization associated with multiplexed SL HARQ reporting with uplink data on PUSCH in the Uu data domain as a solution to problems that may arise due to time overlap between SL HARQ reporting to gNB and UL data transmission. 1. If the “priority indicator” field is equal to 1, as indicated by DCI format 0_1, 0_2, or uplink configuration permission, and URLLC uplink data transmission is on PUSCH, URLLC uplink data transmission always takes precedence over SL HARQ reporting. In such cases, there is no transmission of SL HARQ reporting (i.e., only URLLC uplink data transmission). 2. If the “priority indicator” field is equal to 0, as indicated by DCI format 0_1, 0_2, or uplink configuration permission, as indicated by an unconfigured “priorityIndicator-ForDCIformat”, or as DCI format 0_0, and eMBB uplink data transmission is on PUSCH, several options exist as follows: Option 1: Based on UL data priority and SL HARQ report priority, drop or delay eMBB UL data transmission or SL HARQ report, Option 1a: If the LCP value of the eMBB UL data is lower than the threshold (UL-priorityThreshold), drop or delay the SL HARQ report. Otherwise, if the LCP value of the SL data corresponding to the SL HARQ report is lower than the threshold (SL-priorityThreshold), drop or delay the eMBB UL data. If the eMBB UL data is lower than the threshold (UL-priorityThreshold), or if the LCP value of the SL data corresponding to the SL HARQ report is not lower than the threshold (SL-priorityThreshold), drop or delay the SL HARQ report, Option 1b (i.e., used instead of Option 1a): If the LCP value of the eMBB UL data is lower than the LCP value of the SL data corresponding to the SL HARQ report, drop or delay the SL HARQ report.Conversely, if the LCP value of the eMBB UL data is lower than the LCP value of the SL data corresponding to the SL HARQ report, the eMBB UL data is dropped or delayed, and option 2 (i.e., instead of option 1): the SLHARQ report is piggybacked to PUSCH in the UL transmission.

[0025] Figure 6 shows a flowchart of method 600 for determining priority in simultaneous transmissions of user equipment (UEs) on a physical uplink control channel (PUSCH) within a 5G new radio (NR) network. In block 602, method 600 identifies uplink (UL) data transmissions and sidelink (SL) hybrid automatic repeat request (HARQ) reports that are multiplexed. In block 604, method 600 determines the priority value of the UL data transmission. In block 606, method 600 determines the type of transmission associated with the UL data transmission, at least in part, based on the determined UL data priority value. In block 608, method 600 prioritizes the UE transmissions based on the determined type of transmission associated with the UL data transmission.

[0026] Alternatively, other options may be used when resolving the third issue (i.e., determining the multiplexing order of UL authorizations). Typically, UL authorizations are multiplexed according to the MAC procedure described in TS 38.321 Clause 5.4.3.1.3. In addition, while noting that URLLC traffic may not be multiplexed with SL HARQ, there may be unique problems in determining how to compare SL HARQ reports with common UL logical channels and other MAC CEs in this LCP process. In this case, the following options can be considered: Option 1: Address SL HARQ before any UL LCH. With respect to its relationship with other MAC CEs, it may be multiplexed after UL BSR (non-padding) or SL BSR (non-padding), or the same rules defined for SL BSR cases of RAN2 to be determined may be followed. Option 2: If some UL LCHs with a priority lower than ul-PrioritizationThres are multiplexed before SL HARQ, and the highest priority SL LCH included in the SL MAC PDU that triggers SL HARQ is lower than sl-PrioritizationThres, then SL HARQ is multiplexed first for the other UL LCHs. Otherwise, those UL data are multiplexed before SL HARQ.

[0027] Regarding the fourth issue, the following procedure describes the prioritization of SL authorizations in Mode 1 (in particular, in NR Uu links, where dynamic authorization pushes generally take precedence over configuration authorization pushes, and where time overlaps between dynamic authorization pushes and configuration authorization pushes can occur). 1. When SL configuration authorizations have a time overlap with SL dynamic authorizations, there are two alternative options: Option 1a: SL dynamic authorizations take precedence over SL configuration authorizations, or Option 1b: SL authorizations with lower Logical Channel Priority (LCP) values ​​take precedence. Exemplary system architecture

[0028] In certain embodiments, the 5G system architecture supports data connectivity and services that can be deployed using technologies such as network function virtualization and software-defined networking. The 5G system architecture can leverage service-based bidirectional interaction between control plane network functions. Separating user plane functions from control plane functions enables independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) deployment). Modular functional design enables function reuse and flexible and efficient network slicing. Network functions and their network function services can interact directly or indirectly bidirectionally with other NFs and their network function services via service communication proxies. Another intermediate function can assist in routing control plane messages. The architecture minimizes dependencies between ANs and CNs. The architecture can include a converged core network with a common AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture also supports a unified authentication framework, a stateless NF where computing resources are separated from storage resources, feature exposure, simultaneous access to local and centralized services (user plane functions may be deployed close to the AN to support low-latency services and access to the local data network), and / or roaming for both home routing traffic and local breakout traffic within visited PLMNs.

[0029] A 5G architecture can be defined as service-based, and bidirectional interaction between network functions can include a service-based representation, where a network function in the control plane (e.g., AMF) enables other authorized network functions to access those services. A service-based representation can also include a point-to-point reference point. A reference point representation can also be used to show bidirectional interaction between NF services in a network function, described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0030] Figure 7 shows a service-based architecture 700 in 5GS according to one embodiment. As described in 3GPP TS 23.501, the service-based architecture 700 includes NFs such as NSSF702, NEF704, NRF706, PCF708, UDM710, AUSF712, AMF714, and SMF716 for communicating with UE720, (R)AN722, UPF724, and DN726. NFs and NF services can communicate directly, which is called direct communication, or indirectly via SCP718, which is called indirect communication. Figure 7 also shows the corresponding service-based interfaces, including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf, and Nausf, as well as reference points N1, N2, N3, N4, and N6. Some exemplary functions provided by the NFs shown in Figure 7 are described below.

[0031] NSSF702 supports functions such as selecting a set of network slice instances to serve the UE, determining authorized NSSAIs and mapping them to subscribed S-NSSAIs as needed, determining configured NSSAIs and mapping them to subscribed S-NSSAIs as needed, and / or determining a list of candidate AMFs (one or more) to use to serve the UE, or, based on the configuration, potentially querying the NRF.

[0032] The NEF704 supports the exposure of functions and events. NF functions and events can be securely exposed by the NEF704 (e.g., for third parties, application functions, and / or edge computing). The NEF704 can store / retrieve information as structured data using a standardized interface to UDR (Nudr). The NEF704 can also protect the provision of information from external applications to the 3GPP network and provide application functions for securely providing information to the 3GPP network (e.g., expected UE behavior, 5GLAN group information, and service-specific information), where the NEF704 can authenticate, authorize, and assist in the coordination of application functions. The NEF704 can provide internal-external information conversion by converting between information exchanged with the AF and information exchanged with internal network functions. For example, the NEF704 converts between AF service identifiers and internal 5G core information such as DNN and S-NSSAI. The NEF704 can handle the masking of network and user sensitive information to external AFs according to network policies. The NEF704 can receive information from other network functions (based on the exposed functions of those other network functions) and store the received information in the UDR using a standardized interface. The stored information can then be accessed by the NEF704, republished to other network and application functions, and used for other purposes such as analysis. For the external exposure of services associated with a specific UE(s), the NEF704 may reside within the HPLMN. With the operator's consent, the NEF704 within the HPLMN may have interfaces with NF(s) within the VPLMN. If the UE can switch between EPC and 5GC, SCEF+NEF can be used for service exposure.

[0033] NRF706 supports service discovery by receiving NF discovery requests from NF instances or SCPs and providing information on discovered NF instances to the NF instances or SCPs. NRF706 also supports P-CSCF discovery (a special case of AF discovery by SMF), maintains NF profiles of available NF instances and their supported services, and / or can notify subscriber NF service consumers or SCPs of newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, depending on the network implementation, multiple NRFs may be deployed at various levels, such as the PLMN level (NRFs consist of information about the entire PLMN), the shared slice level (NRFs consist of information belonging to a set of network slices), and / or the slice-specific level (NRFs consist of information belonging to S-NSSAI). In the context of roaming, multiple NRFs can be deployed in different networks, where the NRF(s) within a visited PLMN (known as vNRF) consist of information about the visited PLMN, and the NRF(s) within a home PLMN (known as hNRF) consist of information about the home PLMN referenced by the vNRF via the N27 interface.

[0034] PCF708 manages network behavior by supporting a unified policy framework. PCF708 provides and enforces policy rules for control plane functions (one or more). PCF708 accesses subscription information associated with policy decisions in the Unified Data Repository (UDR). PCF708 can access UDRs located within the same PLMN as PCF.

[0035] The UDM710 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI per subscriber in 5G systems), decryption of privacy-protected subscriber identifiers (SUCI), access authorization based on subscriber data (e.g., roaming restrictions), UE serving NF registration management (e.g., storing the UE's serving AMF, storing the UE's serving SMF for PDU sessions), service / session continuity (e.g., by maintaining SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in the case of outbound roaming where the UDM is the sole contact point to the LI), subscriber management, SMS management, 5G LAN group management processing, and / or external parameter provisioning (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM710 uses subscriber data (including authentication data) that can be stored in the UDR, in which case the UDM does not need to implement application logic and internal user data storage, and several different UDMs can serve the same user in different transactions. The UDM710 may be located within the HPLMN of the subscriber it serves, and may access information from the UDR located within the same PLMN.

[0036] AF728 interacts bidirectionally with the core network to provide services that support, for example, application influence on traffic routing, access to NEF704, bidirectional interaction with the policy framework for policy control, and / or bidirectional IMS interaction with 5GC. Based on the operator's deployment, application functions that the operator considers to be trusted can interact directly bidirectionally with the associated network functions. Application functions that the operator cannot directly access the network functions can interact bidirectionally with the associated network functions using an externally exposed framework via NEF704.

[0037] The AUSF712 supports authentication for 3GPP access and untrusted non-3GPP access. The AUSF712 can also provide network slice-specific authentication and authorization support.

[0038] The AMF714 supports termination of the RAN CP interface (N2), termination of the NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interface to LI systems), transport of SM messages between the UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transport of SMS messages between the UE and SMSF and SEAF, location service management for regulatory services, transport of location service messages between the UE and LMF and between the RAN and LMF, EPS bearer ID assignment for interworking with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, provisioning of external parameters (expected UE behavior parameters or network configuration parameters), and / or network slice-specific authentication and authorization. Some or all of the AMF functions may be supported within a single instance of the AMF714. Regardless of the number of network functions, in certain embodiments, there is only one NAS interface instance per access network between the UE and CN, terminating in at least one of the network functions that implement NAS security and mobility management. The AMF714 may also include policy-related functions.

[0039] In addition to the above-mentioned functions, the AMF714 may include the following functions to support non-3GPP access networks: support for an N2 interface with N3IWF / TNGF, where some information (e.g., 3GPP cell identification) and procedures (e.g., handover-related) defined on 3GPP access may not be applicable, and non-3GPP access-specific information not applicable to 3GPP access may be applicable; support for NAS signaling using UEs on N3IWF / TNGF, where some procedures supported by NAS signaling on 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support for authentication of UEs connected via N3IWF / TNGF; management of mobility, authentication, and separate security context states (one or more) for UEs connected via non-3GPP access, or simultaneously connected via 3GPP and non-3GPP access; support for a coordinated RM management context valid on 3GPP and non-3GPP access; and / or support for a CM management context dedicated to UEs for connections via non-3GPP access. It may not always be necessary to support all of the above features within a network slice instance.

[0040] The SMF716 supports session management (e.g., establishing, modifying, and releasing sessions, including maintaining tunnels between UPF and AN nodes), UE IP address allocation and management (including optional approval), where the UE's IP address may be received from the UPF or from external data networks, DHCPv4 (server and client) and DHCPv6 (server and client) functions, address resolution protocol requests and / or functions responding to IPv6 Neighbor Solicitation requests based on local cache information of Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 Neighbor Solicitation requests by providing the MAC address corresponding to the IP address sent at the time of the request), selection and control of user plane functions including controlling the UPF to proxy ARP or IPv6 Neighbor Discovery, or forwarding all ARP / IPv6 Neighbor Solicitation traffic to the SMF for Ethernet PDU sessions, traffic steering settings in the UPF to route traffic to appropriate destinations, and 5G VN group management (e.g., maintaining the topology of associated PSA UPFs, PSA Establishing and releasing N19 tunnels between UPFs, configuring traffic forwarding in UPFs with local switching applied, and / or N6-based or N19-based forwarding), terminating interfaces to policy control functions, lawful interception (for SM events and interfaces to LI systems), collecting billing data and supporting billing interfaces, controlling and coordinating billing data collection in UPFs, terminating the SM portion of NAS messages, downlink data notification, initiating AN-specific SM information sent from N2 to AN via AMF, determining the SSC mode of a session, optimizing the control plane CIoT 5GS, header compression, deployments that can insert / delete / reposition I-SMFs, functioning as an I-SMF, provisioning external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handling local enforcement and QoS)This includes applying SLAs (VPLMN), billing data collection and billing interfaces (VPLMN), and / or lawful interception (for interfacing SM events to VPLMN and LI systems), bidirectional interaction with external DNs for signaling forwarding for PDU session authentication / authorization by external DNs, and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interfaces. Some or all of the SMF functions may be supported within a single instance of SMF. However, in certain embodiments, it is not necessary for all functions to be supported within an instance of a network slice. In addition to these functions, SMF716 may include policy-related functions.

[0041] SCP718 includes any one or more of the following: indirect communication, delegated discovery, message forwarding and routing to destination NF / NF services, communication security (e.g., authorization of NF service consumers to access NF service producer APIs), load balancing, monitoring, overload control, and / or optionally bidirectional interaction with UDRs to resolve UDM group IDs / UDR group IDs / AUSF group IDs / PCF group IDs / CHF group IDs / HSS group IDs based on UE IDs (such as SUPI or IMPI / IMPU). Some or all of the SCP functionality may be supported within a single instance of SCP. In certain embodiments, SCP718 may be deployed in a distributed manner, and / or more than one SCP may exist in the communication path between NF services. SCPs may be deployed at the PLMN level, shared slice level, and slice-specific level. It may be left to the operator's placement to ensure that SCPs can reliably communicate with the relevant NRF.

[0042] The UE720 may include devices with wireless communication capabilities. For example, the UE720 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks). The UE720 may also include any mobile or non-mobile computing device, or any computing device that includes a wireless communication interface, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, or wireless handset. The UE may also be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, or reconfigurable mobile device. The UE720 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize MTC servers or devices, ProSe or D2D communication, sensor networks, or technologies for exchanging data with other UEs via the IoT network (e.g., M2M technology, MTC technology, or mMTC technology) via the PLMN. M2M data exchange or MTC data exchange may be the exchange of machine startup data. An IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0043] UE720 may be configured to connect to or communicate with (R)AN722 via a radio interface 730, which may be a physical communication interface or layer configured to operate with cellular communication protocols such as GSM protocol, CDMAP network protocol, PTT (Push-to-Talk) protocol, POC (PTT over Cellular) protocol, UMTS protocol, 3GPP LTE protocol, 5G protocol, and NR protocol. For example, UE720 and (R)AN722 can exchange control plane data via a protocol stack including the PHY layer, MAC layer, RLC layer, PDCP layer, and RRC layer using a Uu interface (e.g., LTE-Uu interface). DL transmission may be from (R)AN722 to UE720, and UL transmission may be from UE720 to (R)AN722. UE720 may further communicate directly with another UE (not shown) for D2D, P2P, and / or ProSe communication using a sidelink. For example, the ProSe interface may alternatively be referred to as a sidelink interface and comprises one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink sharing channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0044] (R)AN722 includes one or more access nodes, which may be referred to as base stations (BS), node B, evolved node B (eNB), next-generation node B (gNB), RAN nodes, controllers, transmit / receive points (TRP), etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). (R)AN722 may include one or more RAN nodes to provide macrocells, picocells, femtocells, or other types of cells. Macrocells can cover relatively large geographical areas (e.g., a radius of several kilometers) and may enable unrestricted access by UEs with service subscriptions. Picocells can cover relatively small geographical areas and may enable unrestricted access by UEs with service subscriptions. Femtocells can cover relatively small geographical areas (e.g., a home) and may enable restricted access by UEs associated with the femtocell (e.g., UEs within a closed subscriber group (CSG), UEs for users in a home, etc.).

[0045] Although not shown in the diagram, multiple RAN nodes (such as (R)AN722) may be used, where the Xn interface is defined between two or more nodes. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U provides unguaranteed delivery of user plane PDUs and can support / provide data transmission and flow control functions. The Xn-C can provide mobility support for the UE720 in connection modes (e.g., CM connection), including management and error handling functions, functions to manage the Xn-C interface, and functions to manage UE mobility in connection modes between one or more (R)AN nodes. Mobility support may include context transfer from the old (source) serving (R)AN node to the new (target) serving (R)AN node, and control of the user plane tunnel between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

[0046] The UPF724 can function as an anchor point for internal and inter-RAT mobility, an external PDU session point interconnecting to the DN726, and a branching point to support multi-homed PDU sessions. The UPF724 can also perform packet routing and outgoing, packet inspection, enforce the user plane portion of policy rules, legally intercept packets (UP collection); traffic usage reports, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., QoS flow mapping from SDF), transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggers. The UPF724 may include uplink classifiers to support routing traffic flows to the data network. The DN726 can represent various network operator services, internet access, or third-party services. The DN726 may include, for example, an application server.

[0047] Figure 8 is a block diagram of an exemplary UE800 that can be configured according to various embodiments of this disclosure, including the execution of instructions on a computer-readable medium corresponding to any of the exemplary methods and / or procedures described herein. The UE800 includes one or more processors 802, a transceiver 804, a memory 806, a user interface 808, and a control interface 810.

[0048] One or more processors 802 may include, for example, an application processor, a voice digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 802 may include internal memory and / or one or more interfaces for communicating with external memory (including memory 806). The internal or external memory may store software code, programs, and / or instructions executed by one or more processors 802 to configure and / or facilitate the UE800 to perform various operations, including the operations described herein. For example, the execution of instructions may be configured to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, such as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc., or any other current or future protocols that can be used in conjunction with one or more transceivers 804, user interface 808, and / or control interface 810. As another example, one or more processors 802 may execute program code stored in other memory 806 corresponding to MAC layer protocols (e.g., for NR and / or LTE) standardized by 3GPP (e.g., for NR and / or LTE) and RLC layer protocols. As yet another example, processor 802, together with one or more transceivers 804, may execute program code stored in memory 806 or other memory implementing corresponding PHY layer protocols such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0049] Memory 806 may include memory areas for one or more processors 802 that store variables used for protocols, settings, controls, and other functions of the UE800, including operations corresponding to or having operations corresponding to any of the exemplary methods and / or procedures described herein. Furthermore, memory 806 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static RAM or dynamic RAM), or a combination thereof. Furthermore, memory 806 may interface with a memory slot from which removable memory cards (e.g., SD card, memory stick, compact flash, etc.) in one or more formats can be inserted and removed.

[0050] One or more transceivers 804 may include radio frequency transmitters and / or receiver circuits that facilitate communication between the UE800 and other devices supporting wireless communication standards and / or protocols. For example, one or more transceivers 804 may include switches, mixer circuits, amplifier circuits, filter circuits, and combiner circuits. Such RF circuits may include a receive signal path having a circuit that downconverts the RF signal received from the front-end module (FEM) and provides the baseband signal to a baseband processor of one or more processors 802. The RF circuit may also include a transmit signal path that may include a circuit that upconverts the baseband signal provided by the baseband processor and provides the FEM with an RF output signal for transmission. The FEM may include a receive signal path that may include a circuit configured to operate on RF signals received from one or more antennas, amplify the received signal, and provide the amplified version of the received signal to the RF circuit for further processing. The FEM may also include a transmit signal path that may include a circuit configured to amplify the signal for transmission provided by the RF circuit transmitted by one or more antennas. In various embodiments, amplification through the transmit signal path or the receive signal path may be performed in the RF circuit only, in the FEM circuit only, or in both the RF circuit and the FEM circuit. In some embodiments, the FEM circuit may include a TX / RX switch to switch between transmit mode and receive mode operation.

[0051] In some exemplary embodiments, one or more transceivers 804 include transmitters and receivers that enable device 1200 to communicate with various 5G / NR networks in accordance with various protocols and / or methods proposed for standardization by 3GPP and / or other standards organizations. For example, such functionality can work in cooperation with one or more processors 802 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technologies as described herein with respect to other figures.

[0052] The user interface 808 can take various forms depending on the particular embodiment, or may not be present in the UE800. In some embodiments, the user interface 808 has a microphone, a loudspeaker, a sliding button, a pressable button, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface features commonly found on mobile phones. In other embodiments, the UE800 may include a tablet computing device having a larger touchscreen display. In such embodiments, one or more of the mechanical features of the user interface 808 may be replaced by equivalent or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as is well known to those skilled in the art. In other embodiments, the UE800 may be a digital computing device such as a laptop computer, desktop computer, or workstation, having a mechanical keyboard that may be integrated, detachable, or removable depending on the particular exemplary embodiment. Such a digital computing device may also include a touchscreen display. Many exemplary embodiments of the UE800 having a touchscreen display can receive user inputs such as inputs associated with the exemplary methods and / or procedures described herein, or inputs known to those skilled in the art.

[0053] In some exemplary embodiments of this disclosure, the UE800 may include an orientation sensor that can be used in various ways depending on the features and functions of the UE800. For example, the UE800 may use the output of the orientation sensor to determine when the user has changed the physical orientation of the UE800's touchscreen display. The instruction signal from the orientation sensor may be available to any application program running on the UE800 so that the application program can automatically change the orientation of the screen display (e.g., from portrait to landscape) when it indicates a change of approximately 90 degrees in the physical orientation of the device. In this way, the application program can maintain a screen display in a user-readable manner regardless of the physical orientation of the device. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of this disclosure.

[0054] The control interface 810 can take various forms depending on the particular embodiment. For example, the control interface 810 can be an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I2C interface, a PCMCIA interface, and the like. In some exemplary embodiments of this disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface as described above. In some embodiments of this disclosure, the control interface 810 may include, for example, an analog interface circuit including one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0055] Those skilled in the art will understand that the above list of features, interfaces, and radio frequency communication standards is merely illustrative and does not limit the scope of this disclosure. In other words, the UE800 may include more functions than those shown in Figure 8, including, for example, video and / or still image cameras, microphones, media players and / or recorders. Furthermore, one or more transceivers 804 may include communication circuits using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, one or more processors 802 can control such additional functions by executing software code stored in memory 806. For example, the output of directional velocity and / or position estimates from a GPS receiver may be available to any application program running on the UE800, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of this disclosure.

[0056] Figure 9 is a block diagram of an exemplary network node 900 that can be configured according to various embodiments of this disclosure, including the execution of instructions on a computer-readable medium corresponding to any of the exemplary methods and / or procedures described herein.

[0057] The network node 900 includes one or more processors 902, a wireless network interface 904, memory 906, a core network interface 908, and other interfaces 910. The network node 900 may include, for example, a base station, an eNB, a gNB, an access node, or components thereof.

[0058] One or more processors 902 may include any type of processor or processing circuit and may be configured to perform one of the methods or procedures disclosed herein. Memory 906 stores software code, programs, and / or instructions executed by one or more processors 902 and can configure the network node 900 to perform various operations, including the operations described herein. For example, the execution of such stored instructions may configure the network node 900 to communicate with one or more other devices using protocols according to various embodiments of this disclosure, including one or more of the methods and / or procedures described above. Furthermore, the execution of such stored instructions may also configure and / or facilitate the network node 900 to communicate with one or more other devices using other protocols or protocol layers, such as one or more of the PHY layer protocols, MAC layer protocols, RLC layer protocols, PDCP layer protocols, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher layer protocols used in combination with the radio network interface 904 and the core network interface 908. For example, but not limited to, the core network interface 908 may include an S1 interface, and the wireless network interface 904 may include a Uu interface standardized by 3GPP. Memory 906 may also store variables, settings, controls, and other functions used for the network node 900's protocols. Thus, memory 906 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static RAM or dynamic RAM), network-based storage (e.g., "cloud"), or a combination thereof.

[0059] The wireless network interface 904 may include a transmitter, receiver, signal processor, ASIC, antenna, beamforming unit, and other circuitry that enables the network node 900 to communicate with other devices, such as multiple compatible user equipment (UEs), in some embodiments. In some embodiments, the network node 900 may include various protocols or protocol layers, such as the PHY layer protocol, MAC layer protocol, RLC layer protocol, PDCP layer protocol, and RRC layer protocol, which are standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to further embodiments of the present disclosure, the wireless network interface 904 may include a PHY layer based on OFDM technology, OFDMA technology, and / or SC-FDMA technology. In some embodiments, the functionality of such a PHY layer may be provided collaboratively by the wireless network interface 904 and one or more processors 902.

[0060] In some embodiments, the core network interface 908 may include transmitters, receivers, and other circuits that enable network nodes 900 to communicate with other devices in the core network, such as circuit-switched (CS) and / or packet-switched core (PS) networks. In some embodiments, the core network interface 908 may include the S1 interface standardized by 3GPP. In some embodiments, the core network interface 908 may include one or more interfaces to one or more SGWs, MMEs, SGSNs, GGSNs, and other physical devices, including features found in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks known to those skilled in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layers of the core network interface 908 may include one or more of the following wired or wireless transmission technologies known to those skilled in the art: Asynchronous Transfer Mode (ATM), Internet Protocol over Ethernet (IP), SDH over optical fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies.

[0061] Other interfaces 910 may include transmitters, receivers, and other circuits that enable the network node 900 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining the network node 900 or other network equipment operably connected thereto.

[0062] In one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following Examples section. For example, the baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described below. As another example, a circuit associated with a UE, base station, network element, etc., as described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0063] Examples section

[0064] Example 1a is a method for determining the priority of simultaneous sidelink (SL) transmissions and uplink (UL) transmissions of user equipment (UE) in a 5G new radio (NR) network, the method comprising: processing SL control information (SCI) corresponding to at least one of SL hybrid automatic repetition requests (HARQs) or SL scheduling requests (SRs) included in a UL transmission transmitted by the UE, thereby determining a priority value associated with at least one SL HARQ or SL SR, wherein the UL transmission does not include physical random access channel (PRACH), physical uplink control channel (PUSCH) scheduled by random access response (RAR) UL authorization, or ultra-reliable low-latency communication (URLLC) traffic; processing the SCI of an SL transmission transmitted simultaneously with the UL transmission by the UE, thereby determining a priority value associated with the SL transmission; comparing the priority value of at least one SL HARQ or SL SR with the priority value of the SL transmission; and prioritizing the transmissions based on the comparison of priority values.

[0065] Example 2a may include the method of Example 1a, further comprising determining, based on a comparison of priority values, that at least one SL HARQ or SL SR has a higher priority than an SL transmission, and, in accordance with the determination that at least one SL HARQ or SL SR has a higher priority than an SL transmission, prioritizing UL transmissions over SL transmissions.

[0066] Example 3a may include the method of Example 1a, further comprising: determining that the UL transmission is a physical uplink control channel (PUCCH); determining, based on a comparison of priority values, that at least one SL HARQ or SL SR has a lower priority than the SL transmission; and, in accordance with the determination that at least one SL HARQ or SL SR has a lower priority than the SL transmission, prioritizing the SL transmission over the UL transmission.

[0067] Example 4a may include the method of Example 1a, further comprising: determining that the UL transmission is PUSCH and includes either SL HARQ or SL SR, and does not include other uplink data; determining, based on a comparison of priority values, that SL HARQ or SL SR has a lower priority than SL transmission; and, in accordance with the determination that SL HARQ or SL SR has a lower priority than SL transmission, prioritizing SL transmission over UL transmission.

[0068] Embodiment 5a may include a user equipment (UE) device comprising one or more processors configured to identify radio interface (Uu) uplink (UL) control information (UCI) transmissions and sidelink (SL) hybrid automatic repetitive request (HARQ) reports transmitted by the UE, determine a priority value for Uu UCI transmissions, determine the type of transmission associated with the Uu UCI transmissions based at least in part on the determined priority value, and prioritize the UE's transmissions based on the determined type of transmission associated with the UL transmissions; and a memory configured to store Uu UCI and SL HARQ reports.

[0069] Example 6a may include the apparatus of Example 5a, further configured so that one or more processors determine that the transmission type is an ultra-reliable low-latency communication (URLLC) UCI ​​transmission, and based on the determination that the transmission type is a URLLC UCI transmission, transmit a Uu UCI transmission and drop the SL HARQ report.

[0070] Example 7a may include the apparatus of Example 6a, wherein the URLLC UCI transmission includes one of the following: URLLC downlink HARQ-ACK, channel status information (CSI) report, or schedule request (SR).

[0071] Example 8a may further include the apparatus described in Example 5a, wherein one or more processors determine that the type of transmission is an enhanced mobile broadband (eMBB) UCI ​​transmission, process SL control information (SCI) corresponding to an SL HARQ report based on the determination that the type of transmission is an eMBB UCI transmission, thereby determine a priority value associated with the SL HARQ report, compare the priority value associated with the SL HARQ report with a priority threshold, and prioritize the transmission based on the comparison between the priority value of the SL HARQ report and the priority threshold.

[0072] Example 9a may include the apparatus described in Example 8a, further configured so that one or more processors determine, based on a comparison of the priority value associated with the SL HARQ report with a priority threshold, that the priority value is lower than the priority threshold, and based on the determination that the priority value is lower than the priority threshold, transmit the SL HARQ report and drop the eMBB UCI transmission.

[0073] Example 10a may include the apparatus described in Example 8a, further configured to determine, based on a comparison of a priority value associated with an SL HARQ report with a priority threshold, that the priority value is higher than the priority threshold, and based on the determination that the priority value is higher than the priority threshold, send an eMBB UCI transmission and drop the SL HARQ report.

[0074] Example 11a may include the apparatus of Example 8a, further configured to identify at least one additional SL HARQ report transmitted by the UE, process the SCI corresponding to each of the at least one additional SL HARQ reports, thereby determining the priority value associated with each of the at least one additional SL HARQ reports, and use the SCI corresponding to the SL HARQ report and each of the at least one additional HARQ report having the lowest priority value when compared to a priority threshold.

[0075] Embodiment 12a may include a computer-readable storage medium which, when executed by a processor of a user device (UE) configured to determine the priority of simultaneous transmissions of the user device (UE) on a physical uplink control channel (PUSCH) in a 5G new radio (NR) network, causes the processor to identify sidelink (SL) hybrid automatic repeat request (HARQ) reports that are multiplexed with uplink (UL) data transmissions, determine a priority value for UL data transmissions, determine the type of transmission associated with a UL data transmission based at least in part on the determined UL data priority value, and prioritize the UE's transmissions based on the determined type of transmission associated with a UL data transmission.

[0076] Example 13a may include the computer-readable storage medium of Example 12, further configured to cause the processor to determine that the type of transmission is an ultra-reliable low-latency communication (URLLC) UL data transmission, and based on this determination that the type of transmission is a URLLC UL data transmission, to transmit the UL data transmission and drop the SL HARQ report.

[0077] Embodiment 14a may include a computer-readable storage medium of Embodiment 12a, further configured to cause the processor to determine that the type of transmission is an extended mobile broadband (eMBB) UL data transmission, compare the priority value of the UL data transmission with a UL priority threshold based on the determination that the type of transmission is an eMBB UL data transmission, and prioritize the transmissions of the UE based on the comparison between the priority value of the UL data transmission and the UL priority threshold.

[0078] Example 15a may include a computer-readable storage medium of Example 14a, wherein the instruction further configures the processor to determine that the priority value for UL data transmission is lower than the UL priority threshold, and based on this determination, transmit the UL data transmission and drop or delay the SL HARQ report.

[0079] Embodiment 16a may further include the computer-readable storage medium of Embodiment 14a, wherein the instruction is configured to cause the processor to determine that the priority value of a UL data transmission is higher than the UL priority threshold, to process SL control information (SCI) corresponding to an SL HARQ report based on the determination that the priority value of a UL data transmission is higher than the UL priority threshold, thereby determining the priority value associated with the SL HARQ report, to compare the priority value of the SL HARQ report with the SL priority threshold, and to prioritize the transmission based on the comparison between the priority value of the SL HARQ report and the SL priority threshold.

[0080] Example 17a may include a computer-readable storage medium of Example 16a, wherein the instruction further configures the processor to determine that the priority value of the SL HARQ report is lower than the SL priority threshold, and based on this determination, to send the SL HARQ report and drop or delay the UL data transmission.

[0081] Example 18a may include a computer-readable storage medium of Example 16a, wherein the instruction further configures the processor to determine that the priority value of an SL HARQ report is higher than the SL priority threshold, and based on this determination, to send a UL data transmission and drop or delay the SL HARQ report.

[0082] Embodiment 19a may include a computer-readable storage medium of Embodiment 12a, further configured to cause a processor to determine that the type of transmission is an extended mobile broadband (eMBB) UL data transmission, process SL control information (SCI) corresponding to an SL HARQ report based on the determination that the type of transmission is an eMBB UL data transmission, thereby determine a priority value associated with the SL HARQ report, compare the priority value of the UL data transmission with the priority value of the SL HARQ report, and prioritize the transmission based on the comparison between the priority value of the UL data transmission and the priority value of the SL HARQ report.

[0083] Example 20a may include a computer-readable storage medium of Example 19a, wherein the instruction further configures the processor to determine that the priority value for UL data transmission is lower than the priority value for SL HARQ reporting, and based on this determination, transmit UL data transmission and drop or delay SL HARQ reporting.

[0084] Example 21a is a non-temporary computer-readable storage medium, which, when executed by a processor of a user device (UE) configured to determine the priority of simultaneous sidelink (SL) transmissions and uplink (UL) transmissions of a UE in a 5G new radio (NR) network, causes the processor to process SL control information (SCI) corresponding to at least one of SL hybrid automatic repeating requests (HARQ) or SL scheduling requests (SR) included in a UL transmission transmitted by the UE, thereby causing it to determine a priority value associated with at least one SL HARQ or SL SR, and the UL transmission does not include physical random access channel (PRACH), physical uplink control channel (PUSCH) scheduled by random access response (RAR) UL authorization, or ultra-reliable low-latency communication (URLLC) traffic, and the SCI of an SL transmission transmitted by the UE is processed simultaneously with the UL transmission, thereby causing it to determine a priority value associated with the SL transmission, and at least one SL HARQ or SL It may include a non-temporary computer-readable storage medium containing instructions that compare the priority value of an SR transmission with the priority value of an SL transmission and prioritize transmissions based on the comparison of priority values.

[0085] Embodiment 22a may include a computer-readable storage medium of Embodiment 21a, wherein the instruction further configures the processor to determine, based on a comparison of priority values, that at least one SL HARQ or SL SR has a higher priority than an SL transmission, and in accordance with the determination that at least one SL HARQ or SL SR has a higher priority than an SL transmission, it prioritizes UL transmissions over SL transmissions.

[0086] Embodiment 23a may include a computer-readable storage medium of Embodiment 21a, further configured such that the instruction causes the processor to determine that a UL transmission is a physical uplink control channel (PUCCH), determine, based on a comparison of priority values, that at least one SL HARQ or SL SR has a lower priority than an SL transmission, and, in accordance with the determination that at least one SL HARQ or SL SR has a lower priority than an SL transmission, to prioritize the SL transmission over the UL transmission.

[0087] Example 24a may include the computer-readable storage medium of Example 21, further configured such that the instruction causes the processor to determine that the UL transmission is PUSCH and includes either SL HARQ or SL SR and does not include any other uplink data, determines that SL HARQ or SL SR has a lower priority than SL transmission based on a comparison of priority values, and, in accordance with the determination that SL HARQ or SL SR has a lower priority than SL transmission, prioritizes SL transmission over UL transmission.

[0088] Example 1b may include an apparatus that includes means for performing one or more elements of any of the methods or processes described herein or related to such methods.

[0089] Embodiment 2b may include one or more non-temporary computer-readable media containing instructions, wherein when an instruction is executed by one or more processors of an electronic device, the instruction causes the electronic device to execute one or more elements of the methods described in or related to any of the above embodiments, or any other methods or processes described herein.

[0090] Example 3b may include an apparatus that includes logic, modules, or circuits that perform one or more elements of the methods described in or related to any of the above examples, or any other methods or processes described herein.

[0091] Example 4b may include a method, technique, or process described in or related to any of the above examples, or a part or portion thereof.

[0092] Example 5b may include an apparatus comprising one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a part thereof, described in or related to any of the above embodiments.

[0093] Example 6b may include signals, or parts thereof, described in or related to any of the above examples.

[0094] Example 7b may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in or related to any of the above examples, or any part thereof, or any other described herein.

[0095] Example 8b may include signals encoded by data described in or related to the above examples, or any part thereof, or any other described herein.

[0096] Example 9b may include signals encoded by datagrams, packets, frames, segments, PDUs, or messages described in or related to the above examples, or any part or portion thereof, or any other described herein.

[0097] Example 10b may include an electromagnetic signal carrying a computer-readable instruction, which causes one or more processors to execute a method, technique, or process described in or related to any of the above examples or parts thereof, for the execution of a computer-readable instruction by one or more processors.

[0098] Example 11b may include a computer program in which the execution of a program by a processing element includes instructions that cause the processing element to execute a method, technique, or process described in or related to any of the above examples or parts thereof.

[0099] Example 12b may include signals in a wireless network as described herein.

[0100] Example 13b may include a method of communication in a wireless network as described herein.

[0101] Example 14b may include a system that provides wireless communication as described herein.

[0102] Example 15b may include a device that provides wireless communication as described herein.

[0103] Any of the embodiments described above can be combined with any other embodiment (or combination of embodiments) unless otherwise specified. The above descriptions of one or more implementation forms are illustrative and illustrative, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible based on the above teachings or can be learned from the practice of various embodiments.

[0104] The embodiments and implementations of the systems and methods described herein may include a variety of operations that can be embodied by machine-executable instructions performed by a computer system. The computer system may include one or more general-purpose computers or dedicated computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing operations, or it may include a combination of hardware, software, and / or firmware.

[0105] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, divided into multiple systems, or otherwise divided or combined. In addition, parameters, attributes, aspects, etc. of one embodiment are intended to be used in another embodiment. Parameters, attributes, aspects are described in one or more embodiments for clarity only, and it should be recognized that parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, etc. of another embodiment unless specifically abandoned herein.

[0106] It is well understood that the use of personally identifiable information should be governed by privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0107] While the foregoing has been described in some detail for clarity, it will be clear that certain changes and modifications can be made without departing from the principles. It should be noted that many alternative methods exist for implementing both the processes and apparatus described herein. Therefore, these embodiments should be considered illustrative and not limiting, and the description is not limited to the details given herein and may be modified within the appended claims and equivalents.

Claims

1. A user equipment (UE) device, Identify the radio interface (Uu) uplink (UL) control information (UCI) transmission transmitted by the UE, the sidelink (SL) hybrid automatic repetition request (HARQ) report transmitted by the UE, and at least one additional SL HARQ report transmitted by the UE. Determine the priority value of the Uu UCI transmission, Based at least in part on the priority value determined above, the type of transmission associated with the Uu UCI transmission is determined. Based on the determined transmission type associated with the UL transmission, the UE transmissions are prioritized. In response to determining that the type of transmission is an extended mobile broadband (eMBB) UCI ​​transmission, Determine the priority value associated with the aforementioned SL HARQ report, Determine the additional priority value associated with each of the at least one additional SL HARQ reports mentioned above. The priority value associated with the SL HARQ report or the additional priority value associated with the at least one additional SL HARQ report is compared with the priority threshold, and when compared with the priority threshold, the lowest priority value of the priority value and the additional priority value associated with the SL HARQ report is used. The transmission is prioritized based on the comparison between the priority threshold and the priority value of the SL HARQ report. One or more processors configured as follows, A memory configured to store the Uu UCI and the SL HARQ report, A user equipment (UE) device that includes the following.

2. The one or more processors described above The type of transmission is determined to be ultra-reliable low-latency communication (URLLC) UCI ​​transmission, Based on the determination that the type of transmission is the URLC UCI transmission, The aforementioned Uu UCI transmission is sent, Drop the aforementioned SL HARQ report. It is further structured in such a way. The apparatus according to claim 1.

3. The apparatus according to claim 2, wherein the URLLC UCI transmission includes one of URLLC downlink HARQ-ACK, channel status information (CSI) report, or schedule request (SR).

4. The one or more processors described above Based on a comparison between the priority value associated with the SL HARQ report and the priority threshold, it is determined that the priority value is lower than the priority threshold. Based on the determination that the priority value is lower than the priority threshold, The aforementioned SL HARQ report is transmitted, The aforementioned eMBB UCI transmission is dropped. The apparatus according to claim 1, further configured as follows.

5. The one or more processors described above Based on a comparison between the priority value associated with the SL HARQ report and the priority threshold, it is determined that the priority value is higher than the priority threshold. Based on the determination that the priority value is higher than the priority threshold, The aforementioned eMBB UCI transmission is sent, Drop the aforementioned SL HARQ report. The apparatus according to claim 1, further configured as follows.

6. A computer-readable storage medium, which, when executed by a processor of a user device (UE) configured to determine the priority of simultaneous transmissions of the user device (UE) on a physical uplink control channel (PUSCH) in a 5G new radio (NR) network, the processor is instructed to: Identify uplink (UL) data transmissions and sidelink (SL) hybrid automatic repeating request (HARQ) reports that are multiplexed, and at least one additional SL HARQ report transmitted by the UE, Determine the priority value of the UL data transmission. Based at least in part on the determined UL data priority value, the type of transmission associated with the UL data transmission is determined. Based on the determined transmission type associated with the UL data transmission, the transmissions of the UE are prioritized. In response to determining that the type of transmission is an extended mobile broadband (eMBB) UCI ​​transmission, Determine the priority value associated with the aforementioned SL HARQ report. Determine the additional priority value associated with each of the at least one additional SL HARQ reports. The priority value associated with the SL HARQ report or the additional priority value associated with the at least one additional SL HARQ report is compared with the priority threshold, and when compared with the priority threshold, the lowest priority value of the priority value and the additional priority value associated with the SL HARQ report is used. A computer-readable storage medium including instructions for prioritizing transmissions based on the comparison between the priority threshold and the priority value of the SL HARQ report.

7. The instruction causes the processor to The type of transmission is determined to be ultra-reliable low-latency communication (URLLC) UL data transmission. Based on the determination that the type of transmission is the URLLC UL data transmission, The UL data transmission is sent, Drop the aforementioned SL HARQ report. The computer-readable storage medium according to claim 6, further configured as follows.

8. The instruction causes the processor to The type of transmission is determined to be an extended mobile broadband (eMBB) UL data transmission. Based on the determination that the type of transmission is the eMBBUL data transmission, The priority value of the UL data transmission is compared with the UL priority threshold, Based on the comparison between the priority value of the UL data transmission and the UL priority threshold, the transmission of the UE is prioritized. The computer-readable storage medium according to claim 6, further configured as follows.

9. The instruction causes the processor to If it is determined that the priority value of the UL data transmission is lower than the UL priority threshold, Based on the determination that the priority value of the UL data transmission is lower than the UL priority threshold, The UL data transmission is sent, Drop or delay the aforementioned SL HARQ report. The computer-readable storage medium according to claim 8, further configured as follows.

10. The instruction causes the processor to If it is determined that the priority value of the UL data transmission is higher than the UL priority threshold, Based on the determination that the priority value of the UL data transmission is higher than the UL priority threshold, The SL control information (SCI) corresponding to the SL HARQ report is processed, and the priority value associated with the SL HARQ report is determined accordingly. The priority value of the SL HARQ report is compared with the SL priority threshold. The transmission is prioritized based on the comparison between the priority value of the SL HARQ report and the SL priority threshold. The computer-readable storage medium according to claim 8, further configured as follows.

11. The instruction causes the processor to If the priority value of the SL HARQ report is determined to be lower than the SL priority threshold, Based on the determination that the priority value of the SL HARQ report is lower than the SL priority threshold, The aforementioned SL HARQ report is transmitted, Dropping or delaying the aforementioned UL data transmission, The computer-readable storage medium according to claim 10, further configured as follows.

12. The instruction causes the processor to If the priority value of the SL HARQ report is determined to be higher than the SL priority threshold, Based on the determination that the priority value of the SL HARQ report is higher than the SL priority threshold, The UL data transmission is sent, Drop or delay the aforementioned SL HARQ report. The computer-readable storage medium according to claim 10, further configured as follows.

13. The instruction causes the processor to If it is determined that the priority value of the UL data transmission is lower than the priority value of the SL HARQ report, Based on the determination that the priority value of the UL data transmission is lower than the priority value of the SL HARQ report, The UL data transmission is sent, Drop or delay the aforementioned SL HARQ report. The computer-readable storage medium according to claim 6, further configured as follows.

Images