CN114916024A - Inter-cell switching method, base station, PCF entity and system - Google Patents

Inter-cell switching method, base station, PCF entity and system Download PDF

Info

Publication number
CN114916024A
CN114916024A CN202110171452.6A CN202110171452A CN114916024A CN 114916024 A CN114916024 A CN 114916024A CN 202110171452 A CN202110171452 A CN 202110171452A CN 114916024 A CN114916024 A CN 114916024A
Authority
CN
China
Prior art keywords
network slice
base station
slice
pdu session
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110171452.6A
Other languages
Chinese (zh)
Inventor
信金灿
张乐
孙震强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202110171452.6A priority Critical patent/CN114916024A/en
Publication of CN114916024A publication Critical patent/CN114916024A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Abstract

The disclosure provides an inter-cell switching method, a base station, a PCF entity and a system, and relates to the technical field of communication. In the disclosure, when receiving a network slice sent by a source base station, a target base station determines whether the target base station supports the network slice according to a situation that the target base station supports the network slice. And under the condition that the target base station does not support the first network slice recommended by the source base station, the target base station reallocates the second network slice so that the user equipment can access the target base station by using the second network slice, and sends the allocated second network slice to the core network control plane entity so as to complete the updating of the network slice at the core network side.

Description

Inter-cell switching method, base station, PCF entity and system
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method, a base station, a PCF entity, and a system for inter-cell handover.
Background
With the development of wireless communication technology, the 5G technology gradually becomes a research hotspot in the communication field by its technical features of supporting large broadband, large connection, low delay and the like. 5G systems typically use a Single Network Slice identity (Single Network Slice Selection Assistant Information, S-NSSAI) to uniquely identify an end-to-end Network Slice. Network slicing (also called slicing), which is an important feature of 5G networks, can meet the customized demands of operators for various industries, vertical markets, and various virtual operation services. The network slice can enable a user to access to the most suitable network according to the requirement through the end-to-end configuration of the network, and the flexibility of network resources is improved. In an actual standard, most of the network slicing work is implemented on the core network side, and the access network matches the core network and performs signaling interaction by matching with the network slicing indication of the core network.
When a terminal (also called user equipment) is in a connected state, a base station can realize mobility management of the terminal through a handover process. A handover procedure in a New Radio interface (NR) system defined in the existing protocol TS38.300 keeps Access and Mobility Management functions (AMF) unchanged, that is, a source base station and a target base station are connected to the same AMF (core network control plane entity), and the same AMF supports the same network slice list.
When the terminal moves from the source base station to the target base station, the source base station sends a handover request message to the target base station, wherein the handover request message carries a Protocol Data Unit (PDU) session identifier and corresponding network slice information. And then, the target base station performs admission control, replies a switching request response message and informs the source base station of a PDU session list allowed to be established, and corresponding network slice information is not replied because the network slice is not replaced for the terminal. After the terminal accesses the target base station, the target base station sends a path switching request message to the core network, wherein the path switching request message carries a PDU session list for preparation switching. The core network replies a path switching request response message to the target base station to inform the source base station of the PDU session list allowed to be converted and the network slice list allowed to be converted, wherein the source base station and the target base station are connected to the same AMF, so the path switching request message and the path switching request response message do not carry the network slice information related to each PDU session. Currently, network slicing for terminal replacement is not supported in handover procedures in NR systems defined by the 3rd Generation Partnership Project (3 GPP) Rel-16 standard.
Disclosure of Invention
To this end, the present disclosure provides an inter-cell handover method capable of enabling a user equipment to change a network slice before and after handover.
According to some embodiments of the present disclosure, there is provided an inter-cell handover method, performed by a target base station, including:
after receiving a switching request message sent by a source base station, extracting first network slice information recommended by the source base station from the switching request message;
judging whether the target base station supports a first network slice or not;
if the target base station does not support the first network slice, allocating a second network slice;
sending a handover request response message to the source base station, wherein the handover request response message includes the allocated second network slice information, so that the user equipment can access the target base station by using the second network slice;
after the user equipment accesses the target base station, sending a first path switching request message to a corresponding core network control plane entity, wherein the first path switching request message includes the second network slice information;
and after receiving a path switching request response message sent by the core network control plane entity, replacing the second network slice information with the network slice information included in the path switching request response message.
In some embodiments, further comprising: if the target base station supports the first network slice, sending a switching request response message to the source base station so that user equipment can access the target base station by using the first network slice; after user equipment accesses a target base station, sending a second path switching request message to a corresponding core network control plane entity, wherein the second path switching request message comprises the first network slice information; and after receiving a path switching request response message sent by the core network control plane entity, replacing the first network slice information with network slice information included in the path switching request response message.
In some embodiments, said assigning the second network slice comprises: a centralized entity CU of the target base station selects a second network slice matched with the service of the user equipment from a network slice list supported by the target base station; the CU sends slice pre-configuration information to a separation entity DU of a target base station, wherein the slice pre-configuration information comprises second network slice information; and the DU configures the second network slice for the service of the user equipment according to the pre-configuration information.
In some embodiments, the replacing the second network slice information with the network slice information included in the path switch request response message includes: the CU determines slice confirmation configuration information according to the network slice information included in the path switching request response message; the CU sends the slice confirmation configuration information to the DU; the DU replaces the provisioning information with the slice acknowledgement configuration information; and the DU reconfigures the network slice included in the slice confirmation configuration information for the service of the user equipment according to the slice confirmation configuration information.
In some embodiments, the handover request message includes one or more of a network slice list, a radio access technology/frequency selection priority (RFSP) list, a configuration information list of Protocol Data Unit (PDU) sessions requiring handover, wherein the configuration information list of the PDU sessions includes one or more of a PDU session identification and network slice information recommended for the PDU session.
In some embodiments, the handover request response message includes one or more of a PDU session permission list including one or more of a PDU session identification, network slice information configured for a PDU session, and quality of service QoS flow configuration parameters configured for a PDU session, and a PDU session failure list including one or more of a PDU session identification and a failure cause.
In some embodiments, the first path switching request message or the second path switching request message includes one or more of network slice remapping information corresponding to a PDU session, a PDU session identifier, and network slice information configured for the PDU session.
In some embodiments, the path switch request response message includes one or more of a PDU session switch success list, a PDU session switch failure list, an updated network slice list, and an updated RFSP list, where the PDU session switch success list includes one or more of a PDU session identifier, network slice information allocated for a PDU session, and the PDU session switch failure list includes one or more of a PDU session identifier and a failure cause.
According to another embodiment of the present disclosure, there is provided an inter-cell handover method performed by a policy control function PCF entity, including:
receiving a slice updating request message sent by a core network control plane entity;
extracting network slice information to be verified according to the slice updating request message, and verifying whether a core network side supports the network slice to be verified;
under the condition that the core network side does not support the network slice to be verified, reallocating the network slice to the service of the user equipment;
and sending a first slice update request response message to a core network control plane entity, wherein the first slice update request response message comprises the redistributed network slice information.
In some embodiments, in case that the core network side supports the network slice to be verified, sending a second slice update request response message to a core network control plane entity, the second slice update request response message including the network slice to be verified information.
In some embodiments, further comprising: and updating the network slice list supported by the core network side according to the redistributed network slice information, and synchronizing the updated network slice list to the core network control plane entity.
In some embodiments, the slice update request message includes one or more of a user equipment identity, a target base station identity, network slice information configured for a PDU session.
In some embodiments, the first slice update request response message or the second slice update request response message includes one or more of a PDU session handover success list including one or more of a PDU session identification, network slice information configured for a PDU session, a PDU session handover failure list including one or more of a PDU session identification and a failure cause, an updated network slice list, an updated RFSP list.
According to still further embodiments of the present disclosure, there is provided a base station including: a memory; and a processor coupled to the memory, the processor configured to perform the inter-cell handover method of any embodiment based on instructions stored in the memory.
According to still further embodiments of the present disclosure, there is provided a PCF entity, comprising: a memory; and a processor coupled to the memory, the processor configured to perform the inter-cell handover method of any embodiment based on instructions stored in the memory.
According to still further embodiments of the present disclosure, there is provided an inter-cell handover system, including:
the source base station is used for sending a switching request message to the target base station and receiving a switching request response message sent by the target base station so as to instruct the user equipment to access the target base station by using the network slice information in the switching request response message;
the target base station is the base station in any embodiment;
the core network control plane entity is used for extracting network slice information to be verified from a path switching request message after receiving the path switching request message sent by a target base station; sending a slice updating request message to a policy control function PCF entity, wherein the slice updating request message comprises network slice information to be verified; after receiving a slice update request response message sent by the PCF entity, sending a path switch request response message to the target base station, the path switch request response message including network slice information extracted according to the slice update request response message;
the PCF entity is the PCF entity according to any of the embodiments.
In some embodiments, the core network control plane entity is further configured to send the network slice information in the slice update request response message to the user equipment through a non-access stratum NAS message.
According to yet further embodiments of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the inter-cell handover method of any of the embodiments.
Drawings
The drawings that will be used in the description of the embodiments or the related art will be briefly described below. The present disclosure can be understood more clearly from the following detailed description, which proceeds with reference to the accompanying drawings.
It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without undue inventive faculty.
Fig. 1 illustrates a flow diagram of an inter-cell handover method in accordance with some embodiments of the present disclosure.
Fig. 2 shows a flow diagram of an inter-cell handover method according to further embodiments of the present disclosure.
Fig. 3 illustrates a schematic diagram of a base station, in accordance with some embodiments of the present disclosure.
Fig. 4 shows a flow diagram of an inter-cell handover method according to further embodiments of the present disclosure.
Fig. 5 shows a flow diagram of an inter-cell handover method according to still further embodiments of the present disclosure.
Fig. 6 illustrates a schematic diagram of a PCF entity, in accordance with some embodiments of the present disclosure.
Fig. 7 illustrates a schematic diagram of an inter-cell handover system, in accordance with some embodiments of the present disclosure.
Fig. 8 illustrates a schematic diagram of an inter-cell handover method according to further embodiments of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure.
The descriptions of "first", "second", etc. in this disclosure are intended to refer to different objects, and are not intended to refer to the meaning of size or timing, etc., unless otherwise specified.
Fig. 1 illustrates a flow diagram of an inter-cell handover method in accordance with some embodiments of the present disclosure.
As shown in fig. 1, the method of this embodiment comprises steps 101-106. The method of this embodiment is performed by a target base station.
In the current signaling flow, it is assumed that the source base station and the target base station before and after the handover all use the same slice, and the terminal is not supported to change the network slice before and after the handover. However, in the actual deployment process, if the source base station and the target base station support different network slices and are connected to different AMFs, the target base station cannot change slices for the terminal, and therefore, when the target base station does not support slices adopted by the source base station, the target base station rejects slices configured by the source base station, or the source base station does not trigger a slicing process to the target base station, which all causes a time delay or a failure process of handover. The method of the present embodiment may provide a solution to this problem by the following steps.
In step 101, after receiving a handover request message sent by a source base station, first network slice information recommended by the source base station is extracted from the handover request message.
The handover request message includes one or more of a network slice list, a Radio Access Technology (RAT)/Frequency selection priority (RFSP) list, and a configuration information list of a PDU session that needs to be handed over, where the configuration information list of the PDU session includes one or more of a PDU session identifier and network slice information recommended for the PDU session.
For example, in some embodiments, the handover request message includes, but is not limited to, the following information:
(1) allowed NSSAI list information: the NSSAI information comprises one or more NSSAI information, and represents NSSAI allowing the user equipment to access in the current registration area;
(2) allowed RFSPs indicating mobility configuration information that the user may support when supporting the allowed NSSAI, e.g., IE as defined in TS 23.501;
(3) other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(4) other RFSP information: mobility configuration information required to be supported when the user equipment supports other NSSAI lists;
(5) a PDU session configuration information list that needs to be switched, and the configuration of each PDU session includes but is not limited to the following:
(5a) PDU conversation identification: in a PDU session establishment request message sent to a network, uniquely identifying a PDU session of a UE;
(5b) S-NSSAI 1 currently in use;
(5c) recommended S-NSSAI 2.
At step 102, it is determined whether the target base station supports the first network slice.
And judging whether the target base station can accept the first network slice or not according to the network slice condition supported by the target base station.
In step 103, in case the target base station does not support the first network slice, a second network slice is allocated.
In 3GPP Rel-15, an architecture based on Centralized entities (CUs for short) and Distributed entities (DU for short) is supported. The CU entity is mainly responsible for Protocol functions of a Packet Data Convergence Protocol (PDCP), a Service Data Adaptation Protocol (SDAP), and a Radio Resource Control (RRC) layer, and the DU entity is mainly responsible for Protocol functions of a physical layer, a Media Access Control (MAC) layer, and a Radio Link Control (RLC) layer, and has a part of codec functions of an RRC layer asn.1. According to the current protocol, the physical layer parameters of the base station are generated and configured by DU and notified to CU entity, and the parameters of cell high layer and the parameter configuration such as radio resource management are generated by CU.
In some embodiments, the CU of the target base station selects a second network slice matching the traffic of the user equipment from the list of network slices supported by the target base station; the CU sends slice pre-configuration information to a DU (data Unit) of the target base station, wherein the slice pre-configuration information comprises second network slice information; then, the DU configures a second network slice for the service of the ue according to the pre-configuration information, where the second network slice is a different network slice from the first network slice. The service of the user equipment may include, for example, a PDU session.
In step 104, a handover request response message is sent to the source base station, where the handover request response message includes the allocated second network slice information, so that the user equipment uses the second network slice to access the target base station.
The handover request response message may include, for example, one or more of a PDU session permission list including one or more of a PDU session identification, network slice information configured for the PDU session, and quality of service QoS flow configuration parameters configured for the PDU session, and a PDU session failure list including one or more of a PDU session identification and a failure cause.
For example, in some embodiments, the handover request response message includes, but is not limited to, the following information:
(1) PDU session grant list, the configuration of each successfully established PDU session includes but is not limited to the following:
(2) PDU session identification 1: identifying a successfully established PDU session;
(3) newly assigned S-NSSAI 3;
(4) quality of Service (QoS) flow parameters configured for a PDU session.
In step 105, after the ue accesses the target base station, a first path switching request message is sent to a corresponding core network control plane entity, where the first path switching request message includes second network slice information.
The first path switching request message may include, for example, one or more of network slice remapping information corresponding to the PDU session, a PDU session identifier, and network slice information configured for the PDU session.
For example, in some embodiments, the path switch request message includes, but is not limited to, the following information:
(1) slice remapping request information: the Boolean type indicates that the core network needs to be requested to check newly generated slice information if the type is yes;
(2) a PDU session resource downlink entry to be converted;
(3) PDU session identification 1: one PDU session that uniquely identifies the UE;
(4) S-NSSAI 3: a network slice reallocated for the PDU session.
Sending the first path switching request message to a corresponding core network Control plane entity, so that the core network Control plane entity can verify whether the allocated second network slice is reasonable through a Policy Control Function (PCF), thereby ensuring that the second network slice is used for providing service for the PDU session of the user equipment under the condition that the second network slice passes the verification; and under the condition that the verification fails, the PCF entity redistributes the network slices, thereby ensuring the successful switching and providing service for the PDU conversation of the user equipment.
In step 106, after receiving the path switching request response message sent by the core network control plane entity, the network slice information included in the path switching request response message is used to replace the second network slice information.
The path switching request response message may include, for example, one or more of a PDU session switching success list, a PDU session switching failure list, an updated network slice list, and an updated RFSP list, where the PDU session switching success list includes one or more of a PDU session identifier and network slice information allocated for a PDU session, and the PDU session switching failure list includes one or more of a PDU session identifier and a failure cause.
For example, in some embodiments, the path switch request response message includes, but is not limited to, the following information:
(1) PDU Session 1 conversion success list;
(2) S-NSSAI 5: a slice assigned to the PDU Session;
(3) PDU Session conversion failure list;
(4) PDU Session identification;
(5) the reason for failure is as follows: the core network does not support slicing;
(8) updated allowed NSSAI list information: including one or more NSSAI information indicating NSSAIs (including S-NSSAI5) to which the user equipment is allowed to access in the current registration area;
(7) updated allowed RFSP indicating mobility configuration information that the user can support when supporting allowed NSSAI, IE as defined in TS 23.501;
(8) updated other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(9) updated other RFSP information: mobility configuration information that needs to be supported when the user equipment supports other NSSAI lists.
In some embodiments, replacing the second network slice information with the network slice information included in the path switch request response message includes: the CU determines slice confirmation configuration information according to the network slice information included in the path switching request response message; the CU sends slice confirmation configuration information to the DU; the DU replaces the pre-configuration information with slice confirmation configuration information; the DU reconfigures the network slice included in the slice acknowledgement configuration information for the service of the user equipment according to the slice acknowledgement configuration information.
In the above embodiment, when receiving the network slice sent by the source base station, the target base station determines whether the target base station supports the network slice according to a situation that the target base station supports the network slice. And under the condition that the target base station does not support the first network slice recommended by the source base station, the target base station redistributes the second network slice, the second network slice can be used for ensuring that the service of the user equipment is successfully switched to the target base station, and the distributed second network slice is sent to the core network control plane entity so as to complete the updating of the network slice at the core network side. The target base station can change the network slice of the user equipment, the core network can acquire the changed network slice information from the path switching request message, verify the rationality of the newly distributed network slice, and update the network slice list of the base station according to the requirement, thereby reducing the switching time delay and the switching failure. The method disclosed by the invention utilizes the existing protocol process, partially supplements and perfects the existing protocol, and has the characteristic of less change on the existing protocol.
Fig. 2 shows a flow diagram of an inter-cell handover method according to further embodiments of the present disclosure.
As shown in fig. 2, the method of this embodiment includes step 201-. The method of this embodiment is performed by a target base station.
In step 201, after receiving a handover request message sent by a source base station, first network slice information recommended by the source base station is extracted from the handover request message.
For the specific content of this step, reference may be made to the description of step 101, which is not described herein again.
At step 202, it is determined whether the target base station supports the first network slice.
For details of this step, reference may be made to the description of step 102, which is not described herein again.
In step 203, in case that the target base station supports the first network slice, a handover request response message is sent to the source base station so that the user equipment accesses the target base station using the first network slice.
In step 204, after the ue accesses the target base station, a second path switching request message is sent to the corresponding core network control plane entity, where the second path switching request message includes the first network slice information.
The second path switching request message may further include, for example, one or more of network slice remapping information corresponding to the PDU session, a PDU session identifier, and network slice information configured for the PDU session.
In step 205, after receiving the path switching request response message sent by the core network control plane entity, the first network slice information is replaced by the network slice information included in the path switching request response message.
In some embodiments, replacing the first network slice information with the network slice information included in the path switch request response message includes: the CU determines slice confirmation configuration information according to the network slice information included in the path switching request response message; the CU sends slice confirmation configuration information to the DU; the DU replaces the pre-configuration information with slice confirmation configuration information; the DU reconfigures the network slice included in the slice acknowledgement configuration information for the service of the user equipment according to the slice acknowledgement configuration information.
In the above embodiment, when receiving the network slice sent by the source base station, the target base station determines whether the target base station supports the network slice according to a situation that the target base station supports the network slice. And under the condition that the target base station supports the first network slice, the first network slice is used for ensuring successful switching to the target base station, and the core network side is used for verifying the first network slice. The target base station can change the network slice of the user equipment, the core network can acquire the changed network slice information from the path switching request message, verify the rationality of the newly distributed network slice, and update the network slice list of the base station according to the requirement, thereby reducing the switching time delay and the switching failure. The method disclosed by the invention utilizes the existing protocol process, partially supplements and perfects the existing protocol, and has the characteristic of less change on the existing protocol.
Fig. 3 illustrates a schematic diagram of a base station, in accordance with some embodiments of the present disclosure.
As shown in fig. 3, the base station 300 of this embodiment includes: a memory 301 and a processor 302 coupled to the memory 301, the processor 302 being configured to perform the inter-cell handover method performed by the base station in any of the embodiments of the present disclosure based on instructions stored in the memory 301. For example, the inter-cell handover method described in the embodiments of fig. 1 or fig. 2 may be performed.
The memory 301 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs.
The base station 300 may also comprise an input output interface 303, a network interface 304, a storage interface 305, etc. These interfaces 303, 304, 305 and the memory 301 and the processor 302 may be connected by a bus 306, for example. The input/output interface 303 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 304 provides a connection interface for various networking devices. The storage interface 305 provides a connection interface for external storage devices such as an SD card and a usb disk.
Fig. 4 shows a flow diagram of an inter-cell handover method according to further embodiments of the present disclosure.
As shown in FIG. 4, the method of this embodiment includes steps 401 and 404. The method of this embodiment is performed by the PCF entity.
In the current specification, the target base station does not change the terminal slice information, and the path switching request message sent to the core network side by the target base station only carries the PDU session conversion list and does not carry the slice information. Therefore, after the target base station allocates a new slice to the terminal, the core network side cannot acquire the slice information and verify the reasonability of the slice information, and at this time, if the newly allocated slice is not reasonable, a handover failure may be caused. The method of the present embodiment may provide a solution to this problem by the following steps.
In step 401, a slice update request message sent by a core network control plane entity is received.
The slice update request message may include, for example, one or more of a user equipment identity, a target base station identity, and network slice information configured for the PDU session.
For example, in some embodiments, the slice update request message includes, but is not limited to, the following:
(1) a user identification;
(2) target base station identification information;
(3) a reallocation indication;
(4) NSSAI information list allocated by the target base station: S-NSSAI3 assigned for PDU Session 1.
In step 402, the information of the network slice to be verified is extracted according to the slice update request message, and whether the core network side supports the network slice to be verified is verified.
In step 403, under the condition that the core network side does not support the network slice to be verified, the network slice is reallocated for the service of the user equipment.
For example, the PCF entity selects a network slice matching the service of the user equipment from a list of network slices supported by the core network side, and takes the network slice as a network slice to be reallocated for the service of the user equipment.
In step 404, a first slice update request response message is sent to the core network control plane entity, where the first slice update request response message includes the reallocated network slice information.
The first slice update request response message may further include, for example, one or more of a PDU session handover success list, a PDU session handover failure list, an updated network slice list, and an updated RFSP list, where the PDU session handover success list includes one or more of a PDU session identifier and network slice information configured for the PDU session, and the PDU session handover failure list includes one or more of a PDU session identifier and a failure cause.
For example, in some embodiments, the slice update request response message includes, but is not limited to, the following:
(1) PDU Session 1 conversion success list;
(2) S-NSSAI 5: a slice assigned to the PDU Session;
(3) PDU Session fails to convert the tabulation;
(4) PDU Session identification;
(5) the reason for failure is as follows: the core network does not support slicing;
(6) updated allowed NSSAI list information: including one or more NSSAI information indicating NSSAIs (including S-NSSAI5) for allowing the user equipment to access in the current registration area;
(7) updated allowed RFSP indicating mobility configuration information that the user can support when supporting allowed NSSAI, IE as defined in TS 23.501;
(8) updated other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(9) updated other RFSP information: mobility configuration information that needs to be supported when the user equipment supports other NSSAI lists.
In some embodiments, further comprising: and updating the network slice list supported by the core network side according to the redistributed network slice information, and synchronizing the updated network slice list to the core network control plane entity. For example, the network slice information reallocated by the PCF is added to the network slice list supported by the core network to update the network slice list supported by the core network.
In the above embodiment, the network slice sent by the core network control plane entity may be verified. And under the condition that the PCF entity does not support the network slice to be verified, the PCF entity reallocates the network slice and sends the network slice to the core network control plane entity, so that the core network control plane entity indicates the target base station to access the user equipment by using the reallocated network slice. The embodiment ensures that any network slice allocated by the core network control plane entity can provide service for the service of the user equipment through the verification of the PCF entity, and ensures the continuity of the service at the terminal side.
Fig. 5 shows a flow diagram of an inter-cell handover method according to still further embodiments of the present disclosure.
As shown in FIG. 5, the method of this embodiment comprises steps 501-504. The method of this embodiment is performed by the PCF entity.
In step 501, a slice update request message sent by a core network control plane entity is received.
For details of this step, reference may be made to the description of step 401, which is not described herein again.
In step 502, the information of the network slice to be verified is extracted according to the slice update request message, and whether the core network side supports the network slice to be verified is verified.
For details of this step, reference may be made to the description of step 402, which is not described herein again.
In step 503, in a case that the core network side supports the to-be-verified network slice, a second slice update request response message is sent to the core network control plane entity, where the second slice update request response message includes information of the to-be-verified network slice.
The second slice update request response message may further include, for example, one or more of a PDU session handover success list, a PDU session handover failure list, an updated network slice list, and an updated RFSP list, where the PDU session handover success list includes one or more of a PDU session identifier and network slice information configured for a PDU session, and the PDU session handover failure list includes one or more of a PDU session identifier and a failure cause.
In the current specification, the core network configures an Allowed network slice list Allowed NSSAI information and RFSP for the context information to the base station through an initial context, and if the slice configuration is replaced, the core network does not update the configurations of NSSAI and RSFP, thereby affecting subsequent mobility and possibly causing handover failure. The method of the present embodiment may provide a solution to this problem by the following steps.
In step 504, the network slice list supported by the core network side is updated according to the reallocated network slice information, and the updated network slice list is synchronized to the core network control plane entity.
For example, the network slice information reallocated by the PCF is added to the network slice list supported by the core network to update the network slice list supported by the core network.
In the above embodiment, the network slice sent by the core network control plane entity may be verified. And under the condition that the PCF entity supports the network slice to be verified, sending the verified network slice to the core network control plane entity, so that the core network control plane entity indicates the target base station to access the user equipment by using the verified network slice. The embodiment ensures that any network slice allocated by the core network control plane entity can provide service for the service of the user equipment through the verification of the PCF entity, and ensures the continuity of the service at the terminal side.
Fig. 6 illustrates a schematic diagram of a PCF entity, in accordance with some embodiments of the present disclosure.
As shown in fig. 6, the PCF entity 600 of this embodiment includes: a memory 601 and a processor 602 coupled to the memory 601, wherein the processor 602 is configured to execute the inter-cell handover method performed by the PCF entity in any of the embodiments of the present disclosure based on instructions stored in the memory 601. For example, the inter-cell handover method described in the embodiments of fig. 4 or fig. 5 may be performed.
The memory 601 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs.
PCF entity 600 may also include input output interfaces 603, network interfaces 604, storage interfaces 605, and the like. These interfaces 603, 604, 605 and the memory 601 and the processor 602 may be connected via a bus 606, for example. The input/output interface 603 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 604 provides a connection interface for various networking devices. The storage interface 605 provides a connection interface for external storage devices such as an SD card and a usb disk.
Fig. 7 shows a schematic diagram of an inter-cell handover system, in accordance with some embodiments of the present disclosure.
As shown in fig. 7, the inter-cell handover system 700 of this embodiment includes: a source base station 701, a target base station 702, a core network control plane entity 703 and a PCF entity 704.
The source base station 701 is configured to send a handover request message to the target base station 702, and receive a handover request response message sent by the target base station 702, so as to instruct the user equipment to access the target base station 702 by using the network slice information in the handover request response message. The target base station 702 is the base station shown in the embodiment of fig. 3. PCF entity 704 is the PCF entity shown in the embodiment of fig. 6.
A core network control plane entity 703, configured to extract network slice information to be verified from a path switching request message sent by a target base station 702 after receiving the path switching request message; sending a slice update request message to the PCF entity 704, wherein the slice update request message includes network slice information to be verified; after receiving the slice update request response message sent by PCF entity 704, the path switch request response message is sent to target base station 702, where the path switch request response message includes network slice information extracted according to the slice update request response message. In some embodiments, the core network control plane entity 703 is further configured to send the network slice information in the slice update request response message to the user equipment through a non-access stratum NAS message.
The embodiment solves the problem that the target base station performs network slice remapping on the user equipment, and can support the target base station to reconfigure the network slices for the user equipment when the target base station does not support the network slices distributed by the source base station for the user equipment, so as to improve the switching success rate and reduce the switching delay. Moreover, the above embodiment solves the update function of the Allowed NSSAI list and the related mobility RFSP list, and can achieve that the core network can update the NSSAI and RFSP configurations accordingly after the base station changes the network slice configuration of the PDU session, thereby improving the success rate of handover. And the reasonability of the new network slice allocated by the target base station is verified, the core network control plane entity can acquire an updated network slice list from the path switching request message sent by the target base station, and verify the reasonability of the newly allocated network slice list according to the self network slice supporting condition. The embodiment is enhanced on the existing protocol, a new protocol process is not introduced, the implementation difficulty is low, the influence on the user equipment is small, and good backward compatibility and deployment feasibility are achieved.
Fig. 8 shows a schematic diagram of an inter-cell handover method according to further embodiments of the present disclosure.
As shown in FIG. 8, the method of this embodiment comprises steps 801-811.
This embodiment shows the process of a connected ue being handed over from a source base station to a target base station supporting a different network slice list. The core network side includes: a Slice Selection Function (NSSF) entity, an AMF to which a source base station is connected, an AMF to which a target base station is connected, and a PCF, wherein the AMF to which the source base station is connected and the AMF to which the target base station is connected support different Slice lists, respectively. Only the AMF corresponding to the target base station is shown in the figure.
When a source base station triggers the switching from user equipment to a target base station, if the target base station does not support the network slice distributed by the user equipment (namely a terminal) at the source base station, a recommended network slice identifier is sent to the target base station through a switching command, a centralized entity of the target base station sends pre-configuration information of the pre-distributed network slice to a DU (data channel) of the target base station, the target base station performs network slice mapping for the user equipment according to the pre-configuration information, and a mapping result is notified to the source base station through a switching request response message. The target base station verifies the network slice mapping result to the core network control plane entity corresponding to the target base station through the path switching request message after the user equipment is accessed, the core network entity corresponding to the target base station confirms the network slice capability supported by the user equipment to the PCF, network slice updating confirmation information is sent to the target base station through the core network control plane entity corresponding to the target base station, and the target base station centralized entity sends the network slice mapping confirmation result to the target base station separation entity. And the second core network control plane entity indicates the network slice reallocation result to the first core network control plane entity and sends updated network slice information to the user equipment.
And the source base station is used as the context information of the user according to the slice configuration information sent by the core network and is used for selecting a switching target. Wherein the slice configuration information includes, but is not limited to, the following: allowed NSSAI list information: the method comprises the steps of including one or more NSSAI information which represents NSSAI allowing user equipment to access in a current registration area; allowed RFSPs indicating mobility configuration information that the user may support when supporting the allowed NSSAI, e.g., IE as defined in TS 23.501; other NSSAI list information: NSSAI information indicating that the user equipment can support in addition to the permission NSSAI list; other RFSP information: mobility configuration information that needs to be supported when the user equipment supports other NSSAI lists.
In step 801, the source base station needs to switch the ue to the target base station according to the measurement report, and if the slice of PDU Session 1 of the ue is not in the slice list supported by the target base station, a recommended slice 2 is newly allocated to each unsuitable slice of the ue.
In step 802, the source base station sends the recommended slice 2 to the target base station through a handover request message. Wherein the handover request message includes but is not limited to the following information:
(1) allowed NSSAI list information: the NSSAI information comprises one or more NSSAI information which indicates NSSAI allowing the user equipment to access in the current registration area;
(2) allowed RFSP indicating mobility configuration information that the user can support when supporting allowed NSSAI, IE as defined in TS 23.501;
(3) other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(4) other RFSP information: when the user equipment supports other NSSAI lists, the mobility configuration information required to be supported;
(5) a PDU session configuration information list that needs to be switched, and the configuration of each PDU session includes but is not limited to the following:
(5a) PDU conversation identification: in a PDU session establishment request message sent to a network, uniquely identifying a PDU session of a UE;
(5b) S-NSSAI 1 currently in use;
(5c) recommended S-NSSAI 2.
In step 803, the target base station stores the allowed NSSAI list information, the allowed RFSP information, the other NSSAI list information, and the other RFSP information as one of the context information of the user after receiving the handover request message. And determining that the recommended slice 2 in the handover request message is not acceptable according to the slice support condition, and then detecting that a slice 3 with similar performance exists in the supported slice list by the target base station and can support the slice.
In step 804, the target base station needs to feed back a handover request response message via the direct interface or the indirect interface with the source base station, where the handover request response message includes, but is not limited to, the following information:
(1) PDU session grant list, configuration of each successfully established PDU session includes but is not limited to the following:
(2) PDU session identity 1: identifying a successfully established PDU session;
(3) newly assigned S-NSSAI 3;
(4) quality of Service (QoS) flow parameters configured for a PDU session.
In step 805, the centralized entity of the target base station sends the slice pre-configuration information to the target base station separation entity through the F1 interface, and the target base station separation entity stores the slice pre-configuration information after receiving the slice pre-configuration information. Wherein the slice pre-configuration information comprises:
(1) a list of configuration information of PDU sessions, wherein the configuration of each PDU session includes but is not limited to the following:
(2) PDU session identification 1: one PDU session that uniquely identifies the UE;
(3) NSSAI information 3: newly allocated slice information;
(4) and (7) QOS configuration.
In step 806, after the ue accesses, the target base station sends the reconfigured slice information to the AMF2 through a path switching request message, where the path switching request message includes but is not limited to the following information:
(1) slice remapping request information: the Boolean type indicates that the core network needs to be requested to check newly generated slice information if the type is yes;
(2) a PDU session resource downlink entry to be converted;
(3) PDU session identification 1: one PDU session that uniquely identifies the UE;
(4) S-NSSAI 3: a network slice reallocated for the PDU session.
In step 807, after receiving the path switch message, AMF2 determines a slice update request message to be sent to the PCF entity according to the slice remapping request message, where the slice update request message includes, but is not limited to, the following:
(1) a user identification;
(2) target base station identification information;
(3) a reallocation indication;
(4) NSSAI information list allocated by the target base station: S-NSSAI3 assigned for PDU Session 1.
In step 808, after receiving the slice update request message, the PCF entity determines, according to the support of AMF2, that AMF2 may not support the S-NSSAI3 allocated by the target base station for PDU Session 1, selects an adaptable S-NSSAI5 for the PDU Session in the NSSAI list supported by AMF2, and updates the supported S-NSSAI to the allowed NSSAI list. The PCF sends a slice update request response message to AMF2 including, but not limited to, the following:
(1) PDU Session 1 conversion success list;
(2) S-NSSAI 5: a slice assigned to the PDU Session;
(3) PDU Session fails to convert the tabulation;
(4) PDU Session identification;
(5) the reason for failure is as follows: the core network does not support slicing;
(6) updated allowed NSSAI list information: including one or more NSSAI information indicating NSSAIs (including S-NSSAI5) to which the user equipment is allowed to access in the current registration area;
(7) updated allowed RFSPs indicating mobility configuration information that the user may support when supporting the allowed NSSAI, e.g., IE as defined in TS 23.501;
(8) updated other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(9) updated other RFSP information: mobility configuration information that needs to be supported when the user equipment supports other NSSAI lists.
In step 809, AMF2 sends a path switching request response message to the target base station according to the slice information in the slice update request response message, where the path switching request response message includes, but is not limited to, the following information:
(1) PDU Session 1 conversion success list;
(2) S-NSSAI 5: a slice assigned to the PDU Session;
(3) PDU Session fails to convert the tabulation;
(4) PDU Session identification;
(5) the reason for failure is as follows: the core network does not support slicing;
(8) updated allowed NSSAI list information: including one or more NSSAI information indicating NSSAIs (including S-NSSAI5) to which the user equipment is allowed to access in the current registration area;
(7) updated allowed RFSPs indicating mobility configuration information that the user may support when supporting the allowed NSSAI, e.g., IE as defined in TS 23.501;
(8) updated other NSSAI list information: NSSAI information indicating that the user can support in addition to the permission NSSAI list;
(9) updated other RFSP information: mobility configuration information that needs to be supported when the user equipment supports other NSSAI lists.
In step 810, the target bs centralized entity sends the slice mapping confirmation result to the target bs separation entity through the F1 interface, the target bs separation entity covers the confirmed slice information with the original slice pre-configuration information, and in addition, the target bs covers the updated allowed NSSAI list, the allowed RFSP, the other NSSAI list information, and the other RFSP information with the previously stored allowed NSSAI list information, the allowed RFSP, the other NSSAI list information, and the other RFSP information.
In step 811, the core network sends the S-NSSAI5 newly allocated for PDU Session 1 to the user equipment through an NAS message, informing the user equipment of the updated slice information.
The embodiment solves the problem that the target base station performs network slice remapping on the user equipment, and when the target base station does not support the network slices distributed by the source base station for the user equipment, the embodiment can support the target base station to reconfigure the network slices for the user equipment so as to improve the switching success rate and reduce the switching delay. Moreover, the above embodiment solves the update function of the Allowed NSSAI list and the related mobility RFSP list, and can achieve that the core network can update the NSSAI and RFSP configurations accordingly after the base station changes the network slice configuration of the PDU session, thereby improving the success rate of handover. And the reasonability of the new network slice allocated by the target base station is verified, the core network control plane entity can acquire an updated network slice list from the path switching request message sent by the target base station, and verify the reasonability of the newly allocated network slice list according to the self network slice supporting condition. The embodiment is enhanced on the existing protocol, a new protocol process is not introduced, the implementation difficulty is low, the influence on the user equipment is small, and good backward compatibility and deployment feasibility are achieved.
As will be appreciated by one of skill in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-non-transitory readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims (18)

