configured grant transmission rules

Abstract

Network equipment (e.g., User Equipment (UE), New Radio NB (gNB), or other network components) can process or generate configured authorized transmissions based on logical channels. A selection of at least one of uplink (UL) or supplementary UL (SUL) can be configured to perform the CG transmission on the uplink channel based on the selected CG and a conformance test for interfering or conflicting transmissions used to determine the CG transmission.

Description

Technical Field

[0001] This disclosure relates to wireless technologies, and more specifically to rules for configured authorization. Background Technology

[0002] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communication platforms. The next generation of wireless communication systems, 5G or New Radio (NR), will provide a wide range of users and applications with access to information and data sharing anytime, anywhere. NR promises to be a unified network / system designed to meet diverse and sometimes conflicting performance dimensions and services. These diverse, multidimensional needs are driven by different services and applications. Generally, NR will evolve based on 3GPP LTE-Advanced, with the potential addition of New Radio Access Technologies (RATs), thereby enriching people's lives with better, simpler, and seamless wireless connectivity solutions. NR will enable everything to connect wirelessly, providing fast, rich content and services. Attached Figure Description

[0003] Figure 1 This is an exemplary block diagram illustrating an example of a user equipment (UE) and a next-generation node B (gNB) or access node in a network having network components that can be used in conjunction with the various aspects described herein.

[0004] Figure 2 This is another exemplary block diagram illustrating a system that can be employed at a UE or gNB according to the various aspects described herein.

[0005] Figure 3 This is an exemplary simplified block diagram of a UE wireless communication device or other network device / component (e.g., gNB) according to the various aspects described.

[0006] Figure 4 This is an exemplary simplified block diagram of different time slot configurations for CG emission based on the aforementioned aspects.

[0007] Figure 5 This is an exemplary priority chart for conformance testing of CG launch based on the various aspects described.

[0008] Figure 6 This is an example of interference with other channels or signals caused by overlapping of the transmission with the shared channel configured by the CG, according to the various aspects described above.

[0009] Figure 7 This is an example of available overlap information that can be considered in conformance testing for CG launch, based on the aforementioned aspects.

[0010] Figure 8This is another example of the available information that can be considered in conformance testing for CG launch, based on the aforementioned aspects.

[0011] Figure 9 This is an example of an interruption time that can be incorporated into the conformity test for CG launch, based on the various aspects described above.

[0012] Figure 10 This is another example of an interruption time that can be incorporated into conformance testing for CG launch, based on the aforementioned aspects.

[0013] Figure 11 This is another example of an interruption time that can be incorporated into conformance testing for CG launch, based on the aforementioned aspects.

[0014] Figure 12 This is an example of power ramp-up / ramp-down times that can be incorporated into conformance testing for CG launches, based on the aforementioned aspects.

[0015] Figure 13 These are exemplary processing flows that can be employed at network devices used for communication in accordance with the various aspects discussed herein. Detailed Implementation

[0016] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0017] This disclosure will now be described with reference to the accompanying drawings, wherein similar reference numerals throughout are used to denote similar elements, and the structures and devices shown therein are not necessarily drawn to scale. As used herein, the terms “component,” “system,” “interface,” etc., are intended to refer to computer-related entities, hardware, software (e.g., in execution), and / or firmware. For example, a component can be a processor (e.g., a microprocessor, controller, or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer, and / or user equipment with processing devices (e.g., a mobile phone, etc.). By way of example, an application running on a server and a server can also be components. One or more components may reside in a process, and components may be located on a single computer and / or distributed across two or more computers. This document may describe a set of elements or other sets of components, wherein the term “set” can be interpreted as “one or more.”

[0018] Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored, such as by utilizing modules, for example. Components can communicate via local and / or remote processes, for example, based on signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or throughout a network, such as the Internet, a local area network, a wide area network, or similar networks with other systems via signals).

[0019] For example, a component can be a device with a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry can be operated by a software application or firmware application executed by one or more processors. The one or more processors can be internal or external to the device and can execute at least a portion of the software or firmware application. As another example, a component can be a device that provides a specific function through an electronic component without a mechanical component; the electronic component may include one or more processors to execute software and / or firmware that at least partially endows the electronic component with that function.

[0020] The use of the term “exemplary” is intended to present the concept in a specific manner. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise stated or clearly apparent from the context, “X adopts A or B” is intended to mean any natural inclusive arrangement. That is, “X adopts A or B” is satisfied if X adopts A; X adopts B; or X adopts both A and B. Additionally, the articles “a” and “an” used in this application and the appended claims should generally be interpreted as meaning “one or more” unless otherwise stated or clearly apparent from the context to refer to the singular form. Furthermore, to the extent that the terms “comprising,” “including,” “having,” “having,” “with,” or variations thereof are used in the Detailed Description and Claims, such terms are intended to be included in a manner similar to the term “comprising.” Furthermore, in the context of discussing one or more numbered items (e.g., “first X,” “second X,” etc.), generally, the one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0021] As used herein, the term "circuit" may refer to, be part of, or may include: an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), or associated memory (shared, dedicated, or grouped) operatively coupled to the circuit, which executes one or more software or firmware programs, combinational logic circuits, or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic components that are at least partially operable in hardware.

[0022] The implementation schemes described herein can be implemented into systems or network devices using any appropriately configured hardware and / or software. Figure 1 The architecture of system 100 of a network according to some implementation schemes is shown. System 100 is shown as including UE 101a and UE 101b, which may further represent new radio (NR) devices (e.g., UE or gNB) as discussed herein.

[0023] Figure 1 Exemplary architectures of system 100 for networks according to various implementations are illustrated. The following description is provided for an exemplary system 100 operating in combination with LTE system standards provided by 2GPP technical specifications and 5G or NR system standards. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 2GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0024] like Figure 1As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine electronic control unit (ECU), electronic / engine electronic control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, etc.

[0025] In some implementations, any of UEs 101 can be an IoT UE, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a Public Land Mobile Network (PLMN), Proximity Service (ProSe), or Device-to-Device (D2D) communication, sensor network, or IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0026] UE 101 can be configured to connect to (e.g., communicatively coupled to) a radio access network (RAN) 110. In implementations, RAN 110 can be a next-generation (NG) RAN or a 5G RAN, an evolved-UMTS terrestrial RAN (E-UTRAN), or a legacy RAN such as a UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN," etc., can refer to RAN 110 operating in an LTE or 4G system 100. UE 101 utilizes connections (or channels) 102 and 104, each connection including a physical communication interface or layer (discussed in further detail below).

[0027] In this example, connections 102 and 104 are shown as air interfaces for communication coupling and are compatible with cellular communication protocols such as the Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) network protocols, Push-to-Talk (PTT) protocols, Cellular PTT (POC) protocols, Universal Mobile Telecommunications System (UMTS) protocols, 2GPP LTE protocols, 5G protocols, NR protocols, and / or any other communication protocols discussed herein. In an implementation, UE 101 can directly exchange communication data via ProSe interface 105. ProSe interface 105 may also be referred to as SL interface 105 and may include one or more logical channels, including but not limited to the Physical Side Link Control Channel (PSCCH), Physical Side Link Shared Channel (PSSCH), Physical Side Link Discovery Channel (PSDCH), and Physical Side Link Broadcast Channel (PSBCH).

