WO2022011572A1

WO2022011572A1 - Network handover method, device, equipment, and storage medium

Info

Publication number: WO2022011572A1
Application number: PCT/CN2020/101971
Authority: WO
Inventors: 付喆
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-07-14
Filing date: 2020-07-14
Publication date: 2022-01-20
Also published as: CN115804148A

Abstract

The present application relates to the field of mobile communication. Disclosed are a network handover method, a device, equipment, and a storage medium. The method comprises: acquiring slice information, the slice information being used for indicating information corresponding to a slice network; and determining a handover action on the basis of the slice information, the handover action being used for indicating a scheme by which a network slice performs a handover, thus making clear a specific determination rule for the handover, ensuring a smooth handover process for the network slice, preventing an interruption from occurring during the handover process, ensuring the continuity of the handover process, and increasing network handover accuracy.

Description

Network switching method, device, device and storage medium

technical field

The present application relates to the field of mobile communications, and in particular, to a network switching method, apparatus, device, and storage medium.

Background technique

At present, in the NR (New Radio, new air interface) system, a network slicing technology is proposed. Using the network slicing technology, the physical network can be roughly divided into multiple virtual logical networks. Each virtual logical network corresponds to a virtual scene. The device can establish a connection with the terminal based on the slice information sent by the terminal.

During the handover process, the source base station receives the report result of the terminal, sends a handover request to the target base station based on the report result, and the target base station receives the handover request and obtains the slice information included in the handover request. When the network slice of the target base station does not support the handover request When slicing information is not available, radio resources cannot be allocated for the network slice, resulting in failure to complete network switching in the future. Therefore, there is an urgent need for a method capable of completing network switching.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a network switching method, apparatus, device, and storage medium, which solve the problem of switching interruption during the switching process and improve the accuracy of network switching. The technical solution is as follows:

According to an aspect of the present application, a network switching method is provided, the method comprising:

Obtain slice information, where the slice information is used to indicate information corresponding to the slice network;

According to the slice information, a switching behavior is determined, and the switching behavior is used to indicate a way of switching the network slice.

According to an aspect of the present application, a network switching method is provided, applied to a first entity, and the method includes:

According to an aspect of the present application, a network switching apparatus is provided, the apparatus comprising:

an acquisition module, configured to acquire slice information, where the slice information is used to indicate information corresponding to the slice network;

A determination module, configured to determine a switching behavior according to the slice information, where the switching behavior is used to indicate a way of switching the network slice.

According to an aspect of the present application, a network switching apparatus is provided, which is applied in a first entity, and the apparatus includes:

According to one aspect of the present application, a network device is provided, the network device comprising: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the The processor is configured to load and execute the executable instructions to implement the network switching method as described in the above aspects.

According to one aspect of the present application, a computer-readable storage medium is provided, and executable instructions are stored in the readable storage medium, and the executable instructions are loaded and executed by the processor to implement the above-mentioned aspects. network switching method.

The technical solutions provided by the embodiments of the present application include at least the following beneficial effects:

The method provided by the embodiment of the present application can determine the way of switching network slices based on the acquired slice information, and clarifies the specific judgment rules during switching, so as to ensure the smooth progress of the switching process of network slices, prevent the interruption of the switching process, and ensure The continuity of the handover process is improved, thereby improving the accuracy of network handover. In addition, slice remapping or slice rollback can be determined through the slice information, so as to prevent the situation of service discontinuity during the handover process, and ensure the continuity of the service.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application;

FIG. 2 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application;

FIG. 3 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application;

FIG. 4 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application;

FIG. 5 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application;

FIG. 6 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application;

FIG. 7 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application;

FIG. 8 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application;

FIG. 9 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application;

FIG. 10 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.

detailed description

In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

It is understood that the terms "first", "second" and the like used in this application may be used herein to describe various concepts, but these concepts are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another.

First, briefly introduce the terms involved in the embodiments of the present application:

Network slicing technology: It is an on-demand networking technology that can separate multiple virtual end-to-end networks. Each network slice is logically isolated from the wireless access network bearer network to the core network to meet different types of applications. program requirements.

Among them, the network slice consists of a RAN (Radio Access Network, radio access network) part and a CN (Core Network, core network) part.

Slice identification: The radio access network defines an S-NSSAI (Single-Network Slice Selection Assistance Information, single network slice selection assistance information) for each slice. The terminal side maintains an NSSAI, which is an S-NSSAI list, and the terminal supports up to 8 S-NSSAIs.

S-NSSAI consists of SST (Slice/Service Type, slice or service type) and SD (Slice Differentiator, slice group). SST represents the service type, and SD represents different terminal groups served under the same service type.

Optionally, the slice identifier may also be in other forms, such as a network slice identifier NSID (Network slice Identification, network slice identification number) and the like. There are no restrictions here.

The switching process consists of three steps:

(1) Handover preparation: the source base station configures the terminal to perform measurement reporting, and sends a handover request message to the target base station based on the reporting result of the terminal. The handover request message carries PDU (Packet Data Unit, packet data unit) session related information. The PDU session related information includes slice information and QoS (Quality of Service, quality of service) flow (flow) level QoS configuration information. The target base station performs access control. When the target base station corresponding to the PDU session in the handover request message does not support slicing, the target base station will reject the PDU session. After the target base station agrees to the handover request, an RRC (Radio Resource Control, Radio Resource Control) message is configured for the terminal.

Among them, the RRC message includes resources for RACH (Random Access Channel, random access channel), C-RNTI (Cell Radio Network Temporary Identifier, cell wireless network temporary identifier), target base station security algorithm and target base station system messages, etc. .

(2) Handover execution: the source base station forwards the RRC message to the terminal, and after receiving the handover command, the terminal initiates a random access procedure to the target base station. At the same time, the source base station will send SN (Secondary Node, secondary node) state transition information to the target base station, which is used to inform the target base station of the uplink PDCP SN reception status and the downlink PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol) SN transmission status.

(3) Handover completion: When the terminal successfully accesses the target base station, the target base station will send a path switching request, requesting the MME (Mobility Management Entity) to switch the downlink path. After the path switching is completed, the target base station will instruct the source base station to release the Terminal context, the switch is complete.

FIG. 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application. The communication system may include: an access network 12 and a terminal 13 .

The access network 12 includes several network devices 120 . The network device 120 may be a base station, which is a device deployed in an access network to provide a wireless communication function for a terminal. The base station may include various forms of macro base station, micro base station, relay station, access point and so on. In systems using different radio access technologies, the names of devices with base station functions may be different. For example, in LTE systems, they are called eNodeBs or eNBs; in 5G NR-U systems, they are called gNodeBs or gNBs. . As communication technology evolves, the description of "base station" may change. For the convenience of the embodiments of the present application, the above-mentioned apparatuses for providing the terminal 13 with a wireless communication function are collectively referred to as access network equipment.

The terminal 13 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to the wireless modem, as well as various forms of user equipment, mobile stations (Mobile Station, MS), Terminal (terminal device) and so on. For the convenience of description, the devices mentioned above are collectively referred to as terminals. The access network device 120 and the terminal 13 communicate with each other through a certain air interface technology, such as a Uu interface.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (TDD) systems, Advanced long term evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE on unlicensed frequency bands (LTE-based access to unlicensed spectrum, LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication and Vehicle to Everything (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

FIG. 2 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application, which is applied to the network device shown in FIG. 1 , and the method includes at least part of the following contents:

Step 201: Obtain slice information.

The slice information is used to indicate information corresponding to the slice network. The slice information is used for the network device to determine the switching behavior of switching network slices.

And, the slice information includes at least one of the following:

(1) Equivalent slice or equivalent slice group.

The equivalent slice group includes multiple equivalent slices. Each equivalent slice can handle the same business. Moreover, each equivalent slice corresponds to a service.

(2) default (default) slice or default slice group.

The default slice group includes multiple default slices. The default slice is used to process services or non-services at the system message level, or the default slice may also be a slice corresponding to a service that must be supported or a PDU session.

(3) Slicing support capability of the target base station.

(4) Slice identifiers supported by the source base station.

Wherein, the slice identifier is used to indicate a network slice. Different network slices correspond to different slice identifiers. Optionally, the slice identifier is an ID (Identification, identification number) of the network slice, or other methods are used to identify the network slice.

And the source base station can support different services, and different services correspond to different network slices, then the source base station supports multiple network slices, and each network slice corresponds to a slice identifier.

(5) The slice identifier corresponding to the PDU session currently established by the terminal.

When the terminal is located in a cell, it will establish a PDU session with the source base station in the cell, and the PDU session corresponds to a slice identifier.

(6) Slice identifiers supported by the target base station.

The slice identifier supported by the target base station is similar to the slice identifier supported by the source base station, and details are not described herein again.

(7) The slice identifier corresponding to the PDU session that the target base station allows the terminal to establish.

When the terminal is located in the cell of the target base station, it can establish a PDU session with the target base station, and the target base station can allow the terminal to establish a PDU session supported by the target base station, and the PDU session corresponds to a slice identifier.

(8) The terminal slice identifier allowed by the target base station.

When the terminal needs to switch networks, the slice identifier of the sliced network slice needs to be determined, and the target base station also has the slice identifier of the allowed network slice, then the terminal slice identifier allowed by the target base station can be determined.

(9) The service corresponding to the slice identifier.

Each network slice corresponds to one type of service, so not only the slice identifier of the network slice can be determined, but also the service corresponding to the slice identifier can be determined.

(10) The group to which the slice belongs.

Each network slice has a group to which it belongs, and the configuration information can include the group to which the slice belongs, and then the group to which the slice belongs can be determined based on the slice information. In some cases, the slices in the group to which the slice belongs can communicate with each other, or the services can be replaced to a certain extent, or belong to the same type of services.

(11) An identifier corresponding to whether the equivalent slice or equivalent slice group of the target base station supports it.

The target base station configures and establishes an equivalent slice or an equivalent slice group. Based on the equivalent slice or equivalent slice group, it can determine whether to support the PDU session to be switched, and then it can be determined by identifying the equivalent slice or equivalent slice group. Whether to support the PDU session to be switched.

(12) Whether the equivalent slice or equivalent slice group corresponding to the target base station establishes a session.

The target base station configures and establishes an equivalent slice or an equivalent slice group, and can determine whether the equivalent slice or equivalent slice group has established a session, and then determine that the equivalent slice or equivalent slice group can support the session to be switched.

(13) The flag corresponding to whether the default slice of the target base station is supported.

(14) Whether a session is established corresponding to the default slice of the target base station.

(15) Whether the PDU session or slice to be switched has the requirement or indication of switching service continuity.

Among them, the business continuity means that the business needs to be continuously executed, and the business cannot be interrupted, while some services do not need to be continuously executed and can be interrupted. The service corresponding to each PDU session or slice has a requirement or indication of service continuity.

(16) Whether the PDU session or slice that needs to be handed over but not supported by the target base station is a service or slice guaranteed by priority.

Optionally, the slice information is configured by OAM (Operation Administration and Maintenance, operation maintenance management), or indicated or determined by AMF (Access and Mobility Management Function, access and mobility management entity), or, by NSSP (networkslicing selection policy) , the network slice selection strategy) is determined.

In a possible implementation manner, after the slice information is configured in the OAM, the OAM is sent to the base station, or sent to the base station or the core network through interaction between the base stations. Alternatively, after the AMF configures the slice information, the AMF is sent to the base station, or sent to the base station or the core network through interaction between the base stations. Alternatively, after the NSSP determines the slice information, the NSSP is sent to the base station, or sent to the base station or the core network through interaction between base stations. Or, after the NSSP determines the slice information, the NSSP sends it to the OAM, the OAM sends it to the base station, or sends it to the base station or the core network through the interaction between the base stations. Alternatively, when the OAM or AMF or NSSP receives the request for the exchange of slice information, it sends the handover information to the requesting entity.

Optionally, the network device includes any one of AMF, SMF (Session management Function, session management entity), LTE (Long Term Evolution, Long Term Evolution) base station, and NR base station.

In addition, when the network device is an AMF, the AMF is a source AMF or a target AMF. When the network device is an SMF, the SMF is the source SMF or the target SMF. When the network device is an LTE base station, the LTE base station is a source LTE base station or a target LTE base station. When the network device is an NR base station, the NR base station is a source NR base station or a target NR base station.

Optionally, before acquiring the slice information, the network device receives a handover request sent by the terminal, where the handover request is used to indicate that the terminal needs to switch network slices, the network device acquires the slice information, and determines a method of switching network slices based on the slice information.

Optionally, the network device may also receive a handover request sent by the terminal when acquiring the slice information or after acquiring the slice information, where the handover request is used to indicate that the terminal needs to switch the network slice, then the network device acquires the slice information, and determines based on the slice information. Toggles the way of network slicing.

In a possible implementation manner, when the terminal is in a moving state, if the terminal moves from the current cell to another cell, the terminal sends a handover request to the network device, and the network device executes step 201 .

Step 202: Determine the switching behavior according to the slice information.

The switching behavior is used to indicate the manner in which the switching of the slice network is completed. After the network device receives the slice information, it will determine the handover behavior according to the received slice information, and then perform subsequent operations according to the determined handover behavior.

Optionally, the switching behavior includes at least one of the following:

(1) Switch to reject or not accept.

The handover rejection or non-acceptance is used to indicate that the network device cannot allocate radio resources of the network that needs to be handed over to the terminal.

(2) Toggle Support or Accept.

Wherein, the handover support or reception is used to execute the radio resource that the network device can allocate the network to be handed over to the terminal, and then execute the handover step.

(3) Switch and slice remapping.

Wherein, handover and slice remapping is used to indicate that in the process of performing handover, slice remapping also needs to be performed, so that the remapped network slice can meet the handover requirement.

(4) Switch and slice back.

The switch and slice rollback is used to indicate that in the process of performing the handover, a process of slice rollback needs to be performed, so that the network slice after the slice rollback can meet the switching requirements.

Optionally, when the network device performs step 202, the network device is at least one of AMF, SMF, LTE base station, and NR base station.

In addition, optionally, before determining the above switching behavior, at least one of the following switching behaviors can also be determined:

(1) Trigger handover based on N2 interface or trigger handover based on Xn interface.

In the embodiment of the present application, when the handover is triggered, the handover based on the N2 interface or the handover based on the Xn interface can be triggered.

The handover based on the N2 interface is that the source base station notifies the AMF through the N2 interface to execute the triggering handover process.

In the handover based on the Xn interface, the source base station notifies the target base station through the Xn interface to execute the triggering handover process.

(2) Whether to send a handover request.

Wherein, the network device can determine whether to send a handover request based on the received slice information, and then determine whether to execute the handover process.

(3) Whether to request slice remapping;

Wherein, the network device can determine whether to request slice remapping based on the received slice information, and then can perform the handover process.

(4) Whether to request slice rollback.

Wherein, the network device can determine whether to request a slice rollback based on the received slice information, and then can perform the handover process.

In addition, in this embodiment of the present application, when determining whether to execute the handover procedure based on the N2 interface or the handover procedure based on the Xn interface, at least one of the following handover behaviors is included:

(1) During the handover process of the slice, the handover based on the N2 interface is triggered.

During the handover process of the slice, only the handover based on the N2 interface is triggered, and other types of handover are not performed.

(2) During the handover process of the slice, when the slice does not support or does not support slice remapping or does not support slice fallback and the Xn interface-based handover fails, trigger the N2 interface-based handover.

(3) During the handover process of the slice, the handover based on the Xn interface and the handover based on the N2 interface are triggered.

Optionally, in this embodiment of the present application, when a process of slice remapping or rollback is involved, determining whether to perform a handover process based on an N2 interface or a handover process based on an Xn interface includes at least one of the following handover behaviors:

(1) In the process of slice remapping or rollback, the handover based on the N2 interface is triggered.

(2) In the process of slice remapping or fallback, when the slice does not support or does not support slice remapping or does not support slice fallback and the Xn interface-based handover fails, trigger the N2 interface-based handover.

(3) In the process of slice remapping or rollback, the handover based on the Xn interface and the handover based on the N2 interface are triggered.

Optionally, when the slice behavior is determined based on the slice information, the handover information can be determined based on the reference rule, then step 202 includes step 2021 : determine the handover behavior based on the reference rule and the slice information.

Wherein, the reference rule is set by the network device itself, or set by the operator, or set by other methods.

In addition, the reference rule includes at least one of the following:

(1) The slice identifier supported by the target base station is the same as the slice identifier required by the source base station to be handed over, then the handover is supported or the handover is accepted.

Among them, if the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, it means that the target base station includes the network slice corresponding to the network slice to be switched, and can allocate radio resources for the network slice, and determine whether the switch supports or accepts the switch. .

(2) If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, the switch is rejected or rejected.

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, it means that the target base station does not include the network slice corresponding to the network slice to be switched, and radio resources cannot be allocated for the network slice. .

(3) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the target base station has acquired or configured or supported or established the equivalent slice/equivalent slice group of the slice corresponding to the session requiring handover. slice, toggle support or accept; or, toggle and slice remapping.

If the slice identifier supported by the target base station is different from the slice identifier that the source base station requires to be handed over, it means that the target base station does not include the network slice corresponding to the network slice to be handed over, but the target base station has acquired or configured or supported or established the required handover. The equivalent slice of the slice corresponding to the session/slice in the equivalent slice group indicates that the target base station can allocate radio resources for the session requiring handover, determine handover support or reception, or handover and slice remapping.

(4) The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, and the services corresponding to the slice identifier are different, the handover is not supported or rejected.

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, it means that the target base station does not include the network slice corresponding to the network slice to be switched, and the service corresponding to the slice identifier supported by the target base station is the same as that required by the source base station. When the services corresponding to the slice identifiers are different, it means that the target base station cannot allocate network resources for the slice corresponding to the handover identifier that requires handover, and determines that the handover is not supported or rejected.

(5) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the service corresponding to the slice identifier is the same, then the switch supports or accepts; or, the switch is performed and the slice is remapped.

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, it means that the target base station does not include the network slice corresponding to the network slice to be switched, but the service corresponding to the slice identifier supported by the target base station is the same as that required by the source base station. When the services corresponding to the slice identifiers are the same, it means that the target base station can allocate network resources to the slice corresponding to the slice identifier requiring handover, determine handover support or acceptance, or switch and slice remapping.

(6) The slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, but the target base station does not acquire or configure or does not support or establish the equivalent slice/equivalent slice group of the slice corresponding to the session requiring handover within slices, the toggle is not supported or rejected.

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, it means that the target base station does not include the network slice corresponding to the network slice to be handed over, and the target base station has not acquired or configured it or does not support it or has not established the required network slice. The equivalent slice of the slice corresponding to the handover session/slice in the equivalent slice group indicates that the target base station cannot allocate network resources for the slice corresponding to the required slice identifier at this time, and determines that the handover is not supported or rejected.

(7) The slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, but the target base station does not acquire or configure or does not support or establish the equivalent slice/equivalent slice group of the slice corresponding to the session requiring handover If there are slices within, the toggle supports or accepts; or, toggles and the slice falls back.

If the slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, it means that the target base station does not include the network slice corresponding to the network slice to be handed over, but the target base station has not acquired or configured it or does not support it or has not established the required network slice. The target base station can also allocate network resources for the slice corresponding to the slice identifier that requires the handover, and determine whether the handover is supported or accepted, or the handover and slice fallback.

(8) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target base station has acquired or configured or supported or established a slice in the default slice/default slice group of the slice corresponding to the session requiring handover, then toggle support or accept; alternatively, toggle and slice fallback.

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, it means that the target base station does not include the network slice corresponding to the network slice to be switched. The default slice of the slice corresponding to the session corresponding to the default slice/the slice in the default slice group indicates that the target base station can allocate the radio resources of the corresponding slice for the session requiring handover, and determine the handover support or acceptance; or, the handover and the slice fallback.

(9) The slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, and the target base station does not acquire or configure or does not support or establish the equivalent slice/equivalent slice group of the slice corresponding to the session requiring handover If the target base station has acquired or configured or supported or established a slice in the default slice/default slice group of the slice corresponding to the session requiring handover, the handover supports or accepts; or, the handover and the slice fall back.

Among them, if the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, it means that the target base station does not include the network slice corresponding to the network slice to be switched, but if the target base station does not acquire or configure it or does not support or does not The equivalent slice/slice within the equivalent slice group of the slice corresponding to the session that requires switching is established, and the default slice/default slice group of the slice corresponding to the session requiring switching has been acquired or configured or supported or established, It means that the target base station can allocate radio resources of the corresponding slice for the session requiring handover, and determine whether the handover is supported or accepted; or, the handover and the slice fall back.

(10) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target base station does not acquire or configure or does not support or establish the default slice/default slice group of the slice corresponding to the session requiring handover. slicing, the toggle is not supported or rejected.

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, it means that the target base station does not include the network slice corresponding to the network slice to be handed over. The default slice/slice in the default slice group of the slice corresponding to the session requiring handover indicates that the target base station cannot allocate radio resources of the corresponding slice for the session requiring handover, and determines that handover is not supported or rejected.

(11) The slice identifier supported by the target base station is the same as the slice identifier required by the source base station to switch, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the equivalent of the slice corresponding to the session requiring handover Slices within a slice/equivalent slice group, switch support or accept; or, switch and slice remapping.

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, it means that the target base station includes the network slice corresponding to the network slice to be switched, but the target slice reaches the access threshold. Configure, support or establish the equivalent slice of the slice corresponding to the session requiring handover/slice in the equivalent slice group, then it can be determined that the target base station can allocate the radio resources of the corresponding slice for the session requiring handover, and determine the handover support Either accept, or toggle and slice remap.

(12) The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the default slice/ For the slices in the default slice group, switch to support or accept; or, switch and fall back to the slice.

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, it means that the target base station includes the network slice corresponding to the network slice to be switched, but the target slice reaches the access threshold. Configure, support or establish the default slice/slice in the default slice group of the slice corresponding to the session requiring handover, then it can be determined that the target base station can allocate the radio resources of the corresponding slice for the session requiring handover, and determine whether the handover is supported or accepted; Alternatively, switch and slice back.

(13) The slice identifier supported by the target base station is the same as the slice identifier that the source base station requires for handover, and the target slice reaches the access threshold, and the target base station does not acquire or configure or does not support or establish a slice corresponding to the session requiring handover. If the target base station has acquired or configured or supported or established the default slice/slice in the default slice group of the slice corresponding to the session requiring handover, the handover supports or accepts; or , toggle and slice back.

Based on the description in (12), even if the target base station does not acquire or configure or does not support or establish the equivalent slice of the slice corresponding to the session requiring handover/slice within the equivalent slice group, but the target base station has acquired or configured or supports or establishes the default slice/slice in the default slice group of the slice corresponding to the session that requires the switch, then the switch supports or accepts; or, the switch and the slice rolls back.

(14) The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or accepts; or , toggle and slice back.

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, it means that the target base station includes the network slice corresponding to the network slice to be switched, but the target slice and the equivalent slice/equivalent slice group corresponding to the target slice If the slice reaches the access threshold, the target base station can also allocate radio resources of the corresponding slice for the session requiring handover, and determine whether the handover is supported or accepted; or, the handover and the slice fall back.

(15) The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, and the target base station has obtained or configured or If the default slice/default slice group of the slice corresponding to the session requiring switching is supported or established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, indicating that the target base station includes the network slice corresponding to the network slice to be switched, but the target slice and the equivalent slice/equivalent slice group corresponding to the target slice. If the slice reaches the access threshold, radio resources cannot be allocated to the slice requiring handover only based on the equivalent slice or equivalent slice group, but if the target base station has acquired or configured or supported or established a slice corresponding to the session requiring handover If the default slice/default slice group is based on the default slice/default slice group, if radio resources can be allocated to the slice that requires switching, then the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

(16) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, and the target base station has obtained or configured or If the default slice/default slice group of the slice corresponding to the session requiring switching is supported or established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but the target slice and the equivalent slice/equivalent slice group corresponding to the target slice are included in the target base station. At this time, only the equivalent slice or equivalent slice group cannot allocate radio resources for the slice requiring handover, but if the target base station has acquired or configured or supported or established a session corresponding to the required handover For the slices in the default slice/default slice group of the slice, based on the default slice/default slice group, if radio resources can be allocated to the slice that requires switching, then the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

(17) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or accepts; or , toggle and slice back.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but the target slice and the equivalent slice/equivalent slice group corresponding to the target slice are included in the target base station. If the slice reaches the access threshold, at this time, radio resources can be allocated to the slice that requires switching based on the equivalent slice or equivalent slice group, and the switch is supported or accepted; or, the switch is performed and the slice is rolled back.

(18) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but if the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the handover is not supported or rejected.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but the target slice and the equivalent slice/equivalent slice group corresponding to the target slice are included in the target base station. If the slice reaches the access threshold, and the radio resource cannot be allocated to the slice requiring handover based on the equivalent slice or equivalent slice group at this time, the handover is not supported or rejected.

(19) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, then the handover supports or accepts; and the slice is rolled back; or, toggled and the slice is remapped.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but because the target slice is a slice that has the requirement of handover service continuity or is prioritized Guaranteed services/slices, the target base station needs to allocate network resources for the network slice to be handed over, and then determines whether the handover is supported or accepted; or, handover and slice rollback; or, handover and slice remapping.

(20) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice with priority guarantee, and the target base station has acquired or configured or supported it Or if an equivalent slice of the slice corresponding to the session requiring switching is established/a slice within an equivalent slice group, the switch is supported or accepted; or, the switch is performed and the slice is remapped.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but because the target slice is a slice that has the requirement of handover service continuity or is prioritized Guaranteed service/slice, and the target base station has acquired or configured or supported or established the equivalent slice of the slice corresponding to the session requiring handover/slice within the equivalent slice group, indicating that the target base station can allocate the network slice to be handed over Network resources, determine handover support or acceptance; or, handover and slice remapping.

(21) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has not acquired or configured it or If the equivalent slice of the slice corresponding to the session requiring switching is not supported or the slice in the equivalent slice group is not established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, and the target base station has not acquired or configured or does not support or does not establish and require handover. The equivalent slice of the slice corresponding to the current session/slice in the equivalent slice group, but the target slice is a slice with the requirement of handover service continuity or a service/slice with priority guarantee, the target base station can provide the network slice to be handed over in order to ensure Allocate network resources and determine handover support or acceptance; or, handover and slice fallback.

(22) The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice with priority guarantee, and the target base station has acquired or configured or supported it Or if the default slice/default slice group of the slice corresponding to the session requiring switching is established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, indicating that the target base station does not include the network slice corresponding to the network slice to be switched, but the target slice is a slice with the requirement of handover service continuity or a priority guarantee and the target base station has acquired or configured or supported or established the default slice/slice in the default slice group of the slice corresponding to the session requiring handover, then the target base station can allocate network resources for the network slice to be handed over, Determine toggle support or acceptance; alternatively, toggle and slice fallback.

It should be noted that, in this embodiment of the present application, if it is determined that handover and slice fallback or handover and slice remapping are performed, the AMF, SMF, source base station, and target base station in the network device perform slice fallback or slice remapping to ensure that Implement PDU session switching.

Step 203: Execute a handover process according to the determined handover behavior.

Wherein, after the network device determines the handover behavior, it can further determine the subsequent handover process.

In this embodiment of the present application, the handover behavior includes any one of handover support or acceptance, slice rollback or slice remapping, or handover rejection or non-support.

Optionally, when the network device determines that the handover is supported or accepted, the steps of handover execution and handover completion are performed.

In addition, in this embodiment of the present application, slice rollback or slice remapping can also be determined, and then the handover type can be determined.

Optionally, when the slice rolls back or the slice is remapped, the handover based on the N2 interface is triggered; or,

When the slice rolls back or slice remapping, the handover based on the Xn interface is triggered, and when it is determined that the handover is rejected or the target base station cannot support the slice rollback or slice remapping, the handover based on the N2 interface is triggered.

Optionally, when it is determined that the slice is rejected or the slice is not supported, the handover is rejected.

The method provided by the embodiment of the present application can determine the way of switching network slices based on the acquired slice information, clarifies the specific judgment rules during switching, ensures that the switching process of network slices is performed smoothly, prevents the interruption of the switching process, and ensures that the switching process is interrupted. The continuity of the handover process is improved, thereby improving the accuracy of network handover. In addition, slice remapping or slice rollback can be determined through the slice information, so as to prevent the situation of service discontinuity during the handover process, and ensure the continuity of the service.

FIG. 3 shows a flowchart of a network switching method provided by an exemplary embodiment of the present application, which is applied to the network device shown in FIG. 1 , and the method includes at least part of the following contents:

Step 301: The first entity acquires slice information.

Step 302: The first entity determines the handover behavior based on the slice information.

The processes in steps 301-302 are similar to the above-mentioned steps 201-202, and are not repeated here.

Step 303: When the first entity determines that the switching behavior includes slice remapping or slice rollback, it sends the indication information of slice remapping or slice rollback to the second entity.

When the first entity determines that the switching behavior includes slice remapping or slice rollback, it indicates that it is determined to perform handover and slice remapping or slice rollback at this time, and further instructs the second entity to perform subsequent steps.

It should be noted that, the first entity in this embodiment of the present application is the source base station. And the source base station is an LTE base station or an NR base station.

Step 304, the second entity performs handover and slice remapping or slice rollback.

After receiving the indication information sent by the first entity, the second entity starts to perform the process of handover and slice remapping or slice rollback.

Optionally, the second entity is any one of AMF, SMF, NR base station, and LTE base station.

In the method provided by this embodiment of the present application, the first entity determines the handover behavior according to the slice information, and further instructs the second entity to perform the subsequent handover process, the first entity can determine the handover method, the second entity can perform the handover process, and through the interaction of multiple entities Executing the handover process ensures the accuracy of the judged handover mode, and through slice remapping or slice rollback, the smooth execution of the handover can be ensured, thereby ensuring service continuity.

It should be noted that, the embodiments of the present application are only described by taking the first entity determining the handover behavior based on the slice information and instructing the second entity to perform the handover process as an example. In another embodiment, after receiving the instruction of the first entity, the second entity can continue to determine the handover behavior based on the slice information.

In the method provided by the embodiment of the present application, the second entity can continue to determine the handover behavior based on the slice information, and further make judgment based on the slice information, which improves the accuracy of the judgment of the handover process and further ensures the continuity of the service.

Fig. 4 shows a flowchart of a network handover method provided by an exemplary embodiment of the present application, which is applied to the network device shown in Fig. 1, and when the network device includes AMF, SMF, source base station, and target base station, the The method includes at least some of the following:

Step 401, the AMF determines the handover behavior based on the slice information.

Step 402: When the AMF determines that the handover behavior includes handover remapping or handover rollback, the AMF sends a request to update the session management context to the SMF.

Wherein, the update session management context request includes PDU session remapping or rollback, the reason for remapping or rollback, and the indication of PDU Session Is To Be remapping or rollback (and remapping or rollback Cause). Optionally, for the PDU session to be remapped or rolled back, the SMF will trigger the PDU session modification/establishment process to modify/add the remapped or rolled back PDU session.

Step 403 , the SMF sends a response of updating the session management context to the AMF.

Wherein, the update session management context response is used to indicate that the PDU session list remapping or rollback is successful.

Step 404, the AMF sends a handover request to the target base station.

Wherein, the handover request includes PDU session remapping or rollback, and the reason for the remapping or rollback.

Step 405: The target base station sends a handover request confirmation instruction to the AMF.

Wherein, the handover request confirmation instruction includes PDU session remapping or rollback, and the reason for the remapping or rollback.

In addition, the handover request confirmation instruction further includes the data forwarding channel of the PDU session that needs to be remapped or rolled back.

Step 406: The AMF sends a request for updating the session management context to the SMF.

Wherein, the update session management context request is used to update the information of the SMF based on the result of the target base station.

Step 407 , the SMF sends a response of updating the session management context to the AMF.

Step 408, the AMF sends a handover instruction to the source base station.

Wherein, the handover instruction includes PDU session remapping or rollback, and the reason for the remapping or rollback.

Step 409: The source base station sends a handover instruction to the UE.

Step 410: The source base station forwards the data packet corresponding to the source PDU session to the target base station through the data forwarding channel.

It should be noted that, the embodiments of the present application only take the operations performed when the AMF determines that the handover behavior includes handover remapping or handover rollback as an example for description. In another embodiment, when the AMF determines that the handover behavior is handover unsupported or rejected, the handover behavior further includes at least one of the following:

(1) The AMF informs the source base station that the handover preparation fails.

Optionally, the AMF notifies the source base station of the reason why the slice remapping fails, or the slice rollback fails, or the slice is not supported.

(2) If the AMF determines that handover is supported or accepted, or handover and slice remapping, or handover and slice rollback, AMF continues the existing handover process and notifies SMF and other entities of slice remapping/slice rollback information.

(3) If the AMF judges that the slice is not supported, the AMF continues the existing process, but notifies the target base station that the slice is not supported.

The target base station generates information that the slice does not support, and notifies the source base station of the information that the slice does not support through the AMF.

Wherein, the AMF determines that the handover is not supported or the handover is rejected, including not supporting slices, not supporting handover remapping, not supporting slice fallback, and the like.

It should be noted that the embodiment of the present application only takes the handover based on the N2 interface as an example for description, and in another embodiment, the handover can also be performed based on the Xn interface, which will not be repeated here.

FIG. 5 shows a flowchart of a network handover method provided by an exemplary embodiment of the present application, which is applied to the network device shown in FIG. 1 , and when the network device includes AMF, SMF, source base station, and target base station, the The method includes at least some of the following:

Step 501: The source base station determines the handover behavior based on the slice information.

Step 502: When the source base station determines that the handover behavior includes slice remapping or slice rollback, it sends a handover request to the AMF.

Step 503: The AMF sends a request for updating the session management context to the SMF.

Step 504, the SMF sends a response to the update session management context to the AMF.

Step 505, the AMF sends a handover request to the target base station.

Step 506: The target base station sends a handover request confirmation instruction to the AMF.

Step 507: The AMF sends a request for updating the session management context to the SMF.

Step 508 , the SMF sends a response of updating the session management context to the AMF.

Step 509, the AMF sends a handover instruction to the source base station.

Step 510: The source base station sends a handover instruction to the UE.

Step 511: The source base station forwards the data packet corresponding to the source PDU session to the target base station through the data forwarding channel.

FIG. 6 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application, and the apparatus includes:

an obtaining module 601, configured to obtain slice information, where the slice information is used to indicate information corresponding to the slice network;

The determining module 602 is configured to determine a switching behavior according to the slice information, where the switching behavior is used to indicate a way of switching the network slice.

In one example, the switching behavior includes at least one of the following:

Toggle reject or not accept;

toggle support or acceptance;

switch and slice remapping;

Toggle and slice back.

In one example, the handover behavior is determined by any of AMF, SMF, NR base stations, LTE base stations.

In one example, the switching behavior includes at least one of the following:

Trigger handover based on N2 interface or trigger handover based on Xn interface;

Whether to send a handover request;

Whether to request slice remapping;

Whether to request slice fallback.

In one example, the switching behavior further includes at least one of the following:

During the handover process of the slice, the handover based on the N2 interface is triggered; during the handover process of the slice, when the handover based on the Xn interface fails due to the slice does not support or does not support slice remapping or does not support slice fallback, the N2 interface-based handover is triggered interface switching;

During the handover process of the slice, the handover based on the Xn interface and the handover based on the N2 interface are triggered.

In one example, the determining module 602 is configured to determine the handover behavior based on the reference rule and slice information.

In one example, the switching behavior is determined based on the reference rule and slice information, including at least one of the following:

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, the switch supports or accepts the switch;

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, the handover is rejected or not accepted;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the target base station has acquired or configured or supported or established an equivalent slice of the slice corresponding to the session requiring handover/a slice in an equivalent slice group, then toggle support or accept; or, toggle and slice remapping;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the services corresponding to the slice identifier are different, the handover is not supported or rejected;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the service corresponding to the slice identifier is the same, the switch supports or accepts; or, the switch is performed and the slice is remapped;

The slice ID supported by the target base station is different from the slice ID required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish the equivalent slice of the slice corresponding to the session requiring handover/slice within the equivalent slice group , the switch is not supported or rejected;

The slice ID supported by the target base station is different from the slice ID required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish the equivalent slice of the slice corresponding to the session requiring handover/slice within the equivalent slice group , then switch support or accept; or, switch and slice fallback;

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, but the target base station has acquired or configured or supported or established the slice corresponding to the session requiring switch to the default slice/default slice group, the switch supports the switch. or accept; or, switch and slice back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the target base station does not acquire or configure or does not support or establish an equivalent slice of the slice corresponding to the session requiring handover/a slice in an equivalent slice group , but the target base station has acquired or configured or supported or established the default slice/default slice group of the slice corresponding to the session requiring handover, then the handover is supported or accepted; or, the handover and the slice rollback;

If the slice ID supported by the target base station is different from the slice ID required by the source base station to switch, but the target base station does not acquire or configure or does not support or establish a slice corresponding to the session requiring handover, the default slice/default slice group of the slice is not established, then Toggle not supported or rejected;

The slice identifier supported by the target base station is the same as the slice identifier that the source base station requires to be handed over, but the target slice reaches the access threshold, the target base station has acquired or configured, supported or established the equivalent slice of the slice corresponding to the session requiring handover/etc. Slices in the valence slice group, switch support or accept; or, switch and slice remapping;

The slice identifier supported by the target base station is the same as the slice identifier required by the source base station to switch, but the target slice has reached the access threshold, and the target base station has acquired or configured or supported or established the default slice/default slice group of the slice corresponding to the session requiring handover If there are slices within, switch to support or accept; or, switch and fall back to slices;

The slice identifier supported by the target base station is the same as the slice identifier required by the source base station to be handed over, and the target slice reaches the access threshold, and the target base station does not obtain or configure or does not support or establish an equivalent slice of the slice corresponding to the session requiring handover /Slices in the equivalent slice group, but the target base station has acquired or configured or supported or established the default slice of the slice corresponding to the session requiring handover/Slices in the default slice group, the handover supports or accepts; or, the handover and slice fallback;

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the switch supports or accepts; slice fallback;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, and the target base station has acquired or configured or supported or established If the default slice/default slice group of the slice corresponding to the session that requires switching is found, the switch supports or accepts; or, the switch and the slice rolls back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, and the target base station has acquired or configured or supported or established If the default slice/default slice group of the slice corresponding to the session that requires switching is found, the switch supports or accepts; or, the switch and the slice rolls back;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the switch supports or accepts; slice fallback;

If the slice identifier supported by the target base station is different from the slice identifier required by the source base station to switch, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the handover is not supported or rejected;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice with priority guarantee, then the handover supports or accepts; back; or, switch and slice remapping;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or supported or established The equivalent slice of the slice corresponding to the session that requires switching/a slice in an equivalent slice group, then the switch supports or accepts; or, switch and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has not acquired or configured it or does not support it or If the equivalent slice of the slice corresponding to the session that requires switching is not established/a slice in an equivalent slice group, the switch is supported or accepted; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or supported or established If the slice corresponding to the session requiring switching is the default slice/the slice in the default slice group, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

In one example, the slice information includes at least one of the following:

Equivalent slice or equivalent slice group;

default slice or default slice group;

The slice support capability of the target base station;

Slice identifiers supported by the source base station;

The slice identifier corresponding to the PDU session currently established by the terminal;

The slice identifier supported by the target base station;

The slice identifier corresponding to the PDU session that the target base station allows the terminal to establish;

UE slice identifier allowed by the target base station;

The business corresponding to the slice identifier;

the group to which the slice belongs;

Indicates whether the equivalent slice or equivalent slice group corresponding to the target base station supports it;

The equivalent slice or equivalent slice group corresponding to the target base station is to establish a session;

Indicates whether the default slice or default slice group of the target base station supports it;

Whether the default slice or default slice group corresponding to the target base station establishes a session;

Whether the PDU session or slice that needs to be switched has the requirement or indication of switching service continuity;

Whether the PDU session or slice that needs to be handed over but is not supported by the target base station is a prioritized service or slice.

In one example, the slice information is configured by the OAM, or indicated/determined by the AMF, or determined by the NSSP.

In one example, referring to FIG. 7 , the apparatus further includes:

a triggering module 603, configured to trigger switching based on the N2 interface when the slice rolls back or the slice is remapped; or,

The triggering module 603 is further configured to trigger the handover based on the Xn interface when the slice rolls back or the slice remapping, and trigger the handover based on the N2 interface when it is determined that the handover is rejected or the target base station cannot support the slice rollback or the slice remapping.

FIG. 8 shows a block diagram of a network switching apparatus provided by an exemplary embodiment of the present application, which is applied to the first entity, and the apparatus includes:

an obtaining module 801, configured to obtain slice information, where the slice information is used to indicate information corresponding to the slice network;

The determining module 802 is configured to determine a switching behavior according to the slice information, where the switching behavior is used to indicate a way of switching the network slice.

In one example, the switching behavior includes at least one of the following:

Whether to send a handover request;

Whether to request slice remapping;

Whether to request slice fallback.

During the switching process of the slice, the switching based on the N2 interface is triggered;

In the process of slice switching, when the slice does not support or does not support slice remapping or does not support slice fallback and the Xn interface-based handover fails, trigger the N2 interface-based handover;

In one example, the determining module 802 is configured to determine the handover behavior based on the reference rule and slice information.

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target base station has acquired or configured or supported or established a slice in the default slice/default slice group of the slice corresponding to the session required to be switched, then the switch supports or accept; or, switch and slice back;

The slice identifier supported by the target base station is the same as the slice identifier required by the source base station to be handed over, and the target slice reaches the access threshold, and the target base station does not obtain or configure or does not support or establish an equivalent slice of the slice corresponding to the session requiring handover /Slices in the equivalent slice group, but the target base station has acquired or configured or supported or established the default slice of the slice corresponding to the session requiring handover/Slices in the default slice group, then the handover supports or accepts; or, the handover and slice fallback;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or supported or established The equivalent slice of the slice corresponding to the session that requires switching/a slice in an equivalent slice group, then the switch supports or accepts; or, switch and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or supported or established If the slice corresponding to the session requiring switching is the default slice/the slice in the default slice group, the switch is supported or accepted; or, the switch is switched and the slice is rolled back.

In one example, the slice information includes at least one of the following:

Equivalent slice or equivalent slice group;

default slice or default slice group;

The slice support capability of the target base station;

Slice identifiers supported by the source base station;

The slice identifier supported by the target base station;

UE slice identifier allowed by the target base station;

The business corresponding to the slice identifier;

the group to which the slice belongs;

In an example, the first entity is any one of an NR base station and an LTE base station.

In one example, referring to FIG. 9, the apparatus further includes:

A sending module 803, configured to send the indication information of slice remapping or slice fallback to a second entity when it is determined that the handover behavior includes slice remapping or slice fallback, and the second entity is used to perform slice remapping or slice fallback based on the indication information go back.

In one example, the second entity is any one of AMF, SMF, NR base station, and LTE base station.

FIG. 10 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application. The communication device (network device) includes: a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 and a bus 1005 .

The processor 1001 includes one or more processing cores, and the processor 1001 executes various functional applications and information processing by running software programs and modules.

The receiver 1002 and the transmitter 1003 may be implemented as a communication component, which may be a communication chip.

The memory 1004 is connected to the processor 1001 through the bus 1005 .

The memory 1004 may be configured to store at least one instruction, and the processor 1001 may be configured to execute the at least one instruction to implement various steps in the above method embodiments.

Additionally, memory 1004 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Static Anytime Access Memory (SRAM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Programmable Read Only Memory (PROM) .

In an exemplary embodiment, a computer-readable storage medium is also provided, and executable instructions are stored in the readable storage medium, and the executable instructions are loaded and executed by the processor to implement the above-mentioned various methods. The example provides a network switching method performed by a communication device.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, etc.

The above descriptions are only optional embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A network switching method, characterized in that the method comprises:

Obtain slice information, where the slice information is used to indicate information corresponding to the slice network;

According to the slice information, a switching behavior is determined, and the switching behavior is used to indicate a way of switching the network slice.
The method according to claim 1, wherein the switching behavior comprises at least one of the following:

Toggle reject or not accept;

toggle support or acceptance;

switch and slice remapping;

Toggle and slice back.
The method according to claim 2, wherein the handover behavior is determined by any one of an access and mobility management entity AMF, a session management entity SMF, a new air interface NR base station, and a long-term evolution LTE base station.
The method according to claim 1, wherein the switching behavior comprises at least one of the following:

Trigger handover based on N2 interface or trigger handover based on Xn interface;

Whether to send a handover request;

Whether to request slice remapping;

Whether to request slice fallback.
The method according to claim 4, wherein the switching behavior further comprises at least one of the following:

During the handover process of the slice, the handover based on the N2 interface is triggered; during the handover process of the slice, when the handover based on the Xn interface fails due to the slice does not support or does not support slice remapping or does not support slice fallback, the N2 interface-based handover is triggered interface switching;

During the handover process of the slice, the handover based on the Xn interface and the handover based on the N2 interface are triggered.
The method according to claim 1, wherein the determining the switching behavior according to the slice information comprises:

The handover behavior is determined based on the reference rule and the slice information.
The method according to claim 6, wherein the determining the switching behavior based on the reference rule and the slice information comprises at least one of the following:

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, the switch supports or accepts the switch;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, the switch is rejected or not accepted;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, and the target base station has acquired or configured or supported or established an equivalent slice/equivalent slice of the slice corresponding to the session requiring handover For slices in the group, switch support or accept; or, switch and slice remapping;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the services corresponding to the slice identifier are different, the switch is not supported or rejected;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the service corresponding to the slice identifier is the same, the switch supports or accepts; or, the switch is performed and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish an equivalent slice of the slice corresponding to the session requiring handover/etc. slices in the valence slice group, the switch is not supported or rejected;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish an equivalent slice of the slice corresponding to the session requiring handover/etc. Slices in the valence slice group, switch to support or accept; or, switch and fall back on slices;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target base station has acquired or configured or supported or established the default slice/default slice group of the slice corresponding to the session requiring the switch. , switch to support or accept; or, switch and fall back to the slice;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, and the target base station does not acquire or configure or does not support or establish an equivalent slice of the slice corresponding to the session requiring handover/etc. If the target base station has acquired or configured or supported or established the default default slice/slice in the default slice group of the slice corresponding to the session requiring handover, the handover supports or accepts; or, handover And the slice rolls back;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, but the target base station has not acquired or configured or does not support or does not establish the default slice/default slice of the slice corresponding to the session requiring handover slices within the group, the switch is not supported or rejected;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the slice corresponding to the session requiring handover The equivalent slice of / the slice in the equivalent slice group, then switch support or accept; or, switch and slice remapping;

The slice identifier supported by the target base station is the same as the slice identifier required to be handed over by the source base station, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the slice corresponding to the session requiring handover. If the slice in the default slice/default slice group is switched to support or accept; or, switch and the slice is rolled back;

The slice identifier supported by the target base station is the same as the slice identifier required to be handed over by the source base station, and the target slice has reached the access threshold, and the target base station has not acquired or configured or does not support or does not establish a session corresponding to the required handover If the target base station has acquired or configured or supported or established the default slice of the slice corresponding to the session requiring handover/a slice in the default slice group, then switch to support or accept; or, toggle and slice fallback;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or Accept; or, switch and slice back;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the target base station If the default slice of the slice corresponding to the session that requires switching has been obtained, configured, supported or established, the switch supports or accepts; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the target base station If the default slice of the slice corresponding to the session that requires switching has been obtained, configured, supported or established, the switch supports or accepts; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or Accept; or, switch and slice back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but if the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the handover is not supported. or refuse;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, then the handover supports or accepts; Slice fallback; or, switch and slice remapping;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or If the equivalent slice of the slice corresponding to the session that requires switching is supported or established, or the slice in the equivalent slice group, the switch supports or accepts; or, the switch is switched and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has not acquired or If the equivalent slice of the slice corresponding to the session that is required to be switched is not configured or not supported or is not established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice with priority guarantee, and the target base station has acquired or If the default slice/default slice group of the slice corresponding to the session required to be switched is configured, supported or established, the switch supports or accepts; or, the switch is switched and the slice is rolled back.
The method according to any one of claims 1-7, wherein the slice information includes at least one of the following:

Equivalent slice or equivalent slice group;

default slice or default slice group;

The slice support capability of the target base station;

Slice identifiers supported by the source base station;

The slice identifier corresponding to the packet data unit PDU session currently established by the terminal;

a slice identifier supported by the target base station;

the slice identifier corresponding to the PDU session that the target base station allows the terminal to establish;

The identifier of the UE slice allowed by the target base station;

the service corresponding to the slice identifier;

the group to which the slice belongs;

An identifier corresponding to whether the equivalent slice or equivalent slice group of the target base station supports it;

The equivalent slice or equivalent slice group corresponding to the target base station is to establish a session;

The identifier corresponding to whether the default slice or default slice group of the target base station supports;

Whether a session is established corresponding to the default slice or default slice group of the target base station;

Whether the PDU session or slice that needs to be switched has the requirement or indication of switching service continuity;

Whether the PDU session or slice that needs to be handed over but is not supported by the target base station is a prioritized service or slice.
The method according to any one of claims 1-8, wherein the slice information is configured by an operation maintenance management OAM, or indicated/determined by an AMF, or determined by a network slice selection policy NSSP.
The method according to any one of claims 1-9, wherein the method further comprises:

Trigger N2 interface based handover when slice rollback or slice remapping; or,

When the slice rolls back or slice remapping, the handover based on the Xn interface is triggered, and when it is determined that the handover is rejected or the target base station cannot support the slice rollback or slice remapping, the handover based on the N2 interface is triggered.
A network switching method, characterized in that, applied to a first entity, the method comprising:

Obtain slice information, where the slice information is used to indicate information corresponding to the slice network;

According to the slice information, a switching behavior is determined, and the switching behavior is used to indicate a way of switching the network slice.
The method according to claim 11, wherein the switching behavior comprises at least one of the following:

Trigger handover based on N2 interface or trigger handover based on Xn interface;

Whether to send a handover request;

Whether to request slice remapping;

Whether to request slice fallback.
The method according to claim 11, wherein the switching behavior further comprises at least one of the following:

During the switching process of the slice, the switching based on the N2 interface is triggered;

In the process of slice switching, when the slice does not support or does not support slice remapping or does not support slice fallback and the Xn interface-based handover fails, trigger the N2 interface-based handover;

During the handover process of the slice, the handover based on the Xn interface and the handover based on the N2 interface are triggered.
The method according to claim 11, wherein the determining the switching behavior according to the slice information comprises:

The handover behavior is determined based on the reference rule and the slice information.
The method according to claim 14, wherein the determining the switching behavior based on the reference rule and the slice information comprises at least one of the following:

If the slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, the switch supports or accepts the switch;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, the switch is rejected or not accepted;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, and the target base station has acquired or configured or supported or established an equivalent slice/equivalent slice of the slice corresponding to the session requiring handover For slices in the group, switch support or accept; or, switch and slice remapping;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the services corresponding to the slice identifier are different, the switch is not supported or rejected;

If the slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, and the service corresponding to the slice identifier is the same, the switch supports or accepts; or, the switch is performed and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish an equivalent slice of the slice corresponding to the session requiring handover/etc. slices in the valence slice group, the switch is not supported or rejected;

The slice identifier supported by the target base station is different from the slice identifier required by the source base station to be handed over, but the target base station has not acquired or configured or does not support or does not establish an equivalent slice of the slice corresponding to the session requiring handover/etc. Slices in the valence slice group, switch to support or accept; or, switch and fall back on slices;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target base station has acquired or configured or supported or established the default slice/default slice group of the slice corresponding to the session requiring the switch. , switch to support or accept; or, switch and fall back to the slice;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, and the target base station does not acquire or configure or does not support or establish an equivalent slice of the slice corresponding to the session requiring handover/etc. If the target base station has acquired or configured or supported or established the default slice of the slice corresponding to the session requiring handover/the slice in the default slice group, the handover supports or accepts; or, the handover and slice fallback;

The slice identifier supported by the target base station is different from the slice identifier required to be handed over by the source base station, but the target base station has not acquired or configured or does not support or does not establish the default slice/default slice of the slice corresponding to the session requiring handover slices within the group, the switch is not supported or rejected;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the slice corresponding to the session requiring handover The equivalent slice of / the slice in the equivalent slice group, then switch support or accept; or, switch and slice remapping;

The slice identifier supported by the target base station is the same as the slice identifier required to be handed over by the source base station, and the target slice has reached the access threshold, and the target base station has not acquired or configured or does not support or does not establish a session corresponding to the required handover If the target base station has acquired or configured or supported or established the default slice of the slice corresponding to the session requiring handover/a slice in the default slice group, then switch to support or accept; or, toggle and slice fallback;

The slice identifier supported by the target base station is the same as the slice identifier required to be handed over by the source base station, but the target slice reaches the access threshold, and the target base station has acquired or configured or supported or established the slice corresponding to the session requiring handover. If the slice in the default slice/default slice group is switched to support or accept; or, switch and the slice is rolled back;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or Accept; or, switch and slice back;

The slice identifier supported by the target base station is the same as the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the target base station If the default slice of the slice corresponding to the session that requires switching has been acquired, configured, supported or established, the switch supports or accepts; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the target base station If the default slice of the slice corresponding to the session that requires switching has been obtained, configured, supported or established, the switch supports or accepts; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, then the switch supports or Accept; or, switch and slice back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but if the target slice and the slices in the equivalent slice/equivalent slice group corresponding to the target slice reach the access threshold, the handover is not supported. or refuse;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, then the handover supports or accepts; Slice fallback; or, switch and slice remapping;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or configured or If the equivalent slice of the slice corresponding to the session that requires switching is supported or established, or the slice in the equivalent slice group is supported or established, the switch supports or accepts; or, the switch is switched and the slice is remapped;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has not acquired or If the equivalent slice of the slice corresponding to the session that is required to be switched is not configured or not supported or is not established, the switch is supported or accepted; or, the switch is switched and the slice is rolled back;

The slice identifier supported by the target base station is different from the slice identifier required to be switched by the source base station, but the target slice is a slice with the requirement of handover service continuity or a service/slice guaranteed by priority, and the target base station has acquired or If the default slice/default slice group of the slice corresponding to the session requiring switching is configured, supported or established, the switch supports or accepts; or, the switch and the slice rolls back.
The method according to any one of claims 11-15, wherein the slice information includes at least one of the following:

Equivalent slice or equivalent slice group;

default slice or default slice group;

The slice support capability of the target base station;

Slice identifiers supported by the source base station;

The slice identifier corresponding to the PDU session currently established by the terminal;

a slice identifier supported by the target base station;

the slice identifier corresponding to the PDU session that the target base station allows the terminal to establish;

The identifier of the UE slice allowed by the target base station;

the service corresponding to the slice identifier;

the group to which the slice belongs;

An identifier corresponding to whether the equivalent slice or equivalent slice group of the target base station supports it;

The equivalent slice or equivalent slice group corresponding to the target base station is to establish a session;

The identifier corresponding to whether the default slice or default slice group of the target base station supports;

Whether a session is established corresponding to the default slice or default slice group of the target base station;

Whether the PDU session or slice that needs to be switched has the requirement or indication of switching service continuity;

Whether the PDU session or slice that needs to be handed over but is not supported by the target base station is a prioritized service or slice.
The method according to any one of claims 11-16, wherein the slice information is configured by OAM, or indicated/determined by AMF, or determined by NSSP.
The method according to any one of claims 11-17, wherein the first entity is any one of an NR base station and an LTE base station.
The method of claim 18, wherein the method further comprises:

When it is determined that the switching behavior includes slice remapping or slice rollback, send the indication information of slice remapping or slice rollback to a second entity, where the second entity is configured to perform slice remapping or slice rollback based on the indication information go back.
The method according to claim 19, wherein the second entity is any one of AMF, SMF, NR base station, and LTE base station.
A network switching device, characterized in that the device comprises:

an acquisition module, configured to acquire slice information, where the slice information is used to indicate information corresponding to the slice network;

A determination module, configured to determine a switching behavior according to the slice information, where the switching behavior is used to indicate a way of switching the network slice.
A network switching device, characterized in that, applied to a first entity, the device comprises:

an acquisition module, configured to acquire slice information, where the slice information is used to indicate information corresponding to the slice network;

A determination module, configured to determine a switching behavior according to the slice information, where the switching behavior is used to indicate a way of switching the network slice.
A network device, characterized in that the network device includes:

processor;

a transceiver connected to the processor;

memory for storing executable instructions for the processor;

Wherein, the processor is configured to load and execute the executable instructions to implement the network switching method according to any one of claims 1 to 20.
A computer-readable storage medium, wherein executable instructions are stored in the readable storage medium, and the executable instructions are loaded and executed by the processor to implement any one of claims 1 to 20. network switching method.