Systems and methods for uplink resource muting on the physical uplink shared channel

Abstract

A wireless terminal of a communications system which comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a physical uplink shared channel, PUSCH, muting configuration message from a network node over a radio interface. The processor circuitry is configured to generate a physical uplink shared channel, PUSCH, whereby resource elements of the PUSCH are generated in accordance with the PUSCH muting configuration message.

Description

SYSTEMS AND METHODS FOR UPLINK RESOURCE MUTING ON THE PHYSICAL UPLINK SHARED CHANNEL

[0001] The technology relates to wireless communications, and particularly to muting of uplink resources in a wireless communications system.

[0002] A radio access network typically resides between wireless devices, such as user equipment (UEs), mobile phones, mobile stations, or any other device having wireless termination, and a core network. Example of radio access network types includes the GRAN, GSM radio access network; the GERAN, which includes EDGE packet radio services; UTRAN, the UMTS radio access network; E-UTRAN, which includes Long-Term Evolution; and NG-UTRAN, the New Radio (NR).

[0003] A radio access network may comprise one or more access nodes, such as base station nodes, which facilitate wireless communication or otherwise provides an interface between a wireless terminal and a communications system. A non-limiting example of a base station can include, depending on radio access technology type, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

[0004] The 3rd Generation Partnership Project (“3GPP”) is a group that, e.g., develops collaboration agreements such as 3GPP standards that aim to define globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents may describe certain aspects of radio access networks. Overall architecture for a fifth-generation system, e.g., the 5G System, also called “NR” or “New Radio”, as well as “NG” or “Next Generation”, is shown in Fig. 1, and is also described in 3GPP TS 38.300. The 5G NR network is comprised of NG RAN (Next Generation Radio Access Network) and 5GC (5G Core Network). As shown, NGRAN is comprised of gNBs (e.g., 5G Base stations) and ng-eNBs (i.e. LTE base stations). An Xn interface exists between gNB-gNB, between (gNB)-(ng-eNB) and between (ng-eNB)-(ng-eNB). The Xn is the network interface between NG-RAN nodes. Xn-U stands for Xn User Plane interface and Xn-C stands for Xn Control Plane interface. An NG interface exists between 5GC and the base stations (i.e. gNB & ng-eNB). A gNB node provides NR user plane and control plane protocol terminations towards the UE and is connected via the NG interface to the 5GC. The 5G NR (New Radio) gNB is connected to AMF (Access and Mobility Management Function) and UPF (User Plane Function) in 5GC (5G Core Network).

[0005] The Open Systems Interconnection, OSI, model is a reference framework that explains the process of transmitting data between computers. It is divided into seven layers that work together to carry out specialized network functions, allowing for a more systematic approach to networking. Information transferred from one device to another device travels through 7 layers of OSI model. First data travels down through 7 layers from the sender’s end and then climbs back 7 layers on the receiver’s end. Data flows through the OSI model in a step-by-step process: Layer 7: Application Layer: Applications create the data.

[0006] Layer 6: Presentation Layer: Data is formatted and encrypted.

[0007] Layer 5: Session Layer: Connections are established and managed.

[0008] Layer 4: Transport Layer: Data is broken into segments for reliable delivery.

[0009] Layer 3: Network Layer: Segments are packaged into packets and routed.

[0010] Layer 2: Data Link Layer: Packets are framed and sent to the next device.

[0011] Layer 1: Physical Layer: Frames are converted into bits and transmitted physically.

[0012] A protocol stack may comprise different individual protocols. Protocols may be simply described as set of rules that allow communication between peer entities or they can also be described as set of rules that facilitate horizontal communication. These protocols may be arranged in the layers such as those described above. In a transmitter side, a layer N receives data from layer N+1 and this data is called the SDU or Service Data Unit. This layer will modify the data and convert it into a PDU or a Protocol Data Unit. The peer entity in the receiver is only able to understand this PDU. In the receiver side, the peer entity receives the PDU from layer N-1, e.g., actually layer N-1 SDU, and converts it back into SDU(s) and passes it to layer N+1.

[0013] Radio Link Control (RLC) is a layer 2 Radio Link Protocol used in UMTS, LTE and 5G on the Air interface. This protocol is specified by 3GPP in TS 25.322 for UMTS, TS 36.322 for LTE and TS 38.322 for 5G New Radio (NR). RLC is located on top of the 3GPP MAC-layer and below the PDCP-layer. The main tasks of the RLC protocol are:

[0014] The Radio Resource Control (RRC) plays a role in managing the radio resources between the User Equipment (UE) and the 5G New Radio (NR) network. The major functions of the RRC protocol include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release and outer loop power control. By means of the signaling functions the RRC configures the user and control planes according to the network status and allows for Radio Resource Management strategies to be implemented.

[0015] The Medium Access Control layer plays a role in managing radio resources and ensuring efficient communication within networks. It operates just above the physical layer (PHY) and below the radio link control (RLC) and the packet data convergence protocol (PDCP) layers. The medium access control (MAC) is the layer that controls the hardware responsible for interaction with the wired or wireless transmission medium. The MAC sublayer and the logical link control(LLC) sublayer together make up the data link layer. The LLC provides flow control and multiplexing for the logical link, while the MAC provides flow control and multiplexing for the transmission medium. These two sublayers together correspond to layer 2 of the OSI model. Functions performed by the MAC layer include the following:

[0016] Thus, functions performed by the MAC layer include:

[0017] A RRC is in control of the MAC configuration. A MAC entity of a wireless terminal serves many functions, including handling the following transport channels:

[0018] The access stratum, AS, is a functional layer in protocol stacks between a radio network and user equipment. The access stratum is responsible, e.g., for transporting data over the wireless connection and managing radio resources.

[0019] Uplink (UL) resource muting has been discussed in the duplexing enhancement within RAN1 for enabling cross-link interference (CLI) measurements between network nodes, e.g., between gNB-to-gNB cross-link interference (CLI) measurements. In this process, the network node, gNB, intending to receive CLI measurement reference signal, RS, indicates to the UE to mute certain resource elements, REs, i.e., to transmit no signals on those REs, such that the REs are free of interference from the UEs and the gNB can perform CLI measurements on them. An alternative to UL resource muting would be for the gNB to avoid scheduling any UE transmissions on the reference signal (RS) symbols altogether. However, that would lead to resource underutilization as the rest of the REs on the unscheduled symbols would remain unused.

[0020] Fig. 2 illustrates an example of UL resource muting for gNB-to-gNB CLI measurement.

[0021] RAN1 has discussed UL resource muting on various UL signals and channels. One of the outstanding issues is how to perform UL resource muting on PUSCH repetition Type B. PUSCH repetition Type B involves the transmission of the same transport block, TB, multiple times to improve reliability. Some of the key aspects of PUSCH repetition Type B include the following:

[0022] Further to the topic of nominal and actual repetitions, nominal repetitions refer to the K repetitions indicated for a PUSCH transmission. The nominal repetitions are planned based on the configuration and scheduling information provided by the network. In contrast, actual repetitions refer to the effective transmissions that occur after accounting for various constraints and conditions that may affect the transmission of each nominal repetition. These constraints include invalid symbols, overlapping transmissions, and other scheduling conflicts. For example, suppose the UE is configured to perform 4 nominal repetitions of a TB. Due to overlapping with downlink transmissions and other invalid symbols, only 3 of the repetitions are actually transmitted. In this example case, the number of nominal repetitions (K) is 4, but the number of actual repetitions is 3.

