Master node-secondary node coordination on layer 1 / layer 2-triggered mobility candidate configurations

Abstract

A first network node can be in a communications network that includes a second network node The first network node can determine (310) that the first network node is configured with a maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a 5 communication device. The first network node can further transmit (320) a request to the second network node for an updated maximum number of LTM configurations to be used with the communication device. The first network node can further receive (330) an indication of the updated maximum number of LTM configurations from the second network node.

Description

MASTER NODE-SECONDARY NODE COORDINATION ON LAYER 1 / LAYER 2- TRIGGERED MOBILITY CANDIDATE CONFIGURATIONSTECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to master node (“MN”)-secondary node (“SN”) coordination on layer 1 / layer 2- triggered mobility (“LTM”) candidate configurations.BACKGROUND

[0002] FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] Layer 1 (“Ll”) / Layer 2 (“L2”)-Triggered Mobility (“LTM”) can be defined as a Primary Cell (“PCell”) (or primary secondary cell (“PSCell”)) cell switch procedure, consequently with Cell Group change (e.g., Master Cell Group (“MCG”) or Secondary Cell Group (“SCG”) that the network triggers via media access control (“MAC”) Control Element (“CE”) based on LI measurements. In that procedure, a gNodeB (“gNB”) receives the LI measurement report(s) from the UE, and on their basis the gNB changes UE’s serving cell by a cell switch command signaled via a MAC CE. The cell switch command indicates an LTM candidate cell configuration that the gNB previously prepared and provided to the UE through RRC signaling. Then the UE switches to the target cell according to the cell switch command.

[0004] When the UE moves from the coverage area of one cell to another cell, at some point a serving cell change needs to be performed. Currently serving cell change is triggered by L3 measurements and is done by RRC signaling triggered Reconfiguration with synchronization for change of PCell and PSCell, as well as release add for SCells when applicable. All cases involve complete L2 (and LI) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility. The goal of L1 / L2 based inter-cell mobility is to enable a serving cell change via L1 / L2 signaling, in order to reduce the latency, overhead and interruption time.

[0005] In 3GPP, discussions have started on solutions for L1 / L2 based inter-cell mobility (also referred to as LTM, Ll / L2-triggered mobility, or lower layer-triggered mobility).

[0006] A basic principle with Ll / L2-triggered mobility is that the UE is pre-configured, by the network, with an RRC configuration per LTM candidate cell, which is also known as a LTM candidate cell configuration. A LTM candidate cell configuration may be an RRCReconfiguration message or one or more lEs / fields / parameters such as CellGroupConfig.The UE performs measurements on these LTM candidate cells and transmits corresponding measurement reports to the network. The network then triggers the execution of a LTM cell switch procedure in the UE to one of these LTM candidate cells by transmitting lower layer signaling in a MAC CE, sometimes also referred to as a LTM cell switch command, to the UE, which then connects to the particular LTM candidate cell and switches to the LTM candidate cell configuration.SUMMARY

[0007] According to some embodiments, a method of operating a first network node is provided. The first network node can be in a communications network that includes a second network node. The method includes determining that the first network node is configured with a maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device. The method further includes, transmitting a request to the second network node for an updated maximum number of LTM configurations to be used with the communication device. The method further includes receiving an indication of the updated maximum number of LTM configurations from the second network node.

[0008] In additional or alternative embodiments, transmitting the request includes transmitting the request in response to determining that the maximum number of LTM configurations is different than a required number of LTM configurations to be used with the communication device.

[0009] In additional or alternative embodiments, transmitting the request includes transmitting the request in response to determining that the maximum number of LTM configurations is less than the required number of LTM configurations to be used with the communication device.

[0010] In additional or alternative embodiments, transmitting the request includes transmitting the request in response to determining that the maximum number of LTM configurations is greater than the required number of LTM configurations to be used with the communication device.

[0011] In additional or alternative embodiments, the first network node is configured to provide a secondary node, SN, and the second network node is configured to provide a master node, MN.

[0012] In additional or alternative embodiments, transmitting the request includes transmitting an indication of a difference between the maximum number of LTM configurations and the required number of LTM configurations. Transmitting the indication of the difference between the maximum number of LTM configurations and the required number of LTMconfigurations includes transmitting an indication of whether the difference is positive or negative.

[0013] In additional or alternative embodiments, transmitting the request includes transmitting an indication of a total number of LTM configurations that are required by the first network node.

[0014] In additional or alternative embodiments, the method includes, responsive to receiving the indication of the updated maximum number of LTM configurations, transmitting a rejection of the updated maximum number of LTM configurations to the second network node. Transmitting the rejection of the updated maximum number of LTM configurations includes transmitting an indication of a LTM configuration that will not be used by the first network node.

[0015] In additional or alternative embodiments, the method further includes, responsive to an amount of time elapsing since receiving the updated maximum number of LTM configurations, applying the updated maximum number of LTM configurations.

[0016] In additional or alternative embodiments, the method further includes, subsequent to transmitting the request and / or to receiving the indication of the updated maximum number of LTM configurations, triggering a context modification procedure to modify the LTM configurations.

[0017] In additional or alternative embodiments, transmitting the request to the second network node includes transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0018] In additional or alternative embodiments, determining that the first network node is configured with the maximum number of LTM configurations includes receiving an indication of the maximum number of LTM configurations to be used with the communication device from the second network node.

[0019] According to other embodiments, a method of operating a second network node is provided. The second network node can be in a communications network that includes a first network node. The method includes receiving a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device. The method includes transmitting an indication of the updated maximum number of LTM configurations to the first network node.

[0020] In additional or alternative embodiments, the method further includes transmitting an indication of a first maximum number of LTM configurations to the first network node. Receiving the request includes receiving the request subsequent to transmitting the indication of the first maximum number of LTM configurations.

[0021] In additional or alternative embodiments, the first network node is configured to provide a secondary node, SN, and the second network node is configured to provide a master node, MN.

