Method for slice remapping in subsequent cell change and related device

Abstract

The present application relates to methods and related devices for slice remapping in subsequent cell change. Methods and related devices for providing slice remapping based on a trajectory of a mobile device within a mobile telecommunication network are disclosed.

Description

Technical Field

[0001] This disclosure relates to the field of mobile telecommunications networks. Background Technology

[0002] This section introduces aspects that can help facilitate a better understanding of this disclosure. Therefore, the statements in this section should be read in this light and should not be construed as an admission of what is prior art or what is not prior art.

[0003] Network slicing is a key feature of telecommunications networks that use the same or similar underlying hardware and software infrastructure to support different services. In addition, network slices can differ based on: (1) their service requirements, for example, one slice may provide ultra-reliable low-latency communication (URLLC) services while another slice may provide enhanced mobile broadband (eMBB) services, or (2) the “tenants” (i.e., entities or organizations that utilize a particular network slice or segment of the telecommunications infrastructure) that provide such services.

[0004] A network slice (or "slice") is uniquely identified by a Single Network Slice Selection Auxiliary Information (S-NSSAI) in a fifth-generation (5G) network. In next-generation networks (e.g., sixth-generation (6G)), the same identifier, similar identifiers, or different identifiers may be used. The current 3GPP 5G specification allows a user equipment (UE) to connect to and be served by eight network slices simultaneously (i.e., associated with eight S-NSSAIs).

[0005] Furthermore, each physical telecommunications cell in a mobile network (e.g., an associated 5G or 6G access node, sometimes simply referred to as an "access node" or "network access node") can support dozens or even hundreds of slices. For example, in the current 5G specification, a tracking area (TA) consisting of logical packets of one or more cells served by an access node can support up to 1024 network slices, and can be further extended to support more slices with additional slice support information.

[0006] The S-NSSAI can include both a Slice Service Type (SST) field and a Slice Distinguisor (SD) field, and has a total length of 32 bits. Alternatively, the S-NSSAI can include only the SST field, in which case the S-NSSAI is 8 bits long and can represent 256 discrete values. The SST field can include so-called normalized and non-normalized values. For example, values ​​0 to 127 are considered to be within the normalized SST range, where a value of 1 can indicate that the slice is suitable for handover to eMBB, and a value of 2 can indicate that the slice is suitable for handover to URLLC, and so on. Non-normalized values ​​can be assigned based on a specific mobile network operator configuration; that is, non-normalized values ​​can be operator-defined.

[0007] In contrast, the value of the SD field is also defined by the operator.

[0008] So-called “adjacent” NG radio access network (RAN) nodes within the same TA can exchange messages, including slice support information, via the so-called “Xn interface”, using Xn establishment (e.g., when two access nodes first establish a connection) and NG-RAN node configuration update procedures (e.g., for updating the configuration of RAN nodes).

[0009] More specifically, during the Xn interface and NG-RAN node configuration update process, slice information (including S-NSSAI) is shared among access nodes to ensure, for example, that each neighboring access node knows the slice configuration supported (or being updated) by each other access node. This allows neighboring access nodes to coordinate, for example, mobility, handover, and load balancing, while preserving slice-specific requirements (such as service level agreements (SLAs) that may include QoS and latency).

[0010] Related to the TA is the "Registration Area" (RA). The RA is a list of TAs that support the same slice from the UE's perspective. When a UE registers with the core telecommunications network (referred to as the "core network"), the UE can send a registration message to the core network (CN) indicating the slices it may need to access and the corresponding S-NSSAI. Typically, elements in the core network (e.g., elements capable of performing 5G Access and Mobility Management Functions (AMF)) are configured to respond to the registration message by analyzing (i.e., comparing) the requesting UE's profile and the UE's corresponding subscription data to verify that the UE is entitled to access the complete list of slices it is requesting, and that the slice list is indeed supported by the TA (hereinafter referred to as the "current TA") indicated by the registration message. Subsequently, the responsible element within the core network sends a response message to the UE, which contains a second list (including the identifier of the "Allowed Slice") and the corresponding Allowed NSSAI (which is the list of allowed S-NSSAIs). Therefore, the allowed slice list may differ from the requested slice list because, for example (1) the requested slice may be unavailable due to resource constraints, or (2) the requested slice may not be supported by the current TA that received the registration message from the UE.

[0011] Nevertheless, assuming the allowed slice list contains at least one slice, one or more elements of the core network can then configure a Registered Area (RA) for the requesting UE. The configured RA contains one or more Transports (TAs) supporting all allowed slices for the UE. Furthermore, slice support information for each TA is exchanged between the access node and the core network (i.e., via NGAP procedures), such as the NG establishment procedure and the RAN configuration update procedure, where the NG is the interface between the access node and the core network. Based on this information, the core network can configure a list of at least one TA for the requesting UE, where slice support is homogeneous for the requesting UE (i.e., allowed slices supporting the UE are in the configured RA). Once the UE leaves a TA in the RA, it needs to perform a Registered Area Update, during which the core network re-evaluates the slices requested by the UE to configure a new RA (or reconfigure a previous RA) if necessary.

[0012] It should be noted that the core network typically identifies and stores the locations of idle UEs (i.e., those UEs that are not actively sending or receiving data) that have previously completed the registration process (i.e., Registration Management (RM) - Registered status).

[0013] In idle mode, the UE typically remains in low-power idle mode until it is triggered, for example, until it is paged by the network.

[0014] Subsequently, the UE can receive network-originating service request messages from core network components (such as AMF components). Essentially simultaneously, the AMF also electronically sends one or more messages to access nodes that are members of the TAs within the RA. Typically, the AMF can apply different paging strategies. One paging strategy allows the AMF to send messages to a subset of the TAs within the RA. For example, the UE might complete the RA update process last with its TA. This minimizes the number of TAs and their corresponding access nodes involved in the message exchange.

[0015] Therefore, it can be said that there is a trade-off between the size of a given RA and the paging volume required to complete such paging, and the number (frequency) of RA updates that the UE must complete. In other words, typically for an RA containing many TAs, fewer RA updates may be needed, but the RA may require more paging (and corresponding paging-related signaling), while for an RA containing fewer TAs, there are typically more RA updates, but fewer paging-related signaling is required. Furthermore, a smaller RA can reach the UE faster. Such a UE may be preferred for certain services where latency limits or constraints are imposed for efficiency.

[0016] Therefore, a UE that is moving from one location to another and requires the support of a network slice associated with a large coverage area may be configured with an RA at its new location (or intermediate and / or final expected destination) that does not include all TAs of the previously supported slice, but only includes a limited set of TAs.

[0017] To enable data-driven operations and automated network management, the telecommunications industry (3GPP working group) has been exploring the integration of automation and data analytics into networks as key features (i.e., Network Data Analytics Function (NWDAF) and Management Data Analytics Service (MDAS)). These features can also be used for network slicing operations and optimization.

[0018] In addition, the industry has also explored artificial intelligence / machine learning (AI / ML). AI / ML processes (e.g., algorithms) can provide powerful tools to help telecom operators improve their network management and user experience by providing insights based on autonomous analysis and processing of collected data.

[0019] To date, the integration of AI / ML has focused on the current NG-RAN architecture and interfaces to enable AI support for 5G networks. The following information can be configured and is available for reporting by NG-RAN nodes: -Predicted resource status information; -UE performance feedback; -Measured UE trajectory; - Energy cost (EC).

[0020] The industry has explored various solutions to achieve service continuity for mobile UEs through a process called slice remapping (hereinafter referred to as "remapping").

[0021] Existing remapping processes involve statically allocating slices using Operations, Administration, and Maintenance (OAM) and Network Management System (NMS) features embedded in one or more elements of the core network for each access node (such as the AMF). However, in static allocation, slice allocation is not dynamically adjusted in real time to account for changing network conditions or user requirements.

[0022] Remapping can be performed between the AMF and the access nodes at a low granularity level (e.g., slice level), a high granularity level (e.g., Protocol Data Unit (PDU) level), or even a medium granularity level (e.g., at the UE level). More specifically, the granularity of the applied remapping strategy performed by the AMF and one or more access nodes (i.e., the degree to which remapping is controlled) can be as follows: Per slice (low granularity level): A node-specific establishment / update process is used between core network elements (which can be configured by OAM (e.g., AMF)) and access nodes, as illustrated by the following exchange of electronic messages / instructions: - S-NSSAI 1<> Remapping List (S-NSSAI 10, S-NSSAI 11) - S-NSSAI 2<> remapping list (S-NSSAI 12, S-NSSAI 13) For example, "S-NSSAI 1" is the first original slice, S-NSSAI 2 is the second original slice, and services (data) initially directed to the first original slice can be remapped to slice 10 or 11, while services (data) initially directed to the second original slice can be remapped to slice 12 or 13. Therefore, for example, if the slice associated with the first original slice S-NSSAI 1 becomes overloaded, services can be dynamically remapped to slice 10 or 11, as specified in the remap list above. This helps support load balancing and service continuity, ensuring that user services provided by access nodes continue during network congestion or slice outages.

[0023] Per UE (Medium granularity): For a given slice, even with signaling for the PDU sessions involved, the selection of possible remapping slices is a general strategy for the UE, as illustrated by the following exchange of electronic messages / commands: UE 1, any PDU session <> remapping list for S-NSSAI 1 (S-NSSAI 10, S-NSSAI 11) UE 2, any PDU session <> remapping list for S-NSSAI 1 (S-NSSAI 12, S-NSSAI 13) Specifically, for the first UE (UE-1), any PDU session associated with the first original slice S-NSAI 1 can be remapped to a slice identified by slice S-NSAI 10 or S-NSAI 11, and for the second UE (UE-2), any PDU session associated with the first original slice S-NSAI 1 can be remapped to a slice identified by slice S-NSAI 12 or S-NSAI 13. In summary, traffic initially mapped to S-NSAI 1 for both the first and second UEs can be redirected to one or more slices in the remapping list. The exact slice used (e.g., S-NSAI 10 or 11 for UE 1) can be selected based on additional factors such as load balancing, QoS requirements, or network congestion.

[0024] Therefore, at the UE level, it can be said that the network (i.e., the core network components) applies a general strategy to determine which slices are available for remapping, regardless of the specific PDU session involved.