[0028] The diagram shows UE 101b configured to access AP 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN terminal 106", "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 106 will include Wireless Fibre. Router. In this example, AP106 is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 101b, RAN 110, and AP 106 can be configured to utilize LTE-WLAN aggregation (LWA) operation and / or LTE / WLAN radio-level operation integrated with IPsec tunneling (LWIP). LWA operation may involve RAN nodes 111a-111b configuring UE 101b, which is in the Radio Resource Control (RRC_CONNECTED) state, to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) transmitted through connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0029] RAN 110 includes one or more access nodes (ANs) or RAN nodes 111a and 111b (collectively referred to as "RAN node 111") that enable connections between 102 and 104. As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, node B, RSU, transmit / receive point (TRxP), or TRP, etc., and can include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 111 (e.g., gNB) operating in NR or 5G system 100, while the terms "E-UT RAN node," etc., can refer to RAN node 111 (e.g., eNB) operating in LTE or 4G system 100. According to various implementation schemes, RAN node 111 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low power (LP) base stations, which are used to provide femtocell base stations, picocell base stations or other similar cells with smaller coverage area, smaller user capacity or higher bandwidth compared to macro cells.

[0030] In some implementations, all or part of the multiple RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a Centralized RAN (CRAN) and / or a Virtual Baseband Unit Pool (vBBUP). In these implementations, the CRAN or vBBUP may implement RAN function partitioning such as Packet Data Convergence Protocol (PDCP) partitioning, where the Radio Resource Control (RRC) and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by the individual RAN nodes 111; Media Access Control (MAC) / Physical (PHY) layer partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by the individual RAN nodes 111; or a “lower PHY” partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by the CRAN / vBBUP, and the lower portion of the PHY layer is operated by the individual RAN nodes 111. This virtualization framework allows the idle processor cores of the multiple RAN nodes 111 to execute other virtualized applications. In some implementations, a single RAN node 111 may represent a gNB distributed unit (DU) connected to the gNB central unit (CU) via a respective F1 interface. In these implementations, the gNB-DU may include one or more remote radio headers or RF front-end modules (RFEMs) (not shown), and the gNB-CU may be operated by a server (not shown) located in RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more of the plurality of RAN nodes 111 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to UE 101 and is connected to 5GC via an NG interface.

[0031] In a V2X scenario, one or more nodes in RAN Node 111 can be an RSU or act as an RSU. The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU", an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU", and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to a passing vehicle UE 101 (vUE 101). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz DSRC band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0032] Any node in RAN 111 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 101. In some implementations, any node in RAN 111 can perform various logical functions of RAN 110, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0033] In the implementation, UE 101 may be configured to communicate with each other or with any of the RAN nodes 111 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals, according to various communication technologies such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0034] In some implementations, the downlink resource grid can be used for downlink transmissions from any node in RAN 111 to UE 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0035] According to various implementations, UE 101 and RAN node 111 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 2.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0036] To operate in unlicensed spectrum, UE 101 and RAN node 111 may use Licensed Assisted Access (LAA), eLAA, and / or feLAA mechanisms. In these specific implementations, UE 101 and RAN node 111 may perform one or more known media sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Media / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0037] LBT is a mechanism that equipment (e.g., UE 101, RAN node 111, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when that medium is sensed to be idle (or when a specific channel in that medium is sensed to be unoccupied). Medium sensing operations may include Clear Channel Assessment (CCA), which utilizes at least Energy Detection (ED) to determine the presence of other signals on the channel in order to determine whether the channel is occupied or cleared. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in a intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0038] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, if more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increments exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for downlink (DL) or uplink (UL) transmission bursts (including Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) transmissions) can have a variable-length LAA contention window between X-extended CCA (ECCA) slots and Y-extended CCA (ECCA) slots, where X and Y are the minimum and maximum values ​​of the LAA contention window size (CWS). In one example, the minimum CWS for LAA transmissions can be 9 microseconds (μs); however, the size of the CWS and the maximum channel occupancy time (MCOT) (e.g., transmission burst) can be based on government regulatory requirements.

[0039] The LAA mechanism is built upon carrier aggregation (CA) technology in LTE-Advanced systems. In CA, each aggregated carrier is called a component carrier (CC). A CC can have a bandwidth of 1.4MHz, 2MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and up to approximately five or more CCs can be aggregated, thus the maximum aggregated bandwidth can be, for example, approximately 100MHz. In Frequency Division Duplex (FDD) systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs may have different bandwidths than the other CCs. In Time Division Duplex (TDD) systems, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0040] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides the primary component carrier (PCC) for both UL and DL and handles Radio Resource Control (RRC) and Non-Access Plane (NAS) related activities. Other serving cells are called SCells, and each SCell provides a single secondary component carrier (SCC) for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, thus indicating different PUSCH start positions within the same subframe.

[0041] The PDSCH carries user data and higher-layer signaling to multiple UEs 101. The Physical Downlink Control Channel (PDCCH) carries information such as transmission format and resource allocation related to the PDSCH channel. It also informs UEs 101 about transmission format, resource allocation, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UEs 101b within the cell) can be performed at any RAN node of RAN node 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each UE in UEs 101.

[0042] The PDCCH uses Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8) can exist.

[0043] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit the EPDCCH. Similarly, each ECCE may correspond to a set of nine with four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0044] RAN nodes 111 can be configured to communicate with each other via interface 112. In an implementation where system 100 is an LTE system, interface 112 can be an X2 interface 112. This X2 interface can be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the evolved packet core (EPC) or core network 120, and / or between two eNBs connected to the EPC 120. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U provides flow control mechanisms for user packets transmitted through the X2 interface and can be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from the primary eNB (MeNB) to the secondary eNB (SeNB); information about the successful in-order delivery of PDCP Packet Data Units (PDUs) from the SeNB to UE 101 for user data; information about PDCP PDUs not delivered to UE 101; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. X2-C can provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0045] In implementations where system 100 is a 5G or NR system, interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to 5GC 120, between a RAN node 111 (e.g., a gNB) connected to 5GC 120 and an eNB, and / or between two eNBs connected to 5GC 120. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 101 in connected modes (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected modes between one or more RAN nodes 111. This mobility support may include context transfer from the old (source) serving RAN node 111 to the new (destination) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (destination) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer and a user plane GPRS Tunneling Protocol (GTP-U) layer on top of the User Datagram Protocol (UDP) and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of the Flow Control Transport Protocol (SCTP). SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0046] RAN 110 is shown communicatively coupled to the core network—in this embodiment, communicatively coupled to the core network (CN) 120. CN 120 may include a plurality of network elements 122 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. Components of CN 120 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network subslice. Network Function Virtualization (NFV) architectures and infrastructure may be used to virtualize one or more network functions onto a physical resource comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally performed by proprietary hardware). In other words, NFV systems can be used to execute virtual or reconfigurable concrete implementations of one or more Evolution Packet Core (EPC) components / functions.

[0047] Generally, application server 130 may be an element that provides IP bearer resources for use with the core network (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). Application server 130 may also be configured to support one or more communication services for UE 101 via EPC 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0048] In the implementation, CN 120 can be a 5GC (referred to as "5GC 120", etc.), and RAN 110 can be connected to CN 120 via NG interface 112. In the implementation, NG interface 112 can be divided into two parts: a Next Generation (NG) User Plane (NG-U) interface 114, which carries traffic data between RAN node 111 and the User Plane Function (UPF); and an S1 Control Plane (NG-C) interface 115, which is the signaling interface between RAN node 111 and the Access and Mobility Management Function (AMF). The core network CN 120 can also be a 5GC 120.

[0049] In one implementation, CN 120 may be a 5G CN (referred to as "5GC 120", etc.), while in other implementations, CN 120 may be an EPC. When CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 may be connected to CN 120 via S1 interface 112. In one implementation, S1 interface 112 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and S-GW; and an S1-MME interface 115, which is the signaling interface between RAN node 111 and MME.