[0022] In additional or alternative embodiments, receiving the request includes receiving an indication of a difference between the maximum number of LTM configurations and a required number of LTM configurations. Receiving the indication of the difference between the maximum number of LTM configurations and the required number of LTM configurations includes receiving an indication of whether the difference is positive or negative.

[0023] In additional or alternative embodiments, receiving the request includes receiving an indication of a total number of LTM configurations that are required by the first network node.

[0024] In additional or alternative embodiments, the method further includes, responsive to transmitting the indication of the updated maximum number of LTM configurations, receiving a rejection of the updated maximum number of LTM configurations from the first network node. Receiving the rejection of the updated maximum number of LTM configurations includes receiving an indication of a LTM configuration that will not be used by the first network node.

[0025] In additional or alternative embodiments, the method further includes receiving acknowledgement of the updated maximum number of LTM configurations from the first network node. The method further includes, responsive to receiving the acknowledgment, applying the updated maximum number of LTM configurations.

[0026] In additional or alternative embodiments, the method further includes, subsequent to transmitting the indication of the updated maximum number of LTM configurations, triggering a context modification procedure to modify the LTM configurations.

[0027] In additional or alternative embodiments, receiving the request from the first network node includes transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0028] According to other embodiments, a method of operating a second network node is provided. The second network node is in a communications network that includes a first network node. The method includes receiving a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device. The method includes determining to maintain a current maximum number of LTM configurations as the updated maximum number of LTM configurations.

[0029] In additional or alternative embodiments, the first network node is configured to provide a secondary node, SN, and the second network node is configured to provide a master node, MN.

[0030] In additional or alternative embodiments, receiving the request includes receiving an indication of a difference between the maximum number of LTM configurations and a required number of LTM configurations. Receiving the indication of the difference between the maximum number of LTM configurations and the required number of LTM configurations includes receiving an indication of whether the difference is positive or negative.

[0031] In additional or alternative embodiments, receiving the request includes receiving an indication of a total number of LTM configurations that are required by the first network node.

[0032] In additional or alternative embodiments, the method further includes transmitting an indication of a rejection of the request.

[0033] According to other embodiments, a network node, a computer program, computer program product, non-transitory computer readable medium, host, or system is provided to perform one of the above methods.

[0034] Certain embodiments may provide one or more of the following technical advantages. In some embodiments, both the MN and SN are able to support subsequent LTM at the UE. Also, it is guaranteed that unused LTM configuration are not wasted and also that UE capabilities are not exceeded. In additional or alternative embodiments, frequent reconfigurations at the UE are avoided with consequent increase in the interruption delay as the UE may not be able to do an ASN.1 decoding and validity check to the LTM configuration as these may change frequently.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;

[0037] FIG. 2 is a diagram illustrating an example of a CG-Config message in accordance with some embodiments;

[0038] FIGS. 3-5 are a flow charts illustrating examples of operations performed by a network node in accordance with some embodiments;

[0039] FIG. 6 is a block diagram of a communication system in accordance with some embodiments;

[0040] FIG. 7 is a block diagram of a user equipment in accordance with some embodiments;

[0041] FIG. 8 is a block diagram of a network node in accordance with some embodiments;

[0042] FIG. 9 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments; and

[0043] FIG. 10 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION

[0044] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0045] Some embodiments herein use the term “L1 / L2 based inter-cell mobility” interchangeably with the terms L1 / L2 mobility, Ll-mobility, LI based mobility, Ll / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility L1 / L2 Triggered Mobility, Lower-layer triggered Mobility or LTM. The basic principle is that the UE receives a lower layer signaling (e.g. a MAC CE) from the network indicating to the UE a change (or switch or activation) of includes serving cell (e.g. change of PCell, from a source to a target PCell), wherein a lower layer signaling is a message / signaling of a lower layer protocol, which may be referred as a L1 / L2 inter-cell mobility execution command or LTM cell switch command. The change of serving cell (e.g. change of PCell) may also lead to a change in Scell(s) for the same cell group e.g. in case the command triggers the UE to change to another cell group configuration of the same type (e.g. another MCG configuration). Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cells (e.g. reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration) A candidate cell configuration may include parameters in the IE CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per candidate cell.

[0046] The term LTM cell switch procedure can be used herein to refer to the process of a UE changing its cell from a source cell to a target cell (which may be called here a candidate cell or a neighbor cell), using L1 / L2 triggered mobility (“LTM”). In the context of LTM, an LTM cell switch procedure may sometimes also be known as dynamic switch, LTM switch, LTM cell switch, LTM serving cell change or LTM cell change. Even if the term change of cell is used,that may comprise a change of a whole cell group configuration, which includes a change in the SpCell (e.g. change of PCell, or change of PSCell) and a change in sCells of the cell group (e.g. addition, modification and / or release of one or more sCells). The LTM cell switch procedure may be triggered by the UE receiving an LTM cell switch command from the network. The source and target cells in a LTM cell switch procedure may be controlled by the same gNB, which sometimes is referred to as the intra-gNB case, or when the gNB uses a distributed CU / DU RAN architecture, the intra-CU inter-DU case or the intra-CU intra-DU case (depending on whether the cells are controlled by the same DU or different DUs). When the source and target cells in a LTM cell switch procedure are controlled by different gNBs, this is sometimes referred to as the inter-gNB case, or inter-CU case, or sometimes known as an inter-CU LTM cell switch procedure.

[0047] There currently exist certain challenges. The MN indicates to the SN how many LTM candidate configuration can be configured. However, this restriction is only possible from MN to SN and therefore the SN has to follow what the MN indicated. However, one aspect of LTM is that the UE is able to perform multiple LTM cell switch procedure without the need to be reconfigured by the network. This concept is known in 3GPP as “subsequent LTM”.

