Compression of user data transmitted between lower layer split central unit and radio unit using bitmap representation

By compressing user data with bitmap representations, the method addresses inefficiencies in data transmission between lower layer split central units and radio units, enhancing resource utilization and pooling efficiency in wireless communication systems.

JP7591074B2Active Publication Date: 2024-11-27TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023022225
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2018-10-03
Filing Date
2023-02-16
Publication Date
2024-11-27
Estimated Expiration
2039-10-01

AI Technical Summary

Technical Problem

Existing wireless communication systems face inefficiencies in data transmission between lower layer split central units and radio units due to high bit rates on fronthaul interfaces, limiting the pooling of shared links and resource utilization.

Method used

Implementing a method for compressing user data using bitmap representations to reduce bit rates on the fronthaul interface by mapping reference symbols to resource elements and transmitting compressed data between lower layer split central units and radio units.

Benefits of technology

The method reduces bit rates on the fronthaul interface, enabling more efficient pooling of shared links and improving resource utilization in wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007591074000001
    Figure 0007591074000001
  • Figure 0007591074000002
    Figure 0007591074000002
  • Figure 0007591074000003
    Figure 0007591074000003
Patent Text Reader

Abstract

Wireless communication and related wireless devices and network nodes are provided. A method for transmitting user data from a lower layer split central unit (LLS-CU) to a radio unit (RU) in a radio access network (RAN) node (200) of a wireless communication system for transmission by the RU over an air interface, the method comprising: mapping reference symbols to be transmitted by the RU to resource elements to provide 3GPP® mapped data; the mapped data including the reference symbols is compressed using a bitmap representation of the mapped data to obtain compressed data; and transmitting the compressed data from the LLS-CU to the RU.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Related Applications This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 740,701, entitled “COMPRESSING USER DATA TRANSMITTED BETWEEN A LOWER LAYER SPLIT CENTRAL UNIT AND A RADIO UNIT USING BITMAP REPRESENTATIONS,” filed October 3, 2018, the entire disclosure of which is incorporated herein by reference.

[0002] The present disclosure relates generally to communications, and more particularly, to wireless communications and associated wireless devices and network nodes. [Background technology]

[0003] FIG. 1 illustrates an example of a wireless communication system 300 represented as a 5G network architecture composed of core network functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface.

[0004] From the access side, the 5G network architecture shown in FIG. 1 includes multiple user equipments (UEs) connected by air interfaces to either a radio access network (RAN) or an access network (AN), and to an access and mobility management function (AMF). In general, the R (AN) comprises a base station, such as an evolved node B (eNB) or a 5G base station (gNB) or the like. From the core network side, the 5G core NF shown in FIG. 1 includes a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and an application function (AF).

[0005] One of the objectives of the 5G core network is to separate the user plane and the control plane. The user plane generally carries user traffic, and the control plane generally carries signaling in the network. In Figure 1, the UPF is in the user plane, and all other NFs (i.e., AMF, SMF, PCF, AF, AUSF, and UDM) are in the control plane. Separating the user plane and the control plane allows each plane resource to be scaled independently. Such separation may also allow the UPF to be distributed and deployed separately from the control plane functions. Summary of the Invention

[0006] According to some embodiments, a method of transmitting user data from a lower-layer split central unit (LLS-CU) to a radio unit (RU) in a network node of a wireless communication system for transmission by the RU over an air interface may be provided. The method may include mapping, in the LLS-CU, reference symbols to be transmitted by the RU to resource elements to provide the mapped data. The method may further include compressing the mapped data including the reference symbols using a bitmap representation of the mapped data to obtain compressed data. The method may further include transmitting the compressed data from the LLS-CU to the RU.

[0007] According to some other embodiments, a method for operating a radio unit in a network node may be provided. The method may include receiving, at a RU, a bitmap representation and compressed data. The method may further include decompressing the compressed data using the bitmap representation at the RU to recover the mapped data. The method may further include transmitting the mapped data over an air interface.

[0008] According to some embodiments of the inventive concept, mechanisms may be provided to reduce the bit rate on the fronthaul interface during low or normal operation of the radio, allowing more efficient pooling of shared links.

[0009] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate several non-limiting embodiments of the inventive concepts. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram illustrating an example of a wireless communication system representing a fifth generation wireless system (5G) network architecture composed of core network functions (NFs). [Diagram 2] FIG. 2 is a block diagram illustrating an example of a network node including a lower layer split central unit and a radio unit, according to some embodiments. [Diagram 3] FIG. 2 illustrates an example of a downlink (DL) functional split for various physical layer channels and transmission modes. [Figure 4] FIG. 1 illustrates an example of an uplink (UL) functional split for various physical layer channels and transmission modes. [Diagram 5] 1 is a signal flow diagram illustrating an example of operation in a wireless communication network according to some embodiments. [Figure 6] FIG. 1 is a signal flow diagram illustrating an example of signals related to a DCI message, according to some embodiments. [Figure 7] FIG. 2 illustrates an example of DACI and UP-UL / UP-DL in accordance with some embodiments. [Figure 8A] FIG. 2 illustrates an example of a mapping of resource elements to physical resource blocks according to some embodiments. [Figure 8B]FIG. 2 illustrates a bitmap in matrix format according to some embodiments. [Figure 9] FIG. 1 is a block diagram illustrating an example of a Radio Access Network (RAN) node, in accordance with some embodiments. [Figure 10] 1 is a flowchart illustrating an example of a process for transmitting user data from a unit in a network node (e.g., a Lower Layer Split Central Unit (LLS-CU)) to another unit in the network node (e.g., a Radio Unit (RU)) in accordance with some embodiments. [Figure 11] 5 is a flow chart illustrating an example of a process for receiving user data by a unit in a network node (e.g., an RU) from another unit in the network node (e.g., an LLS-CU), according to some embodiments. [Figure 12] 1 is a block diagram of a wireless network according to some embodiments. [Figure 13] FIG. 2 is a block diagram of a user equipment according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. However, the inventive concept may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It may be implicitly assumed that an element from one embodiment is present / used in another embodiment.

