UNEQUAL PROTECTION OF DATA STREAMS

A user equipment (UE), next generation NodeB (gNB), or other network component can operate to configure unequal protection of data packets including a transport block (TB), a medium access control (MAC) packet data unit, or the like into a single physical layer encapsulation for transmission. TBs can be protected unequally within the encapsulation over a single physical channel (e.g., physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or the like) with four or few spatial layers (e.g., two spatial layers). Spatial, time, or frequency resources can be unequally utilized among the different TBs or PDUs of the physical layer transmission, especially to prioritize or secure protection more to a specific TB over another within encapsulation for particular protocols or applications.

FIELD

The present disclosure related to wireless technology, and more specifically, pertains to techniques for unequal protection of data streams.

BACKGROUND

Mobile communication in the next generation wireless communication system, 5G, or new radio (NR) network will provide ubiquitous connectivity and access to information, as well as ability to share data, around the globe. High speed, high reliability and low latency are the key benefits that Communication Service Providers (CSPs) expect from 5G, for example. While high speed helps to upload and download video based content faster and in larger volumes, high reliability supports mission-critical services such as connected robotic factories, and low latency makes delay-critical services such as driverless cars a reality. These network benefits have been a prime reason behind 5G development: high speed (targeted at 10 Gbps) reducing latency down to less than a millisecond, and increasing reliability, and fully justify the use of 5G networks for life-critical services like remote surgery and autonomous driverless cars. With IoT opening up a new world of differentiated services including connected homes, automated factories and a massive build-up of small devices, there will be tremendous business opportunities for the IoT service providers as well as the CSPs. ITU has categorized 5G services have been categorized essentially as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (uRLLC) or massive machine-type communications (mMTC) services. Each of these categories has varying needs for latency, reliability, and connectivity, with the success of uRLLC services being the most dependent on these parameters. With its ultra-reliable, low latency characteristics, uRLLC becomes the category of choice for new services like the autonomous car, industrial automation and extended reality (XR), including virtual reality (VR), augmented reality (AR), cloud gaming and other interactive video streaming applications, as well as modern edge computing significantly extending virtualization technology on edge servers. As such, updating data traffic models continue to be under study and there is a need to do so in a way that enables 5G next generation, new radio (NR) device to evolve based on third generation partnership project (3GPP) long term evolution (LTE)-Advanced technology with additional enhanced radio access technologies (RATs) that enable seamless and faster wireless connectivity solutions using orthogonal frequency division multiplexing (OFDM).

DETAILED DESCRIPTION

As used herein, the term “circuitry” can 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 can be implemented in, or functions associated with the circuitry can be implemented by, one or more software or firmware modules. In some embodiments, circuitry can include logic, at least partially operable in hardware.

In consideration of the above, various aspects/embodiments are disclosed for communications in NR network devices (e.g., user equipment (UE), evolved NodeB (eNB), a next generation NodeB (gNB), a new radio (NR) base station (BS), or the like). With respect to LTE advanced and 5G NR devices, maintaining reliability, low latency and throughput in encoding and decoding streaming data can be enhanced by configuring unequal data partitioning in radio links. In particular, when a radio link is not handled to provide reliable low latency communication (RLLC) with high throughput through all data streams, it is important to protect the most critical ones to protect the UE quality of experience (QoE).

In an aspect, a gNB or UE, for example, can configure a physical layer encapsulation by multiplexing different transport blocks (TBs) for a physical layer transmission with an unequal protection between the different TBs of the physical layer encapsulation, such as on the user plane, packets in the evolved packet core (EPC) network encapsulated in specific EPC protocol and tunneled between a Core Network (CN) component (e.g., an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a packet data network gateway (P-GW), or the like) and the e/gNB, a transmission time interval (TTI), or other parameter(s) for the encapsulation of data from higher layers into frames for transmission within a transmission opportunity on the radio link layer. Various resources, including spatial, frequency or time resources can be unequally used to secure protection of the TBs within the physical layer encapsulation for a single transmission burst. The physical layer encapsulation can be provided to transmitter circuitry that transmits (or receives) the data for a physical layer transmission with unequal protection of the TBs multiplexed therein. This physical layer transmission can be configured with four or less spatial layers via a physical channel (e.g., a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) in a next generation (NR) network.

Additional aspects and details of the disclosure are further described below with reference to figures.

