Method and system for provisioning of dynamic network slice coverage

Abstract

Methods and systems are described for reprovisioning a network slice or a network slice subnet configured on a first portion of a network. A movement of a UE connected to the network is detected. Movement prediction of the UE is generated. Then, based on at least one of the movement and the movement prediction, the network slice or the network slice subnet is allocated on a second portion of the network and deallocated on a third portion of the network. The second portion of the network was not configured with the network slice or the network slice subnet before the allocation. The third portion of the network is part of the first portion of the network.

Description

Pl 12426METHOD AND SYSTEM FOR PROVISIONING OF DYNAMIC NETWORK SLICE COVERAGETECHNICAL FIELD

[0001] The present disclosure generally relates to systems and methods for reprovisioning a network slice or a network slice subnet configured on a network. A corresponding computer program and computer program product are also discussed.BACKGROUND

[0002] 5G Networks include the feature of Network Slicing, which can simultaneously provide many different types of virtual networks within a physical network. Each virtual network can be tailored to different use cases and their communication needs. Standards organizations such as 3 GPP have specified the framework, operations and data models that support a multi-vendor standardized implementation of Network Slicing capabilities, both in the network itself, and in the orchestration and management of those capabilities by OSS and BSS software.

[0003] Central to the 3GPP standard are the definitions of Network Slice and Network Slice-Subnet, and corresponding management functions identified for managing instances of those, as shown in Table 1.Pl 12426Table 1

[0004] A service requirement of provisioning of a network slice through orchestration components aligning to the 3GPP standards is the specification of the service area, or area of coverage. The smallest unit of coverage is one radio cell, or cell, and all coverage representations ultimately translate to per-cell coverage. 3GPP specifies coverage area specification for a slice subnet as a list of tracking areas. A tracking area is a logical grouping of RAN cells that are identified together by a common tracking area code, created in order to be used as part of idle UE paging mechanisms in the RAN and to reduce UE registration updates. As part of regular cell planning, the operator configures and occasionally modifies the tracking area codes of radio cells, in order to strike a balance between the amount of UE signaling and the area to page - number of cells to page vs. frequency of paging operation. A coverage area at any one time therefore corresponds to a fixed set of cells in the network known to the operator.

[0005] Specification of the required coverage area for a network slice and network slice subnet in 3GPP is part of the ServiceProfile and SliceProfile data structures respectively. For network slice provisioning or allocation in the 3GPP specification, the consumer of the Network Slice Management Function supplies a coverageArea value, containing a geographic region representation as a string type, as shown in the ServiceProfile dataType attribute list (Section 6.3.3.2) in Fig. 1 and the ServiceProfile coverageArea attribute description and properties (Section 6.4.1) in Fig. 2, from 3GPP TS 28.541 V18.3.1 (2023-04).

[0006] For provisioning or allocation of a Network Slice Subnet by a Network Slice Subnet Management Function, the relevant input parameter is coverageAreaTAEist, which specifies a list of Tracking Area identifiers, as shown in the RANSliceProfile dataType attribute list (Section 6.3.24.2) in Fig. 3 and the RANSliceProfile coverageAreaTAEist attribute description and properties (Section 6.4.1) in Fig. 4, from 3GPP TS 28.541 V18.3.1 (2023-04).Concepts of Tracking Area and Registration Area (5G)

[0007] A tracking area (TA) in 5G is a logical grouping of NR (New Radio) Cells, identified by a Tracking Area Code (TAC). A registration area (RA) in 5G is an amalgamation of one or more TAs. Registration Areas are used for idle UE paging, by thePl 12426Access and Mobility Management Function (AMF) to control TAC-level messaging and have awareness of which registration area a UE is currently in. This is called the Registration Procedure.

[0008] Fig. 5 illustrates one example of an arrangement of NR cells (3110a), TAs (502a, 502b, 502c) — also shown as TAI, TA2, TA3 — and RAs (504a, 504b) managed by AMFs (3108a, 3108b). In this example, TA 502a includes cell 1 (3110a), TA 502b includes cell 2, and TA 502c includes cells 3 and 4. Additionally, registration area 1 (504a) is composed of TA 502a and registration area 2 (504b) is composed of multiple TAs, namely TA 502b and TA 502c. Further, AMF 3108a manages RA 504a while AMF 3108b manages RA 504b. As shown in the illustration, UE 3112a is traversing the registration area boundary defined by registration area 1 and registration area 2, which triggers a RA update via AMFs (3018a, 3108b).

[0009] Network slicing according to existing 3GPP specifications is based on static provisioning, in particular using 3GPP requirements CoverageArea, CoverageAreaTAList as described above, according to whether an end-to-end slice or a slice subnet is being allocated, by an NSMF or NSSMF, respectively. The coverage input at the lower NSSMF level is a set of cell tracking area codes. At the NSMF level, the coverage is expressed as a geographical area input, which must internally be translated to a corresponding set of cell tracking area codes when invoking the allocation requests on the slice subnet constituents. The tracking areas equate to the same geographical area requirement.

[0010] A first use case for network slicing provisioning within an operator’s network is the ‘nationwide’ case, corresponding to availability of the network slice across the entire network that the operator offers to its subscribers before roaming handovers, typically aligning to national boundaries. A nationwide network slice incurs high roll-out and management operational expenditure.

[0011] A second use case for network slicing provisioning is where a network slice is localized to a defined sub-area within the network. This may be done, for example, to enable a premium network quality of service for the attendees at a sports event.

[0012] Problems exist with these use cases. Provisioning using a nationwide network slice is possible, but wasteful and expensive for occasional or low-volume use. Provisioning using individual slices configured and removed day-by-day is an operations andPl 12426maintenance burden. Accordingly, there is a need to address these issues to incur the benefits of network slicing while minimizing waste, expense, and overhead. It is believed that no one prior to the inventors has made or used an invention as described herein.SUMMARY

[0013] An object of the disclosed embodiments is to dynamically reprovision a network slice or network slice subnet in a communication network.

[0014] A first embodiment of the disclosed technology includes a method performed by a network for reprovisioning a network slice or a network slice subnet configured on a first portion of the network. The method comprises detecting a movement of a UE connected to the network, generating a movement prediction of the UE, allocating, based on at least one of the movement and the movement prediction, the network slice or the network slice subnet on a second portion of the network, wherein the second portion was not configured with the network slice or the network slice subnet before the allocation. The method also comprises deallocating, based on at least one of the movement and the movement prediction, the network slice or the network slice subnet on a third portion of the network, wherein the first portion comprises the third portion.

[0015] A second embodiment is the method of the first embodiment, wherein the movement is from a first tracking area to a second tracking area, wherein the network comprises the first tracking area and the second tracking area.

[0016] A third embodiment is the method of the first embodiment, wherein the movement prediction is from a current tracking area to a future tracking area, wherein the network comprises the current tracking area and the future tracking area, and wherein the UE is associated with the current tracking area and not associated with the future tracking area.

[0017] A fourth embodiment is a method for reprovisioning a network slice or a network slice subnet configured on a network. The method comprises receiving a configuration of the network slice or the network slice subnet comprising dynamic network slice parameters. The configuration comprises at least one UE to be supported by the network slice or the network slice subnet. The method also comprises receiving a registration area associated with the at least one UE, wherein the network comprises the registration area, receiving a movement prediction of thePl 12426at least one UE, identifying, based on at least one of the registration area and the movement prediction, at least one component of the network to be reprovisioned, sending, to the at least one component, reprovisioning instructions based on the configuration, wherein the reprovisioning instructions either allocate or deallocate the network slice or the network slice subnet on the at least one component.

