Overlap of DL reception and UL transmission for HD-FDD operation

Abstract

A computer-readable storage medium stores instructions for configuring a UE to communicate utilizing HD-FDD multiplexing in 5G NR and beyond wireless networks and causing the UE to perform operations. The operations include decoding DCI received over a PDCCH, where the DCI indicates reception of a dynamically scheduled DL on a PDSCH. The operations further include detecting an overlap between reception of the dynamically scheduled DL on a PUSCH and a semi-statically configured UL transmission. The operations further include determining to perform either reception of the dynamically scheduled DL or transmission of the semi-statically configured UL based on a start time (T0) of the semi-statically configured UL transmission and a pre-set offset time (Toffset).

Description

[Technical field]

[0001] This application claims the benefit of priority to the following U.S. provisional patent applications:

[0002] U.S. Provisional Patent Application No. 63 / 171,462, filed on April 6, 2021, and entitled “OVERLAP BETWEEN DOWNLINK RECEPTION AND UPLINK TRANSMISSION FOR HALF-DUPLEX FREQUENCY DIVISION MULTIPLEXING OPERATIONS IN NEW RADIO SYSTEMS.”

[0003] U.S. Provisional Patent Application No. 63 / 186,703, filed on May 10, 2021, and entitled "OVERLAP BETWEEN DOWNLINK RECEPTION AND UPLINK TRANSMISSION FOR HALF-DUPLEX FREQUENCY DIVISION MULTIPLEXING OPERATIONS IN NEW RADIO SYSTEMS."

[0004] U.S. Provisional Patent Application No. 63 / 229,799, filed on August 5, 2021, and entitled “OVERLAP BETWEEN DOWNLINK RECEPTION AND UPLINK TRANSMISSION FOR HALF-DUPLEX FREQUENCY DIVISION MULTIPLEXING OPERATIONS IN NEW RADIO SYSTEMS.”

[0005] U.S. Provisional Patent Application No. 63 / 284,226, filed on November 30, 2021, and entitled "OVERLAP BETWEEN DOWNLINK RECEPTION AND UPLINK TRANSMISSION FOR HALF-DUPLEX FREQUENCY DIVISION MULTIPLEXING OPERATIONS IN NEW RADIO SYSTEMS."

[0006] U.S. Provisional Patent Application No. 63 / 284,856, filed on December 1, 2021, and entitled "OVERLAP BETWEEN DOWNLINK RECEPTION AND UPLINK TRANSMISSION FOR HALF-DUPLEX FREQUENCY DIVISION MULTIPLEXING OPERATIONS IN NEW RADIO SYSTEMS."

[0007] Each of the above US provisional patent applications is incorporated herein by reference in its entirety.

[0008] Aspects of the present invention relate to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP (Long Term Evolution) (LTE) networks, 3GPP LTE Advanced (LTE-A) networks, (MultiFire, LTE-U), and fifth generation (5G) networks, and further to wireless networks including 5G-LTE networks such as 5G New Radio (NR) (or 5G-NR) networks, 5G NR Unlicensed Spectrum (NR-U) networks, and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc. Other aspects are directed to mechanisms for handling overlap between downlink (DL) reception and uplink (UL) transmission for half-duplex frequency division duplex (HD-FDD) multiplexing operation in 5G-NR and beyond network communications. [Background technology]

[0009] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated and integrated communications platforms. Applications of 3GPP® LTE systems are increasing with an increasing number of different types of devices communicating with various network devices. The proliferation of mobile devices (user equipment or UE) in modern society is driving the demand for a variety of networked devices in many different environments. Fifth generation (5G) wireless systems are emerging and are expected to enable improved speeds, connectivity, and applications. Next-generation 5G networks (or NR networks) are expected to increase throughput, coverage, and robustness while reducing latency, operational and financial costs. Based on 3GPP LTE-Advanced, 5G-NR networks will continue to evolve with new upcoming Radio Access Technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver rich content and services at high speeds. However, current cellular network frequencies are saturated, and higher frequencies, such as millimeter wave (mmWave) frequencies, may be advantageous in terms of higher bandwidth.

[0010] Possible LTE operation in the unlicensed spectrum includes, but is not limited to, LTE operation in the unlicensed spectrum via dual connectivity (DC) or DC-based LAA, and standalone LTE systems in the unlicensed spectrum, whereby LTE-based technologies operate fully alone in the unlicensed spectrum without the need for an "anchor" in the licensed spectrum, called MulteFire. Further enhanced operation of LTE and NR systems in licensed and unlicensed spectrum is expected in future releases and 5G-NR (and beyond) systems. Such enhanced operation may include mechanisms to handle overlap between DL reception and UL transmission for HD-FDD multiplexing operation in 5G-NR and beyond network communications. [Brief description of the drawings]

[0011] In the drawings, which are not necessarily drawn to scale, like reference numbers may refer to like components in different views. Like reference numbers with different subscripts may refer to different instances of like components. The drawings illustrate, by way of example, but not by way of limitation, various aspects discussed in the present specification. [Figure 1A] 1 illustrates a network architecture according to an embodiment. [Figure 1B] 1 illustrates a non-roaming 5G system architecture according to an embodiment. [Figure 1C] 1 illustrates a non-roaming 5G system architecture according to an embodiment. [Diagram 2] Various systems, devices and components are illustrated that are capable of performing aspects of the disclosed embodiments. [Diagram 3] Various systems, devices and components are illustrated that are capable of performing aspects of the disclosed embodiments. [Figure 4] Various systems, devices and components are illustrated that are capable of performing aspects of the disclosed embodiments. [Diagram 5] 1 illustrates a diagram of overlapping dynamic PDSCH and CG PUSCH according to an aspect. [Figure 6] 1 illustrates a diagram of overlapping dynamic PDSCH and CG PUSCH according to an aspect. [Figure 7] 1 illustrates a diagram of overlapping dynamic PDSCH and dynamic PUSCH according to an aspect. [Figure 8] 1 illustrates a diagram of overlapping dynamic PDSCH and dynamic PUSCH according to an aspect. [Figure 9] 1 illustrates a diagram of overlapping dynamic PDSCH and dynamic PUSCH according to an aspect. [Figure 10]FIG. 1 illustrates a block diagram of a communications device, such as an evolved Node B (eNB), new generation Node B (gNB) (or another RAN node or base station), transmit / receive point (TRP), access point (AP), wireless station (STA), mobile station (MS), or user equipment (UE), according to an aspect. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The following description and drawings sufficiently illustrate the embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for those of other embodiments. The embodiments outlined in the claims encompass all available equivalents of those claims. 1A illustrates an architecture of a network according to some aspects. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101, 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101, 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0013] Any of the wireless links described herein (eg, as used in network 140A or any other illustrated network) may operate in accordance with any example wireless communication technology and / or standard.

[0014] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs, such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique in which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In certain aspects, carrier aggregation may be used when one or more component carriers operate on unlicensed frequencies.

[0015] The aspects described herein may be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, licensed shared spectrum (such as Licensed Shared Access (LSA) in the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and beyond, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0016] The aspects described herein may also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), particularly 3GPP New Radio (NR), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0017] In an aspect, any of the UEs 101, 102 may comprise an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, any of the UEs 101, 102 may comprise a Narrowband (NB) IoT UE (e.g., Enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as Machine-to-Machine (M2M) or Machine-Type Communication (MTC) to exchange data with an MTC server or device over a Public Land Mobile Network (PLMN), Proximity-Based Services (ProSe), or Device-to-Device (D2D) communication, sensor network, or IoT network. The M2M or MTC data exchange may be a machine-initiated exchange of data. The IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with temporary connections. The IoT UE may perform a call to facilitate connectivity to the IoT network, such as to facilitate connectivity to the IoT network.

[0018] In an aspect, any of the UEs 101, 102 may include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0019] The UEs 101, 102 may be configured to connect, e.g., communicatively couple, with a Radio Access Network (RAN) 110. The RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), or a NextGen RAN (NG RAN), or some other type of RAN. UEs 101, 102 utilize connections 103, 104, respectively, each of which comprises a physical communication interface or layer (described in further detail below), which in this example are shown as air interfaces enabling communication coupling and may be consistent with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, etc.

[0020] In one aspect, the UEs 101, 102 may further exchange communication data directly via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0021] The UE 102 is shown configured to access an access point (AP) 106 via a connection 107. The connection 107 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, where the AP 106 may comprise a Wireless Fidelity (WIFI) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

[0022] The RAN 110 may include one or more access nodes that enable the connections 103, 104. These access nodes (AN) may be referred to as base stations (BS), Node Bs, evolved Node Bs (eNBs), next generation Node Bs (gNBs), RAN network nodes, etc., and may comprise terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In an aspect, the communication nodes 111, 112 may be transmission / reception points (TRPs). If the communication nodes 111, 112 are Node Bs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the Node B. The RAN 110 may include one or more RAN nodes for providing a macro cell, such as a macro RAN node 111, and one or more RAN nodes for providing a femto cell or a pico cell (e.g., a cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macro cell), such as a low power (LP) RAN node 112 or an unlicensed spectrum based secondary RAN node 112.

[0023] Either of the RAN nodes 111, 112 may terminate air interface protocols and may be the first point of contact to the UEs 101, 102. In an aspect, either of the RAN nodes 111, 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management, and radio network controller (RNC) functions such as data packet scheduling and mobility management. In one example, either of the nodes 111 and 112 may be a new generation Node B (gNB), an evolved Node B (eNB), or another type of RAN node.

[0024] The RAN 110 is shown communicatively coupled to a Core Network (CN) 120 via an S1 interface 113. In aspects, the CN 120 may be an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as described with reference to FIGS. 1B-1C). In such aspects, the S1 interface 113 is split into two parts: an S1-U interface 114 that carries user traffic data between the RAN nodes 111, 112 and a Serving Gateway (S-GW) 122, and an S1-Mobility Management Entity (MME) interface 115 that is a signaling interface between the RAN nodes 111, 112 and the MME 121.

[0025] In such an aspect, the CN 120 comprises an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription related information to support network entity handling of communication sessions. The CN 120 may comprise one or several HSSs 124 depending on the number of mobile subscribers, equipment capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0026] The S-GW 122 terminates the S1 interface 113 to the RAN 110 and may route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for handovers between RAN nodes and may provide an anchor for inter-3GPP mobility. Other functions of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0027] The P-GW 123 may terminate an SGi interface to the PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, including the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. In general, the application server 184 may be an element that provides applications (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.) that use IP bearer resources in conjunction with a core network. In such an aspect, the P-GW 123 is communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) to the UEs 101, 102 via the CN 120.

[0028] Furthermore, the P-GW 123 may be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in an aspect, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session, namely, a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively connected to the application server 184 via the P-GW 123.

[0029] In an aspect, the communication network 140A may be an IoT network or a 5G network, including 5G new wireless networks that use communications in licensed (5G NR) and unlicensed (5G NR-U) spectrums. One of the current enablers of IoT is Narrowband IoT (NB-IoT).

[0030] The NG system architecture may include a RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 may include multiple nodes such as gNBs and NG-eNBs. The core network 120 (e.g., 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNBs and NG-eNBs via an NG interface. More specifically, in an aspect, the gNBs and NG-eNBs may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNBs and NG-eNBs may be coupled to each other via an Xn interface.

[0031] In an aspect, the NG system architecture can use reference points between various nodes such as those provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In an aspect, each of the gNB and NG-eNB can be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, etc. In an aspect, in a 5G architecture, the gNB can be a master node (MN) and the NG-eNB can be a secondary node (SN). In an aspect, the master / primary node can operate in a licensed band and the secondary node can operate in an unlicensed band.

[0032] FIG. 1B illustrates a non-roaming 5G system architecture according to an aspect. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 may be in communication with a RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes a number of network functions (NFs), such as an Access and Mobility Management Function (AMF) 132, a Location Management Function (LMF) 133, a Session Management Function (SMF) 136, a Policy Control Function (PCF) 148, an Application Function (AF) 150, a User Plane Function (UPF) 134, a Network Slice Selection Function (NSSF) 142, an Authentication Server Function (AUSF) 144, and a Unified Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 may provide connectivity to a Data Network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. The AMF 132 may be used to manage access control and mobility, and may also include a network slice selection function. The SMF 136 may be configured to set up and manage various sessions according to network policies. The UPF 134 may be deployed in one or multiple configurations according to the desired service type. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0033] The LMF 133 may be used in conjunction with 5G positioning functions. In an aspect, the LMF 133 receives measurements and aiding information from the Next Generation Radio Access Network (NG-RAN) 110 and mobile devices (e.g., UE 101) via the AMF 132 over the NLs interface to calculate the position of the UE 101. In an aspect, the NR Positioning Protocol A (NRPPa) may be used to carry positioning information between the NG-RAN and the LMF 133 over the Next Generation Control Plane Interface (NG-C). In an aspect, the LMF 133 configures the UE using the LTE Positioning Protocol (LPP) via the AMF 132. The NG RAN 110 configures the UE 101 using a Radio Resource Control (RRC) protocol over the LTE-Uu and NR-Uu interfaces.