[0050] Figure 2 Exemplary components of device 200 according to some embodiments are shown. In some embodiments, device 200 may include at least application circuitry 202, baseband circuitry 204, radio frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 coupled together as shown. Components of the illustrated device 200 may be included in a UE or RAN node, such as UE 101 / 102 or eNB / gNB 111 / 112. In some embodiments, device 200 may include fewer elements (e.g., the RAN node may not utilize application circuitry 202, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 200 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the following components may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0051] Application circuitry 202 may include one or more application processors. For example, application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 200. In some embodiments, the processor of application circuitry 202 may process IP data packets received from the EPC.

[0052] Baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 206 and generate baseband signals for the transmit signal path of RF circuitry 206. Baseband processing circuitry 204 may interact with application circuitry 202 to generate and process baseband signals and control the operation of RF circuitry 206. For example, in some embodiments, baseband circuitry 204 may include a third-generation (3G) baseband processor 204A, a fourth-generation (4G) baseband processor 204B, a fifth-generation (5G) baseband processor 204C, or other existing, under development, or future generations of baseband processors 204D (e.g., second-generation (2G), sixth-generation (6G), etc.). Baseband circuitry 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions that can communicate with one or more radio networks via RF circuitry 206. In other embodiments, some or all of the functions of the baseband processors 204A-D may be included in modules stored in the memory 204G and executed via the central processing unit (CPU) 204E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 204 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Implementations of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

[0053] Additionally, the memory 204G (and other memory components discussed herein, such as memory, data storage devices, etc.) may include one or more machine-readable media, including instructions that, when executed by the machine or components described herein, cause the machine to perform actions of a method, apparatus, or system for concurrent communication using various communication technologies according to the embodiments and examples described herein. It should be understood that the aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium (e.g., the memory or other storage device described herein). Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media or computer-readable storage devices may be any available medium accessible by a general-purpose or special-purpose computer. By way of example only and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or other tangible and / or non-transitory media that can be used to carry or store desired information or executable instructions. Furthermore, any connection may also be referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media.

[0054] In some embodiments, the baseband circuitry 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all components of the baseband circuitry 204 and the application circuitry 202 may be implemented together, such as (e.g.) on a system-on-a-chip (SoC).

[0055] In some implementations, baseband circuit 204 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 204 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 204 is configured to support radio communication using more than one radio protocol can be referred to as multi-mode baseband circuits.

[0056] RF circuit 206 can communicate with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuit 206 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 206 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 208 and providing a baseband signal to baseband circuit 204. RF circuit 206 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 204 and providing an RF output signal to FEM circuit 208 for transmission.

[0057] In some embodiments, the receive signal path of RF circuit 206 may include mixer circuit 206a, amplifier circuit 206b, and filter circuit 206c. In some embodiments, the transmit signal path of RF circuit 206 may include filter circuit 206c and mixer circuit 206a. RF circuit 206 may also include synthesizer circuit 206d for synthesizing the frequency used by mixer circuit 206a in both the receive and transmit signal paths. In some embodiments, mixer circuit 206a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 208 based on the synthesized frequency provided by synthesizer circuit 206d. Amplifier circuit 206b may be configured to amplify the down-converted signal, and filter circuit 206c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 204 for further processing. In some implementations, although not required, the output baseband signal may be a zero-frequency baseband signal. In some implementations, the mixer circuit 206a of the receiving signal path may include a passive mixer, although the scope of the implementations is not limited in this respect.

[0058] In some implementations, the mixer circuit 206a of the transmission signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 206d to generate an RF output signal for the FEM circuit 208. The baseband signal can be provided by the baseband circuit 204 and can be filtered by the filter circuit 206c.

[0059] In some embodiments, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 206a for the receive signal path and the mixer circuit 206a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 206a for the receive signal path and the mixer circuit 206a for the transmit signal path may be configured for superheterodyne operation.

[0060] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 204 may include a digital baseband interface for communicating with RF circuitry 206.

[0061] In some dual-mode implementations, separate radio IC circuits can be provided to process signals for each spectrum, although the scope of implementations is not limited in this respect.

[0062] In some implementations, synthesizer circuit 206d may be a fractional N synthesizer or a fractional N / N+1 synthesizer, although the scope of implementations is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 206d may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0063] Synthesizer circuit 206d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some embodiments, synthesizer circuit 206d can be a fractional N / N+1 synthesizer.

[0064] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not mandatory. The divider control input may be provided by the baseband circuit 204 or the application processor 202 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 202.

[0065] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable set of delay elements, a phase detector, a charge pump, and D-type flip-flops. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0066] In some embodiments, synthesizer circuitry 206d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 206 may include an IQ / polarity converter.

[0067] FEM circuit 208 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to RF circuit 206 for further processing. FEM circuit 208 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 206 for transmission through one or more of the one or more antennas 210. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 206, only in FEM 208, or in both RF circuit 206 and FEM 208.

[0068] In some implementations, FEM circuit 208 may include a TX / RX switch to switch between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to RF circuit 206). The transmit signal path of FEM circuit 208 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by RF circuit 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of one or more antennas 210).

[0069] In some implementations, PMC 212 can manage the power supplied to baseband circuitry 204. Specifically, PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. PMC 212 is typically included when device 200 can be battery powered, for example, when the device is included in a UE. PMC 212 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0070] Although Figure 2 The PMC 212 is shown coupled only to the baseband circuit 204. However, in other embodiments, the PMC 212 may be additionally or alternatively coupled to other components, such as, but not limited to, the application circuit 202, the RF circuit 206, or the FEM 208, and perform similar power management operations.

[0071] In some implementations, PMC 212 can be controlled or otherwise integrated into various power-saving mechanisms of device 200. For example, if device 200 is in the RRC_Connected state, where it remains connected to the RAN node as expected to receive traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, device 200 can be powered down for short intervals, thereby saving power.

[0072] If there is no data traffic activity during the extended period, device 200 can transition to the RRC_Idle state, in which it disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 200 enters a very low power state and performs paging, in which it periodically wakes up again to listen to the network, and then powers off again. Device 200 cannot receive data in this state; to receive data, it must transition back to the RRC_Connected state.

[0073] An additional power-saving mode allows the device to be unavailable from the network for periods exceeding the paging interval (ranging from seconds to hours). During this time, the device is completely unconnected to the network and can be completely powered off. Any data sent during this period will incur significant latency, which is assumed to be acceptable.

[0074] The processors of application circuit 202 and baseband circuit 204 can be elements used to execute one or more instances of a protocol stack. For example, the processor of baseband circuit 204 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of application circuit 204 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include the Physical (PHY) layer of the UE / RAN node, which will be described in further detail below.

[0075] refer to Figure 3 This diagram illustrates a block diagram of a user equipment wireless communication device (UE) or other network device / component (e.g., gNB, eNB, or other participating entity). The UE device 300 includes: one or more processors 310 (e.g., one or more baseband processors) including processing circuitry and associated interfaces; transceiver circuitry 320 (e.g., including RF circuitry, which may include transmitter circuitry (e.g., associated with one or more transmit chains) and / or receiver circuitry (e.g., associated with one or more receive chains), the transmitter and receiver circuitry may employ common circuitry elements, different circuitry elements, or combinations thereof); and memory 330 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processors 310 or transceiver circuitry 320).

