EP3834567A1

EP3834567A1 - Prioritization of control and data transmsission for different services

Info

Publication number: EP3834567A1
Application number: EP19846385.3A
Authority: EP
Inventors: Gang Xiong; Toufiqul Islam; Sergey PANTELEEV; Debdeep CHATTERJEE; Yushu Zhang; Fatemeh HAMIDI-SEPEHR
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2018-08-10
Filing date: 2019-08-12
Publication date: 2021-06-16
Also published as: WO2020033941A1; EP3834567A4

Abstract

A network device (e.g., a user equipment (UE), a new radio NB (gNB), or other network component) can process or generate a dynamic indication of a prioritization rule based on different physical uplink signals, different physical uplink channels, or a combination thereof. The dynamic indication can activate the priority rule to indicate a handling of a first transmission of a first service type / priority over a second transmission of a second service type / priority. The transmissions can include data, control information or both as uplink transmissions, for example, and the first service type / priority can be an enhanced Mobile Broadband (eMBB) communication and the second service type / priority can be an Ultra-Reliable Low-Latency Communication (URLLC).

Description

PRIORITIZATION OF CONTROL AND DATA TRANSMSISSION FOR DIFFERENT

SERVICES

REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.

62/717,254 filed August 10, 2018, entitled“PRIORITIZATION OF CONTROL AND DATA TRANSMISSION FOR DIFFERENT SERVICES”, the contents of which are herein incorporated by reference in their entirety.

FIELD

[0002] The present disclosure relates to wireless technology and more specifically to the prioritization of the control and data transmission for different services of wireless communications.

BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network / system that target to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple and seamless wireless connectivity solutions. NR will enable everything connected by

wireless and deliver fast, rich contents and services.

[0004] The NR use case families, enhanced mobile broadband (eMBB) and ultra reliable and low latency communications (URLCC), have different objectives in terms of user plane latency and coverage levels. The key objectives for URLLC relate to U-plane latency and reliability may include the following: for URLLC the target for user plane latency is to be 0.5ms for UL, and 0.5ms for DL; The target for reliability is to be 1 x1 O ⁵ within 1 ms. As such various, mechanisms are demanded to be considered for the prioritization of different services regarding control and data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 is a block diagram illustrating an example of user equipment(s) (UEs) and gNBs or access nodes in a network with network components useable in connection with various aspects described herein.

[0006] FIG. 2 is a block diagram illustrating a system employable at a UE or gNB, according to various aspects described herein.

[0007] FIG. 3 is another block diagram illustrating another example dropping rule for uplink with different requirements or service types / priorities in accordance with various aspects described herein.

[0008] FIG. 4 is a diagram illustrating an example physical uplink control channel (PUCCH) resource configuration that can be indicated in accordance with various aspects / embodiments described herein.

[0009] FIG. 5 is a block diagram illustrating an example PUCCH resources in a resource set that can be indicated according to various aspects / embodiments described herein.

[0010] FIG. 6 is an example PUCCH relationship information element / indication according to various aspects / embodiments described herein.

[0011] FIG. 7 is another block diagram illustrating another example dropping rule for uplink with different requirements or service types / priorities in accordance with various aspects described herein.

[0012] FIG. 8 is an example sounding reference signal (SRS) relationship information element / indication according to various aspects / embodiments described herein.

[0013] FIG. 9 is an example multiple SRS resource set indication according to various aspects / embodiments described herein.

[0014] FIG. 10 is a block diagram illustrating an example process flow or call flow chart of UE behavior according to various aspects / embodiments described herein.

[0015] FIG. 11 is a block diagram illustrating an example process flow according to various aspects / embodiments described herein. DETAILED DESCRIPTION

[0016] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms“component,”“system,”“interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term“set” can be interpreted as“one or more.”

[0017] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

[0018] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components. [0019] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term“or” is intended to mean an inclusive“or” rather than an exclusive“or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then“X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles“a” and“an” as used in this application and the appended claims should generally be construed to mean“one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms“including”,“includes”,“having”, “has”,“with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a“first X”, a“second X”, etc.), in general the one or more numbered items may be distinct or they may be the same, although in some situations the context may indicate that they are distinct or that they are the same.

[0020] As used herein, the term“circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or associated memory (shared, dedicated, or group) operably coupled to the circuitry that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0021] In consideration of described deficiencies or needs of NR network

architectures uplink control information (UCI) can be carried by physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). In particular, UCI can include scheduling request (SR), hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback, channel state information (CSI) report, e.g., channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSI resource indicator (CRI) and rank indicator (Rl) and/or beam related information (e.g., L1 -RSRP (layer 1 - reference signal received power)). [0022] In NR, when PUCCH resources carrying different UCI types overlap at least one symbol in time in a slot and if the UE is provided higher layer parameter

simultaneous HARQ-ACK-CSI, the UE could multiplex dynamic HARQ-ACK / SR / one or more CSI in a resource which is indicated by a PUCCH resource indication field in the DCI scheduling a PDSCH reception according to the payload size of the combined UCI.

[0023] However, when PUCCHs carrying UCIs with different reliability requirements overlap in a slot, it may not be desirable to multiplex UCIs into one PUCCH. For example, it is expected that a large amount of resources would be allocated for UCI with very low, e.g. 10 ⁵ Block Error Rate (BLER) target. If UCI with ultra-reliability

requirement is multiplexed with UCI with 10² BLER target and transmitted in one physical channel, this large resource allocation may not be desirable for UCI with 10² BLER target due to spectrum efficiency loss. To address this, certain mechanisms can be defined to multiplex UCI with different reliability and latency requirements, including those related to the prioritization services for PUCCH, prioritization for different services for data transmission, and UE behavior without identifying service type / priority.

[0024] Embodiments described herein can be implemented into a system or network device using any suitably configured hardware and/or software. FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments. The system 100 is illustrated to include a UE 101 and a UE 102, which can further represent new radio (NR) devices (e.g., a UE or gNB) or the like as discussed herein.

[0025] FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments. The system 100 is shown to include a user equipment (UE)

101 and a UE 102. As used herein, the term“user equipment” or“UE” may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term“user equipment” or“UE” may be considered synonymous to, and may be referred to as client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term“user equipment” or“UE” may include any type of wireless/wired device or any computing device including a wireless communications interface. In this example, UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (1C), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems,

microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, machine-type communications (MTC) devices, machine-to-machine (M2M), Internet of Things (loT) devices, and/or the like

[0026] In some embodiments, any of the UEs 101 and 102 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine- initiated exchange of data. An loT network describes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the

connections of the loT network.

[0027] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1 10. The RAN 1 10 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio

Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections (or channels) 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail infra). As used herein, the term“channel” may refer to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term“channel” may be synonymous with and/or equivalent to“communications channel,”“data communications channel,”“transmission channel,”“data transmission channel,”“access channel,”“data access channel,”“link,”“data link,”“carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term“link” may refer to a connection between two devices through a Radio Access Technology (RAT) for the purpose of transmitting and receiving information. In this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0028] In this embodiment, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may

alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH). In various

implementations, the SL interface 105 may be used in vehicular applications and communications technologies, which are often referred to as V2X systems. V2X is a mode of communication where UEs (for example, UEs 101 , 102) communicate with each other directly over the PC5/SL interface 105 and can take place when the

UEs 101 , 102 are served by RAN nodes 1 1 1 , 1 12 or when one or more UEs are outside a coverage area of the RAN 1 10. V2X may be classified into four different types:

vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). These V2X applications can use“co-operative awareness” to provide more intelligent services for end-users. For example, vehicle UEs (vUEs)

101 , 102, RAN nodes 1 1 1 , 1 12, application servers 130, and pedestrian UEs 101 , 102 may collect knowledge of their local environment (for example, information received from other vehicles or sensor equipment in proximity) to process and share that knowledge in order to provide more intelligent services, such as cooperative collision warning, autonomous driving, and the like. In these implementations, the UEs 101 , 102 may be implemented/employed as Vehicle Embedded Communications Systems (VECS) or vUEs.

[0029] The UE 102 is shown to be configured to access an access point (AP) 106 (also referred to as“WLAN node 106”,“WLAN 106”,“WLAN Termination 106” or“WT 106” or the like) via connection 107. The connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 102, RAN 1 10, and AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operation and/or WLAN LTE/WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation. The LWA operation may involve the UE 102 in RRC_CONNECTED being configured by a RAN node 1 1 1 , 1 12 to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 102 using WLAN radio resources (e.g., connection 107) via Internet Protocol Security (IPsec) protocol tunneling to authenticate and encrypt packets (e.g., internet protocol (IP) packets) sent over the connection 107. IPsec tunneling may include encapsulating entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

[0030] The RAN 1 10 can include one or more access nodes that enable the connections 103 and 104. As used herein, the terms“access node,”“access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, Road Side Units (RSUs), and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The term“Road Side Unit” or“RSU” may refer to any transportation infrastructure entity implemented in or by a

gNB/eNB/RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a“UE-type RSU”, an RSU

implemented in or by an eNB may be referred to as an“eNB-type RSU.” The RAN 1 10 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1 1 1 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1 12.

[0031] Any of the RAN nodes 1 1 1 and 1 12 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 1 1 1 and 1 12 can fulfill various logical functions for the RAN 1 10 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0032] In accordance with some embodiments, the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 and 1 12 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0033] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 and 1 12 to the UEs 101 and 102, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. [0034] The Physical Downlink Shared Channel (PDSCH) may carry user data and higher-layer signaling to the UEs 101 and 102. The Physical Downlink Control Channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 1 1 1 and 1 12 based on channel quality information fed back from any of the UEs 101 and 102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

[0035] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1 , 2, 4, 8, etc.).

[0036] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[0037] The RAN 1 10 is shown to be communicatively coupled to a core network (CN) 120 via an S1 interface 1 13. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface 1 13 is split into two parts: the S1 -U interface 1 14, which carries traffic data between the RAN nodes 1 1 1 and 1 12 and the serving gateway (S-GW) 122, and the S1 -mobility management entity (MME) interface 1 15, which is a signaling interface between the RAN nodes 1 1 1 and 1 12 and MMEs 121.

[0038] In this embodiment, the CN 120 comprises the MMEs 121 , the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities’ handling of

communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0039] The S-GW 122 may terminate the S1 interface 1 13 towards the RAN 1 10, and routes data packets between the RAN 1 10 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0040] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120. [0041] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE’s Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE’s IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.

[0042] Referring to FIG. 2, illustrated is a block diagram of a system / device 200 employable at a UE (e.g., URLLC UEs, or non-URLLC UEs) or other network device (e.g., gNB / eNB) that facilitates one or more aspects / embodiments herein. System 200 can include one or more processors 210 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with the other FIGs.) comprising processing circuitry and associated interface(s), transceiver circuitry 220 (e.g., comprising part or all of RF circuitry, which can comprise transmitter circuitry (e.g., associated with one or more transmit chains) and/or receiver circuitry (e.g., associated with one or more receive chains) that can employ common circuit elements, distinct circuit elements, or a combination thereof), and a memory 230 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 210 or transceiver circuitry 220).

[0043] In various embodiments / aspects described herein an enhanced PUSCH transmission can be configured, generated, processed, communicated, transmitted or received for example depending on the network device or component. In particular, various embodiment are directed to UE behavior and signaling of dynamic PUSCH repetition factor in Downlink Control Information (DCI) (e.g., as in Release 16), which can be in contrast to semi-static operation of repetition in NR communication (in a previous Release of related 3GPP standards) ; inter-bandwidth part (BWP) frequency hopping; transport block size (TBS) scaling; and enhanced configured grant (CG) UL transmission. Enhanced CG UL can be renamed from Semi-Persistent Scheduling (SPS) in previous LTE scheduling, but now in NR considered CG for UL while in DL as SPS, for example.

[0044] Referring to FIG. 3, illustrated is an example transmission mechanism for different services with a prioritization or dropping rule in accord with various

embodiments. Uplink transmissions 300 can include one or more of: different physical uplink signals (UCI, Channel State Information (CSI), HARQ-ACK feedback

(Acknowledgement (ACK) / Non-acknowledgement (NACK)), other information or the like), different physical uplink channels (PUSCH, PUCCH, etc.), or a combination thereof. These transmissions 300 can further overlap in a transmission resource, for example, in time or frequency with one another.