Embodiments described herein can be implemented into a system using any suitably configured hardware, software, or other component.FIG.1illustrates an architecture of a system100including a Core Network (CN)120, for example a Fifth Generation (5G) CN (5GC), in accordance with various embodiments. The system100is shown to include a UE101, which can be the same or similar to one or more other UEs discussed herein; a Third Generation Partnership Project (3GPP) Radio Access Network (Radio AN or RAN) or other (e.g., non-3GPP) AN, (R)AN210, which can include one or more RAN nodes (e.g., Evolved Node B(s) (eNB(s)), next generation Node B(s) (gNB(s), and/or other nodes) or other nodes or access points; and a Data Network (DN)203, which can be, for example, operator services, Internet access or third party services; and a Fifth Generation Core Network (5GC)120. The 5GC120can comprise one or more of the following functions and network components: an Authentication Server Function (AUSF)122; an Access and Mobility Management Function (AMF)121; a Session Management Function (SMF)124; a Network Exposure Function (NEF)123; a Policy Control Function (PCF)126; a Network Repository Function (NRF)125; a Unified Data Management (UDM)127; an Application Function (AF)128; a User Plane (UP) Function (UPF)102; and a Network Slice Selection Function (NSSF)129.

In this example, one or more UEs101are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but can 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 (IC), 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 Communication (MTC) devices, Machine to Machine (M2M), Internet of Things (IoT) devices, and/or the like.

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

The UPF102can act as an anchor point for intra-RAT and inter-RAT mobility, an external Protocol Data Unit (PDU) session point of interconnect to DN103, and a branching point to support multi-homed PDU session. The UPF102can also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF102can include an uplink classifier to support routing traffic flows to a data network. The DN103can represent various network operator services, Internet access, or third-party services. DN103can include, or be similar to, an application server. The UPF102can interact with the SMF124via an N4 reference point between the SMF124and the UPF102.

The AUSF122can store data for authentication of UE101and handle authentication-related functionality. The AUSF122can facilitate a common authentication framework for various access types. The AUSF122can communicate with the AMF121via an N12 reference point between the AMF121and the AUSF122; and can communicate with the UDM127via an N13 reference point between the UDM127and the AUSF122. Additionally, the AUSF122can exhibit an Nausf service-based interface.

The AMF121can be responsible for registration management (e.g., for registering UE101, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF121can be a termination point for the N11 reference point between the AMF121and the SMF124. The AMF121can provide transport for SM messages between the UE101and the SMF124, and act as a transparent proxy for routing SM messages. AMF121can also provide transport for SMS messages between UE101and a Short Message Service (SMS) Function (SMSF) (not shown inFIG.1). AMF121can act as Security Anchor Function (SEAF), which can include interaction with the AUSF122and the UE101and/or receipt of an intermediate key that was established as a result of the UE101authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF121can retrieve the security material from the AUSF122. AMF121can also include a Single-Connection Mode (SCM) function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF121can be a termination point of a RAN Control Plane (CP) interface, which can include or be an N2 reference point between the (R)AN110and the AMF121; and the AMF121can be a termination point of Non Access Stratum (NAS) (N1) signaling, and perform NAS ciphering and integrity protection.

AMF121can also support NAS signaling with a UE101over a non-3GPP (N3) Inter Working Function (IWF) interface. The N3IWF can be used to provide access to untrusted entities. N3IWF can be a termination point for the N2 interface between the (R)AN110and the AMF121for the control plane, and can be a termination point for the N3 reference point between the (R)AN110and the UPF102for the user plane. As such, the AMF121can handle N2 signaling from the SMF124and the AMF121for PDU sessions and QoS, encapsulate/de-encapsulate packets for Internet Protocol (IP) Security (IPSec) and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF can also relay uplink and downlink control-plane NAS signaling between the UE101and AMF121via an N1 reference point between the UE101and the AMF121, and relay uplink and downlink user-plane packets between the UE101and UPF102. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE101. The AMF121can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs121and an N17 reference point between the AMF121and a 5G Equipment Identity Register (5G-EIR) (not shown inFIG.1).

The UE101can be registered with the AMF121in order to receive network services. Registration Management (RM) is used to register or deregister the UE101with the network (e.g., AMF121), and establish a UE context in the network (e.g., AMF121). The UE101can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE101is not registered with the network, and the UE context in AMF121holds no valid location or routing information for the UE101so the UE101is not reachable by the AMF121. In the RM-REGISTERED state, the UE101is registered with the network, and the UE context in AMF121can hold a valid location or routing information for the UE101so the UE101is reachable by the AMF121. In the RM-REGISTERED state, the UE101can perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE101is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF121can store one or more RM contexts for the UE101, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF121can also store a 5GC Mobility Management (MM) context that can be the same or similar to an (Enhanced Packet System (EPS))MM ((E)MM) context. In various embodiments, the AMF121can store a Coverage Enhancement (CE) mode B Restriction parameter of the UE101in an associated MM context or RM context. The AMF121can also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

Connection Management (CM) can be used to establish and release a signaling connection between the UE101and the AMF121over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE101and the CN120, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE101between the AN (e.g., RAN110) and the AMF121. The UE101can operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode.

When the UE101is operating in the CM-IDLE state/mode, the UE101may have no NAS signaling connection established with the AMF121over the N1 interface, and there can be (R)AN110signaling connection (e.g., N2 and/or N3 connections) for the UE101. When the UE101is operating in the CM-CONNECTED state/mode, the UE101can have an established NAS signaling connection with the AMF121over the N1 interface, and there can be a (R)AN110signaling connection (e.g., N2 and/or N3 connections) for the UE101. Establishment of an N2 connection between the (R)AN110and the AMF121can cause the UE101to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE101can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN110and the AMF121is released.

The SMF124can be responsible for Session Management (SM) (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to Lawful Interception (LI) system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining Session and Service Continuity (SSC) mode of a session. SM can refer to management of a PDU session, and a PDU session or “session” can refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE101and a data network (DN)103identified by a Data Network Name (DNN). PDU sessions can be established upon UE101request, modified upon UE101and 5GC120request, and released upon UE101and 5GC120request using NAS SM signaling exchanged over the N1 reference point between the UE101and the SMF124. Upon request from an application server, the 5GC120can trigger a specific application in the UE101. In response to receipt of the trigger message, the UE101can pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE101. The identified application(s) in the UE101can establish a PDU session to a specific DNN. The SMF124can check whether the UE101requests are compliant with user subscription information associated with the UE101. In this regard, the SMF124can retrieve and/or request to receive update notifications on SMF124level subscription data from the UDM127.

The SMF124can include the following roaming functionality: handling local enforcement to apply QoS Service Level Agreements (SLAs) (Visited Public Land Mobile Network (VPLMN)); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs124can be included in the system100, which can be between another SMF124in a visited network and the SMF124in the home network in roaming scenarios. Additionally, the SMF124can exhibit the Nsmf service-based interface.

The NEF123can provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF128), edge computing or fog computing systems, etc. In such embodiments, the NEF123can authenticate, authorize, and/or throttle the AFs. NEF123can also translate information exchanged with the AF128and information exchanged with internal network functions. For example, the NEF123can translate between an AF-Service-Identifier and an internal 5GC information. NEF123can also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF123as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF123to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF123can exhibit an Nnef service-based interface.

The NRF125can support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF125also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like can refer to the creation of an instance, and an “instance” can refer to a concrete occurrence of an object, which can occur, for example, during execution of program code. Additionally, the NRF125can exhibit the Nnrf service-based interface.

The PCF126can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF126can also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM127. The PCF126can communicate with the AMF121via an N15 reference point between the PCF126and the AMF121, which can include a PCF126in a visited network and the AMF121in case of roaming scenarios. The PCF126can communicate with the AF128via an N5 reference point between the PCF126and the AF128; and with the SMF124via an N7 reference point between the PCF126and the SMF124. The system100and/or CN120can also include an N24 reference point between the PCF126(in the home network) and a PCF126in a visited network. Additionally, the PCF126can exhibit an Npcf service-based interface.

The UDM127can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE101. For example, subscription data can be communicated between the UDM127and the AMF121via an N8 reference point between the UDM127and the AMF. The UDM127can include two parts, an application Functional Entity (FE) and a Unified Data Repository (UDR) (the FE and UDR are not shown inFIG.1). The UDR can store subscription data and policy data for the UDM127and the PCF126, and/or structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, application request information for multiple UEs101) for the NEF123. The Nudr service-based interface can be exhibited by the UDR221to allow the UDM127, PCF126, and NEF123to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM can include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different FEs can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. The UDR can interact with the SMF124via an N10 reference point between the UDM127and the SMF124. UDM127can also support SMS management, wherein an SMS-FE implements similar application logic as discussed elsewhere herein. Additionally, the UDM127can exhibit the Nudm service-based interface.

The AF128can provide application influence on traffic routing, provide access to NEF123, and interact with the policy framework for policy control. 5GC120and AF128can provide information to each other via NEF123, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE101access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF102close to the UE101and execute traffic steering from the UPF102to DN103via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF128. In this way, the AF128can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF128is considered to be a trusted entity, the network operator can permit AF128to interact directly with relevant NFs. Additionally, the AF128can exhibit an Naf service-based interface.

The NSSF129can select a set of network slice instances serving the UE101. The NSSF129can also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed Single NSSAIs (S-NSSAIs), as appropriate. The NSSF129can also determine the AMF set to be used to serve the UE101, or a list of candidate AMF(s)121based on a suitable configuration and possibly by querying the NRF125. The selection of a set of network slice instances for the UE101can be triggered by the AMF121with which the UE101is registered by interacting with the NSSF129, which can lead to a change of AMF121. The NSSF129can interact with the AMF121via an N22 reference point between AMF121and NSSF129; and can communicate with another NSSF129in a visited network via an N31 reference point (not shown inFIG.1). Additionally, the NSSF129can exhibit an Nnssf service-based interface.

As discussed previously, the CN120can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE101to/from other entities, such as an SMS-Gateway Mobile services Switching Center (GMSC)/Inter-Working MSC (IWMSC)/SMS-router. The SMSF can also interact with AMF121and UDM127for a notification procedure that the UE101is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM127when UE101is available for SMS).