[0012] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and should not be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0013] FIG. 2 illustrates an example of a RAN node 200, according to some embodiments. As illustrated in FIG. 2, the RAN node 200 may include an eNB or gNB with a lower layer split central unit (LLS-CU) and one or more radio units (RUs) connected to the LLS-CU. The LLS-CU may interact with the RU(s) via the LLS-C control plane(s) and / or the LLS-U user plane(s) on the so-called "fronthaul". As illustrated, the LLS-CU is a logical node that includes eNB / gNB functionality as described below. In this regard, the LLS-CU controls the operation of the RU(s) in some embodiments described herein. The LLS-CU communicates with the control plane (CP) and user plane (UP) functions of the core network on the backhaul. The RUs transmit and receive downlink and uplink data, respectively, to / from one or more user equipment (UE) nodes 100 over the air interface.

[0014] Figure 3 shows the downlink (DL) functional split between the LLS-CU and the RU for various physical layer channels and transmission modes. In the DL, iFFT, CP adding, and digital beamforming functions may reside in the RU. According to some embodiments, additional PHY functions may reside in the LLS-CU, including resource element mapping, precoding, layer mapping, modulation, scrambling, rate matching, and coding.

[0015] Figure 4 shows an uplink (UL) functional split for various physical layer channels and transmission modes. As shown in Figure 4, in the UL, FFT, CP removal, and digital beamforming functions may reside in the RU. According to some embodiments, additional PHY functions including resource element demapping, equalization, demodulation, descrambling, rate dematching, and decoding may reside in the LLS-CU.

[0016] As shown in Figure 5, control plane (CP) messages may be exchanged between the LLS-CU and the RU according to the scheduling and beamforming command transfer procedure. One purpose of the CP message is to transmit data-associated control information (DACI) required for processing of user data. For example, in some embodiments, this may include scheduling and / or beamforming commands. Messages may be sent separately for DL-related commands and UL-related commands as shown in Figure 5. Similarly, for purposes including increased flexibility, CP messages may be sent either together or separately depending on the channel on which the information is conveyed. For example, PUCCH and PUSCH may or may not be bundled into a single CP message depending on the implementation.

[0017] In some embodiments disclosed herein, methods and devices related to transmitting losslessly compressed user data between an LLS-CU and an RU are provided. In some embodiments disclosed herein, interfacing between an LLS-CU, such as a central unit and / or baseband unit, and an RU supporting 3GPP LTE and NR is provided.

[0018] In some embodiments, the method includes transmitting a data associated control information message (DACI) from the LLS-CU to the RU. In some embodiments, the DACI includes information that specifies how the RU should handle user data messages forwarded from the LLS-CU to the RU, the DACI including content to be transmitted over the air. In other embodiments, the DACI includes controlling how data is received over the air and inserted into at least one user data message forwarded from the RU to the LLS-CU. Downlink and uplink user plane messages may be referred to herein using the terms UP-DL and UP-UL, respectively.

[0019] DACI can exist as different types. In some embodiments, the most commonly used type of DACI is one with section type 1, which contains information describing how normal transmission should be performed. In some embodiments, a section type 1 DACI message contains a list of sections, each section containing: Identifiers for mapping DACI and UP-DL or UP-UL to section IDs, A logical RU_port to support multiple overlapping (in time / frequency) and independent address ranges of identifiers; A data direction, which may include at least a UL direction or a DL direction; Physical Resource Block (PRB) range, Symbol scope, Information relating to which RE in the PRB range relates to the remaining information; Beamforming indices and / or weights, Compression methods for beamforming weights, as well as · Formats and / or compression methods for user data.

[0020] In some embodiments, the UP-DL and UP-UL messages include: the corresponding identifier(s) (section ID and RU_port) as the corresponding section type 1 message, Formats and / or compression methods for user data; and · One sample per RE in any of several supported formats.

[0021] According to existing specifications, one sample per resource element (RE) may be sent in the data plane message for all REs in a physical resource block (PRB). Each sample includes multiple bits, e.g., 30 bits. For symbols where only reference symbols are sent, samples for all REs may need to be sent even for the "0" in the reference symbol. When the reference signal is sent simultaneously in all sectors of the gNB, the LLS-CU may transmit the full bit rate / bandwidth to all radios for this symbol. For that reason, the possible pooling gain may be reduced.

[0022] FIG. 6 illustrates a signal flow diagram related to DACI messages, according to some embodiments. As shown, one embodiment of DACI(A) is directed to a DACI message sent from the LLS-CU to the RU with information describing the upcoming reception. In this manner, the RU sends one or more UP-UL messages upon request containing samples of the received signal over the air. In another embodiment, DACI(B) is directed to a DACI message sent from the LLS-CU to the RU with information describing the upcoming transmission. The LLS-CU in this embodiment is directed to sending one or more UP-DL messages containing information to be transmitted over the air. In yet another embodiment, DACI(C) is directed to two different DACI messages sent from the LLS-CU to the RU with information describing the upcoming transmission. The two DACI messages describe at least one transmission method for different REs in the same symbol in the same PRB. The LLS-CU in this embodiment then transmits one or more UP-DL messages containing information to be transmitted over the air, combined for the two DACIs.

[0023] Figure 7 shows a high level of the protocol for the DACI message and the UP-UL / UP-DL messages carrying the UP-UL and UP-DL, respectively. In some embodiments, the DACI message includes a common header indicating the RU_Port_ID for the DACI, then a variable set of sections, each describing an upcoming transmission. In some embodiments, the UP-UL and UP-DL messages include a common header indicating the RU_Port_UD for the UP-xx message, then a variable set of sections, each including a section header indicating the contents of the data field, and a data field containing the UP-UL or UP-DL data. The section header according to some embodiments also includes a section ID for mapping to the corresponding section of the DACI message, and the format of the data in the data field.

[0024] In some embodiments, user data conveyed in a UP-DL message from the LLS-CU to the RU may include reference symbols mapped to REs. According to some embodiments, user data forwarded in a UP-DL message to the RU may be compressed for transmission to the RU using a bitmap representation that indicates which samples or resource elements (REs) should not be forwarded further and which should be forwarded.

[0025] In some instances, resource elements (REs) are known to carry 0. For PRBs where only reference symbols are transferred, most of the REs in the PRB will carry 0, i.e., the REs will be empty. In the protocol specification for DACI, there is already a means to signal which REs in a UP-DL message are empty, i.e., marked as reMask field. However, the DACI protocol specification dictates that REs marked as empty shall still have data samples transferred in the associated UP-DL and UP-UL transmissions.