[0045] In the example of FIG. 3, a first transmission 302 can be scheduled by a scheduling signal or grant when a second transmission 304 is scheduled at initial uplink transmissions as shown at 310. In response to receive a dynamic indication from the gNB (1 1 1 , 1 12, 200, or other network device / component), a dropping rule /

prioritization rule can be activated that indicates dropping a service type / priority over another in order to efficiently, reliably and within a needed latency budget for the transmission 304 in the uplink direction as shown at 320.

[0046] In another example, when PUCCHs carrying UCIs with different reliability and latency requirement overlap in a slot, the gNB (1 1 1 , 1 12, 200, or other network device / component) can define a priority rule or dropping rule by dropping the PUCCH carrying UCI with low reliability and latency requirement, e.g., with 10² BLER target.

More specifically, when PUCCH carrying e.g. eMBB related UCI overlaps with PUCCH carrying e.g. URLLC related UCI in a slot, PUCCH carrying eMBB UCI is dropped. To enable the UE (101 , 102, 200, or other network device / component) to drop the lower priority UCI when overlapping with higher priority UCI, certain mechanisms can be utilized to differentiate the service type/priority, e.g., including eMBB and URLLC services.

[0047] Thus, FIG. 3 illustrates an example of dropping / prioritization rule for UCI with different requirements. When information such as control information 304 (e.g., a channel state (CSI), or the like) for URLLC and CSI for eMBB overlap in a slot, for example, CSI for eMBB 302 can be dropped by the UE (101 , 102, 200, or other network device / component), and the UE (101 , 1 .02, 200, or other network device / component) only transmits the CSI for URLLC 304. This can be initiated or activated by a dynamic indication so that it can vary from one overlap to another in the course of various UL communications, be predefined, explicitly signaled by the gNB / higher layer signaling, or implicitly signaled in a resource configuration / parameter / other process.

[0048] Other embodiments can also include PUCCH prioritization triggered by different services (e.g. eMBB and URLLC, or other service type / priority). In one embodiment, a service type or service priority flag can be included in a PUCCH resource configuration, which can be used to distinguish services with different requirements, (e.g., a reliability, a latency requirement, both, or other service requirement). In one example, service type / priority can include high priority and regular priority services, e.g., URLLC and eMBB services, respectively, in which high priority services is greater or takes precedence over regular priority services.

[0049] In this case, for example, a one bit parameter can be included in a PUCCH resource configuration, where bit“1” can indicate high priority service and bit“0” can indicate regular priority service. In another example, service type / priority can include services with different requirements. In this case, a two-bit parameter can be included in a PUCCH resource configuration, which corresponds to four different service types/priorities. Bit“00” can indicate service type/priority with A0 reliability and/or B0 latency requirement, while bit“01” can indicate service type/priority with A1 reliability and/or B1 latency requirement, etc. Other number of bits could also be envision as corresponding to any one or more service types, data type or physical channels for example.

[0050] Referring to FIG. 4, illustrated is a table or indication 400 as one example of a dynamic PUCCH resource configuration 400 for dropping or prioritization rules, where one bit indicator‘serviceType’ or‘servicePriority’ can be included to differentiate URLLC and eMBB service, or other service types / priorities.

[0051] Based on the configured PUCCH resource, a UE (101 , 1.02, 200, or other network device / component) can determine / derive whether a PUCCH carrying UCI is targeted for a URLLC service or an eMBB service. Further, in response to when a PUCCH carrying eMBB UCI overlaps with another PUCCH carrying URLLC UCI in a slot, PUCCH carrying eMBB UCI can be dropped. [0052] In another embodiment, maximum code rate can be configured for each PUCCH resource. Based on this configured maximum code rate, the UE (101 , 1 .02,

200, or other network device / component) can implicitly derive the corresponding service type/priority. One or more thresholds may be defined to allow the UE (101 ,

1.02, 200, or other network device / component) to determine which service type/priority is associated with a corresponding maximum code rate. The rule to determine the service type/priority can be given as follows.

l

[0053] Here, r is the configured maximum code rate; r_{thres k}, (k = 0, ··· , K - 2) are the thresholds, which can be predefined in the specification or configured by higher layers via NR minimum system information (MSI), NR remaining minimum system information (RMSI), NR other system information (OSI), radio resource control (RRC) signaling, or the like.

[0054] In another embodiment, a PUCCH resource partition within a PUCCH resource set can be used to differentiate different services with different requirements, e.g., URLLC and eMBB services. For less than 3 bit UCI payload size, up to 32

PUCCH resources can be configured within a PUCCH resource set, for example.

Further, for more than 2 bit UCI payload size, up to 8 PUCCH resources can be configured within a PUCCH resource set, for example. In this case, a subset of PUCCH resources within a PUCCH resource set can be configured for one service type / priority. By employing PUCCH resource partition within one PUCCH resource set, dynamic switching between URLLC and eMBB services can be realized at the UE for UL transmission.

[0055] FIG. 5 illustrates one example resource partition 500 for service type/priority differentiation. In the example, within a PUCCH resource set, a subset of PUCCH resources 502 can be configured for URLLC and the remaining subset of PUCCH resources 504 can be configured for eMBB services. This can be signaled explicitly or implicitly according to various embodiments herein, in which the gNB 1 1 1 , 1 12, 200, or other network device / component can provide a dynamic indication in DL to the UE 101 , 102, 200. The UE 101 , 102, 200 can then implement the service type with priority over another in response to an overlap occurring within a time (e.g., a slot, symbol, set of symbols, frequency resource, or other parameter) for example.

[0056] In another embodiment, one field in the DCI can be explicitly used to indicate whether a scheduled PDSCH transmission and corresponding HARQ-ACK on PUCCH is targeted for higher priority service, e.g. URLLC or regular priority service, e.g. eMBB. For explicit indication, a new PUCCH resource set for URLLC service can be configured independently from the PUCCH resource set for eMBB service.

[0057] In another embodiment, the service type/priority can be indicated by dynamic indication, for example, 600 of FIG. 6 based on the spatial relation info for each PUCCH resource. An example is shown as follows. A UE can expect that the serviceType configured in each PUCCH-SpatialRelationlnfo in a spatialRelationlnfoToAddModList should be the same. Alternatively, a UE can expect the serviceType for all PUCCH resources in a resource set should be the same. The default value of serviceType is eMBB.