[0018] A fifth embodiment is the method of the fourth embodiment, wherein the configuration further comprises data associated with the at least one UE that will be supported by the network slice or the network slice subnet.

[0019] A sixth embodiment is the method of the fourth or fifth embodiments, wherein the at least one component is associated with one or more target tracking areas of the network, and wherein the at least one UE is not associated with at least one of the target tracking areas.

[0020] A seventh embodiment is the method of the sixth embodiment, wherein the at least one component is part of the RAN of the network, the RAN comprises the one or more target tracking areas, and the reprovisioning instructions are sent to the NSSMF of the RAN.

[0021] An eight embodiment is the method of the seventh embodiment, wherein the at least one component comprises a cell of the network.

[0022] A ninth embodiment is the method of the sixth embodiment, wherein the at least one component is part of the core network of the network and the reprovisioning instructions are sent to at least the NSSMF of the core network.

[0023] A tenth embodiment is the method of the ninth embodiment, wherein the at least one component is at least one of an AMF, an SMF, a UPF, and an MME.

[0024] An eleventh embodiment is a method for reprovisioning a network slice or a network slice subnet configured on a network. The method comprises detecting a movement of a UE connected to the network from a first tracking area to a second tracking area. The network comprises the first tracking area and the second tracking area, and wherein each of the first tracking area and the second tracking area are associated with a registration area of the network. The method also comprises sending, to a controller, the registration area associated with the second tracking area if the registration area associated with the second tracking area is different than the registration area associated with the first tracking area.Pl 12426

[0025] A twelfth embodiment is the method of the eleventh embodiment, wherein the movement is detected based on at least one of a tracking area update message and a registration area update message.

[0026] A thirteenth embodiment is the method of the eleventh or twelfth embodiments, further comprising updating a counter based on the detected movement.

[0027] A fourteenth embodiment is the method of the thirteenth embodiment, wherein the counter is one of a RAN counter, a UE counter, and a core network counter.

[0028] A fifteenth embodiment is a method for reprovisioning a network slice or a network slice subnet configured on a network. The method comprises generating a movement prediction of a UE connected to the network from a current tracking area to a future tracking area. The network comprises the current tracking area and the future tracking area. The UE is associated with the current tracking area and not associated with the future tracking area. The method also comprises sending, to a controller, the movement prediction.

[0029] A sixteenth embodiment is the method of the fifteenth embodiment, wherein the movement prediction is based on one or more of knowledge of the history of a previous path travelled by the UE, GPS data, computed velocity, computed trajectory, terrestrial infrastructure knowledge, and intended destination of the UE.

[0030] A seventeenth embodiment is the method of the fifteenth or sixteenth embodiments, further comprising sending, to the controller, information based on a capacity of the future tracking area.

[0031] An eighteenth embodiment is the method of any of the fifteenth through seventeenth embodiments, wherein the movement prediction is generated with an AI / ML engine.

[0032] A nineteenth embodiment is the method of the eighteenth embodiment, wherein the AI / ML engine is trained using a dataset comprising knowledge of the history of previous paths travelled by a plurality of UEs and terrestrial infrastructure knowledge.

[0033] A twentieth embodiment is a system for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of the first through the third embodiments.Pl 12426

[0034] A twenty-first embodiment is an apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of the fourth through tenth embodiments.

[0035] A twenty-second embodiment is an apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of the eleventh through fourteenth embodiments.

[0036] A twenty-third embodiment is an apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of the fifteenth through nineteenth embodiments.

[0037] A twenty-fourth embodiment is a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of the first through nineteenth embodiments.

[0038] A twenty-fifth embodiment is a computer program product, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of the fifth through nineteenth embodiments.

[0039] A twenty-sixth embodiment is the method of the second embodiment, wherein each of the first tracking area and the second tracking area are associated with a registration area of the network, the method further comprising sending, to a controller, the registration area associated with the second tracking area if the registration area associated with the second tracking area is different than the registration area associated with the first tracking area.

[0040] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.Pl 12426BRIEF DESCRIPTION OF THE DRAWINGS

[0041] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0042] Fig. 1 illustrates a table of ServiceProfile dataType attributes;

[0043] Fig. 2 illustrates a table of ServiceProfile coverageArea attribute description and properties;

[0044] Fig. 3 illustrates a table of RANSliceProfile dataType attributes;

[0045] Fig. 4 illustrates a table of RANSliceProfile coverageAreaTAList attribute description and properties;

[0046] Fig. 5 illustrates the concept of tracking areas and registration areas for cells;

[0047] Fig. 6 shows a flow-chart illustrating one method for reprovisioning a network slice or a network slice subnet according to the present disclosure;

[0048] Fig. 7 shows a flow-chart illustrating another method for reprovisioning a network slice or a network slice subnet according to the present disclosure;

[0049] Fig. 8 shows a flow-chart illustrating a third method for reprovisioning a network slice or a network slice subnet according to the present disclosure;

[0050] Fig. 9 illustrates an example of tracking areas configured with an initial network slice configuration;

[0051] Fig. 10 shows a flow-chart illustrating a fourth method for reprovisioning a network slice or a network slice subnet according to the present disclosure;

[0052] Fig. 11 illustrates an example of an automated slice reconfiguration following UE traversal of registration areas;

[0053] Figs. 12A and 12B illustrate examples of deployment environments for automated slice reconfiguration;

[0054] Fig. 13 illustrates an example of an impact to the 5G core during automated slice reconfiguration;Pl 12426

[0055] Fig. 14 shows a flow chart illustrating training and inference pipelines for machine learning in accordance with some embodiments under the present disclosure;

[0056] Fig. 15 shows an embodiment of a neural network under the present disclosure;

[0057] Fig. 16 shows a schematic of a communication system embodiment under the present disclosure;

[0058] Fig. 17 shows a schematic representation of an embodiment of communication amongst nodes, hosts, and user equipment under the present disclosure;

[0059] Fig. 18 shows a schematic of a user equipment, or wireless device, embodiment under the present disclosure;

[0060] Fig. 19 shows a schematic of a network node embodiment under the present disclosure; and

[0061] Fig. 20 shows a schematic of a virtualization environment embodiment under the present disclosure.DETAILED DESCRIPTION

[0062] Before describing various embodiments of the present disclosure in detail, it is to be understood that this disclosure is not limited to the parameters of the particularly exemplified systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Thus, while certain embodiments of the present disclosure will be described in detail, with reference to specific configurations, parameters, components, elements, etc., the descriptions are illustrative and are not to be construed as limiting the scope of the claimed embodiments. In addition, the terminology used herein is for the purpose of describing the embodiments and is not necessarily intended to limit the scope of the claimed embodiments.

[0063] As discussed herein, the terms network slice, slice, network slice subnet may be used interchangeably with the understanding that attributes particular to a specific term and incompatible with another term stem from their particular term. Moreover, a single term may be representative of all the terms. For example, the term slice may be used to refer to both a network slice and a network slice subnet.Pl 12426

[0064] Also as discussed herein, the terms subscriber movement, user movement, and UE or UE movement may be used interchangeably. Similarly, the terms mobility and movement may be used interchangeably.

[0065] Certain aspects of the disclosure and their embodiments may provide solutions to the aforementioned challenges. A sub-area, or limited area, of a network may be created that is limited in size but expected to move during the operation of the network slice. For example, a moving premium quality of service network slice sold to a team of specialist contractors that work together but at locations that vary day-by-day. The contractors may have robotic machinery that needs specific slice service level agreement, SLA, wherever they operate. Stated differently, these moving and limited area network slices enable active provisioning and modification, or reprovisioning, of the network slices.

