Remapped network slices to support service continuity

Abstract

Methods, systems and devices related to digital wireless communications, and more particularly, to technologies related to: sending a first message including information for handling access and mobility management tasks associated with a mobile device by a first network node to a second network node, wherein the first network node serves the mobile device in a coverage area of ​​the first network node; and determining, at the first network node, information of one or more resources available to the mobile device from the second network node based on a response message from the second network node, in a case where the one or more resources can be remapped from the first network node.

Description

Technical Field

[0001] This patent document relates generally to wireless communications. Background Art

[0002] The rapid development of mobile communications has penetrated into people's work, social life, and all aspects of life, and has brought great impacts on people's lifestyles, work methods, social politics, economy, and other aspects. Human society has entered the information age, and the demand for business applications in all aspects is showing explosive growth. In the future, mobile networks will not only provide communication between people, but also provide services for massive devices in the Internet of Things. For example, virtual reality, high-definition video, and services that require ultra-high-speed services can reach speeds 10 to 100 times the current speed; such as the Internet of Vehicles and other services that require low-latency services, the end-to-end latency can be reduced to one-fifth; the Internet can access 1,000 times the current number of services, and the battery life can be extended to 10 times the current level.

[0003] Differentiated business models and service requirements bring huge challenges to future wireless mobile broadband systems in terms of frequency, technology and operation. Traditional communication networks (i.e., community access networks (RAN) + core CORE) are increasingly unable to meet all scenarios. Building a dedicated network for each scenario will cause a lot of resource waste, which is not practical.

[0004] The development of Network Function Virtualization (NFV) technology allows operators to build different virtual networks for different business needs. Network slicing is based on common physical infrastructure to logically define and divide the network to form an end-to-end virtual network. Each virtual network has different functions and characteristics to dynamically meet various needs and business models.

[0005] A typical network slice includes a collection of virtualized access network functions and core network functions. Network slices are constructed by operators based on demand and policy, and the functions included in the network slices are also determined by operators based on demand and policy. For example, some network slices may include a dedicated forwarding plane in addition to the control plane functions, while some network slices may only include some basic control plane functions. Summary of the invention

[0006] Methods, systems, and devices related to digital wireless communications are disclosed herein, and more particularly, techniques related to reselecting a network in a network sharing split architecture are disclosed.

[0007] In one exemplary aspect, a method for wireless communication includes: sending, by a first network node, to a second network node, a first message including information for handling access and mobility management tasks associated with a mobile device, wherein the first network node serves the mobile device in a coverage area of ​​the first network node; and determining, at the first network node, information of one or more resources from the second network node that are available to the mobile device based on a response message from the second network node, if the one or more resources are remappable from the first network node.

[0008] In another exemplary aspect, a method for wireless communication includes: receiving, at a second network node, a configuration exchange message including information about slice resources for a mobile device served by the first network node that is supported by a coverage area of ​​the first network node, wherein in a case where one or more resources can be remapped from the first network node to the second network node, the information about the slice resources is used for switching of the mobile device based on the configuration exchange message.

[0009] In another exemplary aspect, a method for wireless communication includes sending, by a first network node to a second network node, a handover request for handover of a mobile device, wherein the handover request results in a remapping of resources from the first network node that originally served the mobile device in a coverage area of ​​the first network node to the second network node.

[0010] In another exemplary aspect, a method for wireless communication includes: determining, at a second network node, a remapping of resources from the first network node to the second network node when a mobile device in a coverage area supported by the first network node ceases to be supported by the first network node; and sending, to the first network node, an acknowledgment of a handover request associated with handing over the mobile device from the first network node to the second network node.

[0011] In another exemplary aspect, a method for wireless communication includes: receiving, at a second network node, a handover request associated with handing over a service to a mobile device in a coverage area supported by a first network node, wherein the handover request includes information for selecting allowed network resources to provide the service to the mobile device; and selecting, at a target network node, one or more network resources based on the information for selecting the allowed network resources.

[0012] In another exemplary aspect, a wireless communication device including a processor is disclosed. The processor is configured to implement the methods described herein.

[0013] In yet another exemplary aspect, the various techniques described herein may be embodied as processor-executable code stored on a computer-readable program medium.

[0014] The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a schematic diagram of the 5G architecture illustrating issues associated with continuity of service.

[0016] Figure 2A is a signaling procedure for supporting continuity of service according to an example embodiment.

[0017] Figure 2B is a signaling procedure for supporting continuity of service according to an example embodiment.

[0018] Figure 3 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0019] Figure 4 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0020] Figure 5A is a signaling procedure for supporting continuity of service according to an example embodiment.

[0021] Figure 5B is a signaling procedure for supporting continuity of service according to an example embodiment.

[0022] Fig. 6A is a signaling procedure for supporting continuity of service according to an example embodiment.

[0023] Figure 6B is a signaling procedure for supporting continuity of service according to an example embodiment.

[0024] Figure 7 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0025] Figure 8 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0026] Fig. 9 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0027] Fig.10 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0028] Fig.11 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0029] Fig.12 is a signaling procedure for supporting continuity of service according to an example embodiment.

[0030] Fig.13 An example of a wireless communication system in which the technology according to one or more embodiments of the present technology can be applied is shown.

[0031] Fig.14 A block diagram representation of a portion of a hardware platform.

[0032] Fig.15 A flow chart illustrating an example method for supporting continuity of service.

[0033] Fig.16 A flow chart illustrating an example method for supporting continuity of service.

[0034] Fig.17 A flow chart illustrating an example method for supporting continuity of service.

[0035] Fig.18 A flow chart illustrating an example method for supporting continuity of service.

[0036] Fig.19 A flow chart illustrating an example method for supporting continuity of service. DETAILED DESCRIPTION

[0037] The section headings used in this document are for ease of understanding only and do not limit the scope of the embodiments to the sections in which they are described. In addition, although the embodiments are described with reference to 5G examples, the disclosed techniques may be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0038] The development of a new generation of wireless communications - 5G New Radio (NR) communications - is part of the continuous mobile broadband evolution process to meet the growing network needs. NR will provide greater throughput to allow more users to be connected simultaneously. Other aspects such as energy consumption, equipment cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios.

[0039] Overview

[0040] In current network deployment designs, the availability of some network slices may be limited to only a portion of the network. This means that service continuity may not be guaranteed in certain deployment scenarios.

