WO2024014997A1 - Procédés pour améliorer un transfert intercellulaire et une double connectivité pour une économie d'énergie de réseau - Google Patents

Procédés pour améliorer un transfert intercellulaire et une double connectivité pour une économie d'énergie de réseau Download PDF

Info

Publication number
WO2024014997A1
WO2024014997A1 PCT/SE2023/050604 SE2023050604W WO2024014997A1 WO 2024014997 A1 WO2024014997 A1 WO 2024014997A1 SE 2023050604 W SE2023050604 W SE 2023050604W WO 2024014997 A1 WO2024014997 A1 WO 2024014997A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
node
target
source
handover
Prior art date
Application number
PCT/SE2023/050604
Other languages
English (en)
Inventor
Meysam AGHIGHI
Nianshan SHI
Sofia Svedevall
Ari Kangas
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2024014997A1 publication Critical patent/WO2024014997A1/fr

Links

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/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/165—Performing reselection for specific purposes for reducing network power consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/249—Reselection being triggered by specific parameters according to timing information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This disclosure relates to handover and Dual Connectivity (DC) for Network Energy Saving (NES).
  • DC Dual Connectivity
  • NES Network Energy Saving
  • 5G 5 th Generation
  • RAN Radio Access Network
  • NR New Radio
  • 3GPP Third Generation Partnership Project
  • Rel-18 approved the study and development of a network energy consumption model, especially for the base station.
  • the study investigates how to achieve more efficient operation dynamically and/or semi-statically, and achieve finer granularity adaptation of transmissions and/or receptions in one or more network energy saving techniques.
  • each NG-RAN node comprises a gNB Central unit (gNB-CU) and one or more gNB distributed unit (gNB-DU) logical entities, as illustrated in Fig. 1.
  • gNB-CU gNB Central unit
  • gNB-DU gNB distributed unit
  • the 5G Core Network connects to the NG-RAN nodes over the N2 interface at the control plane, and the N3 interface over the user plane. These connections (e.g. N2 and N3) are depicted as a single NG interface in Fig. 1.
  • gNBs in the NG-RAN are connected through an Xn interface between gNB-CUs.
  • each gNB- CU is connected to one or more gNB-DUs via F1 interfaces.
  • SDAP Service Data Adaptation Protocol
  • PDCP Data Convergence Protocol
  • RRC Radio Resource Control
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical
  • Handover There are two types of handover in New Radio (NR): Xn-based handover, and NG-based handover.
  • NR New Radio
  • the preparation and execution phase of the handover procedure are performed between the gNBs without involvement of the core network.
  • the Xn interface is utilised to perform the handover.
  • the preparation and execution phase of the handover procedure are performed using signalling via the core network (5GC).
  • a User Equipment may be connected to one gNB that acts as a Master node (MN) and another gNB that acts as a Secondary Node (SN).
  • MN Master node
  • SN Secondary Node
  • a UE may connect to a single gNB, acting both as a MN and as a SN, and configuring both a Master Cell Group (MCG) and a Secondary Cell Group (SCG).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • a cell is considered to be operating in a sleep mode if part of or all the cell is switched off to save energy. There are different types of sleep for a cell:
  • Short sleep which may be performed when there is expected to be no transmission in the cell.
  • a short sleep may not affect the accessibility of the cell and might have a small impact on the overall throughput. This kind of sleep is usually expected to be less than 20 milliseconds (ms).
  • Long sleep which may be performed when there is expected to be neither a transmission nor a need to access the cell for a longer period than a short sleep.
  • a long sleep may be likely to have an impact on the overall throughput and might also have a small impact on the overall accessibility. This kind of sleep is usually expected to be less than 160ms.
  • Deep sleep which may be performed when there is no UE connected to the cell and the cell is completely unusable for a period. This type of sleep may take from a few seconds up to a few hours and is performed especially when the load is low in the network (e.g. during night-time).
  • Fig. 2 illustrates different cells in a network. It will be appreciated that the cells are depicted vertically above a geographical area that they service or serve. In Fig. 2, the area serviced/served by cells 301 overlaps with the area serviced/served by cells 302, 305 and 304. As an example, cells 301 and 303 may be put into a deep sleep mode during night-time without having an impact on the accessibility of the system. This is because the remaining cells/l ayers (302, 304 and 305) will be awake and may therefore be able to provide enough service to whichever few UEs still require night-time service that may otherwise have been served by the 301 or 303 cells. In principle, all cells except cell 304 may be put into (at least) the short sleep mode as soon as there is a period of no requested data transmission, as the cell 304 can cover the areas serviced/served by all of the other depicted cells.
  • the network may apply different types of sleep mode, e.g. the long sleep mode or the deep sleep mode. This may lead to any of the following situations:
  • a first NG-RAN node may want to handover the UE to another NG-RAN node, so that the first NG-RAN node can go into the deep sleep mode.
  • the first NG-RAN node may want the target NG- RAN node to take over the UE with a high priority.
  • a NG-RAN node may want to delay the handover process for an incoming handover and allow its cells to wake-up from a sleep mode.
  • a similar issue may occur for the secondary node of dual connectivity (DC): a.
  • a first NG-RAN node may want to change Primary Secondary Cell (PSCell) for some UE(s) to another NG-RAN node, so that the first NG-RAN node can go into a deep sleep mode. In this case it may want the target NG-RAN node to take over the UE with a high priority.
  • a NG-RAN node may want to delay the SN addition process for an incoming dual connectivity setup (due to initial setup or mobility) and allow its cells to wake-up from a sleep mode.
  • This disclosure provides a solution for a source NG-RAN node to indicate to the target NG-RAN node that a handover or PSCell change is related to its Network Energy Saving (NES) policy.
  • the target NG-RAN node can then act accordingly.
  • NES Network Energy Saving
  • This disclosure also provides a solution for the target NG-RAN node to accept - but delay - the handover for a given period of time, in order to ensure the target NG-RAN node can perform its energy saving scheme, where there is no service interruption.
  • This disclosure also provides similar approaches for Dual Connectivity, in that the SN addition can be accepted but delayed, for example, during Quality of Service (QoS) offloading.
  • QoS Quality of Service
  • a source NG-RAN node may indicate its support of the feature, optionally for certain services and connections, and it may indicate if such feature is allowed or not.
  • Some aspects of the present disclosure provide methods/interfaces in the RAN node (e.g. a gNB) as follows:
  • the target NG-RAN node may not be allowed or permitted to perform handover with delay for such services.
  • the target NG-RAN node may accept the handover but indicate a wanted/desired delay in the handover execution.
  • the source NG- RAN node can keep the UE for the given time and execute handover towards UE after the time period.
  • the source secondary NG-RAN node and the master NG-RAN node may indicate that it supports the "node dual connectivity power saving scheme”, or alternatively indicate if the "node dual connectivity power saving scheme” is allowed.
  • critical services it is preferred (or required) for there to be no degradation of the performance, and thus it is not allowed or permitted for the target NG-RAN secondary node to perform dual connectivity setup with delay for such services.
  • the target NG-RAN node may accept the dual connectivity setup, but indicate a delay in the execution of the PSCell change.
  • the master NG-RAN node may delay the RRC reconfiguration of the UE for the given time period. It is assumed that a delay in reception of a Xn Application Protocol (XnAP) S-Node Change Confirm is accepted by the source secondary NG-RAN node.
  • XnAP Xn Application Protocol
  • the target NG-RAN node may accept the dual connectivity setup but indicate a wanted/desired delay in the SN addition execution. Upon receipt of such information, the master NG-RAN node will wait with the RRC reconfiguration of the UE for the given time period.
  • the target NG-RAN node may, or should, prioritise the handover request.
  • a method performed by a source RAN node that is serving a UE comprises: sending a handover request message to a target RAN node indicating that the source RAN node is to handover the UE to the target RAN node.
  • the handover request message comprises one or more of: (i) an indication of whether the source RAN node supports a network energy saving scheme; (ii) an indication that the handover of the UE is due to the network energy saving scheme; and (iii) an indication of a time by which the handover of the UE is to be completed to enable the source RAN node to use the network energy saving scheme.
  • a method performed by a target RAN node comprises: receiving a handover request message from a source RAN node indicating that the source RAN node is to handover a UE to the target RAN node.
  • the handover request message comprises one or more of: (i) an indication of whether the source RAN node supports a network energy saving scheme; (ii) an indication that the handover of the UE is due to the network energy saving scheme; and (iii) an indication of a time by which the handover of the UE is to be completed to enable the source RAN node to use the network energy saving scheme.
  • the method comprises: sending a change request message to a master RAN node for the DC, the change request message requesting a change of responsibility for providing a SCG to another secondary RAN node.
  • the change request message comprises one or more of: (i) an indication of whether the source secondary RAN node supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (iii) an indication of a time by which the change of responsibility for providing the SCG is to be completed to enable the source secondary RAN node to use the network energy saving scheme.
  • a method performed by a target secondary RAN node comprises: receiving a secondary node addition request message from a master RAN node indicating that the target secondary RAN node is to assume responsibility for providing a SCG to enable a UE to use DC.
  • the secondary node addition request message comprises one or more of: (i) an indication of whether a source secondary RAN node that is currently providing the SCG supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (iii) an indication of a time by which the target secondary RAN node is to assume responsibility for providing the SCG is to enable the source secondary RAN node to use the network energy saving scheme.
  • a method performed by a master RAN node that is providing a master cell group (MCG) to enable a UE to use DC comprises: receiving (1201) a change request message from a source secondary RAN node that is responsible for providing a SCG for the DC, the change request message requesting a change of responsibility for providing the SCG to another secondary RAN node.
  • the change request message comprises one or more of: (i) an indication of whether the source secondary RAN node supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (iii) an indication of a time by which the change of responsibility for providing the SCG is to be completed to enable the source secondary RAN node to use the network energy saving scheme.
  • the method also comprises: sending a secondary node addition request message to a target secondary RAN node indicating that the target secondary RAN node is to assume responsibility for providing the SCG.
  • the secondary node addition request message comprises one or more of: (i) the indication of whether the source secondary RAN node that is currently providing the SCG supports a network energy saving scheme; (ii) the indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (iii) the indication of the time by which the target secondary RAN node is to assume responsibility for providing the SCG is to enable the source secondary RAN node to use the network energy saving scheme.
  • a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, or any embodiments thereof.
  • a RAN node configured to: operate as a source RAN node according to the first aspect or any embodiment thereof; operate as a target RAN node according to the second aspect or any embodiment thereof; operate as a source secondary RAN node according to the third aspect or any embodiment thereof; operate as a target secondary RAN node according to the fourth aspect or any embodiment thereof; and/or operate as a master RAN node according to the fifth aspect or any embodiment thereof.
  • a RAN node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said RAN node is operative to: operate as a source RAN node according to the first aspect or any embodiment thereof; operate as a target RAN node according to the second aspect or any embodiment thereof; operate as a source secondary RAN node according to the third aspect or any embodiment thereof; operate as a target secondary RAN node according to the fourth aspect or any embodiment thereof; and/or operate as a master RAN node according to the fifth aspect or any embodiment thereof.
  • Certain aspects and/or embodiments may provide one or more of the following technical advantage(s).
  • One advantage is that it is possible to control handover and/or dual connectivity procedures to ensure that the network (and specifically one or more RAN nodes) can sleep for longer in order to more effectively save the network energy, without limiting the possibility to perform mobility when necessary.
  • Fig. 1 illustrates a split NG-RAN node architecture
  • Fig. 2 illustrates different cells in a network
  • Fig. 3 is a signalling diagram illustrating a handover procedure according to exemplary embodiments
  • Fig. 4 is a table illustrating an exemplary implementation of how to indicate a handover request is accepted, and/or how to indicate other NES scheme-related information in the Handover Request message;
  • Fig. 5 is a table illustrating an exemplary implementation of how to acknowledge acceptance of a Handover Request, while taking into account a NES scheme supported by the target NG-RAN node;
  • Fig. 6 is a signalling diagram illustrating how a Source NG-RAN node indicates that a handover is due to NES;
  • Fig. 7 is a copy of Figure 10.5.2-2: SN change procedure - SN initiated from ETSI TS 137 340 v17.0.0 (2022- 05);
  • Fig. 8 is a flow chart illustrating a method of operating a source RAN node in accordance with some embodiments
  • Fig. 9 is a flow chart illustrating a method of operating a target RAN node in accordance with some embodiments.
  • Fig. 10 is a flow chart illustrating a method of operating a source secondary RAN node in accordance with some embodiments
  • Fig. 11 is a flow chart illustrating a method of operating a target secondary RAN node in accordance with some embodiments
  • Fig. 12 is a flow chart illustrating a method of operating a master RAN node in accordance with some embodiments
  • Fig. 13 shows an example of a communication system in accordance with some embodiments
  • Fig. 14 shows a UE in accordance with some embodiments
  • Fig. 15 shows a RAN network node in accordance with some embodiments
  • Fig. 16 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Fig. 17 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • source NG-RAN node refers to a RAN node in a 5G/NR network, e.g. a gNB, that is currently serving a UE and that wants to hand over the UE to a "target NG-RAN node” according to a handover procedure.
  • the "target NG-RAN node” is another RAN node in the 5G/NR network, e.g. another gNB.
  • the source NG-RAN node can be more generally referred to as a "source RAN node”, which includes RAN nodes in other types of network, such as eNBs, base stations, etc.
  • source RAN node also includes a “source secondary RAN node” as described below.
  • the target NG-RAN node can be more generally referred to as a "target RAN node”, which RAN nodes in other types of network, such as eNBs, base stations, etc.
  • target RAN node also includes a "target secondary RAN node” as described below.
  • the term "master NG-RAN node” used herein refers to a RAN node in a 5G/NR network, e.g. a gNB, that is in a dual connectivity (DC) arrangement for one or more UEs, and that provides control plane signalling for those UEs towards the core network (CN) of the communication network.
  • the master NG-RAN node is responsible for a set of serving cells known as the Master Cell Group (MCG).
  • MCG Master Cell Group
  • the master NG-RAN node can be more generally referred to as a "master RAN node”, which includes RAN nodes in other types of network, such as eNBs, base stations, etc.
  • secondary NG-RAN node refers to a RAN node in a 5G/NR network, e.g. a gNB, that is in a dual connectivity (DC) arrangement for one or more UEs, and that is responsible for one or more secondary serving cells (SCells) in a Secondary Cell Group (SCG) that can provide additional resources to UEs that are using DC.
  • the secondary NG-RAN node can be more generally referred to as a "secondary RAN node”, which includes RAN nodes in other types of network, such as eNBs, base stations, etc.
  • source secondary NG-RAN node refers to a secondary NG-RAN node that is currently providing a SCG and that wants to move or transfer responsibility for providing a SCG for DC to another NG-RAN node.
  • target secondary NG-RAN node refers to the NG-RAN node in the 5G/NR network, e.g. a gNB, and is the RAN node to which the source secondary NG-RAN node and/or master NG-RAN node intend to transfer responsibility for providing the SCG.
  • the target secondary NG-RAN node can be more generally referred to as a "target secondary RAN node”, which includes RAN nodes in other types of network, such as eNBs, base stations, etc.
  • a network energy saving scheme refers to an ability of any of the above types of RAN node to use an alternative mode of operation to temporarily or periodically reduce energy consumption of the RAN node.
  • a network energy saving scheme can comprise one or more sleep modes that can be applied to or in one or more cells provided by the RAN node.
  • the sleep modes can include any of the short sleep mode, long sleep mode and deep sleep mode outlined above.
  • the following embodiments relate to a potential handover of a UE from a source NG-RAN node to a target NG- RAN node.
  • the source NG-RAN node can indicate to the target NG-RAN node that it supports the network energy saving scheme.
  • the target NG-RAN node When the target NG-RAN node receives the handover, it performs admission control and prepares the resource(s), but in order to allow the cells provided by the target NG-RAN node to wake up from deep sleep, it would indicate that the handover is successful but will delay a given time period, for example 50 ms, although delays of other durations are possible. That is, when the target NG-RAN node receives a handover decision (i.e.
  • the target NG-RAN node can indicate to the source NG- RAN node that the handover request is accepted but that there will be a defined delay in executing the handover.
  • the source NG-RAN node when receiving the delay indication, can keep serving the UE for the given delay time, and continue the handover procedure only after the time has passed.
  • This procedure is shown in the signalling diagram in Fig. 3, which shows the signalling between a UE, a source NG-RAN node and a target NG-RAN node in which the target NG-RAN node acknowledges the handover but indicates a delay in execution.
  • An exemplary implementation of the above technique can be to use signalling over, e.g., XnAP, and the signalling can include the essential or necessary information in the Handover Request message and the Handover Acknowledgement (Ack) message.
  • the table in Fig. 4 provides an exemplary implementation of how to indicate a handover request is accepted, and/or how to indicate other network energy saving scheme-related information in the Handover Request message.
  • the table in Fig. 4 is a modified version of the Handover Request table in 3GPP TS 38.423 v17.0.0, section 9.1.1.1, and the new Information Element (IE) is referred to as "Network Energy Saving Information”.
  • CGI refers to a "Cell Global Identifier”
  • ProSe refers to "Proximity Services”.
  • the table in Fig. 5 provides an exemplary implementation of how to acknowledge acceptance of a Handover Request, while taking into account a network energy saving scheme supported by the target NG-RAN node.
  • the Handover Request Acknowledgement can indicate information about the network energy saving scheme, such as the length of a delay to executing the handover due to the network energy saving scheme.
  • the table in Fig. 5 is a modified version of the Handover Request Acknowledgement table in 3GPP TS 38.423 v17.0.0, section 9.1.1.2, and the new IE is referred to as "Network Energy Saving Response”. It will be appreciated that the teachings of the present disclosure can be implemented in inter-NG-RAN node messages other than the types shown in Figs. 4 and 5.
  • MBS refers to "Multicast and Broadcast Service”.
  • the source NG-RAN node may also include a time value in the handover request message indicating how long the source NG-RAN node can keep serving the UE before it has to perform the handover. In normal operation, the target NG-RAN should take this time value into consideration in deciding the delay period.
  • the source NG-RAN node can indicate to the target NG-RAN node (e.g. in the handover request message) that the handover is due to its power saving scheme, and that it would like to handover the UE(s) so that it can go into a longer power saving (sleep) mode.
  • the target NG-RAN node may prioritise the handover procedure, particularly when there is a potential congestion situation.
  • the signalling diagram in Fig. 6 illustrates the signalling between a UE, a source NG-RAN node and a target NG-RAN node where the source NG-RAN node indicates that the handover due to NES. As shown in Fig.
  • the indication that the handover is due to the power saving scheme can be indicated by the Network Energy Saving Information IE in the Handover Request message.
  • the indication that the handover is due to the power saving scheme can be indicated in a different IE to the one that indicates whether the source NG-RAN node supports the network energy saving scheme, and in some implementations the indication can be in a different handover message to the handover request message.
  • the following embodiments relate to a potential change of a secondary NG-RAN node that is responsible for providing a SCG for dual connectivity operation for one or more UEs.
  • the source secondary NG-RAN node for a DC configuration can indicate to the master NG-RAN node for the DC configuration that it supports a "network energy saving scheme”.
  • the source secondary NG- RAN node can indicate this to the master NG-RAN node in a message that requests the master NG-RAN node change the secondary NG-RAN node in the DC configuration.
  • the source secondary NG-RAN node can indicate this support in a XnAP message, for example an XnAP "S-Node Change Required” message, which is used to indicate that a change of secondary node (S-Node) is required. This information (i.e.
  • the information indicating that the source secondary NG-RAN node supports a network energy saving scheme can be relayed or sent to the target secondary NG-RAN node by the master NG-RAN node.
  • This information can be sent to the target secondary NG-RAN node in a XnAP message, for example a XnAP "S-Node Addition Request” message.
  • the target secondary NG-RAN node receives the request, it can perform admission control and prepare the resource(s). If the cells of the target secondary NG-RAN node are in a sleep mode (e.g.
  • the node can indicate to the master NG-RAN node that the target secondary NG-RAN node can be a secondary node and establish a SCG for DC after a given delay time period.
  • This indication can be sent to the master NG-RAN node in a XnAP message, for example in a Xn-AP "S-Node Addition Request Acknowledge” message that indicates the SN addition is successful but will be delayed for a given time period, for example 50 ms.
  • the master NG-RAN node when the master NG-RAN node receives the delay indication, the master NG-RAN node will wait the given time and continue the RRC Reconfiguration procedure to establish the DC involving the target secondary NG-RAN node only after the time has passed. The master NG-RAN node can then respond to the source secondary NG-RAN node about the transfer procedure as normal.
  • the source secondary NG-RAN node can also include a time that indicates how long it can keep serving the UE before it has to perform the secondary cell (PSCell) change. In normal operation, the target secondary NG-RAN should take this time value into consideration in deciding the duration of any delay period.
  • PSCell secondary cell
  • the source secondary NG-RAN node can indicate to the target secondary NG-RAN node (via the master NG-RAN node), that the PSCell change is due to the power saving scheme of the source secondary NG-RAN node, and that it wishes to move the SCG for the UE(s) so that it can enter a longer power saving (sleep) mode.
  • the target NG-RAN node can prioritise the SN addition procedure, particularly when there is a potential congestion situation.
  • one or more new data fields or lEs can be added to the XnAP S-Node Change Required and XnAP S-Node Addition messages.
  • These new data fields or lEs can be similar to, or the same as, the "Network Energy Saving Information” and “Network Energy Saving Response” lEs described above and shown in Figs. 4 and 5 respectively.
  • Fig. 7 shows a standardised secondary RAN node change procedure.
  • Fig. 7 is taken from the specification ETSI TS 137 340 v17.0.0 (2022-05), and shows the signalling between a UE, a master RAN node (MN), a source secondary RAN node (S-SN), and a target secondary RAN node (T-SN) when the S-SN initiates the secondary node change procedure to transfer a UE context from the source secondary RAN node to the target secondary RAN node and to change the SCG configuration in the UE from one secondary RAN node to the other.
  • MN master RAN node
  • S-SN source secondary RAN node
  • T-SN target secondary RAN node
  • a brief outline of the signalling in Fig. 7 - taken from the above-referenced specification - is as follows:
  • the source SN initiates the SN change procedure by sending the SN Change Required message, which contains a candidate target node ID and may include the SCG configuration (to support delta configuration) and measurement results related to the target SN.
  • the MN requests the target SN to allocate resources for the UE by means of the SN Addition procedure, including the measurement results related to the target SN received from the source SN. If data forwarding is needed, the target SN provides data forwarding addresses to the MN.
  • the target SN includes the indication of the full or delta RRC configuration.
  • the MN For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message.
  • the MN triggers the UE to apply the new configuration.
  • the MN indicates the new configuration to the UE in the MN RRC reconfiguration message including the SN RRC reconfiguration message generated by the target SN.
  • the UE applies the new configuration and sends the MN RRC reconfiguration complete message, including the SN RRC response message for the target SN, if needed.
  • the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure.
  • the MN confirms the change of the source SN. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the SN Change Confirm message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding.
  • the MN informs the target SN via SN Reconfiguration Complete message with the included SN RRC response message for the target SN, if received from the UE.
  • the UE synchronizes to the target SN.
  • the source SN sends the SN Status Transfer, which the MN sends then to the target SN, if needed.
  • data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the SN Change Confirm message from the MN.
  • the source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2.
  • a PDU Session path update procedure is triggered by the MN.
  • the source SN Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.
  • the source secondary RAN node can indicate support for the network energy saving scheme in the "SN Change Required” message that is sent to the master RAN node.
  • the target secondary RAN node can indicate the delay time period for assuming responsibility for the SCG to the master RAN node in the "SN Addition Request Acknowledge” message.
  • the master RAN node then waits for the indicated time period before sending the RRC Connection Reconfiguration message (message 4 in Fig. 7) to the UE, and thus the master RAN node also waits for the expiry of the time period (and completion of the RRC reconfiguration procedure with the UE) before sending the SN Change Confirm acknowledgement message to the source secondary RAN node.
  • Fig. 8 is a flow chart illustrating a method according to various embodiments performed by a source RAN node.
  • the source RAN node is a network node in the RAN of the communication network, and is also referred to herein as a "RAN network node”.
  • the source RAN node may be the RAN network node 1310 or RAN network node 1500 as described later with reference to Fig. 13 and 15 respectively.
  • the source RAN node may perform the method in response to executing suitably formulated computer readable code.
  • the computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium.
  • the computer readable medium may be part of a computer program product.
  • the source RAN node is serving a UE, and in step 801 , the source RAN node sends a handover request message to a target RAN node indicating that the source RAN node is to handover the UE to the target RAN node.
  • the handover request message comprises one or more of: (I) an indication of whether the source RAN node supports a network energy saving scheme; (ii) an indication that the handover of the UE is due to the network energy saving scheme; and (ill) an indication of a time by which the handover of the UE is to be completed to enable the source RAN node to use the network energy saving scheme.
  • the network energy saving scheme may comprise one or more sleep modes that can be applied to one or more cells provided by the source RAN node and/or the target RAN node.
  • the handover request message sent in step 801 may be sent using XnAP signalling.
  • the source RAN node may receive an acknowledgement message in response to the handover request message from the target RAN node.
  • the received acknowledgement message may comprise an indication of a time period until the handover to the target RAN node is to be executed.
  • the received acknowledgement message may comprise the indication of the time period when the handover request message comprises the indication that the source RAN node supports the network energy saving scheme. In either case, the time period may be an amount of time required for the target RAN node to activate one or more cells from a sleep mode of the network energy saving scheme.
  • the source RAN node may perform the handover of the UE to the target RAN node after the expiry of the time period.
  • Performing the handover can comprise, after the expiry of the time period, the source RAN node sending an RRC reconfiguration message to the UE that requests the UE to handover to the target RAN node.
  • the UE then performs a random access on the target cell/target RAN node and completes the handover.
  • the source RAN node can perform the handover of the UE to the target RAN node before the expiry of the time period.
  • the source RAN node can then operate according to the network energy saving scheme.
  • Fig. 9 is a flow chart illustrating a method according to various embodiments performed by a target RAN node.
  • the target RAN node is a network node in the RAN of the communication network, and is also referred to herein as a "RAN network node”.
  • the target RAN node may be the RAN network node 1310 or RAN network node 1500 as described later with reference to Fig. 13 and 15 respectively.
  • the target RAN node may perform the method in response to executing suitably formulated computer readable code.
  • the computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium.
  • the computer readable medium may be part of a computer program product.
  • the target RAN node receives a handover request message from a source RAN node indicating that the source RAN node is to handover the UE to the target RAN node.
  • the handover request message comprises one or more of: (I) an indication of whether the source RAN node supports a network energy saving scheme; (ii) an indication that the handover of the UE is due to the network energy saving scheme; and (ill) an indication of a time by which the handover of the UE is to be completed to enable the source RAN node to use the network energy saving scheme.
  • the network energy saving scheme may comprise one or more sleep modes that can be applied to one or more cells provided by the source RAN node and/or the target RAN node.
  • the handover request message received in step 901 may be received using XnAP signalling.
  • the target RAN node may send an acknowledgement message to the source RAN node indicating a delay until the handover to the target RAN node is to be executed.
  • the handover of the UE from the source RAN node to the target RAN node is performed after the indicated delay (i.e. the source RAN node sends an RRC reconfiguration message to the UE that requests the UE to handover to the target RAN node, and the UE performs random access on the target RAN node).
  • the delay indicated in the acknowledgement message can be determined based on the received indication of the time.
  • the target RAN node may have a desired delay for completing a handover of the UE, and the delay indicated in the acknowledgement message can be determined based on the desired delay.
  • the received handover request message can comprise the indication of the time by which the handover of the UE is to be completed, and the target RAN node has a desired delay for completing a handover of the UE.
  • the delay indicated in the acknowledgement message can be determined based on the received indication of the time and the desired delay.
  • the target RAN node can determine if one or more cells provided by the target RAN node are to be activated from a sleep mode of the network energy saving scheme before the handover.
  • the target RAN node then sends an acknowledgement message to the source RAN node indicating a time period until the handover to the target RAN node is to be executed.
  • the time period may be an amount of time required for the target RAN node to activate the one or more cells from the sleep mode of the network energy saving scheme.
  • the handover of the UE from the source RAN node to the target RAN node is performed after the expiry of the time period (i.e. the source RAN node sends an RRC reconfiguration message to the UE that requests the UE to handover to the target RAN node, and the UE performs random access on the target RAN node).
  • the handover request message comprises the indication of a time period by which the handover of the UE is to be completed, the handover of the UE from the source RAN node to the target RAN node is performed before the expiry of the time period.
  • the target RAN node may prioritise the handover of the UE from the source RAN node.
  • Fig. 10 is a flow chart illustrating a method according to various embodiments performed by a source secondary RAN node.
  • the source secondary RAN node is a network node in the RAN of the communication network, and is also referred to herein as a "RAN network node”.
  • the source secondary RAN node may be the RAN network node 1310 or RAN network node 1500 as described later with reference to Fig. 13 and 15 respectively.
  • the source secondary RAN node may perform the method in response to executing suitably formulated computer readable code.
  • the computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium.
  • the computer readable medium may be part of a computer program product.
  • the source secondary RAN node is providing a SCG to enable a UE to use dual connectivity (DC).
  • DC dual connectivity
  • the source secondary RAN node sends a change request message to a master RAN node for the DC.
  • the change request message requests a change of responsibility for providing a SCG to another secondary RAN node.
  • the change request message comprises one or more of (i) an indication of whether the source secondary RAN node supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (iii) an indication of a time by which the change of responsibility for providing the SCG is to be completed to enable the source secondary RAN node to use the network energy saving scheme.
  • the network energy saving scheme may comprise one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the target secondary RAN node.
  • the change request message sent in step 1001 may be sent using XnAP signalling.
  • the source secondary RAN node may receive an acknowledgement message from the master RAN node in response to the change request message.
  • the change request message comprises the indication of a time period by which the change of responsibility for providing the SCG to another secondary RAN node is to be completed
  • the change of responsibility for providing the SCG from the source secondary RAN node to the other secondary RAN node is completed before the expiry of the time period.
  • the source secondary RAN node can then operate according to the network energy saving scheme.
  • Fig. 11 is a flow chart illustrating a method according to various embodiments performed by a target secondary RAN node.
  • the target secondary RAN node is a network node in the RAN of the communication network, and is also referred to herein as a "RAN network node”.
  • the target secondary RAN node may be the RAN network node 1310 or RAN network node 1500 as described later with reference to Fig. 13 and 15 respectively.
  • the target secondary RAN node may perform the method in response to executing suitably formulated computer readable code.
  • the computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium.
  • the computer readable medium may be part of a computer program product.
  • the target secondary RAN node may receive secondary node addition request message from a master RAN node.
  • the secondary node addition request message indicates that the target secondary RAN node is to assume responsibility for providing a SCG to enable a UE to use DC.
  • the secondary node addition request message comprises one or more of: (I) an indication of whether a source secondary RAN node that is currently providing the SCG supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (ill) an indication of a time by which the target secondary RAN node is to assume responsibility for providing the SCG is to enable the source secondary RAN node to use the network energy saving scheme.
  • the network energy saving scheme may comprise one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the target secondary RAN node.
  • the secondary node addition request message received in step 1101 may be received using XnAP signalling.
  • the target secondary RAN node may send an acknowledgement message to the master RAN node indicating a delay until the change of responsibility for providing the SCG to the target secondary RAN node is to be executed.
  • the target secondary RAN node may determine the delay based on the received indication of the time.
  • the target secondary RAN node may have a desired delay for completing a change of responsibility for providing the SCG, and the delay indicated in the acknowledgement message can be determined based on the desired delay.
  • the received secondary node addition request message may comprise the indication of the time by which the change of responsibility for providing the SCG is to be completed, and the target secondary RAN node may have a desired delay for completing a change of responsibility for providing the SCG.
  • the delay indicated in the acknowledgement message can be determined based on the received indication of the time and the desired delay.
  • the target secondary RAN node may determine if one or more cells provided by the target secondary RAN node are to be activated from a sleep mode of the network energy saving scheme in order to provide the SCG.
  • the target secondary RAN node can then send an acknowledgement message to the master RAN node indicating a time period until the target secondary RAN node is to assume responsibility for providing the SCG.
  • the time period may be an amount of time required for the target secondary RAN node to activate the one or more cells from the sleep mode of the network energy saving scheme.
  • the master RAN node can execute the change to the target secondary RAN node providing the SCG for the UE after the expiry of the time period.
  • the master RAN node can execute the change to the target secondary RAN node providing the SCG for the UE before the expiry of the time period.
  • the target secondary RAN node can prioritise the change of responsibility for providing the SCG from the source secondary RAN node to the target secondary RAN node.
  • Fig. 12 is a flow chart illustrating a method according to various embodiments performed by a master RAN node.
  • the master RAN node is a network node in the RAN of the communication network, and is also referred to herein as a "RAN network node”.
  • the master RAN node may be the RAN network node 1310 or RAN network node 1500 as described later with reference to Fig. 13 and 15 respectively.
  • the master RAN node may perform the method in response to executing suitably formulated computer readable code.
  • the computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disc, or other storage medium.
  • the computer readable medium may be part of a computer program product.
  • the master RAN node is providing a MCG to enable a UE to use DC.
  • the master RAN node receives a change request message from a source secondary RAN node that is responsible for providing a SCG for the DC.
  • the change request message requests a change of responsibility for providing the SCG to another secondary RAN node.
  • the change request message comprises one or more of: (I) an indication of whether the source secondary RAN node supports a network energy saving scheme; (ii) an indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (ill) an indication of a time by which the change of responsibility for providing the SCG is to be completed to enable the source secondary RAN node to use the network energy saving scheme.
  • the master RAN node sends a secondary node addition request message to a target secondary RAN node indicating that the target secondary RAN node is to assume responsibility for providing the SCG.
  • the secondary node addition request message comprises one or more of: (I) the indication of whether the source secondary RAN node that is currently providing the SCG supports a network energy saving scheme; (ii) the indication that the change of responsibility for providing the SCG is due to the network energy saving scheme; and (ill) the indication of the time by which the target secondary RAN node is to assume responsibility for providing the SCG is to enable the source secondary RAN node to use the network energy saving scheme.
  • the network energy saving scheme may comprise one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the target secondary RAN node.
  • the change request message and/or secondary node addition request message can be sent using XnAP signalling.
  • the master RAN node may receive an acknowledgement message from the target secondary RAN node in response to the secondary node addition request message.
  • the master RAN node may also or alternatively send an acknowledgement message to the source secondary RAN node in response to the change request message.
  • the acknowledgement message received from the target secondary RAN node may comprise an indication of a time period until the change of responsibility for providing the SCG to the target secondary RAN node is to be executed.
  • the master RAN node can wait until the time period has expired before sending a reconfiguration message to the UE that reconfigures the UE to use the target secondary RAN node for the SCG.
  • the time period can be an amount of time required for the target secondary RAN node to activate one or more cells from a sleep mode of the network energy saving scheme.
  • the master RAN node can perform the change of responsibility for providing the SCG to the target secondary RAN node before the expiry of the time period.
  • Fig. 13 shows an example of a communication system 1300 in accordance with some embodiments.
  • the communication system 1300 includes a telecommunication network 1302 that includes an access network 1304, such as a radio access network (RAN), and a core network 1306, which includes one or more core network nodes 1308.
  • the access network 1304 includes one or more access network nodes, such as access network nodes 1310a and 1310b (one or more of which may be generally referred to as access network nodes 1310), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the access network nodes 1310 facilitate direct or indirect connection of wireless devices (also referred to interchangeably herein as user equipment (UE)), such as by connecting UEs 1312a, 1312b, 1312c, and 1312d (one or more of which may be generally referred to as UEs 1312) to the core network 1306 over one or more wireless connections.
  • the access network nodes 1310 may be, for example, 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
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1300 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 1300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the wireless devices/UEs 1312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1310 and other communication devices.
  • the access network nodes 1310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1312 and/or with other network nodes or equipment in the telecommunication network 1302 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1302.
  • the core network 1306 connects the access network nodes 1310 to one or more hosts, such as host 1316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 1306 includes one more core network nodes (e.g. core network node 1308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the wireless devices/UEs, access network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1308.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 1316 may be under the ownership or control of a service provider other than an operator or provider of the access network 1304 and/or the telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider.
  • the host 1316 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 1300 of Fig. 13 enables connectivity between the wireless devices/UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • Wireless local area network such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WIMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LIFI, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • WIMax Worldwide Interoperability for Microwave Access
  • NFC Near Field Communication
  • LIFI Low-power wide-area network
  • LPWAN low-power wide-area network
  • the telecommunication network 1302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1302. For example, the telecommunications network 1302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive Internet of Things (loT) services to yet further UEs.
  • the UEs 1312 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1304.
  • a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 1314 communicates with the access network 1304 to facilitate indirect communication between one or more UEs (e.g. UE 1312c and/or 1312d) and access network nodes (e.g. access network node 1310b).
  • the hub 1314 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs.
  • the hub 1314 may be a broadband router enabling access to the core network 1306 for the UEs.
  • the hub 1314 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 1314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 1314 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 1314 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 1314 may have a constant/persistent or intermittent connection to the network node 1310b.
  • the hub 1314 may also allow for a different communication scheme and/or schedule between the hub 1314 and UEs (e.g. UE 1312c and/or 1312d), and between the hub 1314 and the core network 1306.
  • the hub 1314 is connected to the core network 1306 and/or one or more UEs via a wired connection.
  • the hub 1314 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 1304 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 1310 while still connected via the hub 1314 via a wired or wireless connection.
  • the hub 1314 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1310b.
  • the hub 1314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1310b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Fig. 14 shows a wireless device or UE 1400 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a wireless device/UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over Internet Protocol (IP) (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • IP Internet Protocol
  • PDA personal digital assistant
  • Wi-Fi wireless local loop phone
  • PDA personal digital assistant
  • gaming console or device music storage device
  • wearable terminal device wireless endpoint
  • mobile station tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a wireless device/UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g. a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g. a smart power meter).
  • the UE 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Fig. 14. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 1402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1410.
  • the processing circuitry 1402 may be implemented as one or more hardware- implemented state machines (e.g. in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 1402 may include multiple central processing units (CPUs).
  • the processing circuitry 1402 may be operable to provide, either alone or in conjunction with other UE 1400 components, such as the memory 1410, to provide UE 1400 functionality.
  • the processing circuitry 1402 may be configured to cause the UE 1402 to perform the methods as described herein.
  • the input/output interface 1406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include 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.
  • An input device may allow a user to capture information into the UE 1400.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 1408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g. an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 1408 may further include power circuitry for delivering power from the power source 1408 itself, and/or an external power source, to the various parts of the UE 1400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1408.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1408 to make the power suitable for the respective components of the UE 1400 to which power is supplied.
  • the memory 1410 may be or be configured to include memory such as random access memory (RAM), readonly memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416.
  • the memory 1410 may store, for use by the UE 1400, any of a variety of various operating systems or combinations of operating systems.
  • the memory 1410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a Universal SIM (USIM) and/or Integrated SIM (ISIM), 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
  • the UICC may for example be an embedded UICC (eUlCC), integrated UICC (IUICC) or a removable UICC commonly known as ‘SIM card.
  • eUlCC embedded UICC
  • IUICC integrated UICC
  • SIM card removable UICC commonly known as ‘SIM card.
  • the memory 1410 may allow the UE 1400 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1410, which may be or comprise a device-readable storage medium.
  • the processing circuitry 1402 may be configured to communicate with an access network or other network using the communication interface 1412.
  • the communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422.
  • the communication interface 1412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g. another UE or a network node in an access network).
  • Each transceiver may include a transmitter 1418 and/or a receiver 1420 appropriate to provide network communications (e.g. optical, electrical, frequency allocations, and so forth).
  • the transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g. antenna 1422) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 1412 may include cellular communication, Wi-Fi communication, LPWAN communication, 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.
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile (GSM), LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/! nternet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile
  • NR New Radio
  • UMTS Worldwide Interoperability for Mobile
  • Ethernet Transmission control protocol/
  • a UE may provide an output of data captured by its sensors, through its communication interface 1412, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g. once every 15 minutes if it reports the sensed temperature), random (e.g. to even out the load from reporting from several sensors), in response to a triggering event (e.g. when moisture is detected an alert is sent), in response to a request (e.g. a user initiated request), or a continuous stream (e.g. a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device
  • AR Augmented
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-loT (Narrowband-loT) standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Fig. 15 shows a network node 1500 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access network nodes such as 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
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • the network node 1500 can be configured to operate as any of the RAN nodes described herein, such as the source RAN node, the target RAN node, the source secondary RAN node, the target secondary RAN node and the master RAN node.
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multistandard 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g. Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multistandard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g. Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 1500 includes processing circuitry 1502, a memory 1504, a communication interface 1506, and a power source 1508, and/or any other component, or any combination thereof.
  • the network node 1500 may be composed of multiple physically separate components (e.g. a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1500 comprises multiple separate components (e.g. BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1500 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g. separate memory 1504 for different RATs) and some components may be reused (e.g. a same antenna 1510 may be shared by different RATs).
  • the network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1500.
  • RFID Radio Frequency Identification
  • the processing circuitry 1502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1500 components, such as the memory 1504, to provide network node 1500 functionality.
  • the processing circuitry 1502 may be configured to cause the network node to perform the methods as described herein.
  • the processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, the radio frequency (RF) transceiver circuitry 1512 and the baseband processing circuitry 1514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514.
  • the radio frequency (RF) transceiver circuitry 1512 and the baseband processing circuitry 1514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 1504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1502.
  • 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-
  • the memory 1504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1502 and utilized by the network node 1500.
  • the memory 1504 may be used to store any calculations made by the processing circuitry 1502 and/or any data received via the communication interface 1506.
  • the processing circuitry 1502 and memory 1504 is integrated.
  • the communication interface 1506 is used in wired or wireless communication of signalling and/or data between network nodes, the access network, the core network, and/or a UE. As illustrated, the communication interface 1506 comprises port(s)/terminal(s) 1516 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1506 can also include radio front-end circuitry 1518 that may be coupled to, or in certain embodiments a part of, the antenna 1510.
  • Radio front-end circuitry 1518 comprises filters 1520 and amplifiers 1522.
  • the radio front-end circuitry 1518 may be connected to an antenna 1510 and processing circuitry 1502.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1510 and processing circuitry 1502.
  • the radio front-end circuitry 1518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 1518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1520 and/or amplifiers 1522.
  • the radio signal may then be transmitted via the antenna 1510.
  • the antenna 1510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1518.
  • the digital data may be passed to the processing circuitry 1502.
  • the communication interface may comprise different components and/or different combinations of components.
  • the access network node 1500 does not include separate radio front-end circuitry 1518, instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510.
  • the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510.
  • all or some of the RF transceiver circuitry 1512 is part of the communication interface 1506.
  • the communication interface 1506 includes one or more ports or terminals 1516, the radio front-end circuitry 1518, and the RF transceiver circuitry 1512, as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuitry 1514, which is part of a digital unit (not shown).
  • the antenna 1510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1510 may be coupled to the radio front-end circuitry 1518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1510 is separate from the network node 1500 and connectable to the network node 1500 through an interface or port.
  • the antenna 1510, communication interface 1506, and/or the processing circuitry 1502 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1510, the communication interface 1506, and/or the processing circuitry 1502 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g. at a voltage and current level needed for each respective component).
  • the power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1500 with power for performing the functionality described herein.
  • the network node 1500 may be connectable to an external power source (e.g. the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1508.
  • the power source 1508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 1500 may include additional components beyond those shown in Fig. 15 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.
  • the network node 1500 may include user interface equipment to allow input of information into the network node 1500 and to allow output of information from the network node 1500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1500.
  • Fig. 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, 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.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, a wireless device/UE, a core network node, or host.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 1602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1600 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1604 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs 1608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.
  • the VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606.
  • a virtualization layer 1606 Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1608, and that part of hardware 1604 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1608 on top of the hardware 1604 and corresponds to the application 1602.
  • Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1610, which, among others, oversees lifecycle management of applications 1602.
  • hardware 1604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signalling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.
  • Fig. 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as a UE 1312a of Fig. 13 and/or UE 1400 of Fig. 14), network node (such as network node 1310a of Fig. 13 and/or network node 1500 of Fig. 15), and host (such as host 1316 of Fig. 13) discussed in the preceding paragraphs will now be described with reference to Fig. 17.
  • Embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1702 also includes software, which is stored in or accessible by the host 1702 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702.
  • OTT over-the-top
  • the network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706.
  • the connection 1760 may be direct or pass through a core network (like core network 1306 of Fig. 13) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 1306 of Fig. 13
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1706 includes hardware and software, which is stored in or accessible by UE 1706 and executable by the UE's processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific "app” that may be operable to provide a service to a human or non-human user via UE 1706 with the support of the host 1702.
  • a client application such as a web browser or operator-specific "app” that may be operable to provide a service to a human or non-human user via UE 1706 with the support of the host 1702.
  • an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1750 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT
  • the OTT connection 1750 may extend via a connection 1760 between the host 1702 and the network node 1704 and via a wireless connection 1770 between the network node 1704 and the UE 1706 to provide the connection between the host 1702 and the UE 1706.
  • the connection 1760 and wireless connection 1770, over which the OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between the host 1702 and the UE 1706 via the network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1702 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1706.
  • the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction.
  • the host 1702 initiates a transmission carrying the user data towards the UE 1706.
  • the host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706.
  • the request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706.
  • the transmission may pass via the network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1712, the network node 1704 transmits to the UE 1706 the user data that was carried in the transmission that the host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1714, the UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1706 associated with the host application executed by the host 1702.
  • the UE 1706 executes a client application which provides user data to the host 1702.
  • the user data may be provided in reaction or response to the data received from the host 1702.
  • the UE 1706 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an inpu t/output interface of the UE 1706. Regardless of the specific manner in which the user data was provided, the UE 1706 initiates, in step 1718, transmission of the user data towards the host 1702 via the network node 1704.
  • the network node 1704 receives user data from the UE 1706 and initiates transmission of the received user data towards the host 1702.
  • the host 1702 receives the user data carried in the transmission initiated by the UE 1706.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1706 using the OTT connection 1750, in which the wireless connection 1770 forms the last segment. More precisely, the teachings of these embodiments may improve the power consumption of the communication network.
  • factory status information may be collected and analysed by the host 1702.
  • the host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1702 may collect and analyse real-time data to assist in controlling vehicle congestion (e.g. controlling traffic lights).
  • the host 1702 may store surveillance video uploaded by a UE.
  • the host 1702 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1702 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analysing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1702 and/or UE 1706.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1704. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signalling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1702.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1750 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g. UEs, network nodes, hosts
  • computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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 may process information 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • time period is an amount of time required for the target RAN node to activate one or more cells from a sleep mode of the network energy saving scheme.
  • the method further comprises: performing the handover of the UE to the target RAN node before the expiry of the time period; and operating the source RAN node according to the network energy saving scheme.
  • the network energy saving scheme comprises one or more sleep modes that can be applied to one or more cells provided by the source RAN node and/or the target RAN node.
  • the handover request message is sent using Xn Application Protocol, XnAP, signalling.
  • a method performed by a target radio access network, RAN, node comprising: receiving a handover request message from a source RAN node indicating that the source RAN node is to handover a user equipment, UE, to the target RAN node, wherein the handover request message comprises one or more of:
  • the method further comprises: determining if one or more cells provided by the target RAN node are to be activated from a sleep mode of the network energy saving scheme before the handover; and sending an acknowledgement message to the source RAN node indicating a time period until the handover to the target RAN node is to be executed.
  • time period is an amount of time required for the target RAN node to activate the one or more cells from the sleep mode of the network energy saving scheme.
  • the method further comprises: performing the handover of the UE from the source RAN node before the expiry of the time period.
  • the method further comprises: prioritising the handover of the UE from the source RAN node.
  • the network energy saving scheme comprises one or more sleep modes that can be applied to one or more cells provided by the source RAN node and/or the target RAN node.
  • a method performed by a source secondary radio access network, RAN, node that is providing a secondary cell group, SCG, to enable a user equipment, UE, to use dual connectivity, DC comprising: sending a change request message to a master RAN node for the DC, the change request message requesting a change of responsibility for providing a SCG to another secondary RAN node, wherein the change request message comprises one or more of:
  • the network energy saving scheme comprises one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the other secondary RAN node.
  • a method performed by a target secondary radio access network, RAN, node comprising: receiving a secondary node addition request message from a master RAN node indicating that the target secondary RAN node is to assume responsibility for providing a secondary cell group, SCG, to enable a user equipment, UE, to use dual connectivity, DC, wherein the secondary node addition request message comprises one or more of:
  • an indication of a time by which the target secondary RAN node is to assume responsibility for providing the SCG is to enable the source secondary RAN node to use the network energy saving scheme.
  • the method further comprises: determining if one or more cells provided by the target RAN node are to be activated from a sleep mode of the network energy saving scheme in order to provide the SCG; and sending an acknowledgement message to the master RAN node indicating a time period until the target RAN node is to assume responsibility for providing the SCG.
  • the time period is an amount of time required for the target RAN node to activate the one or more cells from the sleep mode of the network energy saving scheme.
  • the method further comprises: prioritising the change of responsibility for providing the SCG from the source secondary RAN node to the target secondary RAN node.
  • the network energy saving scheme comprises one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the target secondary RAN node.
  • a method performed by a master radio access network, RAN, node that is providing a master cell group, MCG, to enable a user equipment, UE, to use dual connectivity, DC comprising: receiving a change request message from a source secondary RAN node that is responsible for providing a secondary cell group, SCG, for the DC, the change request message requesting a change of responsibility for providing the SCG to another secondary RAN node, wherein the change request message comprises one or more of:
  • the method further comprises one or both of: receiving, from the target secondary RAN node, an acknowledgement message in response to the secondary node addition request message; and sending, to the source secondary RAN node, an acknowledgement message in response to the change request message.
  • acknowledgement message received from the target secondary RAN node comprises an indication of a time period until the change of responsibility for providing the SCG to the target secondary RAN node is to be executed; and wherein the master RAN node waits until the time period has expired before sending a reconfiguration message to the UE that reconfigures the UE to use the target secondary RAN node for the SCG.
  • time period is an amount of time required for the target secondary RAN node to activate one or more cells from a sleep mode of the network energy saving scheme.
  • the method further comprises: performing the change of responsibility for providing the SCG to the target secondary RAN node before the expiry of the time period.
  • the network energy saving scheme comprises one or more sleep modes that can be applied to one or more cells provided by the source secondary RAN node and/or the target secondary RAN node.
  • a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, or the Group E embodiments.
  • a radio access network, RAN, node configured to perform the method of any one or more of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments.
  • a first radio access network, RAN, node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first RAN node is operative to perform the method of any one or more of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments.
  • a network node comprising: processing circuitry configured to cause the network node to perform any of the steps of the methods of any one or more of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and 47. a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments, to transmit the user data from the host to the UE.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • UE user equipment
  • a communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments to transmit the user data from the host to the UE.
  • the communication system of the previous embodiment further comprising: the network node; and/or the user equipment.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group A embodiments, the Group B embodiments, the Group C embodiments, the Group D embodiments, and the Group E embodiments, to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • UE user equipment

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un procédé mis en oeuvre par un noeud source d'accès radio (RAN) qui dessert un équipement utilisateur. Le procédé comprend les étapes suivantes: l'envoi (801) un message de demande de transfert intercellulaire à un noeud RAN cible indiquant que le noeud RAN source doit transférer l'équipement utilisateur au noeud RAN cible. Le message de demande de transfert intercellulaire comprend un ou plusieurs éléments parmi: (i) une indication indiquant si le noeud RAN source prend en charge un schéma d'économie d'énergie de réseau; (ii) une indication que le transfert de l'équipement utilisateur est dû au schéma d'économie d'énergie de réseau; et (iii) une indication d'un temps par lequel le transfert de l'équipement utilisateur doit être complété pour permettre au noeud RAN source d'utiliser le schéma d'économie d'énergie de réseau.
PCT/SE2023/050604 2022-07-14 2023-06-15 Procédés pour améliorer un transfert intercellulaire et une double connectivité pour une économie d'énergie de réseau WO2024014997A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263389043P 2022-07-14 2022-07-14
US63/389,043 2022-07-14

Publications (1)

Publication Number Publication Date
WO2024014997A1 true WO2024014997A1 (fr) 2024-01-18

Family

ID=87036101

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050604 WO2024014997A1 (fr) 2022-07-14 2023-06-15 Procédés pour améliorer un transfert intercellulaire et une double connectivité pour une économie d'énergie de réseau

Country Status (1)

Country Link
WO (1) WO2024014997A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014036710A1 (fr) * 2012-09-06 2014-03-13 Broadcom Corporation Procédé et appareil d'économie d'énergie dans des réseaux d'accès radio
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change
WO2021236755A1 (fr) * 2020-05-21 2021-11-25 Google Llc Gestion de configurations daps

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014036710A1 (fr) * 2012-09-06 2014-03-13 Broadcom Corporation Procédé et appareil d'économie d'énergie dans des réseaux d'accès radio
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change
WO2021236755A1 (fr) * 2020-05-21 2021-11-25 Google Llc Gestion de configurations daps

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 17)", 8 April 2022 (2022-04-08), XP052134865, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/Specifications/202203_draft_specs_after_RAN_95/Draft_37340-h00.docx> [retrieved on 20220408] *
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 16)", vol. RAN WG3, no. V16.10.0, 23 June 2022 (2022-06-23), pages 1 - 470, XP052183202, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/38_series/38.423/38423-ga0.zip 38423-ga0.doc> [retrieved on 20220623] *