[0048] In some examples, the MN indicates to the SN that it can configure a maximum of 3 LTM candidate configurations at the UE. The SN configures 3 LTM candidate configurations at the UE. The MN indicates to the SN that can configure maximum 4 LTM candidate configurations at the UE. In this example, the SN may decide to not configure the 4thLTM candidate configuration at the UE in order to support subsequent LTM. The MN indicates to the SN that it can configure a maximum of 2 LTM candidate configurations at the UE. In this example, the SN is forced to release one of the LTM candidate configurations at the UE and this means that subsequent LTM candidate configurations will not be supported.

[0049] According to the example, the SN may not be able to support subsequent LTM at the UE since the configuration of the LTM candidate configuration is entirely controlled by the MN. This may cause frequent reconfigurations at the UE with consequent increase in the interruption delay as the UE may not be able to do an ASN.1 decoding and validity check to the LTM candidate configuration as these may change frequently.

[0050] Various embodiments herein address some of these challenges In some embodiments, the SN is allowed to transmit a request to the MN for the configuration of more LTM candidate configuration with respect to those initially indicated. Further, it allows the SN to signal to the MN whether some indicated LTM candidate configurations have not been configured so the MN may eventually configure additional LTM candidate configurations at theUE. This will help the MN to configure additional LTM candidate configurations, if needed, and to not waste, in general, unused LTM candidate configurations.

[0051] In additional or alternative embodiments, assuming the SN has already received the maximum number of LTM candidate configurations that can be configured by the MN, the SN behavior is clarified when a new value for the maximum number of LTM candidate configurations is received. This can avoid wrong network behavior and that the UE capabilities are not exceeded.

[0052] Some embodiments herein refer to at least one LTM candidate cell configuration. This can be referred to as a configuration of a LTM candidate cell, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with L1 / L2 Triggered Mobility. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to that LTM candidate cell e.g. upon reception of the LTM cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell, which becomes the target cell and the current (new) SpCell, or an sCell in a serving frequency. The LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message, an IE CellGroupConfig or an IE SpCellConfig (or the IE sCellConfig, in the case of a Secondary Cell).

[0053] An LTM candidate cell configuration is associated with an identifier that is used in the signaling when referring to a certain LTM candidate cell configuration, such as when the UE receives the LTM candidate cell configuration and when the UE receives an LTM cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell. This identifier is sometimes known as the LTM candidate cell configuration identity or LTM candidate configuration index (or similar).

[0054] An inter-CU LTM cell switch procedure (sometimes referred to as inter-CU LTM or inter-gNB LTM) can be an LTM cell switch procedure resulting in a change of serving cell, e.g. change of SpCell, PCell, PSCell, to an LTM candidate cell controlled by a different gNB than the source gNB or serving gNB of the UE when the execution LTM cell switch procedure was triggered (e.g. upon reception of the LTM cell switch command). From UE point of view, the actions performed during an inter-CU LTM cell switch procedure may be the same type of actions of an LTM cell switch procedure, but may also include additional actions, such as change of security key(s).

[0055] Additional or alternative embodiments refer to an inter Master Node L1 / L2 Triggered Mobility, inter-MN LTM, configuration of inter-MN LTM, execution of inter-MNLTM and an inter-MN LTM cell switch procedure. In the context of this disclosure, inter-MN LTM can refer to inter-CU LTM, sometimes also referred to as inter-gNB LTM, handover or MCG mobility, when the UE is configured with dual connectivity, such as NR-DC, and where the source cell and target cell are both part of the source and target MCG, respectively, and controlled by different CUs or different gNBs.

[0056] The term conditional LTM refers to L1 / L2 Triggered Mobility where the execution of the LTM cell switch is triggered by the UE when an execution condition, such as a layer 1, layer 2 or a layer 3 event, criterion or condition related to, for example, a radio measurement, is fulfilled. Upon the cell switch the UE applies a stored LTM candidate cell configuration.

[0057] Some embodiments herein refer to an inter-CU LTM candidate cell configuration. An inter-CU LTM candidate cell configuration is a LTM candidate cell configuration which includes the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE. In some cases, the UE may receive an inter-CU LTM candidate cell configuration during configuration of inter-MN LTM. In some cases, the UE may apply an inter-CU LTM candidate cell configuration during execution of inter-MN LTM.

[0058] An inter-CU LTM candidate cell configuration may be the same as an LTM candidate cell configuration but it may also include additional information than what is included in the LTM candidate cell configuration used for inter-CU cell switch. In some examples, this information includes information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig with Security AlgorithmConfig. In additional or alternative examples, this information includes an indication to perform PDCP re-establishment. In additional or alternative examples, this information includes an indication to perform a full configuration (e.g., the RRC field fullConfig).

[0059] Some embodiments herein refer to a mobility procedure, configuration of a mobility procedure or execution of a mobility procedure. In the context of this disclosure, a mobility procedure may be L1 / L2 Triggered Mobility, LTM, inter-CU LTM, inter-MN LTM, L3 handover, PCell handover, conditional handover (CHO), conditional LTM, PSCell change or conditional PSCell Addition or Change (CP AC). The solutions described herein sometimes uses an inter-MN LTM as an example. However, many of the examples may also be applied for other mobility procedures, for example, LTM, inter-CU LTM, conditional LTM or CHO.

[0060] Some embodiments herein refer to a mobility configuration. When the UE has been configured with a mobility configuration, it may use the mobility configuration duringpreparation of a mobility procedure, including measurements (such as RSRP measurements on neighbor or serving cells), triggering and transmission of measurement reports, synchronization towards neighbor cells, evaluation of conditions (for conditional mobility, e.g. CHO), and during the execution of a mobility procedure (e.g. execution of an LTM cell switch procedure, execution of an inter-MN LTM cell switch procedure or execution of handover).