[0023] When a Physical Uplink Shared Channel, PUSCH, repetition Type B transmission spans across a slot boundary, several considerations and procedures come into play to ensure proper handling of the transmission. Detailed acts and mechanisms involved may include the following:

[0024] Fig. 3 illustrates nominal and actual repetitions with PUSCH repetition Type B. In the first or top timeline of Fig. 3, 2 nominal repetitions are illustrated as configured on uplink (U) symbols. In the second or middle timeline of Fig. 3, the second nominal repetition is split into two separate actual repetitions due to occurrence of downlink (D) symbols in the middle. In the third or bottom timeline of Fig. 3, the second nominal repetition is split into two actual repetitions because of the occurrence of the slot boundary.

[0025] In comparison with the PUSCH repetition Type B which is illustrated by way of example in Fig. 3, with PUSCH repetition type A, the PUSCH is simply repeated on corresponding resources in separate slots, as illustrated in Fig. 4. PUSCH repetition type B. See, e.g., T.-K. Le, U. Salim, and F. Kaltenberger, “An overview of physical layer design for Ultra-Reliable Low-Latency Communications in 3GPP Releases 15, 16, and 17,” in IEEE Access, vol. 9, pp. 433-444, 2021.

[0026] Table 1 below includes text from TS 38.214 v18.4.0 Section 6.1.2.1.

[0027]

[0028] A document R1-2410790, 3GPP TSG-RAN WG1 Meeting #119, R1-2410790, Orlando, US, November 18th - 22nd, 2024xx, “Summary #3 of CLI handling”, summarizes contributions in RAN1#119 by various participants. Therein participants / companies discussed how to handle UL resource muting for PUSCH repetition and for multi-PUSCH scheduled by a single DCI. For PUSCH repetition type A, most companies proposed that UL resource muting should be applied for each repetition. In addition, some companies also support allowing UL resource muting on some PUSCH repetitions. This can be achieved in different ways depending on whether a periodicity can be configured for UL resource muting. For PUSCH repetition type B, for which the situation is a little different, some companies argued the muting symbols are configured / indicated on a slot basis, thus UE can apply UL resource muting in symbols overlapped with PUSCH repetitions within the slot. For multi-PUSCH scheduled by a single DCI, some companies proposed the UL muting symbols should be indicated separately for each PUSCH.

[0029] In a November 2024 RAN1 meeting, RAN1#119, the following was agreed for determining the time location (i.e., symbols) for UL resource muting on PUSCH:

[0030] One consequence of the above agreement is that the time location, e.g., symbols, for UL resource muting cannot be shifted. It can only be activated or deactivated with an ON / OFF signaling. Therefore, if the gNB needs to measure the CLI and cannot postpone it to the next CLI measurement opportunity, the only option is to keep the UL resource muting activated. As a result, the UL resource muting may inevitably occur on symbols indicated for a PUSCH repetition type B. Hence, UL resource muting on PUSCH repetition type B should be supported in contrast to an earlier proposal by few companies to avoid UL resource muting on PUSCH repetition type B altogether.

[0031] The following agreement was later reached for the simplest PUSCH repetition scenario, which is PUSCH repetition type A with SBFD Configuration 1:

[0032] The following is the definition of SBFD Configuration 1 and Configuration 2 from RAN1#117 (May 2024) agenda item 9.3.1:

[0033] An agreement from RAN1#118 (August 2024) states that “For the reference point of time location of UL resource muting for PUSCH, Option 1 is supported. Option 1: Starting symbol of a slot for both PUSCH mapping type A and type B”.

[0034] The foregoing agreement specifies a reference point, but it does not specify what signaling, e.g., what RRC configuration information element, IE, indicates the time location of UL resource muting with respect to this reference point.

[0035] What is needed are methods, apparatus, and / or techniques to address problems caused by or associated with cross-link interference on the uplink in a wireless network.

[0036] In a first of its example aspects the technology disclosed herein concerns a wireless terminal of a telecommunications system which comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a physical uplink shared channel, PUSCH, muting configuration message from a network node over a radio interface. The processor circuitry is configured to generate a physical uplink shared channel, PUSCH, whereby resource elements of the PUSCH are generated in accordance with the PUSCH muting configuration message. Methods of operating such wireless terminals are also provided.

[0037] In another example of its aspects the technology disclosed herein concerns a wireless terminal of a communications system which comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a configuration message, the configuration message being configured to indicate which resource element(s) of a physical uplink shared channel, PUSCH, should be muted. The processor circuitry is configured to determine valid symbols for inclusion in a repetition of the PUSCH in dependence upon whether a muting pattern implemented by the configuration message includes a resource element on the symbol. Methods of operating such wireless terminals are also provided.

[0038] In another example of its aspects the technology disclosed herein concerns a wireless terminal which comprise receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a configuration message, the configuration message being configured to indicate which resource element(s) of a physical uplink shared channel, PUSCH, should be muted in accordance with a muting pattern. The processor circuitry configured to determine whether to apply the muting pattern on a symbol based, at least in part, on whether an uplink signal can be transmitted on a PUSCH repetition that occurs, fully or partially, on the symbol on one or more resource element(s), RE(s), remaining for the PUSCH repetition transmission. Methods of operating such wireless terminals are also provided.

[0039] In another of its example aspects the technology disclosed herein concerns a network node of a communications system which comprises processor circuitry and transmitter circuitry. The processor circuitry is configured to generate a PUSCH muting configuration message. The transmitter circuitry is configured to transmit the PUSCH muting configuration message over a radio interface to a wireless terminal. Methods of operating such network nodes are also disclosed.

[0040] The foregoing and other objects, features, and advantages of the technology disclosed herein will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the technology disclosed herein.Fig. 1 is a diagrammatic view of overall architecture for a 5G New Radio system.Fig. 2 is a diagrammatic view illustrating an example of UL resource muting for gNB-to-gNB CLI measurement.Fig. 3 is a diagrammatic view illustrating example nominal and actual repetitions with PUSCH repetition Type B.Fig. 4 is a diagrammatic view illustrating example nominal and actual repetitions with PUSCH repetition Type A.Fig. 5A is a diagrammatic view of an exemplary embodiment and mode of a generic communications system wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5B is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5C is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5D is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5E is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5F is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5G is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5H is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 5H is a diagrammatic view of an exemplary embodiment and mode wherein a wireless terminal generates a physical uplink shared channel, PUSCH, which is subject to muting.Fig. 6A is a diagrammatic view illustrating basic, representative acts or steps of an example method performed by the example embodiment and mode of Fig. 5A.Fig. 6B is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5B.Fig. 6C is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5C.Fig. 6D is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5D.Fig. 6E is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5E.Fig. 6F is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5F.Fig. 6G is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5G.Fig. 6H is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5H.Fig. 6I is a diagrammatic view illustrating, e.g., other basic, representative acts or steps of the respective example embodiments and modes of Fig. 5I.Fig. 7 is a diagrammatic view showing an example format for a PUSCH Muting Activation MAC CE.Fig. 8 is a flowchart showing example acts and / or signals including signaling of CLI reference signal, RS, information among neighbor gNBs on a backhaul.Fig. 9 is a diagrammatic view showing example elements comprising electronic machinery which may comprise a wireless terminal, a radio access node, and a core network node according to an example embodiment and mode.