The CN120can also include other elements that are not shown inFIG.1, such as a Data Storage system/architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system can include a Structured Data Storage Function (SDSF), an Unstructured Data Storage Function (UDSF), and/or the like. Any NF can store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown inFIG.1). Individual NFs can share a UDSF for storing their respective unstructured data or individual NFs can each have their own UDSF located at or near the individual NFs. Additionally, the UDSF can exhibit an Nudsf service-based interface (not shown inFIG.1). The 5G-EIR can be an NF that checks the status of Permanent Equipment Identifier (PEI) for determining whether particular equipment/entities are blacklisted from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there can be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted fromFIG.1for clarity. In one example, the CN120can include an Nx interface, which is an inter-CN interface between the MME (e.g., a non-5G MME) and the AMF121in order to enable interworking between CN120and a non-5G CN. Other example interfaces/reference points can include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

According to various embodiments, the UEs101and the RAN nodes110communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum can include channels that operate in the frequency range of approximately 400 MHz to approximately 2.8 GHz, whereas the unlicensed spectrum can include the 5 GHz band.

Medium/carrier sensing operations can be performed according to a listen-before-talk (LBT) protocol. LBT is a mechanism whereby network devices/equipment senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation can include Clear Channel Assessment (CCA), which utilizes at least energy detection (ED) to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED can include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

In some implementations, the LBT procedure for downlink (DL) or uplink (UL) transmission bursts including physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmissions, respectively, can have an LAA contention window that is variable in length between X and Y extended CCA (ECCA) slots, where X and Y are minimum and maximum values for the contention window sizes (CWSs) for LAA. In one example, the minimum CWS for an LAA transmission can be 9 microseconds (μs); however, the size of the CWS and a maximum channel occupancy time (MCOT) (e.g., a transmission burst, or transmission opportunity) can be based on governmental regulatory requirements.

The LAA mechanisms are built upon carrier aggregation (CA) technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a component carrier (CC). A CC can have a bandwidth of 1.4, 2, 5, 10, 15 or 20 MHz and a maximum of about five CCs or otherwise can be aggregated, and therefore, a maximum aggregated bandwidth can be about 100 MHz, for example. In frequency division duplex (FDD) systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In time division duplex (TDD) systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells can differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell can provide a primary component carrier (PCC) for both UL and DL, and can handle radio resource control (RRC) and non-access stratum (NAS) related activities. The other serving cells are referred to as SCells, and each SCell can provide an individual secondary component carrier (SCC) for both UL and DL. The SCCs can be added and removed as required, while changing the PCC can require the UE101to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs101. The physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It can also inform the UEs101about the transport format, resource allocation, and Hybrid Automatic Repeat Request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE101bwithin a cell) can be performed at any of the RAN nodes111based on channel quality information fed back from any of the UEs101. The downlink resource assignment information for scheduling grants (e.g., dynamic grant or the like) can be sent on the PDCCH used for (e.g., assigned to) each of the UEs101.

The RAN110is shown to be communicatively coupled to a core network—in this embodiment, core network (CN)120. The CN120can comprise a plurality of network elements122, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs101) who are connected to the CN120via the RAN110. The components of the CN120can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV can be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums. A logical instantiation of the CN120can be referred to as a network slice, and a logical instantiation of a portion of the CN120can be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more Evolved Packet Core (EPC) components/functions.

FIG.2is an illustration of a control plane protocol stack in accordance with various aspects described herein. In this embodiment, a control plane200is shown as a communications protocol stack between the UE101, the RAN node111, and the AMF121, SMF123, or a mobility management entity (MME).

The PHY layer201may transmit or receive information used by the MAC layer202over one or more air interfaces. The PHY layer201may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer205. The PHY layer201may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer202may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

The RLC layer203may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer203may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer203may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

The PDCP layer204may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

The main services and functions of the RRC layer205may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.

The UE101and the RAN node111may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer201, the MAC layer202, the RLC layer203, the PDCP layer204, and the RRC layer205.

The non-access stratum (NAS) protocols206form the highest stratum of the control plane between the UE101and the MME121. The NAS protocols206support the mobility of the UE101and the session management procedures to establish and maintain IP connectivity between the UE101and the P-GW or AMF.