[0061] A mobility configuration may include one or multiple of the following type of elements where each element includes a configuration of one aspect of LTM. In some examples, the mobility configuration includes LTM candidate cell configuration(s). In additional or alternative examples, the mobility configuration includes inter-CU LTM candidate cell configuration(s). In additional or alternative examples, the mobility configuration includes lower layer information, such as physical layer configuration, MAC layer configuration or RLC layer configuration, Cell Group configuration, serving cell configuration. In additional or alternative examples, the mobility configuration includes higher layer information, such as RRC protocol parameters, such as timer values, PDCP layer configuration, radio bearer configuration or measurement configuration. In additional or alternative examples, the mobility configuration includes configuration of measurements for LTM. In additional or alternative examples, the mobility configuration includes configuration for measurement reports for LTM. In additional or alternative examples, the mobility configuration includes CSI resource configuration(s) for LTM. In additional or alternative examples, the mobility configuration includes CSI report configuration for LTM. In additional or alternative examples, the mobility configuration includes configurations of early synchronization procedures, such as configurations for DL presync for LTM (e.g., configurations for early TCI state activation) or configurations for UL presync for LTM (e.g., configurations for reception of PDCCH ordered triggered preamble transmission and reception of TA). In additional or alternative examples, the mobility configuration includes configurations for the execution of an LTM cell switch procedure for a given LTM candidate cell configuration or inter-CU LTM candidate cell configuration (e.g., whether to perform random access procedure, whether to perform RLC reestablishment, or MAC reset, or PDCP recovery), a timer value, configured UL grants, dedicated RA preambles. In additional or alternative examples, the mobility configuration includes a configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE. In additional or alternative examples, the mobility configuration includes information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig with Security AlgorithmConfig. In additional or alternative examples, the mobility configurationincludes an indication to perform a full configuration, e.g. the RRC field fullConfig. In additional or alternative examples, the mobility configuration includes an indication to perform L2 re-establishment, such as an indication to perform PDCP re-establishment for one or multiple bearers.

[0062] The term “subsequent LTM”, also referred to as “subsequent LTM cell switch (procedures),” can be used to refer to the UE performing a first LTM cell switch procedure from a source cell to a first target cell, then performing a second LTM cell switch procedure from the first target cell (which is now the new source cell) to a second target cell, and between the first and second LTM cell switch procedures there is no RRC reconfiguration of the UE. This implies also that the network does not add / remove / modify the LTM candidate cell configuration(s) or inter-CU LTM candidate cell configuration(s) in the UE between the two LTM cell switch procedures.

[0063] The term “cell” can be used to identify a location (or coverage) on which the UE is located. However, the term “cell” can also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “TRS”. Embodiments herein do not specifically target a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource can also identify a set of configurations, field, parameters, or ASN.1 structures or IES.

[0064] The term MN can be used to identify a first network node that provides a first connectivity link to the UE and SN to identify e second network node that provides a second connectivity link to the UE. However, the terms “MCG” and “MN” can be exchanged without any loss of meaning as well as the terms “SCG” and “SN”.

[0065] In some embodiments, if previously configured with a maximum number of LTM candidate configuration to be configured at the UE, the SN transmits a request to the MN for a new value for the maximum number of LTM candidate configurations if it needs to configure more LTM candidate configurations. In additional or alternative embodiments, the request sent by the SN is represented by the exact number of the LTM candidate configurations that are needed to be configured (i.e., how many more LTM candidate configurations are needed in addition to that one already configured or indicated previously by the MN). In additional or alternative embodiments, the request sent by the SN is represented by the total maximum number of LTM candidate configurations that the SN wants to configure. In this example, the MN can calculate the additional needed LTM candidate configurations by considering the ones that it already signaled previously to the SN.

[0066] In additional or alternative embodiments, the requests sent by the SN is represented by an indication (i.e., 1 bit) to inform the MN that more LTM candidate configurations than theones previously configured are needed. In one embodiment, the SN sets this indication to “0” if the requested number of LTM candidate configurations is lower than the one already configured. In additional or alternative embodiments, the SN sets this indication to “1” if the requested number of LTM candidate configurations is higher than the one already configured.

[0067] In additional or alternative embodiments, assuming the SN has already a maximum number of LTM candidate configurations configured by the MN, upon receiving a new maximum number of LTM candidate configurations by the MN, the SN replies to MN that such new maximum number of LTM candidate configurations is rejected. In additional or alternative embodiments, upon receiving a new maximum number of LTM candidate configurations that are allowed to be configured by the MN, the SN replies to the MN with the remaining / not allocated LTM candidate configurations (i. e. , in case some of the LTM candidate configurations which are allowed to be configured by the MN has not been configured by the SN - e.g., MN indicates to the SN that it can configure a maximum of 3 LTM candidate configurations but the SN only configures 2). In additional or alternative embodiments, upon receiving a new maximum number of LTM candidate configurations by the MN, the SN replies to the MN with the number of the requested LTM candidate configurations. In this example, the SN should release the configured LTM candidate configurations that are necessary to meet the demand of the MN.

[0068] In additional or alternative embodiments, upon sending the request for new maximum number of LTM candidate configurations or after releasing the number of LTM candidate configurations requested by the MN, the SN applies the new SCG configuration to meet the UE capabilities only after the MN has acknowledged the reception of the new maximum number of LTM candidate configurations. This also means that a new reconfiguration is executed at the UE.

[0069] In additional or alternative embodiments, the SN, every time it signals / requests a new maximum number of LTM candidate configurations to the MN, it triggers a UE context modification procedure over Fl towards the interested candidate DU to modify or release LTM candidate configurations.

[0070] In additional or alternative embodiments, the SN sent the request or any other field concerning the maximum number of LTM candidate configurations to the MN via the inter-node RRC messages. In additional or alternative embodiments, the SN sent the request or any other field concerning the maximum number of LTM candidate configurations to the MN via the Xn signaling.

[0071] In additional or alternative embodiments, once the MN configures at the UE all the allowed LTM candidate configurations, the MN sends an indication to the SN with a newnumber of maximum LTM candidate configurations, if more or fewer LTM candidate configurations are needed to be configured. In additional or alternative embodiments, this indication indicates that more LTM candidate configurations are needed whereas in another embodiment, this indication indicates that fewer LTM candidate configurations are needed.

