A method and apparatus for logical channel restriction based on duplex mode

Abstract

Disclosed are devices, methods, and systems for selecting uplink transmission parameters based on duplex mode. One device (500) includes a processor (505) and a transceiver (525) that receives (705) a configuration including first and second sets of LCH restriction configurations. The transceiver (525) receives (710) an uplink resource allocation indicating a set of symbols for an initial PUSCH transmission, and the processor (505) generates (715) a TB corresponding to the uplink resource allocation. The TB is generated (715) using the first set of LCH restriction configurations when the set of symbols operates in a first duplex mode, and the TB is generated (715) using the second set of LCH restriction configurations when the set of symbols has at least one symbol indicated to operate in a second duplex mode. The transceiver (525) transmits (720) the generated TB on the allocated uplink resources.

Description

[0001] Cross-reference of related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 160,687, filed March 12, 2021, entitled "DUPLEX MODEBASED UPLINK TRANSMISSION PARAMETER SELECTION" by Joachim Lohr, Hyejung Jung, Vijay Nangia, and Ravi Kuchibhotla, which is incorporated herein by reference. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically, to the selection of uplink transmit parameters depending on the duplex mode. Background Technology

[0004] For the 3GPP New Radio (“NR”, i.e., 5th Generation Radio Access Technology (“RAT”)), Time Division Duplex (“TDD”) can be used in unpaired spectrum to avoid interference (e.g., UL and / or DL ​​interference within network entities and UE-to-UE interference). However, TDD limits uplink (“UL”) and downlink (“DL”) transmission opportunities and prevents simultaneous accommodation of emergency UL and DL transmissions.

[0005] Full-duplex (“FD”) operation is characterized by the ability to transmit and receive concurrently at the same time and frequency resources. FD operation at the gNB (i.e., NR base station) facilitates reception in the UL from a group of user equipment devices (“UEs”) simultaneously with DL transmissions to another (and potentially disjoint) group of UEs coexisting on the same channel. Summary of the Invention

[0006] A procedure for selecting uplink transmit parameters based on duplex mode is disclosed. The procedure may be implemented by a device, system, method, or computer program product.

[0007] A method for selecting uplink transmission parameters based on duplex mode at a user equipment (“UE”) includes receiving a configuration comprising: A) a first set of logical channel (“LCH”) restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. The method includes: receiving an uplink resource allocation from a network entity; generating a transport block (“TB”) corresponding to the uplink resource allocation, wherein the uplink resource allocation indicates uplink resources for transmission of an initial physical uplink shared channel (“PUSCH”). The TB is generated based on the first set of LCH restriction configurations when the PUSCH is to be transmitted in a set of symbols indicated to operate in a first duplex mode. Otherwise, the TB is generated based on the second set of LCH restriction configurations when the PUSCH is to be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode. The method includes transmitting the generated TB on the allocated uplink resources.

[0008] Another method at the UE includes: identifying a set of symbols corresponding to a time slot of a Physical Random Access Channel (“PRACH”) timing; and detecting overwrite time slot format information of the set of symbols, wherein the overwrite time slot format information indicates that the set of symbols is not an uplink symbol. The method includes: transmitting a first random access channel (“RACH”) message during the PRACH timing when the set of symbols corresponds to a full-duplex time slot.

[0009] A method for selecting uplink transmission parameters based on duplex mode at the RAN includes a transmission configuration comprising: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differs from the first set of logical channel restriction configurations. The method includes allocating uplink resources to the UE for transmission, the uplink resource allocation indicating uplink resources for initial PUSCH transmission. The method includes receiving a TB from the UE on the allocated uplink resources, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols indicated for operation in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols having at least one symbol indicated for operation in a second duplex mode.

[0010] Another method at the RAN includes transmitting overwrite slot format information for the set of symbols, wherein the overwrite slot format information indicates that the set of symbols is not an uplink symbol. The method includes receiving a first RACH message from the UE during the PRACH timing when the set of symbols corresponds to a full-duplex slot. Attached Figure Description

[0011] A more specific description of the embodiments briefly described above will be presented by referring to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and therefore should not be considered limiting; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0012] Figure 1 This is a block diagram illustrating an embodiment of a wireless communication system for selecting uplink transmission parameters based on duplex mode;

[0013] Figure 2 This is a diagram illustrating one embodiment of the New Radio ("NR") protocol stack of the Third Generation Partnership Project ("3GPP");

[0014] Figure 3 This is a diagram illustrating one embodiment of the use of time and frequency for different duplex modes;

[0015] Figure 4 This is a diagram illustrating an example of the abstract syntax representation (“ASN.1”) code for the MsgA-PUSCH-Config information element;

[0016] Figure 5 This is a block diagram illustrating an embodiment of a user equipment device that can be used to select uplink transmission parameters based on duplex mode;

[0017] Figure 6 This is a block diagram illustrating an embodiment of a network device that can be used to select uplink transmission parameters based on duplex mode;

[0018] Figure 7 This is a flowchart illustrating an embodiment of a method for selecting uplink transmit parameters based on duplex mode;

[0019] Figure 8 This is a flowchart illustrating another embodiment of a method for selecting uplink transmit parameters based on duplex mode;

[0020] Figure 9 This is a flowchart illustrating an embodiment of a method for a RACH procedure in full-duplex mode; and

[0021] Figure 10 This is a flowchart illustrating another embodiment of a method for a RACH procedure in full-duplex mode. Detailed Implementation

[0022] Those skilled in the art will understand that aspects of the embodiments may be embodied as systems, devices, methods, or program products. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0023] For example, the disclosed embodiments may be implemented as hardware circuitry (including custom very large-scale integration (“VLSI”) circuitry or gate arrays), off-the-shelf semiconductors (e.g., 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 be organized, for example, as objects, procedures, or functions.

[0024] 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 (hereinafter referred to as code). The storage device may be tangible, non-transitory, and / or non-emitting. The storage device may not embody signals. In certain embodiments, the storage device uses only signals to access the code.

[0025] Any combination of one or more computer-readable media may be used. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device for storing code. The storage device may be, for example (but not limited to), an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0026] Further specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that may contain or store programs for use by or in conjunction with an instruction execution system, device, or apparatus.

[0027] The code used to implement the operations of the embodiments may be written in any number of lines and may include one or more of the following programming languages: object-oriented programming languages ​​(e.g., Python, Ruby, Java, Smalltalk, C++, or similar), conventional procedural programming languages ​​(e.g., the "C" programming language or similar), and / or machine languages ​​(e.g., assembly language). The code may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including local area networks ("LANs"), wireless LANs ("WLANs"), or wide area networks ("WANs"), or may be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0028] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided to provide a thorough understanding of the embodiments, including examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail so as not to obscure aspects of the embodiments.

[0029] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases "in an embodiment," "in an embodiment," and similar language appearing throughout this specification may (but not necessarily) refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly specified otherwise, the terms "comprising," "including," "having," and variations thereof mean "comprising (but not limited to)." Unless expressly specified otherwise, the list of listed items does not imply that any or all items are mutually exclusive. Unless expressly specified otherwise, the terms "a" and "described" also refer to "one or more."

[0030] As used herein, a list containing the conjunction “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 term “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 term “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, excluding 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, excluding combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0031] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can 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 instructions executable by the processor of the computer or other programmable data processing apparatus create components for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0032] The code may also be stored in a storage device, which may instruct a computer, other programmable data processing equipment or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of writing containing instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0033] The code may also be loaded onto a computer, other programmable data processing equipment or other device to cause a series of operational steps to be performed on the computer, other programmable equipment or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0034] The flowcharts, diagrams, and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a code module, segment, or portion containing one or more executable instructions for implementing a specified logical function.

[0035] It should also be noted that in some alternative implementations, the functions described in the boxes may not occur in the order shown in the figures. For example, two boxes shown consecutively may actually be executed in substantial concurrent order, or the boxes may sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustration figures are conceivable.

[0036] While various arrow and line types may be used in call flows, flowcharts, and / or block diagrams, they should not be construed as limiting the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It should also be noted that each box in the block diagram and / or flowchart description, and combinations of boxes in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0037] The description of the elements in each figure can be referenced to the elements in the previous figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0038] Generally, this disclosure describes systems, methods, and apparatus for selecting uplink transmit parameters based on duplex mode. In some embodiments, the methods can be executed using computer code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solution described below.

[0039] This document discloses techniques for timely providing UL / DL symbols / time slots or UL / DL resources to a UE when the serving network entity has the ability to receive and transmit simultaneously (i.e., to perform full-duplex operation with a certain degree of self-interference suppression), while ongoing DL / UL services are being served.

[0040] Full-duplex (“FD”) operation at the serving gNB allows the gNB to receive UL transmissions from a first group of UEs while simultaneously transmitting DL transmissions to a second group of UEs. Compared to a half-duplex (“HDX”) gNB, this operation offers benefits / enhancements in terms of improved spectral efficiency and / or reduced latency. As used herein, the term “FD-gNB” refers to a RAN node (i.e., gNB) capable of full-duplex operation.

[0041] The FD operation is characterized by the ability to transmit and receive concurrently on the same time and frequency resources, facilitated by the self-interference cancellation (“SIC”) component at the FD node. FD operation at the gNB facilitates simultaneous uplink reception from a group of UEs with DL transmissions to another (and potentially disjoint) group of UEs coexisting on the same channel. Therefore, this demonstrates the potential for enhanced spectral efficiency and reduced latency.

[0042] Finally, some users may require or support FD operation; that is, they will need to use the same Physical Resource Block (“PRB”) in both the uplink and downlink. Using the same PRB for both transmission and reception will cause self-interference (“SI”); that is, the transmitted signal will leak energy into the receiver chain, thus contaminating the reception of the useful signal. In order to fully utilize the advantages of FD, SI needs to be properly managed, and for this reason, self-interference cancellation (“SIC”) technology is being extensively studied.

[0043] However, on the UE side, FD operation is challenged by the UE's SIC capability, which is limited in highly dynamic and power-constrained environments. On the gNB side, SIC is considered feasible to be fully implemented using a hybrid of analog filtering and digital cancellation techniques.

[0044] In FD systems where the gNB is FD and the UE is half-duplex (“HDX”), the FD is 1 / 2 multiplexed because they can use the same time frequency twice within the cell to schedule users in both the uplink (“UL”) and downlink (“DL”) directions. In practice, implementing such FD networks would be extremely useful for increasing capacity in overloaded networks.

[0045] Regarding hardware complexity and form factor at the transceiver level, a feasible system-level solution would only use full-duplex at the multi-antenna gNB, while the UE still operates in HDX mode. Using FD communication in the gNB presents both UL-DL user interference, intra-cell and inter-cell cross-linking interference (“CLI”) on the SI at each gNB, and gNB-to-gNB interference.