[0076] In the various embodiments (aspects) discussed herein, a signal or message may be generated and output for transmission, and / or the transmitted message may be received and processed. Depending on the type of signal or message generated (e.g., by processor 310, processor 310, etc.), outputting it for transmission may include one or more of the following operations: generating a set of associated bits encoding the content of the signal or message; encoding (e.g., may include adding cyclic redundancy check (CRC) and / or encoding via turbine code, low-density parity check (LDPC) code, truncated convolutional code (TBCC), etc.); scrambling (e.g., based on a scrambling seed); modulation (e.g., via binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.); and / or resource mapping (e.g., mapping to a set of scheduled resources, mapping to a set of time and frequency resources authorized for uplink transmission, etc.). Depending on the type of the received signal or message, processing (e.g., by processor 310) may include one or more of the following operations: identifying physical resources associated with the signal / message, detecting the signal / message, deinterleaving, demodulating, descrambling, and / or decoding resource elements.

[0077] A single Configurable Grant (CG) can be configured on either the UL or SUL (Supplemental UL) at the cell level. The SUL can be configured on frequency range 1 of FR1 (FR1), and the time division duplex (TDD) spectrum (at 3.5 GHz) used for both DL and UL is above the FDD spectrum at 1.8 GHz. For the uplink, two carriers are configured: one in the TDD spectrum (3.5 GHz) and the other (SUL) at 1.8 GHz. Type 1 is configured by RRC, while CG Type 2 can be activated by DCI, where one or more parameters can be configured by RRC.

[0078] The UL at FR1 has TDD spectrum for both DL and UL, so this UL tends to be at a higher frequency (e.g., around 3.5 GHz). The cell's coverage area is much smaller than the FDD spectrum at 1.8 GHz, so for the uplink, for example, two carriers are configured: one in the TDD spectrum (around 3.5 GHz) and the other (SUL) at 1.8 GHz. In the case of SUL, due to the lower carrier frequency, the path loss is less and the coverage area is larger. Therefore, the same coverage area can be maintained as in the case of FDD. In addition, cell coverage in the UL direction is generally lower than in the DL direction because the UE Tx power (UL power) is not as strong as the gNB Tx power (DL power). When UE 101, 200, or 300 is near the cell edge, the performance degradation in the UL direction due to this difference can be severe. As a possible solution, one idea is to use a frequency that is very low compared to the original UL frequency. Because the frequency is lower, the cell coverage area is larger. This is the motivation behind using an auxiliary UL at a much lower frequency in SUL. When channel conditions are favorable, the network can instruct the UE to use the original UL frequency, and when channel conditions deteriorate below a certain standard, the network can guide the UE to use an auxiliary (supplementary) UL frequency. Several NR bands exist dedicated to SUL (e.g., n80, n81, n82, n83, n84, n86, etc.). These NR bands can be below 2 GHz, which can be below commonly used NR frequencies (e.g., above 3 GHz). However, a potential drawback of this approach is that these SUL bands may conflict with existing LTE bands. Therefore, this can cause NR-LTE coexistence issues.

[0079] In version 16, up to twelve configurable grants can be configured and active at the Bandwidth Part (BWP), some of which can be configured at the UL and some at the SUL. However, no rule is specified for selecting a configurable grant across all configurations, and furthermore, the UE's selection may be inconsistent with network preferences. Therefore, CG rules that allow for adjusting UE behavior and aligning it with network preferences are desirable. CG transmission is one of the rare occasions when the UE has some autonomy in configuring its behavior. Therefore, the implementation described herein configures the UE's behavior to be more predictable on the gNB 111, 200, 300, or 340 side, and thus the gNB 111, 200, 300, or 340 is more likely to enable configurable grant features. As an information element in the logical channel, configurable grants can be used as the configuredGrantConfig for type 1 or type 2 CGs, which can be configured for either the UL or SUL, but not necessarily for both at once in the case of type 1. When an active Configured UL Authorization Type 2 exists, the network does not reconfigure configuredGrantConfig except for synchronous reconfiguration (see TS 38.321[3]). However, the network may release configuredGrantConfig at any time. The configuration element rrc-ConfiguredUplinkGrant can be a configuration transmitted with a Configured Authorization (Type 1) UL Authorization with full RRC configuration. If this field is not present, the UE uses a UL Authorization (Type 2) configured by the DCI addressing to the CS-RNTI. Type 1 Configurable Authorization can be configured for UL or SUL, but not necessarily for both at the same time.

[0080] Figure 4 Examples of different time slots for the transmit configuration 400 for CG configuration in SUL and UL according to various implementation schemes are shown. Type 1 is RRC configured and Type 2 is DCI activated, where many parameters are RRC configured.

[0081] In one scenario, gNB 111, 200, 300, or 340 can be configured with Type 1 CG, where on SUL (at frequency F1), the UE can be configured with a configured license to transmit on time slots n+1, n+3, n+5, etc. (e.g., Type 1 configured license, denoted as CG-x). On UL (at frequency F2), UE 101, 200, or 300 can be configured with a configured license to transmit on time slots n+2, n+4, n+6, etc. (e.g., Type 1 configured license, denoted as CG-y).

[0082] In the exemplary transmission configuration at the top, PUSCHs from time slot n to time slot n+3 are shown consecutively. This can be challenging for UE implementations, as the UE may need to switch from F1 to F2 (e.g., from time slot n to time slot n+1), and from a specification perspective, such a configuration could be considered an error condition. This also relates to the so-called handover time discussed below, i.e., the time taken to switch from UL to SUL or vice versa for CG transmission. In the right-hand diagram, UE 101, 200, or 300 can support this configuration because they will have sufficient time to switch from F1 to F2 and vice versa.

[0083] The various implementations described herein provide conditions for configuring UL, SUL, or both UL and SUL for CG and under what conditions. Furthermore, if UE 101 transmits on F1 at time T but needs to transmit via F2 at time T+ΔT (e.g., Physical Uplink Control Channel (PUCCH) / Physical Random Access Channel (PRACH) / Physical Uplink Shared Channel (PUCCH) / Sound Reference Signal (SRS)), then gNB 111 or the UE indicates some constraints. In other words, when UE 101 selects UL or SUL for CG transmission, this can cause other channels / signals such as PUCCH, SRS, or PRACH to be interrupted. Since UE101 has additional autonomy in version 15 and version 16 to select a transmission via CG, and in version 16 the UE has additional autonomy to select a specific CG for transmission, these transmissions can interfere with ongoing or planned transmissions, such as disrupting HARQ feedback for DL ​​and the conditions for CG transmission. Therefore, these conditions and constraints can be further incorporated into the UE / gNB configuration as a set of CG rules.

[0084] Figure 5 Exemplary information element 500 according to various embodiments is shown. For example, directly related to physical constraints could be constraints based on logical channels. Because the SUL is typically at a lower frequency and the UL is at a higher frequency, the higher frequency with a larger bandwidth is more readily available. Lower frequencies are also generally more robust due to lower path loss. Therefore, logical channels can be configured by gNB111, network configuration, or at UE101 to pass through the SUL instead of the UL, such as by an indication carried by information element (IE) 500. For example, from a delay perspective, as part of the embodiments / aspects herein, logical channel configuration may introduce IE 500 to signal whether the SUL, UL, or both are allowed to be selected and utilized. IE can be used to indicate whether the SUL or UL is allowed for use in a logical channel. It is assumed that the SUL and UL typically have different subcarrier spacings, such as Figure 4In other words, this can be enabled through, for example, the "allowedSCS-List" setting in IE 500's configuration.

[0085] As mentioned above, CG transmission is one of the rare occasions when the UE decides to transmit autonomously. Since most transmissions in the NR network are controlled by the network, the autonomy of UE 101, 200, or 300 can be configured to ensure that this autonomy does not interfere with / suppress / disrupt other expected transmissions at gNB 111, 200, 300, or 340, or conflict with these other transmissions.