[0041] In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the technology disclosed herein. However, it will be apparent to those skilled in the art that the technology disclosed herein may be practiced in other embodiments that depart from these specific details. That is, those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the technology disclosed herein and are included within its spirit and scope. In some instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the technology disclosed herein with unnecessary detail. All statements herein reciting principles, aspects, and embodiments of the technology disclosed herein, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.

[0042] Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0043] As used herein, the term “telecommunication system” or “communications system” can refer to any network of devices used to transmit information. A non-limiting example of a telecommunication system is a cellular network or other wireless communication system. As used herein, the term “cellular network” or “cellular radio access network” can refer to a network distributed over cells, each cell served by at least one fixed-location transceiver, such as a base station. A “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (“IMTAdvanced”); IMT-2020, e.g., 5G; IMT-2030, e.g., 6G, etc. All or a subset of the cell may be adopted by 3GPP as licensed bands (e.g., frequency band) to be used for communication between a base station, such as a Node B, and a UE terminal. A cellular network using licensed frequency bands can include configured cells. Configured cells can include cells of which a UE terminal is aware and in which it is allowed by a base station to transmit or receive information. Examples of cellular radio access networks include E-UTRAN, and any successors thereof (e.g., NUTRAN).

[0044] A core network (CN) may comprise numerous servers, routers, and other equipment. As used herein, the term “core network” can refer to a device, group of devices, or sub-system in a telecommunication network that provides services to users of the telecommunications network. Examples of services provided by a core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc. A core network may communicate over a RAN-CN interface (e.g., N2 interface) with one or more radio access networks (RAN).

[0045] A radio access network (RAN) may communicate with one or more core networks. A radio access network (RAN) typically comprises plural access nodes. As used herein, the term “access node”, “node”, or “base station” can refer to any device or group of devices that facilitates wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, in the 3GPP specification, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

[0046] A radio access network (RAN) serves wireless terminals, which also form part of the radio access network (RAN). As used herein, the term “wireless terminal” can refer to any electronic device used to communicate voice and / or data via a communications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, tablets, netbooks, e-readers, wireless modems, etc.

[0047] A wireless terminal communicates with its serving radio access network (RAN) over a radio or air interface. Communication between radio access network (RAN) and wireless terminal over the radio interface occurs by utilization of “resources”. Any reference to a “resource” herein means “radio resource” unless otherwise clear from the context that another meaning is intended. In general, as used herein a radio resource (“resource”) is a time-frequency unit that can carry information across a radio interface, e.g., either signal information or data information.

[0048] Communication between the radio access network (RAN) 24 and wireless terminal over the radio interface 32 may occur on various layers. Layer 1 includes radio layer 1 or the physical layer. Higher layers, e.g., layers higher than Layer 1 may include radio layer 2 and radio resource control layer 3. The layer 1 communication may occur by utilization of “resources”. Reference to a “resource” herein means “radio resource” unless otherwise clear from the context that another meaning is intended. In general, as used herein a radio resource (“resource”) is a time-frequency unit that can carry information across a radio interface, e.g., either signal information or data information.

[0049] An example of a radio resource occurs in the context of a “frame” of information that is typically formatted and prepared, e.g., by a node. In Long Term Evolution (LTE) a frame, which may have both downlink portion(s) and uplink portion(s), is communicated between the base station and the wireless terminal. Each LTE frame may comprise plural subframes. For example, in the time domain, a 10 ms frame consists of ten one millisecond subframes. An LTE subframe is divided into two slots (so that there are thus 20 slots in a frame). The transmitted signal in each slot is described by a resource grid comprised of resource elements (RE). Each column of the two-dimensional grid represents a symbol (e.g., an OFDM symbol on downlink (DL) from node to wireless terminal; an SC-FDMA symbol in an uplink (UL) frame from wireless terminal to node). Each row of the grid represents a subcarrier. A resource element (RE) is the smallest time-frequency unit for downlink transmission in the subframe. That is, one symbol on one sub-carrier in the sub-frame comprises a resource element (RE) which is uniquely defined by an index pair (k,l) in a slot (where k and l are the indices in the frequency and time domain, respectively). In other words, one symbol on one sub-carrier is a resource element (RE). Each symbol comprises a number of sub-carriers in the frequency domain, depending on the channel bandwidth and configuration. The smallest time-frequency resource supported by the standard today is a set of plural subcarriers and plural symbols (e.g., plural resource elements (RE)) and is called a resource block (RB). A resource block may comprise, for example, 84 resource elements, i.e., 12 subcarriers and 7 symbols, in case of normal cyclic prefix In 5G New Radio (“NR”), a frame consists of 10 ms duration. A frame consists of 10 subframes with each having 1ms duration similar to LTE. Each subframe consists of 2μ slots. Each slot can have either 14 (normal CP) or 12 (extended CP) OFDM symbols. A slot is a typical unit for transmission used by scheduling mechanism. NR allows transmission to start at any OFDM symbol and to last only as many symbols as required for communication. This is known as "mini-slot" transmission. This facilitates very low latency for critical data communication as well as minimizes interference to other RF links. Mini-slots help to achieve lower latency in 5G NR architecture. Unlike slots, mini-slots are not tied to the frame structure. It helps in puncturing the existing frame without waiting to be scheduled. See, for example, https: / / www.rfwireless-world.com / 5G / 5G-NR-Mini-Slot.html, which is incorporated herein by reference.

[0050] In general, communication protocols between the wireless terminal and the telecommunication system may be categorized into Access Stratum (AS) and Non-Access Stratum (NAS). AS protocols, such as Radio Resource Control (RRC) and Medium Access Control (MAC), may be used for the wireless terminal to communicate with access nodes of a RAN, whereas NAS protocol(s), such as the NAS protocol specified in 3GPP TS 24.501, may be used for the wireless terminal to communicate with entities (e.g., AMF) of a CN(s), via access nodes of a RAN. Consequently, the wireless terminal may comprise a function to manage the AS protocols, and a separate function to manage the NAS protocol(s). Herein, terminology “NAS” may be used in some context to refer to the function built into the wireless terminal to manage the NAS protocol(s). Similarly, “RRC” may be used in some context to refer to the function built into the wireless terminal to manage the RRC protocol.

[0051] Logical channels reside between the RLC sublayer and the MAC sublayer which, as already mentioned, are layer 2 protocols in protocol stack. A Logical channel informs what kind of information is transferred. Logical channels can be broadly divided into two types: Control Channels (for the transfer of control plane information) and Traffic Channels (for the transfer of user plane information). A logical channel is eventually mapped to a physical channel.

[0052] The technology disclosed herein generally relates to physical uplink shared channels, including the muting of or on one or more resource element(s), REs, or symbols thereof. The technology disclosed herein encompasses plural example embodiments and modes as described below. The encompassed example embodiments and modes may be generically represented by the example communications system 20 of Fig. 5A and the example method acts illustrated in Fig. 6A.

[0053] Fig. 5A shows a communications system 20 comprising wireless terminal 22 and network node 24. The wireless terminal 22 may also be referred to herein as a “transmitter node” in the sense that the wireless terminal 22 transmits a PUSCH to the network node 24. Conversely, the network node 24 may also be referred to herein as a “receiver node” in the sense that the network node 24 receives the PUSCH from the transmitter node or wireless terminal 22. The network node 24 may be any suitable node, such as a node of a radio access network, or a node of a core network, for example.

[0054] The wireless terminal 22 comprises PUSCH generator 26; PUSCH muting controller 28; and interface 30, e.g., interface circuitry, for communication over radio or air interface 32 with receiver node 24. The network node 24 comprises PUSCH muting configuration message generator 34.