The S1 Application Protocol (S1-AP) layer215may support the functions of the S1 interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node111and the CN120. The S1-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer)22may ensure reliable delivery of signaling messages between the RAN node111and the MME121based, in part, on the IP protocol, supported by the IP layer213. The L2/N2 layer212and the L1/N1 layer211may refer to communication links (e.g., wired or wireless) used by the RAN node and the AMF, SMF, or MME to exchange information. The RAN node111and the MME or AMF121may utilize an interface to exchange control plane data via a protocol stack comprising the L1/N1 layer211, the L2/N2 layer212, the IP layer213, the SCTP layer214, and the S1-AP layer215, for example.

Referring toFIG.3, illustrated is a block diagram of a user equipment (UE) device or other network device/component (e.g., gNB, eNB, or other participating network entity/component). The device300includes one or more processors310(e.g., one or more baseband processors) comprising processing circuitry and associated interface(s), transceiver circuitry320(e.g., comprising 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 memory310(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)310or transceiver circuitry320).

In addition, the memory330(as well as other memory components discussed herein, e.g., memory, data storage, or the like) can comprise one or more machine-readable medium/media including instructions that, when performed by a machine or component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device). Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions. Also, any connection can also be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a 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 medium. As described in greater detail below, system400can facilitate greater power efficiency for data streaming operations, including XR data streaming, including AR, VR, or other data streaming reporting/feedback based on a hierarchical (pre)coding scheme.

In an aspect, the UE/gNB device300can operate to configure by processing/generating/encoding/decoding a physical layer transmission comprising multiple different transport blocks (TBs) based on an unequal protection between the different TBs in a physical layer encapsulation (e.g., EPC packets, a transmission opportunity, MCOT, a single transmission burst, a TTI or other encapsulation protocol or related encapsulation parameter(s) for the encapsulation of data from higher layers into frames for transmission over the air. The physical layer transmission can be received, transmitter, or provide(d) with communication/transmitter circuitry320to similarly process/generate the physical layer transmission with four or less spatial layers via a physical channel in an NR network.

Multiple media access control (MAC) packet data units (PDUs) or TBs can be transmitted, for example, over a single physical channel (e.g., PDSCH or PUSCH) with four or less spatial layers together. Spatial multiplexing can be utilized to transmit multiple layers as multiple parallel transmission on a same time/frequency resource to the same device. Multiple antennas at the transmitter and receiver sides in combination can be used to process interference between the different layers. However, securing error loss in RLLC communications, for example, in data streaming with multiple layers can be further enhanced with unequal error protection of different TBs in one physical layer encapsulation being transmitted as differently coded signals being streamed from each of multiple antennas. One additional benefit with multiplexing multiple MAC PDUs into the same physical channel is to avoid inter-modulation distortion in uplink with an alternative transmission scheme where two PUSCHs carrying one MAC PDU respectively overlap in the time domain; with the disclosed approaches, the UE power amplifier can operate at higher transmission power compared with the case with the alternative approach.

Spatial layer signaling can multiplex transmissions of different data streams using a multi-stream transmission and increased throughput for spatial multiplexing in comparison with traditional single layer transmission. For XR related enhancements, for example, better support for video traffic can be an utmost importance, and key to enabling such enhancements. Low latency, high reliability and high throughput are challenging to be achieved at the same time. When a radio link is not handled to provide RLLC with high throughput for all data streams, it is important to protect the most critical ones to maintain the UE300experience. Thus, various transmission schemes for unequal error protection for different video streams can be configured, and also related to the HARQ feedback operation.

In an aspect, MAC PDUs or TBs in a same PDSCH/PUSCH can be transmitted with different protection levels, different error protection, different data protections among the different PDUs or TBs. Thus, a first TB, for example, can be configured in the encoding of the physical layer encapsulation with a different protection level that is greater than or more protected than a second TB in the same physical layer encapsulation. The UE101or gNB110(e.g., device300) can operate to configure partitions of the different TBs of the physical layer encapsulation with different portions of at least one of: spatial, time or frequency resources among the different TBs of the physical layer encapsulation in order to protect one TB of a same physical layer encapsulation in a physical channel than the other. For example, different modulation bits can be used for different MAC PDUs (e.g., more reliable bits in 16 QAM used for a first MAC PDU or TB). Additionally, or alternatively, different MCS levels can be used among the different TBs or MAC PDUs. MAC PDUs can also be configured rather than TBs herein this disclosure, or vice versa. Additionally, or alternatively, different portions of frequency resources can be used for configuring the different TBs or MAC PDUs. Additionally, or alternatively, different spatial layers can be used for configuring the different TBs or MAC PDUs. Additionally, or alternatively, repeated transmissions of the TBs or MAC PDUs can be configured (e.g., a first TB can be configured to appear in more repetitions than the other within the same physical layer encapsulation or physical channel transmission).

While the methods or process flows are illustrated and described herein as a series of acts (process flow steps, events, or operations), it will be appreciated that the illustrated ordering of such acts are not to be interpreted in a limiting sense. For example, some acts may occur in different orders/concurrently with other acts or events apart from those illustrated/described herein. In addition, not all illustrated acts may be necessarily utilized to implement one or more aspects or embodiments of the description in this disclosure. Further, one or more of the acts depicted herein may be carried out in one or more separate acts/phases.

Referring toFIG.4, illustrated is an example process flow400for configuring unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communications, such as ultra RLLC, RLLC, IoT or other connected components. At402, the method400initiates with encoding a physical layer transmission in a physical layer encapsulation comprising different TBs based on unequal protection of the TBs in the physical layer encapsulation, in which the TBs can correspond to different data streams or different parameters, formatting, syntax, or other characteristics of one or more data streams.

At404, the method further comprises providing the physical layer encapsulation (or transmission comprising the encapsulation) to transmitter circuitry to transmit the physical layer transmission via a physical channel, such as a PDSCH for downlink from a gNB110to the UE101, or a PUSCH for uplink from a UE101to the gNB110.

In an aspect, different TBs can be generated or encoded with different protection levels between at least a first TB and a second TB in the physical layer encapsulation. The different TBs that are encoded can be provided the physical layer encapsulation for the physical layer transmission via the PUSCH by the UE. When receiving the physical layer encapsulation with different TB therein as a single physical channel transmission from the gNB, the UE can process or decode these TBs multiplexed into the single physical layer encapsulation in response to receiving PDSCH. Likewise, a gNB can encode multiple TBs into a physical layer encapsulation for transmission via a single PDSCH transmission, while decoding the same configuration upon receiving a similar physical layer encapsulation multiplexed into one TB with multiple different TBs via the PUSCH. Each TB can be associated with a different data stream or coded data (e.g., scalable video coding, or the like) and configured with unequal protection within the encapsulation according to varies aspects/embodiments herein. The gNB or UE can configure the TBs in the encapsulation for transmission and reception based on four or less spatial layers.

Referring toFIG.5, illustrated is an example process flow500for configuring unequal protection of one or more data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication (e.g., uRLLC, RLLC, or the like). Process flow500can flow from any one or more of the process flow acts ofFIG.4as illustrated via A and connect to acts (502,504) of process flow500at any position or order. The UE101and gNB111can comprise a constellation component520that is configured to encode/decode/generate/process modulation bits of a QAM constellation; although a 16 bit QAM constellation is illustrated, for example, any other configuration or number of bits can also be utilized herein. For example, the UE101or gNB110can be configured to encode if transmitting via PUSCH, or decode if receiving via PDSCH, the different TBs based on one or more first modulation bits associated with a first TB and one or more second modulation bits associated with a second TB at502. At504, the constellation component520can be further configured to configure unequal protection among the TBs by configuring a different number of modulation bits at a constellation point of the QAM constellation of the constellation component520.

In aspect, the constellation component520can generate (encode) or process (decode) a first TB with a most reliable bit of the constellation. For example, a least significant bit of a constellation point can be utilized for the first TB to provide greater reliability or protection to the first TB than a second TB of the physical layer encapsulation in transmission. The constellation component520can further utilize one or more other bits of the same constellation to determine the unequal protection between the different TBs of a physical layer encapsulation for the second TB. Alternatively, or additionally, a different number of bits of a constellation point can be configured to different TBs to provide a greater or lesser protection between TBs of the physical layer encapsulation. For example, while the first TB is modulated based on a most reliable bit (e.g., LSB it or other more reliable bit based on signal strength, direction, or other parameter), the second TB can have two to four bits used for encoding or decoding within the physical layer encapsulation, for example. Although four bits are illustrated for each point, the disclosure is not limited necessarily to any specific number for utilizing the unequal protection of TBs or MAC PDUs, for example.

In an aspect, a determination can be made of a total TB size or total TB coded bit number according to a predefined formulation/function. Based on this total TB coded bit number, one or more percentages of the total TB coded bit number can be dynamically configured. A total TB coded bit number of the physical layer encapsulation can be configured based on a predefined formula, and then a first TB size of a first TB of the different TBs can be configured based on a first percentage of the total coded bit number. The second TB size of a second TB of the different TBs can be based on a second percentage. In one example, a total number of TB coded bits can be determined as 100 coded bits per PRB, in which there can be 20 PRBs in PDSCH, in total being 20×100 coded bits. The first TB and the second TB can be partitioned between the coded bits according to 25%+75%, or 50%+50%, etc. With 50%+50%, each has 10×100 coded bits, but the MCS level of each TB's can be different, so that, for example, a first TB has 100 information carrying bits, TB2has 200 information carrying bits, so though they may consume a similar number of coded bits, the reliability can still be configured to be different between them.

The percentage, reliability, total TB coded bit size, or other parameter(s) related to unequal protection of the different TBs can be determined according to the constellation component520of respective devices (UE101, gNB110), signaled via an RRC layer signaling dynamically per one or more physical layer transmissions, a MAC control element (MAC CE), higher layer signaling, or provided via a dynamic grant PUSCH for PUSCH transmission by a PDCCH. A configured grant CG Type 1, or CG Type 2, in which only the first transmission can be scheduled via a downlink control information (DCI), for example, can also enable the unequal protection for the UE101by the gNB110. For PDSCH transmissions, a dynamic grant PDSCH (which is scheduled by a PDCCH), or DL SPS, in which only the first reception is scheduled by a DCI), can be utilized to configure the different TBs in the physical layer encapsulation with unequal protection. The aspects of this disclosure are not necessarily limited to any one type of signaling for configuring single physical channel transmission with unequal protection between TBs in the physical layer encapsulation. The constellation component520or processor of the UE101/gNB110, for example, can be configured to receive a parameter to determine the unequal protection among the different TBs of the physical layer encapsulation via the MAC CE, RRC signaling, or a higher layer signaling. This parameter(s) can be related to a spatial resource, a time resource, or a frequency resource for communications in an NR network, for example.