[0086] refer to Figure 6 An exemplary priority chart 600 is shown that can be used with various implementations. When the UE transmits via the CG, this can result in the suppression of transmissions of other channels / signals. In a first example, PUSCH transmissions via the CG may overlap with dynamic PUSCH transmissions. In a second example, PUSCH transmissions via the CG may overlap with PUCCHs carrying HARQ-ACKs in response to DL PDSCH transmissions. In a third example, PUSCH transmissions via the CG may overlap with periodic / semi-persistent PUCCH transmissions used for CSI reporting. In a fourth example, PUSCH transmissions via the CG may overlap with semi-persistent PUSCH transmissions used for semi-persistent CSI reporting. In a fifth example, PUSCH transmissions via the CG may overlap with SRS transmissions, which may be periodic, semi-persistent, or aperiodic. In a sixth example, PUSCH transmissions via the CG may overlap with PUCCHs carrying beam fault recovery requests (BFRQs). Other such examples of CG transmission interference are conceivable and not limited to these examples.

[0087] In one implementation, UE 101, 200, or 300 may be configured to perform a conformance test for CG transmission. The conformance test ensures that if CG transmission is performed using the selected CG resources, some signals / channels may be dropped, and in this case, dropping those channels / signals based on the transmission via the selected CG resources is consistent with the drop rules / priority rules defined in Release 15 / Release 16. For the conformance test, UE 101 may be configured to determine when to perform the conformance test using various types of information including the priorities of various network channels / signals, such as low or high (e.g., priority chart 600), and information about the types of signals / channels that may also cause interference.

[0088] For example, UE 101 can perform a conformance test between all periodic / semi-periodic / aperiodic transmissions known at a specific symbol or set of symbols, such as an L2 symbol, prior to the start of the CG transmission or interruption time (e.g., the time when the carrier is switched from UL to SUL and / or vice versa, and the CG transmission time). If any information exists too close to the CG transmission (e.g., DCI or other information scheduling uplink transmissions), UE 101 cannot cancel or modify the UE's CG transmission based on that information.

[0089] In other implementations, UE 101 may be configured to consider the duration of the compliance test. If a CG transmission would disrupt some periodic / semi-persistent / aperiodic transmissions, the disruption may include, for example, the duration of the CG transmission. However, the CG transmission time is not the only duration to consider. For example, depending on which carrier (SUL or UL) is used for the CG transmission and the transmissions before and after the CG, there may be zero, one, or two handover times, where the handover time includes the time from one SUL or UL to another.

[0090] If the CG transmission passes the conformance test, UE 101 may, for example, enter the test CG transmission from the candidate CG transmission set. UE 101 may then, for example, select a CG from the candidate CG transmission set for transmission. UE 101 (including 200 or 300 in this disclosure) may then perform the CG transmission; cancellation of the signal / channel (if any) is performed relative to the CG transmission. Therefore, if the CG configuration within the time slot passes the conformance test, multiple CGs may be candidates for use, and the UE decides which CG or CGs to utilize.

[0091] Figure 7 A simplified box example of a potential interfering signal 700 (such as a CG-based PUSCH that can interfere with, for example, a PUCCH) is shown. In Release 15, drop rules are defined to handle situations where there may be conflicts between signals / channels. These drop rules can be utilized by UE 101 when configuring CG transmissions in SUL, UL, or both. In Release 16, PUCCHs carrying scheduling requests (SRs), PUCCHs carrying HARQ feedback, PUCCHs carrying channel state information (CSI), and PUSCHs can be associated with priority levels and any signals that also have derived priorities. UE 101 can utilize these priority definitions to perform compliance tests, for example, for CG transmissions in UL or SUL.

[0092] For UE 101 to perform a CG transmission, the first step becomes performing a conformance test. UE 101 compares and discards any channels / signals that interfere with the CG transmission. The UE performs the CG transmission to discard lower-priority channels used for the CG transmission. If, for example, a high-priority signal or a high-priority DL transmission and this CG transmission are configured for low priority, UE 101 should not proceed with the CG transmission because the CG transmission has higher priority in the UL, such as, for example, HARQ feedback.

[0093] When 'x' is specified in both the high-priority and low-priority columns of Priority Table 600, a priority can be assigned to either one, such as high or low. For example, PUSCH dynamic authorization can be both, configured by, for example, RRC, gNB 111, UE 101, or other network entity devices. Some content or signals can be both, and some signals and content or signals can always be low. Priority Table 600 is merely an example and can be configured differently in other embodiments described herein. CSI can, for example, always be low, so if any conflict occurs between high-priority CSI and low-priority CSI (like P / SP-CSI), the lower-priority transmission can be discarded or taken into account along with other considerations in conformance testing.

[0094] Some priorities can be dynamically determined, while others can be predefined. CG priorities are configured, for example, by RRC, while DG priorities are indicated in the DCI. SR is configured by RRC, as in HARQ-ACK feedback. Other priorities can be derived, for example, as indicated in the DCI used for DL ​​transmission, where HACK-ACK feedback is high priority if DL transmission is high priority. SP CSI uses the UL of the DCI to activate it, so the UL of the DCI can have a priority field that can be indicated as such. Similarly, the priority of the CSI can have the uplink in the DCI, so the priority can be indicated as such. In other cases, at high levels, the priority of the CSI is configured by RRC or provided by DL, or similarly, can be specified as low priority.

[0095] Figure 8 Exemplary considerations for conformance testing, including available information, according to embodiments herein are illustrated. UE 101 can be configured to utilize L2 symbols or T in the tested CG to transmit 830. proc,2 Consistency tests are performed based on information available prior to the specified time. In the description below, T can be applied wherever "L2 symbol" is used. proc,2The time is used to replace the L2 symbol. If a DCI, for example, scheduling PUSCH-1 820, is received before that point, the gNB 111 scheduling decision is considered in the conformance test; otherwise, no decision is considered (e.g., until the L2 symbol or until a DG PUSCH-2 826 has not been scheduled). L2 is given in TS 38.214, as included below. Note that the determination of L2 depends on T. proc,2 The calculation depends on the PDCCH carrying the PUSCH and the parameter set of the PUSCH. For type 2CG, once activated, the initial transmission of the transport block does not require scheduling the PUSCH's DCI. Several implementation schemes can be configured here:

[0096] Option 1: μ corresponds to the subcarrier spacing (μ) of the uplink channel that will utilize it to transmit CG PUSCH. UL ),

[0097] Option 2: μ corresponds to generating the maximum T proc,2 of (μ) DL ,μ UL One of them, where μ DL The minimum subcarrier spacing of the PDCCH of the DCI that carries the PUSCH and can schedule the PUSCH on the same carrier as the tested CG PUSCH, and μ UL This corresponds to the subcarrier spacing of the uplink channel that will be used to transmit the PUSCH.