[0072] In additional or alternative embodiments, upon receiving a request from the SN that new LTM candidate configurations are needed, the MN simply ignores the request if no spare LTM candidate configurations are available (i.e. , this means that the MN has already configured at the UE all allowed / possible LTM candidate configurations). In additional or alternative embodiments, upon receiving a request from the SN that new LTM candidate configurations are needed, the MN informs the SN of the spare LTM candidate configurations that the SN can use, in addition to the one indicated previously (i.e., this means that the MN will indicate to the SN only the LTM candidate configurations the MN has not used). In additional or alternative embodiments, upon receiving a request from the SN that new LTM candidate configurations are needed, the MN replies to the SN with the number of the requested LTM candidate configurations. In this example, the MN should release as many configured LTM candidate configurations as needed to meet the demand of the SN.

[0073] In additional or alternative embodiments, upon receiving from the SN a request for new LTM candidate configurations with an indication set to “0”, it replies to the MN with a maximum number of LTM candidate configurations that is lower with respect to that one previously indicated. In additional or alternative embodiments, upon receiving from the SN a request for new LTM candidate configurations with an indication set to “1”, it replies to the MN with a maximum number of LTM candidate configurations that is higher with respect to that one previously indicated.

[0074] In additional or alternative embodiments, upon sending the request for new maximum number of LTM candidate configurations or after releasing the number of LTM candidate configurations requested by the SN, the MN applies the new MCG configuration to meet the UE capabilities only after the SN has acknowledged the reception of the new maximum number of LTM candidate configurations. This also means that anew reconfiguration is executed at the UE.

[0075] In additional or alternative embodiments, once the MN indicates to the SN for the first time the maximum number of LTM candidate configurations that the SN is allowed to configure, if the MN wants to change maximum number of LTM candidate configurations at the SN it only indicates an increased number of LTM candidate configurations by SN but never a lower number with respect the one previously indicated. For example, if MN indicates to the SN that a maximum number of 3 LTM candidate configurations can be configured by the SN, theMN later on can indicate only that a number X>3 of LTM candidate configurations can be configured by the SN but never a number which is X<3. In this case, it will be up to the SN to decide whether to configure additional LTM candidate configurations at the UE or to keep the number the same as the one already configured (in case the SN wants to use subsequent LTM at the UE).

[0076] In additional or alternative embodiments, the MN, every time it indicates / requests a new maximum number of LTM candidate configurations to the SN, it triggers UE context modification procedure over Fl towards the interested candidate DU(s) to modify or release LTM candidate configurations.

[0077] In additional or alternative embodiments, the MN sent the request or any other field concerning the maximum number of LTM candidate configurations to the SN via the inter-node RRC messages. In additional or alternative embodiments, the MN sent the request or any other field concerning the maximum number of LTM candidate configurations to the SN via the Xn signaling.

[0078] FIG. 2 illustrates an example of a CG-Config message. This message can be used to transfer the SCG radio configuration as generated by the SgNB or SeNB. It can also be used by a CU to request a DU to perform certain actions, e.g. to request the DU to perform a new lower layer configuration.

[0079] Operations of a network node 800 (implemented using the structure of FIG. 8) will now be discussed with reference to the flow chart of FIGS. 3-5 according to some embodiments of inventive concepts. For example, modules may be stored in memory 804 of FIG. 8, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 802, network node 800 performs respective operations of the flow charts.

[0080] FIG. 3 illustrates examples of operations performed by a first network node (e.g., a secondary node). In some embodiments, the first network node is configured to provide a secondary node, SN, and a second network node is configured to provide a master node, MN.

[0081] At block 310, processing circuitry 802 determines a current maximum number of LTM configurations (the terms LTM configurations and LTM candidate configurations are used interchangeably herein). In some embodiments, determining the current maximum number of LTM configurations includes receiving an indication of the current maximum number of LTM configurations from the second network node.

[0082] At block 320, processing circuitry 802 transmits, via communication interface 806, a request for an updated maximum number of LTM configurations. In some embodiments, transmitting the request includes transmitting an indication of a difference between themaximum number of LTM candidate configurations and the required number of LTM configurations. Transmitting the indication of the difference between the maximum number of LTM candidate configurations and the required number of LTM configurations includes transmitting an indication of whether the difference is positive or negative.

[0083] In additional or alternative embodiments, transmitting the request includes transmitting an indication of a total number of LTM candidate configurations that are required by the first network node.

[0084] In additional or alternative embodiments, transmitting the request to the second network node includes transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0085] At block 330, processing circuitry 802 receives, via communication interface 806, an indication of the updated maximum number of LTM configurations.

[0086] At block 340, processing circuitry 802 transmits, via communication interface 806, a response to the updated maximum number of LTM configurations. In some embodiments, transmitting the response to the updated maximum number of LTM configurations includes transmitting a rejection of the updated maximum number of LTM configurations. In some examples, the rejection includes an indication of a LTM configuration that will not be used by the first network node. In additional or alternative examples, the rejection is transmitted as part of performing an SN release form the MN.

[0087] At block 350 processing circuitry 802 applies the updated maximum number of LTM configurations. In some embodiments, the updated maximum number of LTM configurations are updated after an amount of time elapsing (e.g., based on a timer). In some examples, an indication of the amount of time to wait before applying the updated maximum number of LTM configurations is received from the second network node.

[0088] At block 360, processing circuitry 802 triggers a context modification procedure to modify the LTM candidate configurations.

[0089] FIGS. 4-5 illustrate examples of operations performed by a second network node (e.g., a master node). In some embodiments, the first network node is configured to provide a secondary node, SN, and a second network node is configured to provide a master node, MN.