[0041] Figure 1 is a schematic diagram of the 5G architecture, illustrating issues associated with service continuity. Figure 1As shown, different network slices can be deployed in different RAN nodes (or referred to as base stations in this article). Based on the SLA (Service level agreement), the mobile network operator (MNO) provides different network slices to RAN node 1 and RAN node 3. (As used in this article, a network slice is defined as an end-to-end logical communication network within a public land mobile network (PLMN), and includes a core network (CN) control plane, user plane network functions, and a 5G access network (AN)). For example, RAN node 1 can access network slice 1 and network slice 2, and is connected to the core network (CN). However, RAN node 3 can only access network slice 2. Network slice 1 is not supported or provided to RAN node 2. This Figure 1 Further, as Figure 1 As shown, network slice 1 and network slice 2 are isolated from each other. This indicates that the resources in the slice are only directed to the UE served by the slice. For example, the UE's protocol data unit (PDU) session (shown using dotted lines) utilizes the resources provided by network slice 1, and the UE's PDU session is not allowed to use the resources of network slice 2. The UE accesses the wireless network via RAN node 1 as its access point. The UE requests a PDU session to provide data transmission services. The PDU session request message is sent from the UE to the core network (CN) node. As shown in FIG. Figure 1 As shown, CN selects network slice 1 to provide network-side resources for the UE's PDU session.

[0042] In addition, if Figure 1 As shown, the UE may be mobile and move from a cell in RAN node 1 to a cell in RAN node 2. In this scenario, since RAN node 2 does not support slice 1, service continuity is not guaranteed, and therefore based on conventional technical design, the UE's PDU session will be terminated. Figure 1 It is shown as a circled cross symbol.

[0043] In another hypothetical scenario, a PDU session of the UE is established using slice 2 via RAN node 2. When the UE moves to a cell in RAN node 3, it is possible that there is a shortage of resources in slice 2 in RAN node 2. In this case, because slice 2 lacks resources to support the UE's PDU session, the UE's PDU session is terminated. Continuity of service by RAN node 2 is not guaranteed.

[0044] Therefore, it is necessary to alleviate the aforementioned problem of service discontinuity. In some embodiments, Figure 1 The schematic diagram in may represent the 5G structure specified by the 3GPP TS 38.300 protocol. The structure may include a 5G core network (5GC or 5G core) and a 5G access network. The 5G core network may include network elements related to an access and mobility management unit (AMF), a user plane function (UPF), and a 5G access network, and the 5G access network may include network elements 5G enhanced eNB base stations (ng-eNB) or 5G base stations (gNB). The interface between the network elements of the core network and the network elements of the access network may include an NG interface, and the interface between the network elements of the access network may include an Xn interface. The RAN node may be a gNB (5G base station) that provides new radio (NR) user plane and control plane services. As another example, the RAN node may be an enhanced 4G eNodeB that is connected to the 5G core network via an NG interface, but still uses one or more 4G LTE air interfaces to communicate with the 5G UE.

[0045] Example Embodiments

[0046] Embodiments of the present technology are directed to providing service continuity to user equipment (UE) through slice remapping. Slices in 5G networks are associated with slice IDs. While conventional RAN slices are limited to mapping a slice ID once to a RAN configuration rule, slice remapping allows for resource reuse by reusing the slice ID multiple times, such as each mapping allowing the slice ID to be used for different RAN rules.

[0047] The embodiments herein are applicable to a mobile environment in which a UE leaves the coverage area of ​​a mobile operator but receives continuous or uninterrupted service in the new area. These embodiments may also be applicable to scenarios in which a base station and / or core network has sufficient resources to deploy, but the resources cannot be used due to a shortage of resources or the resources belong to different slices or slices.

[0048] In order to provide continuous or uninterrupted service, the source base station and / or the target base station first identifies the mobility scenario. Embodiments of the present technology are directed to identifying the mobility scenario based on one or more of the following information attributes (e.g., discussed in Example Embodiments 1 to 4):

[0049] a. Information indicating whether the source base station and the target base station belong to the same access and mobility management function (AMF) or AMF set. The AMF or AMF set may include capability information for handling connection and mobility management tasks associated with a UE electronically coupled to the source base station and / or the target base station (embodiment 1).

[0050] b. Information identifying a list of slices supported by the coverage area of ​​the target base station (Embodiment 2)

[0051] c. Information indicating whether the target base station supports the RAN slice remapping function (Example 3)

[0052] d. Information indicating whether the core network supports the RAN slice remapping function (Example 4)

[0053] After the base station identifies the mobile scenario, another problem that needs to be solved is that the source base station determines the method for supporting slice remapping. For example, the method for supporting slice remapping by the source base station is different from the method for supporting slice remapping by the core network. Embodiments of the present technology are directed to several methods for supporting slice remapping (for example, discussed in example embodiments 5 to 8):

[0054] Method 1: Slice remapping by the core network (Example 5)

[0055] The source base station sends a slice remapping request to the core network, and the core network performs slice remapping on the UE's service and notifies the source base station of the result. The source base station switches the UE to the target base station.

[0056] Method 2: Slice remapping performed by both the target base station and the core network (Example 6)

[0057] The source base station sends a handover request message to the target base station, the target base station performs RAN slice remapping, the target base station sends a slice remapping request to the core network, and the core network performs RAN slice remapping and sends a response message to the target base station. The target base station sends a handover request confirmation message to the source base station to complete the handover.

[0058] Method 3: Slice remapping by the target base station (Embodiment 7)

[0059] The source base station sends a handover request message to the target base station, the target base station performs RAN slice remapping, and the target base station sends a handover request confirmation message to the source base station to complete the handover.

[0060] Further, Embodiment 8 discloses a method for a target base station to select a slice to remap a slice, the method comprising: (i) a source base station sends a message carrying a list of allowed network slice selection assistance information (NSSAI) of the UE to a target base station, and (ii) the target base station selects a remapped slice for the UE based on the allowed NSSAI list.

[0061] Furthermore, Example Embodiments 9 to 13 illustrate how to use 3GPP NR technology to achieve service continuity.

[0062] Example 1

[0063] When an interface between base stations is available, the AMF Set information can be sent directly from one base station to another during the connection establishment process. An example of this scenario utilizes Figure 2A The step-by-step signaling process shown in FIG.

[0064] Step 1: When the interface between base stations is established, the source base station sends AMF set information. Figure 2A As shown in the left figure in , when the base station establishes an interface between base stations (for example, during the Xn establishment process), the base station sends the AMF set information supported by the base station to another base station. The AMF set is an identifier of the AMF associated with the base station. All slices supported by the AMF in the AMF set are consistent. For example, all network slices in the AMF set are the same. In some embodiments, the AMF set can be a list of AMF sets.

[0065] An AMF set consists of a collection of AMFs that serve a given area and network slice.

[0066] Or multiple network slices define multiple AMF sets.

[0067] Step 2: The receiving base station sends the home AMF set information to the source base station in a response message. The home AMF set information is the AMF set associated with the receiving base station. The AMF set information of the source base station and the receiving base station can be the same or different.

[0068] As a result of this signaling, the source base station determines whether one or more resources are available to the UE if the UE is to be served by the receiving base station. In some embodiments, determining whether one or more resources are available to the UE includes determining whether the source base station and the target / receiving base station belong to the same AF or AMF set.

[0069] Example 1.1

[0070] In the case where the AMF set information of the source base station is updated, the source base station can send the updated AMF set information during the interface modification process. Figure 2B The step-by-step signaling process shown in FIG.

