EP3738340B1 - Deltakonfiguration in geteilter cu-du-ran-architektur - Google Patents

Deltakonfiguration in geteilter cu-du-ran-architektur Download PDF

Info

Publication number
EP3738340B1
EP3738340B1 EP18830011.5A EP18830011A EP3738340B1 EP 3738340 B1 EP3738340 B1 EP 3738340B1 EP 18830011 A EP18830011 A EP 18830011A EP 3738340 B1 EP3738340 B1 EP 3738340B1
Authority
EP
European Patent Office
Prior art keywords
configuration
layer configuration
network
gnb
event
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP18830011.5A
Other languages
English (en)
French (fr)
Other versions
EP3738340A1 (de
Inventor
Angelo Centonza
Matteo FIORANI
Walter Müller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3738340A1 publication Critical patent/EP3738340A1/de
Application granted granted Critical
Publication of EP3738340B1 publication Critical patent/EP3738340B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present application relates generally to the field of wireless communication networks and, more specifically, to radio access networks (RANs) in which base station functionality is split between central and distributed units.
  • RANs radio access networks
  • FIG. 1 illustrates a high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) and a 5G Core (5GC).
  • the NG-RAN can comprise a set of gNodeB's (gNBs, including gNB 100) connected to the 5GC via one or more NG interfaces, whereas the gNBs can be connected to each other via one or more Xn interfaces.
  • gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • the NG RAN logical nodes shown in Figure 1 include a Central Unit (CU or gNB-CU) and one or more Distributed Units (DU or gNB-DU).
  • gNB 100 includes CU 110 and DUs 120 and 130.
  • a CU can host higher-layer protocols and can include a number of gNB functions, such as controlling the operation of DUs.
  • a DU can host lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions.
  • the terms “central unit” and “centralized unit” are used interchangeably, and the terms “distributed unit” and “decentralized unit” are also used interchangeability.
  • the NG, Xn-C and F1 items shown in Figure 1 are logical interfaces.
  • the NG and Xn-C interfaces for a split gNB terminate in the gNB-CU.
  • the S1-U and X2-C interfaces for a split gNB terminate in the gNB-CU.
  • the gNB-CU connects to gNB-DUs over respective F1 logical interfaces.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB, e.g., the F1 interface is not visible beyond gNB-CU.
  • the F1 interface between the gNB-CU and gNB-DU is specified, or based on, the following general principles:
  • a CU can host higher-layer protocols such as RRC and PDCP, while a DU can host lower-layer protocols such as RLC, MAC and PHY.
  • Other variants of protocol distributions between CU and DU can exist, such as hosting the RRC, PDCP and part of the RLC protocol in CU ( e.g. , Automatic Retransmission Request (ARQ) function), while hosting the remaining parts of the RLC protocol in the DU, together with MAC and PHY.
  • CU can host RRC and PDCP, where PDCP is assumed to handle both UP traffic and CP traffic.
  • other exemplary embodiments may utilize other protocol splits that by hosting certain protocols in CU and certain others in the DU.
  • Exemplary embodiments can also locate centralized control plane protocols (e.g ., PDCP-C and RRC) in a different CU with respect to the centralized user plane protocols (e.g. , PDCP-U).
  • 3GPP RAN WG3 has also stared working on a new open interface - referred to as "E1" - between the control plane (CU-CP) and the user plane (CU-UP) parts of CU.
  • E1 control plane
  • CU-UP user plane
  • DC can be achieved by means of allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs.
  • a gNB can include a gNB-CU connected to one or more gNB-DUs via respective F1 interfaces, all of which are described hereinafter in greater detail.
  • a gNB-DU can be connected to only a single gNB-CU.
  • 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 i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, F1 the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • each gNB is connected to all 5GC nodes within a pool area.
  • the pool area is defined in 3GPP TS 23.501. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP (3GPP TS 33.401) shall be applied.
  • DC support includes establishing master (MN) and secondary nodes (SNs) and distributing UP traffic to the MN and SNs according to optimal, preferred, and/or desirable traffic and radio resource management techniques.
  • MN master
  • SNs secondary nodes
  • CP traffic is assumed to terminate in one node only, i.e. the MN.
  • Figures 2 and 3 below show the protocol and interfaces involved in DC, as described in 3GPP TS 38.300v0.6.0.
  • FIG 2 illustrates that a Master gNB (MgNB) can forward PDCP bearer traffic to a Secondary gNB (SgNB), while Figure 3 illustrates a scenario where the SgNB can forward PDCP bearer traffic to the MgNB.
  • MgNB Master gNB
  • SgNB Secondary gNB
  • the MgNB and/or SgNB can be subject to the RAN split architecture (e.g., CU and DU) discussed above.
  • multi-RAT dual connectivity can also be envisioned as an important feature in 5G RAN architectures.
  • the MN can anchor the control plane towards the CN, while the SN can provide control and user plane resources to the UE via coordination with the MN.
  • Figure 4 is extracted from 3GPP TS 37.340.
  • Figure 5 shows various user-plane (UP) bearer types and corresponding protocol stack configurations for MR-DC, as further described in 3GPP TS 37.340.
  • NG-RAN nodes can provide both NR access via gNBs and E-UTRA (also known as "LTE") access via evolved Node B's (eNBs).
  • E-UTRA also known as "LTE”
  • eNBs evolved Node B's
  • Many features for connectivity, mobility, support of QoS, etc. apply for both NR/5G and E-UTRA/LTE access.
  • any feature described for gNBs can also apply to eNBs, which are often referred to in this conext as "ng-eNB.”
  • ng-eNB it is anticipated that higher/lower layer split described above for gNBs will also be used for ng-eNBs.
  • delta-configuration can be utilized to reduce the size of the RRC messages that are sent over the radio interface, which improves both efficiency and performance. For example, a smaller RRC handover command message (i.e., RRC-Connection-Reconfiguration with Mobility Control Info) may significantly reduce the probability of handover failure, especially in the case of intra-frequency handover.
  • the target node should receive the configuration of the UE in the source node. As such, the target node can generate an RRC message that contains only the delta with respect to the received UE configuration.
  • exemplary embodiments of the present disclosure address these shortcomings in NG-RAN networks, thereby facilitating the sending of a UE configuration from a source gNB-DU to a target gNB-DU in an NG-RAN.
  • Such exemplary embodiments can include methods and/or procedures performed by a central unit (CU, e.g., gNB-CU or MgNB).
  • the CU, together with first and second DUs, can comprise a node of a wireless communication network.
  • the gNB-DU hosting the low layers configuration (e.g. , for RLC/MAC/PHY protocols) is different from the gNB-CU generating the mobility signaling.
  • a source gNB-DU had to provide low layer configuration to the target gNB-DU as part of UE mobility preparation, the information would need to be signaled from source gNB-DU to source gNB-CU, then from source gNB-CU to target gNB-CU, and then from target gNB-CU to target gNB-DU.
  • the source-to-target configuration information needs to travel only from source eNB to target eNB.
  • NG-RAN mobility may be affected by long handover preparation delays. These delays can cause frequent radio link failures due to the UE having moved out of coverage by the time the handover preparation has been completed. Other similar failures due to UE mobility during handover preparation and before handover execution can also occur. Similar problems can be encountered during configuration of dual connectivity (DC) for the UE. If the nodes involved in the DC configuration require long times to exchange their respective low layer configurations, the UE might have moved in locations where the DC configuration is inefficient and/or inappropriate.
  • DC dual connectivity
  • Exemplary embodiments of the present disclosure address these problems by providing mechanisms that enable, facilitate, and/or support delta-configuration in the split gNB-CU/DU architecture while reducing and/or minimizing signaling delays.
  • Such exemplary embodiments can send a UE configuration directly to a target gNB-DU, so that a delta configuration (e.g. , delta-RRC) message can be generated.
  • a delta configuration e.g. , delta-RRC
  • Such exemplary embodiments can be utilized in, but are not limited to, dual-connectivity and mobility procedures.
  • These exemplary embodiments can provide benefits including, e.g ., reduced size of RRC messages over the air interface, delivery of the delta configuration to the UE in short time spans, and increased NG-RAN efficiency and performance due, e.g., to lower probability of handover failures.
  • benefits including, e.g ., reduced size of RRC messages over the air interface, delivery of the delta configuration to the UE in short time spans, and increased NG-RAN efficiency and performance due, e.g., to lower probability of handover failures.
  • 5G/NR solutions can facilitate more timely design, implementation, and deployment of 5G/NR solutions.
  • these and other advantages and/or benefits can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and are important for the growth of over-the-top (OTT) data applications or services external to the 5G network.
  • OTT over-the-top
  • these and other advantages and/or benefits can also lead to improved user experience associated with OTT data applications or services, particularly with
  • the first category embodies the operational principle of a gNB-CU retrieving a configuration of lower layers from a source gNB-DU.
  • the gNB-CU can contact the source gNB-DU and retrieve the current lower-layer configuration for the UE via a new UE-associated procedure over the F1 interface.
  • the gNB-CU can retrieve the source gNB-DU configuration ahead of a mobility or DC event. This can be done by monitoring the measurments reported by the UE, via the gNB-DU, to the gNB-CU and predicting that mobility or DC preparation is needed. By fetching the source gNB-DU configuration ahead of time, the mobility/DC configuration delay will not affect the overall performance of the procedure.
  • the gNB-DU can send an update to gNB-CU whenever the gNB-DU does something that it considers needed for the gNB-CU in the future.
  • the gNB-CU can also send the current lower-layer configuration of the UE to the target gNB-DU.
  • the lower-layer configuration can be included in an RRC container in an F1AP UE Context Setup Request message.
  • Such lower layer configuration can include source gNB-DU to target gNB-DU information such as:
  • the target gNB-DU can determine the new lower-layer configuration for the UE, and generate an RRC container that only includes the delta with respect to the configuration forwarded by the gNB-CU (e.g., the source gNB-DU configuration).
  • the gNB-DU can send the RRC container to the gNB-CU over the F1 interface, e.g., in an F1AP UE Context Setup Response message.
  • the gNB-CU can add and encode information such that the final RRC message can include: (1) delta of the lower-layer configuration generated by the target gNB-DU; and (2) delta of the higher-layer configuration that is generated directly by the gNB-CU.
  • the higher-layer configuration generated by the gNB-CU can include, e.g. , configuration of the PDCP and (if present) the SDAP protocol.
  • the higher-layer configuration is included in the RRC IE RB-Config (radio bearer configuration) that is defined in 3GPP TS 38.331.
  • the higher-layer configuration can also include the measurement configuration for the UE.
  • the gNB-CU can send the RRC message comprising such information over the air to the UE.
  • the second category of exemplary embodiments is based on the operational principle that the gNB-CU stores the lower-layer configuration for the UE.
  • the gNB-CU stores the lower-layer configuration of the UE that is generated by the source gNB-DU.
  • information described above as comprising the source gNB-DU lower-layer configuration can be signaled in advance by the source gNB-DU to the gNB-CU, which can then store the received configuration.
  • the gNB-DU can also acquire UE measurements of neighbor cells, which it can use to determine other information, such as described above with respect to the other category of embodiments.
  • the gNB-CU can also forward the received UE measurements to the target gNB-DU, so that the target gNB-DU is aware of the cells measured by the UE before the mobility or DC configuration is activated.
  • the latter UE measurement forwarding is applicable also in the previous method.
  • the gNB-CU does not need to contact the source gNB-DU and it can directly contact the target gNB-DU. As such, this arrangement can provide a significant reduction in signaling delays.
  • the second category of embodiments can operate in a manner similar as the first category.
  • the gNB-CU can also send the current lower-layer configuration of the UE to the target gNB-DU, e.g., in an RRC container in an F1AP UE Context Setup Request message comprising information described in detail above.
  • the target gNB-DU can also determine the new lower-layer configuration for the UE, and generate an RRC container that only includes the delta with respect to the configuration forwarded by the gNB-CU.
  • the gNB-CU can also add and encode information such that the final RRC message can include the delta of the lower-layer configuration generated by the target gNB-DU, as well as the delta of the higher-layer configuration that is generated directly by the gNB-CU.
  • Figure 6 illustrates an exemplary information flow among elements of a NG-RAN comprising a DU-CU split architecture for supporting inter-gNB-DU handover using delta-configuration, according to some exemplary embodiments of the present disclosure.
  • various operations are given numerical labels or designations. However, this is for convenience only and should not be interpreted as limiting the operations to occur in any particular numerical order.
  • Figure 7 illustrates an exemplary information flow among elements of a NG-RAN comprising a DU-CU split architecture for supporting dual connectivity (DC) using delta-configuration, according to some exemplary embodiments of the present disclosure.
  • various operations are given numerical labels or designations. However, this is for convenience only and should not be interpreted as limiting the operations to occur in any particular numerical order.
  • each numbered operation corresponds to the same numbered item in Figure 7 .
  • operations 1-9 and 12-13 are substantially the same as in the exemplary flow shown in Figure 6 , and their explanations are omitted below.
  • the UE is configured to transmit/receive data via DU1.
  • operations 8-9 the UE sends a measurement report to the CU.
  • CU decides to setup DU2 as a secondary leg.
  • CU generates SCG-Config-Info container, which includes CellGroupConfig1.
  • CU before operation 10, can send a UE CONTEXT MODIFICATION REQUEST to the DU1, informing that DC is going to be activated.
  • DU1 then generates a new CellGroupConfig1 and sends it to the CU.
  • the new CellGroupConfig1 is optimized for supporting DC.
  • the CU can include the new CellGroupConfigl (optimized for DC) in the SCG-Config-Info container.
  • the UE capabilities can be updated and exchanged with gNB-DU1 and gNB-DU2.
  • gNB-CU can trigger a UE Context Modification procedure as specified above with gNB-DU1.
  • the gNB-CU can derive the UE capabilities that gNB-DU1 can relay on the basis of the planned DC configuration. That can be achieved at gNB-CU because gNB-CU is aware of the configuration ( e.g . the bearers to be established, the radio resource needed, the bit rates required, etc .) to be applied at gNB-DU2.
  • gNB-CU can derive a set of UE capabilities gNB-DU1 can use and send them to gNB-DU1 at e.g. UE context Modification.
  • the gNB-CU can send the remaining UE capabilities that the gNB-DU2 can use to gNB-DU2 via message 11 (UE context Setup) or any equivalent message.
  • message 11 UE context Setup
  • gNB-CU can perform a UE context Modification Request towards gNB-DU1.
  • the gNB-DU1 has the full UE capabilities previously received from gNB-CU, and can therefore deduce the UE capabilities that it can use to send to gNB-CU a set of UE capabilities that gNB-DU2 can then access and use.
  • This exemplary embodiments leaves deduction of UE capabilities to be used by gNB-DU1 and gNB-DU2 to gNB-DU1.
  • Figure 8 illustrates an exemplary method and/or procedure performed by a central unit (CU, e.g., gNB-CU or MgNB) of a node in a wireless network, in accordance with various exemplary embodiments of the present disclosure.
  • CU central unit
  • the CU can comprise a base station, gNB, en-gNB, ng-eNB, etc. of a radio access network (RAN).
  • RAN radio access network
  • the exemplary method and/or procedure is illustrated in Figure 8 by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown in Figure 8 .
  • the exemplary method and/or procedure shown in Figure 8 can be complimentary to the exemplary methods and/or procedures shown in Figures 9-10 .
  • the exemplary methods and/or procedures shown in Figures 8-10 are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove.
  • Optional operations are indicated by dashed lines.
  • the exemplary method and/or procedure can include the operations of block 810, where the CU can send, to the first DU, a context setup request concerning the UE. In some embodiments, the exemplary method and/or procedure can include the operations of block 820, where the CU can send a request, to the first DU, for the lower-layer configuration of the UE in response to one or more measurements made by the UE that were received from the first DU.
  • the exemplary method and/or procedure can include the operations of block 830, where the CU can receive from the first DU, prior to occurrence of a first event concerning a UE that is in communication with the first DU, a lower-layer configuration of the UE.
  • the lower-layer configuration of the UE can be received in response to the particular request sent by the CU.
  • the received lower-layer configuration of the UE can include the RRM configuration used by the first DU with respect to the UE and/or the access stratum configuration used by the first DU with respect to the UE.
  • the exemplary method and/or procedure can also include the operations of block 840, where the CU can store the lower-layer configuration of the UE.
  • the exemplary methods and/or procedures can include the operations of block 850, where the CU can receive one or more neighbor-cell measurements made by the UE and determine a further lower-layer configuration of the UE based on the received neighbor-cell measurements.
  • the exemplary methods and/or procedures can include the operations of block 860, where the CU can determine to trigger the first event based on one or more measurements received from the first DU.
  • the first event can a mobility event or a dual-connectivity event.
  • the exemplary method and/or procedure can also include the operations of block 870, where the CU can send, to the second DU, a setup request comprising the stored lower-layer configuration of the UE.
  • the setup request can include the further lower-layer configuration.
  • sending the setup request message can be in response to determining to trigger the first event.
  • the exemplary method and/or procedure can also include the operations of block 880, where the CU can receive, from the second DU, a setup response comprising a first delta configuration indicating one or more differences between a lower-layer configuration of the second DU and the stored lower-layer configuration.
  • the exemplary method and/or procedure can also include the operations of block 890, where the CU can send, to the first DU, a modification request comprising the first delta configuration.
  • the exemplary methods and/or procedures can include the operations of block 885, where the CU can generate a second delta configuration indicating one or more differences between higher-layer configurations of the UE with respect to the first and the second DUs.
  • the modification request sent in block 890 can also include the second delta configuration.
  • Figure 9 illustrates an exemplary method and/or procedure performed by a second distributed unit (DU, e.g., gNB-DU or SgNB) of a node in a wireless network, in accordance with various exemplary embodiments of the present disclosure.
  • DU distributed unit
  • the second DU can comprise a base station, gNB, en-gNB, ng-eNB, etc. of a radio access network (RAN).
  • RAN radio access network
  • the exemplary method and/or procedure is illustrated in Figure 9 by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown in Figure 9 .
  • the exemplary method and/or procedure shown in Figure 9 can be complimentary to the exemplary methods and/or procedures shown in Figures 8 and 10 .
  • the exemplary methods and/or procedures shown in Figures 8-10 are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove.
  • Optional operations are indicated by dashed lines.
  • the exemplary method and/or procedure can include the operations of block 910, where the second DU can receive, from the CU in response to a first event, a setup request comprising a lower-layer configuration of a UE in communication with the first DU prior to the first event.
  • the exemplary method and/or procedure can include the operations of block 920, where the second DU can determine a first delta configuration indicating one or more differences between a lower-layer configuration of the second DU and the received lower-layer configuration the UE.
  • the exemplary method and/or procedure can include the operations of block 930, where the second DU can send, to the CU, a setup response comprising the first delta configuration.
  • the first event can be one of a mobility event and a dual-connectivity event.
  • the lower-layer configuration of the UE can include the RRM configuration used by the first DU with respect to the UE and/or the access stratum configuration used by the first DU with respect to the UE.
  • Figure 10 illustrates an exemplary method and/or procedure performed by a first distributed unit (DU, e.g., gNB-DU or SgNB) of a node in a wireless network, in accordance with various exemplary embodiments of the present disclosure.
  • DU distributed unit
  • the first DU can comprise a base station, gNB, en-gNB, ng-eNB, etc. of a radio access network (RAN).
  • RAN radio access network
  • the exemplary method and/or procedure is illustrated in Figure 10 by blocks in a particular order, this order is exemplary and the operations corresponding to the blocks can be performed in different orders, and can be combined and/or divided into blocks having different functionality than shown in Figure 10 .
  • the exemplary method and/or procedure shown in Figure 10 can be complimentary to the exemplary methods and/or procedures shown in Figures 8-9 .
  • the exemplary methods and/or procedures shown in Figures 8-10 are capable of being used cooperatively to provide the benefits, advantages, and/or solutions to problems described hereinabove.
  • Optional operations are indicated by dashed lines.
  • the exemplary methods and/or procedures can include the operations of block 1010, where the first DU can receive a context setup request from the CU. In some embodiments, the exemplary methods and/or procedures can include the operations of block 1020, where the first DU can send, to the CU, one or more measurements made by the UE. In such embodiments, the exemplary methods and/or procedures can include the operations of block 1030, where the first DU can receive, from the CU, a request for the lower-layer configuration of the UE subsequent to sending the one or more measurements.
  • the exemplary method and/or procedure can include the operations of block 1040, where the first DU can send to the CU, in advance of occurrence of a first event concerning a UE that is in communication with the first DU, a lower-layer configuration of the UE.
  • the lower-layer configuration of the UE can be sent in response to the particular received request.
  • the lower-layer configuration of the UE can include the RRM configuration used by the first DU with respect to the UE and/or the access stratum configuration used by the first DU with respect to the UE.
  • the first event can be one of a mobility event and a dual-connectivity event.
  • the exemplary method and/or procedure can also include the operations of block 1050, where the first DU can receive, from the CU, a modification request comprising a first delta configuration indicating one or more differences between a lower-layer configuration of the second DU and the lower-layer configuration of the UE.
  • the modification request can further include a second delta configuration indicating one or more differences between higher-layer configurations of the UE with respect to the first and the second DUs.
  • the exemplary method and/or procedure can also include the operations of block 1060, where the first DU can send, to the UE, a modification request comprising the first delta configuration.
  • the modification request can also include the second delta configuration.
  • a wireless network such as the example wireless network illustrated in Figure 11 .
  • the wireless network of Figure 11 only depicts network 1106, network nodes 1160 and 1160b, and WDs 1110, 1110b, and 1110c.
  • a wireless network can 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 1160 and wireless device (WD) 1110 are depicted with additional detail.
  • the wireless network can 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 can 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 can be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network can 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 1106 can 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 1160 and WD 1110 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 can 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 can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • 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 can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station can be a relay node or a relay donor node controlling a relay.
  • a network node can 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 can 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
  • network nodes can 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 1160 can include processing circuitry 1170, device readable medium 1180, interface 1190, auxiliary equipment 1184, power source 1186, power circuitry 1187, and antenna 1162.
  • network node 1160 illustrated in the example wireless network of Figure 11 can represent a device that can include the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node can comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein.
  • network node 1160 can comprise multiple different physical components that make up a single illustrated component (e.g. , device readable medium 1180 can comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 1160 can comprise multiple physically separate components (e.g. , a NodeB component and a RNC component, or a BTS component and a BSC component, etc .), which can each have their own respective components.
  • network node 1160 can comprise multiple separate components (e.g. , BTS and BSC components)
  • one or more of the separate components can be shared among several network nodes.
  • a single RNC can control multiple NodeB's.
  • each unique NodeB and RNC pair can in some instances be considered a single separate network node.
  • network node 1160 can be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 1160 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1160.
  • Processing circuitry 1170 can be 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 1170 can include processing information obtained by processing circuitry 1170 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 1170 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 1170 can 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 1160 components, such as device readable medium 1180, network node 1160 functionality.
  • processing circuitry 1170 can execute instructions stored in device readable medium 1180 or in memory within processing circuitry 1170. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 1170 can include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 1170 can include one or more of radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174.
  • radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174 can 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 1172 and baseband processing circuitry 1174 can be on the same chip or set of chips, boards, or units
  • processing circuitry 1170 executing instructions stored on device readable medium 1180 or memory within processing circuitry 1170.
  • some or all of the functionality can be provided by processing circuitry 1170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 1170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1170 alone or to other components of network node 1160, but are enjoyed by network node 1160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 1180 can 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 can be used by processing circuitry 1170.
  • 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
  • Device readable medium 1180 can 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 1170 and, utilized by network node 1160.
  • Device readable medium 1180 can be used to store any calculations made by processing circuitry 1170 and/or any data received via interface 1190.
  • processing circuitry 1170 and device readable medium 1180 can be considered to be integrated.
  • Interface 1190 is used in the wired or wireless communication of signalling and/or data between network node 1160, network 1106, and/or WDs 1110. As illustrated, interface 1190 can comprise port(s)/terminal(s) 1194 to send and receive data, for example to and from network 1106 over a wired connection. Interface 1190 also can include radio front end circuitry 1192 that can be coupled to, or in certain embodiments a part of, antenna 1162. Radio front end circuitry 1192 can comprise filters 1198 and amplifiers 1196. Radio front end circuitry 1192 can be connected to antenna 1162 and processing circuitry 1170. Radio front end circuitry can be configured to condition signals communicated between antenna 1162 and processing circuitry 1170.
  • Radio front end circuitry 1192 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1192 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1198 and/or amplifiers 1196. The radio signal can then be transmitted via antenna 1162. Similarly, when receiving data, antenna 1162 can collect radio signals which are then converted into digital data by radio front end circuitry 1192. The digital data can be passed to processing circuitry 1170. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • network node 1160 may not include separate radio front end circuitry 1192, instead, processing circuitry 1170 can comprise radio front end circuitry and can be connected to antenna 1162 without separate radio front end circuitry 1192.
  • processing circuitry 1170 can comprise radio front end circuitry and can be connected to antenna 1162 without separate radio front end circuitry 1192.
  • all or some of RF transceiver circuitry 1172 can be considered a part of interface 1190.
  • interface 1190 can include one or more ports or terminals 1194, radio front end circuitry 1192, and RF transceiver circuitry 1172, as part of a radio unit (not shown), and interface 1190 can communicate with baseband processing circuitry 1174, which is part of a digital unit (not shown).
  • Antenna 1162 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1162 can be coupled to radio front end circuitry 1190 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1162 can 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 can be used to transmit/receive radio signals in any direction
  • a sector antenna can be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna can be referred to as MIMO.
  • antenna 1162 can be separate from network node 1160 and can be connectable to network node 1160 through an interface or port.
  • Antenna 1162, interface 1190, and/or processing circuitry 1170 can 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 can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1162, interface 1190, and/or processing circuitry 1170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 1187 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1160 with power for performing the functionality described herein. Power circuitry 1187 can receive power from power source 1186. Power source 1186 and/or power circuitry 1187 can be configured to provide power to the various components of network node 1160 in a form suitable for the respective components ( e.g., at a voltage and current level needed for each respective component). Power source 1186 can either be included in, or external to, power circuitry 1187 and/or network node 1160.
  • network node 1160 can 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 1187.
  • power source 1186 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1187. The battery can provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, can also be used.
  • network node 1160 can include additional components beyond those shown in Figure 11 that can 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 1160 can include user interface equipment to allow and/or facilitate input of information into network node 1160 and to allow and/or facilitate output of information from network node 1160. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1160.
  • 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 WD can be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly can 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 WD can be configured to transmit and/or receive information without direct human interaction.
  • a WD can 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 WD 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 ..
  • a WD can support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and can 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 WD can represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD can be a UE implementing the 3GPP 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 WD can 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 WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
  • wireless device 1110 can include antenna 1111, interface 1114, processing circuitry 1120, device readable medium 1130, user interface equipment 1132, auxiliary equipment 1134, power source 1136 and power circuitry 1137.
  • WD 1110 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 1110.
  • Antenna 1111 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1114.
  • antenna 1111 can be separate from WD 1110 and be connectable to WD 1110 through an interface or port.
  • Antenna 1111, interface 1114, and/or processing circuitry 1120 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna 1111 can be considered an interface.
  • interface 1114 can comprise radio front end circuitry 1112 and antenna 1111.
  • Radio front end circuitry 1112 comprise one or more filters 1118 and amplifiers 1116.
  • Radio front end circuitry 1114 is connected to antenna 1111 and processing circuitry 1120, and can be configured to condition signals communicated between antenna 1111 and processing circuitry 1120.
  • Radio front end circuitry 1112 can be coupled to or a part of antenna 1111.
  • WD 1110 may not include separate radio front end circuitry 1112; rather, processing circuitry 1120 can comprise radio front end circuitry and can be connected to antenna 1111.
  • some or all of RF transceiver circuitry 1122 can be considered a part of interface 1114.
  • Radio front end circuitry 1112 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1112 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1118 and/or amplifiers 1116. The radio signal can then be transmitted via antenna 1111. Similarly, when receiving data, antenna 1111 can collect radio signals which are then converted into digital data by radio front end circuitry 1112. The digital data can be passed to processing circuitry 1120. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • Processing circuitry 1120 can 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 WD 1110 components, such as device readable medium 1130, WD 1110 functionality.
  • processing circuitry 1120 can execute instructions stored in device readable medium 1130 or in memory within processing circuitry 1120 to provide the functionality disclosed herein.
  • processing circuitry 1120 can include one or more of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126.
  • the processing circuitry can comprise different components and/or different combinations of components.
  • processing circuitry 1120 of WD 1110 can comprise a SOC.
  • RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 can be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 1124 and application processing circuitry 1126 can be combined into one chip or set of chips, and RF transceiver circuitry 1122 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1122 and baseband processing circuitry 1124 can be on the same chip or set of chips, and application processing circuitry 1126 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 can be combined in the same chip or set of chips.
  • RF transceiver circuitry 1122 can be a part of interface 1114.
  • RF transceiver circuitry 1122 can condition RF signals for processing circuitry 1120.
  • processing circuitry 1120 executing instructions stored on device readable medium 1130, which in certain embodiments can be a computer-readable storage medium.
  • some or all of the functionality can be provided by processing circuitry 1120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 1120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1120 alone or to other components of WD 1110, but are enjoyed by WD 1110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 1120 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1120, can include processing information obtained by processing circuitry 1120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1110, 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 1120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1110, 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 1130 can 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 1120.
  • Device readable medium 1130 can 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 can be used by processing circuitry 1120.
  • processing circuitry 1120 and device readable medium 1130 can be considered to be integrated.
  • User interface equipment 1132 can include components that allow and/or facilitate a human user to interact with WD 1110. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1132 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 1110. The type of interaction can vary depending on the type of user interface equipment 1132 installed in WD 1110. For example, if WD 1110 is a smart phone, the interaction can be via a touch screen; if WD 1110 is a smart meter, the interaction can 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 1132 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1132 can be configured to allow and/or facilitate input of information into WD 1110, and is connected to processing circuitry 1120 to allow and/or facilitate processing circuitry 1120 to process the input information. User interface equipment 1132 can 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 1132 is also configured to allow and/or facilitate output of information from WD 1110, and to allow and/or facilitate processing circuitry 1120 to output information from WD 1110.
  • User interface equipment 1132 can 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 1132, WD 1110 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.
  • Auxiliary equipment 1134 is operable to provide more specific functionality which may not be generally performed by WDs. This can 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 1134 can vary depending on the embodiment and/or scenario.
  • Power source 1136 can, 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, can also be used.
  • WD 1110 can further comprise power circuitry 1137 for delivering power from power source 1136 to the various parts of WD 1110 which need power from power source 1136 to carry out any functionality described or indicated herein.
  • Power circuitry 1137 can in certain embodiments comprise power management circuitry.
  • Power circuitry 1137 can additionally or alternatively be operable to receive power from an external power source; in which case WD 1110 can 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 1137 can also in certain embodiments be operable to deliver power from an external power source to power source 1136. This can be, for example, for the charging of power source 1136. Power circuitry 1137 can perform any converting or other modification to the power from power source 1136 to make it suitable for supply to the respective components of WD 1110.
  • Figure 12 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 can 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 can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 12200 can be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 1200 is one example of a WD 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
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile communications
  • LTE Long Term Evolution
  • 5G 5G
  • the term WD and UE can be used interchangeable. Accordingly, although Figure 12 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE 1200 can include processing circuitry 1201 that is operatively coupled to input/output interface 1205, radio frequency (RF) interface 1209, network connection interface 1211, memory 1215 including random access memory (RAM) 1217, read-only memory (ROM) 1219, and storage medium 1221 or the like, communication subsystem 1231, power source 1233, and/or any other component, or any combination thereof.
  • Storage medium 1221 can include operating system 1223, application program 1225, and data 1227. In other embodiments, storage medium 1221 can include other similar types of information.
  • Certain UEs can utilize all of the components shown in Figure 12 , or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 1201 can be configured to process computer instructions and data.
  • Processing circuitry 1201 can 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 1201 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
  • input/output interface 1205 can be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 1200 can be configured to use an output device via input/output interface 1205.
  • An output device can use the same type of interface port as an input device.
  • a USB port can be used to provide input to and output from UE 1200.
  • the output device can 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 1200 can be configured to use an input device via input/output interface 1205 to allow and/or facilitate a user to capture information into UE 1200.
  • the input device can 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 can include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor can 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 can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 1209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 1211 can be configured to provide a communication interface to network 1243a.
  • Network 1243a can 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 1243a can comprise a Wi-Fi network.
  • Network connection interface 1211 can 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 1211 can implement receiver and transmitter functionality appropriate to the communication network links ( e.g. , optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
  • RAM 1217 can be configured to interface via bus 1202 to processing circuitry 1201 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 1219 can be configured to provide computer instructions or data to processing circuitry 1201.
  • ROM 1219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 1221 can 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 1221 can be configured to include operating system 1223, application program 1225 such as a web browser application, a widget or gadget engine or another application, and data file 1227.
  • Storage medium 1221 can store, for use by UE 1200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 1221 can 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 external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a removable user
  • Storage medium 1221 can allow and/or facilitate UE 1200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to offload data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium 1221, which can comprise a device readable medium.
  • processing circuitry 1201 can be configured to communicate with network 1243b using communication subsystem 1231.
  • Network 1243a and network 1243b can be the same network or networks or different network or networks.
  • Communication subsystem 1231 can be configured to include one or more transceivers used to communicate with network 1243b.
  • communication subsystem 1231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.12, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver can include transmitter 1233 and/or receiver 1235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links ( e.g. , frequency allocations and the like). Further, transmitter 1233 and receiver 1235 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.
  • the communication functions of communication subsystem 1231 can 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 1231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 1243b can 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 1243b can be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 1213 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1200.
  • communication subsystem 1231 can be configured to include any of the components described herein.
  • processing circuitry 1201 can be configured to communicate with any of such components over bus 1202.
  • any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1201 perform the corresponding functions described herein.
  • the functionality of any of such components can be partitioned between processing circuitry 1201 and communication subsystem 1231.
  • the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
  • FIG. 13 is a schematic block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments can be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which can 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 can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1300 hosted by one or more of hardware nodes 1330. 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 can be entirely virtualized.
  • the functions can be implemented by one or more applications 1320 (which can 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 1320 are run in virtualization environment 1300 which provides hardware 1330 comprising processing circuitry 1360 and memory 1390.
  • Memory 1390 contains instructions 1395 executable by processing circuitry 1360 whereby application 1320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 1300 can comprise general-purpose or special-purpose network hardware devices 1330 comprising a set of one or more processors or processing circuitry 1360, which can 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 1360 which can 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 can comprise memory 1390-1 which can be non-persistent memory for temporarily storing instructions 1395 or software executed by processing circuitry 1360.
  • Each hardware device can comprise one or more network interface controllers (NICs) 1370, also known as network interface cards, which include physical network interface 1380.
  • NICs network interface controllers
  • Each hardware device can also include non-transitory, persistent, machine-readable storage media 1390-2 having stored therein software 1395 and/or instructions executable by processing circuitry 1360.
  • Software 1395 can include any type of software including software for instantiating one or more virtualization layers 1350 (also referred to as hypervisors), software to execute virtual machines 1340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 1340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1350 or hypervisor. Different embodiments of the instance of virtual appliance 1320 can be implemented on one or more of virtual machines 1340, and the implementations can be made in different ways.
  • processing circuitry 1360 executes software 1395 to instantiate the hypervisor or virtualization layer 1350, which can sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 1350 can present a virtual operating platform that appears like networking hardware to virtual machine 1340.
  • hardware 1330 can be a standalone network node with generic or specific components.
  • Hardware 1330 can comprise antenna 13225 and can implement some functions via virtualization.
  • hardware 1330 can 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) 13100, which, among others, oversees lifecycle management of applications 1320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV can 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.
  • virtual machine 1340 can 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 1340, and that part of hardware 1330 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 1340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 13200 that each include one or more transmitters 13220 and one or more receivers 13210 can be coupled to one or more antennas 13225.
  • Radio units 13200 can communicate directly with hardware nodes 1330 via one or more appropriate network interfaces and can 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 13230 which can alternatively be used for communication between the hardware nodes 1330 and radio units 13200.
  • FIG. 14 shows a high-level diagram of a communication system, in accordance with various exemplary embodiments of the present disclosure.
  • the communication system can include telecommunication network 1410, such as a 3GPP-type cellular network, which can comprise access network 1411, such as a radio access network, and core network 1414.
  • Access network 1411 can comprise a plurality of base stations 1412a, 1412b, 1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1413a, 1413b, 1413c.
  • Each base station 1412a, 1412b, 1412c is connectable to core network 1414 over a wired or wireless connection 1415.
  • a first UE 1491 located in coverage area 1413c can be configured to wirelessly connect to, or be paged by, the corresponding base station 1412c.
  • a second UE 1492 in coverage area 1413a is wirelessly connectable to the corresponding base station 1412a. While a plurality of UEs 1491, 1492 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 1412.
  • Telecommunication network 1410 is itself connected to host computer 1430, which can 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 1430 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider.
  • Connections 1421 and 1422 between telecommunication network 1410 and host computer 1430 can extend directly from core network 1414 to host computer 1430 or can go via an optional intermediate network 1420.
  • Intermediate network 1420 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1420, if any, can be a backbone network or the Internet; in particular, intermediate network 1420 can comprise two or more sub-networks (not shown).
  • the communication system of Figure 14 as a whole enables connectivity between the connected UEs 1491, 1492 and host computer 1430.
  • the connectivity can be described as an over-the-top (OTT) connection 1450.
  • Host computer 1430 and the connected UEs 1491, 1492 are configured to communicate data and/or signaling via OTT connection 1450, using access network 1411, core network 1414, any intermediate network 1420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 1450 can be transparent in the sense that the participating communication devices through which OTT connection 1450 passes are unaware of routing of uplink and downlink communications.
  • base station 1412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1430 to be forwarded (e.g., handed over) to a connected UE 1491. Similarly, base station 1412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1491 towards the host computer 1430.
  • host computer 1510 can comprise hardware 1515 including communication interface 1516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1500.
  • Host computer 1510 can further comprise processing circuitry 1518, which can have storage and/or processing capabilities.
  • processing circuitry 1518 can 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 1510 can further comprise software 1511, which is stored in or accessible by host computer 1510 and executable by processing circuitry 1518.
  • Software 1511 can include host application 1512.
  • Host application 1512 can be operable to provide a service to a remote user, such as UE 1530 connecting via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the remote user, host application 1512 can provide user data which is transmitted using OTT connection 1550.
  • Communication system 1500 can also include base station 1520 provided in a telecommunication system and comprising hardware 1525 enabling it to communicate with host computer 1510 and with UE 1530.
  • Hardware 1525 can include communication interface 1526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1500, as well as radio interface 1527 for setting up and maintaining at least wireless connection 1570 with UE 1530 located in a coverage area (not shown in Figure 15 ) served by base station 1520.
  • Communication interface 1526 can be configured to facilitate connection 1560 to host computer 1510. Connection 1560 can be direct or it can pass through a core network (not shown in Figure 15 ) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1525 of base station 1520 can also include processing circuitry 1528, which can 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 1520 further has software 1521 stored internally or accessible via an external connection.
  • Communication system 1500 can also include UE 1530 already referred to. Its hardware 1535 can include radio interface 1537 configured to set up and maintain wireless connection 1570 with a base station serving a coverage area in which UE 1530 is currently located. Hardware 1535 of UE 1530 can also include processing circuitry 1538, which can 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 1530 can further comprise software 1531, which is stored in or accessible by UE 1530 and executable by processing circuitry 1538. Software 1531 can include client application 1532. Client application 1532 can be operable to provide a service to a human or non-human user via UE 1530, with the support of host computer 1510.
  • an executing host application 1512 can communicate with the executing client application 1532 via OTT connection 1550 terminating at UE 1530 and host computer 1510.
  • client application 1532 can receive request data from host application 1512 and provide user data in response to the request data.
  • OTT connection 1550 can transfer both the request data and the user data.
  • Client application 1532 can interact with the user to generate the user data that it provides.
  • host computer 1510, base station 1520 and UE 1530 illustrated in Figure 15 can be similar or identical to host computer 1430, one of base stations 1412a, 1412b, 1412c and one of UEs 1491, 1492 of Figure 14 , respectively.
  • the inner workings of these entities can be as shown in Figure 15 and independently, the surrounding network topology can be that of Figure 14 .
  • OTT connection 1550 has been drawn abstractly to illustrate the communication between host computer 1510 and UE 1530 via base station 1520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure can determine the routing, which it can be configured to hide from UE 1530 or from the service provider operating host computer 1510, or both. While OTT connection 1550 is active, the network infrastructure can 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 1570 between UE 1530 and base station 1520 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 1530 using OTT connection 1550, in which wireless connection 1570 forms the last segment.
  • the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality-of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network.
  • QoS quality-of-service
  • a measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 1550 can be implemented in software 1511 and hardware 1515 of host computer 1510 or in software 1531 and hardware 1535 of UE 1530, or both.
  • sensors can be deployed in or in association with communication devices through which OTT connection 1550 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1511, 1531 can compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1550 can include message format, retransmission settings, preferred routing etc .; the reconfiguring need not affect base station 1520, and it can be unknown or imperceptible to base station 1520. Such procedures and functionalities can be known and practiced in the art.
  • measurements can involve proprietary UE signaling facilitating host computer 1510's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 1511 and 1531 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 1550 while it monitors propagation times, errors etc.
  • FIG 16 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments of the present disclosure.
  • the communication system includes a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the host computer provides user data.
  • substep 1611 (which can be optional) of step 1610, 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 1630 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 1640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 17 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments of the present disclosure.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 17 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 can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1730 (which can be optional), the UE receives the user data carried in the transmission.
  • FIG. 18 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments of the present disclosure.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section.
  • step 1810 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1820, the UE provides user data.
  • substep 1821 (which can be optional) of step 1820, the UE provides the user data by executing a client application.
  • substep 1811 (which can be optional) of step 1810, 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 can further consider user input received from the user.
  • the UE initiates, in substep 1830 (which can be optional), transmission of the user data to the host computer.
  • step 1840 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.
  • FIG 19 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with various embodiments of the present disclosure.
  • the communication system includes a host computer, a base station and a UE which can be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure 19 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 1930 (which can be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can 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.

Landscapes

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

Claims (18)

  1. Verfahren, das von einer zentralen Einheit, CU, (110) durchgeführt wird, die zusammen mit einer ersten und zweiten verteilten Einheit, DU, (120, 130) einen Knoten (100, 1160) eines drahtlosen Kommunikationsnetzwerks bildet, wobei das Verfahren umfasst:
    Empfangen (830), von der ersten DU vor Auftreten eines ersten Ereignisses, das eine Benutzerausrüstung, UE, (1110) betrifft, die mit der ersten DU in Kommunikation steht, einer Konfiguration unterer Schichten der UE;
    Speichern (840) der Konfiguration unterer Schichten der UE;
    Senden (870) einer Setup-Anfrage, die die gespeicherte Konfiguration unterer Schichten der UE umfasst, an die zweite DU;
    Empfangen (880) einer Setup-Antwort von der zweiten DU, die eine erste Delta-Konfiguration umfasst, welche einen oder mehrere Unterschiede zwischen einer Konfiguration unterer Schichten der zweiten DU und der gespeicherten Konfiguration unterer Schichten anzeigt; und
    Senden (890) einer Modifizierungsanfrage, die die erste Delta-Konfiguration umfasst, an die erste DU, wobei die Konfiguration unterer Schichten der UE mindestens eine der Folgenden umfasst:
    eine Radio Resource Management-, RRM, Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird; und
    eine Access Stratum-Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird.
  2. Verfahren nach Anspruch 1, das weiter das Bestimmen (860), dass das erste Ereignis ausgelöst werden soll, auf Basis einer oder mehrerer Messungen umfasst, die von der ersten DU empfangen werden.
  3. Verfahren nach einem der Ansprüche 1-2, wobei das Senden (870) der Setup-Anfragenachricht in Antwort auf das Bestimmen (860), dass das erste Ereignis ausgelöst werden soll, erfolgt.
  4. Verfahren nach einem der Ansprüche 1-3, wobei es sich beim ersten Ereignis um eines aus einem Mobilitätsereignis und einem Dual-Konnektivitäts-Ereignis handelt.
  5. Verfahren nach einem der Ansprüche 1-4, wobei die Modifikationsanfrage weiter eine zweite Delta-Konfiguration einschließt, die einen oder mehrere Unterschiede zwischen Konfigurationen höherer Schichten der UE in Bezug auf die erste und die zweite DU anzeigen.
  6. Verfahren nach Anspruch 5, das weiter das Erzeugen (885) der zweiten Delta-Konfiguration umfasst.
  7. Verfahren nach einem der Ansprüche 1-6, das weiter das Senden (810) einer Kontext-Setup-Anfrage an die erste DU umfasst, wobei in Antwort auf die Kontext-Setup-Anfrage die Konfiguration unterer Schichten der UE empfangen wird.
  8. Verfahren nach einem der Ansprüche 1-6, das in Antwort auf eine oder mehrere von der UE vorgenommene Messungen, die von der ersten DU empfangen wurden, weiter das Senden (820) einer Anfrage an die erste DU bezüglich der Konfiguration unterer Schichten der UE umfasst.
  9. Verfahren nach einem der Ansprüche 1-8, weiter umfassend:
    Empfangen (850) einer oder mehrerer Nachbarzellen-Messungen, die von der UE vorgenommen wurden;
    Bestimmen (850) einer weiteren Konfiguration unterer Schichten der UE auf Basis der empfangenen Nachbarzellen-Messungen, wobei die Setup-Anfrage die weitere Konfiguration unterer Schichten umfasst.
  10. Verfahren, das von einer zweiten verteilten Einheit, DU, (120) durchgeführt wird, die zusammen mit einer zentralen Einheit, CU, (100) und einer ersten DU (110) einen Knoten (100, 1160) eines drahtlosen Kommunikationsnetzwerks bildet, wobei das Verfahren umfasst:
    Empfangen (910), von der CU in Antwort auf ein erstes Ereignis, einer Setup-Anfrage, die eine Konfiguration unterer Schichten einer mit der ersten DU in Kommunikation stehenden Benutzerausrüstung, UE, (1110) vor dem ersten Ereignis umfasst;
    Bestimmen (920) einer ersten Delta-Konfiguration, die einen oder mehrere Unterschiede zwischen einer Konfiguration unterer Schichten der zweiten DU und der empfangenen Konfiguration unterer Schichten der UE anzeigt; und
    Senden (930) einer Setup-Antwort an die CU, die die erste Delta-Konfiguration umfasst, wobei die Konfiguration unterer Schichten der UE mindestens eine der Folgenden umfasst:
    eine Radio Resource Management-, RRM, Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird; und
    eine Access Stratum-Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird.
  11. Verfahren nach Anspruch 10, wobei es sich beim ersten Ereignis um eines aus einem Mobilitätsereignis und einem Dual-Konnektivitäts-Ereignis handelt.
  12. Verfahren, das von einer ersten verteilten Einheit, DU, (110) durchgeführt wird, die zusammen mit einer zentralen Einheit, CU, (100) und einer zweiten DU (120) einen Knoten (100, 1160) eines drahtlosen Kommunikationsnetzwerks bildet, wobei das Verfahren umfasst:
    Senden (1040), vor Auftreten eines ersten Ereignisses, das eine Benutzerausrüstung, UE, (1110) betrifft, die mit der ersten DU in Kommunikation steht, einer Konfiguration unterer Schichten der UE an die CU;
    Empfangen (1050) einer Modifizierungsanfrage, die eine erste Delta-Konfiguration umfasst, welche einen oder mehrere Unterschiede zwischen einer Konfiguration unterer Schichten der zweiten DU und der Konfiguration unterer Schichten der UE anzeigt, von der CU; und
    Senden (1060) einer Modifizierungsanfrage, die die erste Delta-Konfiguration umfasst, an die UE, wobei die Konfiguration unterer Schichten der UE mindestens eine der Folgenden umfasst:
    eine Radio Resource Management-, RRM, Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird; und
    eine Access Stratum-Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird.
  13. Verfahren nach Anspruch 12, wobei es sich beim ersten Ereignis um eines aus einem Mobilitätsereignis und einem Dual-Konnektivitäts-Ereignis handelt.
  14. Verfahren nach einem der Ansprüche 12-13, wobei die Modifikationsanfrage weiter eine zweite Delta-Konfiguration einschließt, die einen oder mehrere Unterschiede zwischen Konfigurationen höherer Schichten der UE in Bezug auf die erste und die zweite DU anzeigen.
  15. Verfahren nach einem der Ansprüche 12-14, das weiter das Empfangen (1010) einer Kontext-Setup-Anfrage von der CU umfasst, wobei in Antwort auf die Kontext-Setup-Anfrage die Konfiguration unterer Schichten der UE gesendet wird.
  16. Verfahren nach einem der Ansprüche 12-14, weiter umfassend:
    Senden (1020) einer oder mehrerer Messungen, die von der UE vorgenommen wurden, an die CU; und
    Empfangen (1030) einer Anfrage bezüglich der Konfiguration unterer Schichten der UE von der CU im Anschluss an das Senden der einen oder der mehreren Messungen.
  17. Zentrale Einheit, CU, (110) eines Netzwerkknotens (100, 1160), der für Betrieb in einem drahtlosen Kommunikationsnetzwerk konfiguriert ist, wobei die CU so eingerichtet ist, dass sie:
    von einer ersten verteilten Einheit, DU, (120) vor Auftreten eines ersten Ereignisses, das eine Benutzerausrüstung, UE, (1110) betrifft, die mit der ersten DU in Kommunikation steht, eine Konfiguration unterer Schichten einer Benutzerausrüstung, UE, empfängt (830);
    die Konfiguration unterer Schichten der UE speichert (840);
    eine Setup-Anfrage, die die gespeicherte Konfiguration unterer Schichten der UE umfasst, an eine zweite DU (130) sendet (870);
    von der zweiten DU eine Setup-Antwort empfängt (880), die eine erste Delta-Konfiguration umfasst, welche einen oder mehrere Unterschiede zwischen einer Konfiguration unterer Schichten der zweiten DU und der gespeicherten Konfiguration unterer Schichten anzeigt; und
    eine Modifizierungsanfrage, die die erste Delta-Konfiguration umfasst, an die erste DU sendet (890), wobei die Konfiguration unterer Schichten der UE mindestens eine der Folgenden umfasst:
    eine Radio Resource Management-, RRM, Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird; und
    eine Access Stratum-Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird.
  18. Erste verteilte Einheit, DU, (120) eines Netzwerkknotens (100, 1160), der für Betrieb in einem drahtlosen Kommunikationsnetzwerk konfiguriert ist, wobei die erste DU so eingerichtet ist, dass sie:
    vor Auftreten eines ersten Ereignisses, das eine Benutzerausrüstung, UE, (1110) betrifft, die mit der ersten DU in Kommunikation steht, eine Konfiguration unterer Schichten der UE an eine zentrale Einheit, CU, (110) sendet (1040);
    von der CU eine Modifizierungsanfrage empfängt (1050), die eine erste Delta-Konfiguration umfasst, welche einen oder mehrere Unterschiede zwischen einer Konfiguration unterer Schichten der zweiten DU und der Konfiguration unterer Schichten der UE anzeigt; und
    eine Modifizierungsanfrage, die die erste Delta-Konfiguration umfasst, an die UE sendet (1060), wobei die Konfiguration unterer Schichten der UE mindestens eine der Folgenden umfasst:
    eine Radio Resource Management-, RRM, Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird; und
    eine Access Stratum-Konfiguration, die von der ersten DU in Bezug auf die UE verwendet wird.
EP18830011.5A 2018-01-12 2018-12-11 Deltakonfiguration in geteilter cu-du-ran-architektur Active EP3738340B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862616912P 2018-01-12 2018-01-12
PCT/SE2018/051271 WO2019139517A1 (en) 2018-01-12 2018-12-11 Delta configuration in split cu-du ran architecture

Publications (2)

Publication Number Publication Date
EP3738340A1 EP3738340A1 (de) 2020-11-18
EP3738340B1 true EP3738340B1 (de) 2021-02-24

Family

ID=64949363

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18830011.5A Active EP3738340B1 (de) 2018-01-12 2018-12-11 Deltakonfiguration in geteilter cu-du-ran-architektur

Country Status (4)

Country Link
US (1) US11064405B2 (de)
EP (1) EP3738340B1 (de)
CN (1) CN111567088B (de)
WO (1) WO2019139517A1 (de)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019160743A1 (en) * 2018-02-14 2019-08-22 Google Llc Full and delta configuration in a central unit-distributed unit architecture
WO2019245339A1 (ko) * 2018-06-21 2019-12-26 삼성전자주식회사 이동 통신 시스템에서 기지국 노드 간 패킷 복제 동작 동기화 방법 및 장치
EP3813475A4 (de) * 2018-06-21 2022-02-09 Ntt Docomo, Inc. Netzwerkknoten
EP3861661B1 (de) * 2018-10-03 2023-12-06 Telefonaktiebolaget LM Ericsson (publ) Komprimierung von benutzerdaten, die zwischen einer geteilten zentraleinheit einer unteren schicht und einer funkeinheit übertragen werden, unter verwendung von bitmap-darstellungen übertragen werden
JP7488255B2 (ja) * 2019-04-26 2024-05-21 株式会社Ｎｔｔドコモ 無線通信ノード
US11082900B1 (en) 2020-01-28 2021-08-03 PanPsy Technologies, LLC Wireless device and wireless network processes based on wireless device type
EP4186273A4 (de) * 2020-10-22 2023-07-26 ZTE Corporation Verfahren und vorrichtungen zur verbesserung von integrierten zugangs-backhaul-netzwerken für new radio
CN112511980B (zh) * 2020-11-06 2022-09-13 中国联合网络通信集团有限公司 一种通信系统、方法及装置
US11304109B1 (en) 2020-11-10 2022-04-12 Cisco Technology, Inc. Techniques to prevent and/or minimize user equipment service disruptions in virtualized radio access network architectures
WO2023130246A1 (en) * 2022-01-05 2023-07-13 Qualcomm Incorporated Uu adaptation layer support for layer two relaying
WO2024022687A1 (en) * 2022-07-29 2024-02-01 Nokia Technologies Oy Inter cell beam management
CN117979442A (zh) * 2022-10-18 2024-05-03 大唐移动通信设备有限公司 一种数据传输方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2479534B (en) * 2010-04-12 2014-11-12 Samsung Electronics Co Ltd Handover with carrier aggregation
WO2018009340A1 (en) * 2016-07-05 2018-01-11 Intel Corporation Systems, methods and devices for control-user plane separation for 5g radio access networks
US10568004B2 (en) * 2017-03-23 2020-02-18 Futurewei Technologies, Inc. Layer 2 (L2) mobility for new radio (NR) networks
US10469358B2 (en) * 2017-05-18 2019-11-05 Qualcomm Incorporated Wireless multihop relay
US20180376380A1 (en) * 2017-06-23 2018-12-27 Huawei Technologies Co., Ltd. Exposure of capabilities of central units and distributed units in base station entities for admission control

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN111567088A (zh) 2020-08-21
US11064405B2 (en) 2021-07-13
CN111567088B (zh) 2024-02-06
WO2019139517A1 (en) 2019-07-18
US20200120559A1 (en) 2020-04-16
EP3738340A1 (de) 2020-11-18

Similar Documents

Publication Publication Date Title
EP3738340B1 (de) Deltakonfiguration in geteilter cu-du-ran-architektur
US11910460B2 (en) Assistance information for SPCell selection
US20200053815A1 (en) Tunnel Modification for Split Bearers in Multi-RAT Dual Connectivity (MR-DC) and NR-NR Dual Connectivity (NR-DC)
EP3767857A1 (de) Vermeidung von mehrfachen neuübertragungen von durch 5g-nas-transport transportierter signalisierung
US11659451B2 (en) Serving gateway control plane function to manage a plurality of serving gateway user plane functions, and mobility management entity to communicate with the same
US20230180065A1 (en) Methods and Apparatuses for Early Data Forwarding in Conditional Handover of a UE in Multi-Connectivity
EP3964014B1 (de) Zweistufiger konfliktfreier zufallszugriff
EP3753295B1 (de) Übergabe zwischen funkzugangstechnologie
WO2022074620A1 (en) Handling conditional pscell change (cpc) upon sn release
US20220408325A1 (en) Conditional Configuration in Multi-Connectivity Operation
WO2020032846A1 (en) Pdu session information over f1 for uplink pdu session ambr traffic policing
EP3864927B1 (de) Verfahren und vorrichtung für übertragungszuverlässigkeit
US20230269646A1 (en) Dual Active Protocol Stack (DAPS) Handover During URLLC Packet Duplication
WO2021013753A2 (en) Methods, apparatus and machine-readable media relating to dual- or multi-connectivity in a wireless communication network
EP4193634A1 (de) Referenzsignalstrahlkonfiguration in einem drahtloskommunikationsnetzwerk
WO2021206616A1 (en) Multi-connectivity operation in a wireless communication network
US20210227382A1 (en) To Increase Security of Dual Connectivity
EP4282223B1 (de) Signalisierung zur freigabe einer sekundärzellengruppenkonfiguration
WO2024035291A1 (en) Reference configuration for l1/l2 inter-cell mobility candidate(s)
WO2020222093A1 (en) Method for load coordination in multi-radio secondary node selection

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602018013172

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0036000000

Ipc: H04W0036060000

17P Request for examination filed

Effective date: 20200417

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/08 20090101ALI20201030BHEP

Ipc: H04W 80/00 20090101ALI20201030BHEP

Ipc: H04W 76/15 20180101ALI20201030BHEP

Ipc: H04W 36/00 20090101ALI20201030BHEP

Ipc: H04W 36/06 20090101AFI20201030BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
INTG Intention to grant announced

Effective date: 20201208

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1366027

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210315

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018013172

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210524

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210624

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210525

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210524

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1366027

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210624

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018013172

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

26N No opposition filed

Effective date: 20211125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210624

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20211231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211211

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211231

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211231

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20181211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231227

Year of fee payment: 6

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20231226

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210224

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231229

Year of fee payment: 6