[0025] For example, even if a PDU session (e.g., a video streaming session) signals its requirements (e.g., bandwidth or latency), the slices that can be used for remapping can be determined based on an overall policy for the entire UE. Therefore, slice remapping is managed by UE-specific policies, rather than being dynamically customized for individual PDU sessions.

[0026] Therefore, by exchanging such messages (or “mappings”), the core network can determine how to dynamically remap services (data) for a UE to alternative slices based on current core network conditions, service requirements, or policies. This enables the core network to apply and implement per-UE slice remapping policies to deliver and support specific customized services to each UE.

[0027] Per PDU session (high-granularity level): Slices are associated using the same principles as those used during the PDU session establishment process, which can be illustrated by exchanging the following electronic messages / instructions: UE 1, PDU Session 1, S-NSSAI 1<> Remapping List (S-NSSAI 10, S-NSSAI 11) UE 1, PDU Session 2, S-NSSAI 1<> Remapping List (S-NSSAI 12, S-NSSAI 13) UE 2, PDU Session 3, S-NSSAI 1<> Remapping List (S-NSSAI 14, S-NSSAI 15) Wherein: (a) for the first UE-1, PDU session 1 associated with the first original slice S-NSAI 1 can be remapped to a slice in a list containing slices S-NSAI 10 and S-NSAI 11; (b) for the first UE-1, PDU session 2 associated with the first original slice S-NSAI 1 can be remapped to a slice in a list containing slices S-NSAI 12 and S-NSAI 13; and (c) for the second UE-2, PDU session 3 associated with the original slice S-NSAI 1 can be remapped to a slice in a list containing slices S-NSAI 14 and S-NSAI 15.

[0028] Therefore, at the PDU session level, the network element executes and applies the slice remapping procedure previously used during the initial PDU session establishment process. More specifically, typically when a PDU session is established, a logical connection is established between the UE and the network element to establish one or more data streams for a specific service or application. PDU sessions can be associated with slices based on factors such as QoS requirements, service type, and network policies, to name just a few.

[0029] The “per PDU session” process enables the network to make fine-tuning adjustments during each PDU session based on the specific requirements or characteristics of a given session.

[0030] In another example, the remapping configuration can be set by OAM.

[0031] While the slice remapping process just described can be used, the 5G telecom industry has not yet adopted a standardized slice remapping process for the RAN, although there have been recent discussions about adopting one or more of the aforementioned processes. Nevertheless, for example, due to network congestion, the 5G telecom industry has specified slice replacement for the core network.

[0032] When a UE moves from one location to another, remapping may be required. When a UE moves, it must “switch” electronically and communicationally from one mobile telecommunications cell area (hereinafter referred to as “cell”) to another cell in order to maintain active connectivity, continuity, or data sessions (e.g., when a UE is watching streaming video while moving from one cell to another).

[0033] 3GPP has released several proposals or concepts related to this type of UE movement. The proposal known as “Subsequent Cell Change” attempts to simplify continuous handover (HO) (introduced by 3GPP Release 18, hereinafter referred to as “Release 18”; ​​see Subsequent L1 / L2 Triggered Mobility (LTM) and Subsequent Conditional Primary / Secondary Cell Group (SCG) Cell Addition or Change (CPAC)).

[0034] Now for reference Figure 1A The diagram depicts a simplified illustration of UE 10 moving from the current or source cell 20a (hereinafter referred to as "source cell") and RA1 to the second or next cell 20b and RA2 and then to the final next cell 20n and RA3 (hereinafter collectively referred to as "n" where "n" represents the final or destination next cell).

[0035] As shown in Table 1 below, the supported slice list indicates that slice 1 is supported by cell 1 in RA1, slices 2 and 3 are supported by cell 2 in RA2 (slice 1 is not supported), and slices 3 and 4 are supported by cell 3 in RA3 (slices 1 and 2 are not supported). In this example, potential slice remapping options could be slice 1 <--> slice 2, slice 3 and slice 2 <--> slice 3, slice 4. Therefore, if a UE with an allowed S-NSSAI of slice 1 moves from cell 1 in Registration Area (RA) to cell RA2, and then to cell RA3 (see...),... Figure 1A In an example scenario, slice 1 can be remapped to slice 2 in cell RA2, and then slice 2 will be remapped to slice 3 in cell RA3. That is, multiple cascaded slice remappings can occur on the UE's trajectory, with corresponding additional signaling overhead. While existing research proposes remapping the current slice to another slice to ensure service / slice continuity for HO between two adjacent cells, the existing process does not address subsequent cell changes in a signaling-efficient manner.

[0036]

[0037] Table 1 Therefore, it is desirable to address and provide solutions to this remapping challenge. In particular, methods and related devices are provided to reduce or minimize signaling (e.g., non-access stratum (NAS) overhead) while also mitigating the risk of service disruption due to slice remapping. Summary of the Invention

[0038] This disclosure describes exemplary methods and related devices for reducing or minimizing signaling (e.g., NAS overhead) by taking into account the UE trajectory during slice remapping, while also reducing the risk of service interruption during slice remapping.

[0039] In one embodiment, an apparatus in a telecommunications network associated with at least one slice of a source cell includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: receive information identifying one or more permitted slices available to the apparatus during one or more anticipated handovers to one or more next cells, based at least on a anticipated trajectory of the apparatus, wherein the anticipated trajectory includes the one or more next cells; adjust at least one slice to at least one first permitted slice among the identified one or more permitted slices based on the anticipated trajectory; and complete a first handover to the first next cell among the one or more anticipated handovers to access telecommunications resources associated with the at least one first permitted slice.

[0040] In one embodiment, a system in a telecommunications network includes a first network device comprising: at least one first processor; and at least one first memory storing instructions that, when executed by the at least one first processor, cause the first network device to: send information identifying one or more permitted slices available to the UE during one or more anticipated handovers to one or more cells in the telecommunications network, based at least on an anticipated trajectory of a user equipment (UE) in the telecommunications network, wherein the anticipated trajectory includes one or more cells. The system also includes a second network device comprising: at least one second processor; and at least one second memory storing instructions that, when executed by the at least one second processor, cause the second network device to: receive a first handover indication in response to the satisfaction of a first handover condition for handing the UE to a first next cell, the first handover indication indicating that the UE will use at least one first permitted slice of the one or more permitted slices based on the UE's anticipated trajectory; and complete a first handover to the first next cell in the anticipated handover to allow the UE access telecommunications resources associated with the at least one first permitted slice.

[0041] In one embodiment, a network apparatus in a telecommunications network includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network apparatus to: send information identifying one or more permitted slices available to the first user equipment (UE) during one or more anticipated handovers to one or more cells in the telecommunications network, based at least on a first anticipated trajectory of the first UE, wherein the first anticipated trajectory includes one or more cells; receive a handover indication from the second UE in response to a handover condition for handing over a second UE to a cell of the network apparatus being met, the handover indication indicating that the second UE has selected a permitted slice from one or more permitted slices based on the second UE's anticipated trajectory; and complete the handover of the second UE to allow the second UE to access telecommunications resources associated with the permitted slice.

[0042] In an embodiment, an apparatus in a telecommunications network supported by at least one slice of a source cell includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: receive information identifying one or more permitted slices available to the apparatus during one or more anticipated handovers to one or more next cells, at least based on the apparatus's anticipated trajectory, wherein the anticipated trajectory includes one or more next cells; receive a first handover trigger indication including information identifying a first permitted slice among one or more permitted slices available to the apparatus during a first handover to a first cell in one or more next cells, at least based on the apparatus's anticipated trajectory; adjust the at least one slice to at least one first permitted slice selected from the identified first permitted slice based on the anticipated trajectory; and complete the first handover to the first cell to access telecommunications resources associated with the selected at least one first permitted slice.

[0043] In an embodiment, a system in a telecommunications network includes a first network device comprising: at least one first processor; and at least one first memory storing instructions that, when executed by the at least one first processor, cause the first network device to: send information identifying one or more permitted slices available to the UE during one or more anticipated handovers to one or more next cells, based at least on a user equipment (UE) anticipated trajectory, wherein the anticipated trajectory includes one or more next cells; and send a first handover trigger indication including information identifying a first permitted slice available to the UE during a first handover to the first cell, based at least on the UE's anticipated trajectory, wherein the anticipated trajectory includes the first cell, and the first permitted slice is among the one or more permitted slices. The system also includes a second network device comprising: at least one second processor; and at least one second memory storing instructions that, when executed by the at least one second processor, cause the second network device to: receive a first handover indication from the UE instructing the UE to use at least one first permitted slice from the one or more permitted slices based on the UE's anticipated trajectory; and complete a first handover during the anticipated handover to the first cell associated with the second network device to access telecommunications resources associated with the at least one first permitted slice.

[0044] In an embodiment, a network apparatus in a cell of a telecommunications network includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the network apparatus to: transmit information based at least on a first expected trajectory of a first user equipment (UE) identifying one or more allowed slices available to the UE during one or more expected handovers to one or more cells in the telecommunications network, wherein the first expected trajectory includes one or more cells; transmit a first handover trigger indication including information based at least on the first expected trajectory of the first UE identifying a first allowed slice available to the first UE during a first handover to a first next cell, wherein the first expected trajectory includes the first next cell and the first allowed slice is among one or more allowed slices; transmit a second handover trigger indication including information based at least on a second expected trajectory of a second UE identifying different allowed slices available to the second UE during a handover to a subsequent next cell, wherein the second expected trajectory includes the subsequent next cell; receive a handover indication from the second UE indicating that slice remapping has been performed by the second UE and that the second UE has updated and stored different allowed slices; and complete a handover of the second UE to allow the second UE to access telecommunications resources associated with at least one different allowed slice among the different allowed slices selected by the second UE.

[0045] Other example embodiments are provided or described for each example embodiment, including: an associated example method; components for performing any example method; a non-transitory computer-readable storage medium including instructions stored thereon, the instructions being configured, when executed by at least one processor, to cause a computing system to perform any example method; and an apparatus including at least one processor and at least one memory including computer program code configured, together with the at least one processor, to cause the apparatus to perform at least any example method.

[0046] Details of one or more examples of embodiments are set forth in the accompanying drawings and the following description. Other features will be apparent from the specification, the drawings, and the claims. Attached Figure Description