[0071] Initially, when the interface is established, the base station sends AMF set information. For example, this step can be similar to step 1 discussed in embodiment 1.

[0072] Step 1: If Figure 2B As shown, when the connection between a base station and an AMF set changes, the base station sends an updated AMF set to a receiving base station using a modification procedure such as a NG-RAN NODE CONFIGURATION UPDATE procedure.

[0073] Step 2: The receiving base station sends the updated AMF set information to the source base station in a response message.

[0074] As a result of this signaling, the source base station determines whether one or more resources are available to the UE if the UE is to be served by the receiving base station. In some embodiments, determining whether one or more resources are available to the UE includes determining whether the source base station and the target / receiving base station belong to the same AF or AMF set.

[0075] Example 1.2

[0076] When there is no direct interface between base stations, the core network can be used as an intermediary to send AMF set information to the receiving base station. An example of this situation is to use Figure 3 The step-by-step signaling process shown in FIG.

[0077] Step 1: The base station sends AMF set information (associated with the base station) to the core network element. Figure 3 As shown, the base station sends the associated AMF set information to the core network using a configuration exchange message between base stations. For example, as part of the configuration transfer message process, the AMF set information of the source base station can be included in the UPLINK RAN CONFIGURATION TRANSFER message.

[0078] Step 2: The core network element relays or transmits the AMF set information of the source base station to the receiving base station. Figure 3 As shown, the base station sends the relevant AMF set information to the receiving base station using the configuration exchange message between base stations. For example, as part of the configuration transfer message process, the AMF set information of the source base station can be included in the DOWNLINK RAN CONFIGURATION TRANSFER message.

[0079] As a result of this signaling, the source base station determines the resource information available to the UE in the event that the UE will be served by the receiving base station. For example, the resource information may indicate whether the source base station and the target / receiving base station belong to the same AMF or AMF set.

[0080] Example 1.3

[0081] When there is no direct interface between base stations, the AMF set information of the source base station can be sent to the receiving base station through the core network during the handover process.

[0082] Step 1: The source base station sends a handover request message and sends the relevant AMF set information to the core network element. For example, the base station can use the handover required message to carry the AMF set (associated with the source base station) to the target base station.

[0083] Step 2: The core network element sends the AMF set information of the source base station to the target base station.

[0084] As a result of this signaling, the source base station determines information about resources available to the UE if the UE will be served by the receiving base station. In some embodiments, the information about resources may include determining whether the source base station and the target / receiving base station belong to the same AMF or AMF set.

[0085] Example 2

[0086] The slice information supported by the tracking area (TA) of the base station (e.g., the source base station and / or the target base station) can be used to determine whether the handover belongs to the intra-registration area type or the inter-registration area type. However, in the case where a direct interface between base stations is not available, the source base station cannot obtain the slice information supported by the target base station, and vice versa. To solve this problem, the source base station and the target base station can use the core network element to exchange the slice information supported by the TA. An example of this situation utilizes Figure 4 The step-by-step signaling process shown in FIG.

[0087] Step 1: The source base station sends the slice information supported by the TA to the core network element. Figure 4 As shown, the source base station uses the inter-base station configuration exchange message to send the slice information supported by the TA to the core network element. (For example, the slice information supported by the TA can be included in the UPLINK RAN CONFIGURATION TRANSFER message in the configuration transfer message process).

[0088] Step 2: The core network element relays or transmits the slice information supported by the source base station TA to the receiving base station. Figure 4 As shown, the core network uses the inter-base station configuration exchange message to send the slice information supported by the TA to the receiving base station. (For example, the slice information supported by the TA can be included in the DOWNLINK RANCONFIGURATION TRANSFER message in the configuration transfer message process from the core network to the receiving base station).

[0089] As a result of this signaling, the target base station can determine whether the handover is of an intra-registration area type or an inter-registration area type.

[0090] Example 3

[0091] In some embodiments, the base station may support RAN-side slice remapping functionality, which enables efficient use of physical network resources. For example, the base station may use the RAN slice remapping indicator field to indicate whether the base station supports the RAN-side slice remapping functionality. The RAN slice remapping indicator information may include one or more fields based on the following information attributes:

[0092] 1: Instruct the base station to support the slice remapping function

[0093] 2: Indicates the list of slices supported by the base station TA that can be remapped slices

[0094] 3: Instruct the source base station to send the list of allowed network slice selection assistance information (NSSAI) of the user equipment (UE)