[0034] In an aspect, the 5G system architecture 140B configures different reference signals to enable positioning measurements. Exemplary reference signals that may be used for positioning measurements include a positioning reference signal (NR PRS) in the downlink and a sounding reference signal (SRS) for positioning in the uplink. The downlink positioning reference signal (PRS) is a reference signal configured to support a downlink-based positioning method.

[0035] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP multimedia subsystem (IMS) 168B, as well as a call session control function (CSCF). More specifically, the IMS 168B includes a CSCF that can operate as a Proxy CSCF (P-CSCF) 162 BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be a first point of contact for the UE 102 in the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state in the network, and the E-CSCF can be configured to handle some aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to act as a contact point within the operator's network for all IMS connections destined for the network operator's subscribers or roaming subscribers currently located within the network operator's service area. In an aspect, the I-CSCF 166B may be connected to another IP multimedia network 170E, e.g., an IMS operated by a different network operator.

[0036] In an aspect, the UDM / HSS 146 may be coupled to an application server 160E, which may include a telephony application server (TAS) or another application server (AS). The AS 160B may be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0037] The reference point representation indicates that there may be interactions between corresponding NF services. For example, FIG. 1B shows N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between SMF 136 and PCF 148, not shown), N8 (between UFM 146 and AMF 132, not shown), N9 (between two UPFs 134 and DN 152), N10 (between UFM 146 and SMF 136, not shown), N11 (between AMF 132 and SM 1B shows the following reference points: N12 (between AUSF 144 and AMF 32, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between PCF 148 and AMF 132 in case of a non-roaming scenario, or between PCF 148, visited network, and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Note that other reference point representations not shown in FIG. 1B may be used.

[0038] 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in FIG. 1B, the system architecture 140C may also include a network publication function (NEF) 154 and a network repository function (NRF) 156. In an aspect, the 5G system architecture may be service-based, and the interactions between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0039] In an aspect, as shown in Figure 1C, a service-based representation may be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, and Nudsf) may also be used.

[0040] 2, 3, and 4 illustrate various systems, devices, and components that can implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR (and beyond) networks. UEs, base stations (such as gNBs), and / or other nodes (such as satellites or other NTN nodes) may be configured to perform the disclosed techniques.

[0041] 2 illustrates a network 200 according to various embodiments. Network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, example embodiments are not limited in this respect, and the described embodiments may also be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems.

[0042] The network 200 may include UEs 202, which may include any mobile or non-mobile computing device designed to communicate with the RAN 204 via an over-the-air connection. The UEs 202 may be, but are not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine type communication device, an M2M or D2D device, an IoT device, etc.

[0043] In an embodiment, the network 200 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0044] In an embodiment, the UE 202 can further communicate with the AP 206 via an over-the-air connection. The AP 206 can manage a WLAN connection, which can serve to offload some / all network traffic from the RAN 204. The connection between the UE 202 and the AP 206 can conform to any IEEE 802.11 protocol, and the AP 206 can be a Wireless Fidelity (Wi-Fi) router. In an embodiment, the UE 202, the RAN 204, and the AP 206 can utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation can also be configured by the RAN 204 for the UE 202 to utilize both cellular radio resources and WLAN resources.

[0045] The RAN 204 may include one or more access nodes, such as the access node (AN) 208. The AN 208 may terminate air interface protocols for the UE 202 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this manner, the AN 208 may enable data / voice connectivity between the core network (CN) 220 and the UE 202. In some embodiments, the AN 208 may be implemented as one or more software entities running on a separate device or on a server computer as part of a virtual network, which may be referred to as, for example, a CRAN or a virtual baseband unit pool. The AN 208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 208 may be a macrocell base station or a low power base station to provide a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0046] In embodiments where the RAN 204 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2 / Xn interface, which in one embodiment may be divided into a control / user interface, allows the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0047] Each of the ANs of the RAN 204 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 202 with an air interface for network access. The UE 202 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 204. For example, the UE 202 and the RAN 204 may use carrier aggregation to allow the UE 202 to connect with multiple component carriers, each corresponding to a Pcell or an Scell. In case of dual connectivity, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0048] The RAN 204 may provide an air interface via a licensed or unlicensed spectrum. To operate in the unlicensed spectrum, the node may use LAA, ELaA, and / or feLAA mechanisms based on carrier aggregation techniques with PCell / SCell. Before accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example, based on a listen-before-talk (LBT) protocol.

[0049] In the case of V2X, the UE 202 or AN 208 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE type RSU", an eNB may be referred to as an "eNB type RSU", a gNB may be referred to as a "gNB type RSU", etc. In one example, the RSU is a computing device coupled to radio frequency circuits located on the roadside that provide connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, and media, as well as applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications necessary for high speed events such as collision avoidance, traffic alerts, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0050] In an embodiment, the RAN 204 may be an LTE RAN 210 having an eNB, e.g., eNB 212. The LTE RAN 210 may provide an LTE air interface with the following characteristics: subcarrier spacing (SCS) of 15 kHz, CP-OFDM waveform for downlink (DL) and SC-FDMA waveform for uplink (UL), turbo codes for data, and TBCC for control. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for estimating the channel for cell search, initial acquisition, channel quality measurements, and coherent demodulation / detection at the UE. The LTE air interface may operate in sub-6 GHz bands.

[0051] In an embodiment, the RAN 204 may include, for example, a gNB having a gNB 216, or For example, the NG-RAN 214 may include ng-eNBs having an ng-eNB 218. The gNB 216 may connect to a 5G-capable UE using a 5G NR interface. The gNB 216 may connect to a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 218 may connect to a 5G core through the NG interface and to a UE via an LTE air interface. The gNB 216 and the ng-eNB 218 may connect to an Xn interface.

[0052] In one embodiment, the NG interface can be divided into two parts: an NG User Plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 214 and the UPF 248 (e.g., the N3 interface), and an NG Control Plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 214 and the AMF 244 (e.g., the N2 interface).

[0053] The NG-RAN 214 may provide the 5G-NR air interface with the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM, DFT-s-OFDM for UL, polar, repetitive, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS to track phase for PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate in the FR1 band, which includes the sub-6 GHz bands, or the FR2 band, which includes the bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include synchronization signals and physical broadcast channel (SS / PBCH) blocks (SSBs), which are areas of the downlink resource grid that contain PSS / SSS / PBCH.

[0054] In an embodiment, the 5G-NR air interface can utilize BWPs (bandwidth portions) for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For example, the UE 202 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 202, the SCS of the transmission is also changed. Another example use case of BWPs relates to power saving. In particular, multiple BWPs can be configured for the UE 202 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP that includes a smaller number of PRBs can be used for data transmission with a small traffic load while enabling power saving at the UE 202 and possibly at the gNB 216. A BWP that includes a larger number of PRBs can be used for scenarios with a higher traffic load.

[0055] The RAN 204 is communicatively connected to the CN 220, which includes network elements for providing various functions to customers / subscribers (e.g., users of UEs 202) for supporting data and telecommunication services. The components of the CN 220 may be implemented in one physical node or separate physical nodes. In an embodiment, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 220 onto physical computation / storage resources in servers, switches, etc. A logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice.

[0056] In one embodiment, the CN 220 may be connected to an LTE wireless network as part of an Enhanced Packet System (EPS) 222, sometimes referred to as the EPC (or Enhanced Packet Core). The EPC 222 may include an MME 224, an SGW 226, an SGSN 228, an HSS 230, a PGW 232, and a PCRF 234, connected together via interfaces (or "reference points") as shown. A brief description of the functionality of each component of the EPC 222 is as follows:

[0057] The MME 224 may implement mobility management functions to track the current location of the UE 202 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0058] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the EPC 222. The SGW 226 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other functions may include lawful interception, charging, and some policy enforcement.

[0059] The SGSN 228 may track the location of the UE 202 and perform security functions and access control. Furthermore, the SGSN 228 may perform EPC inter-node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME 224, MME selection for handover, etc. The S3 reference point between the MME 224 and the SGSN 228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0060] The HSS 230 may include a database for network users that includes subscription-related information to support network entity handling of communication sessions. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 230 and the MME 224 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 220.

[0061] The PGW 232 may terminate an SGi interface to a data network (DN) 236, which may include an application / content server 238. The PGW 232 may route data packets between the LTE CN 220 and the data network 236. The PGW 232 may be connected to the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 232 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 232 and the data network 236 may be an operator external public, private PDN, or an intra-operator packet data network, for example, to provide IMS services. The PGW 232 may be connected to the PCRF 234 via a Gx reference point.

[0062] The PCRF 234 is the policy and charging control element of the LTE CN 220. The PCRF 234 may be communicatively coupled to an app / content server 238 to determine appropriate QoS and charging parameters for a service flow. The PCRF 234 may provision the PCEF with the appropriate TFT and QCI along with the associated rules (over the Gx reference point).

[0063] In one embodiment, the CN 220 may be a 5GC 240. The 5GC 240 may include an AUSF 242, an AMF 244, an SMF 246, a UPF 248, an NSSF 250, an NEF 252, an NRF 254, a PCF 256, a UDM 258, and an AF 260, which are connected to each other via interfaces (or "reference points") as shown. A brief description of the function of each component of the 5GC 240 is as follows.

[0064] The AUSF 242 can store data and process authentication related functions for authenticating the UE 202. The AUSF 242 facilitates a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 240 via reference points as shown, the AUSF 242 can provide a Nausf service based interface.

[0065] The AMF 244 enables other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and subscribe to notifications about mobility events related to the UE 202. The AMF 244 may be responsible for registration management (e.g., for registering the UE 202), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. The AMF 244 may provide transport for SM messages between the UE 202 and the SMF 246. It may act as a transparent proxy for routing SM messages. The AMF 244 may also provide transport for SMS messages between the UE 202 and the SMSF. The AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Additionally, the AMF 244 may include or be the N2 reference point between the RAN 204 and the AMF 244, and may be the termination point of the RAN CP interface. The AMF 244 may be the termination point for NAS (N1) signaling and may perform NAS encryption and integrity protection, and may support NAS signaling with the UE 202 over the N3 IWF interface.

[0066] The SMF 246 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 248 and the AN 208), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in the UPF 248 to route traffic to the appropriate destination, termination of the interface to the policy control functions, control of policy enforcement, charging, and parts of QoS, lawful interception (for SM events and interface to the L1 system), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information sent over N2 to the AN 208 via the AMF 244, as well as determining the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.

[0067] The UPF 248 can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnecting to the data network 236, and a branching point for supporting multi-homed PDU sessions. The UPF 248 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), perform transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 248 can include an uplink classifier to support routing of traffic flows to the data network.

[0068] The NSSF 250 can select a set of network slice instances to serve the UE 202. The NSSF 250 can also determine the allowed NSSAIs and their mapping to subscribed S-NSSAIs, if necessary. The NSSF 250 can also determine the AMF set, or a list of candidate AMFs, to be used to serve the UE 202 based on a preferred configuration, possibly by querying the NRF 254. The selection of a set of network slice instances for the UE 202 is triggered by the AMF 244 to which the UE 202 is registered, by interacting with the NSSF 250, which can result in a change of AMF. The NSSF 250 can interact with the AMF 244 via the N22 reference point and communicate with another NSSF in a visited network via the N31 reference point (not shown). In addition, the NSSF 250 can indicate an Nnssf service-based interface.

[0069] The NEF 252 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF 260), edge computing systems or fog computing systems, etc., and in such embodiments, the NEF 252 can authenticate, authorize, or throttle the AF. The NEF 252 can also translate information exchanged with the AF 260 and with internal network functions. For example, the NEF 252 can translate between AF service identifiers and internal 5GC information. The NEF 252 can also receive information from other NFs based on the exposed capabilities of the other NFs. This information may be stored in the NEF 252 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 252 to other NFs and AFs, or used for other purposes, such as analytics. Additionally, the NEF 252 can present an Nnef service-based interface.

[0070] The NRF 254 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to the NF instances. The NRF 254 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate," "instance," and the like may refer to the creation of an instance, and an "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 254 may expose an Nnrf service-based interface.

[0071] The PCF 256 can provide policy rules to the control plane functions to enforce them and can also support a unified policy framework to manage network behavior. The PCF 256 can also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 258. In addition to communicating with functions through reference points as shown, the PCF 256 exhibits an Npcf service-based interface.