As discussed within this disclosure, the protection of the TBs can be configured based on a priority assigned to either TB based on the data stream type it is associated with or an additional data stream type, for example, with less or more resolution, or other parameter (e.g., a particular application, protocol, or format) of communication streaming. For example, in order to support a DL error protection for a video codecs a checkerboard pattern of data can be configured with two different types of data based on one or more semantic encodings, syntax formats or error detections. As such packages or physical layer encapsulations can be generated to target data or resources in TBs for different types of data. Thus, if one survives transmission, but the other is lost, a QoE can be maintained, especially within NR network communications for RLLC.

Referring toFIG.6, illustrated is an example process flow600for configuring unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication. Process flow600can flow from any one or more of the process flow acts ofFIG.4or5, as illustrated via A/B and connect to acts of process flow600at any position or order.

At602, the different TBs can be encoded or decoded within the physical layer encapsulation based on different modulation coding schemes (MCS) levels. One or more first TBs of the different TBs can be encoded with a first MCS level and one or more second TBs of the different TBs with a second MCS level that is different than the first MCS level to provide different protections to the different TBs within the physical layer encapsulation. For example, a first TB in the physical layer encapsulation can be protected with an MCS level 2, and a second TB in the physical layer encapsulation protected with MCS level 5. A lower MCS level can provide a better protection, and thus, different levels of protections can be configured for the TBs multiplexed into a single physical layer encapsulation in a single physical channel.

At604, an MCS level for configuring the different TBs of the physical layer encapsulation can be determined/adjusted dynamically. The signal or indication being signaled of an MCS level associated with the first or second TB of the different TBs can be generated or received for the unequal protection of TBs being encoded/decoded.

In an aspect, one MCS level can be signaled and another be derived based on an adjustment factor comprising a correlation to the first MCS level by a mathematical operation, for example, in order to have a differentiation between MCS levels of TBs in the encapsulation. In one example, a first MCS level can be based on/configured in a DCI and the second MCS level of another TB of the physical layer encapsulation can be a function of the first MCS level. Alternatively, or additionally, a pair of MCSs to encode/decode the different TBs can be determined via an RRC signaling associated with at least one of: a downlink (DL) semi-persistent scheduling (SPS) or an uplink (UL) configured grant (CG). Alternatively, or additionally, the different TBs of the physical layer encapsulation can be configured to be encoded, or decoded, based on a predefined pair of MCSs, respectively, in response to UL CG comprising a CG Type 1.