1. An inter-cell handover method, performed by a target base station, comprising:
after receiving a switching request message sent by a source base station, extracting first network slice information recommended by the source base station from the switching request message;
judging whether the target base station supports a first network slice;
if the target base station does not support the first network slice, allocating a second network slice;
sending a handover request response message to the source base station, wherein the handover request response message includes the allocated second network slice information, so that the user equipment can access the target base station by using the second network slice;
after the user equipment accesses the target base station, sending a first path switching request message to a corresponding core network control plane entity, wherein the first path switching request message includes the second network slice information;
and after receiving a path switching request response message sent by the core network control plane entity, replacing the second network slice information with the network slice information included in the path switching request response message.
2. The inter-cell handover method of claim 1, further comprising:
if the target base station supports the first network slice, sending a switching request response message to the source base station so that user equipment can access the target base station by using the first network slice;
after user equipment accesses a target base station, sending a second path switching request message to a corresponding core network control plane entity, wherein the second path switching request message comprises the first network slice information;
and after receiving a path switching request response message sent by the core network control plane entity, replacing the first network slice information with network slice information included in the path switching request response message.
3. The inter-cell handover method of claim 1, the allocating a second network slice comprising:
a centralized entity CU of the target base station selects a second network slice matched with the service of the user equipment from a network slice list supported by the target base station;
the CU sends slice pre-configuration information to a separation entity DU of a target base station, wherein the slice pre-configuration information comprises second network slice information;
and the DU configures the second network slice for the service of the user equipment according to the pre-configuration information.
4. The inter-cell handover method according to claim 3, wherein the replacing the second network slice information with the network slice information included in the path switch request response message includes:
the CU determines slice confirmation configuration information according to the network slice information included in the path switching request response message;
the CU sends the slice confirmation configuration information to the DU;
the DU replaces the pre-configuration information with the slice confirmation configuration information;
and the DU reconfigures the network slice included in the slice confirmation configuration information for the service of the user equipment according to the slice confirmation configuration information.
5. The inter-cell handover method according to any one of claims 1 to 3,
the switching request message comprises one or more items of a network slice list, a radio access technology/frequency selection priority (RFSP) list and a configuration information list of a Protocol Data Unit (PDU) session needing switching, wherein the configuration information list of the PDU session comprises one or more items of a PDU session identification and network slice information recommended for the PDU session.
6. The inter-cell handover method according to any one of claims 1 to 3,
the handover request response message comprises one or more items of a PDU session permission list and a PDU session failure list, wherein the PDU session permission list comprises one or more items of a PDU session identification, network slice information configured for the PDU session and quality of service (QoS) flow configuration parameters configured for the PDU session, and the PDU session failure list comprises one or more items of the PDU session identification and a failure reason.
7. The inter-cell handover method according to any one of claims 1 to 3,
the first path switching request message or the second path switching request message includes one or more of network slice remapping information corresponding to the PDU session, a PDU session identifier, and network slice information configured for the PDU session.
8. The inter-cell handover method according to any one of claims 1 to 3,
the path switching request response message includes one or more items of a PDU session switching success list, a PDU session switching failure list, an updated network slice list, and an updated RFSP list, where the PDU session switching success list includes one or more items of a PDU session identifier and network slice information allocated for a PDU session, and the PDU session switching failure list includes one or more items of a PDU session identifier and a failure cause.
9. An inter-cell handover method, performed by a Policy Control Function (PCF) entity, includes:
receiving a slice updating request message sent by a core network control plane entity;
extracting network slice information to be verified according to the slice updating request message, and verifying whether a core network side supports the network slice to be verified;
under the condition that the core network side does not support the network slice to be verified, reallocating the network slice to the service of the user equipment;
and sending a first slice update request response message to a core network control plane entity, wherein the first slice update request response message comprises the redistributed network slice information.
10. The inter-cell handover method according to claim 9,
and sending a second slice update request response message to a core network control plane entity under the condition that the core network side supports the network slice to be verified, wherein the second slice update request response message comprises the network slice information to be verified.
11. The inter-cell handover method of claim 9, further comprising:
and updating the network slice list supported by the core network side according to the redistributed network slice information, and synchronizing the updated network slice list to the core network control plane entity.
12. The inter-cell handover method according to any one of claims 9 to 11,
the slice update request message includes one or more of a user equipment identity, a target base station identity, and network slice information configured for a PDU session.
13. The inter-cell handover method according to any one of claims 9 to 11,
the first slice update request response message or the second slice update request response message includes one or more of a PDU session handover success list, a PDU session handover failure list, an updated network slice list, and an updated RFSP list, wherein the PDU session handover success list includes one or more of a PDU session identifier and network slice information configured for a PDU session, and the PDU session handover failure list includes one or more of a PDU session identifier and a failure reason.
14. A base station, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the inter-cell handover method of any of claims 1-8 based on instructions stored in the memory.
15. A PCF entity, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the inter-cell handover method of any of claims 9-13 based on instructions stored in the memory.
16. An inter-cell handover system comprising:
the source base station is used for sending a switching request message to the target base station and receiving a switching request response message sent by the target base station so as to indicate the user equipment to access the target base station by using the network slice information in the switching request response message;
a target base station being the base station of claim 14;
the core network control plane entity is used for extracting network slice information to be verified from a path switching request message after receiving the path switching request message sent by a target base station; sending a slice updating request message to a policy control function PCF entity, wherein the slice updating request message comprises network slice information to be verified; after receiving a slice update request response message sent by the PCF entity, sending a path switch request response message to the target base station, wherein the path switch request response message comprises network slice information extracted according to the slice update request response message;
the PCF entity, being the PCF entity of claim 15.
17. The inter-cell handover system of claim 16, wherein,
and the core network control plane entity is further configured to send the network slice information in the slice update request response message to the user equipment through a non-access stratum NAS message.
18. A non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the inter-cell handover method of any of claims 1-13.
CN202110171452.6A 2021-02-08 2021-02-08 Inter-cell switching method, base station, PCF entity and system Pending CN114916024A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110171452.6A CN114916024A (en) 2021-02-08 2021-02-08 Inter-cell switching method, base station, PCF entity and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110171452.6A CN114916024A (en) 2021-02-08 2021-02-08 Inter-cell switching method, base station, PCF entity and system