[0047] This disclosure is illustrated by way of example and is not limited to the accompanying drawings, wherein the same reference numerals indicate similar elements, and wherein: Figure 1A A simplified diagram is depicted illustrating the potential remapping challenges faced by the UE and the access network cell when the UE moves from the original RA to a different subsequent RA and eventually to a subsequent destination RA.

[0048] Figure 1BSlice remapping according to exemplary embodiments of the present disclosure is depicted.

[0049] Figure 2 The present disclosure describes a message flow exchanged between a UE and a source cell and a next cell during conditional handover, according to an exemplary embodiment of the present disclosure.

[0050] Figure 3 The present disclosure describes a message flow exchanged between the UE and the source cell and the next cell during LTM handover according to an exemplary embodiment of the present disclosure.

[0051] Figure 4 A simplified configuration of the UE's processor and memory is shown.

[0052] Figure 5 A simplified configuration of the processor and memory of a network access node is shown.

[0053] Specific embodiments of this disclosure are illustrated herein with reference to various accompanying drawings and sketches. Descriptions and illustrations have been prepared to enhance understanding. Therefore, it should be understood that the networks depicted in the drawings do not represent actual networks, devices, or apparatuses; rather, they are merely illustrations to explain the features of the disclosed methods and apparatus.

[0054] The aim is to provide both the illustrations and descriptions with simplicity and clarity, so as to effectively enable those skilled in the art to make, use, and best practice the exemplary embodiments described herein, in light of what is known in the art. Those skilled in the art will understand that various modifications and changes may be made to the specific embodiments described herein without departing from the spirit and scope of this disclosure. Therefore, the text and drawings should be considered illustrative and exemplary rather than restrictive or all-encompassing, and modifications to the specific embodiments described herein are intended to be included within the scope of this disclosure. Detailed Implementation

[0055] The following detailed description describes exemplary embodiments and is not intended to limit it to the explicitly disclosed combinations. Therefore, unless otherwise stated, the embodiments disclosed herein may be combined to form additional combinations not shown for the sake of brevity.

[0056] As used herein and in the appended claims, the terms “comprising,” “including,” or variations thereof are intended to refer to non-exclusive inclusion, such that a process, method, article, apparatus, or device that includes a list of elements includes not only those elements in the list but may also include other elements not expressly listed or other elements inherent to such process, method, article, or apparatus.

[0057] As used herein, the term “a” or “an” is defined as one or more. As used herein, the term “multiple” is defined as two or more. As used herein, the term “another” is defined as at least a second or more.

[0058] As used herein, the terms “include” and / or “have” are defined as including (i.e., open-ended language).

[0059] In the accompanying drawings, similar reference numerals are used consistently throughout the drawings to denote similar features.

[0060] Unless otherwise stated, the term "or" is used in this document in the sense of alternatives and combinations.

[0061] The terms “illustrative” and “exemplary” are used to indicate examples in this disclosure, not to indicate a level of quality.

[0062] As used herein, the term “user equipment” or “UE” means an apparatus that includes electronic components (e.g., modems) that function as radio frequency transceivers to (i) wirelessly transmit signals, messages and data to one or more components (e.g., devices, apparatuses) of a mobile telecommunications network using an air interface, and (ii) wirelessly receive signals, messages and data from one or more components of the network using an air interface.

[0063] As used herein, where applicable, the use of the letters “a” and “n” in a phrase indicates the first and last element or step in a group of elements or steps, such as cell 20a to 20n.

[0064] As used herein, the term “element” means: (a) an electronic hardware circuit implementation (e.g., an implementation of analog and / or digital circuitry) capable of performing one or more functions (such as network functions (NF) or user interface functions); and / or (b) a combination of electronic circuitry and a computer program product comprising software and / or firmware instructions stored on one or more electronic memories, the software and / or firmware instructions working together to cause an apparatus or device to perform one or more NF, UE, or method steps described herein; and / or (c) an electronic circuitry, such as an electronic microprocessor, a portion of a microprocessor, a processor, a portion of a processor, an electronic integrated circuit, or an electronic application processor (collectively referred to herein as a “processor”), which executes stored instructions (e.g., software or firmware) retrieved from at least one electronic memory, the instructions, when executed by the processor, causing the apparatus or element itself to perform one or more features, NF, UE, or method steps.

[0065] As used herein, the names “first,” “second,” “third,” and other relational terms (if any) are used only to distinguish one network or UE function, feature, or step from another, and do not necessarily require or imply any actual such relationship, order, or importance between these functions, features, or steps.

[0066] As used herein, the phrase "electronic memory" (referred to herein as "memory") means a non-transitory electronic storage medium (e.g., a volatile or non-volatile memory device). Examples of non-transitory electronic storage media include, but are not limited to: random access memory (RAM); programmable read-only memory (PROM); erasable programmable read-only memory (EPROM); flash memory EPROM; magnetic computer-readable media (e.g., floppy disk, hard disk, magnetic tape, any other magnetic medium); optical computer-readable media (e.g., compressed optical disc read-only memory (CD-ROM); digital versatile optical disc (DVD); Blu-ray disc (BD), etc., or combinations thereof), or any other non-transitory medium from which an electronic processor can retrieve stored instructions that, when executed, cause a device to perform one or more functions, features, or steps of a method or process.

[0067] Now for reference Figure 2 This illustrates an exemplary message flow between UE 100 and cell 200a and the next cells 200b to 200n, which are part of the telecommunications core network 200, during a conditional handover. In this first embodiment, cell 200a can be referred to as the source cell because cell 200a (i.e., the network access node within cell 200a) is currently supporting / serving UE 100. Figure 2 The diagram also shows a second UE 100a and its source cell 400, which will be discussed later. The access node is exemplarily referred to as 6G Node B (6NB) in this diagram. For simplicity, cells associated with the access node are labeled and used to explain the exemplary embodiments herein. Therefore, it should be understood that one or more cells may be associated with the access node.

[0068] It should be understood that, although in Figure 2 Only two UEs, 100 and 100a, are shown in the diagram, but in reality, cells 200a to 200n and 400 can support multiple UEs. Furthermore, it should be understood that messages can include one or more electronic signals, which may include instructions and data. Additionally, the telecommunications core network 200 can be a 5G core network, a 6G core network, or an evolved 5G core network.

[0069] During step 1a, the source cell and the next cells 200a to 200n, as well as the core network 200, have previously determined the allowed slice set based on the trajectory of UE100.

[0070] In an embodiment, UE 100 may include means associated with at least one slice (“current slice”) of the source cell 200a associated with an access node. For the purposes of this invention and for the sake of simplicity herein, the source cell 200a and its associated access node may be referred to as source cell 200a, but it should be understood that an access node may comprise multiple cells. Similarly, the next cells 200b to 200n and their associated next access nodes may each be referred to as next cells 200b to 200n, but it should be understood that each next access node may also be associated with multiple next cells.

[0071] UE 100 may include at least one electronic processor and at least one electronic memory for storing instructions that, when executed by the at least one processor, cause UE 100 (i.e., the device) to perform certain functions, features, and steps described herein. For the reader's reference. Figure 4 A simplified configuration of the processor 504 and memory 505 of UE 100 is shown. For the sake of brevity and to avoid repetition, it should be understood that when the discussion herein indicates that UE 100 (or UE 100a) has performed a function, feature, or step, it should be understood that at least the processor 504 of the corresponding UE executes electronic instructions from at least one memory 505 that have enabled the UE to perform such a feature, function, or step.

[0072] Next, in step 2a, UE 100 may receive a message that includes information, at least based on UE 100's expected trajectory identifier, about one or more permitted slices available to UE 100 during one or more expected handovers to one or more next cells (such as cells 200b to 200n). In an embodiment, the previously determined expected trajectory may include one or more next cells, including cells 200b to 200n. Figure 1B An example of slice remapping information for each cell is provided.