[0072] The UDM 258 can process subscription related information to support network entity processing of communication sessions and can store subscription data of the UE 202. For example, the subscription data can be communicated via the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 can include two parts: application front-end and UDR. The UDR can store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for publishing and application data for the NEF 252 (including PFD for application discovery, application request information for multiple UEs 202). The Nudr service-based interface can be indicated by the UDR to enable the UDM 258, the PCF 256, and the NEF 252 to access a particular set of stored data, as well as to read, update (e.g., add or modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM can include a UDM-FE responsible for credential processing, location management, subscription management, etc. Different front-ends can provide services to the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 258 can expose a Nudm service-based interface.

[0073] The AF 260 provides application influence over traffic routing, provides access to the NEF, and can interact with the policy framework for policy control.

[0074] In an embodiment, the 5GC 240 can enable edge computing by selecting an operator / third-party service to be geographically close to the point where the UE 202 attaches to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 240 can select a UPF 248 close to the UE 202 and perform traffic steering from the UPF 248 to the data network 236 over the N6 interface. This is obtained based on the UE subscription data, the UE location, and information provided by the AF 260. In this way, the AF 260 can influence the UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 260 is considered to be a trusted entity, the network operator can allow the AF 260 to directly interact with the associated NF. In addition, the AF 260 can exhibit a Naf service-based interface.

[0075] The data network 236 may represent, for example, various network operator services, Internet access, or third party services provided by one or more servers, including an application / content server 238 .

[0076] 3 illustrates a schematic of a wireless network 300 according to various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 may be similar to similarly named components described elsewhere herein and may be substantially interchangeable.

[0077] The UE 302 may be communicatively coupled to the AN 304 via a connection 306. The connection 306 is shown as an air interface for enabling a communication connection and may conform to a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at mm-wave or sub-6 GHz frequencies.

[0078] The UE 302 may include a host platform 308 coupled to a modem platform 310. The host platform 308 may include an application processing circuit 312 that may be coupled to a protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 may execute various applications for the UE 302 to source / sink application data. Additionally, the application processing circuit 312 may implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0079] The protocol processing circuitry 314 may implement one or more layer operations to facilitate transmission or reception of data over the connection 306. The layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0080] The modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations that are "lower" layer operations in a network protocol stack performed by the protocol processing circuitry 314. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, determination of received symbol / bit metrics, multi-antenna port precoding / decoding that may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0081] The modem platform 310 may further include transmit circuitry 318, receive circuitry 320, RF circuitry 322, and RF front end (RFFE) 324, which may include or be connected to one or more antenna panels 326. The selection and arrangement of components of the transmit circuitry 318, receive circuitry 320, RF circuitry 322, RFFE 324, and antenna panel 326 (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether the communication is TDM or FDM at mmWave or sub-6 GHz frequencies. In an embodiment, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc.

[0082] In an embodiment, the protocol processing circuitry 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0083] UE reception can be established by and through the antenna panel 326, the RFFE 324, the RF circuitry 322, the receive circuitry 320, the digital baseband circuitry 316, and the protocol processing circuitry 314. In one embodiment, the antenna panel 326 can receive transmissions from the AN 304 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 326.

[0084] UE transmissions may be established by and through protocol processing circuitry 314, digital baseband circuitry 316, transmit circuitry 318, RF circuitry 322, RFFE 324, and antenna panel 326. In one embodiment, the transmit components of the UE 302 may apply spatial filters to data to be transmitted in order to form transmit beams emitted by antenna elements of the antenna panel 326.

[0085] Similar to the UE 302, the AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled to a protocol processing circuit 334 of the modem platform 330. The modem platform may further include a digital baseband circuit 336, a transmit circuit 338, a receive circuit 340, an RF circuit 342, an RFFE circuit 344, and an antenna panel 346. The components of the AN 304 may be similar to and substantially interchangeable with similarly named components of the UE 302. In addition to performing data transmission / reception as described above, the components of the AN 304 may perform various logical functions including RNC functions such as radio bearer management, dynamic radio resource management for uplink and downlink, and data packet scheduling.

[0086] 4 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable medium) and performing any one or more of the methods described herein, according to an example embodiment. Specifically, FIG. 4 illustrates a schematic diagram of hardware resources 400 including one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry. In an embodiment in which node virtualization (e.g., NFV) is utilized, a hypervisor 402 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 400.

[0087] Processor 410 may include, for example, processors 412, 414. Processor 410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0088] The memory / storage device 420 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 420 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0089] The communications resources 430 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 404 or one or more databases 406 or other network elements over the network 408. For example, the communications resources 430 may include wired communications components (e.g., for coupling via USB, Ethernet), cellular communications components, NFC components, Bluetooth (or Bluetooth Low Energy) components, Wi-Fi components, and other communications components.

[0090] The instructions 450 may comprise software, programs, applications, applets, apps, or other executable code for causing the processor 410 to perform any one or more of the methods described herein. The instructions 450 may reside completely or partially within the processor 410 (e.g., in a cache memory of the processor), the memory / storage device 420, or any suitable combination thereof. Furthermore, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral device 404 or the database 406. Thus, the memory of the processor 410, the memory / storage device 420, the peripheral device 404, and the database 406 are examples of computer-readable and machine-readable media.

[0091] For one or more embodiments, at least one of the components outlined in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as outlined in the exemplary section below. For example, baseband circuitry associated with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. In another example, circuitry associated with a UE, base station, satellite, network element, etc. as described above in connection with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the exemplary section.

[0092] The term "application" may refer to a complete, deployable packaged environment for achieving a particular function in an operating environment. A term such as "AI / ML application" may be an application that includes an artificial intelligence (AI) / machine learning (ML) model and application-level description. In an embodiment, the AI / ML application may be used to configure or implement one or more of the disclosed aspects.

[0093] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models to perform a particular task without explicit instructions, relying instead on patterns and inference. An ML algorithm builds or infers a mathematical model(s) (e.g., referred to as an "ML model") based on sample data (e.g., referred to as "training data," "model training information," etc.) to make predictions or decisions without being explicitly programmed to perform such a task. In general, an ML algorithm is a computer program that learns from experience with respect to a task and a performance measure, and an ML model can be any object or data structure created after an ML algorithm is trained on one or more training data sets. After training, the ML model can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept than the term "ML model," these terms described herein can be used interchangeably in this disclosure.

[0094] The terms "machine learning model", "ML model", and the like may refer to ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that uses ML algorithms to address a particular use case during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, and the like), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), and the like), reinforcement learning (e.g., Q-learning, multi-armed blind learning, deep RL, and the like), neural networks, and the like. Depending on the implementation, a particular ML model may have many submodels as components, and the ML model may train all the submodels together. Also, ML models trained separately may be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, features, or functional entities specific to an ML-assisted solution, and an ML pipeline may include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or more data sources in actors. An "actor" is an entity that hosts an ML-assisted solution using the output of ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during inference mode (including both online learning and model execution, if applicable). The ML host informs actors about the output of the ML algorithm, and the actors decide on an action (an "action" is taken by an actor as a result of the output of an ML-assisted solution). The term "model inference information" refers to information used as input to an ML model to determine inferences; although data used to train an ML model and data used to determine inferences may overlap, "training data" and "inference data" refer to different concepts.

[0095] The 5G NR specification can support a diverse set of verticals and use cases, including enhanced Mobile Broadband (eMBB) and ultra-reliable low latency communications (URLLC) services. Support for Low Power Wide Area (LPWA) networks, as well as use cases for extremely low complexity / cost devices targeting ultra-coverage and ultra-long battery life, are expected to be served by MTC (category M UE) and NB-IoT (category NB UE) technologies. In some aspects, the disclosed techniques support a class of NR UEs having lower complexity and power consumption levels than Rel-15 NR UEs, and serve related use cases that require lower complexity, small device form factors, and relatively long battery life, such as industrial wireless sensor networks (IWSNs), a class of wearables, and video surveillance, to further facilitate a smooth transition from 3.5G and 4G technologies to 5G (NR) technologies for currently deployed bands.

[0096] In some aspects, a class of reduced capability (RedCap) NR UEs can be defined that can be served using the currently specified 5G NR framework with the necessary adaptations and extensions to limit device complexity and power consumption while minimizing any adverse impact on network resource utilization, system spectral efficiency, and operational efficiency.

[0097] For frequency division duplexing (FDD) bands, a further complexity reduction feature is support for half-duplex frequency division duplexing (HD-FDD) multiplexing, which allows duplexers to be replaced with switches, reducing costs as well as insertion loss due to the duplexers. However, HD-FDD UEs may not be able to simultaneously receive and transmit on downlink (DL) and uplink (UL) carriers. In this regard, the disclosed techniques may be used to address scenarios with time overlap between DL reception and UL transmission, even in FDD deployments (e.g., HD-FDD deployments). The disclosed techniques further present various options for enhancing system operation when considering support for HD-FDD in RedCap NR UEs and NR systems.

[0098] In one embodiment, in FDD operation, DL reception is performed on the DL carrier and UL transmission is performed on the paired UL carrier. HD-FDD UEs may not support simultaneous reception on the DL carrier and simultaneous transmission on the UL carrier. Thus, the gap between DL reception and UL transmission, i.e., the DL to UL switching time N DL-UL and the gap between UL reception and DL transmission, i.e., the UL to DL switching time N UL-DL Here, the timing is considered from the UE's perspective (i.e., taking into account the effect of the timing advance that takes into account the propagation delay between the gNB and the UE). DL-UL and N UL-DL can be separately predefined or configured by a higher layer. DL-UL and N UL-DL may be the same and may be predefined or configured by common higher layer signaling.

[0099] In an aspect, DL reception may overlap with UL transmission at the UE side according to higher layer configuration and / or dynamic scheduling by the gNB. Furthermore, the gap between DL reception and UL transmission may be smaller than the DL-UL or UL-DL switching time, which can be considered as a special case of overlap. In such a case, the HD-FDD UE can only receive or transmit at a time. In an aspect, a de-prioritized channel / signal is cancelled if any symbol of the de-prioritized channel / signal overlaps with any symbol of a prioritized channel / signal or a period before or after the prioritized channel / signal. In some aspects, all symbols of the de-prioritized channel / signal are erased. Alternatively, a subset of symbols of the de-prioritized channel / signal that overlaps with any symbol of the prioritized channel / signal or a period before or after the prioritized channel / signal is cancelled. In an aspect, the above period before and after the prioritized channel / signal can be determined by the DL-UL or UL-DL switching time at the UE side.

[0100] In an embodiment, the above-mentioned period before and after the prioritized channel / signal is quantized to an integer number of symbols. If the DL channel / signal has a different subcarrier spacing (SCS) than the UL channel / signal, the quantization is obtained based on a higher SCS between the DL channel / signal and the UL channel / signal. Alternatively, the quantization is obtained based on a lower SCS between the DL channel / signal and the UL channel / signal. Alternatively, the quantization can be based on the SCS of the prioritized channel / signal. Alternatively, the quantization can be based on the SCS of the de-prioritized channel / signal. Alternatively, the quantization is obtained based on a reference SCS that may be configured by higher layer signaling.

[0101] In an embodiment, the overlap between DL reception and UL transmission may be interpreted to include (i) both the overlap between DL channel / signal symbols and UL channel / signals and the overlap between the de-prioritized channel / signal and the above-mentioned period before and after the prioritized channel / signal, or (ii) only the overlap between DL channel / signal symbols and UL channel / signals. For DL ​​and UL channels / signals, the same prioritization rules apply to the two overlap cases in (i), including defined rules for prioritizing either DL or UL channels / signals, or up to the UE implementation for receiving DL or transmitting UL.

[0102] In an embodiment, if DL reception and UL transmission are not overlapped, but the gap between DL reception and UL transmission is smaller than the DL-UL or UL-DL switching time, i.e., in the case of non-overlapping UL / DL without sufficient gap, any combination of DL channel / signal and UL channel / signal may be allowed for scheduling or configuration if the corresponding overlap case between the two channels / signals in the combination is not an error case. Alternatively, the case of non-overlapping UL / DL without sufficient gap is allowed only for certain combinations of DL channel / signal and UL channel / signal. For example, both channels / signals in the allowed combination should be semi-statically configured, and at least one channel / signal is cell-specifically configured. The remaining combinations of DL channel / signal and UL channel / signal are considered as error cases. In particular, the allowed combinations may be 1) a valid RO and / or a valid MsgA PUSCH and a cell-specifically or dedicatedly configured DL channel / signal, and 2) a SS / PBCH block indicated by ssb-PositionsInBurst or ServingCellConfigCommon and in SIB1 and a dedicatedly configured UL channel / signal.