[0026] The protocol also allows multiple DACI sections to point to PRB(s) with different reMask sets to allow different control (e.g., beamforming) for different sets of REs in the PRB(s). The current protocol allows two DACI messages to point to the same PRB for the RU_port_ID. The corresponding UP-DL and UP-UL are still combined into one packet for both those DACI sections.

[0027] FIG. 8A illustrates a physical resource block (PRB) onto which data to be transmitted from the LLS-CU to the RU in a UP-DL message is mapped, where the PRB includes cell-specific reference symbols (CRS) in predefined locations within the PRB. The PRB spans 14 OFDM symbols in the time dimension (horizontal axis) and 12 frequency subchannels in the frequency dimension (vertical axis). Each time / frequency element in the PRB corresponds to an RE of the PRB. As shown in FIG. 8A, the PRB includes two REs carrying CRS in symbols 0, 4, 7, and 11. In this example, all other REs in the PRB carry 0. Generally, some REs in the PRB are known to carry 0, and in a PRB where only reference symbols are carried, the majority of the REs will carry 0.

[0028] Some embodiments compress UP-DL data in a UP-DL message from the LLS-CU to the RU using a bitmap representation of the mapped data to reduce the bandwidth requirements of the UP-DL message. The bitmap representation may be carried in the corresponding DACI message and / or in the header of the UP-DL message. When a bitmap is sent, data corresponding to REs carrying 0 does not need to be included in the UP-DL message.

[0029] In some embodiments, the reMask field of the DACS may be used as a bitmap, and a field is added in the DACS corresponding to the UP-DL message that indicates that only bits set to 1 in the DACS should be forwarded. This allows the UP-DL to avoid including unused REs in data messages. In some examples, this field may be included in the udCompHdr field of the DACS message.

[0030] In additional or alternative embodiments, a bitmap field may be added in the UP-DL message itself to indicate how samples in the UP-DL message should be mapped to REs. For example, the bitmap may include a list of bits indicating which of the REs are not sent and which are sent. For example, a "0" in the bitmap indicates that the corresponding RE carries a 0 and that no samples are sent for that RE, and a "1" in the bitmap indicates that the corresponding RE carries a non-zero value and that a sample is sent for that RE. The format of the reMask may be reused for this purpose. This may ensure that the LLS-CU and the RU have the same understanding of what samples are included in the UP-DL message. If this field were left out of the UP-DL message, a missing DACI message may indicate that some REs should be forwarded, resulting in misunderstanding of which samples belong to which RE. In some examples, the bitmap field may be included in the UdCompHdr field of the UP-DL message.

[0031] 8A, a bitmap may be generated that represents the presence of 0 and non-0 samples in the PRB, and the bitmap indicates the mapped data including RE and corresponding reference symbols. For example, the symbols may be described as columns in the bitmap, such that symbols 0 and 7 in the PRB correspond to 10000010000b in the bitmap, symbols 4 and 11 correspond to 000100000100b in the bitmap, and symbols 1, 2, 3, 5, 6, 8, 9, 10, 12, and 13 correspond to 000000000000b in the bitmap. Thus, the bitmap may be represented in a matrix format, as shown in FIG. 8B.

[0032] According to some embodiments, samples corresponding to 0 in the bitmap (corresponding to REs carrying 0 values) are not transmitted in the UP-DL message, and only samples corresponding to 1 in the bitmap are transmitted. Thus, the bandwidth of the UP-DL message can be significantly reduced.

[0033] It will be appreciated that user data carried in UP-DL messages may also be compressed, and the compression described herein may be performed in addition to such data compression (i.e., "in addition" to user data compression).

[0034] In some embodiments, compressing user data using a bitmap representation can reduce the bit rate on the fronthaul interface during low or normal operation of the wireless unit and enable further pooling of shared links.

[0035] FIG. 9 illustrates an example of a RAN node 200 (also referred to as a network node, base station, eNB, eNodeB, gNB, gNodeB, etc.) of a wireless communication network configured to provide cellular communications, according to an embodiment of the inventive concept. The RAN node 200 may correspond to a central unit, a radio unit, or a combination of a central unit and a radio unit in a RAN node. As shown, the RAN node 200 may include a transceiver circuit 202 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink wireless communications with wireless devices. The RAN node 200 may include a network interface circuit 204 (also referred to as a network interface) configured to provide communications with other nodes of the wireless communication network (e.g., with other base stations and / or core network nodes). The RAN node 200 may also include a processor circuit 206 (also referred to as a processor) coupled to the transceiver circuit 202, and a memory circuit 208 (also referred to as a memory) coupled to the processor circuit 206. The memory circuitry 208 may include computer readable program code that, when executed by the processor circuitry 206, causes the processor circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processor circuitry 206 may be defined to include memory such that a separate memory circuitry is not required.

[0036] As described herein, operations of the RAN node 200 may be performed by the processor 206, the network interface 204, and / or the transceiver 202. For example, the processor 206 may control the transceiver 202 to transmit downlink communications over the air interface through the transceiver 202 to one or more UEs and / or receive uplink communications over the air interface through the transceiver 202 from one or more UEs. Similarly, the processor 206 may control the network interface 204 to transmit communications over the network interface 204 to one or more other network nodes and / or receive communications from one or more other network nodes through the network interface. Moreover, modules may be stored in the memory 208 that, when their instructions are executed by the processor 206, provide instructions for the processor 206 to perform respective operations (e.g., operations described below with respect to the exemplary embodiments). Additionally, a structure similar to that of FIG. 9 may be used to implement other network nodes, e.g., omitting the transceiver 202. Moreover, the network nodes described herein may be implemented as virtual network nodes.

[0037] The operation of a RAN node, such as a gNB, will now be described with reference to the flowchart of Figure 10. For example, modules may be stored in the memory 208 of Figure 9 that provide instructions that, when executed by the processor 206, cause the processor 206 to perform the respective operations of the flowchart of Figure 10. Although Figure 10 is described below with respect to the RAN node 200 shown in Figure 9, the process may be performed by any node in a 5G network.

[0038] Figure 10 illustrates an example of operations for transmitting user data from one unit in a network node to another unit in the network node. Although Figure 10 is described below with respect to an LLS-CU transmitting to a RU for transmission by the RU over the air interface, other implementations are possible. For example, the operations may be performed with respect to an RU transmitting to an LLS-CU.