[0095] 4: Instruct the base station to support the slice list through pre-configuration of remapping. (For example, the source base station can directly switch the UE to the target without relying on remapping information assistance, such as the UE's allowed NSSAI list. Instead, the source base station can use a pre-configured table stored in the source base station. The pre-configured table may include details of how the slices are mapped, and which other one or more slices are mapped to a given slice).

[0096] 5: Indicates that the slice resources supported by the base station TA are insufficient

[0097] use Figure 5A and Figure 5B The step-by-step signaling process shown in the figure illustrates an example of a case where the base station supports the slice remapping function on the RAN side.

[0098] Step 1: When a connection interface is established or modified, the source base station sends its associated RAN slice remapping indicator. Figure 5A As shown, when the interface between base stations is established (e.g., during the Xn establishment process), the source base station sends RAN slice remapping indicator information.

[0099] Step 2: The receiving base station sends RAN slice remapping indicator information in a response message, such as Figure 5A shown.

[0100] like Figure 5B As shown, when the AMF set of a base station changes, the changed base station uses a modification procedure (such as AMFCONFIGURATION UPDATE) to send updated RAN slice remapping indicator information. In response, the receiving base station sends the updated RAN slice remapping indicator information to the source base station in a response message.

[0101] As a result of this signaling, the source base station can determine resource information indicating whether the target base station supports the RAN side slice remapping function.

[0102] Example 4

[0103] In some embodiments, the core network may support slice remapping functionality. The base station may not know whether the core network supports slice remapping functionality. An example of this situation is to use Fig. 6A and Figure 6B The step-by-step signaling process shown in FIG.

[0104] Step 1: The base station initiates the establishment of the interface between the base station and the core network. Fig. 6A As shown, the base station initiates the establishment of the NG interface. For example, the source base station can request the slice remapping indicator information of the core network in the NG interface establishment message.

[0105] Step 2: The core network element sends a response message with slice remapping indicator information.

[0106] In the scenario, when the slice remapping indication information of the core network changes or is modified, the updated slice remapping indication is included in the interface modification process (for example, in Figure 6B In response, the base station sends an AMF CONFIGURATION UPDATE ACKNOWLEDGE message, such as Figure 6B shown.

[0107] In some embodiments, the slice remap indicator information includes at least one of the following attributes:

[0108] 1: The core network supports slice remapping instructions

[0109] 2: Indication of a list of slices supported by the core network that can be used for slice remapping.

[0110] As a result of this signaling, the source base station can determine resource information indicating whether the core network supports the RAN side slice remapping function.

[0111] Example 5

[0112] In some embodiments, the source base station performs the handover after the slice remapping is performed by the core network. Figure 7 The step-by-step signaling process shown in FIG.

[0113] Step 1: The source base station identifies the mobility scenario (eg, using the methods discussed in Embodiments 1 to 4). For example, the source base station determines whether the service (eg, PDU session) of the served UE can be handed over to the target base station.

[0114] Step 2: The source base station sends a slice remapping request (e.g., including UE ID, PDU session ID) to the core network to perform slice remapping for the UE. For example, the slice remapping request message can be part of the PDU session resource modification indication message of the NG interface.

[0115] Step 3: The core network performs slice remapping for the services of the UE.

[0116] Step 4. The core network notifies the source base station of the result of the slice remapping, which includes the mapped slice ID. After receiving the response message from the core network, the source base station updates the slice information served by the UE.

[0117] Step 5: The source base station switches the UE to the target base station (eg, a handover process). Further, the handover process may include a handover request and a handover confirmation step.

[0118] Example 6

[0119] In some embodiments, the target base station and the core network perform slice remapping. An example of this scenario utilizes Figure 8 The step-by-step signaling process shown in FIG.

[0120] Step 1: The source base station identifies the mobility scenario (eg, using the methods discussed in Embodiments 1 to 4). For example, the source base station determines whether the service (eg, PDU session) of the served UE can be handed over to the target base station.

[0121] Step 2: The source base station sends a handover request message to the target base station.

[0122] Step 3: The target base station performs RAN slice remapping (eg, using the methods discussed in Embodiments 1 to 4). For example, the target base station selects an appropriate slice for remapping (eg, as disclosed in Embodiment 8).

[0123] Step 4: The target base station sends a slice remapping request (eg, including UE ID, PDU session ID, mapped slice ID) to the core network. The mapped slice ID corresponds to the slice selected by the target base station.

[0124] Step 5: The core network performs slice remapping. For example, the slice remapping of the core network is used to verify that the slice selected by the target base station (e.g., the mapped slice ID) is a suitable slice for the UE's handover. For example, the verification may include determining that the mapped slice ID is appropriate from the perspective of the core network, and accordingly changing the UE's service (e.g., PDU session ID) to the mapped slice ID selected by the target base station.

[0125] Step 6: Based on the verification, the core network sends a response message to the target base station confirming the slice selected by the target base station.

[0126] Step 7: Upon receiving the response message from the core network, the target base station sends a handover request confirmation message to the source base station to complete the handover.

[0127] Example 7

[0128] In some embodiments, the target base station performs slice remapping. An example of this scenario utilizes Fig. 9 The step-by-step signaling process shown in FIG.

[0129] Step 1: The source base station identifies the mobility scenario (eg, using the methods discussed in Embodiments 1 to 4). For example, the source base station determines whether the service (eg, PDU session) of the served UE can be handed over to the target base station.

[0130] Step 2: The source base station sends a handover request message to the target base station.

[0131] Step 3: The target base station performs RAN slice remapping. The target base station determines that RAN slice remapping needs to be performed (e.g., as discussed in Embodiments 1 to 4). For example, the target base station selects an appropriate slice for remapping (e.g., as disclosed in Embodiment 8).

[0132] Step 4: The target base station sends a handover request confirmation message to the source base station to complete the handover.

[0133] Example 8

[0134] In some embodiments, the target base station selects one or more remapped slices for the UE. An example of this scenario utilizes Fig.10 The step-by-step signaling process shown in FIG.

[0135] Step 1: The source base station sends a message carrying the UE's allowed NSSAI parameter list to the target base station. For example, the UE's allowed NSSAI list may be included in a handover request message. The message is forwarded to the target base station via the core network. The allowed NSSAI list may include parameters indicating a slice type and a slice distinguisher (which distinguishes between slices of the same type). The UE / core network may initially provide the allowed NSSAI list to the source base station.

[0136] Step 2: The target base station selects a remapped slice for the UE based on the allowed NSSAI list and information identifying the mobility scenario of the UE (e.g., using the methods discussed in Embodiments 1 to 4).

[0137] Step 3: The target base station selects a suitable slice as the remapped slice served by the UE based on the obtained information (for example, using the methods discussed in Examples 1 to 4) and in combination with the allowed NSSAI list supported by the UE.

[0138] Therefore, after slice remapping is performed by the target base station, a UE handover from the source base station to the target base station occurs. The target base station performs slice selection based on the UE's allowed NSSAI list and mobility scenario information.

[0139] Example Embodiment 8.1

[0140] In some embodiments, the target base station selects one or more remapped slices for the UE, and the core network is not involved in signaling resulting in the handover of the UE. Fig.11 The step-by-step signaling process shown in FIG.

[0141] Step 1: The source base station sends a message carrying the allowed NSSAI list (eg, a list of parameters) of the UE to the target base station. For example, the allowed NSSAI list may be included in a handover request message.

[0142] Step 2: The target base station selects a remapped slice for the UE. For example, the target base station selects a suitable slice as the remapped slice for the UE in combination with the allowed NSSAI list supported by the UE (eg, using the methods described in Embodiments 1 to 4).

[0143] Step 3: The target base station sends a response message to the source base station, for example, a handover request confirmation message.

[0144] Example Embodiment 9

[0145] When the mobility scenario corresponds to a registration area scenario, the source and target base stations can use Xn-based handover, and the core network also supports slice remapping. Fig.12The step-by-step signaling process shown in FIG.

[0146] Step 1: The source base station uses the slice remapping function to identify the mobile scenario. For example, if the TA used by the source base station and the target base station is consistent through the measurement report of the UE, the source base station determines that this switch belongs to the scenario within the registration area. The source base station decides to use Xn-based switching (for example, as discussed in Example 3). For example, the source base station may determine (for example, based on the method discussed in Example 3) that the slice (for example, slice 1) currently used by the UE for service is in a state of insufficient resources in the target base station. Further, the source base station may determine (for example, based on the method discussed in Example 4) that the core network supports the slice remapping function and may support the remapping of the slice currently used by the UE.

[0147] Step 2: In order to request the core network to perform slice remapping for the UE, the source base station may determine to support the slice remapping method discussed in Embodiment 5. For example, the source base station sends a PDU session resource modification indication request to the core network to perform slice remapping for the UE.

[0148] Step 3: The core network performs slice remapping for the UE's service and notifies the source base station of the result of the remapping. After receiving the PDU session resource modification confirmation message, the source base station updates the UE service slice on the source base station. For example, the message may indicate that the UE service slice 1 with insufficient resources will be updated to slice 2.

[0149] Step 4: The source base station switches the UE to the target base station to ensure service continuity. For example, at the target base station, slice 1 is insufficient in resources, but slice 2 has sufficient resources.

[0150] Example 10

[0151] When the mobility scenario corresponds to a scenario within the registration area, the source base station and the target base station use Xn-based switching, and both the core network and the target base station support the slice remapping function.

[0152] Step 1: The source base station uses the slice remapping function to identify the mobile scenario. For example, if the TA used by the source base station and the target base station is consistent through the measurement report of the UE, the source base station determines that this handover belongs to the scenario within the registration area. The source base station decides to use Xn-based handover (for example, as discussed in Example 3). For example, the source base station may determine (for example, based on the method discussed in Example 3) that the current service usage slice (for example, slice 1) of the UE is in a state of insufficient resources in the target base station. As a result, the source base station may determine that the target base station needs the UE's allowed S-NSSAI list information. Further, the source base station may determine (for example, based on the method discussed in Example 6) that the target base station supports the slice remapping function and may support the remapping of the slice currently used by the UE.

[0153] Step 2: The source base station sends a handover request message to the target base station. The message may include the allowed S-NSSAI list information of the UE.

[0154] Step 3: The target base station performs RAN slice remapping. As a result, the target base station determines that the mobility scenario corresponds to a type handover within a registration area (e.g., based on the method discussed in Example 1). In addition, the target base station determines that the slice resources of the target base station are insufficient. Therefore, the target base station selects (e.g., based on the method discussed in Example 8) a suitable slice for remapping. Further, the target base station may determine (e.g., based on the method discussed in Example 4) that the core network element supports slice remapping. For example, the target base station may determine that a slice list from the core network and the allowed S-NSSAI list information of the UE have one or more common slices. (The target base station may determine / obtain a slice list from the core network based on its connection to the core network). Further, the target base station may select a slice from one or more common slices in a slice list from the core network and the allowed S-NSSAI list information of the UE.

[0155] Step 4: The target base station sends a slice remapping request to the core network. In some implementations, the message may be a path switch message of the NG interface, and the message may include remapped slice information (from one or more public slices) selected by the target base station.

[0156] Step 5: The core network element performs slice remapping and sends a response message to the target base station. The message may be a path switching confirmation message of the NG interface.

[0157] Step 6: The target base station sends a handover request confirmation message to the source base station to complete the handover.

[0158] Example Embodiment 11

[0159] When the mobility scenario corresponds to a scenario within the registration area, the source base station and the target base station use Xn-based switching, and the slice remapping function is supported by the target base station.

[0160] Step 1: The source base station uses the slice remapping function to identify the mobile scenario. For example, if the TA used by the source base station and the target base station is consistent through the measurement report of the UE, the source base station determines that this switch belongs to the scenario within the registration area. The source base station decides to use Xn-based switching (for example, as discussed in Example 3). For example, the source base station may determine (for example, based on the method discussed in Example 3) that the current service usage slice (for example, slice 1) of the UE is in a state of insufficient resources in the target base station. As a result, the source base station may determine that the target base station needs the UE's allowed S-NSSAI list information. Further, the source base station may determine (for example, based on the method discussed in Example 3) that the target base station supports the slice remapping function and may support the remapping of the slice currently used by the UE.

[0161] Step 2: The source base station sends a handover request message to the target base station. The message may include the allowed S-NSSAI list information of the UE.

[0162] Step 3: The target base station performs RAN slice remapping. As a result, the target base station determines that the mobility scenario corresponds to a registration area type handover (e.g., based on the method discussed in Example 1). In addition, the target base station determines that the slice resources of the target base station are insufficient. The target base station cannot determine whether the core network supports slice remapping or lacks resources to support slice remapping. Therefore, the target base station selects (e.g., based on the method discussed in Example 8) a suitable slice with sufficient resources for remapping.

[0163] Step 4: The target base station sends a handover request confirmation message to the source base station to complete the handover.

[0164] Example Embodiment 12

[0165] When the mobility scenario corresponds to a scenario within the registration area, the source base station and the target base station use NG-based switching, and the slice remapping function is supported by the target base station.

[0166] Step 1: The source base station uses the slice remapping function to identify the mobile scenario. For example, if the TA used by the source base station and the target base station is consistent through the measurement report of the UE, the source base station determines that this handover belongs to the scenario within the registration area. The source base station decides to use NG-based handover based on 3GPP technology. The source base station can determine that the target base station requires the UE's allowed S-NSSAI list information (for example, based on the method discussed in Example 3). Further, the source base station can determine (for example, based on the method discussed in Example 7) that the target base station supports the slice remapping function and can support the remapping of the slice currently used by the UE.

[0167] Step 2: The source base station sends a handover request message to the core network. The message may include the UE's allowed S-NSSAI list information and / or the source base station's AMF set information.

[0168] Step 3: The core network sends a handover request message to the target base station. The message may include the UE's allowed S-NSSAI list information and / or the AMF set information connected to the source base station.

[0169] Step 3: The target base station performs RAN slice remapping. As a result, the target base station determines that the mobility scenario corresponds to a type handover within the registration area (e.g., based on the method discussed in Example 1). In addition, the target base station determines that the slice resources of the target base station are insufficient. The target base station cannot determine whether the core network supports slice remapping or lacks resources to support slice remapping. Therefore, the target base station selects (e.g., based on the method discussed in Example 8) a suitable slice with suitable resources for remapping.

[0170] Step 4: The target base station sends a handover request confirmation message to the core network.

[0171] Step 5: The core network sends a handover request confirmation message to the source base station to complete the handover.

[0172] Example 13

[0173] When the mobility scenario corresponds to an inter-registration area scenario, the source base station and the target base station use Xn-based switching, and the slice remapping function is supported by the target base station.

[0174] Step 1: The source base station uses the slice remapping function to identify the mobility scenario. For example, if the TA used by the source base station and the target base station is inconsistent through the measurement report of the UE, the source base station determines that this handover belongs to the inter-registration area scenario. The source base station decides to use Xn-based handover (for example, as discussed in Example 3). For example, the source base station may determine (for example, based on the method discussed in Example 3) that the target base station does not support the current service usage slice (for example, slice 1) of the UE. As a result, the source base station may determine that the target base station requires the UE's allowed S-NSSAI list information.

[0175] Step 2: The source base station sends a handover request message to the target base station. The message may include the allowed S-NSSAI list information of the UE.

[0176] Step 3: The target base station performs RAN slice remapping. As a result, the target base station determines that the mobility scenario corresponds to an inter-registration area type handover (e.g., based on the method discussed in Embodiment 1). Moreover, the target base station determines that it does not support the slices used by the UE service. The target base station cannot determine whether the core network supports slice remapping or lacks resources for supporting slice remapping. Therefore, the target base station selects (e.g., based on the method discussed in Embodiment 8) an appropriate slice for remapping.

[0177] Step 4: The target base station sends a handover request confirmation message to the source base station to complete the handover.

[0178] Step 5: UE initiates the registration update process.

[0179] Example System Implementation

[0180] Fig.13 An example of a wireless communication system in which the technology according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 1300 may include one or more base stations (BS) 1305a, 1305b, one or more wireless devices 1310a, 1310b, 1310c, 1310d, and a core network 1325. The base stations 1305a, 1305b may provide wireless services to the wireless devices 1310a, 1310b, 1310c, and 1310d in one or more wireless sectors. In some embodiments, the base stations 1305a, 1305b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

[0181] The core network 1325 can communicate with one or more base stations 1305a, 1305b. The core network 1325 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1310a, 1310b, 1310c, and 1310d. The first base station 1305a can provide wireless services based on a first wireless access technology, and the second base station 1305b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 1305a and 1305b can be located at the same location or can be installed separately on site. Wireless devices 1310a, 1310b, 1310c, and 1310d can support a variety of different wireless access technologies. In some embodiments, base stations 1305a, 1305b can be configured to implement some of the technologies described in this document. Wireless devices 1310a to 1310d can be configured to implement some of the technologies described in this document.

[0182] In some implementations, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that can be used to connect to different wireless networks.

[0183] Fig.14 1405 is a block diagram representation of a portion of a hardware platform. A hardware platform 1405, such as a network node or base station or wireless device (or UE), may include a processor electronic device 1410, such as a microprocessor that implements one or more of the techniques presented in this document. The hardware platform 1405 may include a transceiver electronic device 1415 to send and / or receive wireless signals through one or more communication interfaces (such as antenna 1420). The hardware platform 1405 may implement other communication interfaces with defined protocols for sending and receiving data. The hardware platform 1405 may include one or more memories (not explicitly shown) configured to store information (such as data and / or instructions). In some embodiments, the processor electronic device 1410 may include at least a portion of the transceiver electronic device 1415. In some embodiments, the hardware platform 1405 is used to implement at least some of the disclosed techniques, modules or functions, central nodes, distributed nodes, terminals, or network nodes.

[0184] From the foregoing, it should be understood that, for the purpose of illustration, specific embodiments of the presently disclosed technology have been described herein, but various modifications may be made without departing from the scope of the invention. Therefore, the presently disclosed technology is not limited except as limited by the appended claims.

[0185] Fig.15A flow chart of an example method for supporting continuity of service is shown. For example, in embodiments 1, 3, and 4 of this document, the steps of this flow chart are discussed with respect to a source base station. At step 1502, the process sends a first message including information for handling access and mobility management tasks associated with a mobile device to a second network node by a first network node, wherein the first network node serves the mobile device in a coverage area of ​​the first network node. At step 1504, the process determines, at the first network node, information of one or more resources available to the mobile device from the second network node based on a response message from the second network node, if the one or more resources are remappable from the first network node.

[0186] Fig.16 A flowchart of an example method for supporting continuity of service is shown. For example, in Embodiment 2 of this document, the steps of this flowchart are discussed for a target base station. In step 1602, the process receives, at a second network node, a configuration exchange message including information of slice resources for a mobile device served by the first network node that are supported by a coverage area of ​​the first network node, wherein the information of the slice resources is used for switching of the mobile device based on the configuration exchange message in the case where one or more resources can be remapped from the first network node to the second network node.

[0187] Fig.17 A flow chart of an example method for supporting continuity of service is shown. For example, in embodiment 7 of this document, the steps of this flow chart are discussed for a source base station. At step 1702, the process includes a first network node sending a handover request to a second network node for handover of a mobile device, wherein the handover request results in a remapping of resources from the first network node that originally served the mobile device in the coverage area of ​​the first network node to the second network node.

[0188] Fig.18 A flow chart of an example method for supporting continuity of service is shown. For example, in Embodiment 7 of this document, the steps of this flow chart are discussed with respect to a target base station. At step 1802, the process determines, at a second network node, a remapping of resources from the first network node to the second network node in the event that a mobile device in a coverage area supported by the first network node stops being supported by the first network node. At step 1804, the process sends to the first network node an acknowledgment of a handover request associated with handing over the mobile device from the first network node to the second network node.

[0189] Fig.19A flow chart of an example method for supporting continuity of service is shown. For example, in embodiment 8 of this document, the steps of this flow chart are discussed with respect to a target base station. At step 1902, the process receives, at a second network node, a handover request associated with handing over a service to a mobile device in a coverage area supported by a first network node, wherein the handover request includes information for selecting an allowed network resource to provide the service to the mobile device. At step 1904, the process, at the target network node, selects one or more network resources based on the information for selecting the allowed network resource.

[0190] Some embodiments of the disclosed technology are presented in a clause-based format.

[0191] A1. A method for wireless communication (eg, Fig.15 ), comprising:

[0192] A first message including information for handling access and mobility management tasks associated with a mobile device is sent by a first network node to a second network node, wherein the first network node serves the mobile device in a coverage area of ​​the first network node; and in a case where one or more resources can be remapped from the first network node, determining at the first network node information of one or more resources from the second network node that are available to the mobile device based on a response message from the second network node.

[0193] A2. A method according to clause A1, wherein information about one or more resources available to a mobile device in a case where the one or more resources are remapped from a first network node includes at least one of the following: information related to access and mobility management function (AMF) functions supported by the first network node and the second network node, information identifying a list of slices supported by a coverage area of ​​the second network node, information indicating whether the second network node supports a RAN slice remapping function, or information indicating whether a core network element electrically coupled to the first network node supports a RAN slice remapping function.

[0194] A3. A method according to clause A1, wherein the first network node and the second network node are Radio Access Network (RAN) nodes.

[0195] A4. The method according to clause A1 further comprises: determining, based on the response message and the first message, whether the first network node and the second network node belong to the same access and mobility management function (AMF) or AMF set.

[0196] A5. A method according to clause A1, wherein the first message is sent via an Xn interface associated with establishment of a connection between the first network node and the second network node.

[0197] A6. A method according to clause A2, wherein the slice remapping functionality includes one or more of the following instructions: instructions to a network node to support remapping of network slices, a list of network slices supported by the network node that can be used for remapping, instructions to a network node to send allowed network slice selection assistance information (NSSAI) to a mobile device, instructions to a network node to support network slices through pre-configuration of remapping, or an indication of insufficient resources supported by the network node.

[0198] A7. A method according to clause A1, wherein the first network node is a RAN node and the second network node is a core network (CN) element.

[0199] A8. A method according to clause A7, wherein the first message is sent via a NG interface associated with establishment of a connection between the RAN node and the core network element.

[0200] A9. A method according to clause A8, wherein the response message includes information related to the slice remapping function on the core network side.

[0201] A10. A method according to clause A9, wherein the information related to the slice remapping function on the core network side includes one or more of the following: instructions associated with the core network to support the slice remapping function and a list of slices supported by the core network that can be used for remapping.

[0202] A11. A method as in clause A1, wherein remapping of one or more resources from the first network node occurs when the mobile device leaves a coverage area supported by the first network node and moves to a coverage area supported by the second network node.

[0203] A12. The method of clause 1, wherein remapping of one or more resources from the first network node occurs when the first network node experiences a lack of resources to serve the mobile device.

[0204] A13. The method of clause A1, further comprising: receiving a notification message from the second network node indicating a modification of one or more resources available to the mobile device; and sending a confirmation to the second network node.

[0205] A14. A method according to clause A13, wherein the notification message corresponds to a NG-RAN CONFIGURATION UPDATE message.

[0206] A15. A method according to clause A15, wherein the confirmation corresponds to a NG-RAN CONFIGURATION UPDATE ACKNOWLEDGE message.

[0207] A16. A method according to any one or more of clauses A1 to A15, wherein one or more resources from the second network node available to the mobile device correspond to network slice resources.

[0208] B1. A method for wireless communication (eg, Fig.16 The method described in claim 1 comprises: receiving at a second network node a configuration exchange message comprising information about slice resources for a mobile device served by the first network node that are supported by a coverage area of ​​the first network node, wherein in a case where one or more resources can be remapped from the first network node to the second network node, the information about the slice resources is used for switching of the mobile device based on the configuration exchange message.

[0209] B2. A method according to clause B1, wherein the first network node is a source base station and the second network node is a target base station.

[0210] B3. A method according to clause B1, wherein the information of resources supported by the first network node includes slice information supported by the coverage area of ​​the first network node.

[0211] B4. A method according to clause B1, wherein the configuration exchange message is received from a core network element.

[0212] B5. A method according to clause B1, wherein the configuration exchange message is a RAN CONFIGURATION TRANSFER message.

[0213] B6. A method according to clause B1, wherein the information of resources supported by the first network node comprises an AMF set supported by the first network node.

[0214] B7. The method according to clause B1 also includes: at the second network node, based on the information of slice resources supported by the coverage area of ​​the first network node, determining whether the switching of the mobile device belongs to the intra-registration area type switching or the inter-registration area type switching.

[0215] C1. A method for wireless communication (eg, Fig.17 The method described in ), comprises: sending a handover request for handing over a mobile device by a first network node to a second network node, wherein the handover request results in a remapping of resources from the first network node that originally served the mobile device in the coverage area of ​​the first network node to the second network node.

[0216] C2. A method according to clause C1, wherein the remapping of resources occurs at the second network node.

[0217] C3. A method according to clause C1, wherein the first network node is a source base station and the second network node is a target base station.

[0218] C4. A method according to clause C1, wherein sending the handover request is responsive to the first network node determining that the first network node will cease supporting the mobile device.

[0219] C5. The method of clause C1, further comprising: receiving, at the first network node, an acknowledgement of the handover request from the second network node.

[0220] D1. A method for wireless communication (eg, Fig.18 ), comprising: determining, at a second network node, a remapping of resources from the first network node to the second network node, in a case where a mobile device in a coverage area supported by the first network node ceases to be supported by the first network node; and sending to the first network node an acknowledgement of a handover request associated with handing over the mobile device from the first network node to the second network node.

[0221] D2. A method according to clause D1, wherein the first network node is a source base station and the second network node is a target base station.

[0222] D3. A method according to clause D1, wherein the remapping of resources is in response to a handover request.

[0223] E1. A method for wireless communication (eg, Fig.19 ), comprising: receiving, at a second network node, a handover request associated with handing over a service to a mobile device in a coverage area supported by a first network node, wherein the handover request includes information for selecting allowed network resources to provide the service to the mobile device; and selecting, at a target network node, one or more network resources based on the information for selecting the allowed network resources.

[0224] E2. A method according to clause E1, wherein the first network node and the second network node are a source base station and a target base station.

[0225] E3. A method according to clause E1, wherein the handover request is received from a core network element.

[0226] E4. A method according to clause E3, wherein information for selecting allowed network resources to provide services to the mobile device is provided by the first network node to the core network element.

[0227] E5. A method according to clause E3, wherein the information used to select allowed network resources includes a list of network slice selection assistance information (NSSAI) for the mobile device.

[0228] E6. The method of clause E5, wherein the handover request further comprises information of one or more resources from the second network node available to the mobile device in the event that the mobile device ceases to be served by the first network node.

[0229] E7. A method according to any one or more of clauses A1 to E6, wherein the remapping of resources corresponds to remapping network slice resources.

[0230] E8. A method according to clause E7, wherein remapping network slice resources includes: when it is determined that a service to a mobile device supported by a network slice resource with a first ID is to be remapped, changing the association of the service to the mobile device from the network slice resource with the first ID to another network slice resource with a second ID.

[0231] E9. A method according to clause E8, wherein the service to the mobile device is identified according to a protocol data unit (PDU) session ID.

[0232] E10. A method according to any one or more of clauses A1 to E6, wherein the resources are included in a network slice.

[0233] E11. A method according to clause E10, wherein the network slice is identified by an identifier (ID).

[0234] E12. An apparatus for wireless communications, comprising a processor configured to implement a method according to any of clauses A1 to E11.

[0235] E13. A non-transitory computer-readable medium having stored thereon code which, when executed by a processor, causes the processor to implement a method according to any one of clauses A1 to E11.

[0236] The disclosed and other embodiments, modules and functional operations described in this document may be implemented in a digital electronic circuit system, or in computer software, firmware or hardware including the structures disclosed in this document and their structural equivalents, or a combination of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by a data processing device or for controlling the operation of a data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that implements a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" includes all devices, equipment and machines for processing data, including, as examples, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal is an artificially generated signal, such as a machine-generated electrical signal, an optical signal, or an electromagnetic signal generated to encode information for transmission to a suitable receiver device.

[0237] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing portions of one or more modules, subroutines, or code). A computer program may be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communications network.

[0238] The processes and logic flows described herein may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and the apparatus may be implemented as, a special purpose logic circuit system, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0239] As an example, processors suitable for executing computer programs include both general-purpose microprocessors and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. In general, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. In general, a computer will also include one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably coupled to receive data from or transmit data to the one or more mass storage devices, or both. However, a computer does not require such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit system.

[0240] Although this patent document contains many details, these details should not be interpreted as limitations on the scope of any invention or what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features described in this patent document in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as working in certain combinations and even initially claimed as such, in some cases one or more features from a claimed combination may be excluded from the combination, and a claimed combination may be directed to a sub-combination or a variation of a sub-combination.

[0241] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the operations shown be performed, in order to achieve the desired results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0242] Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this patent document.