In another aspect, rather than utilizing a fixed MCS delta or adjustment factor, or MAC CE/RRC configured MCS level pairs, can configured similarly to a Transport Format Combination Indicator (TFCI) as in Universe Mobile Telecommunication Systems (UMTS) to enable the combination of transport blocks to be signaled.

Referring toFIG.7, illustrated is an example process flow700for configuring unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication. Process flow700can flow from any one or more of the process flows acts ofFIG.4,5, or6, as illustrated via A/B/C and connect to acts of process flow700at any position or order.

At702, the process flow comprises determining a list or a set of MCS levels via an RRC signaling, a higher layer signaling, a MAC CE signaling, or a DCI. The set can include one or more pairs, triplets, or otherwise sets of MCS levels configured to be associated for use with two or more different TBs being encapsulated in a physical layer encapsulation, for example.

At704, a plurality of MCSs (e.g., pair, triplet, etc.) can be selected from among the set of MCS levels based on a MCS field from a dynamic grant signaling. For example, a combination pair or other grouping (e.g., MCS 2, MCS 5), (MCS 8, MCS 10), (MCS 10, MCS 12)) can be signaled that can comprises different sets of two or more MCS grouped together to correspond to the different TBs to be encoded/decoded in the physical layer encapsulation.

At706, the different TBs of the physical layer encapsulation can be encoded based on the selected plurality of MCSs, respectively, to transmit in the physical layer transmission via a PUSCH, or decoded based on the indicated/selected plurality of MCSs, respectively, via a PDSCH.

In an aspect, an MCS level for the first TB can be signaled via a DCI. For example, if an “MCS field” indicates “1”, then (MCS 8, MCS 10) could selected for a first TB and a second TB, respectively. Here, the “MCS field” of any signaling can be repurposed to indicate a selected grouping (e.g., pair) of MCS levels among the set of MCS levels. Additionally, or alternatively, an MCS level for the second TB can be derived by an adjustment factor or a delta function with respect to the MCS level of the first TB.

In an aspect, the different TBs of the physical layer encapsulation can be encoded based on the selected plurality of MCSs, respectively, for the PUSCH with a CG Type 2, or decoded based on the plurality of MCSs, respectively, for the PDSCH with a DL semi-persistent scheduling (SPS).

Referring toFIG.8, illustrated is an example process flow800for configuring unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication. Process flow800can flow from any one or more of the process flows acts ofFIG.4,5,6, or7as illustrated via A/B/C and connect to acts of process flow700at any position or order.

At802, a partitioning ratio can be signaled (e.g., via DCI, or other signaling) to enable encoding or decoding of the different TBs of the physical layer encapsulation with the different portions based on the partitioning ratio. Alternatively, or additionally, the different TBs can be partitioned based on at least one of: a wideband partitioning or a distributed partitioning.

At804, the process flow comprises configuring different portions of frequency resources to the different TBs in the encapsulation based on the partitioning ratio, a predefined number of physical resource blocks (PRBs) to a first TB and a remainder of PRBs of frequency resources to a second TB for wideband partitioning, or a first number of resource elements of a PRB to the first TB and a second number to the second TBs for distributed partitioning

In aspect, partitioning with a partitioning ratio, for example, can comprise a percentage of resources (e.g., frequency, spatial, or time) to a first TB (e.g., 60%) and the remainder of the granted resources to another TB (e.g., 40%). This partitioning can be signaled (e.g., a field of a DCI), determined on sight, or other wise signaled (RRC, or higher layer).

The wide partitioning can be associated to wideband or distributed partitioning as utilized in FDM for uRLLC. In wideband partitioning, a number of PRBs can be allocated to a first TB, while a remainder to the second TB multiplexed in one physical layer encapsulation of a transmission. With distributed partitioning, some resource elements (REs) in a PRB can be used for the first TB and some for the second TB.

Referring toFIG.9, illustrated is an example process flow900for configuring unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication. Process flow900can flow from any one or more of the process flows acts ofFIG.4,5,6,7, or8as illustrated via A/B/C/D/E and connect to acts of process flow900at any position or order.

At902, different TBs of a physical layer encapsulation of a physical channel transmission can be partitioned with a partitioning of different spatial layers. For example, a first TB can be configured or associated with a first set of spatial layers that comprise a greater reliability than a second set of spatial layers associated with a second TB of the different TBs. The reliability can be a signal strength, direction, angle of depth, or other associated transmission parameter(s) for spatial layer transmissions. For example, the first set of spatial layers can comprise two spatial layers associated with one or more demodulation reference signal (DMRS) indices of the first TB and the second set of spatial layers comprises another two spatial layers. Alternatively, or additionally, the first set of spatial layers can comprise less spatial layers than the second set of spatial layers.

At904, a UE (e.g., UE101) can be configured receive a spatial layer-to-TB mapping via at least one of: an RRC signaling, a MAC CE, or a dynamic grant signaling to partition the different TBs of the physical layer encapsulation based on the spatial layer-to-TB mapping. Alternatively, or additionally, a gNB110can be configured to transmit such spatial layer-to-TB mapping to indicate a number or type of spatial layers to be associated with each TB of the physical layer encapsulation. For example, a signaling or spatial layer-to-TB mapping can indicate any one or more of the following for one or more physical layer transmissions with a single physical layer encapsulation being multiplexed with two TBs with four or less spatial layers: {spatial layers 1 & 3 for transport block 1, spatial layers 2 & 4 for transport block 2}, {spatial layers 1 & 2 for transport block 1, spatial layers 3 & 4 for transport block 2}.

Referring toFIG.10, illustrated is an example physical layer encapsulation1010with a first TB and a second TB combined with unequal protections or different protection levels (e.g., a first TB1020more heavily protected than a second TB1030, or other TBs). Different TBs can be generated or processed with the unequal protection to the different TBs by partitioning repetitions among the physical layer encapsulation (e.g., a transmission opportunity, TTI, Frame, transmission burst, or other encapsulation) for a physical channel unequally based on a number of repetitions or slot resources. For example, a first TB can comprises more repetitions among repetition1020and1030than a second TB of the physical layer encapsulation, as well as include a greater number of resource elements in a slot or slots of each repetition to have different protection levels.

Referring toFIG.11, illustrated is an example process flow900for configuring hybrid automatic repeat request (HARQ) feedback according to unequal protection of data streams or associated TBs of a physical layer encapsulation in an NR network between a gNB and UE (e.g., UE101or gNB110) for wireless communication. Process flow1100can flow from any one or more of the process flows acts ofFIG.4,5,6,7,8or9as illustrated via A/B/C/D/E/F and connect to acts of process flow900at any position or order.

At1102, in response to receiving two or more TBs multiplexed into one physical channel, the UE101can generate a hybrid automatic repeat request (HARQ) feedback for a first TB configured based on a high priority HARQ codebook and another HARQ feedback for a second TB configured based on a low priority HARQ codebook that is lower in priority than the high priority HARQ codebook. Here, the priority of each TB can be treated equally for HARQ feedback. In an aspect, the UE101can generate HARQ feedback based on a bit width that is a function of a number of TBs (e.g., a maximum number of TBs) multiplexed into a physical downlink shared channel (PDSCH) for at least one of: a Type 1 HARQ codebook, a Type 2 HARQ codebook, or a Type 3 HARQ codebook.

Alternatively, or additionally, the UE101can generate the HARQ feedback only for the first TB configured based on the high priority HARQ codebook. Alternatively, or additionally, the UE101can generate the HARQ feedback only for the second TB configured based on the low priority HARQ codebook.

Examples (embodiments) can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.

In example 1, a baseband processor of a network entity, configured to encode a physical layer transmission in a physical layer encapsulation comprising different transport blocks (TBs) based on an unequal protection between the different TBs in the physical layer encapsulation; and transmit the physical layer transmission via a physical channel of a next generation (NR) network.

In example 2, the baseband processor is further configured to encode the different TBs with different protection levels between at least a first TB and a second TB in the physical layer encapsulation and provide the physical layer encapsulation for the physical layer transmission via a physical uplink share channel (PUSCH), or decode other TBs multiplexed in another physical layer encapsulation in response to receiving a physical downlink shared channel (PDSCH).

In example 3, the baseband processor is further configured to encode the different TBs based on one or more first modulation bits associated with a first TB and one or more second modulation bits associated with a second TB, wherein the one or more first modulation bits comprise a higher reliability than the one or more second modulation bits at a constellation point of a QAM constellation.

In example 4, the baseband processor is further configured to encode the different TBs based on the unequal protection by associating the different TBs in the physical layer encapsulation with a different number of modulation bits at the constellation point.

In example 5, the baseband processor is further configured to encode, a first TB of the different TBs based on a least significant bit of a constellation point and a second TB of the different TBs based on one or more remaining bits of the constellation point.

In example 6, the baseband processor is further configured to determine a total TB coded bit number of the physical layer encapsulation based on a predefined formula, and a first TB size of a first TB of the different TBs based on a first percentage of the total TB coded bit number and a second TB size of a second TB of the different TBs based on a second percentage of the total TB coded bit number.

In example 7, the baseband processor is further configured to receive a parameter to determine the unequal protection among the different TBs of the physical layer encapsulation via a media access control (MAC) control element (MAC CE), a radio resource control (RRC) signaling, or a higher layer signaling.

In example 8, the baseband processor is further configured to encode the different TBs of the physical layer encapsulation based on different modulation coding scheme (MCS) levels by encoding one or more first TBs of the different TBs with a first MCS level and one or more second TBs of the different TBs with a second MCS level that is different than the first MCS level to provide different protections to the different TBs within the physical layer encapsulation.

In example 9, the baseband processor is further configured to determine the first MCS level based on a downlink control information (DCI) and the second MCS level as a function of the first MCS level.

In example 10, the baseband processor is further configured to determine a pair of MCSs to encode the different TBs via an RRC signaling associated with at least one of: a downlink (DL) semi-persistent scheduling (SPS) or an uplink (UL) configured grant (CG).

In example 11, the baseband processor is further configured to encode, the different TBs of the physical layer encapsulation based on a predefined pair of MCSs, respectively, in response to an UL CG comprising a CG Type 1.

In example 12, the baseband processor is further configured to: determine a set of MCSs via an RRC signaling, or a MAC CE signaling; select a plurality of MCSs from among the set of MCSs based on a MCS field from a dynamic grant signaling; and encode the different TBs of the physical layer encapsulation based on the plurality of MCSs, respectively, to transmit in the physical layer transmission via a physical uplink shared channel (PUSCH), or decode other TBs multiplexed in another physical layer encapsulation based on the plurality of MCSs, respectively, via a physical downlink shared channel (PDSCH).

In example 13, the baseband processor is further configured to encode the different TBs of the physical layer encapsulation based on the plurality of MCSs, respectively, for the PUSCH with a CG Type 2, or decode the other TBs of the another physical layer encapsulation based on the plurality of MCSs, respectively, for the PDSCH with a DL semi-persistent scheduling (SPS).

In example 14, the baseband processor is further configured to partition the different TBs of the physical layer encapsulation with different portions of at least one of: spatial, time or frequency resources among the different TBs of the physical layer encapsulation.

In example 15, the baseband processor is further configured to receive a partitioning ratio in a DCI, and encode the different TBs of the physical layer encapsulation with the different portions based on the partitioning ratio.

In example 16, the baseband processor is further configured to partition the different TBs based on at least one of: a wideband partitioning or a distributed partitioning.

In example 17, the wideband partitioning comprises configuring a predefined number of physical resource blocks (PRBs) to a first TB of the different TBs and a remainder of PRBs of frequency resources to a second TB of the different TBs, and the distributed partitioning comprises configuring a first number of resource elements of a PRB to the first TB and a second number of resource elements of the PRB to the second TB.

In example 18, the baseband processor is further configured to partition different spatial layers with the different TBs of the physical layer encapsulation, wherein a first TB is associated with a first set of spatial layers comprising a greater reliability than a second set of spatial layers associated with a second TB of the different TBs.

In example 19, the first set of spatial layers comprises two spatial layers associated with one or more demodulation reference signal (DMRS) indices of the first TB and the second set of spatial layers comprises another two spatial layers, or the first set of spatial layers comprises less spatial layers than the second set of spatial layers.