[0066] Methods and systems are disclosed that provide dynamic area of coverage reconfiguration for a network slice or network slice subnet based on the actual and / or predicted movement of UEs subscribed to the network slice. This may be achieved with a new 3GPP standard input attribute requirement for selection. When enabled, the slice coverage may be automatically adjusted in real-time based on subscriber movement, thereby giving a person-centric or activity-centric approach rather than a location-based approach. By way of non-limiting example, a group of subscribers, with dynamic coverage enabled, could have their purchased network slice seamlessly ‘follow’ them as they move within the network. Portions of the network would have the network slice allocated ahead and deallocated behind the moving UE(s) of the group of subscriber. Efficiencies and cost-savings for the operator at both the node and network levels by provisioning according to need (i.e., just-in-time) would be realized compared to nationwide blanket coverage provisioning.

[0067] A ‘follow-us’ method, such as method 600 illustrated in Fig. 6, to support the provisioning of network slices with dynamic coverage is envisioned. Method 600 may comprise the following three modules, which may be discrete or integrated in any combination, and may loop continually:(1) A controller module 602 that may receive the specification of the requirements for dynamic slices (input requirements), control the overall sequence of operations, and interact with existing slice configuration functionalityPl 12426(2) A movement detection module 604 that may detect the actual travel of each of the included UEs based on, for example, Registration Area Update messages(3) A movement prediction module 606 that may determine the predicted travel of the applicable UEs based on, for example, current trajectory

[0068] Based on the outputs of detection module 604 and / or prediction module 606, the controller module 602 may reprovision the active network slice in real time by configuring the appropriate network elements and cells, effectively adding and removing coverage.

[0069] The method 600 may be implemented, for example, in one embodiment by an OSS / BSS component such as an Orchestration and Assurance product responsible for Network Slice lifecycle management, which itself may be cloud native. In another embodiment, the method 600 may be implemented using an O-RAN Service, Management and Orchestration Framework (SMO) that includes a RAN NSSMF capability as part of its scope, implemented by an rApp in the non-realtime RAN Intelligent Controller.

[0070] Certain embodiments may provide one or more of the following technical advantages. Demand-based dynamic provisioning, rather than static provisioning, enables a subscriber group to have a mobile limited-area network slice, as described above, which is not possible with existing static provisioning for network slices.

[0071] An additional advantage is the enabling of a network efficient and automated orchestration for mobile limited-area use-cases. Examples include premium gaming while travelling, healthcare and emergency response, premium content at venue which then continues to be active for a time period beyond, such as while travelling home.

[0072] Yet another advantage is provided in the form of energy savings, reducing the need to provision cells and gNodeBs with allocated resources for a network slice across large areas of coverage which may never be used by the subscribers of that slice, which is a waste of resources.

[0073] Furthermore, operator management cost and resource reservation cost across the RAN and Core network may be reduced.

[0074] 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.Pl 12426

[0075] Fig. 7 shows a flow-chart illustrating a method 700 for reprovisioning a network slice or a network slice subnet according to the present disclosure. Method 700 may be, in one embodiment, carried out on a controller module that is responsible for the overall flow and interaction with external components. Initially, the controller module may receive 702 input requirements for the configuration of a network slice or network slice subnet. This may include details of the subscribers or UEs that are to be supported by the slice / slice-subnet. The controller module may also, in some embodiments, receive an indication from a motion detection module that a subscriber or UE is on the move. The controller module may contain the logic to configure the initial state of the network slice, and to receive 704, 706 and / or interpret the results of one or both of the motion detection modules and to identify 708 the appropriate reconfiguration (or reprovisioning) steps. The steps may then be sent 710 to the necessary external components.

[0076] The controller module may coordinate with the other modules for deciding on the right configuration. For example, based upon the received 706 projection of the target cell where a UE is moving to, the controller module would identify 708 the target TAC / geo-location that needs to be provisioned for both RAN and core network slicing and then send 710 the right configuration for RAN NSSMF and core NSSMF. Depending on the quality of the predicted path, the controller may identify some, all or one adjacent target to cover.

[0077] In another embodiment, the controller module, and therefore method 700, may be responsible for Service Level Agreement maintenance of the slices in situations of congestion and contention, and identify (not shown) which slices / customers to prioritize.

[0078] Fig. 8 shows a flow-chart illustrating a method 800 for reprovisioning a network slice or a network slice subnet according to the present disclosure. Method 800 may be, in one embodiment, carried out by a movement detection module. This module is responsible for detecting 802 the motion of a UE, which may act as a trigger to the method 700. Detection 802 may use the tracking area and / or registration procedure messaging to detect movement. More granular UE-level cell-to-cell handover messaging could also be used to detect movement.

[0079] Mobility within same registration area (RA). Each registration area includes a list of tracking areas. For user mobility within tracking areas of same registration area, users can be served with same AMF / MME. However, in order to ensure slice quality of service (QoS) / Pl 12426quality of experience (QoE), RAN and UE counters may be used for location update as well as to determine radio resource capacity.

[0080] Mobility between multiple Registration areas. When the UE moves to a tracking area outside its current TA list (served by existing RA), the UE may perform a tracking area update procedure. In this scenario, core network counters / key performance indicators (KPIs) from access and mobility management functions (AMFs) and / or session management functions (SMFs) may be used to make sure the target AMF is configured for the slice service subscribed by the user.

[0081] The movement detection module may monitor mobility behavior among tracking areas that are part of the same registration area and tracking areas that are part of different registration areas. The Mobility Registration Update procedure uses Registration Update message of type Mobility instead of type Initial or type Periodic. The message is routed to the relevant AMF, which may be a new one. Having the view at the registration area level would allow for knowledge of which target MME needs to be provisioned for network slice capabilities that the slice service user has opted for.

[0082] Detecting the UE Motion across TAs both intra and inter RAs provides the means to detect the new coverage requirement for the slice.

[0083] Fig. 9 illustrates an example of tracking areas (TA1-TA10) configured with an initial network slice configuration 904. Accordingly, some tracking areas (TA3, TA7, TA10) do not have the initial network slice configuration 906. In this part of a RAN cellular network, a UE 3112a is located within a starting registration area and associated with an initial registration cell 902. Here, registration areas are comprised of a single tracking area for simplicity of illustration, though registration areas typically span multiple tracking areas. The coverage area of the initial network slice configuration 906 may have been decided by the controller. As shown, the registration areas immediately adjacent to (TAI, TA2, TA4, TA6, TA8, TA9) the RA where the UE 3112a is initially registered (TA5) are included in the initial network slice configuration as a buffer. This buffer may avoid gaps due to not being able to apply new slice coverage quickly enough. Other initial network slice configurations are possible.Pl 12426

[0084] If the UE 3112a moves into another RA, as shown in Fig. 11 below, the movement detection module, via the method 800, detects 802 this motion, and reports 804 the new RA to the controller module.

[0085] The method of identification and maintenance of the list of cells forming the border cells of a particular network slice may provide efficiencies that aid in the operation of the modules that determine subscriber UE motion. Border or boundary cells are identified as those cells forming the edge of coverage of a configured network slice. The identification of border or boundary cells may include a self-updating procedure that takes into account network changes such as cell or tracking area or registration area (paging) reconfiguration.

[0086] The information acquired by these methods can be used in network operations, such as admission control policies that can prioritize UEs using the network slice, energy efficiency policies that can favor maintaining full power in border cells, or other radio resource management policies. The information leads to better mechanisms for keeping network slices in service.