Claims

1. A method for wireless communication, comprising: sending, by a first network node to a second network node, a first message including information for handling access and mobility management tasks associated with a mobile device, wherein the first network node serves the mobile device in a coverage area of ​​the first network node, and the first message is sent prior to a handover request transmitted from the first network node to the second network node; In a case where one or more resources can be remapped from the first network node, determining, at the first network node, information of one or more resources available to the mobile device from the second network node based on a response message from the second network node; as well as An indication of the determined information is included by the first network node in the handover request transmitted from the first network node to the second network node to allow the second network node to select a remap slice based on the indication.

2. The method according to claim 1, wherein the information of the one or more resources available to the mobile device when the one or more resources are remapped from the first network node includes at least one of the following: information related to an access and mobility management function (AMF) function supported by the first network node and the second network node, information identifying a list of slices supported by a coverage area of ​​the second network node, information indicating whether the second network node supports a RAN slice remapping function, or information indicating whether a core network element electrically coupled to the first network node supports a RAN slice remapping function. 3 . The method according to claim 1 , wherein the first network node and the second network node are Radio Access Network (RAN) nodes.

4. The method according to claim 1, further comprising: Determine from the response message and the first message whether the first network node and the second network node belong to the same Access and Mobility Management Function AMF or AMF set.

5. The method of claim 1, wherein the first message is sent via an Xn interface associated with establishment of a connection between the first network node and the second network node.