[0039] At block 1010, the processor 206 maps reference symbols to be transmitted by the RU to resource elements to provide mapped data. In some embodiments, the reference symbols include cell-specific reference signals (CRS). In some embodiments, the processor 206 maps user data with the reference symbols to provide mapped data.

[0040] At block 1020, the processor 206 compresses the mapped data using a bitmap representation of the mapped data to obtain compressed mapped data. Compressing the mapped data using the bitmap representation of the mapped data may be a lossless compression technique. In some embodiments, the bitmap representation of the mapped data corresponds to a physical resource block (PRB) and includes bit positions that correspond to resource elements in the PRB. In additional or alternative embodiments, the user data in the mapped data is already compressed.

[0041] At block 1030, the processor 206 transmits an indication that the mapped data has been compressed using the bitmap representation, and at block 1040, the processor 206 transmits the bitmap representation to the RU. In some embodiments, the indication may be transmitted in a Data Associated Control Information (DACI) message carrying the bitmap representation of the mapped data. The indication may be transmitted in a udCompHdr or udCompParam field of the DACI message. The bitmap representation may be transmitted in a reMask field of the DACI message. In additional or alternative embodiments, the indication and / or the bitmap representation may be transmitted to the RU in a User Plane Downlink (UP-DL) message carrying the compressed mapped data as User Data Downlink (UP-DL) data. The bitmap representation may include a signal regarding the mapping of resource elements. The signal may include a list of bits that are not sent in the UP-DL message and a list of bits that are sent.

[0042] In some examples, the DACI message may include a first section that corresponds to the PRB and includes a first resource element mask or reMask that identifies a first set of resource elements in the PRB. The DACI message may include a second section that corresponds to the PRB and includes a second resource element mask or reMask that identifies a second set of resource elements in the PRB that is different from the first set of resource elements in the PRB. The first and second sets of resource elements in the PRB may include different beamforming parameters. In additional or alternative examples, the DACI message includes a field that causes only non-zero bits to be transferred. The field may be in a udCompHdr field.

[0043] The processor 206 transmits the compressed mapped data from the LLS-CU to the RU at block 1050. In some embodiments, the compressed mapped data is transmitted to the RU in a UP-DL message.

[0044] Various operations from the flowchart of Figure 10 may be optional with respect to some embodiments and related methods. With respect to the methods of exemplary embodiments 1 and 17 (described below), for example, the operation of block 1030 of Figure 10 may be optional. Furthermore, the order of operations corresponding to blocks 1010, 1020, 1030, and 1040 of Figure 10 is only an example order. Thus, the operations corresponding to blocks 1010, 1020, 1030, and 1040 of Figure 10 may be performed in a different order other than the order shown.

[0045] Figure 11 illustrates an example of a unit in a network node receiving user data from another unit in the network node. Although Figure 11 is described below with respect to the RU receiving from the LLS-CU, other implementations are possible. For example, the operations may be performed with respect to the LLS-CU receiving from the RU.

[0046] At block 1110, the processor 206 receives the bitmap representation at the RU. At block 1120, the processor 206 receives the compressed data. At block 1130, the processor 206 decompresses the compressed data using the bitmap representation to recover the mapped data. For example, the processor 206 may insert zeros in the UP-DL data at locations corresponding to the zeros in the bitmap representation. At block 1140, the processor 206 causes the mapped data to be transmitted to the UE 100 over the air interface.

[0047] Various embodiments describe a network node that includes a processor circuit, a transceiver coupled to the processor circuit, and a memory coupled to the processor circuit, the memory including machine-readable computer program instructions that, when executed by the processor circuit, cause the processor circuit to perform some of the operations illustrated in Figures 10-11.

[0048] Listing of Exemplary Embodiments

[0049] Exemplary embodiments are described below, where reference numbers / letters are given in parentheses as examples / illustrations without limiting the exemplary embodiments to the particular elements indicated by the reference numbers / letters. 1. A method of transmitting user data from a lower layer split central unit (LLS-CU) to a radio unit (RU) in a network node of a wireless communication system for transmission by the RU over a radio interface, the method comprising: Mapping (1010), in the LLS-CU, user data and a plurality of reference symbols to be transmitted by the RU together with the user data to resource elements to provide mapped data; compressing (1020) the mapped data, including the plurality of reference symbols, using the bitmap representation of the mapped data to obtain compressed data; transmitting (1040) a bitmap representation from the LLS-CU to the RU; transmitting (1050) the compressed data from the LLS-CU to the RU; A method comprising: 2. sending (1030) an indication to the RU that the mapped data includes a bitmap representation; 2. The method of embodiment 1, further comprising: 3. The method of embodiment 2, wherein the instruction includes a field in a header of the message that carries a bitmap representation of the mapped data. 4. The method of embodiment 3, wherein the field includes a udCompHdr field or a udCompParam field of a user plane downlink (UP-DL) message. 5. The method of embodiment 2, wherein the instruction includes a field in a data associated control information (DACI) message sent from the LLS-CU to the RU. 6. The method of embodiment 1, in which the indication and the bitmap representation are carried in the same message from the LLS-CU to the RU. 7. The method of embodiment 1, in which the indication, the bitmap representation, and the compressed data are carried in the same message from the LLS-CU to the RU. 8. A method as in any one of embodiments 1 to 7, wherein the bitmap representation of the mapped data includes bit positions corresponding to resource elements of a plurality of resource element physical resource blocks (PRBs) to which the mapped data is mapped. 9. The method of embodiment 1, wherein the bitmap representation is sent to the RU in a data associated control information (DACI) message. 10. The method of embodiment 9, wherein the bitmap representation is carried in a reMask field of a DACI message. 11. The method of embodiment 1, wherein the bitmap representation is sent to the RU in a user plane downlink (UP-DL) message in which the compressed data is transmitted. 12. The method of embodiment 11, wherein the bitmap representation includes a signal regarding mapping of resource elements. 13. The method of embodiment 12, wherein the signal includes a list of samples that are not sent to the RU and a list of samples that are sent to the RU. 14. The method of any one of embodiments 1 to 13, wherein the instruction is sent in a user plane downlink (UP-DL) message in which the compressed data is transmitted. 15. Receiving (1110) a bitmap representation at the RU; Receiving (1120) the compressed data at the RU; decompressing (1130) the compressed data using the bitmap representation at the RU to recover the mapped data; Transmitting (1140) the mapped data over the wireless interface; 15. The method of any one of the preceding claims, further comprising: 16. The method of any one of embodiments 1 to 15, wherein the user data includes pre-compressed user data. 17. A processor circuit; a transceiver coupled to the processor circuit; a memory coupled to the processor circuit; 17. A network node comprising: a memory comprising machine-readable computer program instructions that, when executed by a processor circuit, cause the processor circuit to perform the operations of any one of embodiments 1 to 16. Network node.