[0103] In an embodiment, in the case of non-overlapping UL / DL where there is not enough gap between a valid RO and / or a valid MsgA PUSCH and a cell-specific or dedicated configured DL, it is up to the UE implementation to cancel either DL reception or UL transmission to ensure sufficient switching time, which is the same process as in the case where a valid RO and / or a valid MsgA PUSCH overlaps with the DL. In an aspect, the cell-specific or dedicated configured DL can be PDCCH, PDSCH, CSI-RS, DL PRS, or SSB indicated by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0104] In one embodiment, if the HD-UE receives a PDCCH, PDSCH, CSI-RS, or DL ​​PRS based on configuration by higher layers, or is indicated by ssb-PositionsInBurst or ServingCellConfigCommon in in SIB1 that a SS / PBCH block exists, the HD-UE will transmit a PRACH or MsgA PUSCH starting at timing less than 1. N Rx-Tx Tc after the last symbol in the set of symbols, or N Tx - Rx Before the first symbol in a set of Tc symbols, the HD-UE may choose, based on its implementation, to transmit a PRACH or MsgA PUSCH or to receive a PDSCH, or CSI-RS, or PL RS, or PDCCH, or SS / PBCH block.

[0105] In an embodiment, if the HD-UE receives a PDCCH, PDSCH, CSI-RS, or DL ​​PRS based on configuration by higher layers, or the presence of an SS / PBCH block is indicated by a set of symbols by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1, the HD-UE will transmit a PRACH or MsgA PUSCH, where the first symbol of the PRACH or MsgA PUSCH is less than 1. N Rx-Tx Tc is the last symbol in the set of symbols or the last symbol of the PRACH or MsgA PUSCH is N Tx-Rx Before the first symbol in a set of Tc symbols, the HD-UE may choose, based on its implementation, to transmit a PRACH or MsgA PUSCH or to receive a PDSCH, or CSI-RS, or PL RS, or PDCCH, or SS / PBCH block.

[0106] In an embodiment, if the HD-UE receives a PDCCH, PDSCH, CSI-RS, or DL ​​PRS based on configuration by higher layers, or the presence of an SS / PBCH block is indicated by a set of symbols by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1, the HD-UE transmits a PRACH or MsgA PUSCH starting earlier than 1. Rx-Tx After the last symbol in said set of Tc symbols, or N Tx-Rx Before the first symbol in a set of Tc symbols, the HD-UE may choose, based on its implementation, to transmit a PRACH or MsgA PUSCH or to receive a PDSCH, or CSI-RS, or PL RS, or PDCCH, or SS / PBCH block.

[0107] In an embodiment, when the HD-UE receives a PDCCH, a PDSCH, a CSI-RS, or a DL PRS based on configuration by higher layers, or when the presence of an SS / PBCH block is indicated by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1, the HD-UE may receive at least N Rx-Tx Tc after the last symbol in the set of symbols, or at least without ending at N Tx-Rx Before the first symbol in a set of Tc symbols, the HD-UE may choose, based on its implementation, to transmit a PRACH or MsgA PUSCH or to receive a PDSCH, or CSI-RS, or PL RS, or PDCCH, or SS / PBCH block.

[0108] In an aspect, if the HD-UE receives a PDCCH, PDSCH, CSI-RS, or DL ​​PRS based on configuration by higher layers, or the presence of an SS / PBCH block is indicated in a set of symbols by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1, the HD-UE transmits a PRACH or MsgA PUSCH that starts or ends at an interval less than 1. N Rx-Tx Tc or N Tx-Rx After the last symbol or before the first symbol in the set of symbols, Tc respectively, the HD-UE may choose, based on its implementation, whether to transmit a PRACH or MsgA PUSCH or to receive a PDSCH, or CSI-RS, or PLRS, or PDCCH, or SS / PBCH block.

[0109] In an embodiment, when the HD-UE receives a PDCCH, a PDSCH, a CSI-RS, or a DL PRS based on configuration by higher layers, or the presence of an SS / PBCH block is indicated in a set of symbols by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1, the HD-UE may receive N Rx-Tx Tc or N Tx-Rx Transmit a PRACH or MsgA PUSCH that starts or ends in a symbol less than Tc. Based on its implementation, the HD-UE can choose to transmit a PRACH or MsgA PUSCH or receive a PDSCH or CSI-RS or PL RS or PDCCH or SS / PBCH block.

[0110] In an aspect, in case of non-overlapping UL / DL where there is not enough gap between SS / PBCH blocks indicated by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon and cell-specific or dedicated configured UL, SS / PBCH blocks are prioritized, which is the same as the prioritization rule when SS / PBCH blocks and UL overlap. The cell-specific or dedicated configured UL can be CG PUSCH, PUCCH, or SRS. In particular, when the UE transmits PUSCH, PUCCH, or SRS based on configuration by higher layers and the presence of SS / PBCH blocks is indicated to the UE by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, the following options can be applied:

[0111] In one option, when the last symbol of a PUSCH or PUCCH transmission is not later than the first symbol of an SS / PBCH block, the last symbol of the PUSCH or PUCCH transmission is preceded by N Tx-RxIf Tc is not present at all, or if the first symbol of a PUSCH or PUCCH transmission is not earlier than the last symbol of an SS / PBCH block, then the first symbol of the PUSCH or PUCCH transmission is not preceded by the last symbol of the SS / PBCH block. Rx-Tx If Tc is absent at all, the UE does not transmit PUSCH or PUCCH.

[0112] Another option is to specify that the last symbol of a PUSCH or PUCCH transmission is N before the first symbol of the SS / PBCH block. Tx-Rx If Tc is less than Tc, or the first symbol of a PUSCH or PUCCH transmission is N after the last symbol of the SS / PBCH block, Rx-Tx If it is less than Tc, the UE does not transmit PUSCH or PUCCH.

[0113] In one embodiment, a PUSCH or PUCCH transmission may occur N Tx-Rx If the transmission of PUSCH or PUCCH ends in less than Tc, or if the transmission of PUSCH or PUCCH ends in N Rx-Tx If the timing starts less than Tc, the UE does not transmit PUSCH or PUCCH.

[0114] In an aspect, the UE may transmit an SRS symbol N s before the first symbol of an SS / PBCH block when the SRS symbol is not later than the first symbol of the SS / PBCH block. Tx-Rx N symbols after the last symbol of the SS / PBCH block when Tc is not at all, or when the SRS symbol is not earlier than the last symbol of the SS / PBCH block Rx-Tx ·Do not transmit SRS in symbols where Tc is not even at most.

[0115] In an aspect, the UE may transmit N Tx-Rx Fewer than Tc symbols or N after the last symbol of the SS / PBCH blockRx-Tx ·Do not transmit SRS in fewer symbols than Tc.

[0116] In one embodiment of the present invention, for an SS / PBCH block indicated by ssb-PositionsInBurst in SIB1 or a cell-specific or dedicated configured UL in ServingCellConfigCommon, the SS / PBCH block is prioritized if it overlaps with the UL or if the SS / PBCH block and the UL do not overlap without a sufficient gap. In one aspect, the cell-specific or dedicated configured UL can be a CG PUSCH, PUCCH, or SRS. In particular, when the UE transmits a PUSCH, PUCCH, or SRS based on configuration by higher layers and the presence of an SS / PBCH block is indicated to the UE by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, the following options may apply:

[0117] In one embodiment, any symbol of a PUSCH or PUCCH transmission may be preceded by N symbols in the SS / PBCH block. Tx-Rx If Tc is less than Tc, or if any symbol of the PUSCH or PUCCH transmission is after any symbol of the SS / PBCH block, N Rx-Tx If it is less than Tc, the UE does not transmit PUSCH or PUCCH.

[0118] In one embodiment, any symbol of a PUSCH or PUCCH transmission is separated from any symbol of an SS / PBCH block by N Tx-Rx Tc or N Rx-Tx If it is less than Tc, the UE does not transmit PUSCH or PUCCH.

[0119] In one embodiment, the last symbol of a PUSCH or PUCCH transmission is preceded by NTx-Rx If Tc is not present at all, or if the first symbol of a PUSCH or PUCCH transmission is after the last symbol of the SS / PBCH block, N Rx-Tx If Tc is absent at all, the UE does not transmit PUSCH or PUCCH.

[0120] In an aspect, the UE may transmit N symbols before the first symbol of the SS / PBCH block when the last symbol of the SS / PBCH block is not earlier than the SRS symbol. Tx-Rx N symbols after the last symbol of the SS / PBCH block when Tc is not at all late or the last symbol of the SS / PBCH block is not later than the SRS symbol Rx-Tx ·Do not transmit SRS in symbols where Tc is not even at most.

[0121] In an aspect, the UE may receive N Tx-Rx After fewer than Tc symbols or any symbol of the SS / PBCH block, N Rx-Tx ·Do not transmit SRS in fewer symbols than Tc.

[0122] In an aspect, the UE may be located N away from any symbol in the SS / PBCH block. Tx-Rx Tc or N Rx-Tx ·Do not transmit SRS in fewer symbols than Tc.

[0123] In an aspect, the UE may receive N Tx-Rx A symbol with no Tc or N after the last symbol of the SS / PBCH block Rx-Tx ·Do not transmit SRS in symbols where Tc is not even at most.

[0124] Dynamically scheduled DL reception overlapping with configured UL transmission In certain aspects, dynamically scheduled DL reception may overlap with semi-statically configured UL transmission. Dynamically scheduled DL reception may include PDSCH or CSI-RS. Semi-statically configured UL transmission may include SRS, PUCCH, or CG PUSCH. In some aspects, this scheme may be applied to PRACH preamble transmission. In some aspects, a timeline may be defined to determine whether DL reception or UL transmission should occur at one time. Denote the start time of UL transmission as T0, and if DL reception is scheduled earlier than T0-Toffset, the UE may prioritize the scheduled DL reception. When multiple UL information are multiplexed and one UL channel is determined to carry the multiplexed UL information, T0 is the start time of the determined UL channel.

[0125] In an embodiment, Toffset may be equal to 1. As defined by T_(proc,2), where T_(proc,2) is assumed to be the PUSCH preparation time for the corresponding UE processing capability. d_2,1=1 and μ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configurations of the SRS, PUCCH, PUSCH, or μ_r corresponds to the SCS configuration of the PRACH if μ_r is 15 kHz or more, otherwise μ_r=0. In an embodiment, if the end symbol of the DL assignment is not later than T0-Toffset, the UE receives the entire DL reception. In some aspects, the UE may drop the UL transmission. Alternatively, if the UL transmission starts earlier than the DL reception at the UE, the UE may transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time.

[0126] In an embodiment, the UE does not expect to receive a DL assignment with an ending symbol later than T0-Toffset. Alternatively, if the ending symbol of the DL assignment is later than T0-Toffset, the UE may transmit the entire UL transmission and drop the entire DL reception. Alternatively, if the DL reception starts earlier than the UL transmission at the UE, the UE may receive the start symbol of the DL reception, drop the last symbol of the DL reception during the DL-UL switching time, and transmit the entire UL transmission.

[0127] 5 illustrates a diagram 500 of overlapping dynamic PDSCH and CG PUSCH, according to an aspect. In some aspects, it may be assumed that the DL assignment is received before T0-Toffset at the UE. Since the terminal has not started preparing for the CG PUSCH, it does not transmit the CG PUSCH and receives the scheduled PDSCH.

[0128] 6 illustrates a diagram 600 of overlapping dynamic PDSCH and CG PUSCH, according to an aspect. In some aspects, it may be assumed that the DL assignment is received after T0-Toffset at the UE. Since the UE has already started preparing for the CG PUSCH, the UE performs a CG PUSCH transmission and does not receive the scheduled PDSCH.

[0129] Dynamically scheduled UL transmission and overlapping dynamically scheduled DL reception In some aspects, dynamically scheduled DL reception may overlap with dynamically scheduled UL transmission. Dynamically scheduled DL reception may include PDSCH or CSI-RS. Dynamically scheduled UL transmission may include SRS, PUCCH, and PUSCH. This scheme may also be applied to PRACH preamble transmission triggered by PDCCH command. A timeline may be defined to determine whether DL reception or UL transmission should be performed at one time. If the start time of UL transmission is denoted as T0, and DL reception is scheduled earlier than T0-Toffset, the UE may prioritize the DL reception or UL transmission scheduled later. If multiple UL information are multiplexed and one UL channel is determined to carry the multiplexed UL information, T0 is the start time of the determined UL channel.

[0130] In some aspects, if the end symbol of the DL assignment is not later than T0-Toffset and if the DL assignment ends later than the UL grant, the UE receives the entire DL reception. In some embodiments, the UE may drop the UL transmission. Alternatively, if the UL transmission starts earlier than the DL reception at the UE, the UE may transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time. In some embodiments, if the end symbol of the DL assignment is not later than T0-Toffset and if the UL grant ends later than the DL assignment, the UE transmits the entire UL transmission. In some aspects, the UE may drop the entire DL reception. Alternatively, if the DL reception starts earlier than the UL transmission at the UE, the UE may receive the start symbol of the DL reception and drop the last symbol of the DL reception during the DL-UL switching time. In some embodiments, the UE does not expect the ending symbol of the DL assignment to be no later than T0-Toffset and the UL grant to end at the same symbol as the DL assignment. Alternatively, if the ending symbol of the DL assignment is no later than T0-Toffset and if the UL grant ends at the same symbol as the DL assignment, the UE may prioritize DL reception. Alternatively, the UE may prioritize UL transmission.