[0055] The wireless terminal 22 and network node 24 of Fig. 5A may operate in accordance with one or more of the example embodiments and modes of Section 1.0, Section 2.0, and Section 3.0 hereof. Further, the wireless terminal 22 and network node 24 of Fig. 5A may selectively switch between the various modes of Section 1.0, Section 2.0, and Section 3.0, and may combine one or more features from two or more of the various modes.

[0056] Fig. 6A shows example, generic, representative acts or steps that may be performed, in whole or in part, by the communications system 20 of Fig. 5A. Act 6-0 comprises the network node 24 generating a PUSCH muting configuration message, e.g., a muting parameter message, for muting a PUSCH. The PUSCH muting message may also be referred to as a PUSCH configuration message. Act 6-1 comprises the network node 24 transmitting the PUSCH muting configuration message over the air interface 32 for reception by the wireless terminal 22. Act 6-2 comprises the wireless terminal 22 generating a physical uplink shared channel, PUSCH, whereby resource elements of the PUSCH are generated in accordance with the muting parameter. Act 6-3 comprises the wireless terminal 22 transmitting the PUSCH, generated in accordance with the muting parameter, to the network node 24 over the air interface 32.

[0057] 1.0: SIGNALING MUTING ON / OFF INDICATION FOR PUSCH In the example embodiments and modes of Section 1.0, the wireless terminal 22 may apply a muting pattern according to a configuration or indication from the network, e.g., from network node 24. The example embodiments and modes of Section 1 may be applied to PUSCH with or without PUSCH repetition. The example embodiments and modes of Section 1.0 may be realized or implemented by a communications system 20 as shown in Fig. 5B.

[0058] Fig. 5B shows in more detail an exemplary communications system 20 suitable for implementation of the example embodiments and modes of Section 1.0 hereof. The communications system 20 of Fig. 5B is similar to the generic system of Fig. 5A but shows selected elements of wireless terminal 22 and network node 24 in more detail. The example units and functionalities illustrated in Fig. 5A - Fig. 5I and other example embodiments and modes hereof are not limiting, e.g., various units and functionalities may be omitted in some implementations and other units and functionalities not illustrated herein may be included.

[0059] Fig. 5B shows network node 24 as including network node processor circuitry which may comprise one or more network node processors 35, as well as network node transceiver circuitry 36, which may also be referred to as network node interface circuitry. As illustrated in Fig. 5B, the network node transceiver circuitry 36 may comprise a transmission and reception point (TRP). The transmission and reception point (TRP) 36 may further comprise transmitter circuitry and receiver circuitry. The network node processors 35 may comprise PUSCH muting message generator 34 as well as PUSCH message processor 38, which processes the PUSCH messages received from wireless terminal 22.

[0060] Fig. 5B also shows various example constituent components and functionalities of wireless terminal 22. For example, Fig. 5B shows wireless terminal 30 as comprising wireless terminal transceiver circuitry 50, which in turn may comprise transmitter circuitry 52 and receiver circuitry 54. The transmitter node transceiver circuitry 50 may include antenna(e) for the wireless transmission. Transmitter circuitry 52 may include, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. Receiver circuitry 54 may comprise, e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

[0061] Fig. 5B further shows wireless terminal 22 also comprising wireless terminal processor circuitry, e.g., one or more wireless terminal processor(s) 60. The wireless terminal 22, e.g., wireless terminal processor(s) 60, may comprise wireless terminal frame or message handler / generator 62. The wireless terminal 22 may also comprise user interfaces 66, including one or more user interfaces. Such user interfaces may serve for both user input and output operations, and may comprise (for example) a keyboard, a mouse, a screen such as a touch screen that can both display information to the user and receive information entered by the user. The user interface 66 may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

[0062] The wireless terminal 22 of Fig. 5B may also comprise one or more unillustrated data buffers or packet buffers into which packets destined for transmission over radio or air interface 32 from the wireless terminal 22 may be stored before pre-processing by the wireless terminal 22 and / or packets from network node 24 and received at the wireless terminal 22 may be stored after post processing by wireless terminal 22. Packets may be inbound packets to wireless terminal 22 from either one or more applications executed by wireless terminal processor(s) 60 or received from unillustrated other nodes to which the wireless terminal 22 may be connected.

[0063] The wireless terminal processor(s) 60 of Fig. 5B also comprise the PUSCH generator 26 and the PUSCH muting controller 28. Fig. 5B also shows in more detail various units or functionalities that may comprise wireless terminal 22, e.g., may comprise PUSCH muting controller 28. For example, terminal processor(s) 60, e.g., the PUSCH muting controller 28, may, in example implementations, comprise muting parameter analyzer 70 and selective muting controller 72.

[0064] The wireless terminal 22 of Fig. 5B and the network node 24 of Fig. 5B may perform the acts of Fig. 6A, and optionally additionally the acts of Fig. 6B as described below.

[0065] The example embodiment and mode of Section 1.0 hereof also encompasses a computer program product in which processor circuitry or the like, such as wireless terminal processor(s) 60, execute instructions stored on a non-transient memory to perform acts such as those described herein, including the acts of Fig. 6A - Fig. 6I.

[0066] 1.1: CONFIGURED GRANT (CG) PUSCH: MUTING PATTERN CONFIGURED BY RRC In an example embodiment and mode, a muting pattern associated with the CG PUSCH may be configured by the radio resource control, RRC, protocol. For example, the PUSCH muting message generator 34 of network node 24 may use RRC to generate and transmit a PUSCH muting message such as the message of act 6-1 of Fig. 6B. Further, the PUSCH muting controller 28 of wireless terminal 22 may, as act 6-2 of Fig. 6B, use the RRC PUSCH muting message for generating a muted PUSCH which may be transmitted as act 6-3 of Fig. 6A. For the generation of the RRC message Fig. 5B shows network node 24 as comprising network node RRC entity 42 and wireless terminal 22 as comprising wireless terminal RRC entity 68.

[0067] Listing 1 below shows an example ASN.1 code according to which the CG PUSCH configuration information element, IE, comprises the muting pattern parameter. In the example of Listing 1, the muting pattern is configured as a zero-power sounding reference signal, SRS (ZP-SRS).

[0068]

[0069] Upon receiving the configuration, the UE applies the muting pattern when transmitting the configured PUSCH.

[0070] 1.2: CONFIGURED GRANT (CG) PUSCH: MUTING PATTERN INDICATED BY L1 OR L2 SIGNAL In other example embodiments and modes of Section 1.0, , such as illustrated by way of example in Fig. 5C and Fig. 6C, a muting pattern for a CG PUSCH is indicated in the PUSCH muting configuration message, e.g., in the CG PUSCH configuration. However, the UE applies the muting pattern if it is activated by a dynamic signaling such as a DCI or a MAC CE message. Such activation signaling is used to control when the muting pattern is applied to the PUSCH and may also be referred to as muting status control message. To this end, Fig. 5C shows communications system 20C as being similar to the communications systems of the previous embodiments but further shows network node 24 as comprising muting status control message generator 44 and the wireless terminal 22 as comprising selective muting status controller 74 . Similarly, the method of Fig. 6C resembles the method of Fig. 6A but further includes acts pertaining to the generation, transmission, and use of a muting status control message 6C-1. For example, Fig. 6C shows acts which are additional to those of Fig. 6A, including act 6C-0 and act 6C-1. Act 6C-0 comprises the network node 24 generating the muting status control message; act 6C-1 comprises the network node 24 transmitting the muting status control message over radio or air interface 32 to network node 24. The acts of Fig. 6C including acts 6-0, 6-1, 6C-0, and 6C-1 may be performed in an order other than the order shown in Fig. 6C.

[0071] 1.2.1: L1 signaling In some example embodiments and modes, a bit / field in a downlink control information, DCI, format 0_0, 0_1, or the like indicates to the wireless terminal 22 that the muting pattern is activated (on). In such example embodiments and modes, the bit / field in the DCI comprises the muting status control message. In response, the wireless terminal 22 applies the muting pattern to the PUSCH until it receives another DCI message with the said bit / field that indicates that the muting pattern is deactivated (off). Then, in response, the UE does not apply the muting pattern to the PUSCH until it receives yet another DCI message with the said bit / field that indicates that the muting pattern is activated (on). For the example embodiments and modes in which the muting pattern is selectively activated to be on or off, the PUSCH muting controller 28 may comprise selective muting controller 72 which, e.g., monitors messages such as the muting status control 6C-1, e.g., DCI messages, and determines whether, based on the most recently received DCI message, the muting pattern is applied to the PUSCH. As mentioned above, the DCI messages whose reception indicates whether the muting pattern is applied to the PUSCH may also be referred to as muting status control message.

[0072] In the case of CG PUSCH Type 2, the bit / field may be comprised by a DCI message that activates or deactivates the transmission of the CG PUSCH, i.e., the DCI message may be scrambled with a configured scheduling radio network temporary identifier (CS-RNTI).

[0073] Yet another variation and / or example embodiment and mode of Section 1.0 is illustrated in Fig. 5D and Fig. 6D. In the example embodiment and mode of Fig. 5D and Fig. 6D, in order for the wireless terminal 22 to expect the bit / field in the DCI that activates or deactivates the muting pattern, an RRC IE may indicate that the muting pattern is to be activated or deactivated by a lower layer signaling such as a DCI. Such RRC IE or comparable indication may be referred to herein as a notification signal or notification message, e.g., a notification message to anticipate receipt of the muting status control message. Fig. 5D shows network node 24 as further comprising notification message generator 46 and wireless terminal 22 as comprising status notification controller 76. Fig. 6D shows acts in addition to those of Fig. 6C, including act 6D-0 and act 6D-1. Act 6D-0 comprises the network node 24, e.g., notification message generator 46, generating the notification message. Act 6D-1 comprises the network node 24 transmitting the notification message 6D-1 over the radio or air interface 32 to wireless terminal 22. Typically but not necessarily, the act 6-0, act 6-1, act 6D-0, and act 6D-1 occur in the order act 6-0, act 6-1, act 6D-0, and act 6D-1, e.g., the messages of the act 6-1 and act 6D-1 are sent after generation, as shown in Fig. 6D. But such order is not required, as in another example embodiment and mode the acts may occur in the order of act 6-0, act 6D-0, act 6-1, and act 6D-1. In yet another example embodiment and mode, the generation of the notification message as act 6D-0 and generation of the muting configuration message of act 6-0 may be combined, and therefore the transmissions of act 6-1 and 6D-1 may be in the same message. See, for example, the example information element ConfiguredGrantConfig in Listing 1 and Listing 2. The messages of acts 6D-0 and 6D-1 typically occur at a higher layer, e.g., RRC, similar to the messages of acts 6-0 and 6-1, which may be unlike the message of act 6C-1 which may occur at a lower layer, such as the physical layer or the medium access control (MAC) sub-layer of the link control layer.

[0074] Listing 2 shows an example ASN.1 code according to which a parameter in the CG PUSCH configuration IE indicates that a DCI bit / field is to be expected by the UE that activates or deactivates the muting pattern. The parameter may be configured with enabled, true, or the like.

[0075]

[0076] In another example embodiment and mode of Section 1.0., wireless terminal 22 may assume that the muting pattern is activated or deactivated initially or by default, e.g., before any DCI message with the said bit / field is received. Alternatively, the UE may be configured with an initial or default state of activated (on) or deactivated (off) for the muting pattern. For this example embodiment and mode Fig. 5E shows wireless terminal 22 as comprising default muting pattern memory 78. The muting pattern memory 78 is configured to sore the default muting pattern. In this context, the default value for the “status control message” before it is received, or if for any reason that the signaling is not valid anymore. Then the default or initial value of the status is indicated by the value “activated” or “deactivated” in the RRC IE The method of Fig. 6E shows such (pre)configuration by act 6E-1. The configuration of the default muting pattern by a configuration signal from network node 24 can be realized, for example, by allowing two values for the parameter that enables activation of the muting pattern, as shown in the example ASN.1 code of Listing 3. $

[0077] If wireless terminal 22 receives the RRC parameter, wireless terminal 22 expects the said bit / field in a DCI message to indicate activation or deactivation of the muting pattern, and takes the value activated or deactivated as an initial or default value. Otherwise, if the wireless terminal 22 does not receive the RRC parameter, the UE does not expect the said bit / field in a DCI message, and therefore, the wireless terminal 22 may assume that the muting pattern is activated on all occurrences of transmitting the CG PUSCH.

[0078] 1.2.2: L2 signaling In example embodiments and modes, illustrated by way of example in Fig. 5F and Fig. 6R, the PUSCH muting configuration message comprises a bit / field in a MAC CE message which indicates to the wireless terminal 22 that the muting pattern is activated (on) or deactivated (off). In this regard, Fig. 5F shows network node 24 as comprising medium access control, MAC, entity 48 which generates the MAC PUSCH muting configuration message as act 6F-0. Fig. 6F shows transmission of the PUSCH muting configuration message as a MAC CE by act 6F-1. In response, the wireless terminal 22 applies or does not apply, respectively, the muting pattern until it receives another MAC CE message with the said bit / field that deactivates or activates the muting pattern, respectively. Similar to the previous examples, a parameter in an RRC IE, for example the CG PUSCH configuration IE, may indicate enabling and potentially an initial or default value of activated or deactivated for applying the muting pattern. Listing 4 shows an example of selectively enabling muting on or off in accordance with the example embodiment and mode of Fig. 5F and Fig. 6F. A difference between the example embodiment and mode of Fig. 6E and the example embodiments and modes of Fig. 6F and Fig. 6G described hereinafter is that act 6C-0 and act 6C-1 in the example embodiment and mode of FIG 6E is in the physical layer (L1), but in example embodiments and modes of Fig. 6F and Fig. 6G it is in the MAC layer (L2).

[0079]

[0080] Fig. 7 shows an example format for the PUSCH Muting Activation MAC CE. In the example of Fig. 7, the one-bit field A is set to ‘1’ if PUSCH muting is activated, otherwise the field is set to ‘0’. Additionally, a field indicates the PUSCH configuration with which the MAC CE is associated. This field may indicate the parameter ConfiguredGrantConfigIndex-r16 in the ConfiguredGrantConfig IE. The field may take a value from 0 to 11, for example.

[0081] 1.3: TIMING SCHEME FOR ACTIVATING / DEACTIVATION MUTING PATTERN In some example embodiments and modes, the wireless terminal 22 additionally applies a timing scheme for activating or deactivating the muting pattern. For example, in an example embodiment and mode illustrated in Fig. 5G, wireless terminal 22 comprises muting duration controller 80. The muting duration controller 80 is configured to apply the timing scheme for activating or deactivating the muting pattern, as indicated by act 6G-2 of Fig. 6G.

