Patent Application
20240147496
The subject matter disclosed herein relates generally to wireless communications and more particularly relates to semi-persistent based modification of Layer-1 (“L1”) parameters for Type-2 Configured Grant (“CG”) resource.
Certain wireless networks support semi-persistent grants of resources, such as a Configured Grant (“CG”). A CG is a type of grant-free uplink transmission feature, e.g., uplink data transmission without resource request. A CG can avoid the regular handshake delay, e.g., sending the scheduling request and waiting for uplink (“UL”) grant allocation. In current Third Generation Partnership Project (“3GPP”) New Radio (“NR”) design, two types of configured grants are supported: Type-1 and Type-2. For Type-1 CG, the uplink grant configuration and activation/deactivation are provided by Radio Resource Control (“RRC”) signaling. For Type-2 CG, the uplink grant configuration is provided via RRC signaling and its activation/deactivation is provided via Downlink Control Information (“DCI”).
Disclosed are procedures for modifying L1 parameters for CG resource. Said procedures may be implemented by apparatus, systems, methods, or computer program products.
One method at a User Equipment (“UE”) for modifying L1 parameters for CG resource includes acquiring channel occupancy for a license-exempt channel and transmitting a first UL transmission during a first set of time units, where the channel occupancy has a maximum duration. The method includes determining a priority of pending uplink transmissions capable of transmission during a remainder of the channel occupancy and releasing the acquired channel occupancy after the first set of time units and prior to a nominal end of the acquired channel occupancy in response to the priority of pending uplink transmissions being less than a priority threshold.
One method at a radio access network (“RAN”) for modifying L1 parameters for CG resource includes configuring a UE with a configuration for releasing a Channel Occupancy. The method includes receiving a first uplink transmission over a first set of time units during a UE-initiated Channel Occupancy and determining that the UE releases the UE-initiated Channel Occupancy.
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)). Furthermore, the described features, structures, or characteristics of the
embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of” includes any single item in the list or a combination of items in the list. For example, “one or more of A, B and C” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of” includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
The call-flow diagrams, flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the call-flow, flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
Generally, the present disclosure describes systems, methods, and apparatus for modifying L1 parameters for a Type-2 configured grant (“CG”) resource. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.
In the current NR design, Type-2 CG parameters are configured using RRC signaling and activated using DCI. However, the parameters for CG such as enabling repetition, number of repetition, beam/spatial relationship cannot be modified or adjusted once activated using DCI.
Disclosed herein are solutions for modifying or adjusting some of the parameters of the uplink CG resource using dynamic signaling, for example in scenarios such as survival time where high reliability enhancements are needed. The solutions may be implemented by apparatus, systems, methods, or computer program products. As used herein, the term “survival time” refers to the time duration for which data sent between communicating applications (transmitting and receiving) can be lost without affecting normal operation.
In periodic communication, survival time is often given as the number of lost messages. Any value above this threshold results in failure. Table 1 depicts motion control use case requirements for Communication Service Availability (“CSA”), as described in 3GPP Technical Report (“TR”) 22.804.
One solution includes modifying one or more L1 parameters such as repetition, Transmission Configuration Indicator (“TCI”) state, priority indicator, P0 and alpha (Open-loop power control parameters) associated with a Type-2 CG resource for a previously activated Type-2 CG resource using DCI.
In one embodiment, the UE may discard/ignore fields used for validating a DCI for activation such as redundancy version and/or Hybrid Automatic Repeat Request (“HARQ”) process number and L1 parameters present in the DCI may be applied for Physical Uplink Shared Channel (“PUSCH”) transmission from the next CG resource.
In one embodiment, a time domain resource allocation field in the DCI may be used to signal the row index indicating the number of repetition otherwise the number of bits associated with the time domain resource allocation field indicate ‘k’ number of repetition. However, the UE may continue to use the time domain allocation of K2 offset, start and length indicator (“SLIV”), mapping type as configured using RRC signaling.
In one embodiment, a high priority Configured Grant (“CG”)PUSCH (i.e., priority indicator in DCI is set to highest value) in the dynamic flexible symbols. Here, features like HARQ ACK/NACK deferral (kl+kldef,) and/or Semi-Persistent Scheduling (“SPS”) ACK/NACK skipping may be disabled during survival time, which may be signaled using the activation DCI. As used herein, “HARQ-ACK” may represent collectively the Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”) and Discontinuous Transmission (“DTX”). ACK means that a Transmission Block (“TB”) is correctly received while NACK (or NAK) means a TB is erroneously received and DTX means that no TB was detected.
In one implementation, the RAN 120 is compliant with the Fifth-Generation (“5G”) cellular system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a Next Generation Radio Access Network (“NG-RAN”), implementing New Radio (“NR”) Radio Access Technology (“RAT”) and/or Long-Term Evolution (“LTE”) RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123. Furthermore, the UL communication signals may comprise one or more uplink channels, such as the Physical Uplink Control Channel (“PUCCH”) and/or Physical Uplink Shared Channel (“PUSCH”), while the DL communication signals may comprise one or more downlink channels, such as the Physical Downlink Control Channel (“PDCCH”) and/or Physical Downlink Shared Channel (“PDSCH”). Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140.
In some embodiments, the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 140. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Internet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141.
In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 141. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QoS Identifier (“5QI”).
In the context of a 4G/LTE system, such as the Evolved Packet System (“EPS”), a to Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., a tunnel between the remote unit 105 and a PDN Gateway (“PGW”, not shown) in the mobile core network 140. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).
The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.
The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121.
Note that during NR operation on unlicensed spectrum (referred to as “NR-U”), the base unit 121 and the remote unit 105 communicate over unlicensed (i.e., shared) radio spectrum. Similarly, during LTE operation on unlicensed spectrum (referred to as “LTE-U”), the base unit 121 and the remote unit 105 also communicate over unlicensed (i.e., shared) radio spectrum. For operation in unlicensed spectrum (e.g., NR-U or LTE-U), when a remote unit 105 or base unit 121 wants to transmit, it has to detect the energy level at a designated time for duration equal to a CCA period. If the energy level in the channel is below the CCA threshold, then the equipment can transmit for duration equal to the COT. After that, if the equipment wishes to continue its transmission, it has to repeat the CCA process.
In one embodiment, the mobile core network 140 is a 5G Core network (“5GC”) or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”) and/or Public Land Mobile Network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session
Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 147, a Unified Data Management function (“UDM”) and a User Data Repository (“UDR”). In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 149. Although specific numbers and types of network functions are depicted in
The UPF(s) 141 is/are responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (“DN”), in the 5G architecture. The AMF 143 is responsible for termination of Non-Access Spectrum (“NAS”) signaling, NAS ciphering and integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) Internet Protocol (“IP”) address allocation and management, DL data notification, and traffic steering configuration of the UPF 141 for proper traffic routing.
The PCF 147 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and may be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like.
In various embodiments, the mobile core network 140 may also include a Network Repository Function (“NRF”) (which provides Network Function (“NF”) service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), a Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), an Authentication Server Function (“AUSF”), or other NFs defined for the SGC. When present, the AUSF may act as an authentication server and/or authentication proxy, thereby allowing the AMF 143 to authenticate a remote unit 105. In certain embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.
In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband (“eMBB”) service. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication (“URLLC”) service. In other examples, a network slice may be optimized for machine type communication (“MTC”) service, massive MTC (“mMTC”) service, Internet-of-Things (“IoT”) service. In yet other examples, a network slice may be deployed for a specific application service, a vertical service, a specific use case, etc.
A network slice instance may be identified by a single-network slice selection assistance information (“S-NSSAI”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 145 and UPF 141. In some embodiments, the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in
While
Moreover, in an LTE variant where the mobile core network 140 is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, the AMF 143 may be mapped to an MME, the SMF 145 may be mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.
Communication devices, such as the remote unit 105 may be configured by the RAN 120 with a UL Type-2 CG configuration 125. As described above, a base unit 121 transmits activation DCI to activate the UL Type-2 CG. The remote unit 105 may then transmit PUSCH 127 to the base unit 121 according to the UL Type-2 CG configuration 125. In some embodiments, the base unit 121 may send additional DCI to modify L1 parameters of the UL Type-2 CG configuration 125, as described in further detail below.
In the following descriptions, the term “gNB” is used for the base station/base unit, but it is replaceable by any other radio access node, e.g., RAN node, ng-eNB, eNB, Base Station (“BS”), Access Point (“AP”), etc. Additionally, the term “UE” is used for the mobile station/remote unit, but it is replaceable by any other remote device, e.g., remote unit, MS, ME, etc. Further, the operations are described mainly in the context of 5G NR. However, the below described solutions/methods are also equally applicable to other mobile communication systems for modifying L1 parameters for CG resource.
The AS layer 225 (also referred to as “AS protocol stack”) for the User Plane protocol stack 201 consists of at least SDAP, PDCP, RLC and MAC sublayers, and the physical layer. The AS layer 227 for the Control Plane protocol stack 203 consists of at least RRC, PDCP, RLC and MAC sublayers, and the physical layer. The Layer-2 (“L2”) is split into the SDAP, PDCP, RLC and MAC sublayers. The Layer-3 (“L3”) includes the RRC sublayer 221 and the NAS layer 223 for the control plane and includes, e.g., an Internet Protocol (“IP”) layer or PDU Layer (note depicted) for the user plane. L1 and L2 are referred to as “lower layers,” while L3 and above (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers.”
The PHY layer 211 offers transport channels to the MAC sublayer 213. The MAC sublayer 213 offers logical channels to the RLC sublayer 215. The RLC sublayer 215 offers RLC channels to the PDCP sublayer 217. The PDCP sublayer 217 offers radio bearers to the SDAP sublayer 219 and/or RRC layer 221. The SDAP sublayer 219 offers QoS flows to the core network (e.g., 5GC). The RRC layer 221 provides for the addition, modification, and release of Carrier Aggregation (“CA”) and/or Dual Connectivity (“DC”). The RRC layer 221 also manages the establishment, configuration, maintenance, and release of Signaling Radio Bearers (“SRBs”) and Data Radio Bearers (“DRBs”).
The MAC layer 213 is the lowest sublayer in the Layer-2 architecture of the NR protocol stack. Its connection to the PHY layer 211 below is through transport channels, and the connection to the RLC layer 215 above is through logical channels. The MAC layer 213 therefore performs multiplexing and demultiplexing between logical channels and transport channels: the MAC layer 213 in the transmitting side constructs MAC PDUs, known as transport blocks, from MAC Service Data Units (“SDUs”) received through logical channels, and the MAC layer 213 in the receiving side recovers MAC SDUs from MAC PDUs received through transport channels.
The MAC layer 213 provides a data transfer service for the RLC layer 215 through logical channels, which are either control logical channels which carry control data (e.g., RRC signaling) or traffic logical channels which carry user plane data. On the other hand, the data from the MAC layer 213 is exchanged with the PHY layer 211 through transport channels, which are classified as downlink or uplink. Data is multiplexed into transport channels depending on how it is transmitted over the air.
The PHY layer 211 is responsible for the actual transmission of data and control information via the air interface, i.e., the PHY layer 211 carries all information from the MAC transport channels over the air interface on the transmission side. Some of the important functions performed by the PHY layer 211 include coding and modulation, link adaptation (e.g., Adaptive Modulation and Coding (“AMC”)), power control, cell search (for initial synchronization and handover purposes) and other measurements (inside the 3GPP system (i.e., NR and/or LTE system) and between systems) for the RRC layer 221. The PHY layer 211 performs transmissions based on transmission parameters, such as the modulation scheme, the coding rate (i.e., the modulation and coding scheme (“MCS”)), the number of physical resource blocks, etc.
According to embodiments of the first solution, one or more configured and/or dynamically indicated L1 parameters such as repetition (e.g., the number of repetitions), a TCI state (or an Sounding Reference Signal (“SRS”) resource indicator), precoding and number of layers, a priority indicator, a MCS table, P0 and/or alpha (i.e., open-loop power control parameters) associated with a Type-2 CG resource or UL Type-2 CG configuration can be modified based on one DCI signaling instead of using a RRC reconfiguration message or using deactivation and re-activation DCI formats or UL Type-2 CG configuration. In this case, MAC control element (“CE”) confirmation message is not sent for the corresponding Type-2 CG resource or UL Type-2 CG configuration.
In one implementation, Type-2 CG activation DCI could be used to modify one or more L1 parameters such as number of repetitions, TCI state (or SRS resource indicator), precoding and number of layers, priority indicator, P0 and/or alpha values associated with a Type-2 CG resource. When a UE 205 receives a ‘second’ Type-2 CG activation DCI corresponding to the previously (i.e., first activation DCI) activated Type-2 CG resource, the UE 205 could discard/ignore fields used for validating a DCI for activation such as redundancy version and/or HARQ process number and L1 parameters present in the DCI could be applied for PUSCH transmission from the next CG resource (e.g., from the first PUSCH after ‘second’ Type-2 CG activation DCI).
In one example, after failing to decode PUSCH in the CG resource or failing to decode ‘N’ consecutive PUSCHs in CG resources, a RAN node could transmit an activation DCI to modify L1 parameters of the CG resource to increase the reliability of the next PUSCH transmission in the same CG resource (or CG configuration) as shown in
In some implementations, the UE 205 receives the DCI to update the L1 parameters for the already(previously) activated UL Type-2 CG and the L1 parameters are applied to the CG resources after a time-offset (configured by network) from the instance when DCI is received. For example, if the time-offset is two slots, then the updated L1 parameters are applied to CG resources after two slots from the slot when DCI is received. In some implementation, the time-offset can be based on a processing capability of the UE 205 (such as value of N2).
In some embodiments, the L1 parameters updated by DCI are applied only for a fixed duration of time, after which the parameters indicated by the activating DCI are applied again. For example, if the duration for applying updated L1 parameters is five slots, then the CG resources within the five slots apply the updated L1 parameters, after which the parameters are updated back according to the activating DCI. In one implementation, updated TCI (or an SRS resource indicator) could be continued for transmitting the CG beyond the predefined time.
In some embodiments, the L1 parameters for UL Type-2 CG can be updated jointly by DCI that is used to schedule dynamic grant PUSCH (such as DCI format 0_1, 0_2). In this case, no separate DCI is needed for updating the L1 parameters of the already activated Type-2 CG resources. The dynamic grant (“DG”) scheduling DCI can be enhanced with a 1-bit field to indicate if the L1 parameters are also applied for updating the already activated CG resources, for example if no such bit field is configured or ‘0’ is indicated, then the LI parameters are not activated for the Type-2 CG resources, if ‘1’ is indicated for the bit field, then the L1 parameters are also applied to update the Type-2 CG resources.
In some implementations, only a subset of the L1 parameters is allowed to be modified with the remaining L1 parameters in the DCI set to a predetermined value. This can be used to distinguish (from the initial Type-2 CG activation DCI) and additionally validate (in addition to the redundancy version and/or HARQ process number for Type-2 CG PDCCH validation fields) the ‘second’ or ‘modification’ Type-2 CG activation DCI for an already activated CG configuration. In another implementation, the ‘second’ or ‘modification’ Type-2 CG activation DCI may be scrambled by a new Radio Network Temporary Identifier (“RNTI”) parameter “cs-mod-RNTI” (e.g., with validation based on the redundancy version and/or HARQ process number validation fields).
In another implementation, time domain resource allocation field in the DCI could be used to signal the row index indicating the number of repetition or the value of the bits associated with the time domain resource allocation field can be reinterpreted to indicate ‘k’ number of repetition. In these cases, however, the UE 205 could continue to use the time domain allocation of K2 offset, start and length indicator (“SLIV”), mapping type indicated in/corresponding to the initial Type-2 CG activation DCI for the CG configuration and time domain allocation list as configured using RRC signaling. In one implementation, if type of repetition (Type A or Type B) and number of repetition ‘k’ is configured using RRC signaling then activation DCI signaling only changes the ‘k’ number of repetitions. In another implementation, if type of repetition (Type A or Type B) and number of repetition ‘k’ is not configured using RRC signaling then activation DCI signaling indicate the type of repetition and ‘k’ number of repetitions. In another implementation, if the Redundancy Version (“RV”) pattern is not provided then the UE 205 could choose the RV pattern of {0,0,0,0} for the transmission of PUSCH repetition.
In one implementation, UL TCI state or associated SRS Resource Indicator (“SRI”) could be used to signal the UL beam or Transmission and Reception Point (“TRP”) for PUSCH transmission in the same CG resource. In another implementation, SRI could be used to select different panels for the transmission of PUSCH using the same CG resource. In another implementation, UL TCI state or associated SRI could be used to signal the transmission of PUSCH using a CG resource to different TRP.
In another implementation, after failing to decode PUSCH in the CG resource (or failing to decode ‘N’ consecutive PUSCH in CG resources) or when survival timer starts, the RAN node could increase the priority of the CG transmission by modifying the priority indication in the DCI and such increase in the priority value could increase the reliability of the PUSCH transmission (e.g., avoid or reduce the cancellation of PUSCH due to overlap in time with other UL channels and/or signals) corresponding to other UL physical channel such as SRS; PUCCH for the intra-UE multiplexing. In one implementation, priority value is reverted to the RRC configured priority value after receiving ACK, or ‘N’ consecutive ACK, or expiry of the survival timer.
In another implementation, open-loop power control parameter set indication in the DCI could indicate P0 and/or alpha for the transmission of PUSCH in the same CG resource.
The procedure 300 begins and the RAN node 210 sends to the UE 205 an RRC configuration of Type-2 CG resources (see messaging 305). The RAN node 210 also sends a first DCI activation command for the configured Type-2 CG resource (see messaging 310).
During a CG transmission opportunity, the UE 205 performs PUSCH transmission using the configured CG resources (see messaging 315). The UE 205 may perform one or more PUSCH transmissions on CG resources, including one or more repetitions, as discussed in further detail below.
The RAN node 210 determines to modify one or more L1 parameters (see block 320). For example, the RAN node 210 after failing to decode PUSCH in the CG resource or failing to decode ‘N’ consecutive PUSCHs in CG resources may decide to modify L1 parameters of the CG resource to increase the reliability of the next PUSCH transmission in the same CG resource.
Accordingly, the RAN node 210 sends a second DCI activation command to the UE 205 to modify L1 parameters of the CG resource to increase the reliability of the next PUSCH transmission in the same CG resource (see messaging 325). During a next CG transmission opportunity, the UE 205 then performs PUSCH transmission on the configured CG resources using the modified L1 parameters (see messaging 330).
The procedure 400 begins and the RAN node 210 sends to the UE 205 an RRC configuration of Type-2 CG resources (see messaging 405). The RAN node 210 also sends a first DCI activation command for the configured Type-2 CG resource (see messaging 410).
During a CG transmission opportunity, the UE 205 performs PUSCH transmission using the configured CG resources (see messaging 415). The UE 205 may perform one or more PUSCH transmissions on CG resources, including one or more repetitions, as discussed in further detail below.
The RAN node 210 determines to modify the number of repetitions of a PUSCH transmission (see block 420). For example, the RAN node 210 after failing to decode PUSCH in the CG resource or failing to decode ‘N’ consecutive PUSCHs in CG resources may decide to modify the number of repetitions of a PUSCH transmission to increase the reliability of the next PUSCH transmission in the same CG resource.
Accordingly, the RAN node 210 sends a second DCI activation command to the UE 205 to modify L1 parameters of the CG resource to increase the reliability of the next PUSCH transmission in the same CG resource (see messaging 425). During a next CG transmission opportunity, the UE 205 then performs PUSCH transmission on the configured CG resources using the modified number of repetitions (see messaging 430).
However, in the procedure 400 the RAN node 210 further determines to also modify the TCI state of a PUSCH transmission (see block 435). For example, if the RAN node 210 is still unable to decode PUSCH in the CG resource then it may decide to modify the TCI of a PUSCH transmission to increase the reliability of the next PUSCH transmission in the same CG resource.
Accordingly, the RAN node 210 sends a third DCI activation command to the UE 205 to modify L1 parameters of the CG resource to increase the reliability of the next PUSCH transmission in the same CG resource (see messaging 440). During a next CG transmission opportunity, the UE 205 then performs PUSCH transmission on the configured CG resources using the modified TCI state (see messaging 445). Note that this latest PUSCH transmission may have both the number of repetition and the TCI state modified from the original parameter values transmitted in the RRC message.
In another implementation, a new overriding CG resource configuration using DCI activation includes a set of L1 parameters signaled using RRC and specify one or more L1 parameters that could be allowed to change for the same CG resource using the DCI activation.
In some embodiments, one or more configuration of L1 parameters for the Type-2 CG resource could be modified using DCI scrambled using Configured Scheduling Radio Network Temporary Identifier (“CS-RNTI”), in this case the UE 205 could ignore the non-toggled new data indicator (“NDI”) for retransmission grant, i.e., if the RAN node 210 did not decode PUSCH from the last CG resource but could apply/indicate one or more configuration of L1 parameters for PUSCH transmission of next TB in the CG resource.
In one implementation, the UE 205 is signaled to ignore the retransmission grant. In another implementation, the UE 205 could start the survival time after receiving non-toggled NDI from the RAN node 210 and during survival time (before the expiry of the survival timer), every next TBs are transmitted using higher reliability and hence the one or more configuration of L1 parameters for the Type-2 CG resource could be modified using DCI scrambled using CS-RNTI during survival time.
In some embodiments, to increase the availability of UL symbols for PUSCH transmission during survival time, CG PUSCH repetition is allowed for high priority CG PUSCH (i.e., priority indicator in DCI is set to highest value) in the dynamic flexible symbols. In one example, a UE 205 can be configured with cell-specific flexible symbols as UE-specific UL or UE-specific flexible symbols with tdd-UL-DL-ConfigurationDedicated, which can override flexible symbols of tdd-UL-DL-ConfigurationCommon. Further, the UE 205 may receive an indication of Slot Format Indicator (“SFI”) via DCI indicating that the semi-static flexible symbols are dynamic flexible symbols. For the UE-specific UL or UE-specific flexible symbols, there is no Physical Random Access Channel (“PRACH”) and/or SRS transmission from any UE is expected, and the UE 205 could use the dynamic flexible symbols for high priority CG PUSCH repetitions.
In some embodiments, time/frequency resource and/or MCS signaled in the RRC could be overwritten by this second DCI field of timing assignment/frequency assignment and/or MCS. In one example, more UL resource could be signaled to the UE 205 during survival time that could make use of larger TB size considering lower MCS. In some embodiment, offset between successive CG resource in a period could be modified using the activation DCI. In some embodiments, the UE 205 could revert back to the RRC configuration after receiving Ack or ‘N’ consecutive Acks or after a predefined time or survival timer stopped.
In some embodiments, features like HARQ Ack/Nack deferral (kl+kldef,) and/or SPS Ack/Nack skipping could be disabled during survival time, which could be signaled using the activation DCI or after receiving NACK in the form of non-toggle NDI or Downlink Feedback Indicator (“DFI”) for that HARQ process. In another implementation, HARQ Ack/Nack deferral (kl+kldef,) and/or SPS Ack/Nack skipping could be enabled after receiving Ack or ‘N’ consecutive Acks or after a predefined time after receiving the activation DCI disabling feature command or non-toggled NDI.
Regarding URLLC, non-slot-based repetition (Repetition Type B), the following parameters are defined:
For any RV sequence, the repetitions shall be terminated when one of the following conditions is reached: 1) After transmitting K nominal repetitions; or 2) At the last transmission occasion among the K nominal repetitions within the period P; or 3) From the starting symbol of a repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever conditions is reached first.
Regarding rules for RV and repetitions, the higher layer parameter repK-RV defines the redundancy version pattern to be applied to the repetitions. If the parameter cg-RetransmissionTimer is provided, then the redundancy version for uplink transmission with a configured grant is determined by the UE 205. If the parameter repK-RV is provided in the configuredGrantConfig, but the parameter cg-RetransmissionTimer is not provided, then for the nth transmission occasion among K repetitions, n=1, 2, . . . , K, it is associated with (mod(n-1,4)+1)th value in the configured RV sequence. However, if the parameter repK-RV is not provided in the configuredGrantConfig and if the parameter cg-RetransmissionTimer is not provided, then the redundancy version for uplink transmissions with a configured grant shall be set to 0.
If a configured grant configuration is configured with startingFromRV0-r16 set to ‘off’, the initial transmission of a transport block may only start at the first transmission occasion of the K repetitions. Otherwise, the initial transmission of a transport block may start at one of: 1) the first transmission occasion of the K repetitions if the configured RV sequence is {0, 2, 3, 1}; or 2) any of the transmission occasions of the K repetitions that are associated with RV=0 if the configured RV sequence is {0, 3, 0, 3}; or 3) any of the transmission occasions of the K repetitions if the configured RV sequence is {0, 0, 0, 0}, except the last transmission occasion when K≥8.
Regarding PDCCH validation for DL SPS and UL grant Type-2, the UE 205 validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or a configured UL grant Type-2 PDCCH if: the Cyclic Redundancy Check (“CRC”) of a corresponding DCI format is scrambled with a CS-RNTI provided by cs-RNTI, and the new data indicator field in the DCI format for the enabled transport block is set to ‘0’, and the DFI flag field, if present, in the DCI format is set to ‘0’, and if validation is for scheduling activation and if the PDSCH-to-HARQ_feedback timing indicator field in the DCI format is present, the PDSCH-to-HARQ_feedback timing indicator field does not provide an inapplicable value from dl-DataTo UL-ACK-r16.
If a UE 205 is provided a single configuration for UL grant Type-2 PUSCH or for SPS PDSCH, validation of the DCI format is achieved if all fields for the DCI format are set according to Table 2 (taken from 3GPP Technical Specification (“TS”) 38.213, Table 10.2-1) or Table 3 (taken from 3GPP TS 38.213, Table 10.2-2). Tables 2 and 3 show special fields for single DL SPS or single UL grant Type-2 scheduling activation PDCCH validation when the UE 205 is provided a single SPS PDSCH or UL grant Type-2 configuration in the active DL/UL BWP of the scheduled cell.
If the UE 205 is provided more than one configurations for UL grant Type-2 PUSCH or for SPS PDSCH, a value of the HARQ process number field in a DCI format indicates an activation for a corresponding UL grant Type-2 PUSCH or for a SPS PDSCH configuration with a same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively. Validation of the DCI format is achieved if the RV field for the DCI format is set as in Table 4 (taken from 3GPP TS 38.213, Table 10.2-3). Table 4 shows special fields for a single DL SPS or single UL grant Type-2 scheduling activation PDCCH validation when the UE 205 is provided multiple DL SPS or UL grant Type-2 configurations in the active DL/UL BWP of the scheduled cell.
Where a UE 205 is provided more than one configuration for UL grant Type-2 PUSCH or for SPS PDSCH, if the UE 205 is provided ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, then a value of the HARQ process number field in a DCI format indicates a corresponding entry for scheduling release of one or more UL grant Type-2 PUSCH or SPS PDSCH configurations. However, if the UE 205 is not provided ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, then a value of the HARQ process number field in a DCI format indicates a release for a corresponding UL grant Type-2 PUSCH or for a SPS PDSCH configuration with a same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively.
Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 5 (taken from 3GPP TS 38.213, Table 10.2-4). Table 5 shows special fields for a single or multiple DL SPS and UL grant Type-2 scheduling release PDCCH validation when the UE 205 is provided multiple DL SPS or UL grant Type-2 configurations in the active DL/UL BWP of the scheduled cell. If validation is achieved, the UE 205 considers the information in the DCI format as a valid activation or valid release of DL SPS or configured UL grant Type-2. If validation is not achieved, the UE 205 discards all the information in the DCI format.
A UE 205 is expected to provide HARQ-ACK information in response to a SPS PDSCH release after N symbols from the last symbol of a PDCCH providing the SPS PDSCH release. IfprocessingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell with the PDCCH providing the SPS PDSCH release, N=5 for μ=0, N=5.5 for μ=1, and N=11 for μ=2, otherwise, N=10 for μ=0, N=12 for μ=1, N=22 for μ=2, and N=25 for μ=3, wherein μ corresponds to the smallest subcarrier spacing (“SCS”) configuration between the SCS configuration of the PDCCH providing the SPS PDSCH release and the SCS configuration of a PUCCH carrying the HARQ-ACK information in response to a SPS PDSCH release.
In some embodiments, the input device 815 and the output device 820 are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus 800 may not include any input device 815 and/or output device 820. In various embodiments, the user equipment apparatus 800 may include one or more of: the processor 805, the memory 810, and the transceiver 825, and may not include the input device 815 and/or the output device 820.
As depicted, the transceiver 825 includes at least one transmitter 830 and at least one receiver 835. In some embodiments, the transceiver 825 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. In various embodiments, the transceiver 825 is operable on unlicensed spectrum. Moreover, the transceiver 825 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 825 may support at least one network interface 840 and/or application interface 845. The application interface(s) 845 may support one or more APIs. The network interface(s) 840 may support 3GPP reference points, such as Uu, N1, PC5, etc. Other network interfaces 840 may be supported, as understood by one of ordinary skill in the art.
The processor 805, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 805 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 805 executes instructions stored in the memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825.
In various embodiments, the processor 805 controls the user equipment apparatus 800 to implement the above described UE behaviors. In certain embodiments, the processor 805 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
In various embodiments, the transceiver 825 receives an RRC configuration for at least one UL Type-2 CG resource and further receives a first DCI to activate the at least one UL Type-2 CG resource. Via the transceiver 825, the processor 805 performs at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The transceiver 825 further receives a second DCI that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and the processor 805 further performs (i.e., via the transceiver 825) at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission, where the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the processor 805 applies the at least one L1 parameter updated by the second DCI for a fixed duration of time and reverts the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI is an activation DCI that contains at least one (e.g., extraneous) validation field, the validation field being a RV field and/or HARQ process field. In such embodiments, the processor 805 further ignores the at least one validation field in the activation DCI.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, the modified priority indicator is set to a highest value. In such embodiments, the processor 805 controls the transceiver 825 to transmit one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the processor 805 reverts the modified priority of the PUSCH transmission to a previously configured priority value after receiving a predetermined number of consecutive positive acknowledgements (i.e., one or ‘N’ consecutive ACK). In another embodiment, the processor 805 reverts the modified priority of the PUSCH transmission to a previously configured priority value after the expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the second DCI is scrambled using a CS-RNTI of the communication device. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter. In certain embodiments, the processor 805 further ignores a non-toggled NDI for retransmission grant in response to receiving the second DCI scrambled by CS-RNTI.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission. In such embodiments, the disabled feature may be one or more of: HARQ acknowledgement (i.e., Ack/Nack) deferral and/or SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the processor 805 further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number of consecutive positive acknowledgements (i.e., one or ‘N’ consecutive ACK). In another embodiment, the processor 805 further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
The memory 810, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 810 includes volatile computer storage media. For example, the memory 810 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 810 includes non-volatile computer storage media. For example, the memory 810 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 810 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 810 stores data related to modifying L1 parameters for CG resource. For example, the memory 810 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 810 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 800.
The input device 815, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 815 may be integrated with the output device 820, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 815 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 815 includes two or more different devices, such as a keyboard and a touch panel.
The output device 820, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 820 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 820 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light-Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 820 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 800, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 820 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 820 includes one or more speakers for producing sound. For example, the output device 820 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 820 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 820 may be integrated with the input device 815. For example, the input device 815 and output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 820 may be located near the input device 815.
The transceiver 825 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 825 operates under the control of the processor 805 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 805 may selectively activate the transceiver 825 (or portions thereof) at particular times in order to send and receive messages.
The transceiver 825 includes at least transmitter 830 and at least one receiver 835. One or more transmitters 830 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 835 may be used to receive DL communication signals from the base unit 121, as described herein. Although only one transmitter 830 and one receiver 835 are illustrated, the user equipment apparatus 800 may have any suitable number of transmitters 830 and receivers 835. Further, the transmitter(s) 830 and the receiver(s) 835 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 825 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 825, transmitters 830, and receivers 835 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 840.
In various embodiments, one or more transmitters 830 and/or one or more receivers 835 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. In certain embodiments, one or more transmitters 830 and/or one or more receivers 835 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 840 or other hardware components/circuits may be integrated with any number of transmitters 830 and/or receivers 835 into a single chip. In such embodiment, the transmitters 830 and receivers 835 may be logically configured as a transceiver 825 that uses one more common control signals or as modular transmitters 830 and receivers 835 implemented in the same hardware chip or in a multi-chip module.
In some embodiments, the input device 915 and the output device 920 are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus 900 may not include any input device 915 and/or output device 920. In various embodiments, the network apparatus 900 may include one or more of: the processor 905, the memory 910, and the transceiver 925, and may not include the input device 915 and/or the output device 920.
As depicted, the transceiver 925 includes at least one transmitter 930 and at least one receiver 935. Here, the transceiver 925 communicates with one or more remote units 105. Additionally, the transceiver 925 may support at least one network interface 940 and/or application interface 945. The application interface(s) 945 may support one or more APIs. The network interface(s) 940 may support 3GPP reference points, such as Uu, N1, N2 and N3. Other network interfaces 940 may be supported, as understood by one of ordinary skill in the art.
The processor 905, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 905 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. In some embodiments, the processor 905 executes instructions stored in the memory 910 to perform the methods and routines described herein. The processor 905 is communicatively coupled to the memory 910, the input device 915, the output device 920, and the transceiver 925.
In various embodiments, the network apparatus 900 is a RAN node (e.g., gNB) that communicates with one or more UEs, as described herein. In such embodiments, the processor 905 controls the network apparatus 900 to perform the above described RAN behaviors. When operating as a RAN node, the processor 905 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
In various embodiments, the processor 905 controls the transceiver 925 to transmit a RRC configuration to a UE (i.e., a communication device) for at least one UL Type-2 CG resource. Via the transceiver 925, the processor 905 transmits a first DCI to the UE to activate the at least one UL Type-2 CG resource and monitors for (i.e., attempts to receive) at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. Note that the processor 905 may be unable to successfully receive and decode a PUSCH transmission from the UE.
Accordingly, the processor 905 may determine to update one or more L1 parameters, e.g., in order to increase reliability of PUSCH reception. Via the transceiver 925, the processor 905 transmits a second DCI to the UE that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and monitors for (i.e., attempts to receive) at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission, and the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the UE is configured to apply the at least one L1 parameter updated by the second DCI for a fixed duration of time and to revert the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In such embodiments, monitoring for at least one second PUSCH transmission according to the at least one L1 parameter updated by the second DCI includes monitoring during the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, processor 905 sets the modified priority indicator to a highest value. In such embodiments, the transceiver 925 further monitors for one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the processor 905 reverts the modified priority of the PUSCH transmission to a previously configured priority value after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor 905 reverts the modified priority of the PUSCH transmission to a previously configured priority value after the expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the processor 905 further scrambles the second DCI using a CS-RNTI of the UE. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission, said feature being one or more of. HARQ acknowledgement (i.e., Ack/Nack) deferral and/or disables SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the processor 905 further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor 905 further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
The memory 910, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 910 includes volatile computer storage media. For example, the memory 910 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 910 includes non-volatile computer storage media. For example, the memory 910 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 910 includes both volatile and non-volatile computer storage media.
In some embodiments, the memory 910 stores data related to modifying L1 parameters for CG resource. For example, the memory 910 may store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 910 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 900.
The input device 915, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 915 may be integrated with the output device 920, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 915 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 915 includes two or more different devices, such as a keyboard and a touch panel.
The output device 920, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 920 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 920 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 920 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus 900, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 920 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
In certain embodiments, the output device 920 includes one or more speakers for producing sound. For example, the output device 920 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 920 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 920 may be integrated with the input device 915. For example, the input device 915 and output device 920 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 920 may be located near the input device 915.
The transceiver 925 includes at least transmitter 930 and at least one receiver 935. One or more transmitters 930 may be used to communicate with the UE, as described herein. Similarly, one or more receivers 935 may be used to communicate with network functions in the Public Land Mobile Network (“PLMN”) and/or RAN, as described herein. Although only one transmitter 930 and one receiver 935 are illustrated, the network apparatus 900 may have any suitable number of transmitters 930 and receivers 935. Further, the transmitter(s) 930 and the receiver(s) 935 may be any suitable type of transmitters and receivers.
The method 1000 begins and receives 1005 a RRC configuration for at least one UL Type-2 CG resource. The method 1000 includes receiving 1010 a first DCI that activates the at least one UL Type-2 CG resource. The method 1000 includes performing 1015 at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The method 1000 includes receiving 1020 a second DCI that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource. The method 1000 includes performing 1025 at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI. The method 1000 ends.
The method 1100 begins and transmits 1105 a RRC configuration to a communication device (i.e., a UE) for at least one UL Type-2 CG resource. The method 1100 includes transmitting 1110 a first DCI to the communication device that activates the at least one UL Type-2 CG resource. The method 1100 includes monitoring 1115 for at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The method 1100 includes transmitting 1120 a second DCI to the communication device that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource. The method 1100 includes monitoring 1125 for at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI. The method 1100 ends.
Disclosed herein is a first apparatus for modifying L1 parameters for CG resource,
according to embodiments of the disclosure. The first apparatus may be implemented by a UE device, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 800, described above. The first apparatus includes a processor and a transceiver that receives an RRC configuration for at least one UL Type-2 CG resource and further receives a first DCI to activate the at least one UL Type-2 CG resource. Via the transceiver, the processor performs at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The transceiver further receives a second DCI that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and the processor further performs (i.e., via the transceiver) at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission, where the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the processor applies the at least one L1 parameter updated by the second DCI for a fixed duration of time and reverts the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI is an activation DCI that contains at least one (e.g., extraneous) validation field, the validation field being a RV field and/or HARQ process field. In such embodiments, the processor further ignores the at least one validation field in the activation DCI.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, the modified priority indicator is set to a highest value. In such embodiments, the processor controls the transceiver to transmit one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the processor reverts the modified priority of the PUSCH transmission to a previously configured priority value after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor reverts the modified priority of the PUSCH transmission to a previously configured priority value after the expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the second DCI is scrambled using a CS-RNTI of the communication device. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter. In certain embodiments, the processor further ignores a non-toggled NDI for retransmission grant in response to receiving the second DCI scrambled by CS-RNTI.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission. In such embodiments, the disabled feature may be one or more of: HARQ acknowledgement (i.e., Ack/Nack) deferral and/or SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the processor further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
Disclosed herein is a first method for modifying L1 parameters for CG resource, according to embodiments of the disclosure. The first method may be performed by a UE device, such as the remote unit 105, the UE 205, and/or the user equipment apparatus 800, described above. The first method includes receiving a RRC configuration for at least one UL Type-2 CG resource. The first method includes receiving a first DCI to activate the at least one UL Type-2 CG resource and performing at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The first method includes receiving a second DCI that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and performing at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission, where the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified LI parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the first method further includes applying the at least one L1 parameter updated by the second DCI for a fixed duration of time and reverting the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI is an activation DCI that contains at least one (e.g., extraneous) validation field, the validation field being a RV field and/or HARQ process field. In such embodiments, the first method further includes ignoring the at least one validation field in the activation DCI.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, the modified priority indicator is set to a highest value. In such embodiments, the first method further includes transmitting one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the priority of the PUSCH transmission reverts to a previously configured priority value after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the priority of the PUSCH transmission reverts to a previously configured priority value after expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the second DCI is scrambled using a CS-RNTI of the communication device. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter. In certain embodiments, the first method further includes ignoring a non-toggled NDI for retransmission grant in response to receiving the second DCI scrambled by CS-RNTI.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission, said feature being one or more of: HARQ acknowledgement (i.e., Ack/Nack) deferral and/or disables SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the first method includes enabling the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACKs). In another embodiment, the first method includes enabling the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
Disclosed herein is a second apparatus for modifying L1 parameters for CG resource, according to embodiments of the disclosure. The second apparatus may be implemented by a network entity, such as the base unit 121, the RAN node 210, and/or the network apparatus 900, described above. The second apparatus includes a processor and a transceiver that transmits a RRC configuration to a communication device (i.e., a UE) for at least one UL Type-2 CG resource. Via the transceiver, the processor transmits a first DCI to the communication device to activate the at least one UL Type-2 CG resource and monitors for at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. Via the transceiver, the processor transmits a second DCI to the communication device that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and monitors for at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission, and the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the communication device is configured to apply the at least one L1 parameter updated by the second DCI for a fixed duration of time and to revert the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In such embodiments, monitoring for at least one second PUSCH transmission according to the at least one L1 parameter updated by the second DCI includes monitoring during the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, processor sets the modified priority indicator to a highest value. In such embodiments, the transceiver further monitors for one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the processor reverts the modified priority of the PUSCH transmission to a previously configured priority value after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor reverts the modified priority of the PUSCH transmission to a previously configured priority value after the expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the processor further scrambles the second DCI using a CS-RNTI of the communication device. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission, said feature being one or more of: HARQ acknowledgement (i.e., Ack/Nack) deferral and/or disables SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the processor further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the processor further enables the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
Disclosed herein is a second method for modifying L1 parameters for CG resource, according to embodiments of the disclosure. The second method may be performed by a network entity, such as the base unit 121, the RAN node 210, and/or the network apparatus 900, described above. The second method includes transmitting a RRC configuration to a communication device (i.e., a UE) for at least one UL Type-2 CG resource. The second method includes transmitting a first DCI to the communication device to activate the at least one UL Type-2 CG resource and monitoring for at least one first PUSCH transmission on the at least one activated UL Type-2 CG resource according to parameters configured by the RRC configuration, the first DCI, or some combination thereof. The second method includes transmitting a second DCI to the communication device that updates at least one L1 parameter for the at least one activated UL Type-2 CG resource and monitoring for at least one second PUSCH transmission on the at least one activated UL Type-2 CG resources according to the at least one L1 parameter updated by the second DCI.
In some embodiments, the RRC configuration does not indicate any type of repetition or number of repetitions of the PUSCH transmission, and the first DCI indicates a type of repetition and a number of repetitions of a PUSCH transmission. In some embodiments, the first DCI contains a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified LI parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the communication device is configured to apply the at least one L1 parameter updated by the second DCI for a fixed duration of time and to revert the at least one L1 parameter updated by the second DCI after expiration of the fixed duration of time. In such embodiments, monitoring for at least one second PUSCH transmission according to the at least one L1 parameter updated by the second DCI includes monitoring during the fixed duration of time. In some embodiments, the second DCI contains a plurality of updated L1 parameters for the at least one UL Type-2 CG, said plurality of updated L1 parameters selected from: a TCI state, an SRS resource indicator, a number of repetitions, a priority indicator, a MCS table, and an open loop power control parameter.
In some embodiments, the second DCI contains a modified priority indicator that increases the priority of the PUSCH transmission on the at least one activated UL Type-2 CG resource. In certain embodiments, the second method includes setting the modified priority indicator to a highest value. In such embodiments, the second method further includes receiving one or more PUSCH repetitions in a dynamic flexible symbol during a survival time associated with the PUSCH transmission.
In one embodiment, the priority of the PUSCH transmission reverts to a previously configured priority value after transmitting a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACK). In another embodiment, the priority of the PUSCH transmission reverts to a previously configured priority value after expiry of a survival timer associated with the PUSCH transmission.
In some embodiments, the second method further includes scrambling the second DCI using a CS-RNTI of the communication device. In such embodiments, the second DCI may contain a plurality of modified L1 parameters for the at least one UL Type-2 CG, said plurality of modified L1 parameter selected from: a TCI state, a number of repetitions, a priority indicator, and an open loop power control parameter.
In some embodiments, the second DCI disables a feature during a survival time associated with the PUSCH transmission, said feature being one or more of: HARQ acknowledgement (i.e., Ack/Nack) deferral and/or disables SPS acknowledgement (i.e., Ack/Nack) skipping. In one embodiment, the second method includes enabling the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after receiving a predetermined number (i.e., one or N) of consecutive positive acknowledgements (i.e., ACKs). In another embodiment, the second method includes enabling the disabled feature (e.g., HARQ-Ack/Nack deferral and/or SPS-Ack/Nack skipping) after expiry of a predetermined time since receiving the second DCI (i.e., the activation DCI that disables the feature command).
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims priority to U.S. Provisional Patent Application No. 63/154,610 entitled “SEMI-PERSISTENT BASED MODIFICATION OF L1 PARAMETERS FOR TYPE-2 CG RESOURCE” and filed on Feb. 26, 2021, for Karthikeyan Ganesan, Hyejung Jung, Ankit Bhamri, Vijay Nangia, and Ravi Kuchibhotla, which application is incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2022/051755 | 2/28/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63154610 | Feb 2021 | US |