[0087] Fig. 10 shows a flow-chart illustrating a method 1000 for reprovisioning a network slice or a network slice subnet according to the present disclosure. Method 100 may be, in one embodiment, carried out by a movement prediction module. Method 1000 is responsible for predicting 1002 the likely motion of a UE and then sending 1004 the prediction as information to the controller module, acting as another potential trigger to the reprovisioning process. The predicting 1002 may leverage a variety of information. In some embodiments, the information may include knowledge of the history of a UEs’ previous path travelled, computed velocity, computed trajectory, underlying terrestrial infrastructure knowledge such as roads and rail lines, input details such as intended destination, or any combination thereof.

[0088] KPIs may also be leveraged when the predicting 1002 is carried out. KPIs may provide 1006, in some embodiments, additional information to the controller regarding the capacity of the predicted location, which may help determine the appropriate reconfiguration, or mitigation steps where insufficient network capacity exists.

[0089] Additionally, in some embodiments, Al generated prediction may also be employed, using a machine learning Al function to predict a likely next destination of cells for the UE’s based on a wide data set.Pl 12426RAN Slice-Subnet automated reprovisioning by Follow-Us method

[0090] In an embodiment of the method 600, a function of the controller module 602 is to automatically reprovision the network slice based on the data from the movement detection module 604 and / or the movement prediction module 606. The reprovisioning will immediately extend the coverage of a UE’s active slice to the cells corresponding to the tracking areas of the new registration area, in order to have uninterrupted service of the active slice. In some embodiments, the surrounding RAs of the new RA may be preemptively covered, to one or more levels of contiguity, as a means to slightly overprovision to include all of the next possible registration areas the UE could move to in order to ensure seamless availability but balancing this against the configuration cost.

[0091] The controller module 602 may decide or be configured to simultaneously or otherwise deprovision the active slice from previously activated coverage areas, maintaining only an optimally focused patch of coverage as opposed to the full historical track.

[0092] Fig. 11 illustrates an example of an automated slice reconfiguration following a traversal of registration areas by UE 3112a. Here, the UE 3112a has moved from TA5 to TA6. The controller module 602 has assessed the motion outputs from the movement detection module 604 and / or the movement prediction module 606 and decided to extend slice coverage to TA3, TA7 and TA 10, collectively the newly configured registration areas 1102. At the same time, the controller module 602 has decided to remove the slice availability from TAI, TA4 and TA8, collectively the de-configured registration areas 1106. The slice availability at TA2, TA5, TA6, and TA9, collectively the continuing registration areas 1104, remains unchanged.Core Slice-Subnet automated reprovisioning by Follow-Us method

[0093] In another embodiment, the core network may also need to be updated based on the knowledge derived by the controller module 602 for end-to-end slice availability. For example, when a user moves closer to a tracking area that is controlled by different 5G core functions (e.g., AMF, SMF, UPF) than the currently serving network functions, as shown in Figs.12A and 12B, UE location information analysis may be used to provision the target core functions with the network slice service opted by the user. This would allow the UE to register for the opted S-NSSAIs during registration area update procedure. The core dynamic slice re-configuration isPl 12426beneficial for edge deployments when UPF would be deployed at edge locations while AMF and SMF might be deployed at central locations.

[0094] Fig. 13 illustrates an example of an impact to the 5G core during automated slice reconfiguration. As illustrated in Fig. 13, the AMF 1 1304a and UPF 1 1306a are current serving Core network functions — supporting paging and user plane traffic, for example — for the service user registration area that includes TAC 1 1308a and TAC 2 1308b.

[0095] TAC 3 1308c is being served by a separate AMF and UPF, AMF 2 1304b and UPF 2 1306b. By considering user mobility behavior, it is important to provision the TAC 3 1308c RAN and core network functions with the slice service opted by a user to enable slice service continuity. Accordingly, the controller module 602 may instruct the core NSSMF 1302 to provision the core resources — AMF 2 1304b and UPF 2 1306b in this example — by means of, for example, a core service order and a RAN service order. With this provisioning, the network would be ready for the user once they move to the target TA, TAC 3 1308c, permitting UE slice service continuity. The target AMF, AMF 2 1304b, would be able to register the user for services they have opted for instead of default service.

[0096] Implementation of the embodiments disclosed herein may expose management and scheduling capability to provide restrictions and customizations in order to save unnecessary cost, for example. Additional restrictions may include geographical limitations such as a distance (e.g., within 100km of a headquarters), or time-related (e.g., Monday-Friday working hours only). Other restrictions may include operating within relevant local privacy legislation regarding, for example, the tracking of users.

[0097] Various embodiments under the present disclosure can incorporate AI / ML functionality. For example, for purposes of the present disclosure, the movement prediction module 606 of Fig. 6 and method 1000 of Fig. 10 can be said to make use of an AI / ML engine (not shown). An apparatus implementing the movement prediction module 606 may comprise the AI / ML engine, or a “central” AI / ML engine could be running at the controller module 602, or another location on the network in communication with the movement prediction module 606. As described above, the AI / ML engine may leverage data about the history of previous paths travelled by a plurality of UEs, terrestrial infrastructure knowledge or otherwise receive or utilize a varietyPl 12426of other data. This data can be used to generate a movement prediction for a UE. This data can also be used to train the AI / ML engine, or can be analyzed by a previously trained AI / ML engine.

[0098] It should be understood that the AI / ML engine can comprise one or more AI / ML engines. Commonly the terms machine learning engine or machine learning algorithm are used to refer to a specific algorithm. The term artificial intelligence commonly is used to refer to an entire system that achieves intelligence-like outcomes while using multiple sub-systems, such as multiple machine learning algorithms. But both ML and Al have been used to identify a variety of functionalities or types of systems that utilize various combinations of specific ML algorithms. As used herein, AI / ML engine is intended to denote a variety of AI / ML functionalities that fall under the category of Al or ML algorithms and systems that utilize such functionalities. Examples of the AI / ML engine can comprise any one or more of e.g.: supervised learning, reinforcement learning, natural language processing such as LLMs, neural networks, computer vision, facial recognition, chatbots, virtual assistants, unsupervised learning, generative Al, other Al or ML models, and / or combinations of any of the foregoing.