[0131] In an embodiment, the UE may not expect the end symbol of the DL assignment to be later than T0-Toffset. Alternatively, if the end symbol of the DL assignment is later than T0-Toffset, the UE may transmit the entire UL transmission and drop the entire DL reception. Alternatively, if the DL reception starts earlier than the UL transmission at the UE, the UE may receive the start symbol of the DL reception, drop the last symbol of the DL reception during the DL-UL switching time, and transmit the UL transmission.

[0132] 7 illustrates a diagram 700 of overlapping dynamic PDSCH and dynamic PUSCH in accordance with some aspects. In some aspects, the DL assignment is received before T0-Toffset and after the UL grant on the UE side. The UE can receive the entire PDSCH and drop the PUSCH.

[0133] 8 illustrates a diagram 800 of overlapping dynamic PDSCH and dynamic PUSCH in accordance with some aspects. In some aspects, the DL assignment is received before T0-Toffset but earlier than the UL grant on the UE side. In some aspects, the UE can transmit the entire PUSCH and drop the PDSCH.

[0134] FIG. 9 illustrates a diagram 900 of overlapping dynamic PDSCH and dynamic PUSCH, according to some aspects. In some aspects, DL assignment is received after T0-Toffset at the UE side. Since the UE has already started preparing for CG PUSCH, the UE transmits the entire PUSCH and drops the PDSCH. Dynamically scheduled UL transmission overlaps with semi-statically configured DL reception. In certain aspects, semi-statically configured DL reception may overlap with dynamically scheduled UL transmission. In some aspects, the semi-statically configured DL reception may include PDCCH, SPS PDSCH, or CSI-RS. In the case of SPS PDSCH, the first SPS occasion after reception of activation DCI is considered as a dynamically scheduled PDSCH, not a semi-statically configured DL reception occasion. In some embodiments, the dynamically scheduled UL transmission may include SRS (specifically, aperiodic SRS (A-SRS)), PUCCH, or PUSCH. This scheme can also be applied to PRACH preamble transmission triggered by a PDCCH command. In some embodiments, the PUCCH carrying HARQ-ACK feedback in response to a dynamically scheduled PDSCH and the PUCCH carrying SP CSI_feedback at the first opportunity after activation of semi-persistent CSI (SP CSI) feedback are considered as dynamically scheduled PUCCH.

[0135] In some embodiments, if a semi-statically configured DL reception overlaps with a dynamically scheduled UL transmission, the dynamically scheduled UL transmission may take precedence. The UE transmits the entire UL transmission. The UE may not be expected to receive a DL channel or signal. Alternatively, the UE does not receive a DL channel or signal. Alternatively, if the DL reception starts earlier than the UL transmission at the UE side, the UE may receive the start symbol of the DL reception and drop the last symbol of the DL reception for the DL-UL switching time. In a further example of this embodiment, if the canceled DL reception involves an SPS PDSCH that is not the first SPS occasion after activation, the UE is expected to send a negative acknowledgement (NACK) as part of the HARQ-ACK feedback in response to the SPS PDSCH. As another alternative, if the canceled DL reception involves an SPS PDSCH, the UE is expected not to report a HARQ-ACK feedback in response to the canceled SPS PDSCH occasion. As yet another alternative, if the canceled DL reception involves an SPS PDSCH, the UE is expected to not report HARQ-ACK feedback in response to the canceled SPS PDSCH opportunity only if the HARQ-ACK feedback is not multiplexed with any other UCI bits or another HARQ-ACK bit in the same HARQ-ACK codebook (CB).

[0136] In an embodiment, when a semi-statically configured DL reception overlaps with a dynamically scheduled UL transmission, different priorities can be assigned to different types of DL reception. In an aspect, the UE can receive the entire DL reception in case of a high priority DL reception. In some aspects, the UE can drop the UL transmission. Alternatively, when the UL transmission starts earlier than the DL reception at the UE side, the UE can transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the DL-UL switching time. In some aspects, the UE can transmit the entire UL transmission in case of a low priority DL reception. In some aspects, the UE can drop the entire DL reception. Alternatively, when the DL reception starts earlier than the UL transmission at the UE side, the UE can receive the start symbol of the DL reception and drop the last symbol of the DL reception during the UL-DL switching time.

[0137] In certain aspects, PDCCH monitoring may have a higher priority than other DL receptions. In another example, PDCCH monitoring for some or all common search space sets may have a higher priority than other DL receptions.

[0138] In certain aspects, when a semi-statically configured DL reception overlaps with a dynamically scheduled UL transmission, different priorities can be assigned to different types of DL reception and UL transmission. In some aspects, a relative priority between the priority of DL reception and the priority of UL transmission can be further defined or configured. In certain aspects, when a DL reception has a higher priority than a UL transmission, the UE can receive the entire DL reception. In some aspects, the UE can drop the UL transmission. Alternatively, when a UL transmission starts earlier than a DL reception at the UE side, the UE can transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time. In some embodiments, when a UL transmission has a higher priority than a DL reception, the UE can transmit the entire UL transmission. In some embodiments, the UE can drop the entire DL reception. Alternatively, when a DL reception starts earlier than a UL transmission at the UE side, the UE can receive the start symbol of the DL reception and drop the last symbol of the DL reception during the DL-UL switching time. On the other hand, in some embodiments, when a DL reception has the same priority as a UL transmission, the UE can prioritize a dynamically scheduled UL transmission. SSB overlaps with UL transmission.

[0139] In an embodiment, dynamically scheduled or semi-statically configured UL transmissions can overlap with SSBs. In an embodiment, the UE may or may not need to receive the SSBs at once. In some aspects, if the UE receives the SSB, the UE may drop the UL transmission. Alternatively, if the UL transmission starts earlier than the SSB at the UE side, the UE may transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time. In an embodiment, dynamically scheduled UL transmissions may include SRS (specifically, aperiodic SRS (A-SRS)), PUCCH, PUSCH, and PRACH preamble transmissions in a valid RO (see the following subsection for the definition of "valid RO") triggered by a PDCCH command. In some embodiments, semi-statically configured UL transmissions may include SRS (specifically, periodic SRS (P-SRS) or semi-persistent SRS), PUCCH, CG PUSCH (except for the first CG PUSCH occasion after receiving an activation DCI for a Type-2 CG PUSCH), and PRACH preamble transmissions in enabled ROs that are not responsive to a PDCCH command (see subsection below).

[0140] In an embodiment, the UE does not expect to be dynamically scheduled with an UL transmission that may overlap with one or more symbols of a slot indicated to the UE by ServingCellConfigCommon SIB1 or ssb-PositionsInBurst in ssbPositionsInBurst for reception of an SS / PBCH block. Alternatively, the UE may receive an SSB if the UE needs to receive an SSB and the UE does not transmit a UL transmission. On the other hand, if a semi-statically configured UL transmission overlaps with an SSB, the UE may receive an SSB if the UE needs to receive an SSB, and the UE may transmit a UL transmission if not. In a further example, if a CG PUSCH occasion, except for the first CG PUSCH occasion after receiving an activation DCI for a Type 2 CG PUSCH, overlaps with one or more symbols of a slot indicated to the UE by ServingCellConfigCommon SIB1 or ssb-PositionsInBurst in ssbPositionsInBurst for receiving an SS / PBCH block, the UE may transmit a CG PUSCH, but the UE does not expect any other UL transmission occasions that overlap with symbols indicated to the UE for receiving an SS / PBCH block. In some embodiments, the UE may always prioritize transmission of a CG PUSCH over reception of an SS / PBCH block. Alternatively, the UE may receive an SS / PBCH block if the UE needs to receive an SS / PBCH block, otherwise the UE may transmit a CG PUSCH. In another example, when configured with UL skipping for dynamically allowed (DG) PUSCH, the UE may expect that, in addition to CG PUSCH occasions, DG PUSCHs will overlap in one or more symbols of a slot indicated for SS / PBCH block reception, in which case the UE may or may not transmit PUSCH during the overlapping occasions.

[0141] In an embodiment, if a dynamically scheduled or semi-statically configured UL transmission overlaps with an SSB, the UE may receive the SSB if the UE needs to receive the SSB, otherwise the UE may transmit the UL transmission.

[0142] In an embodiment, if a dynamically scheduled or semi-statically configured UL transmission overlaps with an SSB, the UE may receive the SSB if the UE needs to receive the SSB, and the UE does not transmit the UL transmission.

[0143] In an embodiment, if a dynamically scheduled or semi-statically configured UL transmission overlaps with an SSB, the UE may transmit the UL transmission and not receive the SSB.

[0144] In certain aspects, if a dynamically scheduled UL transmission may overlap with an SSB, the UE may transmit a UL transmission and not receive the SSB. In some aspects, if a semi-statically configured UL transmission overlaps with an SSB, the UE may receive the SSB if the UE needs to receive it, and otherwise the UE may transmit a UL transmission.

[0145] In an embodiment, the type 0 / 0 A / 1 / 2 PDCCH common search space (CSS) sets are configured to schedule system information block 1 (SIB1), other system information, random access, and paging related transmissions, respectively. In some embodiments, the type 0 / 0 A / 1 / 2 CSS sets may overlap with dynamically scheduled or semi-statically configured UL transmissions. The above embodiments handling overlaps between SSBs and dynamically scheduled or semi-statically configured UL transmissions can be applied to monitoring opportunities (MOs) for the type 0 / 0 A / 1 / 2 PDCCH CSS sets. MOs for the type 0 / 0 A / 1 / 2 PDCCH CSS sets can be handled in the same or different manner as SSBs.

[0146] In an embodiment, a Type 1 PDCCH CSS set may be treated differently from a Type 0 / 0 A / 2 PDCCH CSS set to handle overlap with UL transmissions. In some aspects, the gNB may transmit a PDCCH in a Type 1 CSS set in response to a detected PRACH preamble for the UE. Thus, after transmitting a PRACH preamble, the UE may prioritize detection of a PDCCH in a Type 1 CSS set and an associated PDSCH scheduled by the PDCCH. For example, if a Type 1 CSS set overlaps with a dedicated configured UL transmission, the UE may prioritize detection of a PDCCH in a Type 1 CSS set. On the other hand, the UE may not expect to be configured with a Type 0 / 0 A / 2 PDCCH CSS set that overlaps with a dedicated configured UL transmission.

[0147] In an embodiment, the above distinction between Type 1 PDCCH CSS set and Type 0 / 0 A / 2 PDCCH CSS set may also be applied to handle overlaps between Type 0 / 0 A / 1 / 2 PDCCH CSS and dynamically scheduled UL transmissions. Alternatively, the same behavior may be applied to Type 0 / 0 A / 1 / 2 CSS set when overlapping with dynamically scheduled UL transmissions. For example, the transmission of the dynamically scheduled UL transmission is prioritized. PRACH opportunities and DL reception overlap.

[0148] In an embodiment, dynamically scheduled or semi-statically configured DL reception may overlap with PRACH Occasions (ROs). An RO may or may not be a valid RO. For non-RedCap UEs, all ROs are valid for paired spectrum or auxiliary UL (SUL) bands. In one embodiment, for HD-FDD UEs operating in paired spectrum, all ROs are valid. In this way, the RO validation rules for full-duplex FDD UEs and HD-FDD UEs are aligned. In another embodiment, for HD-FDD UEs operating in paired spectrum, a valid RO corresponds to an RO that is subject to the same constraints as for non-RedCap UEs operating in unpaired spectrum. Specifically, for paired spectrum: (a) If the UE is not provided with a semi-statically configured UL-DL pattern, then a PRACH occasion in a PRACH slot shall not precede an SS / PBCH block in the PRACH slot and shall not overlap with a set of consecutive symbols before the start of the next channel occupancy period (e.g., 3GPP TS 37.213) during which the UE does not transmit if channelAccessMode=semi-static is provided, and shall not precede an SS / PBCH block in the PRACH slot and shall not overlap with a set of consecutive symbols before the start of the next channel occupancy period (e.g., 3GPP TS 37.213) during which the UE does not transmit if channelAccessMode=semi-static is provided.

[0149] (a.1) Candidate SS / PBCH block indices for SS / PBCH blocks correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon as described in clause 4.1 of TS 38.213. (b) If the UE is provided with a semi-statically configured UL-DL pattern, the PRACH occasions in the PRACH slots are (b.1) Within the UL symbol; or (b.2) In a PRACH slot, the symbols after the last downlink symbol of at least N_gap and the symbols after the last SS / PBCH block symbol of at least N_gap are not preceding the SS / PBCH block and do not overlap with a set of consecutive symbols before the start of the next channel occupancy period without any transmission as described in TS 37.213 if channelAccessMode=semi-static is provided in Table 8.1-2.