[0090] FIG. 4 illustrates an example of operations performed by a second network node that decides to respond to a request to update a maximum number of LTM configuration.

[0091] At block 405, processing circuitry 802 transmits, via communication interface 806, an indication of a first maximum number of LTM configurations to the first network node.

[0092] At block 410, processing circuitry 802 receives, via communication interface 806, a request for an updated maximum number of LTM configurations. In some examples, theupdated maximum number of LTM configurations can be considered an update relative to the first maximum number of LTM configurations. In some embodiments, receiving the request includes receiving an indication of a difference between the maximum number of LTM candidate configurations and a required number of LTM configurations. Receiving the indication of the difference between the maximum number of LTM candidate configurations and the required number of LTM configurations includes receiving an indication of whether the difference is positive or negative.

[0093] In additional or alternative embodiments, receiving the request includes receiving an indication of a total number of LTM candidate configurations that are required by the first network node.

[0094] In additional or alternative embodiments, receiving the request from the first network node includes transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0095] At block 420, processing circuitry 802 transmits, via communication interface 806, an indication of the updated maximum number of LTM configurations. In some embodiments, the second network node further transmits an indication of an amount of time to wait before applying the updated maximum number of LTM configurations.

[0096] At block 430, processing circuitry 802 receives, via communication interface 806, a response in regards to the updated maximum number of LTM configurations. In some embodiments, receiving the response includes receiving a rejection of the updated maximum number of LTM configurations from the first network node. In some examples, receiving the rejection of the updated maximum number of LTM configurations includes receiving an indication of a LTM configuration that will not be used by the first network node. In additional or alternative examples, an indication of the rejection is included as part of an SN release. In additional or alternative embodiments, receiving the response includes receiving acknowledgement of the updated maximum number of LTM configurations from the first network node.

[0097] At block 440, processing circuitry 802 applies the updated maximum number of LTM configurations. In some embodiments, the updated maximum number is applied in response to receiving the acknowledgement.

[0098] At block 450, processing circuitry 802 triggers a context modification procedure to modify the LTM candidate configurations.

[0099] FIG. 5 illustrates an example of operations performed by a second network node that determines to ignore a request for an updated maximum number of LTM configurations. At block 510, processing circuitry 802 receives, via communication interface 806, a request for anupdated maximum number of LTM configurations to be used with a communication device. At block 520, processing circuitry 802 determines to maintain the current maximum number of LTM configurations. At block 530, processing circuitry 802 transmits, via communication interface 806, an indication of a rejection of the request. In some examples, the indication of the rejection includes a period of time elapsing since receiving the request.

[0100] Various operations from the flow charts of FIGS. 3-5 may be optional with respect to some embodiments of communication devices and related methods.

[0101] Example Embodiments are described below.

[0102] Embodiment 1. A method of operating a first network node in a communications network that includes a second network node, the method comprising: determining (310) that the first network node is configured with a maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device; responsive to determining that the maximum number of LTM configurations is different than a required number of LTM configurations to be used with the communication device, transmitting (320) a request to the second network node for an updated maximum number of LTM configurations to be used with the communication device; and receiving (330) an indication of the updated maximum number of LTM configurations from the second network node.

[0103] Embodiment 2. The method of Embodiment 1, wherein the first network node is configured to provide a secondary node, SN, and wherein the second network node is configured to provide a master node, MN.

[0104] Embodiment 3. The method of any of Embodiments 1-2, wherein transmitting the request includes transmitting an indication of a difference between the maximum number of LTM candidate configurations and the required number of LTM configurations.

[0105] Embodiment 4. The method of Embodiment 3, wherein transmitting the indication of the difference between the maximum number of LTM candidate configurations and the required number of LTM configurations comprises transmitting an indication of whether the difference is positive or negative.

[0106] Embodiment 5. The method of any of Embodiments 1-2, wherein transmitting the request includes transmitting an indication of a total number of LTM candidate configurations that are required by the first network node.

[0107] Embodiment 6. The method of any of Embodiments 1-5, further comprising:responsive to receiving the indication of the updated maximum number of LTM configurations, transmitting (340) a rejection of the updated maximum number of LTM configurations to the second network node.

[0108] Embodiment 7. The method of Embodiment 6, wherein transmitting the rejection of the updated maximum number of LTM configurations comprises transmitting an indication of a LTM configuration that will not be used by the first network node.

[0109] Embodiment s. The method of any of Embodiment 1-7, further comprising: responsive to an amount of time elapsing since receiving the updated maximum number ofLTM configurations, applying (350) the updated maximum number of LTM configurations.

[0110] Embodiment 9. The method of any of Embodiments 1-8, further comprising: subsequent to transmitting the request and / or to receiving the indication of the updated maximum number of LTM configurations, triggering (360) a context modification procedure to modify the LTM candidate configurations.

[0111] Embodiment 10. The method of any of Embodiments 1-9, wherein transmitting the request to the second network node comprises transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0112] Embodiment IL A method of operating a second network node in a communications network that includes a first network node, the method comprising: receiving (410) a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations; and transmitting (420) an indication of the updated maximum number of LTM configurations to the first network node.

[0113] Embodiment 12. The method of Embodiment 11, wherein the first network node is configured to provide a secondary node, SN, and wherein the second network node is configured to provide a master node, MN.

[0114] Embodiment 13. The method of any of Embodiments 11-21, wherein receiving the request includes receiving an indication of a difference between the maximum number of LTM candidate configurations and a required number of LTM configurations.

[0115] Embodiment 14. The method of Embodiment 13, wherein receiving the indication of the difference between the maximum number of LTM candidate configurations and the required number of LTM configurations comprises receiving an indication of whether the difference is positive or negative.

[0116] Embodiment 15. The method of any of Embodiments 11-12, wherein receiving the request includes receiving an indication of a total number of LTM candidate configurations that are required by the first network node.