[0082] In one example implementation of the communications system of Fig. 5G, the wireless terminal 22, e.g., muting duration controller 80, starts applying the muting pattern after a duration of T, e.g., T number of symbols, T number of slots, T number of milliseconds, etc. The wireless terminal 22 may require the duration of T to decode the L1 / L2 message comprising the bit / field that activates or deactivates the muting pattern.

[0083] In another example implementation of the communications system of Fig. 5G, an activation or deactivation of the muting pattern as indicated by an L1 / L2 signaling may remain valid for a duration of T, T number of symbols, T number of slots, T number of milliseconds, or a number N of the associated CG PUSCH occasions. This is useful when the network intends to indicate to the wireless terminal 22 to apply the muting temporarily for a limited number of times, for example 1 or 2 times, and does not expect the UE to apply the muting pattern indefinitely. This timing scheme can save resources that are otherwise wasted for muting and, at the same time, avoids the requirement from the network to send a separate L1 / L2 message for deactivating the muting after the 1 or 2 times. This behavior may be specified by the standard or configured by the network.

[0084] 1.4: DYNAMIC GRANT (DG) PUSCH: MUTING PATTERN Similar methods to those described above may be applied to the case of a dynamic grant, DG, PUSCH, except that the PUSCH is not configured by the radio resource control, RRC, but instead it is scheduled by a DCI format 0_0 or 0_1. Therefore, any RRC parameter that may indicate a muting pattern, enable activation of the muting pattern by L1 / L2 signaling, and / or indicate an initial / default value for activation or deactivation of the muting pattern is to be comprised by another RRC IE.

[0085] In an example embodiment and mode, a PUSCH-Config IE comprises an indication of a muting pattern, enabling activation by a lower layer (L1 / L2) signaling, and / or an initial / default value for activation or deactivation. Listing 5 shows an example ASN.1 code for this purpose.

[0086]

[0087] It should be noted that, in various realizations of at least some of the foregoing example embodiments and modes, the RRC parameter for enabling activation / deactivation of the muting pattern may further indicate to the wireless terminal 22 to expect the indication in one or multiple certain DCI formats, e.g., DCI format 0_0, 0_1, or the like. Listing 6 is an example ASN.1 code for this purpose.

[0088]

[0089] As an alternative, in a further example embodiment and mode, a PUSCH-ConfigCommon IE comprises one or multiple parameters that indicate a muting pattern and / or enables activation / deactivation of the muting pattern for all the UEs in a cell. The following is an example ASN.1 code for this purpose.

[0090]

[0091] The wireless terminal 22 may not expect to apply a muting pattern if it has not indicated to the network that it is capable of doing so. In that case, a wireless terminal 22 receiving a muting pattern indication for a cell may neglect the said parameters in the PUSCH-ConfigCommon IE.

[0092] 2.0: INVALIDATING SYMBOLS THAT CONTAIN MUTED RESOURCE ELEMENTS In some example embodiments and modes, the wireless terminal 22 may receive a first configuration of a UL resource muting pattern, as understood, for example, with reference to one or more of the foregoing example embodiments and modes. The first configuration may be expressed in a PUSCH muting configuration message, and may indicate a zero-power SRS (ZP-SRS), which is essentially an SRS configuration that does not comprise information of sequence generation, power control, beam / spatial information, and so on. The first configuration indicates which resource element(s), RE(s), that the wireless terminal 22 should mute, i.e., on which to transmit no signal, or equivalently, a zero-power signal. The reference point for the time location, expressed in symbols, of the UL resource muting REs may be indicated with reference to the starting symbol of a slot in which the REs are located.

[0093] In the example embodiments and modes of Section 2.0 hereof, the wireless terminal 22 UE additionally receives a second configuration of a PUSCH with repetition type B, which indicates that the PUSCH repetitions may occur on varying symbols in different slots, and / or there may be multiple repetitions of a PUSCH in a same slot. Such second configuration may be referred to herein as a PUSCH repetition configuration, and may be expressed in a PUSCH repetition configuration message. Each repetition indicated by the second configuration may be a nominal repetition, not an actual repetition. Then, according to standard specifications and / or other signaling, the wireless terminal 22 may determine actual repetitions based on the nominal repetitions. For example, the wireless terminal 22 may exclude symbols specified as invalid by the standard in order to determine the actual repetitions.

[0094] Fig. 5H shows an example communications system which is suitable for implementation of the example embodiments and modes of Section 2.0 hereof. In the example communications system of Fig. 5H, network node 24 further comprises PUSCH repetition configuration message generator 49 and wireless terminal 22 further comprises PUSCH repetition controller 82. Fig. 6H shows act 6H-0 as comprising the network node 24 generating the PUSCH repetition configuration message; act 6H-1 as comprising network node 24 transmitting the PUSCH repetition configuration message across the radio or air interface 32 to wireless terminal 22; act 6H-5 as comprising wireless terminal 22 generating the PUSCH repetition configuration message in accordance with the PUSCH repetition configuration message, and in a manner to include symbols that are determined to be valid; and, act 6H-6 as comprising the wireless terminal 22 transmitting the thusly generated PUSCH repetition to the network node 24 over the radio or air interface 32.

[0095] The wireless terminal 22 determines valid symbols for PUSCH repetition(s), e.g., for inclusion in the PUSCH repetition(s). Such determination may be included in act 6H-4 of Fig. 6H. For the example embodiments and modes of Section 2.0 hereof, when determining valid symbols for PUSCH repetitions, the wireless terminal 22 determines whether a symbol is valid based, at least in part, on whether the UL resource muting (pattern) includes REs on the symbol. In the example embodiments and modes of Section 2.0, the wireless terminal 22 further comprises symbol validity analyzer 84. The symbol validity analyzer 84 may be realized by the wireless terminal processor(s) 60 and may be conceptualized as comprising PUSCH muting controller 28 or PUSCH repetition controller 82.

[0096] In an example embodiment and mode, if REs from the UL resource muting pattern occur on a symbol configured for a PUSCH repetition, the symbol is considered invalid by the symbol validity analyzer 84.

[0097] In another example embodiment and mode, if REs from the UL resource muting pattern occur on a symbol configured for a PUSCH repetition, the symbol is considered invalid by symbol validity analyzer 84 if the UL resource muting pattern and / or REs on the symbol are activated. The activation may be performed by a lower layer signaling, e.g., a field in a DCI or a MAC CE, or by a higher layer signaling, .g., a field in an RRC IE.

[0098] In yet another example embodiment and mode, if REs from the UL resource muting pattern occur on a symbol configured for a PUSCH repetition, the symbol is considered invalid by symbol validity analyzer 84 if the UL resource muting pattern and / or REs on the symbol are activated, provided that the activation signaling, e.g., a DCI or a MAC CE indicating the activation, is received earlier than the first symbol of the PUSCH repetition by at least a minimum time threshold. In this case, if the activation signaling is received later than the minimum time threshold prior to the starting symbol of the PUSCH repetition, the wireless terminal 22 does not consider the activation information into account in order to determine whether the symbol is valid.

[0099] Alternatively, in other example embodiments and modes, the wireless terminal 22 may need to determine all the actual repetitions beforehand. In this case, the symbol is considered invalid by symbol validity analyzer 84 if the UL resource muting pattern and / or REs on the symbol are activated, provided that the activation signaling is received earlier than the first symbol of the first PUSCH for a transport block, TB, by at least a minimum time threshold.