[0150] (b.3) The candidate SS / PBCH block indices of the SS / PBCH blocks correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon as described in clause 4.1 of TS 38.213. In the following, "overlap with a valid RO" means an overlap in one or more of the symbols corresponding to a valid RO, or an overlap in Ngap symbols before a valid RO as described in clause 8.1 of TS 38.213, or an overlap in the above-mentioned period before and after a valid RO.

[0151] In certain aspects, the UE may or may not need to transmit a PRACH preamble in a valid RO depending on some other conditions. If the UE transmits a PRACH preamble in the RO, the UE may drop the DL reception. Alternatively, if the DL reception starts earlier than the RO at the UE side, the UE may receive the start symbol of the DL reception and drop the last symbol of the DL reception for the DL-UL switching time. Dynamically scheduled DL reception may include PDSCH or aperiodic CSI-RS. Semi-statically configured DL reception may include PDCCH, SPS PDSCH, or periodic or semi-persistent (SP) CSI-RS.

[0152] In an embodiment, the UE may not expect to be scheduled with a dynamically scheduled DL reception that overlaps with a valid RO. Alternatively, the UE may transmit a PRACH preamble in the RO if the UE needs to transmit a PRACH preamble and the UE does not receive the DL reception. In some embodiments, if a semi-statically configured DL reception overlaps with a RO, the UE may transmit a PRACH preamble in the RO if the UE needs to transmit a PRACH preamble, otherwise the UE may receive the DL reception.

[0153] In an aspect, if a dynamically scheduled or semi-statically configured DL reception overlaps with a valid RO, the UE may transmit a PRACH preamble in the RO if it needs to; otherwise, the UE may receive DL reception.

[0154] In one embodiment of the present invention, if a dynamically scheduled or semi-statically configured DL reception overlaps with a valid RO, the UE may transmit a PRACH preamble when the UE needs to transmit a PRACH preamble and the UE does not receive the DL reception.

[0155] In an embodiment, if a dynamically scheduled or semi-statically configured DL reception overlaps with a valid RO, the UE may receive the DL reception and skip the PRACH preamble transmission.

[0156] In an embodiment, if a dynamically scheduled DL reception may overlap with a valid RO, the UE may receive the DL reception and skip the PRACH preamble transmission if the timeline for canceling the PRACH transmission is met. In some aspects, if a semi-statically configured DL reception overlaps with a RO, the process may be up to the UE implementation. In some embodiments, the UE may transmit a PRACH preamble in the RO if the UE needs to transmit a PRACH preamble, otherwise the UE may receive a DL reception. Alternatively, the UE may transmit a PRACH preamble in the RO if the UE needs to transmit a PRACH preamble and the UE does not receive a DL reception. Alternatively, the UE does not expect the configured DL reception to overlap with a valid RO.

[0157] In an aspect, if a dynamically scheduled DL reception may overlap with a valid RO, the UE may receive the DL reception and skip the PRACH preamble transmission if the timeline for canceling the PRACH transmission is met. Otherwise, the UE needs to transmit a PRACH preamble, and if the UE does not receive a dynamically scheduled DL reception, the UE can transmit the PRACH preamble in the RO. In another embodiment of the present invention, a UE may not receive a DL channel or signal if it may overlap with a valid RO in one or more symbols of a slot.

[0158] In another embodiment, the prioritization of valid RO or configured DL reception may depend on the type of configured DL reception. Different types include dedicated configured DL reception, configured type 0 / 0 A / 1 / 2 CSS set, and SSB. The method of handling overlap between valid RO and the above three types of configured DL reception may be the same or different.

[0159] In an embodiment, the above embodiment may also be applied to MsgA PRACH and PUSCH for two-step RACH. In one embodiment, for HD-FDD UEs operating in paired spectrum, MsgA PUSCH occasions are valid if they do not overlap in time and frequency with any valid PRACH occasions associated with either Type 1 or Type 2 random access procedures. In another embodiment, for HD-FDD UEs operating in paired spectrum, in addition to not overlapping with any valid PRACH occasions, validation of MsgA PUSCH occasions may be further subject to the same constraints as for non-RedCap UEs, i.e., operation in unpaired spectrum for SS / PBCH blocks with indexes provided by ssb-PositionsInBurst or ServingCellConfigCommon in SIB1. (a) If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PUSCH occasion is (a.1) Not preceding SS / PBCH block in PUSCH slot (a.2) At least N gap Symbol N after the last SS / PBCH block symbol gap is provided in Table 8.1-2 and does not overlap with the set of consecutive symbols before the start of the next channel occupancy period (e.g., 3GPP TS 37.213) during which the UE does not transmit, if channelAccessMode=Semi-Static is provided.

[0160] (b) If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PUSCH occasion is (b.1) Within the UL symbol; or (b.2) Not preceding SS / PBCH block in PUSCH slot (b.3) At least N gap The symbol after the last downlink symbol and at least Ngap Symbol N after the last SS / PBCH block symbol gap is provided in Table 8.1-2 and does not overlap with the set of consecutive symbols before the start of the next channel occupancy period (e.g., 3 GPP TS 37.213) during which the UE does not transmit, if channelAccessMode=Semi-Static is provided.

[0161] In an embodiment, the same prioritization rules for overlap processing may be applied to the MsgA PRACH and the MsgA PUSCH. Alternatively, the prioritization rules for the MsgA PRACH and the MsgA PUSCH may be different.

[0162] In an embodiment, the prioritization of the MsgA PUSCH and the dynamically scheduled or configured DL reception may depend on the transmission status of the MsgA PRACH associated with the MsgA PUSCH. If the configured MsgA PUSCH overlaps with the dynamically scheduled or configured DL reception, and if the MsgA PUSCH is not transmitted because the associated MsgA PRACH is not transmitted, the dynamically scheduled or configured DL reception is received at the UE. On the other hand, if the MsgA PRACH is transmitted, the MsgA PUSCH is prioritized. Alternatively, if the MsgA PRACH is to be transmitted, the transmission of the MsgA PUSCH follows other prioritization rules that handle the overlap between the MsgA PUSCH and the dynamically scheduled or configured DL reception.

[0163] In an aspect, when a dynamically scheduled DL reception overlaps with MsgA PUSCH, the UE may receive the DL reception and skip MsgA PUSCH transmission if the timeline for canceling MsgA PUSCH transmission is met. For example, if the start time of MsgA PUSCH is T0 and DL reception is scheduled by PDCCH that ends by T0-Toffset, the UE may prioritize the scheduled DL reception and cancel MsgA PUSCH transmission. For example, Toffset may be T_(proc,2), which is defined in NR as the minimum time to cancel uplink transmission. Otherwise, the UE may still transmit MsgA PUSCH.

[0164] In an aspect, if a semi-statically configured DL reception overlaps with a MsgA PUSCH, the UE may be expected to cancel the MsgA PUSCH and receive the configured DL reception.

[0165] In an embodiment, if a semi-statically configured DL reception overlaps with a MsgA PUSCH, the process may be up to the UE implementation. That is, if the UE needs to transmit a MsgA PUSCH, the UE may transmit a MsgA PUSCH, otherwise the UE may receive a DL reception. In some aspects, if the UE needs to transmit a MsgA PUSCH and the UE does not receive a DL reception, the UE may transmit a MsgA PUSCH. In yet another alternative, the UE does not expect the DL reception to be configured to overlap with a MsgA PUSCH, that is, such an overlap is considered an error case.

[0166] In an embodiment, the prioritization of the MsgA PRACH or the dynamically scheduled or configured DL reception may depend on the availability of the transmission of the MsgA PUSCH. If the MsgA PUSCH cannot be transmitted due to overlap with a dynamically scheduled or configured DL reception, the UE skips the transmission of the MsgA PRACH. Otherwise, the UE may transmit the MsgA PRACH followed by the MsgA PUSCH. In another embodiment of the invention, if the MsgA PRACH is transmitted and the MsgA PUSCH cannot be transmitted due to overlap with a dynamically scheduled or configured DL reception, the UE returns to the four-step RACH procedure. The semi-statically configured UL transmission and the semi-statically configured DL reception overlap.

[0167] In an embodiment, semi-statically configured DL reception may overlap with semi-statically configured UL transmission. In some embodiments, semi-statically configured DL reception may include PDCCH, SPS PDSCH, or CSI-RS. In an aspect, semi-statically configured UL transmission may include SRS, PUCCH, CG PUSCH, and PRACH preamble transmission in a valid RO or MsgA PUSCH.

[0168] In certain aspects, HD-FDD UEs may not be expected to be semi-statically configured with transmit and receive occasions that may overlap in one or more symbols of a slot.

[0169] In an embodiment, if a semi-statically configured DL reception overlaps with a semi-statically configured UL transmission, the UL transmission may be prioritized. In some embodiments, the UE transmits the entire UL transmission. In some embodiments, the UE may drop the entire DL reception. In some embodiments, if the DL reception starts earlier than the UL transmission at the UE, the UE may receive the start symbol of the DL reception and drop the last symbol of the DL reception during the DL-UL switching time. In a further example, the UL transmission may be prioritized only if the semi-static DL reception opportunity corresponds to a PDCCH monitoring opportunity.

[0170] In an embodiment, if a semi-statically configured DL reception overlaps with a semi-statically configured UL transmission, the DL reception may be prioritized. In some embodiments, the UE receives the entire DL reception. In some embodiments, the UE may drop the entire UL transmission. In some embodiments, if the UL transmission starts earlier than the DL reception at the UE, the UE may transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time.

[0171] In an embodiment, prioritization rules between DL reception opportunities and UL transmission opportunities that may overlap in one or more symbols of a slot are configured in the HD-FDD UE via higher layer signaling. In a further example, such configuration and prioritization rules may be defined for overlaps with one or more of the following UL transmission occasions: CG PUSCH occasions or Scheduling Request (SR) occasions. In some aspects, such configuration and prioritization rules may be defined for overlaps with one or more of the following DL reception occasions: PDCCH monitoring occasions (MOs) or DL ​​SPS occasions.

[0172] In one embodiment of the present invention, different priorities can be assigned to different types of DL receptions when semi-statically configured DL receptions overlap with semi-statically configured UL transmissions. In some aspects, the UE can receive the entire DL reception in case of high priority DL reception. In some aspects, the UE can drop the UL transmission. Alternatively, if the UL transmission starts earlier than the DL reception at the UE side, the UE can transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time. In some aspects, the UE can transmit the entire UL transmission in case of low priority DL reception. In some aspects, the UE can drop the entire DL reception. Alternatively, if the DL reception starts earlier than the UL transmission at the UE side, the UE can receive the start symbol of the DL reception and drop the last symbol of the DL reception during the DL-UL switching time.

[0173] In certain aspects, PDCCH monitoring may have a higher priority than other DL receptions. In another example, PDCCH monitoring for some or all common search space sets may have a higher priority than other DL receptions.

[0174] In certain aspects, when a semi-statically configured DL reception overlaps with a semi-statically configured UL transmission, different priorities may be assigned to different types of DL reception and UL transmission. In some embodiments, the relative priority between the priority of DL reception and the priority of UL transmission may be further defined or configured. In some aspects, when a DL reception has a higher priority than a UL transmission, the UE may receive the entire DL reception. In some embodiments, the UE may drop the UL transmission. Alternatively, when a UL transmission starts earlier than a DL reception at the UE side, the UE may transmit the start symbol of the UL transmission and drop the last symbol of the UL transmission during the UL-DL switching time. In some embodiments, when a UL transmission has a higher priority than a DL reception, the UE may transmit the entire UL transmission. In some embodiments, the UE may drop the entire DL reception. Alternatively, when a DL reception starts earlier than a UL transmission at the UE side, the UE may receive the start symbol of the DL reception and drop the last symbol of the DL reception during the DL-UL switching time. In some aspects, when a DL reception has the same priority as a UL transmission, a rule may be defined to prioritize DL reception or UL transmission. For example, the DL reception or UL transmission that starts first is given priority, or the DL reception or UL transmission that starts later is given priority.

[0175] NR supports dynamic slot format indication (SFI) via DCI format 2_0. In some aspects, if DL reception is configured in a symbol in a slot and the symbol is not indicated as a DL symbol by the dynamic SFI, the DL reception is canceled in the slot. If UL transmission is configured in a symbol in a slot and the symbol is not indicated as a UL symbol by the dynamic SFI, the UL transmission is canceled in the slot. In some embodiments, when DL reception and UL transmission overlap, the above embodiment that handles the overlap between DL reception and UL transmission is performed first. In some aspects, the selected channel(s) is received or transmitted only if it does not conflict with an SFI in DCI format 2_0. For example, if the selected channel in a symbol is a configured DL reception, but the symbol is not indicated as a DL symbol by the SFI, the selected channel is canceled. However, if the selected channel in a symbol is a configured UL transmission, the symbol is not indicated as a UL symbol by the SFI, and the selected channel is canceled.