[0117] Embodiment 16. The method of any of Embodiments 11-15, further comprising: responsive to transmitting the indication of the updated maximum number of LTM configurations, receiving (430) a rejection of the updated maximum number of LTM configurations from the first network node.

[0118] Embodiment 17. The method of Embodiment 16, wherein receiving the rejection of the updated maximum number of LTM configurations comprises receiving an indication of a LTM configuration that will not be used by the first network node.

[0119] Embodiment 18. The method of any of Embodiment 11-17, further comprising: receiving (430) acknowledgement of the updated maximum number of LTM configurations from the first network node; and responsive to receiving the acknowledgment, applying (440) the updated maximum number of LTM configurations.

[0120] Embodiment 19. The method of any of Embodiments 11-18, further comprising: subsequent to transmitting the indication of the updated maximum number of LTM configurations, triggering (450) a context modification procedure to modify the LTM candidate configurations.

[0121] Embodiment 20. The method of any of Embodiments 11-19, wherein receiving the request from the first network node comprises transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

[0122] Embodiment 21. A method of operating a second network node in a communications network that includes a first network node, the method comprising: receiving (510) a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations; and determining (520) to maintain a current maximum number of LTM configurations as the updated maximum number of LTM configurations.

[0123] Embodiment 22. A network node (QQ300) adapted to perform any of the operations of Embodiments 1-21.

[0124] Embodiment 23. A computer program comprising program code to be executed by processing circuitry (QQ302) of a network node (QQ300), whereby execution of the program code causes the network node to perform any of the operations of Embodiments 1-21.

[0125] Embodiment 24. A computer program product comprising a non-transitory storage medium (QQ304) including program code to be executed by processing circuitry (QQ302) of a network node (QQ300), whereby execution of the program code causes the network node to perform any of the operations of Embodiments 1-21.

[0126] FIG. 6 shows an example of a communication system 600 in accordance with some embodiments.

[0127] In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. Moreover, as will be appreciated by those of skill in the art, the network nodes 610 are not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that the network nodes 610 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 602 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 602 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 602, including one or more network nodes 610 and / or core network nodes 608.

[0128] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualizationenvironment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.

[0129] 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. Moreover, in different embodiments, the communication system 600 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 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0130] The UEs 612 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 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 612 and / or with other network nodes or equipment in the telecommunication network 602 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 602.

[0131] In the depicted example, the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. 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 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), HomeSubscriber 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).

[0132] The host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and / or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider. The host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as 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.

[0133] As a whole, the communication system 600 of FIG. 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, 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., 6G); wireless local area network (WLAN) standards, 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.

[0134] In some examples, the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 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 loT services to yet further UEs.

[0135] In some examples, the UEs 612 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. Additionally,a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, 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).

[0136] In the example, a hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 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. As another example, the hub 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 614 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.

[0137] The hub 614 may have a constant / persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication scheme and / or schedule between the hub 614 and UEs (e.g., UE 612c and / or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 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 610b. In other embodiments, the hub 614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0138] FIG. 7 shows a UE 700 in accordance with some embodiments. As used herein, 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 UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, 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. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0139] A 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). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, 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). Alternatively, 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).

[0140] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 7. 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.

[0141] The processing circuitry 702 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 710. The processing circuitry 702 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), togetherwith appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).

[0142] In the example, the input / output interface 706 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 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, 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.

[0143] In some embodiments, the power source 708 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 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.

[0144] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.

[0145] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, externalhard 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 USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow the UE 700 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 710, which may be or comprise a device-readable storage medium.

[0146] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 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 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0147] In the illustrated embodiment, communication functions of the communication interface 712 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), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0148] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, 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).

[0149] As another example, 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. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0150] 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. Non-limiting examples of such an loT device are a device which is or which is 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, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 700 shown in FIG. 7.

[0151] As yet another specific example, in an loT scenario, 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. As oneparticular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, 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.

[0152] In practice, any number of UEs may be used together with respect to a single use case. For example, 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. When the user makes changes from the remote controller, 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. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0153] FIG. 8 shows a network node 800 in accordance with some embodiments. As used herein, 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. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), NRNodeBs (gNBs)), O-RAN nodes, or components of an O-RAN node (e.g., intelligent controller, O-RU, O-DU, O-CU).

[0154] 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. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0155] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), 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).

[0156] The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 800.

[0157] The processing circuitry 802 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 800 components, such as the memory 804, to provide network node 800 functionality.

[0158] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

[0159] The memory 804 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 othervolatile 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 802. The memory 804 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 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

[0160] The communication interface 806 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. The communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 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 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0161] In certain alternative embodiments, the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

[0162] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-endcircuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.

[0163] The antenna 810, communication interface 806, and / or the processing circuitry 802 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 810, the communication interface 806, and / or the processing circuitry 802 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.

[0164] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 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 808. As a further example, the power source 808 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.

[0165] Embodiments of the network node 800 may include additional components beyond those shown in FIG. 8 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. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.

[0166] FIG. 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of FIG. 6, in accordance with various aspects described herein. As used herein, the host 900 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 900 may provide one or more services to one or more UEs.

[0167] The host 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a network interface 908, a power source 910, and a memory 912. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of host 900.

[0168] The memory 912 may include one or more computer programs including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by a UE for the host 900 or data generated by the host 900 for a UE. Embodiments of the host 900 may utilize only a subset or all of the components shown. The host application programs 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 900 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0169] FIG. 10 is a block diagram illustrating a virtualization environment 1000 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, 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 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1000 includes components defined by the O-RAN Alliance, such asan O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0170] Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0171] Hardware 1004 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 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

[0172] The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, 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.

[0173] In the context of NFV, a VM 1008 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 1008, and that part of hardware 1004 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. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.

[0174] Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization.Alternatively, hardware 1004 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 1010, which, among others, oversees lifecycle management of applications1002. In some embodiments, hardware 1004 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. In some embodiments, some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

[0175] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, 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. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0176] In certain embodiments, some or all of the functionality described herein may be provided by 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. In alternative embodiments, 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. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to theprocessing 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.

Claims

CLAIMSWhat is claimed is:

1. A method of operating a first network node in a communications network that includes a second network node, the method comprising: determining (310) that the first network node is configured with a maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device; transmitting (320) a request to the second network node for an updated maximum number of LTM configurations to be used with the communication device; and receiving (330) an indication of the updated maximum number of LTM configurations from the second network node.

2. The method of Claim 1, wherein transmitting the request comprises transmitting the request in response to determining that the maximum number of LTM configurations is different than a required number of LTM configurations to be used with the communication device.

3. The method of Claim 2, wherein transmitting the request comprises transmitting the request in response to determining that the maximum number of LTM configurations is less than the required number of LTM configurations to be used with the communication device.

4. The method of Claim 2, wherein transmitting the request comprises transmitting the request in response to determining that the maximum number of LTM configurations is greater than the required number of LTM configurations to be used with the communication device.

5. The method of any of Claims 1-4, wherein the first network node is configured to provide a secondary node, SN, and wherein the second network node is configured to provide a master node, MN.

6. The method of any of Claims 1-5, wherein transmitting the request includes transmitting an indication of a difference between the maximum number of LTM configurations and the required number of LTM configurations, and wherein transmitting the indication of the difference between the maximum number of LTM configurations and the required number of LTM configurations comprises transmitting anindication of whether the difference is positive or negative.

7. The method of any of Claims 1-6, wherein transmitting the request includes transmitting an indication of a total number of LTM configurations that are required by the first network node.

8. The method of any of Claims 1-7, further comprising: responsive to receiving the indication of the updated maximum number of LTM configurations, transmitting (340) an indication of a rejection of the updated maximum number of LTM configurations to the second network node, wherein transmitting the indication of the rejection of the updated maximum number of LTM configurations comprises transmitting an indication of a LTM configuration that will not be used by the first network node.

9. The method of any of Claim 1-8, further comprising: responsive to an amount of time elapsing since receiving the updated maximum number of LTM configurations, applying (350) the updated maximum number of LTM configurations.

10. The method of any of Claims 1-9, further comprising: subsequent to transmitting the request and / or to receiving the indication of the updated maximum number of LTM configurations, triggering (360) a context modification procedure to modify the LTM configurations.

11. The method of any of Claims 1-10, wherein transmitting the request to the second network node comprises transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

12. The method of Claim any of Claims 1-11, wherein determining that the first network node is configured with the maximum number of LTM configurations comprises receiving an indication of the maximum number of LTM configurations to be used with the communication device from the second network node.

13. A method of operating a second network node in a communications network that includes a first network node, the method comprising:receiving (410) a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device; and transmitting (420) an indication of the updated maximum number of LTM configurations to the first network node.

14. The method of Claim 13, further comprising: transmitting (405) an indication of a first maximum number of LTM configurations to the first network node, wherein receiving the request comprises receiving the request subsequent to transmitting the indication of the first maximum number of LTM configurations.

15. The method of any of Claims 13-14, wherein the first network node is configured to provide a secondary node, SN, and wherein the second network node is configured to provide a master node, MN.

16. The method of any of Claims 13-15, wherein receiving the request includes receiving an indication of a difference between the maximum number of LTM configurations and a required number of LTM configurations, and wherein receiving the indication of the difference between the maximum number of LTM configurations and the required number of LTM configurations comprises receiving an indication of whether the difference is positive or negative.

17. The method of any of Claims 13-16, wherein receiving the request includes receiving an indication of a total number of LTM configurations that are required by the first network node.

18. The method of any of Claims 13-17, further comprising: responsive to transmitting the indication of the updated maximum number of LTM configurations, receiving (430) an indication of a rejection of the updated maximum number of LTM configurations from the first network node, wherein receiving the indication of the rejection of the updated maximum number of LTM configurations comprises receiving an indication of a LTM configuration that will not be used by the first network node.

19. The method of any of Claim 13-18, further comprising:receiving (430) acknowledgement of the updated maximum number of LTM configurations from the first network node; and responsive to receiving the acknowledgment, applying (440) the updated maximum number of LTM configurations.

20. The method of any of Claims 13-19, further comprising: subsequent to transmitting the indication of the updated maximum number of LTM configurations, triggering (450) a context modification procedure to modify the LTM configurations.

21. The method of any of Claims 13-20, wherein receiving the request from the first network node comprises transmitting the request via at least one of: an inter-node radio resource control, RRC, message; and an Xn signal.

22. A method of operating a second network node in a communications network that includes a first network node, the method comprising: receiving (510) a request from the first network node for an updated maximum number of layer 1 / layer 2-triggered mobility, LTM, configurations to be used with a communication device; and determining (520) to maintain a current maximum number of LTM configurations as the updated maximum number of LTM configurations.

23. The method of Claim 22, wherein the first network node is configured to provide a secondary node, SN, and wherein the second network node is configured to provide a master node, MN.

24. The method of any of Claims 22-23, wherein receiving the request includes receiving an indication of a difference between the maximum number of LTM configurations and a required number of LTM configurations, and wherein receiving the indication of the difference between the maximum number of LTM configurations and the required number of LTM configurations comprises receiving an indication of whether the difference is positive or negative.

25. The method of any of Claims 22-24, wherein receiving the request includes receiving anindication of a total number of LTM configurations that are required by the first network node.

26. The method of any of Claims 22-25, further comprising: transmitting (530) an indication of a rejection of the request.

27. A network node (800) adapted to perform any of the operations of Claims 1-26.

28. A computer program comprising program code to be executed by processing circuitry (802) of a network node (800), whereby execution of the program code causes the network node to perform any of the operations of Claims 1-26.

29. A computer program product comprising a non-transitory storage medium (804) including program code to be executed by processing circuitry (802) of a network node (800), whereby execution of the program code causes the network node to perform any of the operations of Claims 1-26.

Images