[0050] Explanations of abbreviations from the above disclosure are provided below. Abbreviation Description 3GPP 3rd Generation Partnership Project 5G (fifth generation wireless system) NG Next generation IoT Internet of Things AKA Authentication and Key Agreement UICC Universal Integrated Circuit Card SA2 3GPP Architecture Working Group SA3 3GPP Security Group UP User Plane LTE Long Term Evolution (4th generation wireless system) CP Control Plane AS Access Hierarchy eNB Evolved Node B UE User Equipment or End User Device SMC Security Mode Commands RRC Radio Resource Control PDCP Packet Data Convergence Protocol RAN Radio Access Network CN Core Network PDU Packet Data Unit DRB Data Radio Bearer AN Access Network (R)AN Both 3GPP and non-3GPP access networks NAS Network Access Hierarchy AMF Access and Mobility Management Functions NF Network Function UDM Unified Data Management PCF Policy Control Function DRB-IP Data Radio Bearer Integrity Protection IE Information Elements QoS Quality of Service gNB 5G base station NEF Network Exposure Function NWDAF network data analysis function PCF Policy Control Function UDM Unified Data Management UPF User Plane Function DL Downlink UL Uplink LLS Lower Layer Split LLS-U Lower Layer Split User Plane LLS-C Lower Layer Split Control Plane LLS-CU Lower Layer Split Central Unit PHY Physical Layer MP Management Plane SSM Synchronization Status Messages TRX Transceiver

[0051] As used herein, the following terms and definitions may apply:

[0052] Control Plane: specifically refers to real-time control between the LLS-CU and the RU, and should not be confused with the UE's control plane; c_eAxC: component eAxC: the portion of the eAxC flow that is allocated to a particular LLS-CU processing element.

[0053] Downlink: Data flow towards a radiating antenna (generally on the LLS interface), eAxC: Extended Antenna Carrier: Data flow (or spatial stream) for a single antenna for a single carrier in a single sector.

[0054] Lower Layer Split: The logical interface between the LLS-CU and the RU when using lower layer (intra-PHY based) functional split.

[0055] Lower Layer Split User Plane: The logical interface between the LLS-CU and the RU when using lower layer functional split.

[0056] Lower Layer Split Control Plane: A logical interface between the LLS-CU and the RU when using lower layer functional split.

[0057] High PHY: The PHY processing part on the LLS-CU side of the fronthaul interface, including FEC encoding / decoding, scrambling, and modulation / demodulation.

[0058] Lower Layer Split Central Unit: A logical node that hosts the PDCP / RLC / MAC / Higher PHY layers based on the lower layer functional split.

[0059] Low PHY: Part of the PHY processing on the RU side of the fronthaul interface, including FFT / iFFT, digital beamforming, and PRACH extraction and filtering.

[0060] Management Plane: refers to non-real-time management operations between the LLS-CU and the RU: Radio Unit: a logical node that hosts the lower PHY layer and RF processing based on a lower layer functional split. It is similar to the 3GPP "TRP" or "LLS-DU", but is more specific in including the lower PHY layer (FFT / iFFT, PRACH extraction).

[0061] Synchronization Plane: refers to traffic between the RU or LLS-CU and a synchronization controller, which is generally an IEEE-1588 Grandmaster (although the Grandmaster functionality may be embedded in the LLS-CU).

[0062] Slot: This is a group of 14 symbols for LTE and NR. LTE has a separate slot definition in 3GPP that is 7 symbols, but that definition is not used herein. Thus, for NR, "slot" in this document means a slot as defined by 3GPP, while for LTE, "slot" in this document correlates to an LTE "TTI" as defined by 3GPP.

[0063] Spatial Stream: The data flow on the DL related to the precoded data (can be the same as a layer or different if there is an extension in precoding), and the data flow on the UL related to the number of outputs from the digital beamforming (sometimes called "beams").

[0064] Synchronization Status Messages: Part of the ITU G.781 and G.8264 standards.

[0065] TRX: Refers to a specific processing chain in the RU associated with a D / A or A / D converter. With digital beamforming, the number of TRXs can exceed the number of spatial streams, and with analog beamforming, the number of TRXs can be less than the number of antenna elements.

[0066] User Plane: Refers to IQ sample data transferred between LLS-CU and RU UL: UpLin: Data flow away from the radiating antenna (generally on the LLS interface), XRB: xRAN Resource Block: For LTE, this is the same as PRB (Physical Resource Block), while for NR, this is the same as CRB (Common Resource Block). In NR, there can be a dynamically variable offset between CRB and PRB, but this specification wishes to use a fixed offset (for operational consistency), which is the case for PRB in LTE.

[0067] Citations for references from the above disclosure are provided below. References [1]: 3GPP TR23.724 V1.0.0 (2018-07), Technical Specification Group Services and System Aspects; Research on Cellular IoT Support and Development for 5G Systems (Release 16); and Reference [2]: CRAN-FH.CUS.0-v02.00, published July 27, 2018 on www.xran.org

[0068] Further definitions and embodiments are described below.

[0069] In the above description of various embodiments of the inventive concept, it should be understood that the terminology used herein is merely for describing specific embodiments, and is not intended to limit the inventive concept. Unless otherwise specified, all terms (including technical and scientific terms) used herein have the same meaning as those commonly understood by those skilled in the art to which the inventive concept belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning according to the meaning of those terms in the context of this specification and related art, and should not be interpreted in an ideal or overly formal sense unless expressly so defined herein.

[0070] When an element is referred to as being "connected," "coupled," "responsive" to another element, or variations thereof, the element may be directly connected, coupled, or responsive to the other element, or there may be intervening elements. In contrast, when an element is referred to as being "directly connected," "directly coupled," "directly responsive" to another element, or variations thereof, there are no intervening elements. Like numbers refer to like elements throughout. Furthermore, as used herein, "coupled," "connected," "responsive," or variations thereof may include wirelessly coupled, wirelessly connected, or wirelessly responsive. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. For the sake of brevity and / or clarity, well-known functions or constructions may not be described in detail. The term "and / or" includes any and all combinations of one or more of the associated listed items.

[0071] Terms such as first, second, third, etc. may be used herein to describe various elements / operations, but it will be understood that these elements / operations should not be limited by these terms. These terms are merely used to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be called a second element / operation in other embodiments without departing from the teachings of the inventive concept. The same reference numbers or characters refer to the same or similar elements throughout this specification.

[0072] As used herein, the terms "comprise," "comprising," "comprises," "include," "including," "includes," "have," "has," "having," or variations thereof, are open-ended and include one or more stated features, integers, elements, steps, components, or functions, but do not exclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Additionally, as used herein, the common abbreviation "eg," from the Latin phrase "exempli gratia," may be used to introduce or specifically name one or more general examples of the aforementioned items, without limiting such items. The common abbreviation "ie," from the Latin phrase "id est," may be used to specifically name a particular item from a more general statement.

[0073] Exemplary embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices) and / or computer program products. It should be understood that the blocks of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by computer program instructions carried out by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general-purpose computer circuit, a special-purpose computer circuit, and / or other programmable data processing circuit to create a machine, such that the instructions executing via the processor of the computer and / or other programmable data processing apparatus transform and control transistors, values ​​stored in memory locations, and other hardware components in such circuits to implement the function / act specified in one or more blocks of the block diagrams and / or flowcharts, and thereby create means (functions) and / or structures for implementing the function / act specified in the block(s) of the block diagrams and / or flowcharts.

[0074] These computer program instructions may also be stored on a tangible computer readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored on the computer readable medium produce an article of manufacture containing instructions that implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts. Thus, embodiments of the inventive concepts may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor, such as a digital signal processor, which may be collectively referred to as a "circuit," "module," or variations thereof.

[0075] It should also be noted that in some alternative implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functions / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks, and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks shown, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Moreover, while some of the figures include arrows on communication paths to indicate a primary direction of communication, it should be understood that communication may occur in the opposite direction to the illustrated arrows.

[0076] Many variations and modifications may be made to the embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be considered as illustrative and not limiting, and the example embodiments are intended to encompass all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Thus, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of the present disclosure, including the example embodiments and their equivalents, and should not be limited or restricted by the above detailed description.

[0077] Further explanation is provided below.

[0078] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding another step, and / or it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0079] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0080] FIG. 12: A wireless network according to some embodiments.

[0081] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in FIG. 12. For simplicity, the wireless network of FIG. 12 illustrates only network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline, a service provider, or any other network node or end device. Of the components shown, network node QQ160 and wireless device (WD) QQ110 are illustrated with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or via the wireless network.

[0082] The wireless network may include and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement a communications standard, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0083] Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0084] The network nodes QQ160 and WD QQ110 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functions, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0085] A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power levels), and may then be referred to as femto, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Still further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below.More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0086] In FIG. 12, network node QQ160 includes processing circuit QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power supply QQ186, power circuit QQ187, and antenna QQ162. Although the network node QQ160 shown in the exemplary wireless network of FIG. 12 may represent a device including the shown combination of hardware components, other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, although the components of network node QQ160 are illustrated as a single box located within a larger box or nested within multiple boxes, in reality the network node may include multiple different physical components that make up a single shown component (e.g., device readable medium QQ180 may include multiple separate hard drives as well as multiple RAM modules).

[0087] Similarly, the network node QQ160 may be assembled from multiple physically separate components (e.g., Node B and RNC components, or BTS and BSC components, etc.), each of which may have their own respective components. In some scenarios in which the network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some cases. In some embodiments, the network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media QQ180 for different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various shown components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into network node QQ160. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within network node QQ160.

[0088] The processing circuit QQ170 is configured to perform any decision, calculation, or similar operation (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit QQ170 may include processing information acquired by the processing circuit QQ170, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0089] The processing circuit QQ170 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide network node QQ160 functionality, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180. For example, the processing circuit QQ170 may execute instructions stored on the device readable medium QQ180 or instructions stored in a memory within the processing circuit QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit QQ170 may include a system on a chip (SOC).

[0090] In some embodiments, the processing circuit QQ170 may include one or more of a radio frequency (RF) transceiver circuit QQ172 and a baseband processing circuit QQ174. In some embodiments, the radio frequency (RF) transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on the same chip or set of chips, board, or unit.

[0091] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be implemented by the processing circuit QQ170 executing instructions stored in a device-readable medium QQ180, or in a memory within the processing circuit QQ170. In alternative embodiments, some or all of the functionality may be provided by the processing circuit QQ170 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuit QQ170 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuit QQ170 alone, or by other components of the network node QQ160, but by the network node QQ160 as a whole, and / or by end users and wireless networks in general.

[0092] The device-readable medium QQ180 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit QQ170. The device-readable medium QQ180 may store any suitable instructions, data, or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit QQ170 and utilized by the network node QQ160. The device-readable medium QQ180 may be used to store calculations performed by the processing circuit QQ170 and / or data received via the interface QQ190. In some embodiments, the processing circuit QQ170 and the device-readable medium QQ180 may be considered to be integrated.

[0093] The interface QQ190 is used in wired or wireless communication of signaling and / or data between the network node QQ160, the network QQ106, and / or the WD QQ110. As shown, the interface QQ190 comprises a port(s) / terminal(s) QQ194 for sending and receiving data to and from the network QQ106, for example over a wired connection. The interface QQ190 also includes a radio front-end circuit QQ192, which is coupled to the antenna QQ162 or, in some embodiments, may be part of the antenna QQ162. The radio front-end circuit QQ192 comprises a filter QQ198 and an amplifier QQ196. The radio front-end circuit QQ192 may be connected to the antenna QQ162 and the processing circuit QQ170. The radio front-end circuit may be configured to condition the signal communicated between the antenna QQ162 and the processing circuit QQ170. The wireless front-end circuit QQ192 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The wireless front-end circuit QQ192 may convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of a filter QQ198 and / or an amplifier QQ196. The wireless signal may then be transmitted via the antenna QQ162. Similarly, when receiving data, the antenna QQ162 may collect the wireless signal, which is then converted to digital data by the wireless front-end circuit QQ192. The digital data may be passed to the processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

[0094] In some alternative embodiments, the network node QQ160 may not include a separate radio front-end circuit QQ192, and instead the processing circuit QQ170 may include a radio front-end circuit and may be connected to the antenna QQ162 without a separate radio front-end circuit QQ192. Similarly, in some embodiments, all or a portion of the RF transceiver circuit QQ172 may be considered part of the interface QQ190. In still other embodiments, the interface QQ190 may include one or more ports or terminals QQ194, the radio front-end circuit QQ192, and the RF transceiver circuit QQ172 as part of a radio unit (not shown), and the interface QQ190 may communicate with a baseband processing circuit QQ174 that is part of a digital unit (not shown).

[0095] Antenna QQ162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna QQ162 may be coupled to radio front-end circuit QQ190 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices within a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

[0096] The antenna QQ162, the interface QQ190, and / or the processing circuit QQ170 may be configured to perform any receiving operation and / or some acquisition operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna QQ162, the interface QQ190, and / or the processing circuit QQ170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0097] The power circuit QQ187 may comprise or be coupled to a power management circuit and is configured to supply power to the components of the network node QQ160 for performing the functions described herein. The power circuit QQ187 may receive power from the power source QQ186. The power source QQ186 and / or the power circuit QQ187 may be configured to provide power to the various components of the network node QQ160 in a form suitable for the respective components (e.g., at the voltage and current levels required for each respective component). The power source QQ186 may either be included in the power circuit QQ187 and / or the network node QQ160 or be external to the power circuit QQ187 and / or the network node QQ160. For example, the network node QQ160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuit QQ187. As a further example, the power source QQ186 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit QQ187. The battery may provide backup power in the event that the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0098] Alternative embodiments of network node QQ160 may include additional components other than those shown in FIG. 12 that may be responsible for providing some aspects of the functionality of the network node, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface devices to enable input of information into network node QQ160 and output of information from network node QQ160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

[0099] A wireless device (WD) as used herein refers to a device capable of, configured to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predefined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node. The WD may in this case be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context.As one particular example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status or other functions related to its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0100] As shown, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuit QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power supply QQ136, and power circuit QQ137. WD QQ110 may include multiple sets of one or more of the shown components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chips or sets of chips as other components in WD QQ110.

[0101] The antenna QQ111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to the interface QQ114. In some alternative embodiments, the antenna QQ111 may be separate from the WD QQ110 and connectable to the WD QQ110 through an interface or port. The antenna QQ111, the interface QQ114, and / or the processing circuit QQ120 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuit and / or the antenna QQ111 may be considered an interface.

[0102] As shown, the interface QQ114 comprises a radio front-end circuit QQ112 and an antenna QQ111. The radio front-end circuit QQ112 comprises one or more filters QQ118 and an amplifier QQ116. The radio front-end circuit QQ114 is connected to the antenna QQ111 and the processing circuit QQ120 and is configured to condition signals communicated between the antenna QQ111 and the processing circuit QQ120. The radio front-end circuit QQ112 may be coupled to the antenna QQ111 or may be part of the antenna QQ111. In some embodiments, the WD QQ110 may not include a separate radio front-end circuit QQ112, rather the processing circuit QQ120 may comprise a radio front-end circuit and be connected to the antenna QQ111. Similarly, in some embodiments, some or all of the RF transceiver circuit QQ122 may be considered part of the interface QQ114. The radio front-end circuit QQ112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit QQ112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of a filter QQ118 and / or an amplifier QQ116. The radio signal may then be transmitted via the antenna QQ111. Similarly, when receiving data, the antenna QQ111 may collect the radio signal, which is then converted to digital data by the radio front-end circuit QQ112. The digital data may be passed to the processing circuit QQ120. In other embodiments, the interface may include different components and / or different combinations of components.

[0103] The processing circuitry QQ120 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide WD QQ110 functionality, either alone or in conjunction with other WD QQ110 components such as device readable medium QQ130. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuitry QQ120 may execute instructions stored in the device readable medium QQ130 or in memory within the processing circuitry QQ120 to provide the functionality disclosed herein.

[0104] As shown, the processing circuit QQ120 includes one or more of the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuit QQ120 of the WD QQ110 may comprise a SOC. In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined into one chip or set of chips, and the RF transceiver circuit QQ122 may be on a separate chip or set of chips. In further alternative embodiments, some or all of the RF transceiver circuitry QQ122 and the baseband processing circuitry QQ124 may be on the same chip or set of chips, and the application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry QQ122, the baseband processing circuitry QQ124, and the application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry QQ122 may be part of the interface QQ114. The RF transceiver circuitry QQ122 may condition the RF signal for the processing circuitry QQ120.

[0105] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry QQ120 executing instructions stored in a device-readable medium QQ130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry QQ120 without executing instructions stored in a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuitry QQ120 may be configured to perform the described functionality, regardless of whether it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry QQ120 alone or by other components of the WD QQ110, but by the WD QQ110 as a whole, and / or by end users and wireless networks in general.

[0106] The processing circuit QQ120 may be configured to perform any of the decision, calculation, or similar operations (e.g., some acquisition operations) described herein as being performed by the WD. These operations as performed by the processing circuit QQ120 may include processing information acquired by the processing circuit QQ120, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored by the WD QQ110, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0107] The device-readable medium QQ130 may be operable to store applications, including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit QQ120. The device-readable medium QQ130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit QQ120. In some embodiments, the processing circuit QQ120 and the device-readable medium QQ130 may be considered to be integrated. The user interface device QQ132 may provide components that allow a human user to interact with the WD QQ110. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface device QQ132 may be operable to generate output to a user and to allow the user to provide input to the WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in the WD QQ110. For example, if the WD QQ110 is a smartphone, the interaction may be through a touch screen, and if the WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device QQ132 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device QQ132 is configured to allow input of information to the WD QQ110 and is connected to the processing circuit QQ120 to allow the processing circuit QQ120 to process the input information.The user interface device QQ132 may include, for example, a microphone, proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device QQ132 is also configured to enable the output of information from the WD QQ110 and to enable the processing circuitry QQ120 to output information from the WD QQ110. The user interface device QQ132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device QQ132, the WD QQ110 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functionality described herein.

[0108] The auxiliary device QQ134 is operable to provide more specific functions that may not generally be implemented by the WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device QQ134 may vary depending on the embodiment and / or scenario.

[0109] The power source QQ136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD QQ110 may further comprise a power circuit QQ137 for delivering power from the power source QQ136 to various parts of the WD QQ110 that require power from the power source QQ136 to perform any function described or indicated herein. The power circuit QQ137 may comprise a power management circuit in some embodiments. The power circuit QQ137 may additionally or alternatively be operable to receive power from an external power source, in which case the WD QQ110 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit QQ137 may also be operable in some embodiments to deliver power from the external power source to the power source QQ136. This may be, for example, for charging the power source QQ136. Power circuit QQ137 may perform any formatting, conversion, or other modification on the power from power source QQ136 to make the power suitable for the respective components of the WD QQ110 that it powers.

[0110] FIG. 13: User equipment according to some embodiments.

[0111] FIG. 13 illustrates an embodiment of a UE according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UE, Machine Type Communication (MTC) UE, and / or enhanced MTC (eMTC) UE. The UE QQ200 shown in Figure 13 is an example of a WD configured for communication according to one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 13 is a UE, the components described herein are equally applicable to a WD and vice versa.

[0112] In FIG. 13, UE QQ200 includes a processing circuit QQ201 operatively coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, a network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read only memory (ROM) QQ219, storage medium QQ221, etc., a communication subsystem QQ231, a power source QQ233, and / or other components, or any combination thereof. Storage medium QQ221 includes an operating system QQ223, application programs QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 13 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0113] In FIG. 13, the processing circuit QQ201 may be configured to process computer instructions and data. The processing circuit QQ201 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit QQ201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0114] In the illustrated embodiment, the input / output interface QQ205 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE QQ200 may be configured to use an output device via the input / output interface QQ205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE QQ200 may be configured to use an input device via the input / output interface QQ205 to allow a user to capture information on the UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0115] In FIG. 13, the RF interface QQ209 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface QQ211 may be configured to provide a communication interface to the network QQ243a. The network QQ243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network QQ243a may comprise a Wi-Fi network. The network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface QQ211 may implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or may alternatively be implemented separately.

[0116] The RAM QQ217 may be configured to interface to the processing circuit QQ201 via the bus QQ202 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. The ROM QQ219 may be configured to provide computer instructions or data to the processing circuit QQ201. For example, the ROM QQ219 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium QQ221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, storage medium QQ221 may be configured to include an operating system QQ223, an application program QQ225, such as a web browser application, a widget or gadget engine, or another application, and data files QQ227. Storage medium QQ221 may store any of a variety of different operating systems or combinations of operating systems for use by UE QQ200.

[0117] The storage medium QQ221 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium QQ221 may enable the UE QQ200 to access, offload data, or upload data to computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium. An article of manufacture, such as an article of manufacture utilizing the communication system, may be tangibly embodied in storage medium QQ221, which may comprise a device-readable medium.

[0118] In FIG. 13, the processing circuit QQ201 may be configured to communicate with the network QQ243b using the communication subsystem QQ231. The networks QQ243a and QQ243b may be the same network or networks or different networks or networks. The communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with the network QQ243b. For example, the communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter QQ233 and / or a receiver QQ235 for respectively implementing a transmitter function or a receiver function appropriate for a RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0119] In the illustrated embodiment, the communication capabilities of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE QQ200.

[0120] The features, benefits and / or functions described herein may be implemented in one of the components of the UE QQ200 or split across multiple components of the UE QQ200. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem QQ231 may be configured to include any of the components described herein. Furthermore, the processing circuit QQ201 may be configured to communicate with any of such components over the bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit QQ201, perform the corresponding functions described herein. In another example, the functions of any of such components may be split between the processing circuit QQ201 and the communication subsystem QQ231. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0121] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments.

[0122] The term unit may have its conventional meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.

[0123] Many different embodiments have been disclosed herein with reference to the above description and drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and unclear. Thus, all embodiments may be combined in any manner and / or combination, and the present specification, including the drawings, is intended to constitute a complete written description of every combination and subcombination of the embodiments described herein and of the manner and process of making and using them, and to support claims to any such combination or subcombination.

[0124] In the drawings and specification, exemplary embodiments of the inventive concept are disclosed and specific terms are employed, but they are used in a generic and descriptive sense only and not for purposes of limitation; the scope of the inventive concept is set forth in the following claims.

Claims

1. 1. A method for transmitting data between units in a network node of a wireless communication system, the method comprising the steps of: generating, in a first unit of the network node, mapped data by mapping a plurality of reference symbols transmitted by the first unit onto a plurality of resource elements; compressing, in the first unit, user data including data samples corresponding to the plurality of reference symbols based on a bitmap representation of the mapped data to generate compressed data; transmitting the bitmap representation and the compressed data from the first unit to a second unit; Including, the bitmap representation indicates that a first resource element included in the plurality of resource elements carries a zero; compressing the user data includes determining, based on the bitmap representation, that a first data sample corresponding to the first resource element should not be transmitted to the second unit; the compressed data does not include the first data sample; method.

2. transmitting an indication from the first unit to the second unit that the user data is compressed, the indication causing the second unit to decompress the compressed data prior to transmitting the user data to a UE; The method of claim 1 further comprising:

3. The method of claim 1, wherein compressing the user data includes eliminating data samples that belong to the first resource element.

4. The method of claim 1 , wherein the user data includes pre-compressed user data, and wherein compressing the user data is performed on top of the pre-compressed user data.

5. The method of claim 1 , wherein the first unit comprises a lower layer split central unit (LLS-CU) and the second unit comprises a radio unit (RU).

6. 2. The method of claim 1, wherein the bitmap representation is transmitted from the first unit to the second unit in a first message and the compressed data is transmitted from the first unit to the second unit in a second message.

7. The method of claim 1 , wherein the bitmap representation and the compressed data are transmitted from the first unit to the second unit in the same message.

8. A computer-readable storage medium comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 7.

9. A processor circuit; a transceiver coupled to the processor circuit; a memory coupled to the processor circuit; 8. A network node comprising: said memory comprising machine-readable computer program instructions which, when executed by said processor circuitry, cause said processor circuitry to perform a method according to any one of claims 1 to 7. Network node.

Citation Information

Patent Citations

  • Distributed wireless communication base station system and communication method

    JP2015142189A

  • Method and system for managing user information

    WO2018166326A1