Similar Documents

Publication Publication Date Title
WO2023105073A1 (fr) Commande d&#39;admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2024014997A1 (fr) Procédés pour améliorer un transfert intercellulaire et une double connectivité pour une économie d&#39;énergie de réseau
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2024096793A1 (fr) Commutation de cellule de mobilité déclenchée par couche 1/couche 2
WO2024094855A1 (fr) Systèmes et procédés d&#39;activation de faisceau à la demande
WO2023194554A1 (fr) Priorisation de liaison montante et de liaison latérale pour transmissions à trajets multiples
WO2023131929A1 (fr) Fourniture d&#39;informations d&#39;emplacement
WO2024072281A1 (fr) Procédés pour la fabrication d&#39;un équipement utilisateur conscient d&#39;une transmission ou d&#39;une réception discontinue par un réseau
WO2023062509A1 (fr) Activation de cellule secondaire basée sur un signal de référence temporaire par l&#39;intermédiaire d&#39;une commande de ressources radio
WO2024028838A1 (fr) Économie d&#39;énergie de réseau dans un ng-ran scindé
TW202325063A (zh) 使用頻率特定優先級之量測及量測報告
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2024035304A1 (fr) Signalisation de réseau de rapport de pscell réussie
WO2024014996A1 (fr) Signalisation d&#39;informations d&#39;économie d&#39;énergie dans un réseau d&#39;accès radio
TW202341794A (zh) 在執行雙主動協定堆疊交接時存錄及報告多重隨機存取程序資訊
WO2023136759A1 (fr) Envoi et réception d&#39;un rapport
WO2023101591A1 (fr) Configuration de réduction au minimum des essais en conduite dans un équipement utilisateur
WO2024035287A1 (fr) Évitement de situations de concurrence entre mobilité l1/l2 et l3
WO2024035311A1 (fr) Minimisation de portée de configuration de tests de disque pour différents types de réseau
WO2024033811A1 (fr) Signalisation de contexte d&#39;ue et de données de ng-ran à un réseau cœur
WO2023161819A1 (fr) Systèmes et procédés de prise en charge d&#39;intervalle de multiples modules d&#39;identité d&#39;abonné universels
EP4338470A1 (fr) Traitement de rejet de cellules cibles candidates pour un changement conditionnel de pscell
WO2024038116A1 (fr) Signalisation d&#39;informations de réalité étendue

Legal Events

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

Ref document number: 23734772

Country of ref document: EP

Kind code of ref document: A1