[0176] In an embodiment, the SFI is checked first, which may cancel the configured DL reception or the configured UL transmission. Then, the UE only performs overlap processing for the remaining DL reception and / or UL transmission. If there is an overlap between the remaining DL reception and the remaining UL transmission, the above embodiment dealing with the overlap between the DL reception and the UL transmission may be performed. In one example, if a dynamically scheduled DL reception overlaps with a configured UL transmission, the UL transmission may be canceled by the SFI check, even if the first symbol of the UL transmission is T_(proc,2) relative to the last symbol of the PDCCH that schedules the DL reception. As a result, the UE may receive the scheduled DL reception.

[0177] In an embodiment, when a dedicated configured DL reception overlaps with a dedicated configured UL transmission, if one of the DL reception or UL transmission is canceled by checking the SFI, the UE can process the remaining UL transmission or DL ​​reception. Thus, in an embodiment, when a dedicated configured DL reception overlaps with a dedicated configured UL transmission occasion, if the UE detects a dynamic SFI via DCI format 2_0 that cancels one of the higher layer configured occasions (DL or UL, respectively) starting at least from the first overlapping symbol, it can process (transmit or receive, respectively) the other. However, if it does not detect DCI 2_0, the UE cancels both the DL and UL occasions at least in the overlapping symbols. Furthermore, the UE does not expect to receive a dynamic SFI indicating codepoint 0 in DCI 2_255 for one or more (semi-static flexible) symbols where the dedicated DL and UL configurations may overlap. Alternatively, if the UE receives a dynamic SFI indicating codepoint 255 in DCI 2_0 for one or more (semi-static flexible) symbols where a dedicated DL configuration and a UL configuration may overlap, the UE shall erase both DL and UL occasions, at least in the overlapping symbols, subject to the last symbol of the CORESET carrying DCI 2_0 occurring at least Tproc,2 before the earliest erasure time for a UL transmission occasion.

[0178] In an embodiment, application of the SFI in DCI format 2_0 may be subject to a timeline check. For example, the UE may not expect to cancel the transmission of a PUCCH or PUSCH or PRACH in a symbol set if the first symbol in the set occurs in the symbol set. T_(proc,2) is relative to the last symbol of the CORESET in which the UE detects DCI format 2_0.

[0179] The disclosed techniques may use one or more of the following example aspects: In some embodiments, a wireless communication method and system is disclosed for supporting half-duplex frequency domain multiplexing (HD-FDD) user equipment (UE). In some aspects, if a dynamically scheduled DL reception overlaps with a semi-statically configured UL transmission, the UE prioritizes the scheduled DL reception if the DL reception is scheduled earlier than T0-Toffset, where T0 is the start time of the UL transmission.

[0180] In an embodiment, if the UE does not expect to receive a DL assignment with an ending symbol that is later than T0-Toffset, or if the ending symbol of the DL assignment is later than T0-Toffset, the UE prioritizes UL transmission.

[0181] In an embodiment, when a dynamically scheduled DL reception overlaps with a dynamically scheduled UL transmission, a timeline is defined to determine whether the DL reception or the UL transmission should occur at one time.

[0182] In an embodiment, when a semi-statically configured DL reception overlaps with a dynamically scheduled UL transmission, the dynamically scheduled UL transmission is prioritized, or different priorities are assigned to different types of DL reception, or different priorities are assigned to different types of DL reception and UL transmission.

[0183] In one embodiment, if a semi-statically configured UL transmission overlaps with an SS / PBCH block, the UE receives the SS / PBCH block if the UE needs to receive the SS / PBCH block, and otherwise the UE transmits the UL transmission.

[0184] In an embodiment, the semi-statically configured UL transmission includes only CG PUSCH transmission. In some embodiments, the UE does not expect to be dynamically scheduled with a UL transmission that overlaps with one or more symbols of the SS / PBCH block. In some embodiments, if a dynamically scheduled UL transmission overlaps with an SS / PBCH block, the UE transmits a UL transmission. In some embodiments, the Type 1 PDCCH CSS set is treated differently than the Type 0 / 0 A / 2 PDCCH CSS set to handle overlaps with UL transmissions. In some aspects, for HD-FDD UEs operating in paired spectrum, all ROs are valid or RO validation depends on the configuration of the SS / PBCH block. In some embodiments, if a semi-statically configured DL reception overlaps with a valid RO, the UE transmits a PRACH preamble in the RO if it needs to transmit a PRACH preamble, otherwise the UE receives a DL reception. In some aspects, the UE does not expect to be scheduled with a dynamically scheduled DL reception that overlaps with a valid RO. In some aspects, if a dynamically scheduled DL reception overlaps with a valid RO, the UE receives the DL reception and skips the PRACH preamble transmission. In some embodiments, for HD-FDD UEs operating in paired spectrum, an MsgA PUSCH occasion is valid if it does not overlap in time and frequency with any valid RO. In some embodiments, the RO validation depends on the configuration of the SS / PBCH block. In some aspects, the prioritization of the MsgA PUSCH and the overlapping dynamically scheduled or configured DL reception depends on the transmission status of the MsgA PRACH associated with the MsgA PUSCH.

[0185] In an aspect, if a dynamically scheduled DL reception overlaps with a MsgA PUSCH, the UE receives the DL reception and skips the MsgA PUSCH transmission if the timeline for canceling the MsgA PUSCH transmission is met. In some embodiments, if a semi-statically configured DL reception overlaps with a MsgA PUSCH, the UE is expected to cancel the MsgA PUSCH and receive the configured DL reception. In some embodiments, if a semi-statically configured DL reception overlaps with a semi-statically configured UL transmission, the UL transmission is prioritized, or the DL reception is prioritized, or different priorities are assigned to different types of DL reception, or different priorities are assigned to different types of DL reception and UL transmission.

[0186] In certain aspects, when semi-statically configured DL reception overlaps with semi-statically configured UL transmission, prioritization rules between overlapping DL reception and UL transmission opportunities in one or more symbols of a slot are configured in the HD-FDD UE via higher layer signaling. In some embodiments, HD-FDD UEs are not expected to be semi-statically configured with overlapping transmission and reception occasions in one or more symbols of a slot. In some embodiments, overlap between DL reception and UL transmission includes both overlap between symbols of two channels / signals and overlap between one channel / signal and the above-mentioned period before and after the prioritized channel / signal.

[0187] In an embodiment, for DL ​​and UL channels / signals, the same prioritization rules are applied for the two overlapping cases, including defined rules for prioritizing either DL or UL channels / signals, or up to UE implementation for receiving DL or transmitting UL. In some aspects, if both channels / signals are semi-statically configured and at least one channel / signal is cell-specifically configured, scheduling or configuration is allowed in case of overlap between one channel / signal and the above-mentioned period before and after the other channel / signal. In some aspects, a de-prioritized channel / signal is canceled if any symbol of the de-prioritized channel / signal overlaps with any symbol of a prioritized channel / signal or with a period before or after the prioritized channel / signal.

[0188] 10 illustrates a block diagram of a communications device, such as an evolved Node B (eNB), new generation Node B (gNB) (or another RAN node or base station), a transmit / receive point (TRP), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), according to some aspects. In alternative aspects, the communications device 1000 may operate as a standalone device or may be connected (e.g., networked) to other communications devices.

[0189] A circuit (e.g., processing circuit) is a collection of circuits implemented in a tangible entity of device 1000 that includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership may be flexible over time. A circuit includes components that, when operational, can perform specified operations alone or in combination. In one example, the hardware of a circuit may be invariably designed (e.g., hardwired) to perform a particular operation. In one example, the hardware of a circuit may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include a machine-readable medium that is physically modified (e.g., magnetically, electrically, a movable arrangement of invariant assembled particles, etc.) to encode instructions for a particular operation.

[0190] In connecting the physical components, the underlying electrical properties of the hardware components are changed, for example, from an insulator to a conductor or vice versa. The instructions allow the embedded hardware (e.g., an execution unit or a loading mechanism) to create members of a circuit within the hardware through the variable connections to perform some of the specific operations during operation. Thus, in one example, the machine-readable medium element is part of a circuit or is communicatively coupled to other components of a circuit when the device is operating. In one example, any of the physical components can be used in two or more components of two or more circuits. For example, during operation, an execution unit can be used in a first circuit of a first circuit at one time and reused by a second circuit of the first circuit or by a third circuit of the second circuit at a different time. Additional examples of these components with respect to device 1000 are provided below.

[0191] In an aspect, the device 1000 may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked arrangement, the communication device 1000 may operate as a server communication device, a client communication device, or both in a server-client network environment. In one example, the communication device 1000 may operate as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. The communication device 1000 may be a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web appliance, network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by the communication device. Furthermore, although only a single communication device is shown, the term "communication device" shall also be construed to include any collection of communication devices that individually or collectively execute a set (or sets) of instructions to perform any one or more of the methods described herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

[0192] An example may include or operate on logic or some components, modules, or mechanisms as described herein. A module is a tangible entity (e.g., hardware) capable of performing specified operations and may be configured or arranged in a particular manner. In one example, a circuit may be arranged (e.g., internally or with respect to an external entity such as other circuits) in a specified manner as a module. In one example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured as modules that operate to perform operations specified by firmware or software (e.g., instructions, application parts, or applications). In one example, the software may reside on a communication device readable medium. In one example, the software, when executed by the module's underlying hardware, causes the hardware to perform the specified operations. Thus, the term "module" is understood to encompass a tangible entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., temporarily) configured (e.g., programmed) to operate in a specified manner or to perform some or all of any operations described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any given moment. For example, if the modules include a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, the software may configure the hardware processor, for example, to configure a particular module at one time and a different module at a different time.

[0193] A communications device (e.g., a UE) 1000 may include a hardware processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1004, a static memory 1006, and a storage device 1007 (e.g., a hard drive, a tape drive, flash storage, or other block or storage device), some or all of which may communicate with each other via an interlink (e.g., a bus) 1008.

[0194] The communication device 1000 may further include a display device 1010, an alphanumeric input device 1012 (e.g., a keyboard), and a user interface (UI) navigation device 1014 (e.g., a mouse). In one example, the display device 1010, the input device 1012, and the UI navigation device 1014 may be touch screen displays. The communication device 1000 may further include a signal generating device 1018 (e.g., a speaker), a network interface device 1020, and one or more sensors 1021, such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 1000 may include an output controller 1028, such as a serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0195] The storage device 1007 may include a communication device-readable medium 1022 on which one or more sets of data structures or instructions 1024 (e.g., software) are stored that embody or are utilized by any one or more of the techniques or functions described herein. In some aspects, the processor 1002, the main memory 1004, the static memory 1006, and / or the registers of the storage device 1007 may be or include (completely or at least partially) the device-readable medium 1022 on which one or more sets of data structures or instructions 1024 that embody or are utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of the hardware processor 1002, the main memory 1004, the static memory 1006, or the mass storage device 1016 may constitute the device-readable medium 1022.

[0196] As used herein, the term "device readable medium" is interchangeable with "computer readable medium" or "machine readable medium." Although the communication device readable medium 1022 is shown as a single medium, the term "communication device readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 1024. The term "communication device readable medium" includes the term "machine readable medium" or "computer readable medium" and may include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 1024) for execution by the communication device 1000, causing the communication device 1000 to perform any one or more of the techniques of this disclosure, or capable of storing, encoding, or carrying data structures used by or related to such instructions. Non-limiting examples of communication device readable media may include solid-state memory and optical and magnetic media. Specific examples of communication device readable media may include non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM)) and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, random access memory (RAM), and CD-ROM and DVD-ROM disks.

[0197] In one example, the communication device readable medium may include a non-transitory communication device readable medium.

[0198] In some examples, the communication device readable medium may include a communication device readable medium that is not a transitory propagating signal.

[0199] The instructions 1024 may further be transmitted or received over a communications network 1026 using a transmission medium via the network interface device 1020 utilizing any one of a number of transport protocols. In one example, the network interface device 1020 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the communications network 1026. In one example, the network interface device 1020 may include multiple antennas for wirelessly communicating using at least one single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) technique. In some examples, the network interface device 1020 may communicate wirelessly using multiple user MIMO techniques.

[0200] The term "transmission medium" shall be construed to include any intangible medium capable of storing, encoding, or carrying instructions for execution by communication device 1000, including digital or analog communication signals or another intangible medium for facilitating communication of such software. In this regard, transmission media in the context of this disclosure are device-readable media.

[0201] The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure. These terms are defined to include both machine storage media and transmission media. Thus, these terms include both storage devices / media and carrier waves / modulated data signals. The described implementations of the subject matter may include one or more features, either alone or in combination, such as those illustrated below by way of example.