6. The method of claim 2, wherein the slice remapping functionality comprises one or more of the following instructions: an instruction to a network node for supporting remapping of network slices, a list of network slices supported by the network node and available for remapping, an instruction to a network node to send allowed network slice selection assistance information NSSAI to the mobile device, an instruction to a network node for pre-configured support of network slices through remapping, or an indication of insufficient resources supported by the network node.

7. The method of claim 1, wherein the first network node is a RAN node, and the second network node is a core network (CN) element.

8. The method of claim 7, wherein the first message is sent via a NG interface associated with establishment of a connection between the RAN node and a core network element.

9. The method according to claim 8, wherein the response message includes information related to the slice remapping function on the core network side.

10. The method according to claim 9, wherein the information related to the slice remapping function on the core network side includes one or more of the following: instructions associated with the core network to support the slice remapping function and a list of slices supported by the core network that can be used for remapping.

11. The method of claim 1 , wherein the one or more resources are to be remapped from the first network node when the mobile device leaves a coverage area supported by the first network node and moves to a coverage area supported by the second network node.

12. The method of claim 1, wherein the one or more resources are to be remapped from the first network node occurs when the first network node experiences a lack of resources to serve the mobile device.

13. The method according to claim 1, further comprising: receiving, from the second network node, a notification message indicating a modification of the one or more resources available to the mobile device; as well as An acknowledgement is sent to the second network node.