[0046] This document discloses a mechanism for efficient uplink transmission in time slots operated by the gNB in ​​full-duplex mode, i.e., simultaneous DL transmission occurring in time slots where UL transmission also occurs. When the UE transmits uplink channels / signals in symbols indicated as flexible or downlink, the signal interference and signal-to-noise ratio (“SINR”) of the uplink channels / signals at the network entity's receiver are likely to be low due to potential DL transmissions by the network entity. Therefore, specifically, this disclosure provides a method for ensuring that QoS requirements for UL transmissions are met in time slots where the gNB is operating in FD mode.

[0047] This disclosure provides a mechanism for selecting uplink transmit parameters based on duplex mode, wherein at least the following enhancements to the parameter selection are proposed and described:

[0048] In some embodiments, the UE applies a different set of LCH constraint configurations for the symbol group in which uplink transmissions occur, based on the uplink resource allocation depending on the duplex mode indicated by the gNB, for TB generation. In some embodiments, the UE applies a different set of LCH constraint configurations for PUSCH transmissions occurring on a set of symbols indicated as full-duplex and half-duplex. The uplink resource allocation (e.g., UL DCI) indicates which set of LCH constraints the UE will apply during the LCP procedure.

[0049] In some embodiments, the LCH / radio bearer is configured with parameters indicating which duplex mode the LCH / radio bearer supports. In some embodiments, for example, a new parameter / field is configured in the logicalChannelConfig IE that indicates whether data from this LCH / radio bearer is allowed to be multiplexed into a PUSCH / TB transmitted within a set of symbols / slots / PUSCH durations in which the gNB operates in full-duplex mode (i.e., simultaneous downlink transmission).

[0050] In some embodiments, the UL DCI indication for allocating uplink resources for PUSCH transmission is operated by the gNB for the duplex mode of the corresponding PUSCH. In some embodiments, the UE applies a different set of power control parameters (i.e., open-loop, path loss reference, and closed-loop configuration) to the scheduled UL transmission depending on the duplex mode operated by the gNB for the corresponding symbol / slot / PUSCH duration group.

[0051] In some embodiments, if the MsgA PUSCH transmission occurs in at least one symbol indicated for operation in full-duplex mode, the UE applies a separately predefined and / or separately configured MCS value and α value for the MsgA-PUSCH transmission. In some embodiments, the UE determines the duplex state of a symbol / symbol group / slot at a predefined specific time example (e.g., a predefined time prior to the PDCCH timing / slot received since the first UL authorization for the new transmission was triggered, or before the CG UL resources used for PHR transmission / calculation) to determine whether to calculate the PHR based on power control parameters for full-duplex or non-full-duplex mode.

[0052] Figure 1 A wireless communication system 100 for selecting uplink transmission parameters based on duplex mode, according to embodiments of the present disclosure, is described. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may be composed of a basic unit 121, and the remote unit 105 communicates with the basic unit 121 using a wireless communication link 123. Even Figure 1 The system depicts a specific number of remote units 105, basic units 121, wireless communication links 123, RAN 120, and mobile core network 140, but those skilled in the art will recognize that the wireless communication system 100 may include any number of remote units 105, basic units 121, wireless communication links 123, RAN 120, and mobile core network 140.

[0053] In one implementation, RAN 120 conforms to the fifth-generation (“5G”) cellular system specified in the 3GPP (“3GPP”) specification. For example, 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 instance, RAN 120 may contain non-3GPP RATs (e.g., Alternatively, it may conform to the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 series of WLANs. In another embodiment, RAN 120 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 may implement other open or proprietary communication networks, such as global interoperability for microwave access (“WiMAX”) or the IEEE 802.16 series of standards and other networks. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0054] In one embodiment, remote unit 105 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smartphone, smart TV (e.g., a TV connected to the Internet), smart appliance (e.g., an appliance connected to the Internet), set-top box, game console, security system (including surveillance cameras), in-vehicle computer, network device (e.g., router, switch, modem), or the like. In some embodiments, remote unit 105 includes a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, remote unit 105 may be referred to as UE, user unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, user station, user terminal, wireless transmit / receive unit (“WTRU”), apparatus, or other terms used in the art. In various embodiments, remote unit 105 includes a user identity and / or identification module (“SIM”) and mobile equipment (“ME”) that provide mobile terminal functions such as radio transmission, handover, voice encoding and decoding, error detection and correction, signaling, and access to the SIM. In some embodiments, the remote unit 105 may include terminal equipment (“TE”) and / or be embedded in an appliance or device (e.g., a computing device, as described above).

[0055] Remote unit 105 can communicate directly with one or more of the basic units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals can be carried via wireless communication link 123. The UL communication signal may include one or more uplink channels, such as the Physical Uplink Control Channel (“PUCCH”) and / or the Physical Uplink Shared Channel (“PUSCH”), while the DL communication signal may include one or more downlink channels, such as the Physical Downlink Control Channel (“PDCCH”) and / or the Physical Downlink Shared Channel (“PDSCH”). Here, RAN 120 is an intermediate network providing remote unit 105 with access to the mobile core network 140.

[0056] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Internet Protocol Voice Telephony (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0057] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Remote unit 105 may establish additional PDU sessions to communicate with other data networks and / or other communication peers.

[0058] 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 a remote unit 105 and a specific data network (“DN”) via UPF 141. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0059] In the context of a 4G / LTE system, such as an Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides end-to-end connectivity between the remote unit and the PDN. The PDN connectivity procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the PDN gateway (“PGW”, not shown) in the mobile core network 140. In some embodiments, a one-to-one mapping may exist between the EPS bearer and a QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier (“QCI”).

[0060] Basic unit 121 may be distributed across a geographical area. In some embodiments, basic unit 121 may also be referred to as an access terminal, access point, base station, base station, node-B (“NB”), evolved node B (abbreviated as eNodeB or “eNB”, also referred to as an evolved universal terrestrial radio access network (“E-UTRAN”) node B), 5G / NR node B (“gNB”), home node-B, relay node, RAN node, or referred to by any other terminology used in the art. Basic unit 121 typically comprises a portion of a RAN (e.g., RAN 120) communicatively coupled to one or more controllers corresponding to basic unit 121. These and other elements of the radio access network are not described but are generally well known to those skilled in the art. Basic unit 121 is connected to mobile core network 140 via RAN 120.

[0061] Basic unit 121 can serve several remote units 105 within a service area (e.g., a cell or cell sector) via wireless communication link 123. Basic unit 121 can communicate directly with one or more of the remote units 105 via communication signals. Typically, basic unit 121 transmits DL communication signals to serve the remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried via wireless communication link 123. Wireless communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the basic unit 121.

[0062] Note that during NR operation on unlicensed spectrum (referred to as "NR-U"), basic unit 121 and remote unit 105 communicate via unlicensed (i.e., shared) radio spectrum. Similarly, during LTE operation on unlicensed spectrum (referred to as "LTE-U"), basic unit 121 and remote unit 105 also communicate via unlicensed (i.e., shared) radio spectrum.

[0063] In one embodiment, the mobile core network 140 is a 5G core network (“5GC”) or an evolved packet core (“EPC”) that may be coupled to a packet data network 150, such as the Internet, private data networks, and other data networks. The remote unit 105 may have a subscription or other account to the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”) and / or a public terrestrial mobile network (“PLMN”). This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0064] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes at least one UPF 141. Mobile core network 140 also includes multiple control plane (“CP”) functions, including (but not limited to) access and mobility management functions (“AMF”) 143, session management functions (“SMF”) 145, policy control functions (“PCF”) 147, unified data management functions (“UDM”), and user data repository (“UDR”) serving RAN 120. In some embodiments, UDM and UDR are co-located and depicted as a combined entity “UDM / UDR” 149. Although Figure 1 The description contains a specific number and type of network functions, but those skilled in the art should recognize that the mobile core network 140 may contain any number and type of network functions.

[0065] In the 5G architecture, UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting the data network (DN). AMF 143 is responsible for non-access spectrum (“NAS”) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. SMF 145 is responsible for session management (i.e., session establishment, modification, and release), remote unit (i.e., UE) Internet Protocol (“IP”) address allocation and management, DL data notification, and service orientation configuration of UPF 141 for correct service routing.

[0066] PCF 147 is responsible for the unified policy framework, providing policy rules to CP functions and accessing subscription information in the UDR used for policy decisions. UDM is responsible for authentication and Key Protocol (“AKA”) credential generation, user identifier handling, access authorization, and subscription management. The UDR is a repository of subscription information and can be used to serve several network functions. For example, the UDR can store subscription data, policy-related data, subscription-related data permitted to be exposed to third-party applications, and the like.

[0067] 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 the appropriate services among themselves and communicate with each other via 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 5GC. When present, the AUSF may be used as an authentication server and / or authentication proxy, thereby allowing AMF 143 to authenticate remote unit 105. In some embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0068] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, each mobile data connection utilizing a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") services. As another example, one or more network slices may be optimized for ultra-reliable low-latency communication ("URLLC") services. In other instances, network slices may be optimized for machine-type communication ("MTC") services, massive MTC ("mMTC") services, and Internet of Things ("IoT") services. In still other instances, network slices may be deployed for dedicated services, vertical services, specific use cases, etc.

[0069] Network slice examples can be identified by single network slice selection aid information (“S-NSSAI”), while a set of network slices authorized for use by remote unit 105 is identified by network slice selection aid information (“NSSAI”). Here, “NSSAI” refers to a vector value containing one or more S-NSSAI values. In some embodiments, various network slices may contain individual examples of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For ease of illustration, Figure 1 Different network slices are not shown, but their support is assumed.

[0070] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the described embodiments for selecting uplink transmission parameters based on duplex mode are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular networks), General Packet Radio Service (“GPRS”), General Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like.

[0071] Furthermore, in the LTE variant of the mobile core network 140 where EPC is used, the described network functions can be replaced by appropriate EPC entities (e.g., Mobility Management Entity (“MME”), Serving Gateway (“SGW”), PGW, Home Subscriber Server (“HSS”), and the like). For example, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or mapped to the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0072] The public provides schemes that allow network entities to dynamically schedule UL transmissions using different LCH constraint configurations and / or uplink transmit parameters to address different interference conditions / received SINRs when operating in different duplex modes (i.e., half-duplex and full-duplex). These schemes provide support for QoS-aware uplink scheduling, thereby taking into account the QoS requirements of the associated radio bearers.

[0073] In the following description, the term "gNB" is used for base station / basic unit, but it can be replaced by any other radio access node (e.g., RAN node, ng-eNB, eNB, base station ("BS"), access point ("AP"), NR BS, 5G NB), transmit and receive point ("TRP"), etc. Additionally, the term "UE" is used for mobile station / remote unit, which can be replaced by any other remote device (e.g., remote unit, MS, ME, etc.). Furthermore, the operation is primarily described in the context of 5G NR. However, the solutions / methods described below are also applicable to other mobile communication systems using duplex mode-based selection of uplink transmit parameters.