[0202] Example 1 is an apparatus for a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) and beyond wireless network, comprising: a processing circuit, for configuring the UE for communication using half-duplex frequency division duplex (HD-FDD) multiplexing in the 5G NR and beyond wireless network, the processing circuit comprising: receiving downlink control information (DCI) received via a physical downlink control channel (PDCCH); detecting an overlap of the DCI between a dynamically scheduled downlink (DL) reception on a physical downlink shared channel (PDSCH) and a semi-statically configured uplink (UL) transmission on a physical uplink shared channel (PUSCH); determining to perform one of the dynamically scheduled DL reception or the semi-statically configured UL transmission based on a start time (T0) and a pre-configured offset time (Toffset) of the semi-statically configured UL transmission; and a memory coupled to the processing circuit and configured to store the start time and the pre-configured offset time. In Example 2, the subject matter of Example 1 includes the subject matter where the processing circuitry is configured to determine to perform the dynamically scheduled DL reception if the dynamically scheduled DL reception is scheduled earlier than (T0-Toffset).

[0203] In Example 3, the subject matter of Examples 1-2 includes the subject matter that the processing circuitry is configured to determine to perform the semi-statically configured UL transmission when the end symbol of the dynamically scheduled DL reception is later than (T0-Toffset).

[0204] In Example 4, the subject matter of Examples 1-3 includes the subject matter where the processing circuitry is configured to detect a second overlap between the dynamically scheduled UL transmission and reception of a synchronization signal / physical broadcast channel (SS / PBCH) block and determine to prioritize performance of the dynamically scheduled UL transmission over reception of the SS / PBCH block.

[0205] In Example 5, the subject matter of Examples 1-4 includes the subject matter where the processing circuitry is configured to detect a second overlap between the semi-statically configured DL reception and the dynamically scheduled UL transmission on the PUSCH and determine to prioritize the dynamically scheduled UL transmission over the semi-statically configured DL reception.

[0206] In Example 6, the subject matter of Examples 1-5 includes the subject matter where the processing circuitry is configured to detect a second overlap between the dynamically scheduled DL reception and the dynamically scheduled UL transmission.

[0207] In Example 7, the subject matter of Example 6 includes the subject matter where the processing circuitry is configured to determine to perform one of the dynamically scheduled DL reception or the dynamically scheduled UL transmission based on a start time T0 of the dynamically scheduled UL transmission and a preconfigured offset time.

[0208] In Example 8, the subject matter of Examples 1-7 includes the subject matter where the UE is configured for operation in a paired spectrum and the processing circuitry is configured to determine that a Message A (MsgA) PUSCH occasion is valid if the Message A (MsgA) PUSCH occasion does not overlap in time and frequency with a valid Random Access Channel (RACH) occasion (RO).

[0209] In Example 9, the subject matter of Example 8 includes the subject matter where the processing circuitry is configured to perform validation of the RO based on a configuration of the synchronization signal / physical broadcast channel (SS / PBCH) block.

[0210] In Example 10, the subject matter of Examples 1-9 includes a transceiver circuit coupled to the processing circuit, and two or more antennas coupled to the transceiver circuit.

[0211] Example 11 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions causing the UE to perform operations of: configuring the UE for communication using half-duplex frequency division duplexing (HD-FDD) multiplexing in fifth generation new radio (5G NR) and beyond wireless networks; decoding downlink control information (DCI) received via a physical downlink control channel (PDCCH), the DCI indicating a dynamically scheduled downlink (DL) reception on a physical downlink shared channel (PDSCH); detecting an overlap between the dynamically scheduled DL reception and a semi-statically configured uplink (UL) transmission on a physical uplink shared channel (PUSCH); and determining to perform one of the dynamically scheduled DL reception or the semi-statically configured UL transmission based on a start time (T0) and a pre-configured offset time (Toffset) of the semi-statically configured UL transmission.

[0212] In Example 12, the subject matter of Example 11 includes an operation further comprising determining to perform dynamically scheduled DL reception if the dynamically scheduled DL reception is scheduled earlier than (T0-Toffset).

[0213] In Example 13, the subject matter of Examples 11-12 includes that the operations further include determining to perform the semi-statically configured UL transmission if an end symbol of the dynamically scheduled DL reception is later than (T0-Toffset).

[0214] In Example 14, the subject matter of Examples 11-13 includes the operations further including detecting a second overlap between the dynamically scheduled UL transmission and reception of a synchronization signal / physical broadcast channel (SS / PBCH) block, and determining to prioritize performance of the dynamically scheduled UL transmission over reception of the SS / PBCH block.

[0215] In Example 15, the subject matter of Examples 11-14 includes the operations further including detecting a second overlap between a semi-statically configured DL reception and a dynamically scheduled UL transmission on the PUSCH, and determining to prioritize the dynamically scheduled UL transmission over the semi-statically configured DL reception.

[0216] In Example 16, the subject matter of Examples 1-15 includes where the operations further include detecting a second overlap between the dynamically scheduled DL reception and the dynamically scheduled UL transmission.

[0217] In Example 17, the subject matter of Example 16 includes the operation further comprising determining to perform one of the dynamically scheduled DL reception or the dynamically scheduled UL transmission based on a start time T0 of the dynamically scheduled UL transmission and a preset offset time.

[0218] In Example 18, the subject matter of Examples 11-17 includes the subject matter where the UE is configured for operation in a paired spectrum, and the operations further include determining that the Message A (MsgA) PUSCH occasion is valid if the Message A (MsgA) PUSCH occasion does not overlap in time and frequency with a valid Random Access Channel (RACH) occasion (RO).

[0219] In Example 19, the subject matter of Example 18 includes where the operations further include performing validation of the RO based on a configuration of a synchronization signal / physical broadcast channel (SS / PBCH) block.

[0220] Example 20 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for communication using fifth generation new radio (5G NR) and half-duplex frequency division duplex (HD-FDD) multiplexing over a wireless network, the instructions including: decoding downlink control information (DCI) received over a physical downlink control channel (PDCCH), the DCI indicating a dynamically scheduled downlink (DL) reception on a physical downlink shared channel (PDSCH); detecting an overlap between the dynamically scheduled DL reception and a dynamically scheduled uplink (UL) transmission; and determining to perform one of the dynamically scheduled DL reception or the dynamically scheduled UL transmission based on a start time (T0) of the dynamically scheduled UL transmission and a preconfigured offset time. Example 21 is at least one machine-readable medium including instructions that, when executed by a processing circuit, cause the processing circuit to perform operations that implement any of Examples 1-20.

[0221] Example 22 is an apparatus comprising means for implementing any of Examples 1-20.

[0222] Example 23 is a system that implements any of Examples 1-20.

[0223] Example 24 is a method of practicing any of Examples 1-20.

[0224] Although the embodiments have been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings should be regarded in an illustrative and not a restrictive sense. Accordingly, this detailed description should not be construed in a restrictive sense, and the scope of the various embodiments is defined solely by the appended claims, together with the full scope of equivalents to which such claims are entitled.

Claims

1. 1. A user equipment (UE) device configured for half-duplex (HD) operation in a fifth generation new radio (5G NR) network, comprising: A processing circuit for configuring the UE device for the HD operation in the 5G NR network, Decoding higher layer signaling that configures a physical uplink shared channel (PUSCH) transmission in a symbol set; Decoding a downlink control information (DCI) format configuring a physical downlink shared channel (PDSCH) reception in a symbol subset of the set of symbols; a processing circuit for determining to prioritize the PUSCH transmission or the PDSCH reception based on a comparison between a preconfigured offset and a time offset between a first symbol of the symbol set and a last symbol of the DCI format; a memory coupled to the processing circuit and configured to store the higher layer signaling and the DCI format.

2. The apparatus of claim 1, wherein the preconfigured offset is a UE PUSCH preparation time (Tproc, 2).

3. The method of claim 2, wherein the processing circuit prioritizes the PUSCH transmission based on the time offset being less than or equal to the UE PUSCH preparation time.

3. The apparatus of claim 2.

4. The apparatus of claim 3, wherein the processing circuit prioritizes the PDSCH reception and cancels the PUSCH transmission based on the time offset being greater than the UE PUSCH preparation time.

5. The device described in any one of claims 1 to 4, wherein the upper layer signaling configures a second PDSCH reception in the symbol set, the DCI format configures a second PUSH transmission in at least one symbol of the symbol set, and the processing circuit determines to prioritize the second PUSH transmission over the second PDSCH reception.

6. The processing circuitry includes: Detecting overlap between dynamically scheduled uplink transmissions and reception of a synchronization signal / physical broadcast channel (SS / PBCH) block; determining to prioritize execution of the dynamically scheduled uplink transmission over reception of the SS / PBCH block; 5. Apparatus according to any one of claims 1 to 4.

7. The processing circuitry includes: Detecting overlap between semi-statically configured downlink reception and dynamically scheduled uplink transmission in a PUSCH; determining to prioritize the dynamically scheduled uplink transmission over the semi-statically configured downlink reception; 5. Apparatus according to any one of claims 1 to 4.

8. The processing circuitry includes: Detecting overlap between dynamically scheduled downlink reception and dynamically scheduled uplink transmission; 5. The apparatus of claim 1 , further comprising: a first receiving unit configured to receive a first transmission from a first receiving node and a second receiving node, the first receiving node being configured to receive a first transmission from a first receiving node and a second ...

9. The UE device configured to operate in a paired spectrum, 2. The apparatus of claim 1, wherein the processing circuitry determines that a Message A (MsgA) PUSCH occasion is valid if the Message A (MsgA) PUSCH occasion does not overlap in time and frequency with a valid Random Access Channel (RACH) occasion (RO).

10. a transceiver circuit coupled to the processing circuit; and two or more antennas coupled to the transceiver circuitry.

2. The apparatus of claim 1.

11. 1. A computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), comprising: The instructions configure the UE and cause the UE to perform operations for half-duplex (HD) operation in a fifth generation new radio (5G NR) network; The operation includes: Decoding higher layer signaling for transmission to a user equipment (UE), the higher layer signaling configuring a physical uplink shared channel (PUSCH) transmission in a symbol set; decoding a downlink control information (DCI) format for transmission to the UE, the DCI format configuring a physical downlink shared channel (PDSCH) reception in a subset of symbols of the set of symbols; determining to prioritize the PUSCH transmission or the PDSCH reception based on a comparison between a preconfigured offset and a time offset between a first symbol of the symbol set and a last symbol of the DCI format. A computer readable storage medium.

12. The computer-readable storage medium of claim 11, wherein the preconfigured offset is a UE PUSCH preparation time (Tproc, 2).

13. The operation comprises: prioritizing the PUSCH transmission based on the time offset being less than or equal to the UE PUSCH preparation time.

13. The computer-readable storage medium of claim 12.

14. The computer-readable storage medium of claim 13, wherein the operation prioritizes the PDSCH reception and cancels the PUSCH transmission based on the time offset being greater than the UE PUSCH preparation time.

15. A computer-readable storage medium as described in any one of claims 11 to 14, wherein the upper layer signaling configures a second PDSCH reception in the symbol set, the DCI format configures a second PUSH transmission in at least one symbol of the symbol set, and the operation includes determining to prioritize the second PUSH transmission over the second PDSCH reception.

16. The operation includes: Detecting overlap between dynamically scheduled uplink transmissions and reception of a synchronization signal / physical broadcast channel (SS / PBCH) block; determining to prioritize execution of the dynamically scheduled uplink transmission over reception of the SS / PBCH block.

15. A computer readable storage medium according to any one of claims 11 to 14.

17. The operation includes: Detecting overlap between semi-statically configured downlink reception and dynamically scheduled uplink transmission in a PUSCH; 15. The computer-readable storage medium of claim 11, further comprising: determining to prioritize the dynamically scheduled uplink transmission over the semi-statically configured downlink reception.

18. The operation includes: Detecting overlap between dynamically scheduled downlink reception and dynamically scheduled uplink transmission; determining to perform one of the dynamically scheduled downlink reception or the dynamically scheduled uplink transmission based on a start time of the dynamically scheduled uplink transmission and the preconfigured offset; 15. A computer readable storage medium according to any one of claims 11 to 14, comprising:

19. A user equipment (UE) device configured for half-duplex (HD) operation in a fifth generation new radio (5G NR) network, comprising: means for decoding higher layer signaling configuring a Physical Uplink Shared Channel (PUSCH) transmission in a set of symbols; means for decoding a downlink control information (DCI) format for configuring a physical downlink shared channel (PDSCH) reception in a subset of symbols of the set of symbols; and means for determining to prioritize the PUSCH transmission or the PDSCH reception based on a comparison between a preconfigured offset and a time offset between a first symbol of the symbol set and a last symbol of the DCI format.

20. The apparatus of claim 19, wherein the preconfigured offset is a UE PUSCH preparation time (Tproc, 2).

Images