[0100] In any of the foregoing embodiments, if an activation signaling is received later than the threshold, the wireless terminal 22 may neglect the signaling for the PUSCH repetition or for all the PUSCH repetitions of the TB. Alternatively, this may be an error case, i.e., the UE may not expect to receive the activation signaling later than the threshold. In this case, the wireless terminal 22 may handle the issue by implementation.

[0101] In yet other example embodiments and modes, the wireless terminal 2 may not consider a symbol invalid unconditionally if REs of an UL resource muting pattern, e.g., an active UL resource muting pattern, occurs on the symbol. Instead, the wireless terminal 22 may additionally consider the number of resources remaining for the PUSCH repetition that occurs, fully or partially, on the symbol. For example, if the wireless terminal 22 determines that, upon muting the REs of the UL resource muting pattern, the number of REs remaining for the PUSCH repetition falls below a minimum threshold, or the transmission rate of the UL signal on the PUSCH repetition exceeds a maximum threshold, then the symbol may be considered invalid by symbol validity analyzer 84.

[0102] The behavior of the wireless terminal 22 according to any or all the foregoing example embodiments and modes may be specified by the standard, configured or signaled by the network, or a combination thereof.

[0103] Table 2 is an example of how an example embodiment and mode may be implemented, for example how the example embodiment and mode may be implemented in the context of TS 38.213 Section 6.1.2.1, in which underlining particularly shows text pertinent to the example embodiment and mode.

[0104]

[0105] 3.0: DEPRIORITIZING MUTING BY THE UE For the example embodiments and modes of Section 3.0 hereof, in similar manner with the example embodiments and modes of Section 2.0, the wireless terminal 22 receives a first configuration of a UL resource muting pattern, which may be a ZP-SRS and a second configuration of a PUSCH with repetition type B. Then, according to standard specifications and / or other signaling, the UE may determine actual repetitions based on the nominal repetitions. In the example embodiments and modes of Section 3.0, the wireless terminal 22 may determine whether to apply the UL resource muting pattern on a symbol based, at least in part, on whether it is able to transmit the uplink signal on a PUSCH repetition that occurs, fully or partially, on the symbol on the remaining REs. In this case, the UE prioritizes PUSCH transmission over the UL resource muting.

[0106] The example embodiments and modes of Section 3.0 may be represented by the communications system of Fig. 5I and the method shown by Fig. 6I. In the communications system of Fig. 5I, wireless terminal 22 further comprises remaining resource element-contingent muting controller 90, e.g., remaining RE-contingent muting controller 90. In the method of Fig. 6I, the wireless terminal 22 performs act 6I-2. Act 6I-2 comprises the wireless terminal 22 generating a PUSCH repetition in which muting is based on sufficiency of remaining resource element(s). Act 6I-3 comprises wireless terminal 22 transmitting the PUSCH repetition over radio or air interface 32 to network node 24, with any muting of the PUSCH repetition being based on the sufficiency of remaining resource element(s) as determined at act 6I-2.

[0107] In an example implementation of the example embodiments and modes of Section 3.0, the wireless terminal 22, e.g., remaining RE-contingent muting controller 90, may determine whether the remaining RE(s), the resource elements remaining available for uplink transmission, are sufficient for a transmission on / of the PUSCH repetition. The PUSCH repetition may be actual or nominal. If the remaining REs fall below a minimum threshold, or the rate of the signal on the PUSCH repetition exceeds a maximum threshold, or if otherwise the UE determines that the remaining REs are not sufficient for the PUSCH repetition transmission, then the UE may not apply the UL resource muting.

[0108] In another example implementation of the example embodiments and modes of Section 3.0, upon determining that the remaining REs are not sufficient, the wireless terminal 22, e.g., remaining RE-contingent muting controller 90, may apply a partial UL resource muting such that the remaining REs are sufficient for the PUSCH repetition transmission.

[0109] In some example embodiments and modes, the wireless terminal 22 may indicate to the network, through an uplink signaling such as a UCI, a MAC CE, or an RRC IE, that it did not apply the UL resource muting, fully or partially. The signaling may comprise information of the symbols, REs, PUSCH repetitions, or the like, on which the UL resource muting was not applied fully or partially.

[0110] In some example embodiments and modes, any or all of the thresholds may be specified by the standard, configured or signaled by the network, determined by an implementation, or a combination thereof.

[0111] 4.0: EXAMPLE FLOWCHART Fig. 8 shows an example flowchart or example timeline that includes signaling of CLI reference signal, RS, information among neighbor gNBs on the backhaul.

[0112] FURTHER CONSIDERATIONS The outlined captions hereof are not technically limiting but only for textual organizational.

[0113] Terminology for the described messages herein, e.g., muting status control message, notification message, etc. does not imply that these messages or signals are whole new messages or signals, nor that the transmission that includes the message or signal is wholly devoted to the content of such message or signal as described herein. Rather, the names of the message(s) and signal(s) are applied only to indicate that those message(s) and / or signal(s) include the information germane for implementation of the respectively described example embodiment and mode. Many but not necessarily all of the proposed signals and messages may be realized as additional parameters in existing messages, e.g., in existing messages or existing information elements of messages already known in the communications art and / or described in existing industry standards. In many example embodiments and modes hereof more optional parameters are added to existing signals or messages, or added to existing information elements, IEs. Moreover, in some instances the words “message” and “signal” may be utilized interchangeably, but the skilled person will understand the proper appellation in view of the communications layer involved.

[0114] For the foregoing example embodiments and modes, units and functionalites of any example embodiment and mode which have the same reference numbers of other example embodiments and modes should be understood to be the same as structure and operation even if not discussed in the context of the example embodiment and mode, unless otherwise clear from the context.

[0115] As mentioned above, aspects of one or more of the various example embodiments and modes may be used in combination with one or more example embodiments and modes. For example, one or more of the example embodiments and modes of Fig. 5B / Fig. 6B through and including Fig. 5I / Fig. 6I may be used in combination with one or more of the example embodiments and modes of Fig. 5B / Fig. 6B through and including Fig. 5I / Fig. 6I. Moreover, while some of the illustrations for the various example embodiments and modes of Fig. 5B / Fig. 6B through and including Fig. 5I / Fig. 6I are shown as including structures, features, or acts of other example embodiments and modes, it should be understood that in some cases not all such structures, features, or acts of preceding and / or other example embodiments and modes need necessarily be included in order to accomplish the objectives of the discussed example embodiment and mode.

[0116] Each of the example embodiments and modes discussed herein, including the example embodiments and modes of Section 1.0, Section 2.0, and Section 3.0 hereof encompass a computer program product in which processor circuitry or the like, such as wireless terminal processor(s) 60 and network node processors 35, execute instructions stored on a non-transient memory to perform acts such as those above described, including the acts of one or more of Fig. 6A - Fig. 6I.

[0117] In terms of wireless communication, the wireless terminal 22 may be either a wireless terminal such as user equipment or mobile station, or a network node. Similarly and conversely, the network node 24 may be either a wireless terminal such as user equipment or mobile station, or a network node. It should be understood that herein “network” may be used interchangeably with “network node”. A network node may be either a core network node or a node of a radio access network, such as a RAN access node, e.g., a base station node, for example. The wireless terminal UE may be any electronic device used to communicate voice and / or data via a communications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, tablets, netbooks, e-readers, wireless modems, etc.be any A core network may comprise one or more core network nodes. A core network node may comprise or be realized by any suitable type of core network node entities, such as a core network management entity, e.g., an Access and Mobility Management Function (AMF). A core network and one or more of its constituent core network nodes is connected to at least one radio access network through a core-RAN interface circuit.