Publications (1)

Publication Number Publication Date
CN114916024A true CN114916024A (en) 2022-08-16

Family

ID=82761757

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110171452.6A Pending CN114916024A (en) 2021-02-08 2021-02-08 Inter-cell switching method, base station, PCF entity and system

Country Status (1)

Country Link
CN (1) CN114916024A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324645A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Network Slice Information for Handover Procedure
CN109392038A (en) * 2017-08-11 2019-02-26 华为技术有限公司 Communication means and source base station, target BS, equipment of the core network, terminal device
CN109951877A (en) * 2017-12-20 2019-06-28 华为技术有限公司 A kind of slice information update method and device
CN110419240A (en) * 2017-03-24 2019-11-05 华为技术有限公司 It is sliced compatible switch device and method
CN110461027A (en) * 2018-05-07 2019-11-15 华为技术有限公司 A kind of network slice selection method and device
CN112188544A (en) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 Method and device for processing network slice information of user equipment between base stations

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110419240A (en) * 2017-03-24 2019-11-05 华为技术有限公司 It is sliced compatible switch device and method
US20180324645A1 (en) * 2017-05-04 2018-11-08 Ofinno Technologies, Llc Network Slice Information for Handover Procedure
CN109392038A (en) * 2017-08-11 2019-02-26 华为技术有限公司 Communication means and source base station, target BS, equipment of the core network, terminal device
CN109951877A (en) * 2017-12-20 2019-06-28 华为技术有限公司 A kind of slice information update method and device
CN110461027A (en) * 2018-05-07 2019-11-15 华为技术有限公司 A kind of network slice selection method and device
CN112188544A (en) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 Method and device for processing network slice information of user equipment between base stations

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI等: "KI#1, Sol #1: Updates of Solution #1", 3GPP TSG-WG SA2 MEETING #140E E-MEETING S2-2006501, 1 September 2020 (2020-09-01) *