[0099] The architecture of the AI / ML engine (e.g., structure, number of layers, nodes per layer, activation function etc.) may need to be tailored for each particular use case. Lor example, properties to vary can include e.g.: knowledge about the history of previous paths travelled by a plurality of UEs, terrestrial infrastructure knowledge, and a variety of other factors. These may all need to be considered when designing the AI / ML engine architecture.[000100] Building the AI / ML engine can include several development steps where the actual training of a ML model or algorithm is just one step in a training pipeline. An important part in AI / ML development is AI / ML model lifecycle management. One embodiment of a model lifecycle management procedure 2700 is illustrated in Eigure 14. The model lifecycle management can in some embodiments comprise two pipelines: a training pipeline 2705 and an inference pipeline 2750.[000101] At 2710 in the training pipeline 2705, data ingestion 2710 occurs, which includes gathering raw (training) data from a data storage. After data ingestion 2710, there may also be a step that controls the validity of the gathered data. At 2715 data pre-processing occurs, which can include feature engineering applied to the gathered data. This may involve, e.g., data normalization or data formatting or transformation required for the input data to the AI / ML model.Pl 12426After the ML model’s architecture is fixed, it should be trained on one or more datasets. At 2720 model training is performed in which the AI / ML model is trained with the raw training data. To achieve good performance during live operation in a system (the so-called inference phase), the training datasets should be representative of actual data the ML model will encounter during live operation. The training process often involves numerically tuning the ML model’s trainable parameters (e.g., the weights and biases of the underlying neural network (NN)) to minimize a loss function on the training datasets. The loss function may be, for example, based on data about the history of previous paths travelled by a plurality of UEs, terrestrial infrastructure knowledge, or other data. The purpose of the loss function is to meaningfully quantify the reconstruction error for the particular use case at hand. At 2725 model evaluation can be performed where the performance is benchmarked to some baseline. Model training 2720 and evaluation 2725 can be iterated until an acceptable level of performance is achieved. At 2730 model registration occurs, in which the AI / ML model is registered with any corresponding data on how the AI / ML model was developed, and e.g., AI / ML model evaluation data. At 2735 model deployment occurs, wherein the trained / re-trained AI / ML model is implemented in the inference pipeline 2750.[000102] Data ingestion 2755 in the inference pipeline 2750 refers to gathering raw (inference) data from a data source. Data pre-processing 2760 can be essentially identical / similar to the data pre-processing 2715 of the training pipeline 2705. At 2765, the operational model received from the training pipeline 2705 is used to process new data received during operation of e.g., method 700 of Fig. 7 or components thereof. At 2770 data and model monitoring is performed. Here the inference data is analyzed to determine whether the inference data are from a distribution that aligns with the training data, as well as monitoring model outputs for detecting any performance, or operational, variance or drifts. The variance or drift is used at 2745 (drift detection) to update the AI / ML model registration.[000103] The training process is typically based on some variant of a gradient descent algorithm, which, at its core, typically comprises three components: a feedforward step, a back propagation step, and a parameter optimization step. These steps can be described using a dense ML model (i.e., a dense NN with a bottleneck layer) as an example.[000104] Feedforward: A batch of training data, such as a mini-batch, (e.g., several downlink-channel estimates) is pushed through the ML model, from the input to the output. ThePl 12426loss function is used to compute the reconstruction loss for all training samples in the batch. The reconstruction loss may be an average reconstruction loss for all training samples in the batch.[000105] Back propagation (BP): The gradients (partial derivatives of the loss function, L, with respect to each trainable parameter in the ML model) are computed. The back propagation algorithm sequentially works backwards from the ML model output, layer-by-layer, back through the ML model to the input. The back propagation algorithm is built around the chain rule for differentiation: When computing the gradients for layer n in the ML model, it uses the gradients for layer n + 1.[000106] Parameter optimization: The gradients computed in the back propagation step are used to update the ML model’s trainable parameters. An approach is to use the gradient descent method with a learning rate hyperparameter (a) that scales the gradients of the weights and biases. It is preferred to make small adjustments to each parameter with the aim of reducing the average loss over the (mini) batch. It is common to use special optimizers to update the ML model’s trainable parameters using gradient information. The following optimizers are widely used to reduce training time and improving overall performance: adaptive sub-gradient methods (AdaGrad), RMSProp, and adaptive moment estimation (ADAM).[000107] The above process (feedforward, back propagation, parameter optimization) can be repeated many times until an acceptable level of performance is achieved on the training dataset. An acceptable level of performance may refer to the ML model achieving a pre-defined average reconstruction error over the training dataset (e.g., normalized MSE of the reconstruction error over the training dataset is less than, say, 0.1). Alternatively, it may refer to the ML model achieving a pre-defined value chosen by a user.[000108] In some implementations, a function F(-) may be generated by a ML process, such as, for example, supervised learning, reinforcement learning, and / or unsupervised learning. It should further be understood that supervised learning may be done in various ways, such as, for example, using random forests, support vector machines, neural networks, and the like. By way of non-limiting example, any of the following types of neural networks that may be utilized, including, deep neural networks (DNNs), convolutional neural networks (CNNs), and recurrent neural networks (RNNs), or any other known or future neural network that satisfies the needs of the system. In an implementation using supervised learning the neural networks may bePl 12426easily integrated into the hardware described in communication system 3100 of Fig. 16 (e.g., in the form of simple vector-matrix multiplications).[000109] Referring now to Fig. 15, an example NN 2900 (e.g., DNN) is shown. In some implementations, and as shown, the neural network 2900 may include two hidden layers represented by dashed boxes 2901 and 2902. In one implementation, the inputs 2903 may be fed into the NN 2900. Next, the inputs 2403 may go through a set of hidden layers (e.g., 2901 and / or 2902). Once the inputs 2903 pass though the hidden layers 2901 and / or 2902, they may be output (e.g., as an output layer) as outputs 2904, 2905. Outputs 2904, 2905 could be, e.g., a movement prediction of a UE or another output valuable. Possible inputs can include e.g.: knowledge of the history of the previous path travelled by the UE, GPS data, computed velocity, computed trajectory, terrestrial infrastructure knowledge, intended destination of the UE, or other variables.[000110] As should be understood by one of ordinary skill in the art, in order for the NN 2900 to output proper a proper analysis, it should be trained properly (e.g., with a collection of samples) to accurately extract the likelihood values. If not trained properly, overfitting (e.g., when the NN memorizes the structure of the preambles but is unable to generalize to unseen preamble characteristics) or underfitting (e.g., when the NN is unable to learn a proper function even on the data that it was trained on) may happen. Thus, implementations may exist that prevent overfitting or underfitting, involving a set of well-engineered features that must be extracted from the preamble characteristics.Additional Embodiments[000111] Fig. 16 shows an example of a communication system 3100 in accordance with some embodiments. In the example, the communication system 3100 includes a telecommunications network 3102 that includes an access network 3104, such as a radio access network (RAN), and a core network 3106, which includes one or more core network nodes 3108. The access network 3104 includes one or more access network nodes or base stations of various types, access network nodes 3110A and 3110B are depicted (which may be collectively referred to as network nodes 3110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 3104 may include more than one access network technology. The network nodes 3110 of access networkPl 124263104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 3112A, 3112B, 3112C, and 3112D (one or more of which may be generally referred to as UEs 3112) to the core network 3106 over one or more wireless connections.[000112] Moreover, a network node is 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 network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 3102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 3102 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 3102, including one or more access network nodes 3110 and / or core network nodes 3108.[000113] 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 control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN 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. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (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 O-2 interface defined by the O-RAN Alliance or comparable technologies.[000114] The network nodes 3110 facilitate direct or indirect connection of one or more UEs 3112 to the core network 3106 over one or more wireless connections. Example wirelessPl 12426communications 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 3100 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 3100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.[000115] The UEs 3112 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 3110 and other communication devices. Similarly, the network nodes 3108, 3110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 3102) with the UEs 3112 and / or with other network nodes or equipment in the telecommunications network 3102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 3102. More specifically, UEs 3112 may send messages, data, and / or other signals to network nodes 3108, 3110 or other elements of the telecommunications network 3102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 3108, 3110 may send messages, data, and other signals to UEs 3112, other network nodes 3108, 3110, and other devices in telecommunications network 3102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 3112 by transmitting the message to an access network node 3110 that will then transmit the message to the intended UE 3112. Similarly, a core network node 3108 may receive a particular message from a UE 3112 by receiving the message from an access network node 3110 that itself received the message from the UE 3112.Pl 12426[000116] In the depicted example, the core network 3106 connects elements of the access network 3104 (e.g., one or more of the network nodes 3110) to one or more host computing systems, such as host 3116. 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 3106 includes one or more core network nodes (e.g., core network node 3108) of various types, one or more of which may be generally referred to as network nodes 3108. Network nodes 3108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).[000117] The host 3116 may be under the ownership or control of a service provider other than an operator or provider of the access network 3104 and / or the telecommunications network 3102. The host 3116 may be operated by the service provider or on behalf of the service provider. The host 3116 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.[000118] As a whole, the communication system 3100 of Figure 16 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 3100 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);Pl 12426wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 3100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 3100 supporting different standards, protocols, or rule sets.[000119] As one example, in certain embodiments, access network 3104 may contain some access network nodes 3110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 3110 support (or the same access network nodes 3110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 3102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.[000120] Telecommunications network 3102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 3102. For example, the telecommunications network 3102 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.[000121] In some examples, one or more of the UEs 3112 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 3104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3104. 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)Pl 12426and 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).[000122] In the example, the hub 3114 communicates with the access network 3104 to facilitate indirect communication between one or more UEs (e.g., UE 3112C and / or 3112D) and network nodes (e.g., network node 3 HOB). In some examples, the hub 3114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 3114 may be a broadband router enabling access to the core network 3106 for the UEs. As another example, the hub 3114 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 3110, or by executable code, script, process, or other instructions in the hub 3114.[000123] As another example, the hub 3114 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 3114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 3114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 3114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 3114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.[000124] The hub 3114 may have a constant / persistent or intermittent connection to the network node 3110B. The hub 3114 may also allow for a different communication scheme and / or schedule between the hub 3114 and UEs (e.g., UE 3112C and / or 3112D), and between the hub 3114 and the core network 3106. In other examples, the hub 3114 is connected to the core network 3106 and / or one or more UEs via a wired connection. Moreover, the hub 3114 may be configured to connect to an M2M service provider over the access network 3104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 3110 while still connected via the hub 3114 via a wired or wireless connection. In some embodiments, the hub 3114 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 3 HOB. In otherPl 12426embodiments, the hub 3114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 3 HOB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.[000125] Fig. 17 is another example of a communication system 3200 according to some embodiments. As used herein, the communication system 3200 includes multiple access points (APs) 3210 (with four exemplary APs 3210A, 3210B, 3210C, and 3210D being depicted) and multiple wireless devices, referred to in the context of communication system 3200 as stations (STAs) 3212 (referred to individually as STA 3212A, STA 3212B, STA 3212C, STA 3212D, and STA 3212E). STA 3212A is served by AP 3210A in a first basic service set (BSS) 3220A. STA 3210B and STA 3210C are served by AP 3210B in a second BSS, BSS 3220B. STA 3212D is served by AP 3210C in a third BSS, BSS 3220C. STA 3212E is served by AP 3210D in a fourth BSS, BSS 3220D. Stations 3212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, headmounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 3212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.[000126] Each of STAs 3212 may connect through a radio link to one of APs 3210. For example, depending on location or channel conditions experienced by a given STA 3212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.[000127] Each AP 3210 may provide data connectivity to STAs 3212 connected to a particular AP 3210. As illustrated, APs 3210 may be connected to a data network 3230. In this way, APs 3210 may also provide data connectivity between STAs 3212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 3212 and its serving AP 3210 mayPl 12426be used for providing various kinds of services to STA 3212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 3212 and / or on a device linked to STA 3212. By way of example, Fig. 17 illustrates an application service platform 3232 provided in data network 3230. The application(s) executed on STA 3212 and / or on one or more other devices linked to STA 3212 may use the radio link for data communication with one or more other STA 3212 and / or the application service platform 3232, thereby enabling utilization of the corresponding service(s) at STA 3212.[000128] Fig. 18 shows a wireless device 3300, which may be configured to operate in communication system 3100 of Fig. 16 or in communication system 3200 of Fig. 3200. The wireless device 3300 may be alternatively referred to as a UE 3300, like a UE 3112 within the context of communication system 3100, or as a station (STA) 3300 or as a non-access-point station (non-AP STA) 3300, like a STA 3212 within the context of the communication system 3200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of 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.[000129] A wireless device 3300 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, wireless device 3300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 3300 may represent a device that is intended for sale to, orPl 12426operation 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, wireless device 3300 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).[000130] In particular embodiments, wireless device 3300 includes processing circuitry 3302 that is operatively coupled via a bus 3304 to an input / output interface 3306, a power source 3308, a memory 3310, a communication interface 3312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 3300 may include all or a subset of the components shown in Fig. 18. The level of integration between the components may vary from one embodiment of wireless device 3300 to another. In general, in a particular embodiment of wireless device 3300, processing circuitry 3302, input / output interface 3306, power source 3308, memory 3310, and communication interface 3312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 3300. Further, certain embodiments of wireless devices 3300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.[000131] The processing circuitry 3302 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 3310. The processing circuitry 3302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 3302 may include multiple central processing units (CPUs).[000132] In the example, the input / output interface 3306 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 wireless devicePl 124263300. 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.[000133] In some embodiments, the power source 3308 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 to supply power to circuitry or to charge an associated battery. The power source 3308 may further include power circuitry for delivering power from the power source 3308 itself, and / or an external power source, to the various parts of wireless device 3300 via input circuitry or an interface such as an electrical power cable. Power source 3308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 3300 to which power is supplied.[000134] The memory 3310 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 read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 3310 includes one or more programs 3314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 3316. The memory 3310 may store, for use by wireless device 3300, any of a variety of various operating systems or combinations of operating systems.[000135] The memory 3310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digitalPl 12426data 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 IS IM, 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 3310 may allow wireless device 3300 to access instructions, 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 3310, which may be or comprise a device-readable storage medium.[000136] The processing circuitry 3302 may be configured to communicate with an access network or other network via or using the communication interface 3312. The communication interface 3312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 3322. The communication interface 3312 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 3318 and / or a receiver 3320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 3318 and receiver 3320 may be coupled to one or more antennas (e.g., antenna 3322) and may share circuit components, software or firmware, or alternatively be implemented separately.[000137] In the illustrated embodiment, communication functions of the communication interface 3312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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 RadioPl 12426(NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.[000138] In particular embodiments, wireless device 3300 may provide an output of data captured via a sensor, through its communication interface 3312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 3300 can be communicated through a wireless connection to a network node via another wireless device 3300. In particular embodiments, such 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).[000139] As another example, wireless device 3300 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, wireless device 3300 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.[000140] Wireless device 3300, 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, wearable technology, extended industrial application and healthcare. Nonlimiting 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 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 anyPl 12426kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 3300 represents an loT device that 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 example embodiment of wireless device 3300 shown in Fig. 18.[000141] As yet another specific example, in an loT scenario, wireless device 3300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 3300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 3300 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 3300 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.[000142] In practice, any number of wireless devices 3300 may be used together with respect to a single use case. For example, a first wireless device 3300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 3300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 3300 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 wireless device 3300 can also include more than one of the functionalities described above. For example, wireless device 3300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.[000143] Fig. 19 shows a network node 3400 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 telecommunications network. In accordance with respective embodiments, network node 3400 may be configured to operate in communication system 3100 of Fig. 16, like network nodes 3108 or 3110, or in communication system 3200 of Fig. 17, like an AP 3210 or a station 3212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points),Pl 12426base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).[000144] Network nodes 3400 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. Network node 3400 may be a relay node or a relay donor node controlling a relay. Network nodes 3400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) 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).[000145] Other examples of network nodes 3400 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).[000146] In particular embodiments, network node 3400 includes a processing circuitry 3402, a memory 3404, a communication interface 3406, and a power source 3408. In general, in a particular embodiment of network node 3400, processing circuitry 3402, memory 3404, communication interface 3406, and power source 3408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 3400.[000147] The network node 3400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 3400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC mayPl 12426control 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 3400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 3404 or portions of memory 3404 for different RATs) and some components may be reused (e.g., a same antenna 3410 may be shared by different RATs). The network node 3400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 3400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 3400.[000148] The processing circuitry 3402 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 components, such as the memory 3404, to provide network node 3400 functionality.[000149] In some embodiments, the processing circuitry 3402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3402 includes one or more of radio frequency (RF) transceiver circuitry 3412 and baseband processing circuitry 3414. In some embodiments, the RF transceiver circuitry 3412 and the baseband processing circuitry 3414 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 3412 and baseband processing circuitry 3414 may be on the same chip or set of chips, boards, or units.[000150] The memory 3404 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), readonly memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memoryPl 12426devices that store information, data, and / or instructions that may be used by the processing circuitry 3402. The memory 3404 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 3402 and utilized by the network node 3400. The memory 3404 may be used to store any calculations made by the processing circuitry 3402 and / or any data received via the communication interface 3406. In some embodiments, the processing circuitry 3402 and memory 3404 is integrated.[000151] The communication interface 3406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 3406 comprises port(s) / terminal(s) 3416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 3300 may be capable of wireless communication and communication interface 3406 may also include radio front-end circuitry 3418 that may be coupled to, or in certain embodiments a part of, an antenna 3410. Particular embodiments of radio front-end circuitry 3418 include filter(s) 3420 and amplifier(s) 3422. The radio front-end circuitry 3418 may be connected to an antenna 3410 and processing circuitry 3402. The radio front-end circuitry may be configured to condition signals communicated between antenna 3410 and processing circuitry 3402. The radio front-end circuitry 3418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 3418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 3420 and / or amplifiers 3422. The radio signal(s) may then be transmitted via the antenna 3410. Similarly, when receiving data, the antenna 3410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3418. The digital data may be passed to the processing circuitry 3402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.[000152] In certain alternative embodiments, network node 3400 may be capable of wireless communication but does not include separate radio front-end circuitry 3418, instead, the processing circuitry 3402 includes radio front-end circuitry and is connected to the antenna 3410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3412 is part of thePl 12426communication interface 3406. In still other embodiments, the communication interface 3406 includes one or more ports or terminals 3416, the radio front-end circuitry 3418, and the RF transceiver circuitry 3412, as part of a radio unit (not shown), and the communication interface 3406 communicates with the baseband processing circuitry 3414, which is part of a digital unit (not shown).[000153] The antenna 3410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3410 may be coupled to the radio front-end circuitry 3418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 3410 is separate from the network node 3400 and connectable to the network node 3400 through one or more interfaces or ports.[000154] The antenna 3410, communication interface 3406, and / or the processing circuitry 3402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 3400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 3410, the communication interface 3406, and / or the processing circuitry 3402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 3400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.[000155] The power source 3408 provides power to the various components of network node 3400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3400 with power for performing the functionality described herein. For example, the network node 3400 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 3408. As a further example, the power source 3408 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.Pl 12426[000156] Embodiments of the network node 3400 may include additional components beyond those shown in Fig. 19 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 3400 may include user interface equipment to allow input of information into the network node 3400 and to allow output of information from the network node 3400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3400.[000157] Fig. 20 is a block diagram illustrating a virtualization environment 3500 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 3500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a 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 3500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.[000158] Applications 3502 (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.[000159] Hardware 3504 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 3506 (alsoPl 12426referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 3508A and VM 3508B (which may be collectively referred to as VMs 3508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 3506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 3508.[000160] The VMs 3508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 3506. Different embodiments of the instance of a virtual appliance 3502 may be implemented on one or more of VMs 3508, 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.[000161] In the context of NFV, each of the VMs 3508 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 3508, and that part of hardware 3504 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 of the VMs 3508 on top of the hardware 3504 and corresponds to an application 3502.[000162] Hardware 3504 may be implemented in a standalone network node with generic or specific components. Hardware 3504 may implement some functions via virtualization. Alternatively, hardware 3504 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 3510, which, among others, oversees lifecycle management of applications 3502. In some embodiments, hardware 3504 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, somePl 12426signaling can be provided with the use of a control system 3512 which may alternatively be used for communication between hardware nodes and radio units.[000163] 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.[000164] 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 thePl 12426processing 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.[000165] 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.[000166] 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 thePl 12426processing 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.[000167] It will be appreciated that computer systems are increasingly taking a wide variety of forms. In this description and in the claims, the terms “controller,” “computer system,” or “computing system” are defined broadly as including any device or system — or combination thereof — that includes at least one physical and tangible processor and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor. By way of example, not limitation, the term “computer system” or “computing system,” as used herein is intended to include personal computers, desktop computers, laptop computers, tablets, hand-held devices (e.g., mobile telephones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multi-processor systems, network PCs, distributed computing systems, datacenters, message processors, routers, switches, and even devices that conventionally have not been considered a computing system, such as wearables (e.g., glasses).[000168] The computing system also has thereon multiple structures often referred to as an “executable component.” For instance, the memory of a computing system can include an executable component. The term “executable component” is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods, and so forth, that may be executed by one or more processors on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media. The structure of the executable component exists on a computer-readable medium in such a form that it is operable, when executed by one or more processors of the computing system, to cause the computing system to perform one or more functions, such as the functions and methods described herein. Such a structure may be computer-readable directly by a processor — as is the case if the executable component were binary. Alternatively, the structure may be structured to be interpretable and / or compiled — whether in a single stage or in multiple stages — so as to generate such binary that is directly interpretable by a processor.Pl 12426[000169] The terms “component,” “service,” “engine,” “module,” “control,” “generator,” or the like may also be used in this description. As used in this description and in this case, these terms — whether expressed with or without a modifying clause — are also intended to be synonymous with the term “executable component” and thus also have a structure that is well understood by those of ordinary skill in the art of computing.[000170] In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, the term “processor” or “controller” also refers to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.[000171] In general, the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as nonlimiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.[000172] While not all computing systems require a user interface, in some embodiments a computing system includes a user interface for use in communicating information from / to a user. The user interface may include output mechanisms as well as input mechanisms. The principles described herein are not limited to the precise output mechanisms or input mechanisms as such will depend on the nature of the device. However, output mechanisms might include, for instance, speakers, displays, tactile output, projections, holograms, and so forth. Examples of input mechanisms might include, for instance, microphones, touchscreens,Pl 12426projections, holograms, cameras, keyboards, stylus, mouse, or other pointer input, sensors of any type, and so forth.Abbreviations and Defined Terms[000173] To assist in understanding the scope and content of this written description and the appended claims, a select few terms are defined directly below. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure pertains.[000174] The terms “approximately,” “about,” and “substantially,” as used herein, represent an amount or condition close to the specific stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a specifically stated amount or condition.[000175] Various aspects of the present disclosure, including devices, systems, and methods may be illustrated with reference to one or more embodiments or implementations, which are exemplary in nature. As used herein, the term “exemplary” means “serving as an example, instance, or illustration,” and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein. In addition, reference to an “implementation” of the present disclosure or embodiments includes a specific reference to one or more embodiments thereof, and vice versa, and is intended to provide illustrative examples without limiting the scope of the present disclosure, which is indicated by the appended claims rather than by the present description.[000176] As used in the specification, a word appearing in the singular encompasses its plural counterpart, and a word appearing in the plural encompasses its singular counterpart, unless implicitly or explicitly understood or stated otherwise. Thus, it will be noted that, as used in this specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. For example, reference to a singular referent (e.g., “a widget”) includes one, two, or more referents unless implicitly or explicitly understood or stated otherwise. Similarly, reference to a plurality of referents should be interpreted as comprisingPl 12426a single referent and / or a plurality of referents unless the content and / or context clearly dictate otherwise. For example, reference to referents in the plural form (e.g., “widgets”) does not necessarily require a plurality of such referents. Instead, it will be appreciated that independent of the inferred number of referents, one or more referents are contemplated herein unless stated otherwise.[000177] References in the specification to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.[000178] It shall be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.[000179] It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.Conclusion[000180] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunctionPl 12426with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.[000181] It is understood that for any given component or embodiment described herein, any of the possible candidates or alternatives listed for that component may generally be used individually or in combination with one another, unless implicitly or explicitly understood or stated otherwise. Additionally, it will be understood that any list of such candidates or alternatives is merely illustrative, not limiting, unless implicitly or explicitly understood or stated otherwise.[000182] In addition, unless otherwise indicated, numbers expressing quantities, constituents, distances, or other measurements used in the specification and claims are to be understood as being modified by the term “about,” as that term is defined herein. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the subject matter presented herein. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the subject matter presented herein are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical values, however, inherently contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.[000183] Any headings and subheadings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. The terms and expressions which have been employed herein are used as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding any equivalents of the features shown and described or portions thereof, but it is recognized that various modifications are possible within the scope of the present disclosure. Thus, it should be understood that although the present disclosure has been specifically disclosed in part by certain embodiments, and optional features, modification and variation of the concepts herein disclosed may be resorted to by those skilled in the art, and such modifications and variations are considered to be within the scope of this present description.Pl 12426[000184] It will also be appreciated that systems, devices, products, kits, methods, and / or processes, according to certain embodiments of the present disclosure may include, incorporate, or otherwise comprise properties or features (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Accordingly, the various features of certain embodiments can be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Thus, disclosure of certain features relative to a specific embodiment of the present disclosure should not be construed as limiting application or inclusion of said features to the specific embodiment. Rather, it will be appreciated that other embodiments can also include said features, members, elements, parts, and / or portions without necessarily departing from the scope of the present disclosure.[000185] Moreover, unless a feature is described as requiring another feature in combination therewith, any feature herein may be combined with any other feature of a same or different embodiment disclosed herein. Furthermore, various well-known aspects of illustrative systems, methods, apparatus, and the like are not described herein in particular detail in order to avoid obscuring aspects of the example embodiments. Such aspects are, however, also contemplated herein.[000186] It will be apparent to one of ordinary skill in the art that methods, devices, device elements, materials, procedures, and techniques other than those specifically described herein can be applied to the practice of the described embodiments as broadly disclosed herein without resort to undue experimentation. All art-known functional equivalents of methods, devices, device elements, materials, procedures, and techniques specifically described herein are intended to be encompassed by this present disclosure.[000187] When a group of materials, compositions, components, or compounds is disclosed herein, it is understood that all individual members of those groups and all subgroups thereof are disclosed separately. When a Markush group or other grouping is used herein, all individual members of the group and all combinations and sub-combinations possible of the group are intended to be individually included in the disclosure.[000188] The above-described embodiments are examples only. Alterations, modifications, and variations may be effected to the particular embodiments by those of skill inPl 12426the art without departing from the scope of the description, which is defined solely by the appended claims.

Claims

Pl 12426CLAIMSWhat is claimed is:

1. A method (600) performed by a network (3102) for reprovisioning a network slice or a network slice subnet configured on a first portion of the network, the method comprising:detecting (602) a movement of a UE connected to the network;generating (604) a movement prediction of the UE;allocating (606), based on at least one of the movement and the movement prediction, the network slice or the network slice subnet on a second portion of the network, wherein the second portion was not configured with the network slice or the network slice subnet before the allocation; anddeallocating (606), based on at least one of the movement and the movement prediction, the network slice or the network slice subnet on a third portion of the network, wherein the first portion comprises the third portion.

2. The method of claim 1 , wherein the movement is from a first tracking area to a second tracking area, wherein the network comprises the first tracking area and the second tracking area.

3. The method of claim 1, wherein the movement prediction is from a current tracking area to a future tracking area, wherein the network comprises the current tracking area and the future tracking area, and wherein the UE is associated with the current tracking area and not associated with the future tracking area.Pl 124264. A method (700) for reprovisioning a network slice or a network slice subnet configured on a network, the method comprising:receiving (702) a configuration of the network slice or the network slice subnet comprising dynamic network slice parameters, the configuration comprising at least one UE to be supported by the network slice or the network slice subnet;receiving (704) a registration area associated with the at least one UE, wherein the network comprises the registration area;receiving (706) a movement prediction of the at least one UE;identifying (708), based on at least one of the registration area and the movement prediction, at least one component of the network to be reprovisioned; andsending (710), to the at least one component, reprovisioning instructions based on the configuration, wherein the reprovisioning instructions either allocate or deallocate the network slice or the network slice subnet on the at least one component.

5. The method of claim 4, wherein the configuration further comprises data associated with the at least one UE that will be supported by the network slice or the network slice subnet.

6. The method of claims 4 or 5, wherein the at least one component is associated with one or more target tracking areas of the network, and wherein the at least one UE is not associated with at least one of the target tracking areas.

7. The method of claim 6, wherein the at least one component is part of the RAN of the network, the RAN comprises the one or more target tracking areas, and the reprovisioning instructions are sent to the NSSMF of the RAN.Pl 124268. The method of claim 7, wherein the at least one component comprises a cell of the network.

9. The method of claim 6, wherein the at least one component is part of the core network of the network and the reprovisioning instructions are sent to at least the NSSMF of the core network.

10. The method of claim 9, wherein the at least one component is at least one of:an AMF, an SMF, a UPF, and an MME.

11. A method (800) for reprovisioning a network slice or a network slice subnet configured on a network, the method comprising:detecting (802) a movement of a UE connected to the network from a first tracking area to a second tracking area, wherein the network comprises the first tracking area and the second tracking area, and wherein each of the first tracking area and the second tracking area are associated with a registration area of the network; andsending (804), to a controller, the registration area associated with the second tracking area if the registration area associated with the second tracking area is different than the registration area associated with the first tracking area.

12. The method of claim 11, wherein the movement is detected based on at least one of a tracking area update message and a registration area update message.Pl 1242613. The method of claims 11 or 12, further comprising updating a counter based on the detected movement.

14. The method of claim 13, wherein the counter is one of:a RAN counter;a UE counter; anda core network counter.

15. A method (1000) for reprovisioning a network slice or a network slice subnet configured on a network, the method comprising:generating (1002) a movement prediction of a UE connected to the network from a current tracking area to a future tracking area, wherein the network comprises the current tracking area and the future tracking area, and wherein the UE is associated with the current tracking area and not associated with the future tracking area; andsending (1004), to a controller, the movement prediction.

16. The method of claim 15, wherein the movement prediction is based on one or more of:knowledge of the history of a previous path travelled by the UE;GPS data;computed velocity;Pl 12426computed trajectory;terrestrial infrastructure knowledge; andintended destination of the UE.

17. The method of claims 15 or 16, further comprising:sending (1006), to the controller, information based on a capacity of the future tracking area.

18. The method of any of claims 15-17, wherein the movement prediction is generated with an AI / ML engine.

19. The method of 18, wherein the AI / ML engine is trained using a dataset comprising:knowledge of the history of previous paths travelled by a plurality of UEs; andterrestrial infrastructure knowledge.

20. A system for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of claims 1 to 3.

21. A apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructionsPl 12426executable by the processing circuitry whereby the system is operative to perform any of claims 4 to 10.

22. A apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of claims 11 to 14.

23. A apparatus for reprovisioning a network slice or a network slice subnet configured on a network comprising processing circuitry and a memory, the memory containing instructions executable by the processing circuitry whereby the system is operative to perform any of claims 15 to 19.

24. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 19.

25. A computer program product, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 19.

Images