[0118] A radio access network in turn comprises one or more radio access network (RAN) nodes, such as a base station node. The base station node serves at least one cell. The radio access network, RAN, typically comprises plural access nodes. A base station node may have architecture such as split architecture comprising a central unit and one or more distributed units that comprise mobile termination (MT).

[0119] It should be understood that the various foregoing example embodiments and modes may be utilized in conjunction with one or more example embodiments and modes described herein. For example, the example embodiments and modes of all aspects of the technology disclosed herein, may be utilized in combination with one or more other example embodiments and modes disclosed herein.

[0120] Certain units and functionalities of the communications systems may be implemented by electronic machinery. For example, electronic machinery may refer to the processor circuitry described herein, such as network node processors 34 and wireless terminal processor(s) 60. Moreover, the term “processor circuitry” is not limited to mean one processor, but may include plural processors, with the plural processors operating at one or more sites, and with the at least one processor, e.g., plural processors, operating independently and / or concurrently. Moreover, as used herein the term “server” is not confined to one server unit but may encompass plural servers and / or other electronic equipment and may be co-located at one site or distributed to different sites. The following units and functionalities described herein may be implemented by machinery and processor circuitry:

[0121] The foregoing are not exhaustive lists as other units and functionalities may also be implemented by processor circuitry.

[0122] With these understandings, Fig. 9 shows an example of electronic machinery, e.g., processor circuitry, as comprising one or more processors 490, program instruction memory 492; other memory 494 (e.g., RAM, cache, etc.); input / output interfaces 496 and 497, peripheral interfaces 498; support circuits 499; and busses 500 for communication between the aforementioned units. The processor(s) 490 may comprise the processor circuitries described herein, for example, network node processors 34 and wireless terminal processor(s) 60.

[0123] A memory or register described herein may be depicted by memory 494, or any computer-readable medium, may be one or more of readily available memory such as random-access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature, as and such may comprise memory. The support circuits 499 are coupled to the processors 490 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input / output circuitry and subsystems, and the like.

[0124] The processes and methods of the disclosed embodiments may be implemented as a software routine. Alternatively or additionally, some or all of method steps that are disclosed therein may be performed in hardware as well as by a processor running software. As such, the embodiments may be implemented in software, as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware. The software routines of the disclosed embodiments are capable of being executed on any computer operating system and is capable of being performed using any CPU architecture.

[0125] The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller”, may be provided through the use of hardware such as circuit hardware and / or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and / or computer-implemented, and thus, machine-implemented.

[0126] In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) [ASIC], and / or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

[0127] In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term “processor” or “controller” may also be construed to refer to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.

[0128] Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, the technology disclosed herein may additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

[0129] The acts described herein may be performed by a software program product stored tangibly on a non-transient computer-readable medium which, when executed by one or more processors as herein mentioned, performs such acts either in whole or in part.

[0130] Moreover, each functional block or various features of the wireless terminal 22 and network node 24 employed in each of the aforementioned embodiments may be implemented or executed by circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

[0131] It will be appreciated that the technology disclosed herein is directed to solving radio communications-centric issues and is necessarily rooted in computer technology and overcomes problems specifically arising in radio communications. Moreover, the technology disclosed herein improves, e.g., interference in a communications system.

[0132] Although the description above contains many specificities, these should not be construed as limiting the scope of the technology disclosed herein but as merely providing illustrations of some of the presently preferred embodiments of the technology disclosed herein. Thus the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. Therefore, it will be appreciated that the scope of the technology disclosed herein fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the technology disclosed herein is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." The above-described embodiments could be combined with one another. All structural, chemical, and functional equivalents to the elements of the above-described preferred embodiment that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the technology disclosed herein, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims.

[0133] <Cross Reference> This patent application claims priority on US Provisional Application No. 63 / 755,064 filed on February 6, 2025, the entire contents of which are hereby incorporated by reference.

Claims

1. A wireless terminal of a communications system, the wireless terminal comprising: receiver circuitry configured to receive a physical uplink shared channel, PUSCH, muting configuration message from a network node over a radio interface; at least one processor, configured individually and / or collectively to generate a physical uplink shared channel, PUSCH, whereby resource elements of the PUSCH are generated in accordance with the PUSCH muting configuration message.

2. The wireless terminal of claim 1, wherein the PUSCH muting configuration message comprises a muting parameter, and wherein the muting parameter is included in a configured grant, CG, PUSCH configuration information element.

3. The wireless terminal of claim 1, wherein: the PUSCH muting configuration message comprises a muting parameter, the receiver circuitry is further configured to receive a muting status control message configured to indicate selective activation and deactivation of the muting parameter; and the at least one processor is further configured to selectively apply the muting parameter for generation of the PUSCH in dependence upon the muting status control message.

4. The wireless terminal of claim 3, wherein the muting status control message is included in at least one of a downlink control indicator, DCI, or a medium access control, MAC, control element, CE, message.

5. The wireless terminal of claim 3, wherein the receiver circuitry is further configured to receive a notification message; and wherein the at least one processor is further configured upon receipt of the notification message to anticipate receipt of the muting status control message.

6. The wireless terminal of claim 5, wherein the notification message is a layer 1 signal.

7. The wireless terminal of claim 3, wherein the muting parameter comprises a muting pattern, and wherein the at least one processor is configured: (1) for a default state, either to apply or not apply a muting pattern to the PUSCH; and (2) upon a next reception of the muting status control message to reverse act (1).

8. The wireless terminal of claim 1, wherein the receiver circuitry is further configured to receive a muting duration control signal configured to indicate a duration of activation of the muting parameter; and wherein the at least one processor is further configured to generate a physical uplink shared channel, PUSCH, whereby resource elements of the PUSCH are generated in accordance with the muting parameter for a duration indicated by the muting duration control signal.

9. A method of operating a node of a communications network, the method comprising: receiving a configuration of a PUSCH, the configuration comprising a first indication of an uplink resource muting pattern and a second indication that the muting pattern is activated or deactivated by a lower-layer message; receiving the lower-layer message comprising a field that indicates whether the muting pattern is activated; transmitting the PUSCH while applying the muting pattern upon determining that the muting pattern is activated or transmitting the PUSCH while not applying the muting pattern upon determining that the muting pattern is deactivated.

10. A network node of a communications system, the node comprising: at least one processor, configured individually and / or collectively to generate a PUSCH muting configuration message; transmitter circuitry configured to transmit the PUSCH muting configuration message over a radio interface to a wireless terminal.

11. The network node of claim 10, wherein the PUSCH muting configuration message comprises a muting parameter, and wherein the muting parameter is included in a configured grant, CG, PUSCH configuration information element.

12. The network node of claim 10, wherein the at least one processor is further configured to generate a muting status control message configured to indicate selective activation and deactivation of the muting parameter.

13. The network node of claim 12, wherein the at least one processor is further configured to generate a notification message configured to alter the wireless terminal to anticipate receipt of the muting status control message.

14. The network node of claim 10, wherein the at least one processor is further configured to generate a default state signal which is configured to indicate to the wireless terminal whether a default state is to apply or not apply the muting patterns to the PUSCH.

15. The network node of claim 10, wherein the at least one processor is further configured to generate a muting duration control signal configured to indicate to the wireless terminal a duration of activation of the PUSCH muting configuration.

Images