[0073] More in detail, such as Figure 1B As shown, one or more allowed slices in the received information may include at least one or more allowed slice lists, wherein each list is associated with one or more next cells 200b to 200n. Figure 1B In the example, RA1 can represent the current cell (corresponding to...) Figure 2 In cell 200a), and RA2 and RA3 can represent the next cell (corresponding to Figure 2 (Communities 200b and 200n in the middle). Figure 1BEach allowed slice list shown can indicate which network slices are supported in each cell (i.e., which network slices are supported by the current cell and each next cell, based on the UE's expected trajectory). Furthermore, each of the one or more allowed slice lists can include a mapping from a slice of the source cell to at least one slice of the target cell. For example, Figure 1B This indicates that slice 2 in RA1 is mapped to slice 1 in RA2, and slice 1 in RA2 is mapped to slice 3 in RA3.

[0074] Therefore, upon receiving the received information, UE 100 can select an allowed slice from one or more identified allowed slices. More specifically, it can select the selected slice from one of the allowed slice lists, where the selected allowed slice is further associated with the next cell (in this case, cell 200b). To distinguish this selected allowed slice from other slices, we can refer to it as the "first" allowed slice selected from the "first" allowed slice list of one or more allowed slice lists. Additionally, for clarity, next cell 200b can be referred to as the "first" next cell to distinguish it from other next cells; it should be understood that "next cell" refers to at least one network access node associated with next cell 200b.

[0075] In an embodiment, UE 100 may select a first allowed slice based on determining that the slice is supported by one or more access nodes in one or more of the next cells 200b to 200n involved in each of the one or more expected handovers.

[0076] In step 3a, in response to the handover condition (hereinafter referred to as the "first handover condition") being met, and after receiving information identifying one or more permitted slices, UE 100 may adjust (i.e., remap) at least one slice (i.e., the current slice) to the selected first permitted slice (as described above) based on UE 100's expected trajectory. This selected first permitted slice has been chosen by UE 100 from the identified one or more permitted slices. As an example of the remapping process, Figure 1B It is shown that when moving from RA1 to RA2, slice 2 is remapped to slice 1 because RA2 does not support slice 2. In addition, UE100 can use one or more received allowed slices to update the previously stored list of allowed slices and electronically store one or more received allowed slices in its memory.

[0077] Because UE 100 has received one or more allowed slices and selected one of such slices before being handed over to the next cell 200b, the source cell 200a or the next cell 200b (i.e., the network elements within such cells) does not need to dedicate signaling overhead (NAS overhead) to determining and selecting slices, thus saving valuable signaling overhead.

[0078] Furthermore, unlike existing methods, even after a handover is completed (e.g., first handover, second handover), the UE 100 can electronically store and retain the information it receives in its memory. This information is based on the UE 100's expected trajectory identifier during one or more expected handovers to one or more next cells 200b to 200n, and is available to the UE 100 in one or more permitted slices.

[0079] During step 4a, UE 100 may perform a handover procedure to the first next cell 200b among one or more next cells 200b to 200n. A handover is initiated in response to the handover conditions for UE 100 being met, and the handover message transmission in step 4a indicates that UE 100 has selected a first allowed slice from one or more allowed slices based on UE 100's trajectory (in...). Figure 2 Step 4a is shown as “Slice remapping has been performed”. Furthermore, during the handover process, UE 100 may send a handover indication (hereinafter referred to as “first handover indication”) to the second network device associated with the first next cell 200b, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to the first allowed slice.

[0080] Upon receiving such a first handover instruction, the second network device of the first next cell 200b may forward a message to network elements within the core network 200 during step 5a. This message indicates that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected first allowed slice. In an embodiment, the first handover instruction including the allowed slice list update may include a transparent container, which may then be forwarded by the second network device of the first next cell 200b to network elements within the core network 200.

[0081] During step 6a, based on the fact that the first handover condition has been met, UE 100 can complete a first handover to the first next cell 200b among one or more next cells 200b to 200n (including in a planned handover) to allow UE 100 to access telecommunications resources associated with the first permitted slice that UE 100 has selected. More specifically, during step 6a, UE 100 and the first next cell 200b can exchange messages indicating that the first handover has been completed, and UE 100 can be served by the first next cell 200b.

[0082] As used herein, the phrase “complete” handover means that the UE (such as UE 100), the source cell, and the next cell have completed the functions, features, and steps (including message exchange) set forth in steps 2a to 6a or similar steps described herein (e.g., steps 7a to 10a), thereby releasing radio resources by the source cell and establishing communication between the UE and the next cell. Therefore, the first handover described above can be completed when UE 100, its current source cell 200a, and the first next cell 200b have completed the functions, features, and steps (including message exchange) set forth in steps 2a to 6a, thereby releasing radio resources by the source cell 200a and establishing communication between UE 100 and the next cell 200b.

[0083] A timer, time information, or valid time information can be used to determine the time period during which the UE 100 is permitted (i.e., handover) within the corresponding cell in each of the next cells 200b to 200n (e.g., the first next cell 200b). In an embodiment, each next cell 200b to 200n can generate its own time period. Therefore, in such an embodiment, in response to the first handover condition being met during the time period set by the first next cell 200b, the UE 100 must adjust at least one slice (its current slice) to the selected first permitted slice and complete the first handover.

[0084] Now let's turn to the discussion of a subsequent or second switch.

[0085] At some point in time, the expected trajectory of UE 100 is to move from cell 200b to cell 200n (i.e., part of the aforementioned "expected trajectory"). To distinguish between the two cells, the movement can be described as from the first next cell 200b to the second next cell 200n. Although in Figure 2Only two next cells are shown, but it should be understood that this is merely exemplary. In alternative embodiments, the number of next cells may be more than two (“multiple” cells). Therefore, assuming that each of the multiple next cells has been included in the expected trajectory of UE 100, one or more slices supported by each of the multiple next cells will be among the one or more permitted slices initially sent to UE 100 during step 2a (e.g., see [link to relevant documentation]). Figure 1B It can be stored and retained by UE 100 even after the handover.

[0086] Next, having already received and stored one or more permitted slices identified based on the trajectory of UE 100, UE 100 does not need to receive them again. Therefore, in step 7a of the conditional handover procedure, UE 100 can continue to select another permitted slice from one or more permitted slice lists, wherein the selected permitted slice is also associated with another next cell, in this case cell 200n. To distinguish this selected permitted slice from other slices, it can be referred to as the "second" permitted slice selected from the "second" permitted slice list. Furthermore, for clarity, next cell 200n can be referred to as the "second" next cell to distinguish it from other next cells; it should be understood that "second next cell" means at least one network access node within next cell 200n.

[0087] In another embodiment, if the slice is supported by an access node in each of the next cells 200b to 200n involved in each handover, the selected second allowed slice may be the same slice as the first allowed slice.

[0088] Furthermore, during step 7a, in response to the satisfaction of another handover condition (hereinafter referred to as the "second handover condition"), based on the expected trajectory of UE 100, UE 100 may adjust (i.e., remap) the first allowed slice (i.e., its current slice) to a selected second allowed slice, which has been selected by UE 100 from one or more identified allowed slices. Additionally, UE 100 may update its stored list of allowed slices again.

[0089] Because UE 100 has already selected the second allowed slice before being switched to the second next cell 200n, cell 200b or 200n (i.e., network elements within such cells) does not need to dedicate signaling overhead (NAS overhead) to determining and selecting slices, thus saving valuable signaling overhead.

[0090] Similarly, unlike existing methods, even after the second handover has been completed, UE 100 continues to store and retain the information it has received in its memory, which identifies one or more permitted slices available to UE 100 during one or more anticipated handovers.

[0091] During step 8a, in response to the satisfaction of the second handover condition for handing over UE 100, UE 100 may proceed with another handover process to a second next cell 200n among one or more next cells 200b to 200n. The handover communication as part of the handover process in step 8a indicates that UE 100 has selected a second allowed slice from one or more allowed slices based on the UE 100's trajectory (in... Figure 2 Step 8a is shown as “Slice remapping configured”. Additionally, during this handover process, UE 100 may send a handover indication (hereinafter referred to as “second handover indication”) to the third network device associated with the second next cell 200n, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to the second allowed slice.

[0092] Upon receiving such a second handover instruction, the third network device of the second next cell 200n may forward a message to network elements within the core network 200 during step 9a. This message indicates that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected second allowed slice. In another embodiment, the second handover instruction, including the allowed slice list update, may include a transparent container, which can then be forwarded by the third network device of the second next cell 200n to network elements within the core network 200.

[0093] During step 10a, in response to the second handover condition being met, UE 100 may complete a second handover to one or more next cells 200b to 200n, specifically to the second next cell 200n (in the anticipated handover), to allow UE 100 access to telecommunications resources associated with the second permitted slice. More specifically, during step 10a, UE 100 and the second next cell 200n may exchange messages indicating that the second handover has been completed.

[0094] Furthermore, it should be understood that the completion of the second handover means that UE 100, its current source cell 200b, and the next cell 200n have completed the functions, features, and steps (including message exchange) described in steps 7a to 10a, thereby releasing radio resources by cell 200b and establishing communication between UE 100 and the next cell 200n.

[0095] The timer, time information, or valid time information can be used again to determine the time period during which the second next cell 200n can allow the UE 100 to be permitted (i.e., handover). Therefore, in this embodiment, in response to the handover condition being met during the time period set by the second next cell 200n, the UE 100 must adjust the first allowed slice (its current slice) to the selected second allowed slice and complete the second handover.

[0096] As discussed above regarding steps 1a to 10a, source cell 200a and next cells 200b to 200n also involve conditional handover and slice remapping methods. Their involvement will now be discussed in more detail. Thereafter, the phrase "system" may be used to refer to one or more of cells 200a to 200n and UE 100.

[0097] In an embodiment, during step 1a, the source cell and the next cells 200a to 200n have previously determined a set of one or more allowed slices based on the trajectory of UE 100.

[0098] Each of the next 200a to 200n cells may be associated with at least one network device (e.g., a 5G or 6G access node). Furthermore, each network device may include at least one electronic processor and at least one electronic memory for storing instructions, which, when executed by the at least one processor, cause each network device to perform one or more functions, features, or steps set forth herein. For the reader's reference. Figure 5 A simplified configuration of an access node or network device including at least one processor 602 and at least one memory 603 is shown. For the sake of brevity and to avoid repetition, it should be understood that when the discussion herein indicates that a first, second, or third network device has performed a function, feature, or step, it should be understood that at least the processor 602 of the corresponding network device executes electronic instructions from at least one memory 603 that have caused the device to perform those features, functions, and steps.

[0099] During step 1a, a set of one or more allowed slices has been pre-determined based on the trajectory of UE 100 during the CHO handover process. A first network device (e.g., a 5G source access node or a 6G source access node) associated with the source cell 200a of the system can send information (hereinafter referred to as "sending information") to UE 100. This information is based at least on the expected trajectory of UE 100 identifying one or more allowed slices of UE 100 during one or more expected handovers to one or more cells 200b to 200n in the telecommunications network 200. To distinguish the processor and memory of other network devices, the processor of the first network device may be referred to as the "first" processor and the memory as the "first" memory.

[0100] As previously stated, the transmitted information may include at least one or more lists of allowed slices, each list being associated with one of one or more cells 200b to 200n (e.g., see...). Figure 1B Furthermore, each of the one or more allowed slice lists may also include: a mapping of at least one slice of source cell 200a to at least one slice within each of the one or more allowed slice lists.

[0101] Next, during step 4a, when UE 100 is ready to move from its source cell 200a to the next cell 200b (i.e., the first next cell discussed above), in response to the first handover condition for handing over UE 100 being met, the second network device associated with the first next cell 200b can perform a first handover procedure with UE 100. The communication associated with the first handover procedure indicates that UE 100 has selected a first allowed slice from one or more allowed slices based on UE 100's trajectory. Additionally, as previously mentioned, during the handover procedure, UE 100 can send a first handover indication to the second network device of the first next cell 200b, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted its current slice to the first allowed slice.

[0102] Upon receiving the first handover instruction, the second network device of the first next cell 200b may forward a message to network elements within the core network 200 during step 5a, the message indicating that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected first allowed slice. In another embodiment, the first handover instruction including the allowed slice list update may include a transparent container, which may then be forwarded by the second network device to network elements within the core network 200.

[0103] As previously described, the second network device of the first next cell 200b may set a timer to determine the time period during which the UE 100 is allowed to enter cell 200b (i.e., handover). Therefore, in this embodiment, in response to the handover condition being met during the time period set by the first next cell 200b, the UE 100 must adjust at least one slice (its current slice) to the selected first allowed slice and complete the first handover.

[0104] Subsequently, during step 6a, the second network device may complete a first handover (as defined above) to a first next cell 200b in one or more anticipated handovers to allow UE 100 to access telecommunications resources associated with the first permitted slice. More specifically, in step 6a, the second network device and UE 100 may exchange a message indicating that a first handover to a first cell 200b in one or more anticipated handovers has been completed, allowing UE 100 to access telecommunications resources associated with the first permitted slice. Similarly, it should be understood that the completion of the second handover means that radio resources are released by cell 200a and communication is established between UE 100 and the next cell 200b.

[0105] We now turn to a discussion of some steps that focus on cells 200a to 200n (and the network devices within these cells) during subsequent handovers (in this case, the second handover).

[0106] As previously described, at some point in time, the trajectory of UE 100 is expected to move from cell 200b to cell 200n. Cells 200b and 200n can again be referred to as the first next cell 200b and the second next cell 200n, respectively, and the network devices associated with such cells can be referred to as the second network device and the third network device (e.g., a 5G access node or a 6G access node). Remember that, according to the disclosure herein, the permitted slices identified based on the trajectory of UE 100 have already been received and stored, and UE 100 does not need to receive them again. Accordingly, in step 7a of the conditional handover procedure, UE 100 can, in response to another handover condition (hereinafter referred to as the "second handover condition") being met, adjust the selected first permitted slice to the second permitted slice and update its permitted slice list when UE 100 moves from the first next cell 200b to the second next cell 200n.

[0107] Therefore, in step 8a, when UE 100 is ready to move (or handover) from the first next cell 200b to the second next cell 200n, in response to the second handover condition for handing UE 100 to the second next cell 200n being met, the third network device can perform a second handover procedure with UE 100. The communication during the second handover procedure indicates that UE 100 has selected a second allowed slice from one or more allowed slices based on UE 100's trajectory. Additionally, as previously mentioned, during the handover procedure, UE 100 can send a second handover indication to the third network device of the second next cell 200n, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted its current slice to the second allowed slice.

[0108] Upon receiving the second handover instruction, the third network device of the second next cell 200n may forward a message to network elements within the core network 200 during step 9a. This message indicates that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected second allowed slice. In an embodiment, the second handover instruction, including the allowed slice list update, may include a transparent container, which can then be forwarded by the third network device to network elements within the core network 200.

[0109] As previously described, the second next cell 200n (the third network device within the second next cell 200n) can be configured with a timer to determine the time period during which the second next cell 200n can allow the UE 100 to be permitted (i.e., to hand over to its cell). Therefore, in this embodiment, in response to the second handover condition being met during the time period set by the second next cell 200n, the UE 100 must adjust its first allowed slice (its current slice) to the selected second allowed slice and complete the second handover.

[0110] Before further explanation, it should be understood that the third network device, as well as the first and second network devices, may include, for example, a 5G access node or a 6G access node.

[0111] Subsequently, in step 10a, the third network device associated with the second next cell 200n can complete the second handover as expected, thereby allowing UE 100 to access telecommunications resources associated with the second permitted slice. In summary, to complete the second handover of UE 100, its source cell 200b and next cell 200n can exchange messages including the release of radio resources by cell 200b and the establishment of communication between UE 100 and next cell 200n.

[0112] It should be noted earlier that telecommunications network 200 includes a second UE 100a. Now, let's turn to the discussion of utilizing this second UE 100a.

[0113] In the discussion above, cell 200a (and associated network devices, such as access nodes) is used as the source cell for UE 100. Furthermore, cell 200a can also be used as the "next" cell for other UEs. In fact, each of cells 200a through 200n can be used as the source cell for some UEs and the "next" cell for others.

[0114] In this embodiment, cell 200a can act as the "next" cell of UE 100a and as the source cell of UE 100. For clarity, UE 100 is referred to as the "first" UE, and UE 100a is referred to as the "second" UE.

[0115] Therefore, as the source cell of the first UE 100, the associated network device (e.g., a 5G or 6G access node) within cell 200a can perform the steps described above, including sending information that identifies one or more permitted slices available to the first UE 100 during one or more anticipated handovers from the first UE 100 to one or more cells 200a to 200n, based at least on the anticipated trajectory of the first UE 100. This trajectory can be referred to as the "first" anticipated trajectory, wherein the first anticipated trajectory includes one or more cells 200a to 200n.

[0116] Possibly simultaneously, a network device within cell 200a can be used as the "next" cell for the second UE 100a. Therefore, the network device can complete the handover process with the second UE 100a in response to the handover conditions for handover to the second UE 100a being met. Communication during the handover process indicates that the UE 100a has selected an allowed slice from one or more allowed slices based on the UE 100a's trajectory. Additionally, during the handover process, the UE 100a can send a handover indication to the network device associated with cell 200a, indicating that the UE 100a has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to the first allowed slice.

[0117] Upon receiving such a handover instruction, the network device may forward a message to network elements within the core network 200, indicating that UE 100a has updated its allowed slice list and adjusted its current slice to the selected first allowed slice. In an embodiment, the handover instruction including the allowed slice list update may include a transparent container, which can then be forwarded by the network device to network elements within the core network 200.

[0118] Subsequently, the network device can complete the handover of the second UE 100a to cell 200a in one or more cells (as defined above as "complete"), thereby enabling the second UE 100a to access telecommunications resources associated with the selected permitted slice. More specifically, the network device, the second UE 100a, and the source cell 400 of the second UE 100a can exchange messages via telecommunications channels 401 to 403, the messages including one or more steps as described above, indicating that the handover to cell 200a has been completed, so that the second UE 100a can access the telecommunications resources associated with the selected permitted slice. To complete the handover of the second UE 100a, the second UE 100a, its source cell 400, and the next cell 200a can exchange messages including the release of radio resources by cell 400 and the establishment of communication between the second UE 100a and the next cell 200a.

[0119] As previously mentioned, such network devices associated with cells 200a (and 400) may include 5G access nodes or 6G access nodes.

[0120] Now for reference Figure 3 This illustrates an exemplary electronic message flow between UE 100 and cell 200a and the next cells 200b to 200n, which are part of the telecommunications core network 200, during LTM handover. Again, in this embodiment, cell 200a can be referred to as the "source cell" because cell 200a is currently supporting UE 100. Figure 3 The second UE100a and its source cell 400 are also shown again (we will set these cells aside for later discussion).

[0121] It should be understood that, although in Figure 3 Only two UEs, 100 and 100a, are shown, but in reality, cells 200a to 200n (and 400) can support multiple UEs. Furthermore, it should be understood that messages can include one or more electronic signals, which may include instructions and data. Also, again, the telecommunications core network 200 can be, for example, a 5G core network, a 6G core network, or an evolved 5G core network.

[0122] During step 1b, cells 200a to 200n have previously determined a set of one or more allowed slices based on the trajectory of UE 100.

[0123] In this embodiment, UE 100 may again include means associated with at least one slice (“current slice”) of its source cell 200a. For the purposes of this document, source cell 200a and its associated access node may again be referred to as source cell 200a, but it should be understood that an access node may be associated with multiple cells. Similarly, next cells 200b to 200n and their associated next access nodes will be referred to as next cells 200b to 200n, but it should be understood that each next access node may be associated with multiple next cells.

[0124] UE 100 may include at least one electronic processor and at least one electronic memory for storing instructions, which, when executed by the at least one processor, cause UE 100 to perform one or more functions, features, and steps described herein. Again, for the reader's reference, Figure 4 A simplified configuration of processor 504 and memory 505 is shown. For the sake of brevity, it should be understood that when the discussion herein indicates that UE 100 has completed a function, feature, or step, the processor 504 of the corresponding UE 100 executes electronic instructions from at least one memory 505 that have enabled UE 100 to complete those features, functions, and steps.

[0125] More specifically, during step 2b, UE 100 may receive information that identifies one or more permitted slices available to UE 100 during one or more anticipated handovers to one or more next cells 200b to 200n, based at least on UE 100's anticipated trajectory. In an embodiment, the anticipated trajectory includes one or more next cells 200b to 200n.

[0126] Next, unlike CHO slice remapping, in LTM slice remapping, UE 100 first receives a trigger from the cell of network 200 (in this case, from source cell 200a) before adjusting its current slice. In an embodiment, during step 3b, UE 100 may receive a first handover trigger indication including a trigger (first trigger), which also includes information identifying a first allowed slice available to UE 100 during a first handover to first cell 200b, based at least on UE 100's expected trajectory. In an embodiment, the first allowed slice is among one or more previously received allowed slices.

[0127] The information identifying the first allowed slice may include at least one or more lists of first allowed slices, wherein each list is associated with one of the one or more next cells 200b to 200n. Furthermore, each of the one or more lists of first allowed slices may also include a mapping from at least one slice (i.e., the current slice) of the source cell 200a to at least one slice within each of the one or more lists of first allowed slices. Figure 1B Example slice remapping information is described below. Note that for LTM slice remapping, each allowed slice list can be associated with an allowed slice list ID (e.g., see [link to example]). Figure 3 Step 3B in the process.

[0128] Next, upon receiving the first handover trigger indication message, UE 100 can then select a first allowed slice from the identified first allowed slice during step 4b, wherein the selected first allowed slice is associated with the next cell (in this case, cell 200b).

[0129] In an embodiment, the first permitted slice may be selected by the UE 100 based on a determination that the slice is supported by one or more access nodes in one or more of the next cells 200b to 200n involved in each of the one or more anticipated handovers.

[0130] When selecting the first allowed slice, UE 100 may adjust one of its current slices (at least one slice) to the selected first allowed slice based on the expected trajectory of UE 100 during step 4b.

[0131] Unlike existing methods, UE 100 can store information previously received by UE 100 during steps 2b and 3b. More specifically, even after the first handover has been completed, UE 100 can store and retain information that identifies the first allowed slice available to UE 100 during the first handover to the first next cell 200b, based at least on UE 100's expected trajectory. Furthermore, UE 100 can update its allowed slices.

[0132] Because UE 100 has received the allowed slice and selected one of the received slices before being handed over to the next cell 200b, the source cell 200a or the next cell 200b (i.e., network elements within such cells) does not need to dedicate signaling overhead (NAS overhead) to determining and selecting slices, thus saving valuable signaling overhead.

[0133] During step 5b, in response to the handover conditions for UE 100 being met, UE 100 may complete a first handover procedure to the first next cell 200b among one or more next cells 200b to 200n. The communication during the second handover procedure indicates that UE 100 has selected a first allowed slice from one or more allowed slices based on UE 100's trajectory. Furthermore, during the first handover procedure, UE 100 may send a first handover indication to the second network device associated with the first next cell 200b, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to the first allowed slice.

[0134] Upon receiving such a first handover instruction, during step 6b, the second network device of the first next cell 200b may forward a message to network elements within the core network 200, indicating that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected first allowed slice. In an embodiment, the first handover instruction including the allowed slice list update may include a transparent container, which may then be forwarded by the second network device of the first next cell 200b to network elements within the core network 200.

[0135] During step 7b, UE 100 may complete a first handover to the first next cell 200b among one or more next cells 200b to 200n in the anticipated handover, so that UE 100 can access telecommunications resources associated with the first permitted slice. Similarly, as used herein, the phrase “completed” handover means that UE 100, its current source cell 200a, and the next cell 200b have completed the functions, features, and steps (including message exchange) set forth in steps 2b to 7b or similar steps described herein (e.g., steps 8b to 12b), such that radio resources are released by the source cell 200a and communication has been established between UE 100 and the next cell 200b.

[0136] It can be said that UE 100 would not have adjusted its slice or completed the handover if it had not received the first handover trigger indication in step 3b. Therefore, it can be clearly stated that UE 100 does so in response to the received first handover trigger indication in order to adjust at least one slice to the selected first allowed slice and complete the first handover.

[0137] A timer, time information, or valid time information can be used to determine the time period during which the next cell 200b allows the UE 100 to hand over. Therefore, in this embodiment, the UE 100 must adjust its current slice to the selected first allowed slice and complete the first handover during the time period set by the first next cell 200b.

[0138] Now let's turn to the discussion of a subsequent or second switch.

[0139] At a certain point in time, the expected trajectory of UE 100 is to move from cell 200b to cell 200n. To distinguish between the two cells, we can again say that the movement is from the first next cell 200b to the second next cell 200n. Although in Figure 3 Only two next cells are shown, but it should be understood that this is merely exemplary. In alternative embodiments, the number of next cells may be more than two (“multiple” cells). Therefore, assuming that each of the multiple next cells has been included in the expected trajectory of UE 100, then each supported slice for each of the multiple next cells will be in one or more identified allowed slices that were initially sent to UE 100 during steps 2b and 3b, and that have been stored and retained by UE 100 even after the handover.

[0140] One or more allowed slices have already been received and stored based on the trajectory of UE 100, and UE 100 does not need to receive them again. Therefore, in step 8b, UE 100 may receive a second handover trigger indication message including a second or subsequent trigger, which may include at least one piece of information based at least on the expected trajectory of UE 100 identifying a second allowed slice available to UE 100 during a second handover to a second next cell 200n, wherein the expected trajectory includes the second next cell 200b. In an embodiment, the information identifying the second allowed slice is in one or more allowed slices received by UE 100 during step 2b, based at least on the expected trajectory of UE 100 to one or more next cells 200b to 200n.

[0141] Upon receiving the second handover trigger indication message, UE 100 may then select a second allowed slice from the identified second allowed slice during step 9b, wherein the selected second allowed slice is further associated with the next cell 200n.

[0142] In this embodiment, based on determining that one or more access nodes in the next cell 200n support the second allowed slice, the UE 100 can select the selected second allowed slice. Thereafter, the UE 100 can adjust its current slice (the first allowed slice) to the selected second allowed slice based on its expected trajectory.

[0143] Unlike existing methods, during step 9b, even after the second handover has been completed, the UE 100 can update its stored list of allowed slices and electronically store and retain the updated list in its memory.

[0144] Because UE 100 has already received the allowed slice and selected one of such slices before being handed over to the next cell 200n, cell 200b or cell 200n (i.e., network elements within such cells) does not need to dedicate signaling overhead (NAS overhead) to determining and selecting slices, thus saving valuable signaling overhead.

[0145] During step 10b, in response to the satisfaction of the second handover condition for UE 100, UE 100 can complete another handover procedure to the second next cell 200n. The handover procedure communication indicates that UE 100 has selected a second allowed slice from one or more allowed slices based on UE 100's trajectory. Furthermore, during the second handover procedure, UE 100 can send a second handover indication to the third network device associated with the second next cell 200n, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to the second allowed slice.

[0146] During step 11b, upon receiving such a second handover indication, the third network device associated with the second next cell 200n can forward a message to network elements within the core network 200, indicating that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected second allowed slice. In an embodiment, the second handover indication, including the allowed slice list update, may include a transparent container, which can then be forwarded by the third network device of the second next cell 200n to network elements within the core network 200.

[0147] During step 12b, UE 100 may complete a second handover to the second next cell 200n in the anticipated handover, in order to allow UE 100 access to telecommunications resources associated with the second permitted slice. Similarly, as used herein, the phrase “completed” second handover means that UE 100, its current source cell 200b, and the next cell 200n have completed the functions, features, and steps (including message exchange) set forth in steps 8b through 12b, thereby releasing radio resources from the current source cell 200b and establishing communication between UE 100 and the next cell 200n.

[0148] A timer can be used to determine the time period during which the next cell 200n allows the UE 100 to be handed over. Therefore, in this embodiment, the UE 100 must adjust its current slice (the first allowed slice) to the selected second allowed slice and complete the second handover during the time period set by the second next cell 200n.

[0149] As described above, during steps 1b to 12b, source cell 200a and next cells 200b to 200n also participate in the LTM handover slice remapping process. Their participation will now be discussed in more detail. Thereafter, the phrase "system" may be used to refer to one or more cells among cells 200a to 200n.

[0150] In an embodiment, during step 1b, the source cell 200a and the next cell 200n have previously determined a set of one or more allowed slices based on the trajectory of UE 100.

[0151] Each of the next 200a to 200n cells may be associated with a network device (e.g., a 5G or 6G access node). Additionally, the network device may include at least one electronic processor and at least one electronic memory for storing instructions, which, when executed by the at least one processor, cause each network device to perform one or more functions, features, or steps.

[0152] For readers' reference again, Figure 5A simplified configuration of a network device (e.g., an access node associated with at least one cell 200a to 200n) is shown, which may include at least one electronic processor 602 and at least one electronic memory 603.

[0153] One or more allowable slices have been pre-determined based on the trajectory of UE 100. A first network device associated with the source cell 200a of the system (e.g., a source access node serving UE 100 prior to the first handover, such as a 5G or 6G access node) can send information (hereinafter referred to as "sending information") to UE 100 during step 2b. This information is based at least on the expected trajectory of UE 100 identifying one or more allowable slices available to UE 100 during one or more expected handovers to one or more cells 200b to 200n in the telecommunications network 200. Similarly, in this embodiment, the expected trajectory includes one or more cells (200b to 200n, sometimes referred to herein as "cells" or "next cells"). To distinguish the processors and memories of other network devices, the processor of the first network device may be referred to as the "first" processor, and the memory as the "first" memory.

[0154] As previously described, the transmitted information may include at least one or more allowed slice lists, wherein each list is associated with one of one or more cells 200b to 200n, including a first next cell 200b. Additionally, each of the one or more allowed slice lists may also include a mapping of at least one slice of the source cell 200a supporting UE 100 to at least one slice within each of the one or more allowed slice lists.

[0155] Next, as previously described, during the LTM process, UE 100 adjusts (remaps) its current slice after receiving a trigger from source cell 200a. In an embodiment, a first network device associated with source cell 200a may send a first handover trigger indication message to UE 100 in step 3b. In an embodiment, the first handover trigger indication message may include: a first trigger, and an identifier of a first allowed slice available to UE 100 during a first handover to the first next cell 200b, based at least on the expected trajectory of UE 100, wherein the expected trajectory includes the first next cell 200b. In an embodiment, the first allowed slice in the first handover trigger indication message is among one or more allowed slices previously received by UE 100 during step 2b.

[0156] After UE 100 has adjusted its current slice to the first allowed slice, in step 4b, the second network device in the first next cell 200b of the system can complete the handover process in response to the handover conditions for handing over UE 100 being met. The handover process communication indicates that UE 100 has selected the first allowed slice from one or more allowed slices based on UE 100's trajectory. Additionally, during the handover process, in step 5b, UE 100 can send a first handover indication to the second network device associated with the first next cell 200b, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted its current slice to the first allowed slice.

[0157] Upon receiving such a first handover instruction, during step 6b, the second network device of the first next cell 200b may forward a message to network elements within the core network 200, indicating that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected first allowed slice. In an embodiment, the first handover instruction including the allowed slice list update may include a transparent container, which may then be forwarded by the second network device of the first next cell 200b to network elements within the core network 200.

[0158] Subsequently, the second network device can complete the first handover (from the anticipated handover) to the first next cell 200b. Similarly, as used herein, the phrase “complete” the first handover means that UE 100, its current source cell 200a, and the next cell 200b have completed the functions, features, and steps (including message exchange) described in steps 2b through 7b, thereby releasing radio resources by the source cell 200a and establishing communication between UE 100 and the next cell 200b.

[0159] We now turn to a discussion of some steps that will focus on cells 200a to 200n (and the network devices within these cells) during subsequent or second LTM-based handovers.

[0160] As previously mentioned, at a certain point in time, the trajectory of UE 100 is expected to move from cell 200b to cell 200n. Cells 200b and 200n can again be referred to as the first next cell 200b and the second next cell 200n, respectively, and the network devices having such cells can be referred to as the second network device and the third network device (e.g., 5G access node or 6G access node).

[0161] Next, in step 8b, during the LTM process, after the second network device in the first next cell 200b sends a second handover trigger indication message to the UE 100, the UE 100 may further adjust (remap) its current slice.

[0162] In an embodiment, the second handover trigger indication may include: a second trigger, and an identifier of a second allowed slice available to UE 100 during a second handover to the second next cell 200n, based at least on the expected trajectory of UE 100, wherein the expected trajectory includes the second next cell 200n. In an embodiment, the second allowed slice in the second handover trigger indication message is among one or more received allowed slices previously received by UE 100 during step 2b.

[0163] After UE 100 adjusts its current slice (first allowed slice) to the second allowed slice in step 9b, the third network device in the second next cell 200n of the system can complete the second handover procedure to the second next cell 200n in response to the satisfaction of the second handover condition for handing over UE 100. The communication during the second handover procedure indicates that UE 100 has selected the second allowed slice from one or more allowed slices based on UE 100's trajectory. Furthermore, during the second handover procedure, UE 100 can send a second handover indication to the third network device associated with the second next cell 200n, indicating that UE 100 has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted its current slice to the second allowed slice.

[0164] Upon receiving such a second handover instruction, during step 11b, the third network device of the second next cell 200n may forward a message to network elements within the core network 200, indicating that the UE 100 has updated its allowed slice list and adjusted its current slice to the selected second allowed slice. In an embodiment, the second handover instruction including the allowed slice list update may include a transparent container, which may then be forwarded by the third network device of the second next cell 200n to network elements within the core network 200.

[0165] In the embodiments, it should be understood that the third network device may include at least one third processor and at least one third memory storing instructions that, when executed by the at least one third processor, cause the third network device to perform the functions, features and steps described herein.

[0166] As previously described, the second next cell 200n can be configured with a timer to determine the time period during which the second next cell 200n (i.e., the third network device within cell 200n) can allow the UE 100 to be permitted (i.e., handover). Therefore, in this embodiment, the UE 100 must adjust its current slice (the first permitted slice) to the selected second permitted slice and complete the second handover during the time period set by the third network device of the second next cell 200n.

[0167] Subsequently, the third network device within the second next cell 200n can complete the second handover to the second next cell 200b in the expected handover, thereby allowing UE 100 to access the telecommunications resources associated with the second permitted slice. Again, "completing" the second handover means that UE 100, its current source cell 200b, and its current next cell 200n have completed the functions, features, and steps (including message exchange) described in steps 8b to 12b, thereby releasing radio resources by the source cell 200b and establishing communication between UE 100 and the next cell 200n.

[0168] Similar to the first handover, it can be said that "unless" the second handover trigger indication is received in step 8b, UE 100 would not have adjusted its slice or completed the second handover. Therefore, it can be fairly stated that UE 100 does so in response to the received second handover trigger indication in order to adjust its first allowed slice to the selected second allowed slice and complete the second handover.

[0169] In the embodiments, each of the first, second, and third network devices may include, for example, a 5G access node or a 6G access node.

[0170] Now let’s turn our attention to the second UE 100a.

[0171] Although the network device of source cell 200a can be used as the source cell of the first UE 100, it can also be used as the "next" cell of the second UE 100a.

[0172] Therefore, as the source cell, the network device associated with cell 200a (e.g., a 5G or 6G access node) can perform the steps described above, including sending information to the first UE 100, which is based at least on a first expected trajectory identifier of the first UE 100 indicating one or more permitted slices available to the first UE 100 during one or more expected handovers to one or more cells 200a to 200n in the telecommunications network 200. In an embodiment, the first expected trajectory may include one or more cells 200a to 200n.

[0173] Furthermore, when used again as the source cell for UE 100, the network device may send a first handover trigger indication, which includes: a handover trigger, and information identifying a first allowed slice available to the first UE 100 during a first handover to the first next cell (200b in this case), based at least on the expected trajectory of the first UE (hereinafter referred to as the "first expected trajectory"). In an embodiment, the first expected trajectory may include the first next cell 200b, and the first allowed slice may be in one or more allowed slices previously received by the UE 100.

[0174] Furthermore, the network device within cell 200a, now used as the "next" cell for the second UE 100a, can send a second handover trigger indication, which includes: triggering, and information identifying, at least based on the expected trajectory of the second UE 100a (hereinafter referred to as the "second expected trajectory"), the allowed slices ("different allowed slices") available to the second UE 100a during the handover to the subsequent next cell. In embodiments, the second expected trajectory may include subsequent cells 200b to 200n or different subsequent next cells ( Figure 3 (Not shown in the image). Therefore, the "next" cell can be referred to as the subsequent next cell.

[0175] In response to the handover conditions for the second UE 100a being met, the second UE 100a can complete the handover process to cell 200b. The handover process communication indicates that the second UE 100a has selected an allowed slice from one or more allowed slices based on its trajectory. Additionally, during the handover process, the second UE 100a can send a handover indication to another network device associated with cell 200b, indicating that the second UE 100a has updated its allowed slice list by storing one or more received identified allowed slices and has adjusted the current slice to an allowed slice.

[0176] Upon receiving such a handover instruction, the network device of cell 200b can forward a message to network elements within core network 200, indicating that the second UE 100a has updated its allowed slice list and adjusted its current slice to the selected allowed slice. In an embodiment, the handover instruction including the allowed slice list update may include a transparent container, which can then be forwarded by the network device associated with cell 200b to network elements within core network 200.

[0177] Subsequently, the network device can complete the transition from the second UE 100a to the next cell (which may be cell 200b or...). Figure 3The handover of a cell (not shown) to allow the second UE 100a to access telecommunications resources associated with different permitted slices selected by the second UE 100a during the reconfiguration step should be understood to mean that the second UE 100a, its source cell 400, and the next cell 200a can exchange messages via telecommunications channels 401 to 403, including one or more steps as described above, including the release of radio resources by cell 400 and the establishment of communication between the second UE 100a and the next cell 200a.

[0178] As previously described, cell 200a, as the next cell, can be configured with a timer to determine the time period during which cell 200a may allow the second UE 100a to be permitted (i.e., handover). Therefore, in this embodiment, the second UE 100a must adjust its current slice to the selected different permitted slice and complete the handover to the next cell 200a during the time period set by the network device of the next cell 200a.

[0179] Similar to the previous LTM handover, it can be said that "unless" a handover trigger indication is received, the second UE 100a will not adjust its current slice or complete the handover. Therefore, it is fair to say that in order to adjust its current slice to the selected different allowed slice and complete the handover, the second UE 100a does so in response to the received handover trigger indication.

[0180] Furthermore, network devices may include, for example, 5G access nodes or 6G access nodes.

[0181] While the foregoing description and accompanying drawings depict certain exemplary embodiments in the context of certain example combinations of elements, functions, or steps, it should be understood that different combinations of elements, functions, and / or steps may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, combinations of elements, functions, and / or steps different from those explicitly described above are also contemplated as being set forth in some of the appended claims. Although specific terms may be used herein, they are used only in a general and descriptive sense and not for limiting purposes.

[0182] The following claims language is incorporated herein by reference in an expanded form (i.e., from the widest to the narrowest hierarchy), wherein each possible combination indicated by reference in the plurality of dependent claims is described as a unique, independent embodiment.

[0183] The benefits, other advantages, and solutions to challenges have been described above with respect to specific embodiments of this disclosure. However, the benefits, advantages, solutions to challenges, and any elements(s) that may cause or result in such benefits, advantages, or solutions, or make such benefits, advantages, or solutions more apparent, should not be construed as key, essential, or necessary features or elements of any or all claims.

[0184] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0185] Clause 1. An apparatus in a telecommunications network associated with at least one slice of a source cell, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: receive information identifying one or more permitted slices available to the apparatus during one or more anticipated handovers to one or more next cells, at least based on a anticipated trajectory of the apparatus, wherein the anticipated trajectory includes the one or more next cells; adjust the at least one slice to at least one first permitted slice among the identified one or more permitted slices based on the anticipated trajectory; and complete a first handover to the first next cell among the one or more next cells during the plurality of anticipated handovers to access telecommunications resources associated with the at least one first permitted slice.

[0186] Clause 2. The apparatus according to Clause 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: adjust the at least one slice and complete the first switch in response to a first switching condition being met.

[0187] Clause 3. The apparatus according to Clause 1, wherein the received information includes at least one or more lists of allowed slices, wherein each of the lists is associated with one of the one or more next cells.

[0188] Clause 4. The apparatus according to Clause 3, wherein each of the one or more allowed slice lists further includes a mapping of the at least one slice of the source cell to at least one slice within each of the one or more allowed slice lists.

[0189] Clause 5. The apparatus according to Clause 3, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: select the at least one first allowed slice from a first allowed slice list of the one or more allowed slice lists, the first allowed slice list being associated with the first next cell.

[0190] Clause 6. The apparatus according to Clause 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: store the received information in the at least one memory, the information identifying the one or more permitted slices available to the apparatus during the one or more anticipated handovers to the one or more next cells based on the anticipated trajectory; and, upon completion of the first handover, retain the received information identifying the one or more permitted slices in the at least one memory.

[0191] Clause 7. The apparatus according to Clause 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: adjust the at least one slice to at least one second allowed slice among the identified one or more allowed slices based on the expected trajectory, in response to the second handover condition being satisfied; and complete a second handover to a second next cell among the one or more next cells in the plurality of expected handovers to access telecommunications resources associated with the at least one second allowed slice.

[0192] Clause 8. A system in a telecommunications network, the system comprising: a first network device including: at least one first processor; and at least one first memory storing instructions that, when executed by the at least one first processor, cause the first network device to: send information identifying one or more permitted slices available to the UE during one or more anticipated handovers to one or more cells in the telecommunications network, based at least on an anticipated trajectory of a user equipment (UE) in the telecommunications network, wherein the anticipated trajectory includes the one or more cells; a second network device including: at least one second processor; and at least one second memory storing instructions that, when executed by the at least one second processor, cause the second network device to: receive a first handover indication in response to a first handover condition for handing the UE to a first next cell being satisfied, the first handover indication indicating that the UE will use at least one first permitted slice of the one or more permitted slices based on the UE's anticipated trajectory; and complete a first handover to the first next cell in the one or more cells during the anticipated handover to allow the UE to access telecommunications resources associated with the at least one first permitted slice.

[0193] Clause 9. The system according to Clause 8, wherein the first network device includes the source access node currently supporting the UE.

[0194] Clause 10. The system according to Clause 8, wherein the first handover indication further includes an indication that the UE has updated its list of allowed slices and has adjusted at least one current slice to the at least one first allowed slice.

[0195] Clause 11. The system according to Clause 8, wherein the transmitted information includes at least one or more lists of allowed slices, wherein each of the lists is associated with one of the one or more cells.

[0196] Clause 12. The system according to Clause 11, wherein each of the one or more allowed slice lists further comprises: a mapping of at least one slice of the source cell to at least one slice within each of the one or more allowed slice lists.

[0197] Clause 13. The system according to Clause 8 further includes a third network device in a second cell of the telecommunications network, the third network device comprising: at least one third processor; and at least one third memory storing instructions that, when executed by the at least one third processor, cause the third network device to: receive a second handover indication from the UE after a second handover process in response to a second handover condition for handing the UE to a second next cell being satisfied, the second handover indication indicating that the UE has selected at least one second allowed slice from the one or more allowed slices based on the UE's expected trajectory; and complete a second handover in the expected handover to the second cell in the one or more cells to access telecommunications resources associated with the at least one second allowed slice.

[0198] Clause 14. The system according to Clause 13, wherein the second handover indication further includes: an indication that the UE has updated its list of allowed slices and has adjusted the at least one first allowed slice to the at least one second allowed slice.

[0199] Clause 15. The system according to Clause 13, wherein each of the first network device, the second network device and the third network device includes a 5G access node or a 6G access node.

[0200] Clause 16. A network apparatus in a telecommunications network, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network apparatus to: transmit information identifying one or more permitted slices available to the first user equipment (UE) during one or more anticipated handovers to one or more cells in the telecommunications network, based at least on a first anticipated trajectory of the first user equipment (UE), wherein the first anticipated trajectory includes the one or more cells; receive a handover indication from the second UE in response to a handover condition for handing over a second UE to a cell of the network apparatus being met, the handover indication indicating that the second UE has selected a permitted slice from the one or more permitted slices of the second UE based on the anticipated trajectory of the second UE; and complete the handover of the second UE to allow the second UE to access telecommunications resources associated with the permitted slice.

[0201] Clause 17. The network device as described in Clause 16, wherein the network device includes a 5G access node or a 6G access node.

[0202] Clause 18. An apparatus in a telecommunications network supported by at least one slice of a source cell, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: receive information identifying one or more permitted slices available to the apparatus during one or more anticipated handovers to one or more next cells, at least based on the apparatus's anticipated trajectory, wherein the anticipated trajectory includes the one or more next cells; receive a first handover trigger indication including information identifying a first permitted slice among the one or more permitted slices available to the apparatus during a first handover to a first cell among the one or more next cells, at least based on the apparatus's anticipated trajectory; adjust the at least one slice to at least one first permitted slice selected from the identified first permitted slice based on the anticipated trajectory; and complete the first handover to the first cell to access telecommunications resources associated with the selected at least one first permitted slice.

[0203] Clause 19. The apparatus according to Clause 18, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: adjust the at least one slice to the selected at least one first allowed slice and complete the first switch in response to the received first switch trigger indication.

[0204] Clause 20. The apparatus according to Clause 18, wherein the received information identifying the one or more permitted slices includes at least one or more permitted slice lists, wherein each of the lists is associated with one of the one or more next cells.

[0205] Clause 21. The apparatus according to Clause 20, wherein each of the one or more allowed slice lists further comprises: a mapping of the at least one slice of the source cell to at least one slice within each of the one or more allowed slice lists.

[0206] Clause 22. The apparatus according to Clause 18, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: select the at least one first allowed slice from the identified first allowed slice.

[0207] Clause 23. The apparatus according to Clause 18, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: store the information identifying the one or more permitted slices available to the apparatus during the one or more anticipated switching periods.

[0208] Clause 24. The apparatus according to Clause 18, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: receive a second handover trigger indication, the second handover trigger indication including information identifying a second allowed slice available to the apparatus during a second handover to a second cell based at least on the apparatus's expected trajectory; adjust the at least one first allowed slice to at least one second allowed slice selected from the identified second allowed slice based on the expected trajectory; and complete the second handover to the second cell to access telecommunications resources associated with the selected at least one second allowed slice.

[0209] Clause 25. A system in a telecommunications network, the system comprising: a first network device including: at least one first processor; and at least one first memory storing instructions that, when executed by the at least one first processor, cause the first network device to: send information identifying one or more permitted slices available to the UE during one or more anticipated handovers to one or more next cells, at least based on a user equipment (UE) anticipated trajectory, wherein the anticipated trajectory includes the one or more next cells; and send a first handover trigger indication including information identifying a first permitted slice available to the UE during a first handover to the first cell, at least based on the UE's anticipated trajectory, wherein the anticipated trajectory includes the first cell, and the first permitted slice is in the one or more permitted slices; and a second network device including: at least one second processor; and at least one second memory storing instructions that, when executed by the at least one second processor, cause the second network device to: receive a first handover indication from the UE, the first handover indication indicating that the UE will use at least one first permitted slice from the one or more permitted slices based on the UE's anticipated trajectory; and complete a first handover in the anticipated handover to the first cell associated with the second network device to access telecommunications resources associated with the at least one first permitted slice.

[0210] Clause 26. The system according to Clause 25, wherein the first network device includes a source access node that served the UE prior to the first handover.

[0211] Clause 27. The system pursuant to Clause 25, wherein the one or more permitted slices identified as being available to the UE during the one or more anticipated handovers comprise one or more permitted slice lists, wherein each of the lists is associated with one or more cells, wherein the first cell is among the one or more cells.

[0212] Clause 28. The system according to Clause 27, wherein each of the one or more allowed slice lists further comprises: a mapping of at least one slice of the source cell to at least one slice within each of the one or more allowed slice lists.

[0213] Clause 29. The system according to Clause 25, wherein the at least one second processor further executes stored instructions from the at least one second memory to cause the second network device to: send a second handover trigger indication message to the UE, wherein the second handover trigger indication includes an identifier of a second allowed slice available to the UE during a second handover to a second next cell based at least on the UE's expected trajectory, wherein the expected trajectory includes the second next cell, the system further comprising a third network device in the second next cell, the third network device comprising: at least one third processor; and at least one third memory storing instructions that, when executed by the at least one third processor, cause the third network device to: receive a second handover indication from the UE, the second handover indication indicating that the UE will use at least one second allowed slice from the one or more allowed slices based on the UE's expected trajectory; and complete the second handover in the expected handover to the second next cell associated with the third network device to access telecommunications resources associated with the at least one second allowed slice.

[0214] Clause 30. The system pursuant to Clause 29, wherein the second handover indication further includes an indication that the UE has updated its list of allowed slices.

[0215] Clause 31. The system according to Clause 30, wherein each of the first network device, the second network device and the third network device includes a 5G access node or a 6G access node.

[0216] Clause 32. A network apparatus in a cell of a telecommunications network, comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the network apparatus to: transmit information based at least on a first expected trajectory of a first user equipment (UE) identifying one or more permitted slices available to the UE during one or more expected handovers to one or more cells in the telecommunications network, wherein the first expected trajectory includes the one or more cells; and transmit a first handover trigger indication, the first handover trigger indication including information based at least on the first expected trajectory of the first UE identifying a first permitted slice available to the first UE during a first handover to a first next cell, wherein the first expected trajectory includes the first permitted slice of the first UE. A first next cell, and the first allowed slice is among the one or more allowed slices; sending a second handover trigger indication, the second handover trigger indication including information identifying different allowed slices available to the second UE during handover to a subsequent next cell based at least on a second expected trajectory of the second UE, wherein the second expected trajectory includes the subsequent next cell; receiving a handover indication from the second UE, the handover indication indicating that slice remapping has been performed by the second UE and the second UE has updated and stored the different allowed slices; and completing the handover of the second UE to allow the second UE to access telecommunications resources associated with at least one of the different allowed slices selected by the second UE.

[0217] Clause 33. The network device as described in Clause 32, wherein the network device includes a 5G access node or a 6G access node.

[0218] Clause 34. The network apparatus according to Clause 32, wherein the at least one processor executes stored instructions from the at least one memory to cause the network apparatus to: send a message to a network element within the telecommunications network, the message indicating that the second UE has completed slice remapping and has updated and stored the different permitted slices.

Claims

1. An apparatus in a telecommunications network associated with at least one slice of a source cell, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to: Receive information that identifies one or more permitted slices available to the device during one or more anticipated handovers to one or more next cells, based at least on the device’s anticipated trajectory, wherein the anticipated trajectory includes the one or more next cells; Based on the expected trajectory, the at least one slice is adjusted to at least one first allowed slice among the identified one or more allowed slices; as well as Complete a first handover to a first next cell in one or more of the multiple anticipated handovers to access telecommunications resources associated with the at least one first permitted slice.

2. The apparatus of claim 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: adjust the at least one slice and complete the first switch in response to a first switching condition being met.

3. The apparatus of claim 1, wherein the received information includes at least one or more allowed slice lists, wherein each of the lists is associated with one of the one or more next cells.

4. The apparatus of claim 3, wherein each of the one or more allowed slice lists further includes a mapping of the at least one slice of the source cell to at least one slice within each of the one or more allowed slice lists.

5. The apparatus of claim 3, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: select the at least one first allowed slice from a first allowed slice list of the one or more allowed slice lists, the first allowed slice list being associated with the first next cell.

6. The apparatus of claim 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: store the received information in the at least one memory, the information identifying one or more permitted slices available to the apparatus during the one or more anticipated handovers to the one or more next cells based on the anticipated trajectory; and, upon completion of the first handover, retain the received information identifying the one or more permitted slices in the at least one memory.

7. The apparatus of claim 1, wherein the at least one processor further executes stored instructions from the at least one memory to cause the apparatus to: In response to the second switching condition being met, based on the expected trajectory, the at least one slice is adjusted to at least one second allowed slice among the identified one or more allowed slices; and In response to the second handover condition being met, a second handover is completed to the second next cell in one or more of the plurality of anticipated handovers to access telecommunications resources associated with the at least one second permitted slice.

8. A system in a telecommunications network, the system comprising: The first network device includes: At least one first processor; and At least one first memory storing instructions that, when executed by the at least one first processor, cause the first network device to: Send information to identify one or more permitted slices available to the UE during one or more anticipated handovers to one or more cells in the telecommunications network, based at least on the anticipated trajectory of the user equipment (UE) in the telecommunications network, wherein the anticipated trajectory includes the one or more cells; The second network device includes: At least one second processor; and At least one second memory storing instructions that, when executed by the at least one second processor, cause the second network device to: In response to the satisfaction of a first handover condition for handing the UE to a first next cell, a first handover indication is received, the first handover indication indicating that the UE will use at least one first allowed slice of the one or more allowed slices based on the UE's expected trajectory; and Complete the first handover to the first next cell in the expected handover to allow the UE to access telecommunications resources associated with the at least one first permitted slice.

9. The system of claim 8, wherein the first network device includes a source access node currently supporting the UE.

10. The system of claim 8, wherein the first handover indication further includes an indication that the UE has updated its allowed slice list and has adjusted at least one current slice to the at least one first allowed slice.

Images