Patent Application
20240406794
The present disclosure relates generally to wireless communications and, in particular embodiments, to reporting amounts of uplink physical layer information that is to be transmitted from a user equipment (UE) to a network device in a wireless communication network.
In long term evolution (LTE) and new radio (NR), a buffer status reporting procedure is used to provide a serving base station with information about uplink (UL) data volume in a medium access control (MAC) entity. A buffer status report (BSR) is a kind of MAC control element (MAC-CE) from UE to network, carrying information on how much data is in a UE buffer to be sent out.
Current buffer status reporting procedure is for data transmission to high layers above layer 1 (L1) and reported data volume to transmit is based on how much data is in radio link control (RLC) and packet data convergence protocol (PDCP) layers.
Reporting of buffer size or amount of physical layer information to be transmitted remains an issue.
In sixth generation (6G) wireless communication networks, it is expected that more UL layer 1 (L1) data will be involved in real-time intelligent operation in physical layer (PHY), and payload size of UL L1 data may be flexible and determined at least in part by UEs.
According to an aspect of the present disclosure, a method involves transmitting, by a UE to a network device in a wireless communication network, signaling indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. The physical layer information includes control information, data information, or both control information and data information in the physical layer.
A UE according to another aspect of the present disclosure includes a processor and a non-transitory computer readable storage medium that is coupled to the processor. The non-transitory computer readable storage medium stores programming for execution by the processor. The programming includes instructions to, or to cause the processor to, transmit signaling to a network device in a wireless communication network. The signaling is indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. The physical layer information includes control information, data information, or both control information and data information in the physical layer.
A computer program product includes a non-transitory computer readable medium storing programming, and the programming includes instructions to, or to cause a processor to, transmit signaling from a UE to a network device in a wireless communication network. The signaling is indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device, and the physical layer information includes control information, data information, or both control information and data information in the physical layer.
A method according to yet another aspect of the present disclosure involves receiving, by a network device from a UE in a wireless communication network, signaling indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. As in other embodiments, the physical layer information includes control information, data information, or both control information and data information in the physical layer.
In another embodiment in which a network device includes a processor and a non-transitory computer readable storage medium that is coupled to the processor and stores programming for execution by the processor, the programming may include instructions to, or to cause a processor to, receiving signaling from a UE in a wireless communication network. The signaling is indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device, and the physical layer information includes control information, data information, or both control information and data information in the physical layer.
Programming stored in a non-transitory computer readable medium of a computer program product may include instructions to, or to cause a processor to, receive by a network device from a UE in a wireless communication network, signaling indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. The physical layer information includes control information, data information, or both control information and data information in the physical layer.
The present disclosure encompasses these and other aspects or embodiments.
For a more complete understanding of the present embodiments, and the advantages thereof, reference is now made, by way of example, to the following descriptions taken in conjunction with the accompanying drawings.
For illustrative purposes, specific example embodiments will now be explained in greater detail in conjunction with the figures.
The embodiments set forth herein represent information sufficient to practice the claimed subject matter and illustrate ways of practicing such subject matter. Upon reading the following description in light of the accompanying figures, those of skill in the art will understand the concepts of the claimed subject matter and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
Referring to
The terrestrial communication system and the non-terrestrial communication system could be considered sub-systems of the communication system. In the example shown in
Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding. In some examples, the ED 110a may communicate an uplink and/or downlink transmission over a terrestrial air interface 190a with T-TRP 170a. In some examples, the EDs 110a, 110b, 110c and 110d may also communicate directly with one another via one or more sidelink air interfaces 190b. In some examples, the ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172. The air interfaces 190a and 190b may use similar communication technology,
such as any suitable radio access technology. For example, the communication system 100 may implement one or more channel access methods, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA) in the air interfaces 190a and 190b. The air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.
The non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 175 for multicast transmission.
The RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a, 110b, 110c with various services such as voice, data and other services. The RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown), which may or may not be directly served by core network 130 and may, or may not, employ the same radio access technology as RAN 120a, RAN 120b or both. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or the EDs 110a, 110b, 110c or both, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160). In addition, some or all of the EDs 110a, 110b, 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto), the EDs 110a, 110b, 110c may communicate via wired communication channels to a service provider or switch (not shown) and to the Internet 150. The PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and subnets (intranets) or both and incorporate protocols, such as Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP). The EDs 110a, 110b, 110c may be multimode devices capable of operation according to multiple radio access technologies and may incorporate multiple transceivers necessary to support such.
Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to) as a user equipment/device (UE), a wireless transmit/receive unit (WTRU), a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA), a machine type communication (MTC) device, a personal digital assistant (PDA), a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, an industrial device, or apparatus (e.g., communication module, modem, or chip) in the forgoing devices, among other possibilities. Future generation EDs 110 may be referred to using other terms. The base stations 170a and 170b each T-TRPs and will, hereafter, be referred to as T-TRP 170. Also shown in
The ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated. One, some, or all of the antennas 204 may, alternatively, be panels. The transmitter 201 and the receiver 203 may be integrated, e.g., as a transceiver. The transceiver is configured to modulate data or other content for transmission by the at least one antenna 204 or by a network interface controller (NIC). The transceiver may also be configured to demodulate data or other content received by the at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or by wire. Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals.
The ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit(s) (e.g., a processor 210). Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache and the like.
The ED 110 may further include one or more input/output devices (not shown) or interfaces (such as a wired interface to the Internet 150 in
The ED 110 includes the processor 210 for performing operations including those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170, those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170, and those operations related to processing sidelink transmission to and from another ED 110. Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols. Depending upon the embodiment, a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g., by detecting and/or decoding the signaling). An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170. In some embodiments, the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g., beam angle information (BAI), received from the T-TRP 170. In some embodiments, the processor 210 may perform operations relating to network access (e.g., initial access) and/or downlink synchronization, such as operations relating to detecting a synchronization sequence, decoding and obtaining the system information, etc. In some embodiments, the processor 210 may perform channel estimation, e.g., using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.
Although not illustrated, the processor 210 may form part of the transmitter 201 and/or part of the receiver 203. Although not illustrated, the memory 208 may form part of the processor 210.
The processor 210, the processing components of the transmitter 201 and the processing components of the receiver 203 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory (e.g., the in memory 208). Alternatively, some or all of the processor 210, the processing components of the transmitter 201 and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmed field-programmable gate array (FPGA), a graphical processing unit (GPU), or an application-specific integrated circuit (ASIC).
The T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS), a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB), a Home eNodeB, a next Generation NodeB (gNB), a transmission point (TP), a site controller, an access point (AP), a wireless router, a relay station, a remote radio head, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU), a remote radio unit (RRU), an active antenna unit (AAU), a remote radio head (RRH), a central unit (CU), a distribute unit (DU), a positioning node, among other possibilities. The T-TRP 170 may be a macro BS, a pico BS, a relay node, a donor node, or the like, or combinations thereof. The T-TRP 170 may refer to the forgoing devices or refer to apparatus (e.g., a communication module, a modem or a chip) in the forgoing devices.
In some embodiments, the parts of the T-TRP 170 may be distributed. For example, some of the modules of the T-TRP 170 may be located remote from the equipment that houses antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling), message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses antennas 256 of the T-TRP 170. The modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g., through the use of coordinated multipoint transmissions.
The T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated. One, some, or all of the antennas 256 may, alternatively, be panels. The transmitter 252 and the receiver 254 may be integrated as a transceiver. The T-TRP 170 further includes a processor 260 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110; processing an uplink transmission received from the ED 110; preparing a transmission for backhaul transmission to the NT-TRP 172; and processing a transmission received over backhaul from the NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g., multiple input multiple output (MIMO) precoding), transmit beamforming and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols and decoding received symbols. The processor 260 may also perform operations relating to network access (e.g., initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs), generating the system information, etc. In some embodiments, the processor 260 also generates an indication of beam direction, e.g., BAI, which may be scheduled for transmission by a scheduler 253. The processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc. In some embodiments, the processor 260 may generate signaling, e.g., to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is sent by the transmitter 252. Note that “signaling,” as used herein, may alternatively be called control signaling. Dynamic signaling may be transmitted in a control channel, e.g., a physical downlink control channel (PDCCH) and static, or semi-static, higher layer signaling may be included in a packet transmitted in a data channel, e.g., in a physical downlink shared channel (PDSCH).
The scheduler 253 may be coupled to the processor 260. The scheduler 253 may be included within, or operated separately from, the T-TRP 170. The scheduler 253 may schedule uplink, downlink and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (“configured grant”) resources. The T-TRP 170 further includes a memory 258 for storing information and data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.
Although not illustrated, the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.
The processor 260, the scheduler 253, the processing components of the transmitter 252 and the processing components of the receiver 254 may each be implemented by the same, or different one of, one or more processors that are configured to execute instructions stored in a memory, e.g., in the memory 258. Alternatively, some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252 and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a FPGA, a GPU or an ASIC.
Notably, the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and the receiver 274 may be integrated as a transceiver. The NT-TRP 172 further includes a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110; processing an uplink transmission received from the ED 110; preparing a transmission for backhaul transmission to T-TRP 170; and processing a transmission received over backhaul from the T-TRP 170. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g., MIMO precoding), transmit beamforming and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received signals and decoding received symbols. In some embodiments, the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g., BAI) received from the T-TRP 170. In some embodiments, the processor 276 may generate signaling, e.g., to configure one or more parameters of the ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.
The NT-TRP 172 further includes a memory 278 for storing information and data. Although not illustrated, the processor 276 may form part of the transmitter 272 and/or part of the receiver 274. Although not illustrated, the memory 278 may form part of the processor 276.
The processor 276, the processing components of the transmitter 272 and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g., in the memory 278. Alternatively, some or all of the processor 276, the processing components of the transmitter 272 and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a GPU or an ASIC. In some embodiments, the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g., through coordinated multipoint transmissions.
The T-TRP 170, the NT-TRP 172, and/or the ED 110 may include other components, but these have been omitted for the sake of clarity.
One or more steps of the embodiment methods provided herein may be performed by corresponding units or modules, according to
Additional details regarding the EDs 110, the T-TRP 170 and the NT-TRP 172 are known to those of skill in the art. As such, these details are omitted here.
Embodiments disclosed herein encompass UE reporting related to physical layer information. Such reporting involves a UE reporting, to a network device such as a base station, the amount of UL physical layer information that is to be transmitted from the UE to the network device. Physical layer information may also or instead be referred to as physical layer (PHY) data, assistant PHY information or data, or L1 information or data, and may be or include either or both of control signaling or information and data traffic or information. Another way to describe or characterize physical layer information is that it has no associated logical channel.
In 6G, it is expected that features such as real-time intelligent operation in PHY may involve more UL physical layer information being transmitted from UEs to network devices. For example, physical layer information may include information that is related to artificial intelligence (AI) model performance and is transmitted during AI implementation. AI or machine learning (AI/ML) accuracy, AI/ML loss value such as mean square error and/or mean absolute error, gradients, block error rate (BLER), bit error rate (BER), throughput, and latency are examples of physical layer information, any one or more of which may be transmitted during AI implementation.
Physical layer information may also or instead include assistant information for AI training or re-training/update, such as any one or more of: correlation between a base station model or other network-side model and a UE local model, and gradients.
Sensing data is another example of physical layer information, and may include data related to doppler or rate of fading, such as any one or more of: level cross level cross rate (LCR), average fading duration (AFD), delay of multipath, average delay, and delay spread.
Physical layer information and reporting may be dynamic in that a UE may have different physical layer information to report in different time slots, for example, and there may be no need to report on physical layer information repeatedly if there has been no change. A UE may self-determine UL physical layer information reporting to a network device. It may therefore be desirable to provide for physical layer information reporting that enables a network device such as a base station to be informed that UL data to be transmitted by a UE is UL physical layer information, and the amount of physical layer information that is to be transmitted.
According to an embodiment, a MAC-CE includes an L1 BSR that indicates that the BSR is for UL physical layer information, and the buffer size. In the UL physical layer information that is subsequently transmitted by a UE, the UE may report whether each of multiple types of physical layer information is present, and the value of that physical layer information if it is present.
Another embodiment also involves a MAC-CE that includes an L1 BSR and reported physical layer information types. Such a MAC-CE indicates the buffer size of physical layer information, and physical layer information types reported by the UE.
In a further embodiment, there is no explicit BSR, and a network device such as a base station configures a mapping between a scheduling request (SR) resource and physical layer information buffer size. An SR may thereby be dedicated to UL physical layer information, and based on the SR resource that is used by a UE, a network device is able to determine the physical layer information buffer size.
These and other embodiments disclosed herein may be generalized, in method form for example, as involving transmitting, by a UE to a network device in a wireless communication network, signaling that is indicative of an amount of uplink physical layer information that is to be transmitted from the UE to the network device. The physical layer information may be or include control information, data information, or both control information and data information in the physical layer. Further, the signaling comprises a medium access control-control element (MAC-CE) or uplink physical signaling in physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH).
In some embodiments, either or both of the type and the amount of physical layer information that is available at the UE for transmission may be determined by the UE. Other embodiments may involve physical layer information type(s) and/or amount(s) being jointly determined by a network device and a UE. For example, a network device such as a base station may configure available types of physical layer information, and a UE may select one or multiple types to report to the network device.
Signaling that is indicative of an amount of uplink physical layer information to be transmitted from a UE to a network device may be or include a BSR indicating the amount of uplink physical layer information. The BSR may be, or be part of, a MAC-CE for example. An identifier such as a logical channel identifier (LCID) value in a MAC subheader may be included in the signaling to identify a type of the MAC-CE as a BSR MAC-CE for the uplink physical layer information or indicate that the BSR is for UL physical layer information.
In terms of data structure, a MAC-CE of “BSR for UL L1 data” includes L1 buffer size only, and no LCG ID because the buffer size is for physical layer information. Physical layer information is not for logical channels and has no associated logical channel.
A MAC-CE for physical layer information reporting, such as a “BSR for UL L1 data”, may have a higher priority than other MAC-CEs for MAC multiplexing in some embodiments. In MAC layer, to support priority handing, multiple logical channels and MAC-CEs can be multiplexed into one transport channel, within a MAC protocol data unit (PDU), and a “BSR for UL L1 data” MAC-CE or other MAC-CE for physical layer information reporting may be the first MAC-CE(s) to be included into a MAC PDU by a UE.
By receiving a MAC-CE that is used for physical layer information reporting, a network device such as a base station knows that the UE will report physical layer information. The network device may allocate UL communication resources to the UE to transmit the physical layer information. The resource allocation, such as the number of allocated resources, is based on the reported amount of physical layer information, such as physical layer information buffer size. The UL resources may include one or more of time resources, frequency resources, and spatial resources of one or more UL data channels such as physical uplink shared channel (PUSCH) and/or one or more control channels such as physical uplink control channel (PUCCH).
The data format of UL physical layer information is configured by the network device in some embodiments. For example, a base station may configure one or more fields for physical layer information. For a type of physical layer information, to be carried in one field for example, a UE may transmit to the network device an indication as to whether that type of physical layer information is present in the physical layer information to be transmitted, and if present, a value of that type of physical layer information.
As an example, physical layer information may include any one or more of the following types in some embodiments, with a 1-bit indication of presence for each type and a value of the physical layer information of each type if present:
These are examples only, and different indicators of presence and/or value may be used in other embodiments. For example, different types may have different presence indications, and/or the same or different lengths or formats for values.
A new MAC-CE for physical layer information reporting, such as “BSR for UL L1 data” described herein as an example, may support buffer size reporting for physical layer information, to enable real-time UL reports. Such a MAC-CE enables a network device to allocate accurate resources for UL physical layer information transmission. Otherwise, the network device may blindly allocate resources, and a UE may need multiple transmissions if the resources are not sufficient.
Another form of MAC-CE that may be used in physical layer information reporting includes an L1 BSR and reported physical layer information types. Signaling that is indicative of an amount of uplink physical layer information to be transmitted from a UE to a network device may be or include a BSR indicating the amount of uplink physical layer information as described at least above. Such signaling may be further indicative of which of a plurality of different types of uplink physical layer information are included in the amount of uplink physical layer information that is reported to the network device.
As in other embodiments disclosed herein, an identifier such as an LCID value in a MAC subheader may be included in the signaling to identify a type of the MAC-CE as a BSR MAC-CE for the uplink physical layer information or indicate that the BSR is for UL physical layer information.
In terms of data structure, a MAC-CE of “L1 BSR and reported L1 info types” includes L1 buffer size and physical layer information types only, but no LCG ID because the buffer size is for physical layer information. Physical layer information is not for logical channels and has no associated logical channel, as also noted elsewhere herein.
In
The L1 buffer size field in
The total amount of physical layer information that is to be transmitted may be indicated in any of various ways. For example, the L1 buffer size field shown in
Features disclosed herein in respect of a BSR for physical layer information may be provided BSRs that do or do not include reported information types. For example, a MAC-CE that includes an “L1 BSR and reported L1 info types” may have a higher priority than other MAC-CEs for MAC multiplexing, as described at least above for “BSR for UL L1 data” MAC-CEs.
By receiving a MAC-CE of “L1 BSR and reported L1 info types”, a network device such as a base station knows that the UE will report physical layer information and the type(s) of physical layer information that will be transmitted by the UE to the network device. The network device may allocate UL communication resources to the UE to transmit the physical layer information, and resource allocations are provided elsewhere herein.
The data format of UL physical layer information is configured by the network device in some embodiments. For example, a base station may configure one or more fields for physical layer information. In a MAC-CE of “L1 BSR and reported L1 info types”, a UE indicates to the network device whether each type of physical layer information is to be transmitted and will be present in a subsequent transmission of physical layer information. If present, the UE transmits the value of a type of physical layer information. Thus, a method may involve transmitting, by the UE to the network device, a value of each of multiple different types of physical layer information that is included in the amount of uplink physical layer information that was reported to the network device, in a MAC-CE of “L1 BSR and reported L1 info types” for example.
The values of the present types of physical layer information included in the amount of uplink physical layer information reported to the network device may be concatenated in a transmission to the network device. The values may be concatenated in order of physical layer information type identifiers that identify the different types of physical layer information, or in another order. In general, a UE may concatenate present information types according to any of various pre-defined rules, from lowest to highest Info-i or other identifier or index for example.
Considering an “L1 BSR and reported L1 info types” MAC-CE again as an example, a UE may inform a network device that it will report physical layer information types Info-1 and Info-5, with Info-1 being AI/ML model accuracy and Info-5 being Correlation between base station and UE models. In this example, physical layer information then the UL report for L1 data includes:
This is one example only, and different types of physical layer information may also or instead be reported and/or transmitted from a UE to a network device. Other examples of physical layer information are provided elsewhere herein.
Physical layer information embodiments that involve “L1 BSR and reported L1 info types” MAC-CEs, like those that involve “BSR for UL L1 data” MAC-CEs, may support buffer size reporting for physical layer information, to enable real-time UL reports. As discussed at least above for L1 BSR MAC-CEs, an “L1 BSR and reported L1 info types” MAC-CE enables a network device to allocate accurate resources for UL physical layer information transmission, to avoid the network device blindly allocate resources that may be insufficient.
MAC-CE embodiments, including the “BSR for UL L1 data” and “L1 BSR and reported L1 info types” examples, illustrate different options for reporting or indicating types of uplink physical layer information from a UE to a network device. An “L1 BSR and reported L1 info types” MAC-CE provides an example of signaling that includes indications of physical layer information types and an indication of an amount of physical layer information to be transmitted, whereas a “BSR for UL L1 data” MAC-CE provides an example of signaling that includes only an indication of an amount of physical layer information to be transmitted. According to another embodiment, there is no explicit BSR or other form of explicit indication of an amount of physical layer information that is to be transmitted, and mapping between a scheduling request (SR) resource and physical layer information buffer size provides a form of implicit indication of the amount of physical layer information that is to be transmitted by a UE.
For UL physical layer information scheduling, a network device such as a BS may configure dedicated SR resources to a UE. When the network device receives an SR on a dedicated SR resource, the network device knows that the SR is an SR for scheduling UL physical layer information. In addition, the network device may configure a mapping between an SR resource and a physical layer information amount or buffer size, such that a dedicated SR resource is linked to a specific physical layer information amount or buffer size. Multiple dedicated SR resources may be mapped or linked to respective different physical layer information amounts or buffer sizes. Based on the SR resource used by a UE, a network device that received an SR from the UE knows the physical layer information amount or buffer size, and allocates UL resources accordingly. In this solution, no BSR MAC-CE is transmitted by the UE.
Such a mapping may be configured at a UE by a network device, and resource and physical layer information amount information for the mapping, such as SR resource indices and corresponding buffer sizes for the example in
Regarding transmission of uplink physical layer information, the UE may transmit an indication as to whether a type of physical layer information is present in the physical layer information, and a value of the type of physical layer information if present. Transmission of uplink physical layer information types and values are described by way of example at least above, in the context of L1 BSR embodiments. Although resource mapping embodiments do not involve a BSR, resource mapping embodiments may use an approach to transmitting physical layer information that is the same as or similar to an approach disclosed for L1 BSR embodiments.
Another embodiment involves a network device configuring a mapping between one or more dedicated SR resources and one or more types of physical layer information. One SR resource may be mapped to one or multiple physical layer information types. Based on the SR resource on which an SR is received, a network device determines the physical layer information types that a UE is to transmit. The network device may also calculate or otherwise determine an amount of physical layer information types that the UE is to transmit, based on the SR and/or the type(s) of physical layer information.
As described at least above for SR resource/buffer size mapping, a mapping between SR resources and physical layer information types may be configured at a UE by a network device. Resource information and physical layer information types for the mapping, such as SR resource indices and information type identifiers for the example in
Transmission of uplink physical layer information may be the same as or similar to an approach that is disclosed at least above in the context of reporting information types in a MAC-CE, such as “L1 BSR and reported L1 info types”. For example, the UE may concatenate values for different information types. Concatenation may be according to any of various pre-defined rules, such as from lowest to highest Info-i or other identifier or index.
In SR resource mapping embodiments, no MAC-CE is transmitted by the UE. SR resource mapping embodiments involve a UE transmitting signaling that indicates an amount of physical layer information on a communication resource that is configured for uplink physical layer information reporting. The communication resource may be or include an SR communication resource that is dedicated to uplink physical layer information. The communication resource may be linked, associated with, or otherwise mapped to the amount of uplink physical layer information that the UE has to transmit to the network device as shown by way of example in
In another embodiment, one or more SR resources may be mapped to both amount of uplink physical layer information and type of uplink physical layer information. With reference to
SR resource mapping supports amount or buffer size reporting and information type reporting for physical layer information, enabling real-time UL reporting. Such reporting may enable a network device to allocate accurate resources for UL physical layer information transmission and avoid blindly allocating resources that may be insufficient.
Embodiments disclosed herein include embodiments that involve explicit indications of uplink physical layer information amounts, with or without explicit indications of uplink physical layer information type(s), in new types of MAC-CEs, for example. Other embodiments involve implicit indications of uplink physical layer information amounts, type(s), or both, based on SR resource mapping, for example. Values of uplink physical layer information may be transmitted on their own, or with indications of presence or absence of information types.
Transmission of uplink physical layer information may involve transmitting the uplink physical layer information, by the UE to the network device, on a communication resource that is allocated to the UE based on the amount of uplink physical layer information. In some embodiments, transmitting the uplink physical layer information involves transmitting the uplink physical layer information in a format that is configured by the network device for the uplink physical layer information. Concatenation of present information types is an example of one possible format, and others, which may but need not necessarily be configured by the network device, are possible.
Embodiments are described above primarily from the perspective of a UE. As illustrated by way of example in
For example, various features related to transmitting signaling by a UE to a network device at 1110 are described herein, and from the perspective of a network device a method may also or instead involve receiving, by a network device 1104 from a UE 1102 in a wireless communication network, signaling that is indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device.
Features disclosed elsewhere herein may be provided in network-side methods. As described at least above, for example, the physical layer information for which report signaling is received by the network device 1104 at 1110 may be or include control information, data information, or both control information and data information in the physical layer. The uplink physical layer information may be determined by the UE 1102 in some embodiments, and has no associated logical channel because it is physical layer information.
Network-side embodiments may involve signaling that is or includes a BSR indicating the amount of uplink physical layer information. A BSR may be or include a MAC-CE, with an identifier in a MAC subheader to identify a type of the MAC-CE as a BSR MAC-CE for the uplink physical layer information, for example.
The signaling received by the network device 1104 at 1110 may also be indicative of which of different types of uplink physical layer information are included in the amount of uplink physical layer information. The signaling may be or include a bitmap to indicate whether each of the different types of uplink physical layer information is included in the amount of uplink physical layer information, for example. Such a bitmap may be included in a MAC subheader in some embodiments.
A MAC-CE for uplink physical layer information, which may or may not include an indication of information type, may have a higher priority than another MAC-CE for MAC multiplexing, as also described elsewhere herein.
Uplink physical layer information may be transmitted by the UE and received by the network device 1104 on a communication resource that is allocated to the UE by the network device, or another network node, based on the amount of uplink physical layer information that is to be transmitted. Signaling indicative of resource allocation is illustrated in
Transmission of uplink physical information by the UE 1102, at 1114 in
Some embodiments do not involve reporting with an explicit indication of the amount of uplink physical layer information that is to be transmitted. A method may involve the network device 1104 receiving the signaling at 1110 on a communication resource that is configured, by the network device at 1110 or another network node, for uplink physical layer information reporting. As also described elsewhere herein, the communication resource may be or include an SR communication resource that is dedicated to uplink physical layer information. Such a communication resource may be mapped to the amount of uplink physical layer information, a type of uplink physical layer information, or both the amount of uplink physical layer information and a type of uplink physical layer information.
The uplink physical layer information may be received by the network node 1104 from the UE 1102 at 1114 in a format that is configured, by the network device at 1110 or another network node, for the uplink physical layer information.
Configuration signaling is illustrated at 1110, and may involve transmitting signaling by the network device 1104 and receiving signaling by the UE 1102. Signaling related to configuration may be indicative of, for example, one or more of the following: a communication resource that is configured for uplink physical layer information reporting; mapping of communication resources and amounts of uplink physical layer information, types of uplink physical layer information, or both amounts and types of uplink physical layer information; a communication resource that is allocated based on the amount of uplink physical layer information; and a format that is configured for the uplink physical layer information.
The present disclosure encompasses various embodiments, including not only method embodiments, but also other embodiments such as apparatus embodiments and embodiments related to non-transitory computer readable storage media. Embodiments may incorporate, individually or in combinations, the features disclosed herein.
An apparatus may include a processor and a non-transitory computer readable storage medium, coupled to the processor, storing programming for execution by the processor. In
While this disclosure has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the disclosure, will be apparent to persons skilled in the art upon reference to the description. It is therefore intended that the appended claims encompass any such modifications or embodiments.
From the perspective of a UE as an illustrative example, programming stored in or on a non-transitory computer readable storage medium may include instructions to, or to cause a processor to, transmit to a network device in a wireless communication network, signaling indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. The physical layer information may be or include control information, data information, or both control information and data information in the physical layer.
Embodiments related to UEs or non-transitory computer readable storage media for UE operations may include any one or more of the following features, for example, which are also discussed elsewhere herein:
From the perspective of a network device as an illustrative example, programming stored in or on a non-transitory computer readable storage medium may include instructions to, or to cause a processor to, receive, from a UE in a wireless communication network, signaling indicative of an amount of uplink physical layer information to be transmitted from the UE to the network device. The physical layer information may be or include control information, data information, or both control information and data information in the physical layer.
Embodiments related to network devices or non-transitory computer readable storage media for network device operations may include any one or more of the following features, for example, which are also discussed elsewhere herein:
Other features, including those disclosed herein in the context of method embodiments, may also or instead be implemented in apparatus or computer program product embodiments.
Although aspects of the present disclosure have been described with reference to specific features and embodiments thereof, various modifications and combinations can be made thereto without departing from the disclosure. The description and drawings are, accordingly, to be regarded simply as an illustration of some embodiments of the disclosure as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present disclosure. Therefore, although embodiments and potential advantages have been described in detail, various changes, substitutions and alterations can be made herein without departing from the disclosure as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present disclosure, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present disclosure. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
In addition, although described primarily in the context of methods and apparatus, other implementations are also contemplated, as instructions stored on a non-transitory computer-readable medium, for example. Such media could store programming or instructions to perform any of various methods consistent with the present disclosure.
Moreover, any module, component, or device exemplified herein that executes instructions may include or otherwise have access to a non-transitory computer readable or processor readable storage medium or media for storage of information, such as computer readable or processor readable instructions, data structures, program modules, and/or other data. A non-exhaustive list of examples of non-transitory computer readable or processor readable storage media includes magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, optical disks such as compact disc read-only memory (CD-ROM), digital video discs or digital versatile disc (DVDs), Blu-ray Disc™, or other optical storage, volatile and non-volatile, removable and nonremovable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology. Any such non-transitory computer readable or processor readable storage media may be part of a device or accessible or connectable thereto. Any application or module herein described may be implemented using instructions that are readable and executable by a computer or processor may be stored or otherwise held by such non-transitory computer readable or processor readable storage media.
The present application is a continuation of International Application No. PCT/CN2022/076632, filed on Feb. 17, 2022, the disclosure of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2022/076632 | Feb 2022 | WO |
| Child | 18807557 | US |