14. The method of claim 13, wherein the notification message corresponds to a NG-RAN CONFIGURATION UPDATE message.

15. The method of claim 13, wherein the acknowledgement corresponds to a NG-RAN CONFIGURATION UPDATE ACKNOWLEDGE message.

16. A method according to any one or more of claims 1 to 15, wherein the one or more resources from the second network node available to the mobile device correspond to network slice resources.

17. A method for wireless communication, comprising: receiving, at a second network node, a configuration exchange message including information of slice resources for a mobile device served by a first network node supported by a coverage area of ​​the first network node, wherein the information of the slice resources is used for switching of the mobile device based on the configuration exchange message in case one or more resources can be remapped from the first network node to the second network node; A handover request is received at the second network node, the handover request including an indication of information of one or more resources available to the mobile device from the second network node, wherein the information of the one or more resources is determined at the first network node, and the handover request is received after receiving the configuration exchange message.

18. The method of claim 17, wherein the first network node is a source base station and the second network node is a target base station.

19. The method of claim 17, wherein the information of resources supported by the first network node comprises slice information supported by a coverage area of ​​the first network node.

20. The method of claim 17, wherein the configuration exchange message is received from a core network element.

21. The method of claim 17, wherein the configuration exchange message is a RAN CONFIGURATION TRANSFER message.

22. The method of claim 17, wherein the information of resources supported by the first network node comprises an AMF set supported by the first network node.

23. The method of claim 17, further comprising: At the second network node, based on the information of slice resources supported by the coverage area of ​​the first network node, it is determined whether the switching of the mobile device belongs to an intra-registration area type switching or an inter-registration area type switching.

24. A method for wireless communication, comprising: A handover request is sent by a first network node to a second network node for handover of a mobile device, wherein the handover request results in a remapping of resources from the first network node that originally served the mobile device in a coverage area of ​​the first network node to the second network node, and the handover request includes an indication of information of one or more resources available to the mobile device from the second network node, the information of the one or more resources being determined by the first network node based on a configuration exchange response received from the second network node prior to the handover request.

25. The method of claim 24, wherein remapping of resources occurs at the second network node.

26. The method of claim 24, wherein the first network node is a source base station and the second network node is a target base station.

27. The method of claim 24, wherein the handover request is sent in response to the first network node determining that the first network node will stop supporting the mobile device.

28. The method of claim 24, further comprising: An acknowledgement of the handover request is received at the first network node from the second network node.

29. A method for wireless communication, comprising: determining, at a second network node, a remapping of resources from the first network node to the second network node, in a case where a mobile device in a coverage area supported by a first network node ceases to be supported by the first network node, wherein the remapping of resources is determined based on an indication of information of one or more resources available to the mobile device from the second network node, wherein the indication is included in a handover request from the first network node, wherein the information of one or more resources available to the mobile device from the second network node is determined at the first network node based on a configuration exchange response transmitted from the second network node prior to the handover request; and An acknowledgement of the handover request associated with handing over the mobile device from the first network node to the second network node is sent to the first network node.

30. The method of claim 29, wherein the first network node is a source base station and the second network node is a target base station.

31. The method of claim 29, wherein remapping of resources is in response to the handover request.

32. A method for wireless communication, comprising: receiving, at a second network node, a handover request associated with handing over a service to a mobile device in a coverage area supported by a first network node, wherein the handover request includes information for selecting allowed network resources to provide service to the mobile device, wherein the information is determined by the first network node based on a configuration exchange response transmitted by the second network node prior to the handover request; as well as At the target network node, one or more network resources are selected based on the information used to select allowed network resources.

33. The method of claim 32, wherein the first network node and the second network node are a source base station and a target base station.

34. The method of claim 33, wherein the handover request is received from a core network element.

35. The method of claim 34, wherein information for selecting allowed network resources to provide service to the mobile device is provided by the first network node to the core network element.

36. A method according to claim 34, wherein the information for selecting allowed network resources includes a network slice selection assistance information (NSSAI) list of the mobile device.

37. The method of claim 34, wherein the handover request further includes information of one or more resources from the second network node available to the mobile device in the event that the mobile device stops being served by the first network node.

38. A method according to any one of claims 1 to 37, wherein the remapping of resources corresponds to remapping network slice resources.

39. The method of claim 38, wherein remapping the network slice resources comprises: When it is determined that the service to the mobile device supported by the network slice resource with a first ID is to be remapped, the association of the service to the mobile device is changed from the network slice resource with the first ID to another network slice resource with a second ID.

40. The method of claim 39, wherein the service to the mobile device is identified based on a protocol data unit (PDU) session ID.

41. A method according to any one of claims 1 to 40, wherein the resources are included in a network slice.

42. The method of claim 41 , wherein the network slice is identified by an identifier (ID).

43. An apparatus for wireless communication, the apparatus comprising a processor configured to implement the method of any one of claims 1 to 42.

44. A non-transitory computer readable medium having stored thereon codes which, when executed by a processor, cause the processor to implement the method of any one of claims 1 to 42.

Images