[0074] Figure 2 An NR protocol stack 200 according to an embodiment of this disclosure is depicted. Although Figure 2 The diagram shows UE 205, RAN node 207, and 5G core network 209, but these represent a set of remote units 105 interacting with basic unit 121 and mobile core network 140. As depicted, protocol stack 200 includes user plane protocol stack 201 and control plane protocol stack 203. User plane protocol stack 201 includes physical (“PHY”) layer 211, media access control (“MAC”) sublayer 213, radio link control (“RLC”) sublayer 215, packet data convergence protocol (“PDCP”) sublayer 217, and service data adaptation protocol (“SDAP”) layer 219. Control plane protocol stack 203 includes physical layer 211, MAC sublayer 213, RLC sublayer 215, and PDCP sublayer 217. Control plane protocol stack 203 also includes radio resource control (“RRC”) layer 221 and non-access layer (“NAS”) layer 223.

[0075] The AS layer 225 of the user plane protocol stack 201 (also referred to as the "AS protocol stack") consists of at least SDAP, PDCP, RLC, and MAC sublayers and a physical layer. The AS layer 227 of the control plane protocol stack 203 consists of at least RRC, PDCP, RLC, and MAC sublayers and a physical layer. Layer 1 ("L1") contains the PHY layer 211. Layer 2 ("L2") is divided into SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") contains the RRC sublayer 221 of the control plane and the NAS layer 223, and contains, for example, the Internet Protocol ("IP") layer or PDU layer of the user plane (note the depiction). 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." As an example, "upper-layer signaling" may refer to signaling exchange at the RRC layer 221.

[0076] Physical layer 211 provides transport channels to MAC sublayer 213. MAC sublayer 213 provides logical channels to RLC sublayer 215. RLC sublayer 215 provides RLC channels to PDCP sublayer 217. PDCP sublayer 217 provides radio bearers to SDAP sublayer 219 and / or RRC layer 221. SDAP sublayer 219 provides QoS flows to the core network (e.g., 5GC). RRC layer 221 provides the addition, modification, and release of carrier aggregation (“CA”) and / or dual connectivity (“DC”). RRC layer 221 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRB”) and data radio bearers (“DRB”).

[0077] NAS layer 223 is located between UE 205 and 5GC 209. NAS messages are transparently transmitted through the RAN. NAS layer 223 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 205 as UE 205 moves between different cells in the RAN. In contrast, AS layers 225 / 227 carry information between UE 205 and the RAN via the radio portion of the network. Although Figure 2 It is not described in the text, but the IP layer exists above the NAS layer 223, the transport layer exists above the IP layer, and the application layer exists above the transport layer.

[0078] 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 via a transport channel, and its connection to the RLC layer 215 above is via a logical channel. MAC layer 213 therefore performs multiplexing and demultiplexing between the logical and transport channels: on the transmitting side, MAC layer 213 constructs a MAC PDU, called a transport block, from the MAC Service Data Unit (“SDU”) received via the logical channel, and on the receiving side, MAC layer 213 recovers the MAC SDU from the MAC PDU received via the transport channel.

[0079] MAC layer 213 provides data transmission services to RLC layer 215 via logical channels, which are either control logical channels carrying control data (e.g., RRC signaling) or service logical channels carrying user plane data. On the other hand, data from MAC layer 213 is exchanged with the physical layer via transport channels classified as downlink or uplink. Data is multiplexed into transport channels depending on how it was transmitted in the air.

[0080] PHY layer 211 is responsible for the actual transmission of data and control information via the air interface; that is, PHY layer 211 carries all information from the MAC transport channel via the air interface on the transmitting side. Some of the important functions performed by PHY layer 211 include coding and modulation for RRC layer 221, link adaptation (e.g., adaptive modulation and coding (“AMC”)), power control, cell search (for initial synchronization and handover purposes), and other measurements (within and between 3GPP systems (i.e., NR and / or LTE systems)). PHY layer 211 performs transmission based on transmission parameters (e.g., modulation scheme, coding rate (i.e., modulation and coding scheme (“MCS”)), number of physical resource blocks, etc.).

[0081] This disclosure presents a method for achieving efficient uplink transmission in time slots operated by the gNB in ​​full-duplex mode, i.e., simultaneous DL transmission occurring in time slots where UL transmission also occurs. When the UE transmits uplink channels / signals in symbols indicated as flexible or downlink, the signal interference and signal-to-noise ratio (“SINR”) of the uplink channels / signals at the network entity's receiver are likely to be low due to potential DL transmissions by the network entity. Therefore, this disclosure provides a method to ensure that QoS requirements for UL transmissions are met in time slots where the gNB is operating in FD mode.

[0082] The UE applies a different set of LCH constraint configurations for UL transmissions depending on the full-duplex mode in which the gNB operates during the corresponding PUSCH duration. For example, when the gNB operates in full-duplex mode, the UE should not multiplex URLLC services to PUSCH transmissions due to the low SINR of the uplink channel / signal at the receiver of the network entity caused by potential DL transmissions by the network entity. Similarly, a different set of power control parameters and / or uplink transmission parameters are used for UL transmissions by the gNB operating in FD mode.

[0083] According to the first embodiment, the UE depends on the duplex mode in which the gNB operates during the corresponding PUSCH duration to apply a different set of LCH restrictions for scheduled UL transmissions. In one instance, the UE responds to determining that the gNB operates in FD mode during the corresponding PUSCH duration to apply a first set of LCH restrictions for UL transmissions, while the UE responds to determining that the gNB operates in non-FD mode during the corresponding PUSCH duration to apply a second set of LCH restrictions for PUSCH transmissions.

[0084] According to the second embodiment, the UE's LCH / radio bearer is configured with parameters indicating which duplex mode this LCH / radio bearer supports. In one instance, for example, in the logicalchannelconfig IE, a new parameter / field is configured for each logical channel / radio bearer that indicates whether data from this LCH / radio bearer is allowed to be multiplexed into the PUSCH transmitted in a slot where the gNB operates in FD mode (i.e., simultaneous downlink transmission).

[0085] Figure 3 This section depicts different duplex modes and examples of their corresponding frequency and time usage. For Frequency Division Duplex (“FDD”) mode, the first portion of the frequency band is used for uplink (“UL”) transmission, and the second portion is used for downlink (“DL”) transmission. For pure FDD mode, there is no difference in the time domain between UL and DL transmissions, meaning that UL and DL transmissions can use the same time resources to perform simultaneously. Note that a duplex gap (i.e., a guard band) exists in the frequency band, which separates the UL frequency from the DL frequency (i.e., prevents inter-carrier interference).

[0086] For TDD mode, the first part of the time domain (i.e., the first time slot or the first set of time slots) is used for uplink (“UL”) transmission, and the second part of the time domain (i.e., the second time slot or the second set of time slots) is used for downlink (“DL”) transmission. For pure TDD mode, there is no difference in the frequency domain between UL and DL transmissions, meaning that UL and DL transmissions can be performed across the entire frequency band (i.e., using the same frequency resources). Note that a guard period (i.e., a time slot) exists in the time domain, which separates the UL and DL time slots (i.e., prevents inter-slot interference). Also note that some wireless communication systems employ a combination of FDD and TDD principles, i.e., separating UL and DL transmissions in both time and frequency aspects.

[0087] FDD and TDD are examples of half-duplex operation. In contrast, for full-duplex (“FD”) mode, UL and DL transmissions can be performed across the entire frequency band (i.e., using the same frequency resources and the same time resources). FD operation is characterized by the ability to transmit and receive concurrently at the same time and on the same frequency resources, facilitated by self-interference cancellation (“SIC”) at the FD node. In contrast, half-duplex operation provides, for example, communication in two directions, but only in one direction at a time (i.e., TDD), rather than simultaneously in both directions.

[0088] Whenever a new transmission is performed, a Logical Channel Prioritization (“LCP”) procedure is applied. The RRC entity (i.e., at RRC layer 221) controls the scheduling of uplink data by signaling the following parameters to each logical channel of each MAC entity: the parameter priority, where an increased priority value indicates a lower priority level; the parameter prioritizedBitRate, which sets the prioritized bit rate (“PBR”); and the parameter bucketSizeDuration, which sets the bucket size duration (“BSD”).

[0089] The RRC entity further controls the LCP procedure by configuring mapping restrictions for each logical channel, including the following parameters: allowedSCS-List, which sets the subcarrier spacing allowed for transmission; maxPUSCH-Duration, which sets the maximum PUSCH duration allowed for transmission; configuredGrantType1Allowed, which sets whether configured grant (“CG”) type 1 can be used for transmission; allowedServingCells, which sets the cells allowed for transmission; allowedCG-List, which sets the configured grants allowed for transmission; and allowedPHY-PriorityIndex, which sets the PHY priority index of the dynamic grants allowed for transmission.

[0090] The logical channel prioritization procedure also uses a UE variable Bj, which is maintained for each logical channel j. When a logical channel is established, the MAC entity (i.e., at MAC layer 213) should initialize Bj of the logical channel to zero.

[0091] For each logical channel j, the MAC entity should: A) increment Bj by the product PBR×T before each instance of the LCP procedure, where T is the time elapsed since Bj was last incremented; and B) set Bj to the bucket size if the value of Bj is greater than the bucket size (i.e., PBR×BSD).

[0092] Note that, as long as Bj is up-to-date when the authorization is processed through LCP, the exact time when the UE updates Bj between LCP procedures depends on the UE implementation scheme.

[0093] Regardless of the choice of logical channel, when performing a new transmission, the MAC entity shall select a logical channel for each UL grant that satisfies all of the following conditions: 1) the allowed subcarrier spacing (“SCS”) index value set in the allowedSCS-List (if configured) contains the subcarrier spacing index associated with the UL grant; and 2) maxPUSCH-Duration (if configured) is greater than or equal to the PUSCH transmission duration associated with the UL grant; and 3) configuredGrantType1Allowed (if configured) is set to true if the UL grant is configured grant (“CG”) type 1; and 4) allowedSe rvingCells (if configured) contains cell information associated with UL grants (note that this does not apply to logical channels associated with DRBs configured with PDCP replication (i.e., CA replication) within the same MAC entity when CA replication is deactivated for this data radio bearer (“DRB”) in this MAC entity); and 5) allowedCG-List (if configured) contains a configured grant index associated with UL grants; and 6) allowedPHY-PriorityIndex (if configured) contains a priority index associated with dynamic UL grants (as specified in Clause 9 of 3GPP Technical Specification (“TS”) 38.213).

[0094] Note that the subcarrier spacing index, PUSCH transmission duration, cell information, and priority index are included in the uplink transmission information received from the lower layer for the corresponding scheduled uplink transmission.

[0095] Power control (“PC”) and power headroom (“PHR”) formulas for certain aspects of bandwidth portion (“BWP”) operation are adopted in 5G operation. For example, according to 3GPP TS 38.213, if a UE transmits PUSCH on UL BWP b of carrier f in serving cell c using parameter settings configured with index j and PUSCH power control adjustment state with index l, then the UE should set the PUSCH transmit power P in PUSCH transmit period i. PUSCH,b,f,c (i,j,q d ,l) determined as

[0096]