[0058] In other embodiments, the gNB (1 1 1 , 1 12, 200) or UE (101 , 102, 200) can configure mechanisms on prioritization of different services for a data channel.

[0059] For example, when PUSCH carrying data or UCI for URLLC overlaps with PUCCH carrying UCI for eMBB in a same slot, frequency, time or transmission resource, a dropping rule or a prioritization rule can be defined such that if the timeline

requirement is satisfied, the UE (101 , 102, 200) would drop PUCCH carrying UCI for eMBB and only transmit PUSCH carrying data or UCI for URLLC. The same design principle is applied when PUSCH carrying data or UCI for eMBB overlaps with PUCCH carrying UCI for URLLC in a slot. In this case, if the timeline requirement is satisfied, PUSCH carrying data or UCI for eMBB is dropped and UE only transmits PUCCH carrying UCI for URLLC.

[0060] FIG. 7 illustrates one example of dropping rule for PUSCH 702 and PUCCH 704 with different requirements (e.g., latency (e.g., 0.5 ms), reliability (1 x1 O ⁵), or other requirement). In an example, when PUSCH 704 for URLLC overlaps with PUCCH 702 for eMBB in a slot at illustrated at 710 and if the timeline requirement is satisfied, UE would transmit PUSCH for URLLC and drop PUCCH for eMBB as in the illustration 720. [0061] Embodiments of data transmission prioritization for different services, e.g. eMBB and URLLC, are provided as follows:

[0062] In one embodiment, for Type 1 configured grant uplink transmission, service type/priority can be associated with each configured resource. In one example, one field in the resource configuration along with time and frequency resource allocation can be used to indicate whether this configured grant uplink transmission is targeted for URLLC or eMBB service. For instance, 1 bit indicator can be included in the resource configuration, wherein value“1” is used to indicate that configured grant uplink transmission is targeted for URLLC service while value“0” is used to indicate that configured grant uplink transmission is targeted for eMBB service. In another example, whether configured grant uplink transmission is targeted for URLLC or eMBB service can be configured in a UE specific or a group specific or a cell specific manner. More specifically, it can be configured by higher layers via MSI, RMSI, OSI or RRC signaling.

[0063] In another embodiment, for Type 2 configured grant uplink transmission or DL semi-persistent scheduling (SPS) based physical downlink shared channel (PDSCH), in the activation of Type 2 configured grant uplink transmission or DL SPS PDSCH transmission, one field in the downlink control information (DCI) can be used to indicate whether the Type 2 configured grant uplink transmission or DL SPS PDSCH

transmission is targeted for different service types/priorities with different requirements, e.g., URLLC or eMBB service. This can be applied for both initial and subsequent transmissions. In another example, different Radio Network Temporary Identifier (RNTI) can be used to differentiate whether Type 2 configured grant uplink transmission or DL SPS PDSCH transmission is targeted for URLLC or eMBB service. For instance, when cyclic redundancy check (CRC) is masked with RNTI-A, this indicates that this is targeted for URLLC service. In case when CRC is masked with RNTI-B, this indicates that this is targeted for eMBB service. RNTI-A and RNTI-B can be predefined in the specification or configured by higher layers via MSI, RMSI, OSI or RRC signaling.

[0064] In another embodiment, the service type/priority can be configured in a sounding reference signal (SRS) spatial relation information. In one example, it can be configured according to the information element 800 of FIG. 8.

[0065] Alternatively, a UE 101 , 102, 200 can be configured with multiple SRS resource sets, where different resource sets can be used for different service type/priority. Thus, a service type/priority can be configured in each SRS resource set, for example, as illustrated in the SRS resource set 900 of FIG. 9.

[0066] Various other aspects / embodiments can include UE behavior with/ without identifying a service type / priority. For example, in 5G system, a UE 101 , 102, 200 can support communication with multiple traffic types. For example, for a given time, UE 101 , 102, 200 can have received scheduling for simultaneous transmission of one or more PUCCHs or one or more PUSCHs. Among the K > PUCCH(s)/PUSCH(s) that are scheduled with resources that overlap in time and/or frequency domain, 1 < L < K PUCCH(s) / PUSCH(s) can be of higher priority than the rest. For dynamic resource sharing when communication of multiple traffic types with different properties, such as one can be more bursty or urgent than other, network can indicate the UE 101 , 102, 200, either explicitly or implicitly via some rules or indication, to assume certain UE behaviors such as dropping an ongoing transmission or otherwise as disclosed herein.

[0067] In another example, DCI providing grant for PUSCH can have a field which indicates an index corresponding to a certain action / UE behavior, from a set of supported actions / behaviors. For example, if the UE 101 , 102, 200 has a long PUCCH scheduled in a slot, and an UL grant indicates PUSCH resource, overlapping at least in time with the resource of long PUCCH, the grant can indicate to drop the PUCCH transmission. Alternatively, explicit indication in DCI can not be necessary, and UE 101 , 102, 200 can drop any ongoing transmission if it receives a DCI that indicates resource that overlaps with the resources assigned to ongoing transmission. In another example, UE 101 , 102, 200 can be configured to rate-match the PUSCH transmission around the PUCCH transmission. Whether UE rate-matches the PUSCH around PUCCH or drops the PUCCH e.g., at least in the overlapping area, can be pre-configured or indicated in the DCI scheduling the PUSCH.

[0068] In one example, RRC signaling can indicate or configure a UE 101 , 102, 200 with certain behaviors such as dropping an ongoing transmission. For example, if PUCCH resource of a first transmission overlaps with PUCCH resource of a second transmission, where the second transmission occurs after first transmission, UE 101 ,

102, 200 can be configured to drop ongoing PUCCH transmission (i.e., PUCCH of first transmission) and only transmit PUCCH of second transmission.

[0069] In another example, UE 101 , 102, 200 can be configured with a first set of rules in case of PUCCH resource overlap of multiple transmissions and a second set of rules in case of overlap of PUCCH transmission and PUSCH transmission, and a third set of rules in case of overlap of PUSCHs, where one or more PUSCH can be grant based or grant free. One or more of the set of rules can be configured by higher layer signaling such as RRC signaling. Each set (or subset) of rules can identify a set of behaviors such as dropping a complete transmission, dropping only the overlapping portion, drop the transmission, or resume at a next configured transmission duration / occasion or other rule related to transmission resources. At a given time, the UE 101 , 102, 200 can be operating based on an indication or configuration of one set of rules only. For example, in a given slot, UE 101 , 102, 200 has overlapping PUCCH resource assignments, and then the UE can drop the ongoing PUCCH transmission and transmit the other PUCCH according to first set of rules. Later if PUSCH traffic arrives, e.g., grant-free, UE 101 , 102, 200 can follow a second different set of rules, and prioritize the PUSCH transmission by dropping the PUCCH. Hence, course of UE actions/behaviors can be identified based on order of events such as type of overlaps, which can be based on one or more indications the UE 101 , 102, 200 receives.

[0070] As another set of example rules, the UE 101 , 102, 200 can be indicated whether or not certain UL transmission can be over-written by another trigger, or indication, irrespective of the relative timing between the two transmission triggers / configurations. For example, using a bit field in the DCI carrying the UL grant (or activation grant) or implicit association to (i) a particular RNTI (that scrambles the CRC of the scheduling or activation DCI), or (ii) PUSCH or PUCCH durations, e.g., PUSCH or PUCCH durations that span no more than X symbols (e.g., X = 2), the UE can be indicated that the related transmission cannot be over-written by another UL

transmission, and thereby, prioritized in case of any overlaps with any other UL transmission.

[0071] For Type 1 or Type 2 CG PUSCH, such indication can be provided via the UE-specific RRC signaling structure that conveys the resource configuration itself. For HARQ-ACK transmissions in response to dynamically or SPS-scheduled PDSCH, such indication can either be provided using the scheduling DL assignment DCI or the activation DCI respectively.

[0072] Alternatively, similar prioritization can be realized by indicating a set or subset of PUCCH resources configured via UE-specific RRC signaling as not subject to over writing by another UL transmission. Further, the UE cannot expect to be configured with or scheduled such that two UL transmissions, both of which cannot be over-written, overlap in even one symbol in the time domain.

[0073] Referring to FIG. 10, illustrated is a process flow 1000 as a call flow chart is provided to show UE behaviors when subsequent PUCCH(s) and PUSCH(s)

transmission occur where their assigned resource can overlap at least in time. A similar flow can also be considered for different PUSCHs or PUCCHs. At first, the UE 101 , 102, 200 receives RRC signaling of PUCCH resource sets and resource configuration for Type 1 UL transmission without grant from the gNB 1 1 1 , 1 12, 200. Next, according to L1 signaling, UE 101 , 102, 200 identifies resource for a first PUCCH transmission.

Subsequently, UE can be triggered to transmit a second PUCCH in a resource that at least overlaps in time with the resource of first PUCCH. The trigger for transmitting second PUCCH can be received when first PUCCH transmission is ongoing, such as shown in Figure 10, or before first PUCCH transmission starts. Identifying the overlap,

UE 101 , 102, 200 drops first PUCCH transmission and transmits second PUCCH. Next, a packet arrives at UE buffer (e.g., memory 230) and next opportunity to transmit the packet occurs in a resource that overlaps at least in time with the resource of second PUCCH. The packet can arrive when second PUCCH transmission is ongoing, such as shown in Figure 10, or before second PUCCH transmission starts. Identifying the overlap, UE 101 , 102, 200 drops second PUCCH and transmits the packet according Type 1 UL transmission without grant. Although the example here considers Type 1 UL transmission without grant, it can be extended to Type 2 UL transmission without grant or grant-based PUSCH transmission following similar principle.

[0074] In another example, an absolute priority value can be introduced and be associated with each physical channel. The number of priority levels can reflect different possible services running at a UE 101 , 102, 200 simultaneously (e.g. two, four, or more). Each physical channel which is subject to prioritization at a UE (PDSCH, PUSCH, PUCCH, UCI, etc.) can have an associated priority. If not configured, then default priority is assumed for this channel, e.g. lowest priority.

[0075] In case of PDSCH, the priority can be indicated in DL assignment or as part of DL SPS configuration.

[0076] In case of PUSCH, the priority can be indicated in UL grant or as part of UL configured grant Type 1 or Type 2 configuration. [0077] In case of PUCCH, the priority can either be derived from DL assignment or UL grant triggering dynamic PUCCH/UCI transmission or be a part of PUCCH resource configuration.

[0078] Once priorities of different channels triggered to be transmitted or processed are identified at a UE via indication or implicit configuration, the UE applies the priorities to decide on whether to transmit/process each of them in case of overlap: In case of PDSCH reception scheduled in overlapped resources, a UE can be expected to process the PDSCH with higher associated priority; in accordance with certain specifications, the UE cannot expect to be scheduled with multiple unicast PDSCH reception if the

PDSCHs are scheduled with same priority levels, where the overlap in resources imply either time and frequency domain resources or resources only in the time domain; in case of PUSCH transmission scheduled in overlapped resources, a UE can be expected to transmit the PUSCH with higher associated priority and drop at least overlapped part of the lower priority PUSCH. In case of equal priority, the UE can follow its existing behavior; in case of PUxCH (either PUSCH or PUCCH) transmission scheduled in overlapped resources, the UE can be expected to transmit the higher priority PUxCH and drop the lower priority PUxCH. In case of equal priorities, the UE does multiplexing or dropping according to its existing behavior.

[0079] Referring to FIG. 11 , illustrated an example process flow 1 100 for a network device (e.g., a user equipment (UE), a new radio NB (gNB), 5GC component or the like) can process, generate, or monitor new radio (NR) communication via a 5G network system (5GS) to perform UL transmission based on a set of prioritizations or priority rules or the like.

[0080] The process flow 1 100 initiates at 1 102 with receiving one or more indications of a prioritization among a set of channels / signals, or set of prioritization rules, wherein the prioritization corresponds to at least one of: one or more different physical uplink shared channels (PUSCHs), or one or more different physical uplink control channels (PUCCHs).

[0081] At 1 104, the process flow 1 100 includes processing a first assignment of a first uplink (UL) resource, wherein the first UL resource is associated with a first data transmission in a first PUSCH or in a first control transmission in a first PUCCH. [0082] At 1 106, the process flow 1 100 includes processing a second assignment of a second UL resource, wherein the second UL resource is associated with a second data transmission in a second PUSCH or a second control transmission in a second PUCCH;

[0083] At 1 108, the process flow 1 100 includes activating the prioritization based on the one or more indications to generate a UL transmission comprising the second assignment of the second UL resource and drop another UL transmission comprising the first assignment of the first UL resource, wherein the first resource and the second resource overlap in time or frequency

[0084] As it is employed in the subject specification, the term“processor” can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;

parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices. A processor can also be implemented as a combination of computing processing units.

[0085] Examples can include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples above, or any other method or process described herein.

[0086] A first example is an apparatus configured to be employed at a user equipment (UE) for communication in a 5G network system (5GS) comprising: one or more processors configured to: receive one or more indications of a prioritization among a set of channels / signals, or set of prioritization rules, wherein the prioritization corresponds to at least one of: one or more different physical uplink shared channels (PUSCHs), or one or more different physical uplink control channels (PUCCHs);

process a first assignment of a first uplink (UL) resource, wherein the first UL resource is associated with a first data transmission in a first PUSCH or in a first control transmission in a first PUCCH; process a second assignment of a second UL resource, wherein the second UL resource is associated with a second data transmission in a second PUSCH or in a second control transmission in a second PUCCH; activate the prioritization based on the one or more indications to generate a UL transmission comprising the second assignment of the second UL resource and drop another UL transmission comprising the first assignment of the first UL resource, wherein the first resource and the second resource overlap in at least one of: time or frequency; a radio frequency (RF) interface, configured to provide, to RF circuitry, information / bits for transmitting the second UL transmission.

[0087] A second example can include the first example, wherein the first UL resource comprises a first service type / priority comprising an enhanced Mobile Broadband (eMBB) communication and the second UL resource comprises a second service type / priority comprising an Ultra-Reliable Low-Latency Communication (URLLC).

[0088] A third example can include the first or second example, wherein the one or more processors are further configured to: process the one or more indications from a higher level signaling comprising a UE specific radio resource control (RRC) signaling indicating a prioritization rule or priority values associated with at least one of: the first assignment or second assignment.

[0089] A fourth example can include any one of the first through third examples, wherein the one or more processors are further configured to: process the one or more indications from a downlink control information DCI to activate the prioritization of the first assignment or the second assignment.

[0090] A fifth example can include any one of the first through fourth examples, wherein the one or more processors are further configured to: process the DCI comprising a UL scheduling DCI or an UL grant for a PUSCH in a field pointing to a UE behavior of a plurality of UE behaviors to activate the prioritization.

[0091] A sixth example can include any one of the first through fifth examples, wherein the one or more processors are further configured to: process the UL grant, where UL grant is one of the first assignment or the second assignment, when prioritization comprises at least the one or more PUSCHs.

[0092] A seventh example can include any one of the first through sixth examples, wherein the one or more processors are further configured to: process the DCI comprising a DL scheduling DCI or a DL grant for a PDSCH in a field pointing to a UE behavior of a plurality of UE behaviors to activate the prioritization.

[0093] An eighth example can include any one of the first through seventh examples, wherein the one or more processors are further configured to: process the DL grant, where the DL grant is one of the first assignment or the second assignment, when prioritization comprises at least a HARQ-ACK transmission in the one or more

PUCCHs.

[0094] A ninth example can include any one of the first through eighth examples, wherein the one or more processors are further configured to: perform the prioritization rule based on the one or more indications by executing a first set of rules in response to PUCCH resources overlapping, a second set of rules in response to overlap of the PUCCH resource and a PUSCH transmission, and a third set of rules in response to overlap of PUSCHs.

[0095] A tenth example can include any one of the first through ninth examples, wherein the one or more processors are further configured to: determine, based on the one or more indications, whether the UL transmission is over-written by another trigger; or process the one or more indications by processing an implicit signal comprising a Radio Network Temporary Identifier (RNTI) used in a DCI or a duration of a

transmission occasion, based on at least one of: the first assignment or the second assignment.

[0096] An eleven example can include any one of the first through tenth examples, wherein the one or more processors are further configured to: associate absolute priority values to physical channels; and in response to the physical channels overlapping in time or frequency, determine which of the physical channels to transmit by applying a prioritization rule based on the absolute priority values.

[0097] A twelfth example can be an apparatus configured to be employed at a next generation NodeB (gNB) for a new radio (NR) communication in a 5G network system (5GS) comprising: one or more processors configured to: generate a first assignment of a first UL resource for a first uplink (UL) transmission, wherein the first UL resource is associated with a first data transmission in a first physical uplink shared channel (PUSCH) or a first control transmission in a first physical uplink control channel

(PUCCH); generate a second assignment of a second UL resource for a second (UL) transmission, wherein the second UL resource is associated with a second data transmission in a second PUSCH or a second control transmission in a second PUCCH; and provide the one or more indications to activate one or more prioritization rules in response to the first UL transmission and the second UL transmission overlapping in a time or frequency, wherein the one or more prioritization rules comprise at least one of: different physical uplink shared channels, or different physical uplink control channels; a radio frequency (RF) interface, configured to provide, to RF circuitry, information for transmitting or receiving the NR communication.

[0098] A thirteenth example can include the twelfth example, wherein the one or more processors are further configured to: define the one or more prioritization rules to differentiate handling of different services of uplink control information (UCI) based on different service requirements that correspond to UCIs, respectively.

[0099] A fourteenth example can include the twelfth or thirteenth example, wherein the one or more indications of the one or more prioritization rules initiate dropping the first UL transmission as a first Physical Uplink Control Channel (PUCCH) carrying a first UCI with at least one of: a lower reliability requirement or a lower latency requirement, from the second UL transmission as a second PUCCH carrying a second UCI with at least one of: a higher reliability requirement or a higher latency requirement than the first PUCCH carrying the first UCI.

[00100] A fifteenth example can include the twelfth through fourteenth example, wherein the one or more indications comprises a service flag or a service priority flag in a PUCCH resource configuration, wherein the service flag or service priority flag comprises one or more bit parameters designating a different priority to a service type / service priority from another service type / service priority for the one or more

prioritization rules.

[00101] A sixteenth example can include the twelfth through fifteenth example, wherein the one or more processors are further configured to: generate the one or more indications for prioritization based on a code rate, or a PUCCH resource partition within a PUCCH resource for different service types comprising an Ultra-Reliable Low-Latency Communication (URLLC) and an enhanced Mobile Broadband (eMBB) communication. [00102] A seventeenth example can include the twelfth through sixteenth example, wherein the one or more processors are further configured to: generate the one or more indications for prioritization based on a field in a Downlink Control Information (DCI) to indicate whether a scheduled Physical Downlink Shared Channel (PDSCH)

transmission and corresponding Hybrid Automatic Repeat Request -Acknowledgement (HARQ-ACK) on a Physical Uplink Control Channel (PUCCH) comprises a higher priority in the one or more prioritization rules for a first service type over a second service type.

[00103] An eighteenth example can include the twelfth through seventeenth example, wherein the one or more processors are further configured to: generate the one or more indications to enable a PUSCH carrying at least one of: data or a UCI for URLLC that overlaps with a PUCCH carrying UCI for eMBB in a slot, the PUCCH carrying UCI for eMBB is dropped and the PUSCH carrying at least one of: the data or the UCI for the URLLC is to be transmitted.

[00104] A nineteenth example can include the twelfth through eighteenth example, wherein the one or more processors are further configured to: generate the one or more indications to associate a configured resource with a service type priority for a Type 1 configured grant uplink transmission.

[00105] A twentieth example can include the twelfth through nineteenth example, wherein the one or more processors are further configured to: generate the dynamic indication for Type 2 configured grant uplink transmission or downlink (DL) semi- persistent scheduling (SPS) based physical downlink shared channel (PDSCH), in the activation of Type 2 configured grant uplink transmission or DL SPS PDSCH

transmission, based on a field in a downlink control information (DCI) indicating whether the Type 2 configured grant uplink transmission or DL SPS PDSCH transmission is targeted for different service type priorities with different requirements comprising URLLC or eMBB service.

[00106] A twenty-first example can be a computer readable storage device storing executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) for a new radio (NR) communication via a 5G network system (5GS) to perform operations, the operations comprising: receiving one or more indications of a prioritization among a set of channels / signals, or set of prioritization rules, wherein the prioritization corresponds to at least one of: one or more different physical uplink shared channels (PUSCHs), or one or more different physical uplink control channels (PUCCHs); processing a first assignment of a first uplink (UL) resource, wherein the first UL resource is associated with a first data transmission in a first PUSCH or in a first control transmission in a first PUCCH; processing a second assignment of a second UL resource, wherein the second UL resource is associated with a second data transmission in a second PUSCH or a second control transmission in a second PUCCH; activating the prioritization based on the one or more indications to generate a UL transmission comprising the second assignment of the second UL resource and dropping another UL transmission comprising the first assignment of the first UL resource, wherein the first resource and the second resource overlap in time or frequency.

[00107] A twenty-second example can include the twenty-first example, wherein the prioritization rule differentiates handling of different service types / priorities of uplink control information (UCI) based on different service requirements that correspond to UCIs, respectively, or different data resources and UCIs with the different service types / priorities.

[00108] A twenty-third example can include the twenty-first or twenty-second example, wherein the one or more indications activate the prioritization rule by indicating to drop a first transmission of a first service type / priority over a second transmission of a second service type / priority based on the prioritization rule, wherein the first service type / priority comprises an enhanced Mobile Broadband (eMBB) communication and the second service type / priority comprises an Ultra-Reliable Low- Latency Communication (URLLC).

[00109] Moreover, various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term“machine-readable medium” can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data. Additionally, a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.

[00110] Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term“modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[00111] An exemplary storage medium can be coupled to processor, such that processor can read information from, and write information to, storage medium. In the alternative, storage medium can be integral to processor. Further, in some aspects, processor and storage medium can reside in an ASIC. Additionally, ASIC can reside in a user terminal. In the alternative, processor and storage medium can reside as discrete components in a user terminal. Additionally, in some aspects, the processes and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