In example 20, the baseband processor is further configured to receive a spatial layer-to-TB mapping via at least one of: an RRC signaling, a MAC CE, or a dynamic grant signaling to partition the different TBs of the physical layer encapsulation based on the spatial layer-to-TB mapping.

In example 21, the baseband processor is further configured to generate the unequal protection to the different TBs by partitioning repetitions among a transmission opportunity unequally, wherein a first TB comprises more repetitions than a second TB of the physical layer encapsulation.

In example 22, the first TB comprises a greater amount of resource elements among the repetitions than the second TB.

In example 23, the processor is further configured to: in response to transmitting two or more TBs multiplexed into the physical layer encapsulation via one physical channel: receive a hybrid automatic repeat request (HARQ) feedback for a first TB configured based on a high priority HARQ codebook and another HARQ feedback for a second TB configured based on a low priority HARQ codebook that is lower in priority than the high priority HARQ codebook; receive the HARQ feedback only for the first TB configured based on the high priority HARQ codebook; or receive the HARQ feedback only for the second TB configured based on the low priority HARQ codebook.

In example 24, the network entity comprises a user equipment (UE).

In example 2, the network entity comprises a base station.

In example 26, a baseband processor of a network entity, configured to: receive the physical layer transmission via a physical channel in a next generation (NR) network; and decode a physical layer encapsulation by multiplexing different transport blocks (TBs) for a physical layer transmission based on an unequal protection between the different TBs of the physical layer encapsulation.

In example 27, the baseband processor is further configured to decode a first TB of the different TBs based on a first bit or a least significant bit that is more reliable than other bits of a constellation point and a second TB of the different TBs based on one or more other bits of the constellation point to determine the unequal protection among the different TBs in the physical layer encapsulation.

In example 28, the baseband processor is further configured to determine a first TB size of a first TB of the different TBs based on a first percentage of a total TB coded bit number and a second TB size of a second TB of the different TBs based on a second percentage of the total TB coded bit number.

In example 29, the baseband processor is further configured to determine a parameter to encode the unequal protection among the different TBs of the physical layer encapsulation based on a media access control (MAC) control element (MAC CE), a radio resource control (RRC) signaling, or a higher layer signaling.

In example 30, the baseband processor is further configured to decode the different TBs of the physical layer encapsulation based on different modulation coding scheme (MCS) levels associated with the different TBs, or provide a downlink control information (DCI) comprising an indication of an MCS level for multiplexing a first TB with a second TB associated with the different MCS levels of a physical layer encapsulation via a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH).

In example 31, the processor is further configured to determine a pair of MCSs to encode the different TBs via an RRC signaling associated with at least one of: a downlink (DL) semi-persistent scheduling (SPS) or an uplink (UL) configured grant (CG).

In example 32, the processor is further configured to: determine a set of MCSs via an RRC signaling, or a MAC CE signaling; select a plurality of MCSs from among the set of MCSs based on an MCS field for a dynamic grant signaling; and configure the different TBs of the physical layer encapsulation based on the plurality of MCSs, respectively, to transmit the physical layer transmission for a physical uplink shared channel (PUSCH), or configure other TBs multiplexed in another physical layer encapsulation based on the plurality of MCSs, respectively, for a physical downlink shared channel (PDSCH).

In example 33, the processor is further configured to encode the different TBs of the physical layer encapsulation based on the plurality of MCSs, respectively, for the PDSCH with a configured grant (CG) Type 2, or decode the other TBs of the another physical layer encapsulation based on the plurality of MCSs, respectively, for the PUSCH with a downlink (DL) semi-persistent scheduling (SPS).

In example 34, wherein the processor is further configured to partition the different TBs of the physical layer encapsulation with different portions of at least one of: spatial resources, time resources, or frequency resources.

In example 35, the processor is further configured to partition the different TBs based on at least one of: a wideband partitioning or a distributed partitioning, wherein the wideband partitioning comprises configuring a predefined number of physical resource blocks (PRBs) to a first TB of the different TBs and a remainder of PRBs of frequency resources to a second TB of the different TBs, wherein the distributed partitioning comprises configuring a first number of resource elements of a PRB to the first TB and a second number of resource elements of the PRB to the second TB.

In example 36, wherein the processor is further configured to partition different spatial layers with the different TBs in the physical layer encapsulation, wherein a first TB is configured with a first set of spatial layers comprising a greater reliability than a second set of spatial layers configured with a second TB of the different TBs.

In example 37, a first set of spatial layers comprises at least two spatial layers configured with one or more demodulation reference signal (DMRS) indices for a first TB and a second set of spatial layers comprises two or less spatial layers for a second TB of the different TBs.

In example 38, wherein the processor is further configured to generate a spatial layer-to-TB mapping to partition the different TBs of the physical layer encapsulation based on the spatial layer-to-TB mapping for the unequal protection.

In example 39, the processor is further configured to generate the unequal protection to the different TBs by partitioning repetitions or slot resources among a transmission opportunity unequally, wherein a first TB comprises more repetitions or slot resources than a second TB of the physical layer encapsulation.

In example 40, wherein the baseband processor is further configured to: generate a hybrid automatic repeat request (HARQ) feedback for a first TB configured based on a high priority HARQ codebook and another HARQ feedback for a second TB configured based on a low priority HARQ codebook that is lower in priority than the high priority HARQ codebook; generate the HARQ feedback only for the first TB configured based on the high priority HARQ codebook; or generate the HARQ feedback only for the second TB configured based on the low priority HARQ codebook.

In example 41, the baseband processor is further configured to generate HARQ feedback based on a bit width that is a function of a number of TBs multiplexed into a physical downlink shared channel (PDSCH) for at least one of: a Type 1 HARQ codebook, a Type 2 HARQ codebook, or a Type 3 HARQ codebook.

In example 42, wherein the network entity comprises a user equipment (UE).

In example 43, wherein the network entity comprises a bast station.

In example 44, a method of a network entity comprising: processing, via a processor, a physical layer transmission comprising different transport blocks (TBs) multiplexed into a physical layer encapsulation with an unequal protection among the different TBs; and transmitting, via the processor, the physical layer transmission to transmitter circuitry that transmits the physical layer transmission based on four or less spatial layers in a next generation (NR) network.

In example 45, further comprising: encoding a first TB of the different TBs based on a first bit or a least significant bit that is more reliable than other bits of a constellation point and a second TB of the different TBs based on one or more of the other bits of the constellation point to generate the unequal protection among the different TBs.

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.