CN114071607A

CN114071607A - Slice remapping method, device and storage medium

Info

Publication number: CN114071607A
Application number: CN202010783452.7A
Authority: CN
Inventors: 倪春林
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-08-06
Filing date: 2020-08-06
Publication date: 2022-02-18

Abstract

The embodiment of the application provides a slice remapping method, a slice remapping device and a storage medium. Receiving a handover request message sent by a source RAN node; if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information. Therefore, the embodiment solves the problem of data transmission interruption when the terminal moves across the registration area, and ensures the continuity of data transmission.

Description

Slice remapping method, device and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a slice remapping method, an apparatus, and a storage medium.

Background

In a communication system, network slicing techniques are various types of services that may allow a provider to provide different feature requirements in a 5G network.

When a terminal moves across a registration area in a slice deployment scene in the current network slice technology, once the terminal moves to a cell inconsistent with a network slice supported by the registration area, data transmission is interrupted under the condition of inconsistent slice support.

Therefore, how to solve the problem of data transmission interruption when the terminal moves across the registration area is a technical problem which needs to be solved currently.

Disclosure of Invention

The embodiment of the application provides a slice remapping method, a slice remapping device and a storage medium, which are used for solving the defect of data transmission interruption when a terminal moves across registration areas in the prior art and realizing the continuity of data transmission.

In a first aspect, an embodiment of the present application provides a slice remapping method, where the method is used for a target radio access network RAN node, and the method includes:

receiving a switching request message sent by a source RAN node;

if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment;

and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information.

Optionally, according to a slice remapping method of an embodiment of the present application, the determining that the target RAN node has a network slice that does not support the source RAN node according to the handover request message includes:

determining first slice information which can be supported by the source RAN node according to the switching request message;

determining second slice information that the target RAN node can support;

and if the first slice information includes a network slice that does not exist in the second slice information, determining that the target RAN node has an unsupported network slice.

Optionally, according to the slice remapping method of an embodiment of the present application, the sending a slice remapping request message to a core network device includes:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

and sending the slice remapping request message carrying the first network slice list to the core network equipment.

Optionally, according to the slice remapping method of an embodiment of the present application, the slice remapping request message further includes a second network slice list that the target RAN node can support.

Optionally, the slice remapping method according to an embodiment of the present application further includes:

sending a switching request confirmation message to the source RAN node, wherein the switching request confirmation message comprises the slice remapping information so that the source RAN node executes Radio Resource Control (RRC) reconfiguration on a terminal according to the slice remapping information;

sending a path switching request message to the core network equipment, wherein the path switching request message comprises the slice remapping information;

and receiving a path switching confirmation message returned by the core network.

In a second aspect, an embodiment of the present application further provides a slice remapping method, where the method is used in a core network device, and includes:

receiving a slice remapping request message sent by a target Radio Access Network (RAN) node, wherein the slice remapping request message is sent to core network equipment by the target RAN node when the target RAN node determines that an unsupported network slice exists in the target RAN node according to a switching request message sent by a source RAN node;

determining corresponding slice remapping information according to the slice remapping request message;

and sending a slice remapping request response message carrying the slice remapping information to the target RAN node so that the target RAN node performs slice remapping according to the slice remapping information.

Optionally, according to the slice remapping method of an embodiment of the present application, the slice remapping request message includes a first network slice list not supported by the target RAN node;

the determining the corresponding slice remapping information according to the slice remapping request message includes:

and determining corresponding slice remapping information according to the first network slice list.

Optionally, according to the slice remapping method of an embodiment of the present application, the slice remapping request message further includes a second network slice list that the target RAN node can support;

the determining of the corresponding slice remapping information according to the first network slice list includes:

and determining corresponding slice remapping information according to the first network slice list and the second network slice list.

In a third aspect, an embodiment of the present application further provides a slice remapping method, where the method is used for a source radio access network RAN node, and the method includes:

if the target RAN node is determined to have the network slice which is not supported, sending a slice remapping request message to the core network equipment;

Optionally, according to a slice remapping method in an embodiment of the present application, the determining that there is an unsupported network slice for a target RAN node includes:

determining first slice information that the source RAN node can support;

acquiring second slice information which can be supported by the target RAN;

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

sending a handover request message to the target RAN node, wherein the handover request message comprises remapped third slice information;

receiving a switching request confirmation message sent by the target RAN node, wherein the switching request confirmation message comprises slice remapping information;

and executing Radio Resource Control (RRC) reconfiguration for the terminal according to the slice remapping information.

In a fourth aspect, an embodiment of the present application further provides a slice remapping method, where the method is used in a core network device, and includes:

receiving a slice remapping request message sent by a source Radio Access Network (RAN) node, wherein the slice remapping request message is sent to core network equipment by the source RAN node when determining that an unsupported network slice exists in a target RAN node;

and sending a slice remapping request response message carrying the slice remapping information to the source RAN node so that the source RAN node performs slice remapping according to the slice remapping information.

In a fifth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the slice remapping apparatus is used for a target radio access network RAN node, and includes a memory, a transceiver, and a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

receiving a switching request message sent by a source RAN node;

Optionally, according to an apparatus for slice remapping according to an embodiment of the present application, the determining that there is a network slice that does not support the source RAN node according to the handover request message includes:

determining second slice information that the target RAN node can support;

Optionally, according to the slice remapping apparatus in an embodiment of the present application, the sending a slice remapping request message to a core network device includes:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

Optionally, according to the slice remapping apparatus in an embodiment of the present application, the slice remapping request message further includes a second network slice list that the target RAN node can support.

Optionally, the slice remapping apparatus according to an embodiment of the present application further includes:

In a sixth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the slice remapping apparatus is used in a core network device, and includes:

Optionally, according to the slice remapping apparatus in an embodiment of the present application, the slice remapping request message includes a first network slice list that is not supported by the target RAN node;

Optionally, according to the slice remapping apparatus in an embodiment of the present application, the slice remapping request message further includes a second network slice list that the target RAN node can support;

In a seventh aspect, an embodiment of the present application further provides a slice remapping apparatus, where the slice remapping apparatus is used for a source radio access network RAN node, and includes a memory, a transceiver, and a processor:

Optionally, according to an apparatus for slice remapping according to an embodiment of the present application, the determining that there is an unsupported network slice for a target RAN node includes:

determining first slice information that the source RAN node can support;

acquiring second slice information which can be supported by the target RAN;

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

In an eighth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the slice remapping apparatus is used in a core network device, and includes:

In a ninth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the apparatus is used for a target radio access network RAN node, and the apparatus includes:

a message receiving module, configured to receive a handover request message sent by a source RAN node;

a first sending module, configured to send a slice remapping request message to a core network device if it is determined that an unsupported network slice exists in the target RAN node according to the handover request message;

a first remapping module, configured to, if a slice remapping request response message sent by the core network device is received, where the slice remapping request response message includes slice remapping information, perform slice remapping according to the slice remapping information.

In a tenth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the apparatus is used for a core network device, and the apparatus includes:

a first receiving module, configured to receive a slice remapping request message sent by a target radio access network RAN node, where the slice remapping request message is sent to the core network device by the target RAN node when it is determined that an unsupported network slice exists in the target RAN node according to a handover request message sent by the source RAN node;

a first determining module, configured to determine corresponding slice remapping information according to the slice remapping request message;

a first response module, configured to send a slice remapping request response message carrying the slice remapping information to the target RAN node, so that the target RAN node performs slice remapping according to the slice remapping information.

In an eleventh aspect, an embodiment of the present application further provides a slice remapping apparatus, where the apparatus is used for a source radio access network RAN node, and the apparatus includes:

a second sending module, configured to send a slice remapping request message to a core network device if it is determined that an unsupported network slice exists in a target RAN node;

and a second remapping module, configured to, if a slice remapping request response message sent by the core network device is received, where the slice remapping request response message includes slice remapping information, perform slice remapping according to the slice remapping information.

In a twelfth aspect, an embodiment of the present application further provides a slice remapping apparatus, where the apparatus is used in a core network device, and the apparatus includes:

a second receiving module, configured to receive a slice remapping request message sent by a source radio access network RAN node, where the slice remapping request message is sent to a core network device by the source RAN node when it is determined that an unsupported network slice exists in a target RAN node;

a second determining module, configured to determine corresponding slice remapping information according to the slice remapping request message;

a second response module, configured to send a slice remapping request response message carrying the slice remapping information to the source RAN node, so that the source RAN node performs slice remapping according to the slice remapping information.

In a thirteenth aspect, an embodiment of the present invention further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable the processor to execute the slice remapping method according to the first aspect, the slice remapping method according to the second aspect, the slice remapping method according to the third aspect, or the slice remapping method according to the fourth aspect.

The slice remapping method, the slice remapping device and the slice remapping storage medium provided by the embodiment of the application receive a switching request message sent by a source RAN node; if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic diagram of a 5G network architecture provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a network slice deployment scenario provided in an embodiment of the present application;

fig. 3 is a schematic flowchart of a slice remapping method provided in an embodiment of the present application;

fig. 4 is a schematic flowchart of a slice remapping method provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a target RAN node initiated slice remapping method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a slice remapping method provided in an embodiment of the present application;

fig. 7 is a schematic flowchart of a slice remapping method provided in an embodiment of the present application;

fig. 8 is a schematic diagram of a source RAN node-initiated slice remapping method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 11 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 12 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 14 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 15 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application;

fig. 16 is a schematic structural diagram of a slice remapping device provided in an embodiment of the present application;

Detailed Description

In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

A slicing technique is introduced into a 5G (5th generation, fifth generation) NR (New Radio, New air interface) system, different slice types correspond to different service types or different service providers, an operator can flexibly configure network slices supported by the operator on a network side according to different requirements, and deployed slice types are independently configured in different cells. However, there is a protocol under the current network architecture that provides that the UE (User Equipment) has a consistent and continuous slice type in the RA (Registration Area). I.e. the serving cell can only be designated by the network as registration area for the UE if the supported slice types are identical. Once the UE moves to a cell that is not consistent with the network slice supported by the registration area, the UE needs to reinitiate registration and the network reallocates the registration area. When the UE moves across the registration area in the connected state, if the activated data connection network slice target node does not support, the target node will refuse the handover, and the data connection will be interrupted. The invention provides a method for solving the problem of how to remap a service network slice to ensure the continuity of data transmission when a connected UE moves across registration areas.

One, network slice concept and standard provisions

Such as the 5G network architecture diagram shown in fig. 1. The network slicing technology is a technology that enables an operator to slice a plurality of virtual end-to-end network slicing instances in a 5G network to provide various types of services with different feature requirements. The operator may also deploy slice instances of the same service type but different service providers to serve different customer groups.

In fig. 1, the terms are specifically:

NSSF (Network Slice Selection Function)

AUSF (Authentication Server Function)

UDM (Unified Data Manager, Unified Data management)

AMF (Access and Mobility Management Function)

SMF (Session Management Function)

PCF (Policy Control Function)

AF (Application Function)

AN (Access Network )

UPF (User Plane Function)

DN (Data Network )

Different Network slices are identified with an S-NSSAI (Single Network Slice Selection Assistance Information) that contains two characteristics, namely a Service type (SST: Slice/Service type) and a Service provider (SD: Slice Differentiator).

In the 5G NR environment, when applying for network Registration, the UE carries a network slice identifier (S-NSSAI) pre-configured and supported in the UE, and the network returns a network slice service identifier (allowed S-NSSAI, which receives single network slice selection assistance information) and a Registration Area (Registration Area) to the UE according to a user subscription and a network support condition.

According to the protocol of 3GPP (3rd Generation Partnership Project) 23.501, the Network slice deployment in the same Tracking Area (TA) is consistent when the Network is deployed, and when the UE is registered, the 5G-CN (Core Network) assigns a registration area consisting of a list (TA list) of tracking areas supporting the same Network slice to the UE. When the UE initiates registration, only the slice of the network supported by the cell in which the UE is located will be designated as the slice that the UE is allowed to access.

Second, method for processing data connection of connection state UE switching across registration areas in current standard

As shown in a schematic diagram of a network slice deployment scenario in fig. 2, when a UE initiates a registration application in a cell 1, a network slice 1 and a network slice 2 carried by the UE apply for information, and a 5G-CN returns registration confirmation information for the UE to receive the network slice 1 and the network slice 2, and provides the UE with a registration area 1, where the registration area 1 includes the cell 1 and the cell 2. The UE may use network slice 1 and network slice 2 when cell 1 activates a data connection. When the connected UE moves within the registration area, network slice 1 and network slice 2 are always supported, so the continuity of data connection can be ensured through the handover procedure. If the UE moves to cell 3, since the registration area 2 of cell 3 includes network slice 1 and network slice 3, i.e. cannot support the relevant data connection of network slice 2, the data connection based on network slice 2 carried by the connected UE is rejected by cell 3 according to the current standard. Thereby causing the data connection to be interrupted.

Therefore, in order to solve the problem that when a connected UE is switched across registration areas in a network slice deployment scenario in fig. 2, once a terminal moves to a cell inconsistent with a network slice supported by the registration area, data transmission is interrupted under the condition that slice support is inconsistent.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable System may be a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a Time Division Synchronous Code Division Multiple Access (Time Division Multiple Access) System, a General Packet Radio Service (GPRS) System, a Long Term Evolution (LTE) System (including TD-LTE and FDD LTE), a long term evolution (long term evolution) System (LTE-a) System, a universal Mobile telecommunications System (universal Mobile telecommunications System, UMTS), a worldwide interoperability for microwave Access (WiMAX-microwave Access, Radio network (New network) System, etc., a Radio Access (NR) System, a Radio Access (New network Access) System, etc. These various systems include terminal devices and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS/5GC), and the like.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services to a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to exchange received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA), may be a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may be an evolved Node B (eNB or e-NodeB) in a Long Term Evolution (LTE) System, may be a 5G Base Station (gbb) in a 5G network architecture (next evolution System), may be a Home evolved Node B (HeNB), a relay Node (relay Node), a Home Base Station (femto), a pico Base Station (pico Base Station), and the like, which are not limited in the embodiments of the present application. In some network architectures, a network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

The following description will be made by way of specific examples.

Fig. 3 is a schematic diagram of a slice remapping method provided in an embodiment of the present application, where the method may be used in a target RAN (Radio Access Network) node, and as shown in fig. 3, the slice remapping method includes the following steps:

s301, receiving a switching request message sent by a source RAN node.

Specifically, the target RAN node receives a handover request message sent by the source RAN node.

For example, in an example scenario, as in fig. 2, the target RAN node refers to a registration area 2 in which a cell 3 is located, and the network slices that can be supported by the registration area 2 are network slice 1 and network slice 3; the source RAN node refers to a registration area 1 in which a cell 1 is located, and the network slices that can be supported by the registration area 1 are a network slice 1 and a network slice 2. I.e., the network slices 1 corresponding to the source RAN node and the target RAN node are identical, except that the source RAN node has no network slice 3 and the target RAN node has no network slice 2. The target RAN node receives the handover request message sent by the source RAN node, that is, the registration area 2 receives the handover request message sent by the registration area 1.

S302, if the target RAN node is determined to have the network slice which is not supported according to the switching request message, a slice remapping request message is sent to core network equipment.

Specifically, if the target RAN determines that the target RAN node has an unsupported network slice according to the received handover request message sent by the source RAN node, the target RAN may send a slice remapping request message to the core network device.

For example, in an exemplary scenario, as shown in fig. 2, if the registration area 2 determines that the target RAN node has an unsupported network slice 2 according to the received handover request information sent by the registration area 1, the registration area 2 sends a slice remapping request message to the core network device, that is, information of the network slice 2 that is not supported by the registration area 2, and the registration area 2 requests the core network to remap information of the network slice 2 to other network slices of the registration area 2.

And S303, if a slice remapping request response message sent by the core network device is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information.

Specifically, if the target RAN node receives a slice remapping request response message sent by the core network device, where the slice remapping request response message includes slice remapping information, the target RAN node may perform slice remapping according to the slice remapping information sent by the core network device.

For example, in an exemplary scenario, as shown in fig. 2, if the registration area 2 receives a slice remapping request response message sent by the core network device, where the slice remapping request response message includes slice remapping information (for example, the core network indicates that the data connection of the network slice 2 of the registration area 1 may be remapped onto the network slice 3 of the registration area 2), the registration area 2 may remap the data connection of the network slice 2 according to the slice remapping information sent by the core network device (for example, the registration area 2 remaps the data connection of the network slice 2 of the registration area 1 onto the network slice 3 of the registration area 2), so that even if the UE moves to the cell 3, the data connection based on the network slice 2 carried by the UE is not rejected by the cell 3, thereby ensuring continuity of data transmission.

As can be seen from the above embodiments, by receiving a handover request message sent by a source RAN node; if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information, so that the target RAN node is used as an initiator of the slice remapping and finally completes the corresponding slice remapping, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

In an optional embodiment, the determining, in S102, that the target RAN node has a network slice that does not support the source RAN node according to the handover request message may include:

s3021, determining first slice information that the source RAN node can support according to the handover request message;

specifically, the target RAN node determines, according to the received handover request message sent by the source RAN node, first slice information that the source RAN node can support.

For example, in an example scenario, as shown in fig. 2, the first slice information here may be that the registration area 1 can support network slice 1 and network slice 2; the registration area 2 determines that the registration area 1 can support the network slice 1 and the network slice 2 according to the received handover request message sent by the registration area 1.

S3022, determining second slice information which can be supported by the target RAN node;

specifically, the target RAN node determines second slice information that it can support;

for example, in an exemplary scenario, as shown in fig. 2, the second slice information may be slice information that can be supported by the registration area 2, which is network slice 1 and network slice 3; the registration area 2 determines slice information that it can support as network slice 1 and network slice 3.

S3023, if the first slice information includes a network slice that does not exist in the second slice information, determining that an unsupported network slice exists in the target RAN node.

Specifically, if the first slice information includes a network slice that does not exist in the second slice information, the target RAN node determines that there is a network slice that is not supported.

For example, in an example scenario, as shown in fig. 2, registry 1 can support network slice 1 and network slice 2; if the slice information that can be supported by the registration area 2 is network slice 1 and network slice 3, it is determined that there is network slice 2 that is not supported by the registration area 2.

As can be seen from the foregoing embodiments, by determining first slice information that can be supported by the source RAN node according to the handover request message; and determining second slice information which can be supported by the target RAN node, and if the first slice information comprises network slices which do not exist in the second slice information, determining that the target RAN node has network slices which are not supported, so that the accuracy of determining that the target RAN node has the network slices which are not supported is improved.

In an alternative embodiment, the sending the slice remapping request message to the core network device in execution S102 may include:

s3024, determining a first network slice list which is not supported by the target RAN node;

specifically, the target RAN node determines a first network slice list that it does not support.

For example, in an example scenario, as shown in fig. 2, the determination by the registration area 2 of the first network slice list that it does not support includes: network slice 2.

S3025, adding the first network slice list to the slice remapping request message;

specifically, the target RAN node adds a first network slice list that is not supported by the target RAN node to a slice remapping request message sent by the core network device.

For example, in an example scenario, as shown in fig. 2, the registration area 2 adds the first network slice list, i.e. network slice 2, which is not supported by the registration area 2, to the slice remapping request message sent to the core network device, i.e. the message includes network slice 2.

S3026, sending the slice remapping request message carrying the first network slice list to the core network device.

Specifically, the target RAN node sends a slice remapping request message carrying a first network slice list that the target RAN node does not support to the core network device.

For example, in an example scenario, as shown in fig. 2, the registration area 2 sends a slice remapping request message carrying the network slice 2 to the core network device.

In addition, the performing of the slice remapping request message in S102 may further include: a second network slice list that the target RAN node can support.

For example, in an example scenario, as shown in fig. 2, the second network slice list that can be supported by the registration area 2 may also be included in the slice remapping request message, which is network slice 1 and network slice 3.

As can be seen from the above embodiments, by determining a first network slice list not supported by the target RAN node; adding the first network slice list, or the first network slice list and the second network slice list, to the slice remapping request message; the chip remapping request message carrying the first network chip list is sent to the core network device, so that the core network device can determine corresponding chip remapping information according to the first network chip list, namely the core network determines to remap data connection in the first network chip list to which network chips of a target RAN node are connected according to the first network chip list, or the first network chip list and the second network chip list, and reliability of determining the chip remapping information by the core network device is improved.

In an optional embodiment, after performing S103, the method may further include:

s304, sending a handover request confirmation message to the source RAN node, where the handover request confirmation message includes the slice remapping information, so that the source RAN node performs RRC reconfiguration for a terminal according to the slice remapping information.

Specifically, the target RAN node sends a handover request confirmation message to the source RAN node, where the handover request confirmation message includes slice remapping information, so that the source RAN node performs RRC reconfiguration of the terminal according to the slice remapping information;

for example, in an exemplary scenario, as shown in fig. 2, the registration area 2 sends handover request acknowledgement information to the registration area 1, where the handover request acknowledgement information includes slice remapping information, that is, data connection remapping of the network slice 2 of the registration area 1 is performed on the network slice 3 of the registration area 2, so that the registration area 1 performs RRC reconfiguration for the terminal according to the remapping information, that is, data connection remapping of the network slice 2 of the registration area 1 is performed on the network slice 3 of the registration area 2.

S305, sending a path switching request message to the core network equipment, wherein the path switching request message comprises the slice remapping information.

Specifically, the target RAN node sends a path switching request message to the core network device, where the path switching request message includes slice remapping information.

For example, in an exemplary scenario, as shown in fig. 2, the registration area 2 sends a path switch request message to the core network, where the path switch request message includes slice remapping information, that is, the data connection of the network slice 2 of the registration area 1 is remapped to the network slice 3 of the registration area 2.

S306, receiving the path switching confirmation message returned by the core network.

Specifically, the target RAN node receives a path switching acknowledgement message returned by the core network.

For example, in an exemplary scenario, as shown in fig. 2, the registration area 2 receives a path switch confirmation message returned by the core network.

As can be seen from the foregoing embodiments, a handover request acknowledgement message is sent to the source RAN node, where the handover request acknowledgement message includes the slice remapping information, so that the source RAN node performs RRC reconfiguration for a terminal according to the slice remapping information; sending a path switching request message to the core network equipment, wherein the path switching request message comprises the slice remapping information; and receiving the path switching confirmation message returned by the core network, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

Fig. 4 is a schematic diagram of a slice remapping method provided in this embodiment, where the method may be used in a core network device, and may include the following steps:

s401, receiving a slice remapping request message sent by a target RAN node, where the slice remapping request message is sent to the core network device by the target RAN node when it is determined that an unsupported network slice exists in the target RAN node according to a handover request message sent by a source RAN node.

Specifically, if the target RAN determines that the target RAN node has an unsupported network slice according to the received handover request message sent by the source RAN node, the core network device may receive a slice remapping request message sent by the target RAN.

S402, determining corresponding slice remapping information according to the slice remapping request message;

specifically, the core network device may determine, according to the slice remapping request message, corresponding slice remapping information, that is, the core network determines, according to the slice remapping request message, which network slices of the target RAN node remap the data connections of the network slices that are not supported by the target RAN node.

S403, sending a slice remapping request response message carrying the slice remapping information to the target RAN node, so that the target RAN node performs slice remapping according to the slice remapping information.

For example, in an example scenario, as shown in fig. 2, the core network device sends slice remapping information (e.g., the core network indicates that the data connections of network slice 2 of registration area 1 may be remapped to network slice 3 of registration area 2) to registration area 2, so that registration area 2 is remapped according to the slice remapping information (e.g., registration area 2 remaps the data connections of network slice 2 of registration area 1 to network slice 3 of registration area 2).

As can be seen from the foregoing embodiments, by receiving a slice remapping request message sent by a target radio access network RAN node, the slice remapping request message is sent to the core network device by the target RAN node when it is determined that an unsupported network slice exists in the target RAN node according to a handover request message sent by a source RAN node; determining corresponding slice remapping information according to the slice remapping request message; and sending a slice remapping request response message carrying the slice remapping information to the target RAN node so that the target RAN node performs slice remapping according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

In an optional embodiment, the slice remapping request message in S401 may include a first network slice list not supported by the target RAN node;

correspondingly, when S402 is executed, the method may include:

s4021, determining corresponding slice remapping information according to the first network slice list.

For example, in an example scenario, as shown in fig. 2, the first network slice list not supported by registration area 2 is network slice 2.

In an optional embodiment, the slice remapping request message in S401 may further include a second network slice list that can be supported by the target RAN node;

correspondingly, when S402 is executed, the method may include:

s4022, determining corresponding slice remapping information according to the first network slice list and the second network slice list.

For example, in an example scenario, as shown in fig. 2, the second network slice list that registration area 2 can support is network slice 1 and network slice 3.

As can be seen from the above embodiments, by determining slice remapping information, i.e. which network slices of a target RAN node a data connection in a first network slice list is remapped to, according to the first network slice list, or the first network slice list and a second network slice list, the reliability of determining the slice remapping information is improved.

Fig. 5 is a schematic diagram of a target RAN node-initiated slice remapping method according to an embodiment of the present application, and as can be seen from fig. 5, the target RAN node-initiated slice remapping performs the following steps:

step 1, a source RAN node initiates an HO (Hand Over) request to a target RAN node and carries slice information.

And step 2, after receiving the HO request of the source RAN node, the target RAN node initiates a slice remapping request to a core network (namely 5G-CN) according to the HO request and the slice supporting condition of the node. The slice remapping request may carry an unsupported slice session list, and optionally a slice list supported by the node.

And 3, replying a slice remapping request response by the core network, wherein the slice remapping request response carries slice remapping information.

And 4, the target RAN node executes slice remapping, namely remapping the slice.

And 5, the target RAN node responds a switching request confirmation message to the source RAN node, wherein the switching request confirmation message can carry the chip remapping information.

And 6 to 8, the source RAN node informs the UE to initiate switching, optionally carrying slice remapping information, and the UE finishes the switching process.

Step 9, the target RAN node initiates a PDU (Protocol Data Unit) path switching request to the 5G-CN, and the PDU path switching request carries slice remapping information

Step 10: the 5G-CN replies to the PDU path switching confirmation message.

As can be seen from the above embodiments, by receiving a handover request message sent by a source RAN node; if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information, solving the problem of data transmission interruption when the terminal moves across the registration area, and ensuring the continuity of data transmission.

Fig. 6 is a flowchart of a slice remapping method provided in an embodiment of the present application, where the method may be used for a source RAN node, and includes the following steps:

s601, if the target RAN node is determined to have the network slice which is not supported, a slice remapping request message is sent to the core network device.

Specifically, the source RAN node determines that the target RAN node has an unsupported network slice, and the source RAN node may send a slice remapping request message to the core network device;

for example, in an example scenario, as shown in fig. 2, if there is an unsupported network slice 2 in the registration area 2, the registration area 1 may send a slice remapping request message to the core network.

S602, if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information.

For example, in an exemplary scenario, as shown in fig. 2, if the registration area 1 receives a slice remapping request response message sent by a core network device, where the slice remapping request response message includes slice remapping information (for example, the core network indicates that the data connection of the network slice 2 of the registration area 1 may be remapped to the network slice 3 of the registration area 2), the registration area 1 performs slice remapping according to the slice remapping information.

As can be seen from the above embodiments, if it is determined that an unsupported network slice exists in a target RAN node, a slice remapping request message is sent to a core network device; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information, so that the source RAN node is used as an initiator of the slice remapping and finally completes the corresponding slice remapping, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

In an optional embodiment, when the step S601 is executed to determine that there is an unsupported network slice in the target RAN node, the step may include:

s6011, a source RAN node determines first slice information which can be supported by a target RAN node;

for example, in an example scenario, as shown in fig. 2, the registration area 1 determines that the first slice information that it can support is network slice 1 and network slice 2.

S6012, the source RAN node acquires second slice information which can be supported by the target RAN node;

for example, in an example scenario, as shown in fig. 2, registration area 1 obtains second slice information network slice 1 and network slice 3 that registration area 2 can support.

S6013, if the first slice information includes a network slice that does not exist in the second slice information, the source RAN node determines that the target RAN node has an unsupported network slice.

For example, in an example scenario, as shown in fig. 2, if the first slice information includes a network slice 2 that is not present in the second slice information, the registration area 1 determines that the registration area 2 has an unsupported network slice 2.

As can be seen from the above embodiments, by determining first slice information that the source RAN node can support; acquiring second slice information which can be supported by the target RAN; and if the first slice information comprises the network slice which does not exist in the second slice information, determining that the target RAN node has the network slice which is not supported, thereby improving the accuracy of determining that the target RAN node has the network slice which is not supported.

In an optional embodiment, when the sending of the slice remapping request message to the core network device in S601 is executed, the method may include:

s6014, the source RAN node determines a first network slice list which is not supported by the target RAN node;

for example, in an example scenario, as shown in fig. 2, registration area 1 determines that the first network slice list not supported by registration area 2 is network slice 2.

S6015, the source RAN node adds the first network slice list to a slice remapping request message;

for example, in an example scenario, registration area 1 adds network slice 2 to the slice remapping request message, as shown in fig. 2.

S6016, the source RAN node sends a slice remapping request message carrying the first network slice list to the core network device.

For example, in an example scenario, as shown in fig. 2, the registration area 1 sends a slice remapping request message carrying the network slice 2 to the core network device.

In addition, when the S601 slice remapping request message is executed, the method may further include: a second network slice list that the target RAN node can support;

for example, in an example scenario, as shown in fig. 2, a second network slice list that can be supported by the registration area 2 may be further included in the slice remapping request message, and the second network slice list may be network slice 1 and network slice 3.

In an optional embodiment, after performing S602, the following may be further included:

s603, the source RAN node sends a switching request message to the target RAN node, wherein the switching request message comprises remapped third slice information;

for example, in an example scenario, as shown in fig. 2, registration area 1 sends a handover request message to registration area 2, where the handover request message includes remapped third slice information, that is, network slice 2 remaps to network slice 3.

S604, the source RAN node receives a handover request acknowledgement message sent by the target RAN node, where the handover request acknowledgement message includes slice remapping information.

For example, in an exemplary scenario, as shown in fig. 2, the registration area 1 receives a handover request acknowledgement message sent by the registration area 2, where the handover request acknowledgement message includes slice remapping information, that is, the data connection of the network slice 2 of the registration area 1 is remapped to the network slice 3 of the registration area 2.

S605, the source RAN node executes RRC reconfiguration to the terminal according to the slice remapping information.

For example, in an exemplary scenario, as shown in fig. 2, registration area 1 performs RRC reconfiguration of the terminal according to slice remapping information.

As can be seen from the foregoing embodiments, by sending a handover request message to the target RAN node, the handover request message includes remapped third slice information; receiving a switching request confirmation message sent by the target RAN node, wherein the switching request confirmation message comprises slice remapping information; and performing Radio Resource Control (RRC) reconfiguration on the terminal according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across registration areas and ensuring the continuity of data transmission.

Fig. 7 is a flowchart of a slice remapping method provided in an embodiment of the present application, where the method may be used in a core network device, and may perform the following steps:

s701, receiving a slice remapping request message sent by a source radio access network RAN node, where the slice remapping request message is sent to a core network device by the source RAN node when determining that an unsupported network slice exists in a target RAN node. (ii) a

For example, in an exemplary scenario, as shown in fig. 2, a core network device receives a slice remapping request message sent by a registration area 1, where the slice remapping request message is sent by the registration area 1 to a core network when determining that an unsupported network slice 2 exists in the registration area 2.

S702, determining corresponding slice remapping information according to the slice remapping request message.

For example, in an exemplary scenario, as shown in fig. 2, the core network device determines corresponding slice remapping information according to the slice remapping request message.

S703, sending a slice remapping request response message carrying the slice remapping information to the source RAN node, so that the source RAN node performs slice remapping according to the slice remapping information.

For example, in an example scenario, as shown in fig. 2, the core network device sends a slice remapping request response message carrying slice remapping information to the registration area 1, so that the registration area 1 performs slice remapping according to the slice remapping information.

As can be seen from the foregoing embodiments, by receiving a slice remapping request message sent by a source RAN node, the slice remapping request message is sent to a core network device by the source RAN node when it is determined that an unsupported network slice exists in a target RAN node; determining corresponding slice remapping information according to the slice remapping request message; and sending a slice remapping request response message carrying the slice remapping information to the source RAN node so that the source RAN node performs slice remapping according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

In an optional embodiment, the slice remapping request message in S701 may include a first network slice list not supported by the target RAN node;

correspondingly, when S702 is executed, the method may include:

s7021, determining corresponding slice remapping information according to the first network slice list.

In an optional embodiment, the slice remapping request message in S701 may further include a second network slice list that can be supported by the target RAN node;

correspondingly, when S702 is executed, the method may include:

s7022, determining corresponding slice remapping information according to the first network slice list and the second network slice list.

Fig. 8 is a schematic diagram of a source RAN node-initiated slice remapping method according to an embodiment of the present application, where the source RAN node-initiated slice remapping may include the following steps:

step 1, the source RAN node makes a switching request judgment according to the situation, and the supporting situation of the target node slice to the switching session is checked by using the supporting situation of the adjacent node slice obtained through Xn

And 2, the source RAN node initiates a slice remapping request to the core network according to the support conditions of the switching session slice and the target node slice. Carrying an unsupported slice session list and target node information.

Step 4, the source RAN node executes the slice remapping

And 5, initiating an HO request by the source RAN node and carrying the remapped slice information.

And 6, the target RAN node responds to the HO request confirmation message to carry the slice remapping information.

And 7-9, the source RAN node informs the UE to initiate switching, optionally carries slice remapping information, and the UE finishes the switching process.

Step 10, the target RAN node initiates a path switching request to the 5G-CN and carries slice remapping information

Step 11: the 5G-CN replies with a path switch acknowledge message.

As can be seen from the above embodiments, if it is determined that an unsupported network slice exists in a target RAN node, a slice remapping request message is sent to a core network device; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information, solving the problem of data transmission interruption when the terminal moves across the registration area, and ensuring the continuity of data transmission.

Fig. 9 is a schematic structural diagram of a slice remapping apparatus according to an embodiment of the present application, where the slice remapping apparatus is used for a target RAN node, and includes a memory 920, a transceiver 900, and a processor 910:

wherein in fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 910, and various circuits, represented by memory 920, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 900 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 in performing operations.

The processor 910 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 920 for storing a computer program; a transceiver 900 for transceiving data under the control of the processor; a processor 900 for reading the computer program in the memory and performing the following operations:

receiving a switching request message sent by a source RAN node;

In an optional embodiment, the apparatus may further include: the determining that there is a network slice that does not support the source RAN node according to the handover request message includes:

determining second slice information that the target RAN node can support;

In an optional embodiment, the apparatus may further include: the sending of the slice remapping request message to the core network device includes:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

In an optional embodiment, the apparatus may further include: the slice remapping request message also includes a second network slice list that can be supported by the target RAN node.

In an optional embodiment, the apparatus may further include:

As can be seen from the above embodiments, by receiving a handover request message sent by a source RAN node; if the target RAN node is determined to have the network slice which is not supported according to the switching request message, sending a slice remapping request message to core network equipment; and if a slice remapping request response message sent by the core network equipment is received and the slice remapping request response message comprises slice remapping information, carrying out slice remapping according to the slice remapping information. Therefore, the data transmission interruption problem when the terminal moves across the registration area is solved, and the continuity of the data transmission is ensured.

Fig. 10 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application, where the slice remapping apparatus is used in a core network device, and includes a memory 1020, a transceiver 1000, and a processor 1010:

where in fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1010 and various circuits of memory represented by memory 1020 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1000 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1010 in performing operations.

The processor 1010 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 1020 for storing a computer program; a transceiver 1000 for transceiving data under the control of the processor; a processor 1010 for reading the computer program in the memory and performing the following operations:

In an optional embodiment, the apparatus may further include: the slice remapping request message includes a first network slice list not supported by the target RAN node;

In an optional embodiment, the apparatus may further include: the slice remapping request message further comprises a second network slice list which can be supported by the target RAN node;

As can be seen from the above embodiments, by receiving a slice remapping request message sent by a target radio access network RAN node, the slice remapping request message is sent to the core network device by the target RAN node when it is determined that an unsupported network slice exists in the target RAN node according to a handover request message sent by a source RAN node; determining corresponding slice remapping information according to the slice remapping request message; and sending a slice remapping request response message carrying the slice remapping information to the target RAN node so that the target RAN node performs slice remapping according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

Fig. 11 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application, where the slice remapping apparatus is used for a source RAN node, and includes a memory 1120, a transceiver 1100, and a processor 1110:

in fig. 11, among other things, the bus architecture may include any number of interconnected buses and bridges with various circuits being linked together, particularly one or more processors represented by processor 1110 and memory represented by memory 1120. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1100 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 1110 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1110 in performing operations.

The processor 1110 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 1120 for storing a computer program; a transceiver 1100 for transceiving data under the control of the processor; a processor 1110 for reading the computer program in the memory and performing the following operations:

In an optional embodiment, the apparatus may further include: the determining that there is an unsupported network slice for the target RAN node includes:

determining first slice information that the source RAN node can support;

acquiring second slice information which can be supported by the target RAN;

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

In an optional embodiment, the apparatus may further include: sending a handover request message to the target RAN node, wherein the handover request message comprises remapped third slice information;

Fig. 12 is a schematic structural diagram of a slice remapping apparatus provided in an embodiment of the present application, where the slice remapping apparatus is used for a core network device, and includes a memory 1220, a transceiver 1200, and a processor 1210:

wherein in fig. 12, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1210, and various circuits, represented by memory 1220, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1200 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 in performing operations.

The processor 1210 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 1220 for storing computer programs; a transceiver 1200 for transceiving data under the control of the processor; a processor 1210 for reading the computer program in the memory and performing the following operations:

receiving a slice remapping request message sent by a source RAN node, wherein the slice remapping request message is sent to core network equipment by the source RAN node when determining that an unsupported network slice exists in a target RAN node;

As can be seen from the above embodiments, by receiving a slice remapping request message sent by a source radio access network RAN node, the slice remapping request message is sent to a core network device by the source RAN node when it is determined that an unsupported network slice exists in a target RAN node; determining corresponding slice remapping information according to the slice remapping request message; and sending a slice remapping request response message carrying the slice remapping information to the source RAN node so that the source RAN node performs slice remapping according to the slice remapping information, thereby solving the problem of data transmission interruption when the terminal moves across the registration area and ensuring the continuity of data transmission.

It should be noted that, the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

Fig. 13 is a schematic structural diagram of a slice remapping apparatus according to an embodiment of the present application, where the apparatus may be used in a target RAN node, and the apparatus includes:

a message receiving module 131, configured to receive a handover request message sent by a source RAN node;

a first sending module 132, configured to send a slice remapping request message to a core network device if it is determined that an unsupported network slice exists in the target RAN node according to the handover request message;

a first remapping module 133, configured to, if a slice remapping request response message sent by the core network device is received, where the slice remapping request response message includes slice remapping information, perform slice remapping according to the slice remapping information.

In an alternative embodiment, the first sending module 132 may include:

a first determining submodule, configured to determine, according to the handover request message, first slice information that can be supported by the source RAN node;

a second determining submodule, configured to determine second slice information that can be supported by the target RAN node;

a third determining sub-module, configured to determine that an unsupported network slice exists in the target RAN node if the first slice information includes a network slice that does not exist in the second slice information.

In an alternative embodiment, the first sending module 132 may include:

a fourth determining submodule, configured to determine a first network slice list that is not supported by the target RAN node;

a first adding submodule, configured to add the first network slice list to the slice remapping request message;

a first message sending submodule, configured to send the slice remapping request message carrying the first network slice list to the core network device.

In an optional embodiment, the slice remapping request message further includes a second network slice list that can be supported by the target RAN node.

In an optional embodiment, the apparatus further comprises:

a second message sending module, configured to send a handover request acknowledgement message to the source RAN node, where the handover request acknowledgement message includes the slice remapping information, so that the source RAN node performs RRC reconfiguration for a terminal according to the slice remapping information;

a third message sending module, configured to send a path switching request message to the core network device, where the path switching request message includes the slice remapping information;

and the first message receiving module is used for receiving the path switching confirmation message returned by the core network.

Fig. 14 is a schematic structural diagram of a slice remapping apparatus according to an embodiment of the present application, where the apparatus may be used in a core network device, and the apparatus includes:

a first receiving module 141, configured to receive a slice remapping request message sent by a target radio access network RAN node, where the slice remapping request message is sent to the core network device by the target RAN node when it is determined that an unsupported network slice exists in the target RAN node according to a handover request message sent by the source RAN node;

a first determining module 142, configured to determine corresponding slice remapping information according to the slice remapping request message;

a first response module 143, configured to send a slice remapping request response message carrying the slice remapping information to the target RAN node, so that the target RAN node performs slice remapping according to the slice remapping information.

In an optional embodiment, the slice remapping request message includes a first list of network slices not supported by the target RAN node; the first determining module 142 may include:

and the fifth determining submodule is used for determining corresponding slice remapping information according to the first network slice list.

In an optional embodiment, the slice remapping request message further includes a second network slice list that the target RAN node can support; the fifth determining submodule is specifically configured to determine corresponding slice remapping information according to the first network slice list and the second network slice list.

Fig. 15 is a schematic structural diagram of a slice remapping apparatus according to an embodiment of the present application, where the apparatus may be used in a source RAN node, and the apparatus includes:

a second sending module 151, configured to send a slice remapping request message to a core network device if it is determined that an unsupported network slice exists in a target RAN node;

a second remapping module 152, configured to perform slice remapping according to the slice remapping information if a slice remapping request response message sent by the core network device is received, where the slice remapping request response message includes the slice remapping information.

In an optional embodiment, the second sending module 151 may include:

a sixth determining sub-module, configured to determine first slice information that the source RAN node can support;

the acquisition submodule is used for acquiring second slice information which can be supported by the target RAN;

a seventh determining sub-module, configured to determine that an unsupported network slice exists in the target RAN node if the first slice information includes a network slice that does not exist in the second slice information.

In an optional embodiment, the second sending module 151 may include:

an eighth determining submodule, configured to determine a first network slice list that is not supported by the target RAN node;

a second adding submodule, configured to add the first network slice list to the slice remapping request message;

and the second sending submodule is used for sending the slice remapping request message carrying the first network slice list to the core network equipment.

In an optional embodiment, the apparatus further comprises: the slice remapping request message also includes a second network slice list that can be supported by the target RAN node.

In an optional embodiment, the apparatus further comprises:

a fourth message sending module, configured to send a handover request message to the target RAN node, where the handover request message includes remapped third slice information;

a second message receiving module, configured to receive a handover request acknowledgement message sent by the target RAN node, where the handover request acknowledgement message includes slice remapping information;

and the RRC reconfiguration module is used for executing RRC reconfiguration on the terminal according to the slice remapping information.

Fig. 16 is a schematic structural diagram of a slice remapping apparatus according to an embodiment of the present application, where the apparatus may be used in a core network device, and includes:

a second receiving module 161, configured to receive a slice remapping request message sent by a source radio access network RAN node, where the slice remapping request message is sent to a core network device by the source RAN node when it is determined that an unsupported network slice exists in a target RAN node;

a second determining module 162, configured to determine corresponding slice remapping information according to the slice remapping request message;

a second response module 163, configured to send a slice remapping request response message carrying the slice remapping information to the source RAN node, so that the source RAN node performs slice remapping according to the slice remapping information.

In an optional embodiment, the slice remapping request message includes a first list of network slices not supported by the target RAN node; the second determining module 162 may include:

and the ninth determining submodule is used for determining corresponding slice remapping information according to the first network slice list.

In an optional embodiment, the slice remapping request message further includes a second network slice list that the target RAN node can support; the ninth determining submodule is specifically configured to determine corresponding slice remapping information according to the first network slice list and the second network slice list.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

It should be noted that the apparatus provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

In another aspect, an embodiment of the present invention further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable the processor to execute the above slice remapping method for a target RAN node, or execute the above slice remapping method for a source RAN node, or execute the above slice remapping method for a core network device.

The processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

As seen from the above embodiments, a processor-readable storage medium stores a computer program for causing the processor to execute the above data compression method. Therefore, the embodiment of the application solves the problem that data transmission is interrupted when the terminal moves across the registration area, and ensures the continuity of data transmission.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for slice remapping for a target radio access network, RAN, node, comprising:

receiving a switching request message sent by a source RAN node;

2. The method of claim 1, wherein the determining that the target RAN node has a network slice that does not support the source RAN node based on the handover request message comprises:

determining second slice information that the target RAN node can support;

3. The method according to claim 1 or 2, wherein the sending the slice remapping request message to the core network device comprises:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

4. The method of claim 3, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support.

5. The method of claim 1 or 2, further comprising:

6. A slice remapping method for a core network device, comprising:

7. The method of claim 6, wherein the slice remapping request message includes a first list of network slices not supported by the target RAN node;

8. The method of claim 7, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support;

9. A method for slice remapping for a source radio access network, RAN, node, comprising:

10. The method of claim 9, wherein the determining that there is an unsupported network slice for the target RAN node comprises:

determining first slice information that the source RAN node can support;

acquiring second slice information which can be supported by the target RAN;

11. The method according to claim 9 or 10, wherein said sending a slice remapping request message to a core network device comprises:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

12. The method of claim 11, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support.

13. The method of claim 9 or 10, further comprising:

14. A slice remapping method for a core network device, comprising:

15. The method of claim 14, wherein the slice remapping request message includes a first list of network slices not supported by the target RAN node;

16. The method of claim 15, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support;

17. A slice remapping apparatus, said slice remapping apparatus for a target radio access network, RAN, node, comprising a memory, a transceiver, a processor:

receiving a switching request message sent by a source RAN node;

18. The apparatus of claim 17, wherein the determining from the handover request message that there is a network slice that does not support the source RAN node comprises:

determining second slice information that the target RAN node can support;

19. The apparatus according to claim 17 or 18, wherein the sending the slice remapping request message to the core network device comprises:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

20. The apparatus of claim 19, wherein the slice remapping request message further comprises a second list of network slices that the target RAN node can support.

21. The apparatus of claim 17 or 18, further comprising:

22. A slice remapping apparatus, said slice remapping apparatus for a core network device comprising a memory, a transceiver, a processor:

23. The apparatus of claim 22, wherein the slice remapping request message includes a first list of network slices not supported by the target RAN node;

24. The apparatus of claim 23, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support;

25. A slice remapping apparatus, for a source radio access network, RAN, node, comprising a memory, a transceiver, a processor:

26. The apparatus of claim 25, wherein the determining that there is an unsupported network slice for a target RAN node comprises:

determining first slice information that the source RAN node can support;

acquiring second slice information which can be supported by the target RAN;

27. The apparatus according to claim 25 or 26, wherein the sending the slice remapping request message to the core network device comprises:

determining a first network slice list not supported by the target RAN node;

adding the first network slice list to the slice remapping request message;

28. The apparatus of claim 27, wherein the slice remapping request message further comprises a second list of network slices that the target RAN node can support.

29. The apparatus of claim 25 or 26, further comprising:

30. A slice remapping apparatus, said slice remapping apparatus for a core network device comprising a memory, a transceiver, a processor:

31. The apparatus of claim 30, wherein the slice remapping request message includes a first list of network slices not supported by the target RAN node;

32. The apparatus of claim 31, wherein the slice remapping request message further includes a second list of network slices that the target RAN node can support;

33. An apparatus for slice remapping for a target radio access network, RAN, node, comprising:

34. A slice remapping apparatus for a core network device, comprising:

35. An apparatus for slice remapping for a source radio access network, RAN, node, comprising:

36. A slice remapping apparatus for a core network device, comprising:

37. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing a processor to perform the method of any of claims 1 to 5, or the method of any of claims 6 to 8, or the method of any of claims 9 to 13, or the method of any of claims 14 to 16.