Similar Documents

Publication Publication Date Title
US11463947B2 (en) Communication method, access network device, and terminal device to facilitate communication in a network slice architecture
CN108738086B (en) User plane reselection method and device
US10917831B2 (en) Radio access network slice generation method, radio access network, and slice manager
CN106102106B (en) Terminal access method, device and network architecture
US20220217587A1 (en) Session Handling Method and Related Device
WO2018028342A1 (en) Service processing method, apparatus, system, base station, terminal and core network element
CN110754116B (en) User device, wireless communication system, and wireless communication method
US20220053456A1 (en) Mode switching method for broadcast service and related device
EP3843458A1 (en) Method and apparatus for selecting network element
US20190159024A1 (en) Implementing Radio Access Network Slicing in a Mobile Network
EP3254189B1 (en) Upgrading of a mobile network function
CN110519807B (en) Communication method and device
CN110651499B (en) User device, wireless communication system, and wireless communication method
KR20110045764A (en) Method for communicating in mobile telecommunication network and system therefor
CN113163457A (en) Session establishment method, switching method and equipment
CN109328472B (en) Switching method and device
Jain et al. Evolutionary 4G/5G network architecture assisted efficient handover signaling
CN110958623A (en) Cell configuration method and device
CN109688631B (en) Connection processing method and device
CN109587744B (en) Switching method, switching system and mobile management entity
JP6754900B2 (en) Wireless communication system, user equipment, wireless base station and wireless communication method
CN114567880A (en) Communication method, system and computer readable storage medium
CN108430084B (en) Base station switching method and system
CN114916024A (en) Inter-cell switching method, base station, PCF entity and system
US20230180066A1 (en) Handover method, device and system in multi-connection network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination