WO2020167236A1 - Gestion de couverture et de capacité - Google Patents

Gestion de couverture et de capacité Download PDF

Info

Publication number
WO2020167236A1
WO2020167236A1 PCT/SE2020/050164 SE2020050164W WO2020167236A1 WO 2020167236 A1 WO2020167236 A1 WO 2020167236A1 SE 2020050164 W SE2020050164 W SE 2020050164W WO 2020167236 A1 WO2020167236 A1 WO 2020167236A1
Authority
WO
WIPO (PCT)
Prior art keywords
coverage
per
information
cell
rach
Prior art date
Application number
PCT/SE2020/050164
Other languages
English (en)
Inventor
Angelo Centonza
Icaro L. J. Da Silva
Pradeepa Ramachandra
Malik Wahaj ARSHAD
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020167236A1 publication Critical patent/WO2020167236A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for management of coverage and capacity.
  • FIGURE 1 illustrates the 5G Radio Access Network (RAN) architecture as described in 3GPP TS 38.401 v. 15.4.0.
  • the Next Generation-RAN consists of a set of gNodeBs (gNBs) connected to the 5G Core (5GC) through the Next Generation interface (NG).
  • An gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual mode operation.
  • gNBs can be interconnected through the Xn interface.
  • a gNB may consist of a gNB Central Unit (gNB-CU) and gNB Distributed Units (gNB-DUs).
  • a gNB- CU and a gNB-DU are connected via FI logical interface.
  • NG, Xn and FI are logical interfaces.
  • the NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture which includes the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, FI the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signalling transport.
  • a gNB may also be connected to an LTE eNB via the X2 interface.
  • Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB.
  • the latter is a gNB not connected directly to a CN and connected via X2 to an eNB for the sole purpose of performing dual connectivity.
  • the architecture in FIGURE 1 can be expanded by splitting the gNB-CU into two entities.
  • one gNB-CU-UP serves the user plane and hosts the Packet Data Convergence Protocol (PDCP) protocol and the other gNB-CU-CP serves the control plane and hosts the PDCP and Radio Resource Control (RRC) protocol.
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical layer
  • Optimization of the Radio Access Channel (RACH) configuration in cells is a Release 9 Self Optimized Network (SON) feature that is key to optimizing the system performance of a mobile network.
  • SON Release 9 Self Optimized Network
  • a poorly configured RACH may result in higher call setup and handover delays due to frequent RACH collisions, or low preamble-detection probability and limited coverage.
  • the amount of uplink resource reserved for RACH also affects the system capacity. Therefore, a network operator should carefully monitor that the RACH parameters are appropriately set, considering factors such as the RACH load, the uplink interference, the traffic patterns and the population under the cell coverage. The task becomes more complicated given that these factors may change dynamically. For example, if the antenna tilt is changed in a cell, it will affect the rates of call arrival and handover in this cell and the surrounding cells, and therefore the RACH load per preamble in all those cells. A change in transmission power settings or handover thresholds may have similar effects.
  • the RACH self-optimization feature should automatically make appropriate measurements of the RACH performance and usage in all the affected cells and determine any necessary updates of the RACH parameters. Some useful measurements are UE reports of the number of RACH attempts needed to obtain access, or time elapsed from the first attempt until access is finally granted.
  • RACH parameters that can then be adjusted are typically the following:
  • the RACH optimization feature facilitates automatic configuration of Physical Random Access Channel (PRACH) parameters (including the PRACH resource configuration, preamble root sequence and cyclic shift configuration) to avoid preamble collisions with neighbouring cells.
  • PRACH Physical Random Access Channel
  • PCI Physical Cell Identifier
  • the PRACH configuration information is included in the‘X2 Setup’ and‘eNB Configuration Update’ procedures. Therefore, whenever a new eNodeB is initialized and learns about its neighbours via the Automatic Neighbor Relation (ANR) function, it can at the same time learn the neighbouring PRACH configurations. It can then select its own PRACH configuration to avoid conflicts with the neighbouring ones.
  • ANR Automatic Neighbor Relation
  • the report of RACH information when random access procedure is performed may be requested by the network via the UE Information procedure in RRC in the case where a RACH procedure was successful.
  • the procedure for requesting a report of RACH information is depicted in FIGURE 2 and is discussed in RRC specification in Section 5.6.5 of 3GPP TS36.331 as follows:
  • the UE information procedure is used by E-UTRAN to request the UE to report information.
  • E-UTRAN initiates the procedure by sending the UEInformationRequest message. E-UTRAN should initiate this procedure only after successful security activation.
  • the UE Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
  • the UEInformationRequest is the command used by E-UTRAN to retrieve information from the UE.
  • the UEInformationResponse message is used by the UE to transfer the information requested by the E-UTRAN.
  • Signalling radio bearer SRB1 or SRB2 (when logged measurement information is included)
  • the UE stores the number of preambles sent, which corresponds to the parameter PREAMBLE TRANSMISSION COUNTER in MAC specifications.
  • the UE sends a preamble and waits for a random-access response (RAR) during a pre-configured time window (RAR window). If the RAR does not come within that time, the UE shall adjust some preamble transmission parameters (e.g. transmission power) and transmit it again (in what is called power ramping adjustment). If the procedure is successful, at the n-th transmission, the preamble will be responded.
  • the number n is what would be provided in the RACH report, so the network knows how many times the UE needed to ramp the power before the procedure was successful.
  • the UE shall set the preamble received target power, which may include the expected power in the RACH receiver at the eNB, to the initial transmission power, which may be a parameter provided by the eNB via SIB2 in LTE, for example.
  • the preamble received target power which may include the expected power in the RACH receiver at the eNB
  • the initial transmission power which may be a parameter provided by the eNB via SIB2 in LTE, for example.
  • These values may range from -120dBm to -90dBm and are provided as part of the Power Ramping Parameters. Note that this may also be a parameter to be optimized later. For example, a too large value may lead to a high RACH success rate, but it could also create unnecessary UL interference, problematic especially in high load scenarios.
  • the PREAMBLE RECEIVED TARGET POWER will be the preamblelnitialReceivedTargetPower + DELTA PREAMBLE.
  • the DELTA PREAMBLE is an offset depending on the preamble format that has been configured by the network in prach-Configlndex, ranging from -3dB to 8 dB.
  • PREAMBLE TRAN SMIS SION C OUNTER is incremented by 1. Then, it is checked if the number of increments has reached its maximum value or not. Additionally, a configurable parameter could be optimized.
  • PREAMBLE RECEIVED TARGET POWER preamblelnitialReceivedTargetPower +
  • DELTA PRE AMBLE + 1 * powerRampingStep The parameter powerRampingStep may be 0 dB, 2 dB, 4 dB or 6 dB. Power ramping parameters as broadcasted in SIB2 as shown below:
  • PREAMBLE RECEIVED TARGET POWER preamblelnitialReceivedTargetPower +
  • the preamble power ramping procedure in case of multiple preamble transmission attempts, as described in the MAC specifications (3GPP TS 36.321) is shown below:
  • the Random Access procedure shall be performed as follows:
  • the random-access procedure shall be performed as follows:
  • the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: else: instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and
  • the MAC entity may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted Random Access Preamble. if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see subclause 5.1.3), the MAC entity shall:
  • the ra-Preamblelndex was explicitly signalled and it was not 000000 and ra-CFRA- Config is not configured:
  • Random Access Response reception is considered not successful and the MAC entity shall: if the notification of power ramping suspension has not been received from lower layers:
  • preambleTransMax + 1
  • Random access procedure is described in the NR MAC specifications and parameters are configured by RRC in, for example, system information or handover (RRCReconfiguration with reconfigurationWithSync). Random access is triggered in many different scenarios such as, for example, when the UE is in RRC IDLE or RRC INACTIVE and wants to access a cell that is camping on (i.e. transition to RRC CONNECTED).
  • RACH configuration is broadcasted in System Information Block-Format 1 (SIB1), as part of the servingCellConfigCommon (with both downlink (DL) and uplink (UL) configurations), where the RACH configuration is within the uplinkConfigCommon.
  • SIB1 System Information Block-Format 1
  • the exact RACH parameters are within what is called initialUplinkBWP , since this is the part of the UL frequency the UE shall access and search for RACH resources.
  • preambleTransMax ENUMERATED (n3, n4, n5, n6, n7, n8, nlO, n20, n50, nlOO, n200 ⁇ ,
  • the RACH report to assist the network to perform RACH optimization contains the number of preamble transmissions until the procedure succeeds. It is also very clear what has happened at the UE between the first transmission and the last transmission until the procedure was considered successful: the UE applied power ramping with a configured step and transmitted the preamble once more.
  • PREAMBLE TRANSMISSION COUNTER assists the UE to perform power ramping, which is sort of RACH state variable. And, as in LTE, during initialization, that counter is set to 1, so that the initial transmission power for the selected preamble is
  • PREAMBLE RECEIVED TARGET POWER preambleReceivedTargetPower + DELTA PREAMBLE. This is just like in LTE, where in the first attempt the transmission power is just the initial transmission power configured by the network + a specified offset which depends on the selected preamble.
  • PREAMBLE TRANSMISSION COUNTER is incremented by 1. Then, it is checked if the number of increments has reached its maximum value or not (also a configurable parameter that could be optimized).
  • a cell in NR is basically defined by a set of these SSBs that may be transmitted in 1 (typical implementation for lower frequencies e.g. below 6GHz) or multiple downlink beams (typical implementation for lower frequencies e.g. below 6GHz).
  • these SSBs carry the same physical cell identifier (PCI) and a MIB.
  • PCI physical cell identifier
  • each of these beams may transmit its own SSB which may be distinguished by an SSB index.
  • RACH-ConfigCommon The mapping between RACH resources and SSBs (or CSI-RS) is also provided as part of the RACH configuration (in RACH-ConfigCommon). Two parameters are relevant here: - #SSBs-per-PRACH-occasion: 1/8, 1 ⁇ 4, 1 ⁇ 2, 1, 2, 8 or 16, which represents the number of SSBs per RACH occasion;
  • FIGURE 3 illustrates an example of different NR structures. Specifically, as shown, if the number of SSBs per RACH occasion is 1, and if the UE is under the coverage of a specific SSB such as, for example, SSB index 2, there will be a RACH occasion for that SSB index 2. If the UE moves and is now under the coverage of another specific SSB such as, for example, SSB index 5, there will be another RACH occasion for that SSB index 5. Thus, each SSB detected by a given UE would have its own RACH occasion.
  • a specific SSB such as, for example, SSB index 2
  • another specific SSB such as, for example, SSB index 5
  • each SSB detected by a given UE would have its own RACH occasion.
  • the network upon detecting a preamble in a particular RACH occasion the network knows exactly which SSB the UE has selected and, consequently, which downlink beam is covering the UE so that the network can continue the downlink transmission (e.g. RAR, etc).
  • the factor 1 is an indication that each SSB has its own RACH resource i.e., a preamble detected there indicates to the network which SSB the UE has selection i.e. which DL beam the network should use to communicate with the UE, such as the one to send the RAR.
  • FIGURE 4 illustrates preamble mapping to different RACH occasions. Note that each SS-block typically maps to multiple preambles (different cyclic shifts and Zadoff-Chu roots) within a PRACH occasion so that it is possible to multiplex different UEs in the same RACH occasions since they may be under the coverage of the same SSB.
  • FIGURE 5 illustrates preamble mapping to a same RACH occasion.
  • the number of SSBs per RACH occasion is 2.
  • a preamble received in that RACH occasion indicated to the network that one of the two beams are being selected by the UE.
  • the network has means via implementation to distinguish these two beams and/or should perform a beam sweeping in the downlink by transmitting the RAR in both beams, either simultaneously or, transmitting in one, waiting for a response from the UE, and if absent, transmit in the other.
  • the UE has selected an SSB (based on measurements performed in that cell), it has transmitted with initial power a selected preamble associated to the PRACH resource mapped to the selected SSB, and it has not received a RAR within the RAR time window. According to the specifications, the UE may still perform preamble re-transmission if a maximum number of allowed transmissions has not been reached. As in LTE, at every preamble retransmission attempt, the UE may assume the same SSB as the previous attempt and perform power ramping similar to LTE. A maximum number of attempts is also defined in NR, which is also controlled by the parameter PRE AMBLE TRAN SMIS SION COUNTER.
  • the UE may alternatively select a different SSB, as long as that new SSB has an acceptable quality such as where, for example, its measurements are above a configurable threshold.
  • the UE does not perform power ramping, but transmits the preamble with the same previously transmitted power.
  • the UE shall not re-initiate the power to the initial power transmission.
  • FIGURES 6A, 6B, and 6C illustrate an example of RACH access to different beam RACH resources.
  • PREAMBLE POWER RAMPING COUNTER a new variable defined in the NR MAC specifications (3GPP TS 38.321) called PREAMBLE POWER RAMPING COUNTER, in case the same beam is selected at a retransmission.
  • PREAMBLE TRANSMISSION COUNTER the previous LTE variable still exists (PREAMBLE TRANSMISSION COUNTER), so that the total number of attempts is still limited, regardless if the UE performs at each attempt SSB/beam re-selection or power ramping.
  • the PREAMBLE POWER RAMPING COUNTER is incremented (i.e. set to 2 in this second attempt) and the transmission power will be:
  • PREAMBLE RECEIVED TARGET POWER preambleReceivedTargetPower + DELTA PREAMBLE + UPREAMBLE POWER RAMPING STEP
  • the PREAMBLE POWER RAMPING COUNTER is not incremented (i.e. remains 1) and the transmission power will be as in the first transmission:
  • PREAMBLE RECEIVED TARGET POWER preambleReceivedTargetPower + DELTA PRE AMBLE
  • That preamble power ramping procedure in case of multiple preamble transmission attempts, is shown below as described in the MAC specifications (3GPP TS 38.321):
  • the MAC entity shall:
  • the MAC entity shall:
  • the MAC entity shall, for each Random Access Preamble:
  • the RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted is computed as:
  • RA-RNTI 1 + s_id + 14 x t_id + 14 x 80 x f id + 14 x 80 x 8 x ul_carrier_id
  • s_id is the index of the first OFDM symbol of the PRACH occasion (0 ⁇ s_id ⁇ 14)
  • t_id is the index of the first slot of the PRACH occasion in a system frame (0 ⁇ t_id ⁇ 80)
  • f id is the index of the PRACH occasion in the frequency domain (0 ⁇ f id ⁇ 8)
  • ul carrier id is the UL carrier used for Random Access Preamble
  • the MAC entity shall:
  • Random Access Response contains a MAC subPDU with Random
  • Random Access Response includes a MAC subPDU with RAPID only:
  • Random Access Response for the same group of contention-based Random Access Preambles has a different size than the first uplink grant allocated during that Random Access procedure, the UE behaviour is not defined.
  • Random Access Resources is met during the backoff time:
  • the MAC entity may stop ra-ResponseWindow (and hence monitoring for Random Access Response(s)) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted
  • the UE Upon declaring the RLF, the UE performs the re-establishment procedure. Before the standardization of MRO related report handling in the network, only the UE was aware of some statistics associated to how did the radio quality looked like at the time of RLF, what is the actual reason for declaring RLF etc. For the network to identify the reason for the RLF, the network needs more information, both from the UE and also from the neighboring base stations.
  • the RLF reporting procedure was introduced in the RRC specification in Rel-9 RAN2 work.
  • the contents of the measurement report have been enhanced with more details in the subsequent releases.
  • RLF failure cause e.g. T310 expiration, random access problems
  • the node serving the cell in which the UE reestablishes can forward the RLF report to the node hosting the last serving cell.
  • This forwarding of the RLF report is done to aid the original serving cell with tuning of the handover related parameters as the original serving cell was the one who had configured the parameters associated to the UE that led to the RLF.
  • Radio link failure indication procedure is used to transfer information regarding RRC re-establishment attempts or received RLF reports between eNBs. This message is sent from the eNB in which the UE performs reestablishment to the eNB which was the previous serving cell of the UE.
  • the contents of the RLF indication message is given below: 9.1.2.18 RLF INDICA TION
  • This message is sent by the eNB2 to indicate an RRC re-establishment attempt or a reception of an RLF Report from a UE that suffered a connection failure at eNBi.
  • the original source cell can deduce whether the RLF was caused due to a coverage hole or due to handover associated parameter configurations. If the RLF was deemed to be due to handover associated parameter configurations, the original serving cell can further classify the handover related failure as too-early, too-late or handover to wrong cell classes. These handover failure classes are explained in brief below.
  • the original serving cell can classify a handover failure to be‘too late handover’ when the original serving cell fails to send the handover command to the UE associated to a handover towards a particular target cell and if the UE reestablishes itself in this target cell post RLF.
  • An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit earlier by decreasing the CIO (cell individual offset) towards the target cell that controls when the IE sends the event triggered measurement report that leads to taking the handover decision.
  • the original serving cell can classify a handover failure to be ‘too early handover’ when the original serving cell is successful in sending the handover command to the UE associated to a handover however the UE fails to perform the random access towards this target cell.
  • An example corrective action from the original serving cell could be to initiate the handover procedure towards this target cell a bit later by increasing the CIO (cell individual offset) towards the target cell that controls when the IE sends the event triggered measurement report that leads to taking the handover decision.
  • CIO cell individual offset
  • the original serving cell can classify a handover failure to be‘handover-to- wrong-celT when the original serving cell intends to perform the handover for this UE towards a particular target cell but the UE declares the RLF and reestablishes itself in a third cell.
  • a corrective action from the original serving cell could be to initiate the measurement reporting procedure that leads to handover towards the target cell a bit later by decreasing the CIO (cell individual offset) towards the target cell or via initiating the handover towards the cell in which the UE reestablished a bit earlier by increasing the CIO towards the reestablishment cell.
  • the serving cell may further benefit from‘handover report’ message which includes the following parameters:
  • This message is sent by the eNBi to report a handover failure event or other critical mobility problem.
  • Such solutions are based on the principle that coverage can be changed by an eNB on a per cell basis and that each cell coverage configuration adopted by an eNB can be associated with an index.
  • Such index can be signaled from one eNB to another neighbor eNB via the X2 interface. Together with this index the eNB can signal information about cells that were split into two or more cells or cells that were merged into one cell.
  • the receiving node can itself signal a coverage index to the first sending node, such index identifying the cell configuration the node adopts at the time of sending the index.
  • the receiving node can send information about any of its cell configuration, e.g. if the cell was split, merged, or if the coverage of the cell changed, which is expressed via the Cell Coverage State IE.
  • the basic mobility solution in NR shares some similarities to LTE.
  • the UE may be configured by the network to perform cell measurements and report them, to assist the network to take mobility decisions.
  • the UE may be configured to perform L3 beam measurements based on different reference signals (SSBs and CSI-RSs) and report them, for each serving and triggered cells, for example, for each cell fulfilling triggering conditions for measurement report (e.g. A3 event).
  • SSBs and CSI-RSs reference signals
  • the measurement model in NR as described in 3GPP TS 38.300 states that in RRC CONNECTED, the UE measures multiple beams (at least one) of a cell and the measurements results (power values) are averaged to derive the cell quality.
  • the UE is configured to consider a subset of the detected beams. Filtering takes place at two different levels: at the physical layer to derive beam quality and then at RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for the serving cell(s) and for the non-serving cell(s). Measurement reports may contain the measurement results of the A" best beams if the UE is configured to do so by the gNB.
  • FIGURE 7 illustrates a high-level measurement model. It may be noted that K beams correspond to the measurements on SSB or CSI-RS resources configured for L3 mobility by gNB and detected by UE at L 1. As depicted in FIGURE 7 :
  • Layer 1 filtering internal layer 1 filtering of the inputs measured at point A. Exact filtering is implementation dependent. How the measurements are actually executed in the physical layer by an implementation (inputs A and Layer 1 filtering) in not constrained by the standard.
  • measurements i.e. beam specific measurements reported by layer 1 to layer 3 after layer 1 filtering.
  • Beam Consolidation/Selection beam specific measurements are consolidated to derive cell quality.
  • the behaviour of the Beam consolidation/selection is standardized and the configuration of this module is provided by RRC signalling.
  • Reporting period at B equals one measurement period at A 1 .
  • - B a measurement (i.e. cell quality) derived from beam-specific measurements reported to layer 3 after beam consolidation/selection.
  • Layer 3 filtering for cell quality filtering performed on the measurements provided at point B.
  • the behaviour of the Layer 3 filters is standardized and the configuration of the layer 3 filters is provided by RRC signalling.
  • Filtering reporting period at C equals one measurement period at B.
  • - C a measurement after processing in the layer 3 filter.
  • the reporting rate is identical to the reporting rate at point B. This measurement is used as input for one or more evaluation of reporting criteria.
  • reporting criteria checks whether actual measurement reporting is necessary at point D.
  • the evaluation can be based on more than one flow of measurements at reference point C e.g. to compare between different measurements. This is illustrated by input C and C 1 .
  • the UE shall evaluate the reporting criteria at least every time a new measurement result is reported at point C, C 1 .
  • the reporting criteria are standardized and the configuration is provided by RRC signalling (UE measurements).
  • Beam filtering filtering performed on the measurements (i.e. beam specific measurements) provided at point A 1 .
  • the behaviour of the beam filters is standardized and the configuration of the beam filters is provided by RRC signalling.
  • Filtering reporting period at E equals one measurement period at A 1 .
  • - E a measurement (i.e. beam-specific measurement) after processing in the beam filter.
  • the reporting rate is identical to the reporting rate at point A 1 . This measurement is used as input for selecting the X measurements to be reported.
  • - Beam Selection for beam reporting selects the X measurements from the measurements provided at point E.
  • the behaviour of the beam selection is standardized and the configuration of this module is provided by RRC signalling.
  • Measurement reports include the measurement identity of the associated measurement configuration that triggered the reporting;
  • the number of non-serving cells to be reported can be limited through configuration by the network; - Cells belonging to a blacklist configured by the network are not used in event evaluation and reporting, and conversely when a whitelist is configured by the network, only the cells belonging to the whitelist are used in event evaluation and reporting;
  • Beam measurements to be included in measurement reports are configured by the network (beam identifier only, measurement result and beam identifier, or no beam reporting).
  • Intra-frequency neighbour (cell) measurements and inter-frequency neighbour (cell) measurements are defined as follows:
  • SSB based intra-frequency measurement a measurement is defined as an SSB based intra-frequency measurement provided the centre frequency of the SSB of the serving cell and the centre frequency of the SSB of the neighbour cell are the same, and the subcarrier spacing of the two SSBs is also the same.
  • SSB based inter-frequency measurement a measurement is defined as an SSB based inter-frequency measurement provided the centre frequency of the SSB of the serving cell and the centre frequency of the SSB of the neighbour cell are different, or the subcarrier spacing of the two SSBs is different.
  • one measurement object corresponds to one SSB and the UE considers different SSBs as different cells.
  • a measurement is defined as a CSI-RS based intra-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbour cell configured for measurement is within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, and the subcarrier spacing of the two CSI-RS resources is the same.
  • a measurement is defined as a CSI-RS based inter-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbour cell configured for measurement is not within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, or the subcarrier spacing of the two CSI-RS resources is different.
  • a cell may be comprised by a set of beams where PSS/SSS are transmitted in different downlink beams, see FIGURE 8. Specifically, FIGURE 8 illustrates an example of beam coverage from multiple cells hosted by different nodes.
  • beam measurement information may be included in measurement reports.
  • One of the purposes of these beam reports is to enable the source node to take educated decisions in terms of ping-pong avoidance. For example, if multiple neighbour cells are reported such as, for example, in an A3 event such as a mobility event where the trigger condition is that the neighbor cell signal becomes better than the source by a certain offset, and these cells have somewhat equivalent quality/coverage (e.g. similar RSRP and/or similar RSRQ and/or similar RSRQ), criteria to decide where to handover the UE to could be the quality of reported beams. For example, network could prioritize the cells with more beams than another cell.
  • CCO Coverage and Capacity Optimization
  • the LTE solution relies on the following steps:
  • Each eNB is configured with a number of cell deployment options. Each option consists of a set of cells to be active as well as a defined coverage for each cell. Different cell deployment options are adopted to resolve issues of sub-optimal coverage/capacity, as shown in FIGURE 1. Notice that cell coverage may be defined in different manners, but a typical measure in LTE is the quality of cell-specific reference signals (CRSs) used for RRM measurements, LI reporting, channel estimation, etc.
  • CRSs cell-specific reference signals
  • Each cell deployment option corresponds to an index, so that neighbouring eNBs can exchange such index to deduce which cell deployment the neighbour node has adopted.
  • a node can learn with time what is the cell deployment associated to a given index at a neighbour node, e.g. by means of UE measurement reports.
  • Neighbouring nodes also exchange information about the cells that have been split or merged.
  • an eNB With time, and thanks to the information signalled between nodes, an eNB is able to learn which own cell deployment fits best the cell deployment index signalled by a neighbour, hence achieving coordination of coverage and capacity optimization across RAN nodes.
  • FIGURE 9 illustrates LTE AAS function enabling cell shaping for CCO.
  • an eNB l When applying the information listed in Section 3.1.4 of 3GPP TS36.423 to the scenario in FIGURE 9, an eNB l would signal to an eNB2 that for Cell 1 a new Cell Coverage State was adopted. The eNB2 would select the Cell Coverage State for Cell 2 that best matches the new configuration at the eNB 1 and the eNB2 would signal it back to the eNB 1.
  • a method performed by a first base station includes detecting an occurrence of an event.
  • the event includes a Random Access Channel (RACH) access.
  • the method further includes the first base station transmitting, to the second base station, information comprising at least one of: a per serving cell per beam reference signal measurement; per target beam per cell reference signal measurement; information relating to a failure event; and information about the RACH access.
  • RACH Random Access Channel
  • a method performed by a first base station includes receiving, from a second base station, information comprising at least one of a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about a RACH access. Based on the information, the first base station takes at least one action to adjust at least one capacity or coverage optimization parameter.
  • a first base station includes processing circuitry configured to detect an occurrence of an event.
  • the event includes a RACH access attempt performed by a wireless device during a mobility procedure from a second base station to the first base station.
  • the processing circuitry is configured to transmit, to the second base station, information comprising at least one of: a per serving cell per beam reference signal measurement, a per target beam per cell reference signal measurement, information relating to a failure event; and information about the RACH access.
  • a first base station includes processing circuitry configured to receive, from a second base station, information comprising at least one of: a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about a RACH access. Based on the information, the processing circuitry is configured to take at least one action to adjust at least one capacity or coverage optimization parameter.
  • one technical advantage may be that certain embodiments achieve a high granular representation of cell coverage at beam level.
  • another technical advantage may be that certain embodiments are able to detect coverage and capacity issues on the basis of a variety of information not only relative to failure cases but also associated to cases of successful operation.
  • Still another technical advantage may be that, when compared to prior art, the embodiments disclosed herein provide with a higher control over the level of coverage changes that can be applied to a given cell/beam and in return with a higher control over the level of coordination between nodes adopting cell coverage and capacity changes.
  • FIGURE 1 illustrates the 5G Radio Access Network (RAN) architecture as described in 3GPP TS 38.401 v. 15.4.0;
  • RAN Radio Access Network
  • FIGURE 2 illustrates a procedure for requesting a report of Random Access Channel (RACH) information
  • FIGURE 3 illustrates an example of different New Radio (NR) structures
  • FIGURE 4 illustrates preamble mapping to different RACH occasions
  • FIGURE 5 illustrates preamble mapping to a same RACH occasion
  • FIGURE 6 A, 6B, and 6C illustrate examples of RACH access to different beam RACH resources
  • FIGURE 7 illustrates a high-level measurement model
  • FIGURE 8 illustrates an example of beam coverage from multiple cells hosted by different nodes
  • FIGURE 9 illustrates LTE AAS function enabling cell shaping for Coverage and Capacity Optimization (CCO);
  • FIGURE 10 illustrates an example solution for coverage on the left and capacity on the right
  • FIGURE 11 illustrates an example of CCO measurement gathering, problem detection, and triggered correction indication
  • FIGURE 12 illustrates an example wireless network, according to certain embodiments.
  • FIGURE 13 illustrates an example network node, according to certain embodiments.
  • FIGURE 14 illustrates an example wireless device, according to certain embodiments.
  • FIGURE 15 illustrate an example user equipment, according to certain embodiments.
  • FIGURE 16 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 17 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 18 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 19 illustrates a method implemented in a communication system, according to one embodiment
  • FIGURE 20 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 21 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 22 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 23 illustrates an example method by a first base station, according to certain embodiments
  • FIGURE 24 illustrates an exemplary virtual computing device, according to certain embodiments.
  • FIGURE 25 illustrates another example method by a first base station, according to certain embodiments.
  • FIGURE 26 illustrates another exemplary virtual computing device, according to certain embodiments.
  • FIGURE 27 illustrates another example method by a first base station, according to certain embodiments.
  • FIGURE 28 illustrates another exemplary virtual computing device, according to certain embodiments.
  • FIGURE 29 illustrates another example method by a first base station, according to certain embodiments.
  • FIGURE 30 illustrates another exemplary virtual computing device, according to certain embodiments.
  • a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node.
  • network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.
  • MSR multi-standard radio
  • RNC radio network controller
  • the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • UE are target device, device to device (D2D) UE, machine type UE or EE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.
  • terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.
  • the methods are disclosed for the optimization of coverage and capacity in a network where at least one node involved in the coverage and capacity optimization supports a cell structure based on beams, as for example an New radio (NR) gNodeB (gNB).
  • NR New radio
  • gNodeB gNB
  • the methods are based on signaling mechanisms between the UE and Radio Access Network (RAN) and between different RAN nodes, by which the nodes involved in the coordination are able to exchange the following information:
  • Per serving cell/beam RS measurements This is useful to understand the signal strength of the serving RS and to check whether the serving cell coverage is sufficiently good or not.
  • Per target(s) beam/cell RS measurement This is useful understand the signal strength of neighbour cells/beams, which are potential mobility targets. With this information, it is possible to understand if the coverage of serving cell and that of neighbour cells have excessive/sufficient/insufficient overlap. For example, it helps deducing if DL coverage holes are in place.
  • This information is evidence of either wrong mobility setting or of coverage issues.
  • the information consists of the following per beam information (where the source or target cell do not have a beam structure cell, the information is collected on a per cell basis):
  • the CCO function should correlate this information with other UE measurements to understand whether the failure is symptom of sub-optimal coverage planning, in which case a CCO action is needed, or if the failure is purely the symptom of sub- optimal mobility setting, in which case CCO should not react and leave functions like MRO to react instead.
  • the RAN configures the UE to start RACH access for a given beam starting from a pre-set transmission power level and ramping up such power at every step, in a pre-set way.
  • the CCO function also knows the transmission power used by the UE per attempt and deduces potential UL coverage issues in case RACH does not succeed
  • the CCO function at the RAN is also able to correlate this information with the resources utilized to serve cell edge UEs.
  • the CCO function is therefore able to deliberate whether there is a need for cell/beam border change in order to ease the situation of capacity utilization and interference arising from UEs being served at cell/beam edge.
  • the RAN is able to control the timing advance setting for the transmission of each UE and depending on the distance of such UE from the receiving point.
  • Information on UE timing advance settings are useful to deduce the location of a UE within a cell/beam. This information could enable the CCO function to deduce the geographical position of a UE with respect to its radio conditions. For example, a UE may be rather close to the cell transmission point, which can be deduced by its timing advance, but its DL RS measured signal may be low. This is symptom of a strong signal fading effect cause by obstacles between UE and RAN reception point.
  • the RAN could react to this by e.g. using low frequency beams (with higher penetration) for such problem.
  • FIGURE 10 illustrates an example solution for coverage on the left and capacity on the right.
  • the methods foresee signaling between different nodes of the network where such signalling is aimed at coordinating the changes in coverage and capacity applied by neighbouring nodes and therefore harmonizing cell coverage.
  • FIGURE 11 An example of the actions that can be taken by nodes within the RAN is shown in FIGURE 11, which illustrates an example of Coverage and Capacity Optimization (COO) measurement gathering, problem detection, and triggered correction indication.
  • COO Coverage and Capacity Optimization
  • FIGURE 11 signaling between a gNB-CU and a gNB-DU is represented. However, it is assumed that similar signaling can be in place when communication is between two RAN nodes, such as two gNBs or a gNB and an eNB.
  • gNB-DUs could signal directly between each other and via their connected gNB-CU indications of detected coverage and capacity issues, indications of applied changes to their beam configuration and indications of suggested changes to the beam configuration of the neighbor gNB-DU.
  • two RAN nodes may be involved in detecting and resolving coverage and capacity issues attributed to sub-optimal cell deployment.
  • Such RAN nodes may support any RAT.
  • it is assumed that such RAN nodes are two gNBs supporting NR cells.
  • each RAN node may signal to the neighbor RAN node the following information, upon the listed associated events:
  • the second node For each UE RACH access deriving from a mobility procedure from a first node cell to a second node cell, the second node should report to the first node the RACH access information listed in section 4.
  • the first node receiving such information is able to deduce the following: a. Level of DL coverage of selected mobility target beam and whether they reveal coverage issues
  • the first node may take actions to modify its cell/beam coverage so to resolve the problems identified. Such action may be taken in isolation, i.e. within the RAN node and without affecting the coverage or configuration of any other RAN nodes.
  • the gNB-CU of the first RAN node which detected the coverage issue, may signal the gNB-DU of the first RAN node an indication of the problem detected and/or an indication of how to modify its configuration, i.e. how to modify the coverage of served cells/beams. With such signaling the gNB-CU may:
  • the gNB-DU may signal that a DL or UL coverage issue has been identified in the area neighbouring one or more source or target node beams.
  • the gNB- DU may simply take this indication into account and attempt to resolve the issue by its own implementation
  • the gNB-CU may signal to the gNB-DU the DL RS measurements at target beam, the number of RACH access attempts performed by the UE before succeeding in accessing the target beam, optionally including information that allow the source node to deduce the RACH access transmission power of the UE.
  • the gNB-CU may also signal the nature of the issue identified, e.g.“coverage issue in beam x neighbourhood”. With the latter information the gNB-DU may be able to resolve the issue identified by its own means.
  • the gNB-CU may also signal to the gNB-DU possible changes in the beam/cell configuration that it is believed are needed to address the detected problem.
  • Such information may include signaling modification in beam direction, Azimuth, transmission power, beam width.
  • the gNB-DU may have signaled the gNB-CU, e.g. before taking any action to optimize its beam/cell configuration, with information about the its capability to extend/contract its beam/cell coverage.
  • the gNB-DU may signal for example, to the gNB-CU that for a give set of beams (or in a given coverage area, e.g. defined by beam/sector direction (the angle of the direction the beam/sector is pointing at), beam/sector width, beam/sector Azimuth) coverage could be extended by a given amount, e.g. quantifiable in dBs.
  • the gNB-DU may also signal information about its antenna system utilization, which may allow the gNB-CU deduce how many more beams or how much more coverage extension may be achieved by the gNBN- DU. Such utilization may be expressed in terms, for example, of antenna array utilization, or in terms of transmission power used versus maximum transmission power.
  • the first node should, together with performing the gNB-CU to gNB-DU communication required to apply changes to its own configuration, signal the second node over an interconnecting interface (either a direct or an indirect interface) such as the X2, Xn, or the NG interface with indications of the problem detected and possibly of the measures to be taken to resolve the problem in a way that is coordinated with the actions of the first node.
  • an interconnecting interface either a direct or an indirect interface
  • Signalling from the first node to the second node may contain information equivalent to those described above for signaling from the gNB-CU to the gNB- DU.
  • the first node may signal to the second node an indication of how the first node has modified its cell/beam configuration. For example one or more of the following indications may be provided from first node to second node:
  • o Indication of coverage change for one or more specific beams (identified by beam IDs).
  • Such indication could be detailed, i.e. made of parameters that characterize in full the new beams configuration, such as beam direction, Azimuth, transmission power, beam width or of could be qualitative such as an indication of coverage expansion/contraction for one or more beams.
  • Indexed configuration namely the first node provides to the second node an index that is mapped to a specific beams configuration.
  • Such index mapping to the relevant beam configuration may either be known by the second node or it may be deduced with time, by means of collection of EU measurements and data revealing the neighbor relations between cells/beams of the second node and cells/beams of the first node. After such period of “training” the second node would know the cell/beam configuration the first node would adopt when a specific configuration index is signalled.
  • the second node receiving an indication from the first node of the change in cell/beam configuration applied could itself decide to apply a change in its configuration that matches the change in the first node. I.e. such second node change should be aimed at producing a coordinated coverage, without coverage wholes, excesses of cell/beam overlaps etc.
  • similar information structures to those described above can be used.
  • the gNB-CU For each RACH access (related or not to a mobility procedure) and with respect to a gNB-CU to gNB-DU communication, the gNB-CU is able to deduce the following:
  • This particular case could detect two types of coverage issue.
  • One is related to suboptimal coverage between first and second node.
  • the signaling mechanisms described above can be adopted to bring coverage to optimal configurations.
  • the second case is one of disparity between coverage in UL and in DL.
  • the detecting node may take a number of actions such as:
  • o Trigger a coverage coordination action with a neighbor RAN node, in order to reduce the DL coverage of the beam/cell for which the disparity was detected and in turn extend the coverage of neighbor cells/beams, to cover the problematic areas
  • a mobility failure could be due to the fact that there is a coverage gap between source and target cell/beam. This would be revealed by source and target beam measurements. This could be corroborated by the information on RACH access the source node would receive from the second node as described above. Further, if the UE re-established to a new beam after having failed mobility due to suboptimal coverage, measurements on the RS of the reestablishment beam could reveal that such beam is the one that should be extended to cover for the coverage hole.
  • a first node may realize the presence of a high density hot spot of UEs near cell/beam edge. Such case could strongly impact capacity due to the high about of resources needed to serve such UEs at cell/beam edge.
  • timing advance measurements may be used to derive the position of UEs with respect to the cell reception point.
  • the first node may decide to change its cell/beam configuration so to either extend its coverage and move cell/beam edge away from the UEs, or to restrict its coverage and allow neighbor cells/beams to serve the UEs, still moving cell/beam edge away from them.
  • new measurements from the UE could be introduced to get the feedback associated to changes in a beam’s coverage.
  • the UE could be instructed to include periodic RRM measurements only when the UE is in the coverage of a beam or when this beam is the strongest beam amongst the beams measured by the UE etc.
  • the network (CU via RRC or DU via MAC/PHY signals) could invoke one of such embodiments when it has changed the beamforming configuration of either the beam that the UE is asked to monitor or to see the impact of changes of another beam on the coverage of this beam.
  • a list of beams could be configured instead of a single beam as part of such reporting from the UE.
  • network could use beam level event triggered reporting.
  • beam level event triggered reporting network could configure beam specific offsets associated to the said beam level measurements. For example, an A2 event configured based on the beam level measurements could tell the UE to trigger the measurement report only when that beam level measurement is below‘X’ dBm.
  • network could configure a set of beamWhiteList or beamBlackList to control the beam level reporting as part of cell level reports required from the UE.
  • FIGURE 12 illustrates a wireless network, in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIGURE 12.
  • the wireless network of FIGURE 12 only depicts network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and wireless device 110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, 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; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), 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.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and wireless device 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • 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.
  • FIGURE 13 illustrates an example network node, according to certain embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • network node 160 illustrated in the example wireless network of FIGURE 11 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node 160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more 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 encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units.
  • processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non
  • Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190.
  • processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or wireless devices 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • all or some of RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187.
  • an external power source e.g., an electricity outlet
  • power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • network node 160 may include additional components beyond those shown in FIGURE 13 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • FIGURE 14 illustrates a wireless device, according to certain embodiments.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term wireless device may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a wireless device may be configured to transmit and/or receive information without direct human interaction.
  • a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a wireless device may support device- to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device- to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a wireless device may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node.
  • the wireless device may in this case be a machine-to-machine (M2M) device, which may in a 3 GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the wireless device may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • Wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device 110.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.
  • interface 114 comprises radio front end circuitry 112 and antenna 111.
  • Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120.
  • Radio front end circuitry 112 may be coupled to or a part of antenna 111.
  • wireless device 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111.
  • some or all of RF transceiver circuitry 122 may be considered a part of interface 114.
  • Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more 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 encoded logic operable to provide, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130, wireless device 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 120 of wireless device 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of wireless device 110, but are enjoyed by wireless device 110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be considered to be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with wireless device 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 110 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 alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • Wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry out any functionality described or indicated herein.
  • Power circuitry 137 may in certain embodiments comprise power management circuitry.
  • Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which power is supplied.
  • FIGURE 15 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 2200 may be any UE identified by the 3 rd Generation Partnership Project (3 GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 15, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 15 is a UE, the components discussed herein are equally applicable to a wireless device, and vice- versa.
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 15, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a 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 telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 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, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (EO), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • EO basic input and output
  • Storage medium 221 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 disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 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 wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 243b 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 telecommunications network, another like network or any combination thereof.
  • network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 16 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390.
  • Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360.
  • Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.
  • processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.
  • hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225.
  • Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.
  • FIGURE 17 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network 410, such as a 3 GPP -type cellular network, which comprises access network 411, such as a radio access network, and core network 414.
  • Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c.
  • Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider.
  • Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 17 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the-top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • FIGURE 18 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518.
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 18) served by base station 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 18) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • processing circuitry 528 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538.
  • Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510.
  • an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, base station 520 and UE 530 illustrated in FIGURE 18 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 17, respectively.
  • the inner workings of these entities may be as shown in FIGURE 18 and independently, the surrounding network topology may be that of FIGURE 17.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.
  • FIGURE 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 17 and 18. For simplicity of the present disclosure, only drawing references to FIGURE 19 will be included in this section.
  • the host computer provides user data.
  • substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 640 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 17 and 18. For simplicity of the present disclosure, only drawing references to FIGURE 20 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 17 and 18. For simplicity of the present disclosure, only drawing references to FIGURE 21 will be included in this section.
  • step 810 the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data.
  • substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application.
  • substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer.
  • step 840 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 17 and 18. For simplicity of the present disclosure, only drawing references to FIGURE 22 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIGURE 23 depicts a method by a first base station.
  • the method begins at step 1002 when the first base station detects an occurrence of an event.
  • the event includes a UE RACH access deriving from a mobility procedure from a second base station to the first base station.
  • the first base station transmits, to the second base station, information comprising at least one of:
  • FIGURE 24 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 12).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 12).
  • Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 23 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 23 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose 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, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause detecting module 1110, transmitting module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.
  • detecting module 1110 may perform certain of the detecting functions of the apparatus 1100.
  • detecting module 1110 may detect detects an occurrence of an event.
  • the event includes a UE RACH access deriving from a mobility procedure from a second base station to the first base station.
  • transmitting module 1120 may perform certain of the transmitting functions of the apparatus 1100. For example, transmitting module 1120 may transmit, to the second base station, information comprising at least one of:
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 25 depicts a method performed by a first base station.
  • the method begins at step 1202 when the first base station detects an occurrence of an event.
  • the event includes a RACH access.
  • the first base station transmits, to the second base station, information comprising at least one of: a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about the RACH access.
  • the information further includes at least one of: an interference measurement on a per UE basis; and information about timing advance.
  • the information relating to the failure event comprises at least one of: per beam measurement of a serving beam, per beam measurement of a target beam, per beam measurement of at least one detected neighbor beam, beam identifier of a beam where a mobility failure occurred, beam identifier of the beam where a re-establishment occurred, and beam identifier of a source beam.
  • the information about the RACH access comprises at least one of: a number of RACH attempts per Beam per cell ID for determining transmission power used by each UE per attempt and/or potential UL coverage issues, information about whether the RACH access was successful or failed and per cell per beam ID where the access was attempted for use in building a map of UL coverage, and measurement of DL reference signal of the beam and/or cell where the RACH access was attempted for use in comparing DL coverage to UL coverage for a beam for which the RACH access was attempted.
  • FIGURE 26 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 12).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 12).
  • Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 25 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 25 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose 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, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause detecting module 1310, transmitting module 1320, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • detecting module 1310 may perform certain of the detecting functions of the apparatus 1300. For example, detecting module 1310 may detect an occurrence of an event.
  • the event includes a RACH access.
  • transmitting module 1320 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1320 may transmit, to the second base station, information comprising at least one of: a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about the RACH access.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 27 depicts a method by a first base station.
  • the method begins at step 1402 when the first base station receives, from a second base station, information comprising at least one of: per serving cell/beam RS measurements, per target beam/cell RS measurement, information relating to a failure event; information about RACH access; interference measurements on a per UE basis; information about timing advance.
  • the first base station takes at least one action to adjust for UL/DL capacity or coverage optimization.
  • FIGURE 28 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 12).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 12).
  • Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 27 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 27 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose 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, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1510, taking module 1520, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1510 may perform certain of the receiving functions of the apparatus 1500. For example, receiving module 1510 may receive, from a second base station, information comprising at least one of:
  • taking module 1520 may perform certain of the taking action functions of the apparatus 1500. For example, taking module 1520 may, based on the information, take at least one action to adjust for UL/DL capacity or coverage optimization.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 29 depicts a method performed by a first base station.
  • the method begins at step 1602 when the first base station receives, from a second base station, information comprising at least one of: a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about a Random Access Channel (RACH) access. Based on the information, the first base station takes at least one action to adjust at least one capacity or coverage optimization parameter, at step 1604.
  • RACH Random Access Channel
  • the information further comprises at least one of: an interference measurement on a per user equipment (UE) basis; and information associated with timing advance.
  • the first base station determines a coverage of a serving cell based on the information, and the at least one action includes comparing the coverage of the serving cell with a threshold to determine whether the coverage of the serving cell greater than the threshold.
  • the first base station determines a coverage of a serving cell based on the information, and the at least one action includes determining whether the coverage of the serving cell and a coverage of at least one neighboring cell at least partially overlap.
  • taking the at least one action to adjust the at least one capacity or coverage optimization parameter includes adjusting a mobility setting or a cell coverage setting.
  • adjusting the mobility setting may include changing an event threshold, for example.
  • adjusting a cell coverage setting may include adjusting an antenna configuration, for example.
  • taking the at least one action includes determining a transmission power used by a UE per attempt of the RACH access.
  • taking the at least one action includes building a map of an UL coverage and/or a DL coverage.
  • taking the at least one action includes determining if an uplink coverage and/or a downlink coverage is greater than an uplink coverage threshold and/or a downlink coverage threshold, respectively.
  • taking the at least one action comprises at least one of: determining if a UE at a border of a serving cell is subject to high interference; determining a need for a cell and/or beam border change; determining a location of a UE within a cell and/or beam; and controlling a timing advance setting for a transmission of a UE.
  • the information relating to the failure event comprises at least one of: a per beam measurement of a serving beam; a per beam measurement of a target beam; a per beam measurement of at least one detected neighbor beam; a beam identifier of a beam where a mobility failure occurred; a beam identifier of the beam where a re-establishment occurred; and a beam identifier of a source beam.
  • the information about the RACH access comprises at least one of: a number of RACH attempts per Beam per cell identifier (ID) for determining a transmission power used by each UE per RACH attempt and/or an UL coverage issue; information about whether the RACH access was successful or failed and a cell per beam ID where the RACH access was attempted for use in building a map of UL coverage; and a measurement of a DL reference signal of a beam per cell where the RACH access was attempted for use in comparing a DL coverage to an UL coverage for a beam for which the RACH access was attempted.
  • ID Radio Access
  • the information about the RACH access comprises at least one of: a number of RACH attempts per Beam per cell identifier (ID) for determining a transmission power used by each UE per RACH attempt and/or an UL coverage issue; information about whether the RACH access was successful or failed and a cell per beam ID where the RACH access was attempted for use in building a map of UL coverage; and a measurement of a DL
  • FIGURE 30 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 12).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 12).
  • Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 29 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 29 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose 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, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1710, taking module 1720, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1710 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1710 may receive, from a second base station, information including at least one of: a per serving cell per beam reference signal measurement; a per target beam per cell reference signal measurement; information relating to a failure event; and information about a RACH access.
  • taking module 1720 may perform certain of the taking action functions of the apparatus 1700. For example, taking module 1720 may, based on the information, take at least one action to adjust at least one capacity or coverage optimization parameter.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • Example Embodiment 1 A method performed by a first base station, the method comprising: detecting an occurrence of an event, the event comprising a LIE RACH access deriving from a mobility procedure from a second base station to the first base station; and transmitting, to the second base station, information comprising at least one of: per serving cell/beam RS measurements, per target beam/cell RS measurement, information relating to a failure event; information about RACH access; interference measurements on a per LIE basis; and information about timing advance.
  • an event comprising a LIE RACH access deriving from a mobility procedure from a second base station to the first base station
  • information comprising at least one of: per serving cell/beam RS measurements, per target beam/cell RS measurement, information relating to a failure event; information about RACH access; interference measurements on a per LIE basis; and information about timing advance.
  • Example Embodiment 2 The method of Embodiment 1, wherein at least one of the first base station and the second base station comprises a gNodeB.
  • Example Embodiment 3 The method of any one of Embodiments 1 to 2, wherein at least one of the first base station and the second base station comprises an eNodeB.
  • Example Embodiment 4 The method of any one of Embodiments 1 to 3, wherein the information relating to the failure event comprises at least one of: Per beam measurements of a serving beam; Per beam measurement of a target beam; Per beam measurement of at least one detected neighbor beam; Beam identifier of a beam where the mobility failure occurred; Beam identifier of the beam where re-establishment occurred; Beam identifier of source beam.
  • Example Embodiment 5 The method of any one of Embodiments 1 to 4, wherein the information about RACH access comprises at least one of: A number of RACH attempts per Beam/cell ID for determining transmission power used by each UE per attempt and/or potential UL coverage issues; Information about successful/failed RACH access together with cell/beam ID where the access was attempted for use in building a map of UL coverage; Measurement of DL RS of the beam/cell where RACH access is attempted for use in comparing DL coverage to UL coverage for a beam for which RACH access is attempted.
  • Example Embodiment 6. A method performed by a first base station, the method comprising: receiving, from a second base station, information comprising at least one of
  • Example Embodiment 7 The method of Embodiment 6, wherein the at least one action comprises comparing a serving cell coverage with a threshold to determining whether cell coverage is sufficiently good.
  • Example Embodiment 8 The method of any one of Embodiments 6 to 7, wherein the at least one action comprises determining whether a coverage of a serving cell and a coverage of at least one neighboring cell sufficiently overlap.
  • Example Embodiment 9 The method of any one of Embodiments 6 to 8, wherein the at least one action comprises adjusting a mobility or cell coverage setting.
  • Example Embodiment 10 The method of any one of Embodiments 6 to 9, wherein the at least one action comprises correlating the information with at least one measurement.
  • Example Embodiment 11 The method of any one of Embodiments 6 to 10, wherein the at least one action comprises determining a transmission power used by a UE per RACH access attempt.
  • Example Embodiment 12 The method of any one of Embodiments 6 to 11, wherein the at least one action comprises building a map of uplink coverage and/ or downlink coverage.
  • Example Embodiment 13 The method of any one of Embodiments 6 to 12, wherein the at least one action comprises determining if uplink and/or downlink coverage is above a respective uplink and/or downlink coverage threshold.
  • Example Embodiment 14 The method of any one of Embodiments 6 to 13, wherein the at least one action comprises determining if a UE at a border of a serving cell is subject to high interference.
  • Example Embodiment 15 The method of any one of Embodiments 6 to 14, wherein the at least one action comprises determining a need for a cell and/or beam border change.
  • Example Embodiment 16 The method of any one of Embodiments 6 to 15, wherein the at least one action comprises determining a location of a TIE within a cell and/or beam.
  • Example Embodiment 17 The method of any one of Embodiments 6 to 16, wherein the at least one action comprises controlling a timing advance setting for a transmission of a TIE.
  • Example Embodiment 18 The method of any one of Embodiments 6 to 17, wherein at least one of the first base station and the second base station comprise a gNodeB.
  • Example Embodiment 19 The method of any one of Embodiments 6 to 18, wherein at least one of the first base station and the second base station comprise an eNodeB.
  • Example Embodiment 20 The method of any one of Embodiments 6 to 19, wherein the information relating to the failure event comprises at least one of: Per beam measurements of a serving beam; Per beam measurement of a target beam; Per beam measurement of at least one detected neighbor beam; Beam identifier of a beam where the mobility failure occurred; Beam identifier of the beam where re-establishment occurred; and Beam identifier of source beam.
  • Example Embodiment 21 The method of any one of Embodiments 6 to 20, wherein the information about RACE! access comprises at least one of: A number of RACH attempts per Beam/cell ID for determining transmission power used by each UE per attempt and/or potential UL coverage issues; Information about successful/failed RACH access together with cell/beam ID where the access was attempted for use in building a map of UL coverage; Measurement of DL RS of the beam/cell where RACH access is attempted for use in comparing DL coverage to UL coverage for a beam for which RACH access is attempted.
  • Example Embodiment 22 A base station for improving network efficiency, the base station comprising: processing circuitry configured to perform any of the steps of any one of Embodiments 1 to 21; and power supply circuitry configured to supply power to the wireless device.
  • Example Embodiment 23 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any one of Embodiments 1 to 21.
  • UE user equipment
  • Example Embodiment 24 The communication system of the previous embodiment further including the base station.
  • Example Embodiment 25 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 26 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • Example Embodiment 27 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any one of Embodiments 1 to 21.
  • UE user equipment
  • Example Embodiment 28 The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
  • Example Embodiment 29 The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
  • Example Embodiment 30 A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • UE user equipment
  • Example Embodiment 31 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any one of Embodiments 1 to 21.
  • UE user equipment
  • Example Embodiment 32 The communication system of the previous embodiment further including the base station.
  • Example Embodiment 33 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 34 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the EGE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé (1200) réalisé par une première station de base (160) qui consiste à détecter une occurrence d'un événement, qui peut comprendre un accès à un canal d'accès aléatoire (RACH pour Random Access Channel) et à transmettre, à la seconde station de base, des informations comprenant : une mesure de signal de référence par cellule de desserte par faisceau ; et/ou une mesure de signal de référence par faisceau cible par cellule ; et/ou des informations se rapportant à un événement de défaillance ; et/ou des informations concernant l'accès à un canal RACH.
PCT/SE2020/050164 2019-02-14 2020-02-13 Gestion de couverture et de capacité WO2020167236A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962805429P 2019-02-14 2019-02-14
US62/805,429 2019-02-14

Publications (1)

Publication Number Publication Date
WO2020167236A1 true WO2020167236A1 (fr) 2020-08-20

Family

ID=72045040

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050164 WO2020167236A1 (fr) 2019-02-14 2020-02-13 Gestion de couverture et de capacité

Country Status (1)

Country Link
WO (1) WO2020167236A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113133058A (zh) * 2021-04-07 2021-07-16 中国移动通信集团陕西有限公司 负载均衡方法、装置及系统
CN114126039A (zh) * 2020-08-28 2022-03-01 中国移动通信集团设计院有限公司 一种定位方法、装置及存储介质
CN114389657A (zh) * 2022-02-15 2022-04-22 赛特斯信息科技股份有限公司 基于多基带合并宏分集的多rru小区无线网络
WO2022151412A1 (fr) * 2021-01-15 2022-07-21 华为技术有限公司 Procédé de communication et appareil de communication
EP4044657A1 (fr) * 2021-02-16 2022-08-17 Viavi Solutions Inc. Optimisation en temps réel de paramètres de réseau
EP4108000A4 (fr) * 2021-01-13 2023-11-08 ZTE Corporation Optimisation de couverture et de capacité de niveau de faisceau

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010057125A1 (fr) * 2008-11-17 2010-05-20 Qualcomm Incorporated Rapport d’échec de liaison radio
US20120250498A1 (en) * 2011-03-31 2012-10-04 Mediatek, Inc. Failure Event Report Correlation for Distributed RAN Self-Organization
EP2512179A1 (fr) * 2010-04-26 2012-10-17 ZTE Corporation Procédé pour déterminer la raison d'un transfert trop tardif à une station de base domestique
WO2013115532A1 (fr) * 2012-01-30 2013-08-08 Lg Electronics Inc. Procédé et appareil de transmission d'un message de compte-rendu de transfert dans un système de communication sans fil
US20170026846A1 (en) * 2014-12-01 2017-01-26 Lg Electronics Inc. Method and apparatus for indicating cell splitting pattern
EP3171638A1 (fr) * 2014-07-18 2017-05-24 Samsung Electronics Co., Ltd. Procédé et appareil permettant d'améliorer le taux de réussite de transfert
WO2019245290A1 (fr) * 2018-06-22 2019-12-26 Lg Electronics Inc. Procédé et appareil permettant de fournir des informations relatives à un faisceau pour une détection de défaillance de connexion dans un système de communication sans fil

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010057125A1 (fr) * 2008-11-17 2010-05-20 Qualcomm Incorporated Rapport d’échec de liaison radio
EP2512179A1 (fr) * 2010-04-26 2012-10-17 ZTE Corporation Procédé pour déterminer la raison d'un transfert trop tardif à une station de base domestique
US20120250498A1 (en) * 2011-03-31 2012-10-04 Mediatek, Inc. Failure Event Report Correlation for Distributed RAN Self-Organization
WO2013115532A1 (fr) * 2012-01-30 2013-08-08 Lg Electronics Inc. Procédé et appareil de transmission d'un message de compte-rendu de transfert dans un système de communication sans fil
EP3171638A1 (fr) * 2014-07-18 2017-05-24 Samsung Electronics Co., Ltd. Procédé et appareil permettant d'améliorer le taux de réussite de transfert
US20170026846A1 (en) * 2014-12-01 2017-01-26 Lg Electronics Inc. Method and apparatus for indicating cell splitting pattern
WO2019245290A1 (fr) * 2018-06-22 2019-12-26 Lg Electronics Inc. Procédé et appareil permettant de fournir des informations relatives à un faisceau pour une détection de défaillance de connexion dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA; NOKIA SHANGHAI BELL: "S-RLF handling for MR-DC", 3GPP DRAFT; R3-173497 MR- DC_ S-RLF _ TP37340, 28 September 2017 (2017-09-28), XP051356247 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114126039A (zh) * 2020-08-28 2022-03-01 中国移动通信集团设计院有限公司 一种定位方法、装置及存储介质
CN114126039B (zh) * 2020-08-28 2023-11-03 中国移动通信集团设计院有限公司 一种定位方法、装置及存储介质
EP4108000A4 (fr) * 2021-01-13 2023-11-08 ZTE Corporation Optimisation de couverture et de capacité de niveau de faisceau
WO2022151412A1 (fr) * 2021-01-15 2022-07-21 华为技术有限公司 Procédé de communication et appareil de communication
EP4262300A4 (fr) * 2021-01-15 2024-02-14 Huawei Tech Co Ltd Procédé de communication et appareil de communication
EP4044657A1 (fr) * 2021-02-16 2022-08-17 Viavi Solutions Inc. Optimisation en temps réel de paramètres de réseau
US11742963B2 (en) 2021-02-16 2023-08-29 Viavi Solutions Inc. Real-time optimization of network parameters
CN113133058A (zh) * 2021-04-07 2021-07-16 中国移动通信集团陕西有限公司 负载均衡方法、装置及系统
CN114389657A (zh) * 2022-02-15 2022-04-22 赛特斯信息科技股份有限公司 基于多基带合并宏分集的多rru小区无线网络
CN114389657B (zh) * 2022-02-15 2023-02-28 赛特斯信息科技股份有限公司 基于多基带合并宏分集的多rru小区无线网络

Similar Documents

Publication Publication Date Title
US11696194B2 (en) Triggered measurement reporting for wireless communications
US20220141725A1 (en) Reporting of Successful Handover to a Target Cell
US20220131793A1 (en) Centralized Unit-Distributed Unit Communication Associated to Radio Link Failure Report and Beam Failure Recovery Attempts
EP3857954B1 (fr) Commutation de canal sans fil
TWI728697B (zh) 具有波束選擇資訊之隨機存取通道報告
JP7315681B2 (ja) 無線リンクモニタリング、ビーム障害検出、及びビーム障害回復のためのユーザ装置からネットワークへの報告
TW201927053A (zh) 在交遞執行中的多波束隨機存取程序
WO2020167236A1 (fr) Gestion de couverture et de capacité
US20220346174A1 (en) Reporting Listen-before-Talk Failures in a Wireless Network
US20220394565A1 (en) Determining Security Keys
US20210410185A1 (en) Adaptive sensing mechanism for unlicensed networks
US11924874B2 (en) Enhanced channel occupancy sharing mechanism for random access and PUCCH in unlicensed spectrum
EP4029341B1 (fr) Procédés fournissant des messages d'information comprenant des rapports rach et dispositifs sans fil associés
US11304237B2 (en) Random access with different TTI durations
WO2021246926A1 (fr) Procédés, appareils et programmes informatiques pour extraire des rapports de canal d'accès aléatoire en connectivité double
WO2021034254A1 (fr) Mise à jour d'une pci dans une architecture divisée du-cu
WO2021126065A1 (fr) Amélioration de la coexistence à l'aide d'une démarcation virtuelle de réseaux non publics dans les macro-réseaux publics
WO2020167212A1 (fr) Récupération après défaillance de liaison radio sur une liaison montante supplémentaire
US20230189374A1 (en) Random access reports for reestablishment
US20240172155A1 (en) Time difference of arrival and signal strength based timing advance validation for configured grant small data transmission

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20755983

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20755983

Country of ref document: EP

Kind code of ref document: A1