[0098] As mentioned in TS 38.214: If the first uplink symbol in the PUSCH allocation for a transport block, including the DM-RS as defined by the slot offset K2 of the scheduling DCI and the start and length indicators SLIV, and including the effects of timing advance, is not earlier than symbol L2, where L2 is defined as the CP start T after the end of the last symbol of the PDCCH carrying the scheduling PUSCH. proc,2 =max((N2+d 2,1 (2048+144)·κ2 -μ ·T C ,d 2,2 If the next uplink symbol is obtained, the UE should transmit a transport block.

[0099] -N2 is based on μ in Tables 6.4-1 and 6.4-2, respectively, for UE processing capabilities 1 and 2, where μ corresponds to the value that generates the maximum T. proc,2 of (μ) DL ,μ UL One of them, where μ DLThe subcarrier spacing of the downlink corresponding to the DCI that has been used to transmit the scheduled PUSCH, and μ UL This corresponds to the subcarrier spacing of the uplink channel that will use it to transmit PUSCH, and κ is defined in Clause 4.1 of [4,TS 38.211].

[0100] -If the first symbol assigned by PUSCH consists only of DM-RS, then d 2,1 =0, otherwise d 2,1 =1.

[0101] - If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation also includes the effect of the timing difference between the component carriers, as given in [11, TS 38.133].

[0102] - If the scheduling DCI triggers a BWP switch, then d 2,2 It equals the switching time defined in [11,TS 38.133], otherwise d 2,2 =0.

[0103] - For a UE that supports capability 2 on a given cell, if the higher-level parameter processingType2Enabled in PUSCH-ServingCellConfig is configured and set to enabled for that cell, the processing time based on UE processing capability 2 is applied.

[0104] - If the PUSCH indicated by the DCI overlaps with one or more PUCCH channels, the transport block is multiplexed according to the procedure in Clause 9.2.5 of [6, TS 38.213]; otherwise, the transport block is transmitted on the PUSCH indicated by the DCI. Otherwise, the UE may ignore the scheduling DCI. proc,2 The value can be used in both regular loop prefix and extended loop prefix cases.

[0105] Table 6.4-1: PUSCH preparation time for PUSCH timing capability 1:

[0106] μ <![CDATA[PUSCH Preparation Time N2 [Symbols]]]> 0 10 1 12 2 23 3 36

[0107] Table 6.4-2: PUSCH preparation time for PUSCH timing capability 2

[0108] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 5 1 5.5

[0109] Interruption time 828 is shown as the time of CG launch 830 at least under compliance testing.

[0110] The L2 symbol can be used to handle UE capabilities or UEs with certain capabilities, which can be indicated as Capability 1 / Capability 2. Capability 1 is slower to process, and Capability 2 is faster, which can depend on the minimum time required for UE 101 from DCI triggering to DCI scheduling to actual UL transmission.

[0111] The UE can consider any information available before that point (e.g., until L2 symbol transmission) during conformance testing for PUSCH-1 820 for configuring CG transmission, PUCCH 822 for HARQ, and PUCCH 824 for periodic CSI (beam management). For example, DG uplink transmission 810 (e.g., DG PUSCH TX), HARQ-ACK feedback 812 for PDSCH, then periodic CSI 814, and their corresponding transmissions, can be considered because they are available to UE101 before L2 symbol point 802. Therefore, if there are many time slots preceding this periodic configuration because it is from RRC, much information can be available before the L2 symbol is configured for actual transmission. However, if some information (e.g., DG PUSCH-Tx 816) becomes available after L2, UE101 either retains or disregards this information because there is no way to react to it or incorporate it into future communications. In this situation, since UE 101 is already ready to transmit via CG, the UE behaves / operates as if these information operations are more cumbersome transmissions, and therefore UE 101 can discard these information without considering higher / lower priority because UE 101 has no time.

[0112] Figure 9 An example of an interruption time 900, which would be considered a factor in a conformance test for a CG transmission according to an embodiment of this document, is shown. As with each embodiment of this document, UE101 uses a conformance test to determine or consider the selection or selection of at least one of a SUL or UL for a configured authorized PUSCH transmission. If the transmission prior to the tested CG transmission, the tested CG transmission itself, and the transmission after the tested CG transmission are on the same carrier, the interruption time may simply be the CG transmission time as shown in the figure.

[0113] consider Figure 9For example, there is a channel / signal (e.g., SRS) anticipated in the near future (e.g., PUCCH-1 via SUL on T2). Using the configured authorized opportunity via SUL at T1 will not give UE 101 sufficient time to switch back to UL; therefore, the anticipated PUCCH-1 transmission will be interrupted. In one example, the information carried by PUCCH-1 is not critical, so the interruption of PUCCH-1 is acceptable and permitted by the conformance test priority rules. In another example, the information carried by PUCCH-1 is critical, and the interruption of PUCCH-1 is not permitted by the conformance test priority rules. Regardless, UE 101 begins transmitting on SUL before the CG transmission, and UE 101 continues to operate on SUL while the CG transmission is under conformance testing and after the CG transmission, where UE 101 can provide another PUCCH transmission.

[0114] Figure 10 Another example of an interruption time 1000, which would be considered a factor in a conformance test for a CG transmission according to an embodiment of this document, is shown. Similarly, UE 101 selects or chooses at least one of a SUL or UL for a configured authorized uplink (e.g., PUSCH) transmission or other shared link (e.g., PDSCH) transmission. If the transmission preceding the tested CG transmission, and the tested CG transmission 1002 itself, are on the same carrier, but the transmission following the tested CG transmission (e.g., PUCCH-1) are on a different carrier, then the interruption time = {CG transmission time} + {switching time 1004}.

[0115] In another scenario, if the transmission preceding the tested CG transmission is on one carrier, but the tested CG transmission itself and the transmission following it are on different carriers, then the interruption time = {switching time} + {CG transmission time}. Here, the switching time 1004 will occur exactly before the CG transmission time 1002, and can be, for example, the same amount of time or different amounts of time. In this case, the interruption time consists of the switching time 1004 and the CG transmission time 1002 itself.

[0116] Figure 11Another example of an interruption time 1100, which would be considered a factor in a conformance test for a CG transmission according to an embodiment of this document, is shown. Similarly, UE 101 selects or chooses at least one of SUL or UL for a configured authorized PUSCH transmission. If the transmission prior to the tested CG transmission and the transmission after the tested CG transmission are on one carrier (e.g., UL), but the CG transmission itself is on another carrier (e.g., SUL), then the interruption time = {switching time 1} + {CG transmission time 1102} + {switching time 2}, as shown below.

[0117] The UE starts at UL, then switches to CG transmission via SUL, and then returns to UL transmission. In this case, along with the CG transmission time 1102, there are two handover times 1104 and 1106 as T1 and T2, respectively, resulting in a longer interruption time. Now, the interruption time consists of handover time 1, the CG transmission 1102 itself, and handover time 2.

[0118] In other aspects / implementations, for the exact duration of the handover time, handover time-1 and handover time-2 may be based on: the handover time that can be seen in TS38.101-1 for “NR UL from ON to OFF transition time” in section 6.3.3.2 of TS38.101-1, such as 10µs; and the “switching time from LTE UL to NR UL” in section 6.3B.1.1 of TS38.101-1, such as 30µs.

[0119] Figure 12 An example of a power shutdown ramp-up and ramp-down time of approximately ten microseconds is shown, depending on various aspects. A universal on / off time mask defines the observation period between the transmit shutdown power and transmit on power, and between the transmit on power and transmit shutdown power for each SCS. On / off scenarios include continuous and discontinuous transmission, etc. The shutdown power measurement period is limited to the duration of at least one time slot excluding any transient periods. On power is defined as the average power within one time slot excluding any transient periods.

[0120] The top diagram includes the NR UL transition time from on to off as described in Section 6.3.3.2 of TS 38.101-1: 10µs. The bottom diagram shows the handover from LTE UL to NR UL as described in Section 6.3B.1.1 of TS 38.101-1: 30µs.

[0121] In one implementation, UE 101 does not anticipate making such a selection of SUL or UL CG transmission if a higher priority channel would be interrupted by the selected SUL or UL CG transmission. Alternatively or additionally, in cases where there is at least partial time overlap between the configured grant and PUCCH / Dynamic Grant PUSCH / SRS / PRACH, UE 101 may be configured to accordingly shrink the configured grant, wherein the duration of the configured grant is reduced. This may be based on a list of Duration Resource Allocation (TDRA) parameters configured for the configured grant. The shrunken CG may therefore result in a change in the TDRA parameters. The TDRA may be signaled during the configured grant (e.g., using CG-UCI) or via blind detection at gNB 111.

[0122] In another implementation, whether to shrink configured authorization or PUCCH / dynamic authorization PUSCH / SRS / PRACH can be based on priority. In the event of a change in CG size, gNB 111 can determine the size to enable correct CG decoding. For example, gNB 111 can blindly estimate the size. Alternatively, gNB 111 configures a fixed subset of CG sizes to UE 101. Alternatively, UE 101 sends a CG with a size selected from a pre-configured size. Alternatively, gNB uses multiple sizes for blind CG decoding.

[0123] In another implementation, UE 101 may be configured to send accompanying uplink control information (UCI) indicating the size of the transmitted packets based on the modified CG size. Thus, the UE indicates the modified CG size in the UCI to avoid interfering with other channels and signals, and therefore notifies gNB 111 of the change.

[0124] refer to Figure 13 An exemplary processing flow is shown for configuring CG transmission by selecting at least one of UL or SUL based on a conformance test. Processing flow 1300 is initiated at 1302, where a Configured Grant (CG) for CG transmission on the Physical Uplink Shared Channel (PUSCH) is determined. At 1304, the processing flow further includes selecting at least one of an uplink (UL) carrier or a supplementary UL (SUL) carrier for CG transmission based on a conformance test. At 1306, processing flow 1300 further includes configuring CG transmission via the PUSCH based on the selection and conformance test.

[0125] Compliance testing can be performed, for example, between CG transmission and information from one or more other channels or signals detected by multiple L2 symbols up to the start of the CG transmission interruption time. Compliance testing can be based on the CG transmission interruption time, where the interruption time includes the CG transmission time, and based on the selection of CG transmission or at least one of UL or SUL for CG transmission, including a single switching time between UL and SUL or two switching times between UL and SUL.

[0126] In the implementation scheme, a conformance test may be performed based on: a logical channel indicating whether the UE is configured to select at least one of SUL or UL, and a set of priorities, higher-layer signaling, or predefined instructions relative to the CG transmission indicating higher or lower priorities corresponding to other channels or signals received from the next-generation node B (gNB).

[0127] In another implementation, the duration of CG transmission can be modified by altering the Duration Resource Allocation (TDRA) parameters and priority of another channel or signal based on at least partial overlap with that channel or signal. The modified duration can be signaled to the gNB via Uplink Control Information (UCI) based on the modified TDRA.

[0128] As used herein, the term "processor" can refer to virtually any computing processing unit or device, including but not limited to single-core processors; single-processors with software multithreading capabilities; multi-core processors; multi-core processors with software multithreading capabilities; multi-core processors with hardware multithreading technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, application-specific integrated circuit, digital signal processor, field-programmable gate array, programmable logic controller, complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and / or processes described herein. Processors can utilize nanoscale architectures, such as, but not limited to, molecular and quantum dot-based transistors, switches, and gates, to optimize space utilization or enhance the performance of mobile devices. Processors can also be implemented as a combination of computing processing units.

[0129] Examples may include subjects such as methods, means for performing actions or blocks of the method, at least one machine-readable medium including instructions that, when executed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), cause the machine to perform actions of a method, means, or system for concurrent communication using multiple communication technologies according to the embodiments and examples described herein.

[0130] The first embodiment is an apparatus configured for use in a user equipment (UE) for new radio (NR) communications, the apparatus comprising: one or more processors configured to: process a configured authorization (CG) of a physical uplink shared channel (PUSCH); generate a selection of at least one of an uplink (UL) carrier or a supplementary UL (SUL) carrier based on a conformance test indicating whether to configure CG transmission according to a set of CG rules; and configure CG transmission via the PUSCH based on the selection and the conformance test; and a radio frequency (RF) interface configured to provide data to RF circuitry for transmitting the CG transmission as part of the NR communications.

[0131] The second embodiment may include the first embodiment, wherein the one or more processors are further configured to perform the conformance test between the CG transmission and information from one or more other channels / signals detected by one or more symbols up to the start of the CG transmission or interruption time.

[0132] The third embodiment may include the first embodiment or the second embodiment, wherein the one or more symbols include a plurality of L2 symbols, and the conformance test is based on a priority level associated with the information of the one or more other channels / signals.

[0133] The fourth embodiment may include any one or more of the first to the third embodiments, wherein the conformance test is further based on the interruption time, which includes the time from multiple L2 symbols prior to the CG launch to the actual PUSCH launch.

[0134] The fifth embodiment may include any or more of the first to fourth embodiments, wherein the interruption time also includes the time of the CG emission.

[0135] The sixth embodiment may include any one or more of the first to fifth embodiments, wherein the interruption time further includes multiple switching times based on whether the UL carrier or the SUL carrier was used before the CG transmission, whether the UL carrier or the SUL carrier was selected for the CG transmission, and whether the UL carrier or the SUL carrier was used for the actual PUSCH transmission after the CG transmission.

[0136] The seventh embodiment may include any or more of the first to sixth embodiments, wherein the set of CG rules includes priority levels associated with other signals / channels to avoid overlapping with or disrupting the expected next-generation node B (gNB) transmission associated with the priority level.

[0137] The eighth embodiment may include any one or more of the first to the seventh embodiments, wherein the one or more processors are further configured to interrupt the other channel / signal transmission based on a lower priority level of the other channel / signal transmission.

[0138] The ninth embodiment may include any or more of the first to eighth embodiments, wherein the one or more processors are further configured to: reduce the duration of the CG transmission based on a duration parameter in response to at least partial overlap of the Physical Uplink Control Channel (PUCCH) / Dynamic Grant PUSCH, Sounding Reference Signal (SRS) or Physical Random Access Channel (PRACH) or the priority of another channel / signal being higher than that of the CG transmission.

[0139] The tenth embodiment may include any one or more of the first to ninth embodiments, wherein the one or more processors are further configured to: communicate the duration of the CG transmission via uplink control information (UCI) in response to reduction.

[0140] The eleventh embodiment is a tangible computer-readable storage device that stores executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) to perform operations including: determining a configured authorization (CG) for CG transmission on a physical uplink shared channel (PUSCH); selecting at least one of an uplink (UL) carrier or a supplementary UL (SUL) carrier for the CG transmission based on a conformance test; and configuring the CG transmission via the PUSCH based on the selection and the conformance test.

[0141] The twelfth embodiment includes the eleventh embodiment, wherein these operations further include performing the conformance test between the CG transmission and information from one or more other channels or signals detected by a plurality of L2 symbols up to the start of the interruption time of the CG transmission.

[0142] The thirteenth embodiment may include the eleventh or twelfth embodiment, wherein these operations further include: performing the conformance test based on the interruption time of the CG emission, wherein the interruption time includes the CG emission time, and the selection of the CG and at least one of the UL or the SUL for the CG emission includes a single switching time between the UL and the SUL or two switching times between the UL and the SUL.

[0143] The fourteenth embodiment may include any or more of the eleventh to thirteenth embodiments, wherein these operations further include performing the conformance test based on: indicating whether the UE is configured to select a logical channel of the SUL or at least one of the ULs, and a set of priorities, higher-layer signaling, or predefined instructions relative to the CG transmission indicating higher or lower priorities corresponding to other channels or signals received from the next-generation node B (gNB).

[0144] The fifteenth embodiment may include any or more of the eleventh to fourteenth embodiments, wherein these operations further include: performing the conformance test to obtain a successful or unsuccessful result; and selecting the CG launch from the candidate CG launch set in response to a successful result of the conformance test.

[0145] The sixteenth embodiment may include any or more of the eleventh to fifteenth embodiments, wherein these operations further include: reducing the duration of the CG transmission by modifying the duration resource allocation (TDRA) parameters and priority of another channel or signal based on at least partial overlap with another channel or signal; and signaling the duration via uplink control information (UCI) based on the modified TDRA.

[0146] The seventeenth embodiment is a tangible computer-readable storage device that stores executable instructions that, in response to execution, cause one or more processors of a next-generation node B (gNB) or other network device to perform operations including: generating a configured authorization (CG) via a logical channel; and implementing a selection of an uplink (UL) or supplementary UL (SUL) for transmitting the CG on an uplink channel based on the CG and a conformance test for determining interference or conflict transmissions of the CG transmission.

[0147] The eighteenth embodiment includes the seventeenth embodiment, wherein these operations further include: providing indications of one or more priority levels corresponding to one or more other channels or signals for consideration as at least part of the conformance test.

[0148] The nineteenth embodiment includes any or more of the seventeenth to eighteenth embodiments, wherein the conformance test includes an interruption time for providing the CG emission and at least one switching time between the UL and the SUL.

[0149] The twentieth embodiment includes any or more of the seventeenth to nineteenth embodiments, wherein these further include: blindly decoding changes in the duration parameter of the CG transmission; or determining the change via uplink control information (UCI) through the uplink channel.

[0150] The embodiments may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described in any of the above embodiments or related to them.

[0151] Furthermore, standard programming and / or engineering techniques can be used to implement the various aspects or features described herein as methods, apparatus, or articles of art. As used herein, the term "article of art" is intended to cover a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., high-density disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., EPROMs, cards, sticks, key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data. Furthermore, a computer program product may include a computer-readable medium having one or more instructions or codes that are operable to cause a computer to perform the functions described herein.

[0152] Communication media embody computer-readable instructions, data structures, program modules, or other structured or unstructured data in data signals such as modulated data signals, such as carrier waves or other transmission mechanisms, and include any information delivery or transmission medium. The term "modulated data signal" or signal refers to a signal whose one or more characteristics are set or altered in a manner that encodes information in one or more signals. By way of example, and not limitation, communication media include wired media such as wired networks or direct wired connections, and wireless media such as acoustic, RF, infrared, and other wireless media.

[0153] An exemplary storage medium can be coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor. Furthermore, in some aspects, the processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a user terminal. Alternatively, the processor and storage medium can reside as discrete components in the user terminal. Furthermore, in some aspects, the process and / or actions of a method or algorithm can reside as one or any combination or set of code and / or instructions on a machine-readable and / or computer-readable medium, and can be incorporated into a computer program product.

[0154] In this regard, although the subject matter disclosed herein has been described in conjunction with various embodiments and corresponding drawings, it should be understood that other similar embodiments may be used, or modifications and additions may be made to the described embodiments, to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the described embodiments. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted in accordance with the breadth and scope of the following appended claims.

[0155] In particular, regarding the various functions performed by the aforementioned components (components, devices, circuits, systems, etc.), unless otherwise stated, the terminology used to describe such components (including references to "means") is intended to correspond to any component or structure that performs the specified function of the said component (e.g., functionally equivalent), even if it is not structurally equivalent to the disclosed structure that performs the function in the exemplary embodiments of this disclosure shown herein. Furthermore, while certain features have been disclosed with respect to only one of several embodiments, it may be desirable and advantageous for any given or particular application to combine such features with one or more other features of other embodiments.

Claims

1. A user equipment (UE), comprising: Radio frequency (RF) circuits; as well as One or more processors, the one or more processors being configured to execute instructions stored in memory to cause the UE to: Receive the configuration of the Configurable Grant (CG) for the Physical Uplink Shared Channel (PUSCH); A selection of at least one of an uplink (UL) carrier or a supplementary UL (SUL) carrier is generated based on a set of CG rules for CG transmission; In response to the CG emission overlapping at least partially with another signal having a higher priority than the CG emission, the duration of the CG emission is reduced by modifying the duration parameter based on the duration parameter configured for the CG. Uplink control information (UCI) indicating a modified duration parameter is transmitted via the RF circuit; and The CG transmission with a reduced duration is transmitted on the PUSCH via the RF circuit based on the selection.

2. The UE of claim 1, wherein the selection is further based on the CG transmission and one or more other channels or signals detected up to one or more symbols prior to the start of the CG transmission or the interruption time for the CG transmission.

3. The UE of claim 2, wherein the one or more symbols comprise a plurality of L2 symbols, and the selection is further based on a priority level associated with the one or more other channels or signals.

4. The UE of claim 2, wherein the interruption time for the CG transmission is based on the time of switching between the UL carrier and the SUL carrier.

5. The UE of claim 4, wherein the interruption time for the CG transmission is further based on the duration of the CG transmission.

6. The UE of claim 4, wherein the interruption time is further based on whether the UL carrier or the SUL carrier was used before the CG transmission, and whether the UL carrier or the SUL carrier was selected for the CG transmission.

7. The UE of claim 1, wherein the set of CG rules includes priority levels associated with the CG transmission and other channels or signals.

8. The UE of claim 7, wherein the one or more processors are further configured such that the UE: Configure the CG transmission and interrupt the transmission of another channel or signal based on the fact that the priority level of the other channel or signal transmission is lower than that of the CG transmission.

9. The UE of claim 1, wherein another signal having a higher priority than the CG transmission includes a Physical Uplink Control Channel (PUCCH) transmission, a Sounding Reference Signal (SRS), or a Physical Random Access Channel (PRACH) transmission.

10. The UE of claim 1, wherein the duration parameter configured for the CG includes a Duration Resource Allocation (TDRA) parameter list.

11. An apparatus for wireless communication, comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations, the operations including: Receive the configuration of the Configurable Grant (CG) for CG transmission on the Physical Uplink Shared Channel (PUSCH); At least one of an uplink (UL) carrier or a supplementary UL (SUL) carrier is selected for the CG transmission based on a set of CG rules; In response to the CG emission overlapping at least partially with another signal having a higher priority than the CG emission, the duration of the CG emission is reduced by modifying the duration parameter based on the duration parameter configured for the CG. Provide uplink control information (UCI) indicating modified duration parameters to the radio frequency (RF) interface for transmission; and Based on the selection, the CG transmission with a reduced duration is provided to the RF interface for transmission on the PUSCH.

12. The apparatus of claim 11, wherein the selection is further based on the CG transmission and one or more other channels or signals detected up to the start of the interruption time of the CG transmission.

13. The apparatus of claim 12, wherein the interruption time is based on the CG transmission time and the switching time between the UL carrier and the SUL carrier.

14. The apparatus of claim 11, wherein the selection is further based on an information element (IE) indicating whether the UL carrier or the SUL carrier is permitted for use in a logical channel associated with the CG transmission.

15. The apparatus of claim 11, wherein the operation further comprises: Determine the candidate CG emission set; and The CG is selected from the candidate CG emission set for the CG emission.

16. An apparatus for wireless communication, comprising: One or more processors; as well as A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations, the operations including: Provide the radio frequency (RF) interface with a configured authorization (CG) for transmission using the Physical Uplink Shared Channel (PUSCH); as well as A selection of at least one of the uplink (UL) or supplementary UL (SUL) is made based on a set of CG rules for CG transmission on the PUSCH; Receive uplink control information (UCI) indicating a modified duration parameter corresponding to the duration of the CG transmission, wherein the modified duration parameter is based on a duration parameter configured for the CG; The CG emission is decoded based on the modified duration parameter indicated in the UCI.

17. The apparatus of claim 16, wherein the operation further comprises: Provides indications of one or more priority levels corresponding to one or more other channels or signals, wherein the selection is based on the one or more priority levels.

18. The apparatus of claim 16, wherein the selection is based on an interruption time for providing the CG transmission and at least one switching time between the UL and the SUL.

Images