[0097] All parameters are defined in 3GPP TS 38.213. Specifically, most PC parameters are configured based on the UL BWP and include: the UE-specific component Po_UE of the target power spectral density (“PSD”) value; the fractional path loss compensation factor α; the path loss (“PL”) reference; the closed-loop power control (“CL-PC”) process; and the transmit bandwidth (i.e., the number of PRBs) allocation. However, the configured maximum UE transmit power Pcmax,f,c and the nominal component Po_nominal of the target PSD value are configured based on the UL carrier of the serving cell, but are not dependent on the selection of the UL BWP.

[0098] Regarding the RACH procedure, the effective PRACH timing in the unpaired spectrum can be defined as follows:

[0099] For unpaired spectrum, if the UE is not provided with tdd-UL-DL-ConfigurationCommon, then the PRACH timing in the PRACH slot is valid if it does not begin before the Synchronization Signal / Physical Broadcast Channel (“SS / PBCH”) block in the PRACH slot and at least N_gap symbols after the last SS / PBCH block received, where N_gap is provided in Table 8.1-2, and if channelAccessMode = 'Semi-static’ is provided, then it will not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which the UE has not transmitted (see 3GPP TS 37.213). Note that the candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in System Information Block #1 (“SIB1”) or in ServingCellConfigCommon, as described in Clause 4.1 of 3GPP TS 38.213.

[0100] For unpaired spectrum, if the UE is provided with tdd-UL-DL-ConfigurationCommon, then the PRACH timing in the PRACH slot is valid if it is within a UL symbol, or if it does not begin before the SS / PBCH block in the PRACH slot and after at least N_gap symbols following the last downlink symbol and after at least N_gap symbols following the last SS / PBCH block symbol, where N_gap is provided in Table 8.1-2, and if channelAccessMode = 'semi-static' is provided, then it should not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which no transmission should occur, as described in 3GPP TS 37.213. Note that the candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided in SIB1 or in ServingCellConfigCommon, as described in Clause 4.1 of 3GPP TS 38.213.

[0101] It should be noted that throughout this disclosure, the terms “symbol,” “time slot,” “sub-slot,” and “transmission interval” refer to a unit of time having a specific duration. For example, “symbol” may refer to a fraction / percentage of the orthogonal frequency division multiplexing (“OFDM”) symbol length associated with a particular subcarrier spacing (“SCS”). In the following, a UL transmission (UL transmission burst) may include multiple transmissions (e.g., in cases where priority is associated with transmissions, multiple transmissions of the same / different priorities may be included).

[0102] According to an embodiment of the first solution, the UE may apply a set of different logical channel (“LCH”) restrictions for scheduled UL transmissions depending on the duplex mode (or generally, an indication or LCH / radio bearer mapping mode / type) indicated by the gNB’s operation within a symbol group (or subgroup) (e.g., the PUSCH duration) in which uplink transmissions occur. In one instance, the UE applies a first set of LCH restrictions for UL transmissions in response to determining that the gNB is operating in full-duplex (“FD”) mode within the corresponding PUSCH duration (or the UE receives an indication of a first mapping mode / type within the corresponding PUSCH duration), and applies a second set of LCH restrictions for PUSCH transmissions in response to the gNB operating in non-FD mode within the corresponding PUSCH duration (or the UE receives an indication of a second mapping mode / type within the corresponding PUSCH duration).

[0103] In some instances, full-duplex mode may include gNB operating in flexible or variable-duplex mode, for example, where the duplex Tx-Rx carrier center frequency separation between any transmit (“Tx”) and receive (“Rx”) channel pairs operated by the gNB is less than the nominal value of the operating band or the default Tx-Rx carrier center frequency separation. For the UE, the Tx-Rx carrier center frequency separation is at least the separation between the default Tx channel (carrier center frequency) and the Rx channel (carrier center frequency) of the operating band (e.g., as specified in 3GPP TS38.101). In other instances, full-duplex mode may include gNB operating a carrier to simultaneously receive uplink on a first frequency portion (e.g., BWP) of the carrier and transmit on a second frequency portion (e.g., BWP) of the carrier. The separation between the first and second frequency portions may be less than a threshold.

[0104] One motivation for using a different set of LCH constraint configurations for different duplex modes (i.e., full-duplex and half-duplex) is to impose restrictions on the UE's uplink transmission parameters (e.g., allowed SCS, maximum PUSCH duration, logical channel priority, etc.) in order to control which LCHs the UE is allowed to multiplex in PUSCH transmissions so as not to compromise the perceived quality of service (“QoS”) of UL transmissions due to increased interference caused by full-duplex operation at the network entity (e.g., gNB). When the network entity operates in full-duplex mode by scheduling or configuring the first UE to transmit UL signals / channels and scheduling the second UE to receive DL signals / channels, the UL signals / channels at the network entity's receivers may suffer from significant self-interference caused by the network entity's transmitters.

[0105] In one instance, the UE can be configured to avoid multiplexing services requiring high reliability (e.g., ultra-reliable and low-latency communication (“URLLC”) data) in PUSCH transmissions operating in full-duplex mode on the gNB side. Because the interference levels for full-duplex operation at network entities can differ from those for half-duplex operation at network entities, the supported QoS for full-duplex symbols / slots can be lower compared to non-FD slots.

[0106] The UE can determine the duplex mode / state / mapping mode (e.g., full-duplex and half-duplex modes) of a symbol / slot based on, for example, explicit signaling / indication received from the gNB. In one embodiment, the gNB indicates to the UE a set of time examples (e.g., slots / symbols) in which the gNB can operate in FD mode. In one instance, downlink control information (“DCT”) scheduling PUSCH transmissions indicates whether the gNB operates the corresponding symbol / slot in which the PUSCH transmission occurs in full-duplex mode or non-FD mode.

[0107] In another implementation, the DCI indicates which set of LCH restrictions should be used for the corresponding PUSCH transmission. In one instance, a flag within the DCI is used to indicate which of the two sets of LCH restriction parameters / configurations should be used for the associated PUSCH transmission. This mechanism allows the gNB to dynamically switch between different (i.e., two) LCH restriction configuration groups.

[0108] Similar to dynamically scheduled PUSCH transmissions, the UE can apply a different set of LCH constraint configurations for situations where a configured uplink transmission happens to occur on a set of symbols / PRBs operating in FD mode via the gNB (i.e., the gNB performs DL transmissions on at least one of the symbols / PRBs used for CG PUSCH). In one instance, the UE can apply a different set of LCH constraints / configurations for FD slots such that LCHs with high reliability requirements are not allowed to be multiplexed to the configured uplink grant.

[0109] According to another embodiment, the uplink configured grant configuration includes more than one transport block size parameter, each of the more than one configured transport block size associated with a duplex mode / state / mapping mode. In one instance, the UE applies a first configured transport block size (“TBS”) and / or modulation and coding scheme (“MCS”) for cases where the configured uplink transmission happens to occur on (a set of) symbols / PRBs operating in FD mode via the gNB (i.e., the gNB performs DL transmission on at least one of the symbols / PRBs used for CGPUSCH), and applies a second configured transport block size and / or MCS for cases where the configured uplink transmission happens to occur on (a set of) symbols / PRBs operating in non-FD mode via the gNB. In one implementation, the UE is configured with multiple mcsAndTBS fields / parameters in IE ConfiguredGrantConfig, for example, one for FD mode and one for non-FD mode.

[0110] According to another embodiment, the LCH / radio bearer is configured with parameters indicating which duplex mode (or mapping mode) this LCH / radio bearer supports. In one instance, for example, in the logicalchannelconfig IE, a new parameter / field is configured for each logical channel / radio bearer indicating whether data from this LCH / radio bearer is allowed to be multiplexed into a PUSCH / TB transmitted over a set of symbols / slots / PUSCH durations in which the gNB operates in FD mode (i.e., simultaneous downlink transmission on at least one of the symbols / slots). This new field can indicate whether the LCH / radio bearer supports FD operation mode. In one instance, when no parameter / field is configured for the LCH / radio bearer, data from this LCH / radio bearer is allowed to be multiplexed into a PUSCH / TB when the gNB operates in any duplex or mapping mode.

[0111] According to another embodiment, the UE is not allowed to multiplex the MAC control element (“CE”) in the PUSCH transmission during the duration of the symbol / slot / PUSCH transmission that is operated in FD mode. In one instance, the UE only considers uplink shared channel (“UL-SCH”) resources scheduled in symbols / slots indicated as non-full-duplex by the gNB as valid UL-SCH resources for transmitting the MAC CE. For example, in the case of carrier aggregation (“CA”), where the UE has multiple UL resource allocations concurrently on different serving cells, the UE should multiplex the MAC CE (if triggered) on the PUSCH of the serving cell that is indicated as not operating in FD mode.

[0112] When a network entity operates in full-duplex mode by scheduling the first UE to transmit UL signals / channels and scheduling the second UE to receive DL signals / channels, the UL signals / channels at the network entity's receivers may suffer significant self-interference caused by the network entity's transmitters. Therefore, the achievable UL data rate can be lower compared to the half-duplex scenario.

[0113] According to an embodiment of the second solution, the UE may apply different power control (“PC”) parameter sets (i.e., open-loop, path loss reference, and closed-loop configuration) for scheduled UL transmissions depending on the duplex mode of the time slot / PUSCH duration corresponding to the gNB operation. In one instance, the UE applies a first PC parameter set for UL transmissions in response to determining that the time slot of the gNB operation in which the corresponding PUSCH transmission occurs in FD mode, and applies a second PC parameter set in response to determining that the time slot of the PUSCH transmission is operated by the gNB in ​​non-FD mode.

[0114] In one example, different PC parameters (at least different open-loop parameters and / or path loss references) are configured for different duplex modes. When the gNB wants to operate in different time slots in different duplex modes, the UE can be configured with different open-loop power control parameters, for example, due to the possible different interference levels of the duplex modes and the different target power spectral density Po and fractional path loss compensation factor α of the possible different closed-loop power control loops.

[0115] According to another embodiment, the UE applies a power offset for uplink transmissions (e.g., PUSCH and / or sounding reference signal (“SRS”) and / or PUCCH (referred to as PUSCH / SRS / PUCCH)) occurring in symbols / slots indicated by the gNB to be operating in FD mode. This power offset may be predefined / preconfigured or explicitly indicated, for example, with an indication that certain symbols / slots are being operated in FD mode by the gNB. The offset may be positive (increasing uplink transmit power) or negative (i.e., decreasing uplink transmit power to limit interference to concurrent DL transmissions). Different UL channels (e.g., PUSCH / SRS / PUCCH) may have separate power offsets defined and / or configured and / or signaled.

[0116] According to another embodiment, the UE determines the duplex mode / state of a symbol / symbol group / slot at a predefined specific time example (e.g., a predefined time before the PDCCH timing / slot received since the PHR has been triggered, or the CG UL resources used for PHR transmission / calculation, e.g., PUSCH preparation time) to determine whether to calculate the PHR based on power control parameters for FD mode or non-FD mode. In one instance, the UE considers performing PHR calculation in slot / symbol N (all control signaling is not received until N-Tpredefined) to determine via the gNB whether slot / symbol N is operating in FD mode or non-FD mode for PHR calculation. Because the UE cannot reliably predict the duplex state / mode of the time / slot where the PHR is reported, the UE will determine the duplex mode / state of the slot based on information received until a predefined time before the slot where the PHR is reported, and thus determine the power control parameters to be used for PHR calculation.

[0117] In one instance, within the current symbol / slot n, if the slot will be considered up to T before slot / symbol n... process,2 If the FD time slot of the newly received authorization / control signaling is used, then the UE should apply the power control parameters configured for FD operation.

[0118] When a UE transmits an uplink channel / signal in a symbol indicated as flexible or downlink (e.g., the gNB operates in full FD mode), the signal interference and signal-to-noise ratio (“SINR”) of the uplink channel / signal at the network entity’s receiver may be low due to potential DL transmissions by the network entity. Therefore, the UE can be configured to transmit the uplink channel / signal at higher transmit power in symbols indicated as flexible or DL ​​based on a larger 'Po' value and / or a larger 'α' value. Furthermore, the UE can be configured to maintain a separate power control adjustment state for transmissions in symbols indicated as flexible or DL ​​(e.g., in FD mode) or reset the power control adjustment state whenever a switch occurs between a transmission in a symbol indicated as flexible / DL and a transmission in a symbol indicated as UL, because the co-channel interference level for full-duplex operation at the network entity may differ from the co-channel interference level for half-duplex operation at the network entity.

[0119] According to an embodiment of the third solution, even when the time slot format information indicates that a set of symbols corresponding to the PRACH timing in a full-duplex time slot is not an uplink symbol, the UE can still transmit a first RACH message during said set of symbols.

[0120] In the implementation, full-duplex operation within a cell may be permitted to utilize resources, where the Physical Random Access Channel (“PRACH”) may be transmitted by one or more UEs within the cell. For example, for a set of symbols in a slot corresponding to a valid PRACH timing (i.e., the set of symbols in a slot configured as UL symbols), the UE may detect a DCI format having a downlink or flexible SFI index field value indicating the set of symbols in the slot; that is, a slot format indicator (“SFI”) dynamically signaled by the slot overrides the semi-statically configured slot format of the slot, and the gNB operates the slot in full-duplex mode.

[0121] When a set of symbols corresponding to a valid PRACH timing slot is designated as an FD slot, the UE can transmit PRACH with an additional power offset to compensate for the lower SINR at the gNB due to potential DL transmissions by network entities. Similar to the additional power offset for a 2-step random access procedure (aka RACH procedure), i.e., POWER_OFFSET_2STEP_RA, a separate power offset for FD operation (e.g., POWER_OFFSET_FullDuplex) is an implementation based on the UE transmitting PRACH in a slot / symbol designated by the network for operation in FD mode.

[0122] In another implementation, a separate power ramp factor is used for the transmission of the random access channel (“RACH”) preamble when the symbols in the time slot corresponding to the valid PRACH timing are operated in full-duplex mode by a network entity (e.g., a gNB).

[0123] In one embodiment, when the UE performs a MsgA (i.e., the first message of the 2-step RACH procedure) PUSCH transmission in at least one symbol indicating operation in full-duplex mode (e.g., via cell-specific (e.g., tdd-UL-DL-ConfigurationCommon) and additional UE-specific (e.g., tdd-UL-DL-ConfigurationDedicated) RRC configuration or via DCI indicating downlink), the UE applies separately predefined and / or separately configured MCS and α values ​​for the MsgA-PUSCH transmission. According to the current specification, IE MsgA-PUSCH-Config is used to specify the PUSCH allocation for MsgA in the 2-step random access type procedure.

[0124] Figure 4 An instance of the abstract syntax representation (“ASN.1”) code depicting the MsgA-PUSCH-Config information element (“IE”). In one implementation, the additional parameters msgA-Alpha-fullduplex 405 and msgA-MCS-fullduplex 410 are configured within the IE MsgA-PUSCH-Config, indicating the MCS and α values ​​to be used for situations where MsgA-PUSCH occurs in a slot / symbol operating in FD mode via gNB (e.g., on at least one symbol in the slot / symbol).

[0125] In one embodiment, for a contention-free random access procedure, in response to the UE's detection of a PDCCH command, the UE may receive an indication to use a supplementary PRACH timing for the contention-free random access procedure, wherein the supplementary PRACH timing is a PRACH timing containing at least one flexible or DL ​​symbol configured for unpaired spectrum via tdd-UL-DL-ConfigurationCommon, or a PRACH timing within a DL carrier of paired spectrum. For example, when a network entity has urgent DL data to transmit to a UE that is not uplink synchronized, and if the synchronization signal block (“SSB”) to PRACH association period (i.e., the minimum number of PRACH configuration periods in which the SS / PBCH block index is mapped to a PRACH timing at least once) is set to long, then the network entity may schedule the UE to transmit PRACH on a supplementary PRACH timing. The network entity may dynamically associate the SSB with a given supplementary PRACH timing, rather than configuring a semi-static association pattern between the SSB index and the supplementary PRACH timing.

[0126] In one implementation, the UE can determine multiple supplementary PRACH opportunities within a PRACH configuration period (e.g., 10, 20, 40, 80, or 160 ms) and further determine multiple subsets of supplementary PRACH opportunities within the PRACH configuration period based on the received PRACH configuration index, the semi-static / cell-specific slot format configuration (provided by tdd-UL-DL-ConfigurationCommon), the semi-static / cell-specific SSB position (provided by ssb-PositionsInBurst), and the number of subsets of supplementary PRACH opportunities within the PRACH configuration period. In the PDCCH command that triggers the contention-free random access procedure, the UE can receive information about the subset of supplementary PRACH opportunities in which the UE can transmit a contention-free PRACH preamble. In this case, the SS / PBCH index in the PDCCH command is not used to determine the PRACH opportunity but can be used to determine the parameter referenceSignalPower for path loss estimation (in cases where the SSB transmits at different transmit powers).

[0127] In one instance, if the Cyclic Redundancy Check (“CRC”) of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (“C-RNTI”) and the “Frequency Domain Resource Assignment” field is all 1s, then DCI format 1_0 is for a random access procedure initiated by a PDCCH command, where the fields are set as follows:

[0128] • DCI format identifier - 1 bit

[0129] • This field is always set to 1, indicating DL DCI format.

[0130] • Frequency domain resource allocation - where the bits are given by clause 7.3.1.0

[0131] • Random access preamble index - 6 bits, according to clause 5.1.2 of 3GPP TS 38.321, ra-PreambleIndex

[0132] • UL / SUL Indicator -1 bit. If the value of "Random Access Preamble Index" is not all zeros and if the UE in the cell is configured with supplementaryUplink in ServingCellConfig, then this field indicates which UL carrier in the cell should transmit PRACH (e.g., according to Table 7.3.1.1.1-1); otherwise, this field is reserved. Here, "SUL" refers to supplementary uplink, that is, where the UE is configured with two UL carriers for one DL carrier in the same cell.

[0133] • SS / PBCH Index - 6 bits. If the value of "Random Access Preamble Index" is not all zeros, then this field indicates the SS / PBCH used to determine the RACH timing and / or reference SignalPower for PRACH transmission; otherwise, this field is reserved.

[0134] • PRACH Mask Index - 4 bits. If the value of "Random Access Preamble Index" is not all zeros, then this field indicates the PRACH timing associated with the SS / PBCH indicated by the "SS / PBCH Index" used for PRACH transmission; otherwise, this field is reserved. Table 1 below shows an example of the mapping between the value of "PRACH Mask Index" and the allowed PRACH timing.

[0135] • Reserved bits - 12 bits are used for operation within the cell via shared spectrum channel access; otherwise, 10 bits.

[0136] Table 1: Examples of modified PRACH mask index values

[0137]

[0138] In the implementation scheme, when the UE transmits a PUCCH with a higher priority index or a PUCCH with HARQ-ACK information in the FD slot of the gNB, the UE may perform PUCCH repetition / expansion in the frequency domain if configured (or if dynamically indicated).

[0139] Figure 5User equipment device 500, according to embodiments of the present disclosure, is described as being usable for selecting uplink transmission parameters based on duplex mode. In various embodiments, user equipment device 500 is used to implement one or more of the solutions described above. User equipment device 500 may be an embodiment of remote unit 105 and / or UE 205 described above. Furthermore, user equipment device 500 may include processor 505, memory 510, input device 515, output device 520, and transceiver 525.

[0140] In some embodiments, the input device 515 and the output device 520 are combined into a single device, such as a touchscreen. In some embodiments, the user equipment device 500 may not include any input device 515 and / or output device 520. In various embodiments, the user equipment device 500 may include one or more of a processor 505, a memory 510, and a transceiver 525, and may not include input device 515 and / or output device 520.

[0141] As depicted, transceiver 525 includes at least one transmitter 530 and at least one receiver 535. In some embodiments, transceiver 525 communicates with one or more cells (or radio coverage areas) supported by one or more basic units 121. In various embodiments, transceiver 525 may operate on unlicensed spectrum. Furthermore, transceiver 525 may include multiple UE panels supporting one or more beams. Additionally, transceiver 525 may support at least one network interface 540 and / or application programming interface 545. Application programming interface 545 may support one or more APIs. Network interface 540 may support 3GPP reference points, such as Uu, N1, PC5, etc. Other network interfaces 540 may be supported, as will be understood by those skilled in the art.

[0142] In one embodiment, processor 505 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 505 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 505 executes instructions stored in memory 510 to perform the methods and routines described herein. Processor 505 is communicatively coupled to memory 510, input device 515, output device 520, and transceiver 525.

[0143] In various embodiments, processor 505 controls user equipment device 500 to perform the aforementioned UE behaviors. In some embodiments, processor 505 may include an application processor (also referred to as a "main processor") that manages application domains and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0144] In various embodiments, via transceiver 525, processor 505 receives configurations including: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. Transceiver 525 receives uplink resource allocations from a network entity (e.g., a gNB), and processor 505 determines a duplex mode corresponding to the uplink resource allocation, wherein the uplink resource allocation indicates uplink resources used for initial PUSCH transmission.

[0145] Processor 505 generates a TB corresponding to the uplink resource allocation, and transceiver 525 transmits the generated TB on the allocated uplink resources. If the PUSCH will be transmitted in a set of symbols indicated to operate in a first duplex mode, then processor 505 generates the TB using a first set of LCH constraint configurations. However, if the PUSCH will be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode, then processor 505 generates the TB using a second set of LCH constraint configurations.

[0146] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol in the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information. In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations.

[0147] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In such embodiments, transceiver 525 may further receive parameters indicating whether a particular LCH is allowed to be multiplexed in the TB when the network entity is operating in full-duplex mode. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration is operating in FD mode. In some embodiments, MAC CE multiplexing into the TB is not allowed when the PUSCH is to be transmitted in a set of symbols indicated to operate in the first duplex mode.

[0148] In some embodiments, receiving uplink resource allocation includes receiving the DCI that schedules PUSCH transmissions. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication of the duplex mode in the DCI. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication in the DCI of which set of LCH constraint configurations to use.

[0149] In some embodiments, the received configuration further includes a first power control parameter set and a second power control parameter set. In such embodiments, transmitting on allocated uplink resources to generate TB further includes: A) applying the first power control parameter set when the PUSCH will transmit in a set of symbols indicated to operate in the first duplex mode; and B) applying the second power control parameter set when the PUSCH will transmit in a set of symbols having at least one symbol indicated to operate in the second duplex mode.

[0150] In some embodiments, transmitting the generated TB on the allocated uplink resources includes applying a predetermined power offset when the PUSCH will be transmitted in a set of symbols predicted to operate in the first duplex mode.

[0151] In various embodiments, processor 505 identifies a set of symbols corresponding to a PRACH timing slot and detects overwrite slot format information for said set of symbols. Here, the overwrite slot format information (e.g., DCI with an SFI index field) indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). Processor 505 determines whether the set of symbols corresponds to a full-duplex slot and controls transceiver 525 to transmit a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during PRACH when the set of symbols corresponds to a full-duplex slot.

[0152] In some embodiments, transmitting the first RACH message includes applying an additional power offset when the set of symbols corresponds to a full-duplex time slot. In some embodiments, transceiver 525 further receives a configuration containing a first power ramp factor to be used when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to be used when the set of symbols corresponds to a non-full-duplex time slot. In such embodiments, transmitting the first RACH message includes applying the first power ramp factor.

[0153] In some embodiments, the first RACH message includes a MsgA for a two-step RACH procedure. In such embodiments, processor 505 further applies individually predetermined (i.e., predefined or preconfigured) MCS and α values ​​to the MsgA when the set of symbols corresponds to a full-duplex time slot. In some embodiments, transceiver 525 further receives a PDCCH command for a contention-free RACH procedure before transmitting the first RACH message, wherein the PDCCH command includes an indication of using a supplementary PRACH timing comprising at least one flexible symbol and / or downlink symbol.

[0154] In one embodiment, memory 510 is a computer-readable storage medium. In some embodiments, memory 510 includes volatile computer storage media. For example, memory 510 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 510 includes non-volatile computer storage media. For example, memory 510 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 510 includes both volatile and non-volatile computer storage media.

[0155] In some embodiments, memory 510 stores data related to uplink transmit parameters selected based on duplex mode. For example, memory 510 may store various parameters, panel / beam configurations, resource assignments, policies, and the like as described above. In some embodiments, memory 510 also stores program code and related data, such as an operating system or other controller algorithms operating on device 500.

[0156] In one embodiment, input device 515 may include any known computer input device, including a touchpad, button, keyboard, pen, microphone, or the like. In some embodiments, input device 515 may be integrated with output device 520 as, for example, a touchscreen or similar touch-sensitive display. In some embodiments, input device 515 includes a touchscreen that allows text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 515 includes two or more different devices, such as a keyboard and a touchpad.

[0157] In one embodiment, output device 520 may be designed to output visual, audible, and / or tactile signals. In some embodiments, output device 520 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 520 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 a similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, output device 520 may include a wearable display, such as a smartwatch, smart glasses, a head-mounted display, or the like, which is separate from but communicatively coupled to the remainder of user equipment device 500. Furthermore, output device 520 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, or the like.

[0158] In some embodiments, the output device 520 includes one or more speakers for generating sound. For example, the output device 520 may generate an audible alarm or notification (e.g., a beep or ring). In some embodiments, the output device 520 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 520 may be integrated with the input device 515. For example, the input device 515 and the output device 520 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 520 may be located near the input device 515.

[0159] Transceiver 525 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 525 operates under the control of processor 505 to transmit and receive messages, data, and other signals. For example, processor 505 may selectively activate transceiver 525 (or a portion thereof) at specific times to send and receive messages.

[0160] Transceiver 525 includes at least a transmitter 530 and at least one receiver 535. One or more transmitters 530 may be used to provide UL communication signals to base unit 121, such as the UL transmitter described herein. Similarly, one or more receivers 535 may be used to receive DL communication signals from base unit 121, as described herein. Although only one transmitter 530 and one receiver 535 are described, user equipment device 500 may have any suitable number of transmitters 530 and receivers 535. Furthermore, transmitters 530 and receivers 535 may be of any suitable type. In one embodiment, transceiver 525 includes a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile optical communication network via unlicensed radio spectrum.

[0161] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network via licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network via unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip that performs 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, some transceivers 525, transmitters 530, and receivers 535 may be physically separate components implemented to access shared hardware and / or software resources, such as (for example) a network interface 540.

[0162] In various embodiments, one or more transmitters 530 and / or one or more receivers 535 may be implemented and / or integrated as a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other types of hardware components. In some embodiments, one or more transmitters 530 and / or one or more receivers 535 may be implemented and / or integrated as a multi-chip module. In some embodiments, other components, such as network interface 540 or other hardware components / circuits, may be integrated with any number of transmitters 530 and / or receivers 535 as a single chip. In this embodiment, transmitters 530 and receivers 535 may be logically configured to use one or more common control signals as transceivers 525 or modular transmitters 530 and receivers 535 configured to be implemented in the same hardware chip or multi-chip module.

[0163] Figure 6A network device 600, which can be used to select uplink transmission parameters based on duplex mode according to embodiments of the present disclosure, is described. In one embodiment, the network device 600 may be an implementation of a RAN device, such as the basic unit 121 and / or RAN node 207 as described above. Furthermore, the network device 600 may include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625.

[0164] In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touchscreen. In some embodiments, the network device 600 may not include any input device 615 and / or output device 620. In various embodiments, the network device 600 may include one or more of a processor 605, a memory 610, and a transceiver 625, and may not include input device 615 and / or output device 620.

[0165] As depicted, transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, transceiver 625 communicates with one or more remote units 105. Additionally, transceiver 625 may support at least one network interface 640 and / or application programming interface 645. Application programming interface 645 may support one or more APIs. Network interface 640 may support 3GPP reference points, such as Uu, N1, N2, and N3. Other network interfaces 640 may be supported, as will be understood by those skilled in the art.

[0166] In one embodiment, processor 605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 605 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 605 executes instructions stored in memory 610 to perform the methods and routines described herein. Processor 605 is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625.

[0167] In various embodiments, network device 600 is a RAN node (e.g., gNB) communicating with one or more UEs, as described herein. In such embodiments, processor 605 controls network device 600 to perform the RAN behaviors described above. When operating as a RAN node, processor 505 may include an application processor (also referred to as a "main processor") that manages application domains and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0168] In various embodiments, via transceiver 625, processor 605 transmits a configuration comprising: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. Transceiver 625 transmits uplink resource allocations to the UE, the uplink resource allocations indicating uplink resources for initial PUSCH transmission. Transceiver 625 receives a TB from the UE on the allocated uplink resources, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols indicated for operation in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols having at least one symbol indicated for operation in a second duplex mode.

[0169] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol from the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information.

[0170] In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations. In some embodiments, MAC CE multiplexing to the TB is not allowed when the PUSCH is to transmit in a set of symbols indicated to operate in a first duplex mode.

[0171] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration operates in FD mode. In another embodiment, the third method includes a parameter indicating whether a specific LCH is allowed to be multiplexed in the TB when the network entity operates in full-duplex mode.

[0172] In some embodiments, transmitting uplink resource allocation includes transmitting a DCI that schedules PUSCH transmissions. In some embodiments, the third method may further include an indication of transmitting a duplex mode in the DCI. In some embodiments, the third method may further include an indication of which set of LCH constraint configurations to use in the DCI.

[0173] In some embodiments, the transmit configuration further includes: A) a first set of power control parameters to be used when the PUSCH is transmitted in a set of symbols indicated to operate in a first duplex mode; and B) a second set of power control parameters to be used when the PUSCH is transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode.

[0174] In various embodiments, via transceiver 625, processor 605 transmits overwrite slot format information for a set of symbols corresponding to a PRACH timing slot. Here, the overwrite slot format information (e.g., a DCI with an SFI index field) indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). Transceiver 625 receives a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during the PRACH timing when the set of symbols corresponds to a full-duplex slot.

[0175] In some embodiments, transceiver 625 further transmits a configuration to the UE, wherein the configuration includes a first power ramp factor to be used when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to be used when the set of symbols corresponds to a non-full-duplex time slot.

[0176] In some embodiments, the first RACH message includes MsgA of a two-step RACH procedure. In such embodiments, the processor 605 further configures (i.e., via transceiver 625) separately (i.e., predefined or preconfigured) MCS and α values ​​for MsgA when the set of symbols corresponds to a full-duplex time slot.

[0177] In some embodiments, transceiver 625 further transmits a PDCCH command to the UE for a contention-free RACH procedure, wherein the PDCCH command includes an indication of the timing of a supplementary PRACH procedure comprising at least one flexible symbol and / or a downlink symbol.

[0178] In one embodiment, memory 610 is a computer-readable storage medium. In some embodiments, memory 610 includes volatile computer storage media. For example, memory 610 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 610 includes non-volatile computer storage media. For example, memory 610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 610 includes both volatile and non-volatile computer storage media.

[0179] In some embodiments, memory 610 stores data related to uplink transmit parameters selected based on duplex mode. For example, memory 610 may store parameters, configurations, resource assignments, policies, and the like as described above. In some embodiments, memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on device 600.

[0180] In one embodiment, input device 615 may include any known computer input device, including a touchpad, button, keyboard, pen, microphone, or the like. In some embodiments, input device 615 may be integrated with output device 620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 615 includes a touchscreen, allowing text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 615 includes two or more different devices, such as a keyboard and a touchpad.

[0181] In one embodiment, output device 620 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 620 may include (but is not limited to) an LCD display, LED display, OLED display, projector, or similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, output device 620 may include a wearable display, such as a smartwatch, smart glasses, head-mounted display, or the like, which is separate from but communicatively coupled to the remainder of network device 600. Furthermore, output device 620 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, or the like.

[0182] In some embodiments, the output device 620 includes one or more speakers for generating sound. For example, the output device 620 may generate an audible alarm or notification (e.g., a beep or ring). In some embodiments, the output device 620 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 620 may be integrated with the input device 615. For example, the input device 615 and the output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 620 may be located near the input device 615.

[0183] Transceiver 625 includes at least a transmitter 630 and at least one receiver 635. One or more transmitters 630 can be used to communicate with a UE, as described herein. Similarly, one or more receivers 635 can be used to communicate with network functions in a Public Land Mobile Network (“PLMN”) and / or RAN, as described herein. Although only one transmitter 630 and one receiver 635 are described, network device 600 may have any suitable number of transmitters 630 and receivers 635. Furthermore, transmitters 630 and receivers 635 may be of any suitable type.

[0184] Figure 7 One embodiment of a method 700 for selecting uplink transmit parameters based on duplex mode, according to embodiments of the present disclosure, is described. In various embodiments, method 700 is performed by a UE device, such as remote unit 105, UE 205, and / or user equipment device 500 described above. In some embodiments, method 700 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0185] Method 700 begins and receives 705 a configuration, said configuration including: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. Method 700 includes receiving 710 an uplink resource allocation from a network entity (e.g., a gNB), said uplink resource allocation indicating uplink resources for an initial PUSCH transmission. Method 700 includes generating 715 a TB corresponding to the uplink resource allocation, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH will be transmitted in a set of symbols indicated to operate in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH will be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode. Method 700 includes transmitting 720 on allocated uplink resources to generate the TB. Method 700 ends.

[0186] Figure 8 One embodiment of a method 800 for selecting uplink transmit parameters based on duplex mode, according to embodiments of the present disclosure, is described. In various embodiments, method 800 is performed by a network entity, such as the basic unit 121, RAN node 207, and / or network device 600 described above. In some embodiments, method 800 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0187] Method 800 begins and transmits 805 a configuration, the configuration including: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. Method 800 includes transmitting 810 uplink resource allocation to the UE, the uplink resource allocation indicating uplink resources for initial PUSCH transmission. Method 800 includes receiving 815 TB from the UE on the allocated uplink resources, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols indicated for operation in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols having at least one symbol indicated for operation in a second duplex mode. Method 800 ends.

[0188] Figure 9 One embodiment of a method 900 for selecting uplink transmit parameters based on duplex mode, according to embodiments of the present disclosure, is described. In various embodiments, method 900 is performed by a UE device, such as remote unit 105, UE 205, and / or user equipment device 500 described above. In some embodiments, method 900 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0189] Method 900 begins and identifies 905 a set of symbols corresponding to a PRACH timing slot. Method 900 includes detecting 910 overwrite slot format information (e.g., a DCI with an SFI index) of the set of symbols, wherein the overwrite slot format information indicates that the set of symbols is not an uplink symbol (e.g., an SFI index field value indicating that the set of symbols is DL or flexible). Method 900 includes transmitting 915 a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during the PRACH timing when the set of symbols corresponds to a full-duplex slot. Method 900 ends.

[0190] Figure 10 One embodiment of a method 1000 for selecting uplink transmit parameters based on duplex mode, according to embodiments of the present disclosure, is described. In various embodiments, method 1000 is performed by a network entity, such as the basic unit 121, RAN node 207, and / or network device 600 described above. In some embodiments, method 1000 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0191] Method 1000 begins by transmitting overwrite slot format information for the set of symbols described in 1005, wherein the overwrite slot format information (e.g., a DCI with an SFI index field) indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). Method 1000 includes receiving a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) from the UE during a PRACH timing period when the set of symbols corresponds to a full-duplex slot. Method 1000 ends.

[0192] This document discloses a first device for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The first device may be implemented by a UE device, such as the remote unit 105, UE 205, and / or user equipment device 500 described above. The first device includes a processor, a transmitter, and a receiver. The receiver receives a configuration comprising: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. The receiver receives uplink resource allocations from a network entity (e.g., a gNB) and determines a duplex mode corresponding to the uplink resource allocation, wherein the uplink resource allocation indicates uplink resources used for initial PUSCH transmission.

[0193] The processor generates a TB corresponding to the uplink resource allocation, and the transmitter transmits the generated TB on the allocated uplink resources. When the PUSCH is to be transmitted in a set of symbols indicated to operate in a first duplex mode, the TB is generated based on the first set of LCH constraint configurations. When the PUSCH is to be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode, the TB is generated based on the second set of LCH constraint configurations.

[0194] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol in the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information. In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations.

[0195] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In such embodiments, the receiver may further receive parameters indicating whether a particular LCH is allowed to be multiplexed into the TB when the network entity is operating in full-duplex mode. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration is operating in FD mode. In some embodiments, MAC CE multiplexing into the TB is not allowed when the PUSCH is to be transmitted in a set of symbols indicated to operate in the first duplex mode.

[0196] In some embodiments, receiving uplink resource allocation includes receiving the DCI that schedules PUSCH transmissions. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication of the duplex mode in the DCI. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication in the DCI of which set of LCH constraint configurations to use.

[0197] In some embodiments, the received configuration further includes a first power control parameter set and a second power control parameter set. In such embodiments, transmitting on allocated uplink resources to generate TB further includes: A) applying the first power control parameter set when the PUSCH will transmit in a set of symbols indicated to operate in the first duplex mode; and B) applying the second power control parameter set when the PUSCH will transmit in a set of symbols having at least one symbol indicated to operate in the second duplex mode.

[0198] In some embodiments, transmitting the generated TB on the allocated uplink resources includes applying a predetermined power offset when the PUSCH will be transmitted in a set of symbols predicted to operate in the first duplex mode.

[0199] This document discloses a second device for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The second device may be implemented by a UE device, such as the remote unit 105, UE 205, and / or user equipment equipment 500 described above. The second device includes a transceiver and a processor that identifies a set of symbols corresponding to a PRACH timing slot and detects overwrite slot format information for the set of symbols. Here, the overwrite slot format information (e.g., a DCI with an SFI index field) indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). The processor determines whether the set of symbols corresponds to a full-duplex slot and controls the transceiver to transmit a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during the PRACH period when the set of symbols corresponds to a full-duplex slot.

[0200] In some embodiments, transmitting the first RACH message includes applying an additional power offset when the set of symbols corresponds to a full-duplex time slot. In some embodiments, the transceiver further receives a configuration containing a first power ramp factor to use when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to use when the set of symbols corresponds to a non-full-duplex time slot. In such embodiments, transmitting the first RACH message includes applying the first power ramp factor.

[0201] In some embodiments, the first RACH message includes a MsgA for a two-step RACH procedure. In such embodiments, the processor further applies individually predetermined (i.e., predefined or preconfigured) MCS and α values ​​to the MsgA when the set of symbols corresponds to a full-duplex time slot. In some embodiments, the transceiver further receives a PDCCH command for a contention-free RACH procedure before transmitting the first RACH message, wherein the PDCCH command includes an indication of using a supplementary PRACH timing comprising at least one flexible symbol and / or downlink symbol.

[0202] This document discloses a first method for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The first method can be performed by a UE device, such as the remote unit 105, UE 205, and / or user equipment device 500 described above. The first method includes receiving a configuration comprising: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differs from the first set of logical channel restriction configurations. The first method includes receiving an uplink resource allocation from a network entity (e.g., a gNB), wherein the uplink resource allocation indicates uplink resources for an initial PUSCH transmission. The method includes determining a duplex mode corresponding to the uplink resource allocation and generating a TB corresponding to the uplink resource allocation. The TB is generated based on the first set of LCH restriction configurations when the PUSCH is to be transmitted in a set of symbols indicated to operate in a first duplex mode. The TB is generated based on the second set of LCH restriction configurations when the PUSCH is to be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode. The first method includes transmitting the generated TB on allocated uplink resources.

[0203] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol in the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information. In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations.

[0204] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In such embodiments, the first method may further include receiving parameters indicating whether a particular LCH is allowed to be multiplexed in the TB when the network entity is operating in full-duplex mode. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration is operating in FD mode. In some embodiments, MAC CE multiplexing into the TB is not allowed when the PUSCH is to be transmitted in a set of symbols indicated to operate in the first duplex mode.

[0205] In some embodiments, receiving uplink resource allocation includes receiving the DCI that schedules PUSCH transmissions. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication of the duplex mode in the DCI. In some embodiments, determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication in the DCI of which set of LCH constraint configurations to use.

[0206] In some embodiments, the received configuration further includes a first power control parameter set and a second power control parameter set. In such embodiments, transmitting on allocated uplink resources to generate TB further includes: A) applying the first power control parameter set when the PUSCH will transmit in a set of symbols indicated to operate in the first duplex mode; and B) applying the second power control parameter set when the PUSCH will transmit in a set of symbols having at least one symbol indicated to operate in the second duplex mode.

[0207] In some embodiments, transmitting the generated TB on the allocated uplink resources includes applying a predetermined power offset when the PUSCH will be transmitted in a set of symbols predicted to operate in the first duplex mode.

[0208] This document discloses a second method for selecting uplink transmission parameters based on duplex mode, according to embodiments of the present disclosure. The second method can be performed by a UE device, such as the remote unit 105, UE 205, and / or user equipment equipment 500 described above. The second method includes identifying a set of symbols corresponding to a PRACH timing slot and detecting overwrite slot format information (e.g., a DCI with an SFI index field) of the set of symbols, wherein the overwrite slot format information indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). The second method includes determining whether the set of symbols corresponds to a full-duplex slot and transmitting a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during the PRACH when the set of symbols corresponds to a full-duplex slot.

[0209] In some embodiments, transmitting the first RACH message includes applying an additional power offset when the set of symbols corresponds to a full-duplex time slot. In some embodiments, the second method further includes a receiving configuration containing a first power ramp factor to use when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to use when the set of symbols corresponds to a non-full-duplex time slot. In such embodiments, transmitting the first RACH message includes applying the first power ramp factor.

[0210] In some embodiments, the first RACH message includes a MsgA for a two-step RACH procedure. In such embodiments, the second method further includes applying individually predetermined (i.e., predefined or preconfigured) MCS and α values ​​to the MsgA when the set of symbols corresponds to a full-duplex time slot. In some embodiments, the second method further includes receiving a PDCCH command for a contention-free RACH procedure before transmitting the first RACH message, wherein the PDCCH command includes an indication of using a supplementary PRACH timing comprising at least one flexible symbol and / or a downlink symbol.

[0211] This document discloses a third device for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The third device may be implemented by a network entity in a mobile communication network, such as the basic unit 121, RAN node 207, and / or network device 600 described above. The third device includes a processor, a transmitter, and a receiver. The transmitter is configured to transmit, the configuration including: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. The transmitter allocates uplink resources to the UE, the uplink resource allocation indicating uplink resources for initial PUSCH transmission. The receiver receives a TB from the UE on the allocated uplink resources, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols indicated for operation in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols having at least one symbol indicated for operation in a second duplex mode.

[0212] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol from the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information.

[0213] In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations. In some embodiments, MAC CE multiplexing to the TB is not allowed when the PUSCH is to transmit in a set of symbols indicated to operate in a first duplex mode.

[0214] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration operates in FD mode. In another embodiment, the third method includes a parameter indicating whether a specific LCH is allowed to be multiplexed in the TB when the network entity operates in full-duplex mode.

[0215] In some embodiments, transmitting uplink resource allocation includes transmitting a DCI that schedules PUSCH transmissions. In some embodiments, the third method may further include an indication of transmitting a duplex mode in the DCI. In some embodiments, the third method may further include an indication of which set of LCH constraint configurations to use in the DCI.

[0216] In some embodiments, the transmit configuration further includes: A) a first set of power control parameters to be used when the PUSCH is transmitted in a set of symbols indicated to operate in a first duplex mode; and B) a second set of power control parameters to be used when the PUSCH is transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode.

[0217] This document discloses a fourth device for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The fourth device may be implemented by a network entity in a mobile communication network, such as the basic unit 121, RAN node 207, and / or network device 600 described above. The fourth device includes a processor and a transceiver that transmits overwrite slot format information for a set of symbols corresponding to a PRACH timing slot. Here, the overwrite slot format information (e.g., a DCI with an SFI index field) indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). The fourth device includes a receiver that receives a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) during the PRACH timing when the set of symbols corresponds to a full-duplex timing slot.

[0218] In some embodiments, the transmitter further transmits a configuration to the UE, wherein the configuration includes a first power ramp factor to be used when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to be used when the set of symbols corresponds to a non-full-duplex time slot.

[0219] In some embodiments, the first RACH message includes MsgA of a two-step RACH procedure. In such embodiments, the processor further configures separately predetermined (i.e., predefined or pre-configured) MCS values ​​and α values ​​to the UE when the set of symbols corresponds to a full-duplex time slot for MsgA.

[0220] In some embodiments, the transmitter further transmits a PDCCH command to the UE for a contention-free RACH procedure, wherein the PDCCH command includes an indication of the timing of a supplementary PRACH procedure comprising at least one flexible symbol and / or a downlink symbol.

[0221] This document discloses a third method for selecting uplink transmission parameters based on duplex mode, according to embodiments of the present disclosure. The third method can be performed by network entities in a mobile communication network, such as the basic unit 121, RAN node 207, and / or network device 600 described above. The third method includes a transmission configuration comprising: A) a first set of LCH restriction configurations; and B) a second set of LCH restriction configurations, which differ from the first set of logical channel restriction configurations. The third method includes allocating uplink resources for transmission to the UE, the uplink resource allocation indicating uplink resources for initial PUSCH transmission. The third method includes receiving a TB from the UE on the allocated uplink resources, wherein the TB is generated based on the first set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols indicated for operation in a first duplex mode, and wherein the TB is generated based on the second set of LCH restriction configurations when the PUSCH is transmitted in a set of symbols having at least one symbol indicated for operation in a second duplex mode.

[0222] In some embodiments, the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode. In some embodiments, for the first duplex mode, at least one symbol from the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to time slot format information.

[0223] In some embodiments, the second set of LCH restriction configurations supports a higher level of QoS than the first set of LCH restriction configurations. In some embodiments, MAC CE multiplexing to the TB is not allowed when the PUSCH is to transmit in a set of symbols indicated to operate in a first duplex mode.

[0224] In some embodiments, the first set of LCH restriction configurations includes restrictions on multiplexed data for certain logical channels. In one embodiment, the UE is not allowed to multiplex URLLC data when the PUSCH duration operates in FD mode. In another embodiment, the third method includes a parameter indicating whether a specific LCH is allowed to be multiplexed in the TB when the network entity operates in full-duplex mode.

[0225] In some embodiments, transmitting uplink resource allocation includes transmitting a DCI that schedules PUSCH transmissions. In some embodiments, the third method may further include an indication of transmitting a duplex mode in the DCI. In some embodiments, the third method may further include an indication of which set of LCH constraint configurations to use in the DCI.

[0226] In some embodiments, the transmit configuration further includes: A) a first set of power control parameters to be used when the PUSCH is transmitted in a set of symbols indicated to operate in a first duplex mode; and B) a second set of power control parameters to be used when the PUSCH is transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode.

[0227] This document discloses a fourth method for selecting uplink transmission parameters based on duplex mode according to embodiments of the present disclosure. The fourth method can be performed by network entities in a mobile communication network, such as the basic unit 121, RAN node 207, and / or network device 600 described above. The fourth method includes transmitting overwrite slot format information (e.g., a DCI with an SFI index field) of the set of symbols, wherein the overwrite slot format information indicates that the set of symbols is not an uplink symbol (e.g., the SFI index field value indicates that the set of symbols is DL or flexible). The fourth method includes receiving a first RACH message (e.g., MsgA or Msg1 / PRACH preamble) from the UE during a PRACH timing when the set of symbols corresponds to a full-duplex slot.

[0228] In some embodiments, the fourth method further includes transmitting a configuration to the UE, wherein the configuration includes a first power ramp factor to be used when the set of symbols corresponds to a full-duplex time slot and a second power ramp factor to be used when the set of symbols corresponds to a non-full-duplex time slot.

[0229] In some embodiments, the first RACH message includes a MsgA for a two-step RACH procedure. In such embodiments, the fourth method further includes configuring separately predetermined (i.e., predefined or pre-configured) MCS values ​​and α values ​​to the UE for MsgA when the set of symbols corresponds to a full-duplex time slot.

[0230] In some embodiments, the fourth method further includes transmitting a PDCCH command to the UE for a contention-free RACH procedure, wherein the PDCCH command includes an indication of the timing of a supplementary PRACH procedure comprising at least one flexible symbol and / or a downlink symbol.

[0231] The embodiments may be practiced in other specific forms. The described embodiments should be considered illustrative rather than limiting in all respects. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims are included within their scope.

Claims

1. A method for a user equipment ("UE"), the method comprising: The configuration received includes the following items: The first group of logical channel ("LCH") restriction configuration, and The second set of LCH restriction configurations is different from the first set of logical channel restriction configurations. Receive uplink resource allocation from network entities, the uplink resource allocation indicating uplink resources for the initial physical uplink shared channel ("PUSCH") transmission; Generate a transport block ("TB") corresponding to the uplink resource allocation. Wherein, when the PUSCH will be transmitted in a set of symbols indicated for operation in a first duplex mode, the TB is generated based on the first set of LCH constraint configurations, and The TB is generated based on the second set of LCH constraint configurations when the PUSCH is to be transmitted in a set of symbols having at least one symbol indicated to operate in a second duplex mode; and The generated TB is transmitted on the allocated uplink resources.

2. The method according to claim 1, wherein the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode.

3. The method according to claim 2, further comprising: For the first duplex mode, at least one of the symbols in the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to the time slot format information.

4. The method of claim 2, wherein the second set of LCH restriction configurations supports a higher level of Quality of Service ("QoS") than the first set of LCH restriction configurations.

5. The method of claim 2, wherein the first set of LCH restriction configurations includes restrictions on multiplexed data of certain logical channels, the method further including a receive parameter indicating whether a particular LCH is allowed to be multiplexed in a TB when the network entity is operating in full-duplex mode.

6. The method of claim 2, wherein MAC CE multiplexing to the TB is not permitted when the PUSCH is to transmit in a set of symbols indicated to operate in a first duplex mode.

7. The method of claim 1, wherein receiving the uplink resource allocation includes receiving downlink control information ("DCI") that schedules the PUSCH transmission, wherein determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication of the duplex mode in the DCI.

8. The method of claim 1, wherein receiving the uplink resource allocation includes receiving downlink control information ("DCI") scheduling the PUSCH transmission, wherein determining the duplex mode corresponding to the uplink resource allocation includes receiving an indication in the DCI of which set of LCH constraint configurations to use.

9. The method of claim 1, wherein the received configuration further comprises a first power control parameter set and a second power control parameter set, wherein transmitting the generated TB on the allocated uplink resources comprises: When the PUSCH is to transmit in a set of symbols indicated to operate in the first duplex mode, the first power control parameter set is applied; and The second power control parameter set is applied when the PUSCH will transmit in a set of symbols having at least one symbol indicated to operate in the second duplex mode.

10. The method of claim 1, wherein transmitting the generated TB on the allocated uplink resources includes applying a predetermined power offset when the PUSCH will be transmitted in a set of symbols predicted to operate in the first duplex mode.

11. A user equipment ("UE") for wireless communication, comprising: At least one memory; as well as At least one processor coupled to the at least one memory and configured to cause the UE to: The configuration received includes the following items: The first group of logical channel ("LCH") restriction configuration, and The second set of LCH restriction configurations is different from the first set of LCH restriction configurations. Receive uplink resource allocation from network entities, the uplink resource allocation indicating uplink resources for transmission of the Physical Uplink Shared Channel ("PUSCH"); Generate a transport block ("TB") corresponding to the uplink resource allocation. Wherein, when the PUSCH transmission will be transmitted in a set of symbols associated with the first duplex mode, the TB is generated based on the first set of LCH constraint configurations, and Wherein, when the PUSCH transmission will be transmitted in a set of symbols having at least one symbol with the second duplex mode, the TB is generated based on the second set of LCH constraint configurations; and The generated TB is transmitted on the allocated uplink resources.

12. The UE according to claim 11, wherein the first duplex mode corresponds to a full-duplex mode, and the second duplex mode corresponds to a non-full-duplex mode.

13. The UE of claim 12, wherein the at least one processor is configured to enable the UE to receive time slot format information, and wherein, for the first duplex mode, at least one symbol of the set of symbols allocated in the uplink resource allocation is indicated as a downlink according to the time slot format information.

14. The UE of claim 12, wherein the second set of LCH restriction configurations supports a higher level of Quality of Service ("QoS") than the first set of LCH restriction configurations.

15. The UE of claim 12, wherein the first set of LCH restriction configurations includes restrictions on multiplexed data of certain LCHs, and wherein the at least one processor is configured to enable the UE to receive parameters indicating whether a particular LCH is allowed to be multiplexed in a corresponding TB when the network entity is operating in full-duplex mode.

16. The UE of claim 12, wherein the configuration indication prohibits the multiplexing of a Media Access Control ("MAC") control element ("CE") into the TB when transmitting the PUSCH in a set of symbols associated with a first duplex mode.

17. The UE of claim 11, wherein, in order to receive the uplink resource allocation, the at least one processor is configured to cause the UE to: receive downlink control information ("DCI") scheduling the transmission of the PUSCH, and an indication in the DCI based on a duplex mode, and determine the duplex mode corresponding to the uplink resource allocation.

18. The UE of claim 11, wherein, in order to receive the uplink resource allocation, the at least one processor is configured to cause the UE to: receive downlink control information ("DCI") scheduling the transmission of the PUSCH, and determine a duplex mode corresponding to the uplink resource allocation based on an indication in the DCI of which set of LCH restriction configurations to use.

19. The UE of claim 11, wherein the at least one processor is configured to cause the UE to receive the configuration, wherein a first power control parameter set and a second power control parameter group are provided, wherein in order to transmit the generated TB on the indicated uplink resource, the at least one processor is further configured to cause the UE to: When the PUSCH transmission is to be transmitted in a set of symbols associated with the first duplex mode, the first power control parameter set is applied; and The second power control parameter set is applied when the PUSCH transmission is to be transmitted in a set of symbols having at least one symbol associated with the second duplex mode.

20. The UE of claim 11, wherein, in order to transmit the generated TB on the indicated uplink resource, the at least one processor is configured to cause the UE to apply a predetermined power offset when the PUSCH transmission is to be transmitted in a set of symbols predicted to operate in the first duplex mode.

Images