[00112] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[00113] In particular regard to the various functions performed by the above described components (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given or particular application.

Claims

CLAIMS What is claimed is:

1. An apparatus configured to be employed at a user equipment (UE) for communication in a 5G network system (5GS) comprising:

one or more processors configured to:

receive one or more indications of a prioritization among a set of channels / signals, or set of prioritization rules, wherein the prioritization corresponds to at least one of: one or more different physical uplink shared channels (PUSCHs), or one or more different physical uplink control channels (PUCCHs);

process a first assignment of a first uplink (UL) resource, wherein the first UL resource is associated with a first data transmission in a first PUSCH or in a first control transmission in a first PUCCH;

process a second assignment of a second UL resource, wherein the second UL resource is associated with a second data transmission in a second PUSCH or in a second control transmission in a second PUCCH;

activate the prioritization based on the one or more indications to generate a UL transmission comprising the second assignment of the second UL resource and drop another UL transmission comprising the first assignment of the first UL resource, wherein the first resource and the second resource overlap in at least one of: time or frequency;

a radio frequency (RF) interface, configured to provide, to RF circuitry, information / bits for transmitting the second UL transmission.

2. The apparatus of claim 1 , wherein the first UL resource comprises a first service type / priority comprising an enhanced Mobile Broadband (eMBB) communication and the second UL resource comprises a second service type / priority comprising an Ultra- Reliable Low-Latency Communication (URLLC).

3. The apparatus of claim 1 , wherein the one or more processors are further configured to: process the one or more indications from a higher level signaling comprising a UE specific radio resource control (RRC) signaling indicating a prioritization rule or priority values associated with at least one of: the first assignment or second assignment.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to: process the one or more indications from a downlink control information DCI to activate the prioritization of the first assignment or the second assignment.

5. The apparatus of claim 4, wherein the one or more processors are further configured to: process the DCI comprising a UL scheduling DCI or an UL grant for a PUSCH in a field pointing to a UE behavior of a plurality of UE behaviors to activate the prioritization.

6. The apparatus of claim 5, wherein the one or more processors are further configured to: process the UL grant, where UL grant is one of the first assignment or the second assignment, when prioritization comprises at least the one or more PUSCHs.

7. The apparatus of claim 4, wherein the one or more processors are further configured to: process the DCI comprising a DL scheduling DCI or a DL grant for a PDSCH in a field pointing to a UE behavior of a plurality of UE behaviors to activate the prioritization.

8. The apparatus of claim 7, wherein the one or more processors are further configured to: process the DL grant, where the DL grant is one of the first assignment or the second assignment, when prioritization comprises at least a HARQ-ACK

transmission in the one or more PUCCHs.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to: perform the prioritization rule based on the one or more indications by executing a first set of rules in response to PUCCH resources overlapping, a second set of rules in response to overlap of the PUCCH resource and a PUSCH transmission, and a third set of rules in response to overlap of PUSCHs.

10. The apparatus of claim 1 , wherein the one or more processors are further configured to:

determine, based on the one or more indications, whether the UL transmission is over-written by another trigger; or

process the one or more indications by processing an implicit signal comprising a Radio Network Temporary Identifier (RNTI) used in a DCI or a duration of a

1 1 . The apparatus of claim 1 , wherein the one or more processors are further configured to:

associate absolute priority values to physical channels; and

in response to the physical channels overlapping in time or frequency, determine which of the physical channels to transmit by applying a prioritization rule based on the absolute priority values.

12. An apparatus configured to be employed at a next generation NodeB (gNB) for a new radio (NR) communication in a 5G network system (5GS) comprising:

one or more processors configured to:

generate a first assignment of a first UL resource for a first uplink (UL) transmission, wherein the first UL resource is associated with a first data transmission in a first physical uplink shared channel (PUSCH) or a first control transmission in a first physical uplink control channel (PUCCH);

generate a second assignment of a second UL resource for a second (UL) transmission, wherein the second UL resource is associated with a second data transmission in a second PUSCH or a second control transmission in a second PUCCH; and

provide the one or more indications to activate one or more prioritization rules in response to the first UL transmission and the second UL transmission overlapping in a time or frequency, wherein the one or more prioritization rules comprise at least one of: different physical uplink shared channels, or different physical uplink control channels; a radio frequency (RF) interface, configured to provide, to RF circuitry, information for transmitting or receiving the NR communication.

13. The apparatus of claim 12, wherein the one or more processors are further configured to: define the one or more prioritization rules to differentiate handling of different services of uplink control information (UCI) based on different service requirements that correspond to UCIs, respectively.

14. The apparatus of claim 12, wherein the one or more indications of the one or more prioritization rules initiate dropping the first UL transmission as a first Physical Uplink Control Channel (PUCCH) carrying a first UCI with at least one of: a lower reliability requirement or a lower latency requirement, from the second UL transmission as a second PUCCH carrying a second UCI with at least one of: a higher reliability requirement or a higher latency requirement than the first PUCCH carrying the first UCI.

15. The apparatus of claim 12, wherein the one or more indications comprises a service flag or a service priority flag in a PUCCH resource configuration, wherein the service flag or service priority flag comprises one or more bit parameters designating a different priority to a service type / service priority from another service type / service priority for the one or more prioritization rules.

16. The apparatus of claim 12, wherein the one or more processors are further configured to: generate the one or more indications for prioritization based on a code rate, or a PUCCH resource partition within a PUCCH resource for different service types comprising an Ultra-Reliable Low-Latency Communication (URLLC) and an enhanced Mobile Broadband (eMBB) communication.

17. The apparatus of claim 12, wherein the one or more processors are further configured to: generate the one or more indications for prioritization based on a field in a Downlink Control Information (DCI) to indicate whether a scheduled Physical Downlink Shared Channel (PDSCH) transmission and corresponding Hybrid Automatic Repeat Request -Acknowledgement (HARQ-ACK) on a Physical Uplink Control Channel (PUCCH) comprises a higher priority in the one or more prioritization rules for a first service type over a second service type.

18. The apparatus of claim 12, wherein the one or more processors are further configured to: generate the one or more indications to enable a PUSCH carrying at least one of: data or a UCI for URLLC that overlaps with a PUCCH carrying UCI for eMBB in a slot, the PUCCH carrying UCI for eMBB is dropped and the PUSCH carrying at least one of: the data or the UCI for the URLLC is to be transmitted.

19 The apparatus of claim 12, wherein the one or more processors are further configured to: generate the one or more indications to associate a configured resource with a service type priority for a Type 1 configured grant uplink transmission.

20. The apparatus of claim 12, wherein the one or more processors are further configured to: generate the dynamic indication for Type 2 configured grant uplink transmission or downlink (DL) semi-persistent scheduling (SPS) based physical downlink shared channel (PDSCH), in the activation of Type 2 configured grant uplink transmission or DL SPS PDSCH transmission, based on a field in a downlink control information (DCI) indicating whether the Type 2 configured grant uplink transmission or DL SPS PDSCH transmission is targeted for different service type priorities with different requirements comprising URLLC or eMBB service.

21 . A computer readable storage device storing executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) for a new radio (NR) communication via a 5G network system (5GS) to perform operations, the operations comprising:

receiving one or more indications of a prioritization among a set of channels / signals, or set of prioritization rules, wherein the prioritization corresponds to at least one of: one or more different physical uplink shared channels (PUSCHs), or one or more different physical uplink control channels (PUCCHs);

processing a first assignment of a first uplink (UL) resource, wherein the first UL resource is associated with a first data transmission in a first PUSCH or in a first control transmission in a first PUCCH; processing a second assignment of a second UL resource, wherein the second UL resource is associated with a second data transmission in a second PUSCH or a second control transmission in a second PUCCH;

activating the prioritization based on the one or more indications to generate a UL transmission comprising the second assignment of the second UL resource and dropping another UL transmission comprising the first assignment of the first UL resource, wherein the first resource and the second resource overlap in time or frequency.

22. The computer readable storage device of claim 21 , wherein the prioritization rule differentiates handling of different service types / priorities of uplink control information (UCI) based on different service requirements that correspond to UCIs, respectively, or different data resources and UCIs with the different service types / priorities.

23. The computer readable storage device of claim 22, wherein the one or more indications activate the prioritization rule by indicating to drop a first transmission of a first service type / priority over a second transmission of a second service type / priority based on the prioritization rule, wherein the first service type / priority comprises an enhanced Mobile Broadband (eMBB) communication and the second service type / priority comprises an Ultra-Reliable Low-Latency Communication (URLLC).