CN112929933B

CN112929933B - AMF entity redirection method and system, management node and terminal

Info

Publication number: CN112929933B
Application number: CN202110183648.7A
Authority: CN
Inventors: 王鑫; 肖征荣; 田新雪
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-02-08
Filing date: 2021-02-08
Publication date: 2022-08-02
Anticipated expiration: 2041-02-08
Also published as: CN112929933A

Abstract

The application discloses an access and mobility management function AMF entity redirection method, a system, a management node and a terminal, wherein the AMF entity redirection method comprises the following steps: receiving user behavior information of a protocol data set unit (PDU) conversation carried by each slice which is currently connected and reported by a terminal and a cell number of a serving cell where the terminal is currently located; wherein the user behavior information includes: averaging the length of the continuous time, averaging the established release frequency; selecting an optimal AMF entity for each slice connected with the terminal; under the condition that all slices connected by the terminal can be subjected to AMF entity redirection according to the user behavior information and the cell number of the service cell, and the optimal AMF entities of at least two slices connected by the terminal are different, selecting a target AMF entity for redirection according to the optimal AMF entity; sending a redirection notification to the source AMF entity; wherein redirecting the notification comprises: the GUAMI of the target AMF entity. The matching degree of the AMF entity and the slice is improved.

Description

AMF entity redirection method and system, management node and terminal

Technical Field

The present application relates to the field of communications, and in particular, to a method and system for redirecting Access and Mobility Management Function (AMF) entities, a Management node, and a terminal.

Background

The AMF entity is a network element in a core network responsible for terminal access management, and when a service required by a terminal changes or a terminal connected to the AMF entity is overloaded, the service capability of the original AMF entity cannot meet a service requirement, an AMF entity redirection procedure is initiated, and a new AMF entity is connected to ensure Quality of service (QoS) of a terminal service.

Currently, selection, switching, and redirection of the AMF entity are mainly initiated from the core network side, for example, selection of the AMF entity is performed from aspects of load balancing, AMF entity capability, slice signing, and the like. When a terminal is connected with a plurality of slices, in order to find that one AMF entity can simultaneously meet the mobile access management of a plurality of slice services, the situation can occur, the capacity of one AMF entity can meet the basic connection of the slice 1, but the QoS matching degree with the slice 1 is lower; and the other AMF entity has a high QoS matching with slice 1 but cannot satisfy the slice 1 basic connection. Therefore, the same AMF entity is used for mobile access management of multiple slices of the terminal, and the AMF entity may not be the best choice, thereby resulting in poor user experience and easily causing the AMF entity to be overloaded.

Disclosure of Invention

The application provides an AMF entity redirection method, an AMF entity redirection system, a management node and a terminal, which can improve the matching degree of an AMF entity and a slice.

In a first aspect, the present application provides an access and mobility management function (AMF) entity redirection method, which is applied to a management node, and includes:

receiving user behavior information of a protocol data set unit (PDU) conversation carried by each slice which is currently connected and reported by a terminal and a cell number of a serving cell where the terminal is currently located; wherein the user behavior information comprises: averaging the length of the continuous time, averaging the established release frequency;

selecting an optimal AMF entity for each slice connected with the terminal;

under the condition that all slices connected with the terminal can be subjected to AMF entity redirection according to the user behavior information and the cell number of the service cell, and the optimal AMF entities of at least two slices connected with the terminal are different, selecting a target AMF entity for redirection according to the optimal AMF entity;

sending a redirection notification to the source AMF entity; wherein the redirect notification comprises: a globally unique AMF identifier, GUAMI, of the target AMF entity.

In some exemplary embodiments, after selecting the target AMF entity for redirection according to the optimal AMF entity, before sending the redirection notification to the source AMF entity, the method further includes:

sending a redirection message to the terminal before the protection time slot for AMF entity redirection;

receiving a confirmation message sent by the terminal; the confirmation message is used for confirming that an application program corresponding to an application program identifier (APP-ID) in a flow identifier in a user equipment routing strategy (URSP) corresponding to a slice which is used as an optimal AMF entity and is connected with a terminal is not in an activated state.

In some exemplary embodiments, the selecting an optimal AMF entity for each slice to which the terminal has connected includes:

receiving the corresponding relation between the single network slice selection auxiliary information S-NSSAI of the slice connected with the terminal and the AMF entity selectable set sent by the source AMF entity;

and screening the AMF entity selectable sets corresponding to all the S-NSSAIs, and selecting the optimal AMF entity for each slice connected by the terminal from the first AMF entity set under the condition that the first AMF entity set which can be shared by all slices connected by the terminal is screened out.

In some exemplary embodiments, in a case that the first AMF entity set that all slices connected by the terminal can share is not screened, the selecting the optimal AMF entity for each slice connected by the terminal further includes:

screening out a second AMF entity set which can be shared by the N-1 slices connected with the terminal and an independent AMF entity set of the remaining single slice;

selecting an optimal AMF entity for each slice of the N-1 slices from the second set of AMF entities, and selecting an optimal AMF entity for the remaining single slices from the independent sets of AMF entities; wherein N is the number of slices to which the terminal has been connected.

In some exemplary embodiments, determining that a slice to which the terminal is connected according to the user behavior information and the cell number of the serving cell may perform AMF entity redirection includes:

the cell number of the service cell where the terminal is located does not change within the preset time, and the average continuous time length and the average setup release frequency of the PDU session carried by a certain slice do not affect the session continuity in the process of AMF entity redirection.

In some exemplary embodiments, the user behavior information further includes: session and service continuation mode;

correspondingly, the selecting, according to the optimal AMF entity, the target AMF entity for redirection includes:

receiving first information reported by the terminal; the first information is used for indicating that the terminal receives a de-registration signaling of a PDU session carried by a first slice or an application program corresponding to an application program identifier APP-ID in a traffic identifier of a user equipment routing policy URSP on the first slice enters a sleep mode;

selecting an optimal AMF entity corresponding to the second slice as the target AMF entity for redirection; wherein the second slice is a slice with a minimum average establishment release frequency of the PDU sessions carried in the slices except the first slice among the slices connected by the terminal and a slice with a service continuity mode of 1.

receiving second information reported by the terminal; the second information is used for indicating that the terminal receives a PDU session establishment request carried by a third slice or an application program corresponding to an APP-ID in a traffic identifier of a URSP on the third slice is switched from a sleep mode to an active mode;

selecting an optimal AMF entity corresponding to the fourth slice as the target AMF entity for reshaping; wherein the fourth slice is a slice with the smallest average establishment release frequency of the borne PDU sessions in the slices with the session and service continuity mode of the PDU sessions borne by the slice to which the terminal is connected and the third slice being 1.

In some exemplary embodiments, the selecting, according to the optimal AMF entity, the target AMF entity for redirection includes:

and for each slice connected by the terminal, selecting the optimal AMF entity of the slice as the target AMF entity for redirection in the time slot resource range of the slice.

receiving third information reported by the terminal; the third information is used to indicate that the terminal receives a de-registration signaling of a PDU session carried by a first slice in a time slot resource range of the first slice, or an application program corresponding to an application program identifier APP-ID in a traffic identifier of a user equipment routing policy URSP in the time slot resource range of the first slice enters a sleep mode;

A second aspect of the present application provides an access and mobility management function AMF entity redirection method, applied to a terminal, the method including:

reporting user behavior information of a protocol data set unit (PDU) conversation borne by each slice which is connected currently and a cell number of a serving cell where the PDU conversation is located currently to a management node; wherein the user behavior information comprises: average continuous time length, average build-up release frequency.

In some exemplary embodiments, the method further comprises:

receiving a redirection message sent by the management node before a protection time slot for AMF entity redirection;

maintaining a CM-CONNECT state during said guard time slot;

sending a confirmation message to the management node; the confirmation message is used for confirming that an application program corresponding to an application program identifier (APP-ID) in a flow identifier in a user equipment routing strategy (URSP) corresponding to a slice which is used as an optimal AMF entity and is connected with a terminal is not in an activated state.

A third aspect of the present application provides a management node, comprising:

the first receiving module is used for receiving user behavior information of a protocol data set unit (PDU) session borne by each currently connected slice reported by a terminal and a cell number of a current serving cell; wherein the user behavior information comprises: averaging the duration of the continuous time, averaging the established release frequency;

a selection module to:

selecting an optimal AMF entity for each slice connected with the terminal;

the first sending module is used for sending a redirection notification to the source AMF entity; wherein the redirect notification comprises: a globally unique AMF identifier, GUAMI, of the target AMF entity.

A fourth aspect of the present application provides a terminal, comprising:

the second sending module is used for reporting the user behavior information of the protocol data set unit PDU session borne by each slice which is currently connected and the cell number of the serving cell where the current serving cell is located to the management node; wherein the user behavior information comprises: average continuous time length, average build-up release frequency.

A fifth aspect of the present application provides an access and mobility management function AMF entity redirection system, including:

a management node to:

selecting an optimal AMF entity for each slice connected with the terminal;

sending a redirection notification to the source AMF entity; wherein the redirect notification comprises: a globally unique AMF identifier, GUAMI, of the target AMF entity;

a terminal for:

This application has following advantage:

according to the embodiment of the application, the optimal AMF entity is selected for each slice connected with the terminal, and then the target AMF entity for redirection is selected based on the optimal AMF entity, so that the matching degree of the AMF entity and the slice is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the application and not to limit the application.

Fig. 1 is a flowchart of an AMF entity redirection method applied to a management node according to an embodiment of the present application;

fig. 2 is a flowchart of an AMF entity redirection method applied to a terminal according to another embodiment of the present application;

fig. 3 is an interaction diagram of an example proposed AMF entity redirection method according to an embodiment of the present application;

fig. 4 is a schematic structural component diagram of a management node according to another embodiment of the present application;

fig. 5 is a schematic structural component diagram of a terminal according to another embodiment of the present application;

fig. 6 is a schematic structural component diagram of an AMF entity redirection system according to another embodiment of the present application.

Detailed Description

The following detailed description of embodiments of the present application will be made with reference to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present application, are given by way of illustration and explanation only, and are not intended to limit the present application.

As used in this disclosure, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

When the terms "comprises" and/or "comprising … …" are used in this disclosure, the presence of stated features, integers, steps, operations, elements, and/or components are specified, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Embodiments of the present disclosure may be described with reference to plan and/or cross-sectional views in light of idealized schematic illustrations of the present disclosure. Accordingly, the example illustrations can be modified in accordance with manufacturing techniques and/or tolerances.

Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

In the embodiment of the application, a management node is newly added to realize AMF entity redirection.

Fig. 1 is a flowchart of an AMF entity redirection method applied to a management node according to an embodiment of the present application.

As shown in fig. 1, an embodiment of the present application provides an AMF entity redirection method, which is applied to a management node, and the method includes:

step 100, receiving user behavior information of a Protocol Data Unit (PDU) session carried by each currently connected slice and Cell Identity (CID) of a serving Cell where the current session is located, which are reported by a terminal; wherein the user behavior information comprises: average continuous time length, average build-up release frequency.

In some exemplary embodiments, the user behavior information further comprises: session and Service Continuity MODE (SSC MODE, Session and Service Continuity MODE).

Step 101, selecting an optimal AMF entity for each slice connected by the terminal.

In some exemplary embodiments, selecting an optimal AMF entity for each slice to which the terminal has connected includes:

receiving a corresponding relation between Single Network Slice Selection auxiliary Information (S-NSSAI) of slices connected with the terminal and AMF entity optional sets, wherein the Single Network Slice Selection auxiliary Information is sent by a source AMF entity;

In some exemplary embodiments, it may be determined whether the first AMF entity set 1 that all slices connected by the terminal can share can be screened out in the following manner:

determining that a first AMF entity set which can be shared by all slices connected by the terminal can be screened out under the condition that the intersection of the AMF entity selectable sets corresponding to all slices connected by the terminal is not empty, wherein the first AMF entity set is the intersection of the AMF entity selectable sets corresponding to all slices connected by the terminal;

and under the condition that the intersection of the AMF entity selectable sets corresponding to all the slices connected by the terminal is empty, determining to screen a first AMF entity set which can be shared by all the slices connected by the terminal.

In some exemplary embodiments, the second AMF entity set that the N-1 slices connected by the terminal can share is an intersection of the AMF entity selectable sets corresponding to the N-1 slices connected by the terminal.

In some exemplary embodiments, an optimal AMF entity may be selected for each slice to which the terminal has connected from the first AMF entity set 1 in the following manner:

for each slice connected with the terminal, selecting an AMF entity with the highest matching degree for the slice from the first AMF entity set; and taking the AMF entity with the highest matching degree as the optimal AMF entity of the slice.

In some exemplary embodiments, the matching degree of the AMF entity may be determined according to information such as a connection rate or a load rate of the AMF entity, and the specific use of which information to determine the matching degree of the AMF entity is not used to limit the protection scope of the embodiment of the present application.

In some exemplary embodiments, the connection rate of the SMF entity refers to an average connection rate when other terminals use the slice.

In some exemplary embodiments, an optimal AMF entity is selected for each slice in the N-1 slices from the second AMF entity set, and a method for selecting an optimal AMF entity for the remaining single slice from the independent AMF entity set is the same as a method for selecting an optimal AMF entity for each slice connected to the terminal from the first AMF entity set by the management node, and is not described herein again.

In some exemplary embodiments, in order to avoid a situation that a source AMF entity lacks a routing pointer and address information of a target AMF entity when performing AMF redirection, after obtaining an optimal AMF entity corresponding to each slice to which a terminal is connected, a management node sends an nrrf _ NFDiscovery _ Request message to a Network warehousing Function (NRF) entity, and the NRF entity returns the routing pointer and address information of each optimal AMF entity to the management node.

And 102, under the condition that all slices connected with the terminal can be subjected to AMF entity redirection according to the user behavior information and the cell number of the service cell and the optimal AMF entities of at least two slices connected with the terminal are different, selecting a target AMF entity for redirection according to the optimal AMF entity.

In some exemplary embodiments, the determining whether the average duration and the average setup and release frequency of the PDU sessions carried by a slice may affect the session continuity in the AMF entity redirection process includes:

judging whether the average continuous time length of the sliced PDU session is smaller than a first preset threshold value or not, and judging whether the average establishment release frequency of the sliced PDU session is smaller than a second preset threshold value or not;

determining that the average continuous time length and the average establishment and release frequency of the sliced PDU session do not influence the session continuity in the AMF entity redirection process under the condition that the average continuous time length of the sliced PDU session is smaller than a first preset threshold and the average establishment and release frequency of the sliced PDU session is smaller than a second preset threshold;

and determining that the average continuous time length and the average establishment and release frequency of the sliced PDU sessions can influence the session continuity in the AMF entity redirection process under the condition that the average continuous time length of the sliced PDU sessions is greater than or equal to a first preset threshold and the average establishment and release frequency of the sliced PDU sessions is greater than or equal to a second preset threshold.

In some exemplary embodiments, selecting a target AMF entity for redirection based on the optimal AMF entity includes:

receiving first information reported by the terminal; the first information is used to indicate that the terminal receives a de-registration signaling of a PDU session carried by a first slice, or an application corresponding to an application identifier APP-ID in a traffic identifier of a user equipment routing Policy (URSP) on the first slice enters a sleep mode;

selecting an optimal AMF entity corresponding to the second slice as the target AMF entity for redirection; wherein the second slice is any one of slices except the first slice among the slices to which the terminal has been connected. For example, to avoid performing AMF redirection for a large number of times, the second slice may be selected as a slice with the smallest average establishment release frequency of PDU sessions carried in slices other than the first slice among slices to which the terminal is connected and a slice with a service continuity mode of 1.

selecting an optimal AMF entity corresponding to the fourth slice as the target AMF entity for reshaping; wherein the fourth slice is any one of the slice to which the terminal is connected and the third slice. For example, to avoid performing AMF redirection for a large number of times, the fourth slice may be selected as the slice with the smallest average establishment release frequency of the PDU sessions carried by the slice to which the terminal is connected and the slice with the service continuity mode 1 of the PDU sessions carried by the third slice.

Step 103, sending a redirection notification to the source AMF entity; wherein the redirect notification comprises: a Globally Unique AMF Identifier (GUAMI, Global Unique AMF Identifier) of the target AMF entity.

In some exemplary embodiments, redirecting the notification further comprises: GUAMI, route pointer, address information of the target AMF entity.

Fig. 2 is a flowchart of an AMF entity redirection method applied to a terminal according to another embodiment of the present application.

As shown in fig. 2, another embodiment of the present application provides an AMF entity redirection method, which is applied to a terminal, and the method includes:

step 200, reporting user behavior information of a protocol data set unit (PDU) session borne by each slice which is connected currently and a cell number of a serving cell where the PDU session is located currently to a management node; wherein the user behavior information comprises: average continuous time length, average build-up release frequency.

In some exemplary embodiments, the user behavior information further comprises: SSC MODE.

In some exemplary embodiments, the method further comprises:

maintaining a CM-CONNECT state during said guard time slot;

The following describes a specific implementation process of the embodiments of the present application in detail by using a specific example, and the example is only for convenience of description and is not used to limit the scope of the embodiments of the present application.

Examples of the invention

As shown in fig. 3, the method includes:

1. and the terminal reports the user behavior information of the PDU session carried by each slice currently connected with the terminal and the CID of the current serving cell to the management node.

In this step, as shown in table 1, the user behavior information of the PDU session carried by the slice includes: the average continuous time length of the PDU session, the average establishment release frequency of the PDU session, and the SSC MODE of the PDU session.

TABLE 1

2. The source AMF entity transmits NSSF _ NSSelection _ Get information to a Network Slice Selection Function (NSSF) entity. NSSF entity is fed back to source AMF entity: AMF entity selection 0 for each slice to which the terminal has connected.

3. And the source AMF entity sends the corresponding relation between the S-NSSAI of the slice connected with the terminal and the AMF entity optional set 0 to the management node.

4. And the management node screens all AMF entity selectable sets 0 corresponding to the S-NSSAI, and continues to execute the step 5-10 under the condition that a first AMF entity set 1 which can be shared by all slices connected with the terminal is screened out. Screening a second AMF entity set 2 which can be shared by N-1 slices connected by the terminal and an independent AMF entity set 3 of the remaining single slice under the condition that a first AMF entity set 1 which can be shared by all slices connected by the terminal cannot be screened, and continuously executing the step 5-10; wherein, N is the number of slices connected by the terminal.

In this step, it may be determined whether the first AMF entity set 1 that all slices connected by the terminal can share can be screened out in the following manner:

under the condition that the intersection of the AMF entity optional sets 0 corresponding to all the slices connected by the terminal is not empty, determining that a first AMF entity set 1 which can be shared by all the slices connected by the terminal can be screened out, wherein the first AMF entity set 1 is the intersection of the AMF entity optional sets 0 corresponding to all the slices connected by the terminal;

and under the condition that the intersection of AMF entity selectable sets 0 corresponding to all slices connected by the terminal is empty, determining to screen a first AMF entity set 1 which can be shared by all slices connected by the terminal.

In this step, the second AMF entity set 2 where the N-1 slices connected to the terminal can share is the intersection of the AMF entity selectable sets 0 corresponding to the N-1 slices connected to the terminal.

5. The management node selects an optimal AMF entity for each slice connected with the terminal from the first AMF entity set 1; or the management node selects an optimal AMF entity for each slice in the N-1 slices from the second AMF entity set and selects an optimal AMF entity for the remaining single slice from the independent AMF entity sets.

And the management node sends an Nnrf _ NFdiscovery _ Request message to the NRF entity, and the NRF entity returns the routing pointer and address information of each optimal AMF entity to the management node.

In this step, the management node may select an optimal AMF entity for each slice to which the terminal is connected from the first AMF entity set 1 in the following manner:

for each slice connected with the terminal, the management node selects an AMF entity with the highest matching degree for the slice from the first AMF entity set 1; and taking the AMF entity with the highest matching degree as the optimal AMF entity of the slice.

In this step, the matching degree of the AMF entity may be calculated based on the connection rate and the load rate.

In this step, the connection rate of the SMF entity refers to an average connection rate when another terminal uses the slice.

In this step, the matching capability may refer to the length, delay, reliability, etc. of the routing path, and the higher the matching capability is, that is, the shorter the routing path is, the lower the delay is, and the lower the reliability is; the lower the matching capability, i.e. the longer the routing path, the longer the delay and the longer the reliability.

In this step, the management node selects an optimal AMF entity for each slice of the N-1 slices from the second AMF entity set, and a method for selecting an optimal AMF entity for the remaining single slice from the independent AMF entity set is the same as a method for selecting an optimal AMF entity for each slice connected to the terminal from the first AMF entity set by the management node, and details are not repeated here.

In this step, in order to avoid the situation that the source AMF entity lacks the routing pointer and address information of the target AMF entity when performing AMF redirection, the management node sends an nrrf _ NFDiscovery _ Request message to the NRF entity after obtaining the optimal AMF entity corresponding to each slice to which the terminal is connected, and the NRF entity returns the routing pointer and address information of each optimal AMF entity to the management node.

6. For each slice connected by the terminal, the management node judges whether the slice can carry out AMF entity redirection according to the average continuous time length, the average establishment release frequency and the cell number of a service cell of the PDU session carried by the slice, and executes the step 7 and the step 8 under the condition that all slices connected by the terminal can carry out AMF entity redirection; in case it is determined that there is a slice to which AMF entity redirection is not possible among the slices to which the terminal has connected, step 10 is performed.

In some exemplary embodiments, determining whether a slice may perform AMF entity redirection according to an average continuous time length of PDU sessions carried by the slice, an average setup release frequency, and a cell number of a serving cell includes:

judging whether the cell number of a service cell where the terminal is located changes within preset time, and judging whether the average continuous time length and the average established release frequency of the PDU session carried by the slice influence the session continuity in the process of AMF entity redirection;

determining that the slice can carry out AMF entity redirection under the conditions that the cell number of a service cell where a terminal is located does not change within preset time, and the average continuous time length and the average establishment release frequency of a PDU session carried by the slice do not influence the continuity of the session in the AMF entity redirection process;

and determining that the slice cannot be subjected to AMF entity redirection under the condition that the cell number of a service cell in which the terminal is positioned changes within preset time, or the average continuous time length and the average establishment and release frequency of the PDU session carried by the slice influence the session continuity in the AMF entity redirection process.

In some exemplary embodiments, when the cell number of the serving cell in which the terminal is located changes within a preset time, the source AMF entity of the new serving cell reports, to the management node, the correspondence between the S-NSSAI of the slice to which the terminal is connected and the AMF entity optional set X, and the management node continues to perform the step of screening all AMF entity optional sets X corresponding to S-NSSAI.

In some exemplary embodiments, the determining whether the average duration and the average setup release frequency of the PDU sessions carried by the slice may affect the session continuity during the AMF entity redirection process includes:

In this step, the terminal maintains a CM-CONNECT state, an RRC-inactive state, or an RRC-CONNECT state during the AMF entity redirection process, instead of disconnecting a Radio Resource Control (RRC) connection to re-perform a network registration connection.

TABLE 2

7. Under the condition that the optimal AMF entities of at least two slices connected with the terminal are different, the management node selects a target AMF entity for redirection according to the optimal AMF entity; and under the condition that the optimal AMF entities of all slices connected by the terminal are the same, the management node determines that AMF entity redirection is not needed.

In this step, any one of the following methods may be adopted to select the target AMF entity for redirection according to the optimal AMF entity.

The first method is to select a target AMF entity for redirection based on service triggering.

when a terminal receives a de-registration signaling of a PDU session carried by a first slice in a slice connected with the terminal or an application program corresponding to an application program identifier (APP-ID) in a flow identifier of a URSP in the first slice enters a sleep mode (namely an IDLE mode), the terminal reports first information to a management node; the first information is used for indicating that a terminal receives a de-registration signaling of a PDU session carried by a first slice or an application program corresponding to an APP-ID in a flow identifier of a URSP on the first slice enters a sleep mode;

the management node receives first information reported by a terminal; selecting an optimal AMF entity corresponding to the second slice as a target AMF entity for redirection; and the second slice is the slice with the minimum average setup release frequency f of the PDU sessions carried by the slices except the first slice in the slices connected with the terminal, wherein the SSC MODE of the PDU sessions carried by the slices is 1.

In the present application, a slice in which an SSC MODE carried by a PDU session is 1 is a slice in which an Internet Protocol (IP) address is allocated and a session service can continue.

when the terminal receives a PDU session establishment request carried by a third slice or an application program corresponding to an APP-ID in a flow identifier of a URSP on the third slice is switched from an IDLE mode to an ACTIVE mode (namely an ACTIVE mode), namely when the third slice needs to have a session again, the terminal reports second information to the management node; the second information is used for indicating that the terminal receives a PDU session establishment request carried by a third slice or an application program corresponding to an APP-ID in a traffic identification of a URSP on the third slice is converted from an IDLE mode to an active mode;

the management node receives second information reported by the terminal; selecting an optimal AMF entity corresponding to the fourth slice as a target AMF entity for reshaping; the fourth slice is a slice with the minimum average setup release frequency f of the PDU sessions carried by the slice connected with the terminal and the slice with the SSC MODE of 1 carried by the third slice.

In some exemplary embodiments, the third slice may be the first slice, and may also be other slices.

And secondly, selecting a target AMF entity for redirection based on clock triggering.

and for each slice connected by the terminal, selecting the optimal AMF entity of the slice as a target AMF entity for redirection in the time slot resource range of the slice.

In some example embodiments, the slot resources for each slice to which the terminal has connected may be pre-allocated. For example, during points 8-9 and 17-18, time slot resources are allocated to a network slice serving map navigation, and the optimal AMF entity of the slice is taken as a target AMF entity for redirection; during points 21-23, time slot resources are allocated to the network slice serving the game traffic, and the optimal AMF entity of the slice is taken as the target AMF entity for redirection.

And thirdly, selecting a target AMF entity for reshaping based on a mixed mechanism of business triggering and clock triggering.

when the terminal receives a de-registration signaling of a PDU session carried by a first slice or an application program corresponding to an APP-ID in a flow identifier of a URSP on the slice enters a sleep mode (namely an IDLE mode) in a time slot resource range of the first slice, the terminal reports third information to a management node; the third information is used for indicating the terminal to receive a de-registration signaling of a PDU session carried by the first slice in the timeslot resource range of the first slice, or indicating that an application program corresponding to the APP-ID in the traffic identifier of the URSP on the slice in the timeslot resource range of the first slice enters the sleep mode;

the management node receives third information reported by the terminal; selecting an optimal AMF entity corresponding to the second slice as a target AMF entity for redirection; and the second slice is the slice with the minimum average setup release frequency f of the PDU sessions carried by the slices except the first slice in the slices connected with the terminal, wherein the SSC MODE of the PDU sessions carried by the slices is 1.

In some exemplary embodiments, when the terminal receives a PDU session establishment request carried by a first slice or an application program corresponding to an APP-ID in a traffic identifier of a URSP on the first slice is changed from an IDLE mode to an ACTIVE mode (i.e., ACTIVE mode) within a time slot resource range of the first slice, the terminal reports fourth information to the management node; the fourth information is used for indicating the terminal to receive a PDU session establishment request carried by the first slice in the timeslot resource range of the first slice, or to change an application program corresponding to the APP-ID in the traffic identifier of the URSP on the first slice in the timeslot resource range of the first slice from the dormant mode to the active mode;

selecting the target AMF entity for redirection further comprises: and the management node selects the optimal AMF entity corresponding to the first slice as a target AMF entity for redirection.

8. The management node redirects a target AMF entity for redirection according to time slot multiplexing, and in order to smoothly switch the AMF entity, the following detailed steps are also required to be performed:

A. before redirecting to a target AMF entity, a protection time slot t needs to be reserved, and a management node sends a redirection message to a terminal before the protection time slot t for AMF entity redirection; after receiving the redirection message, the terminal keeps the CM-CONNECT state in the protection time slot t and does not convert the CM-IDEL state; the terminal sends a confirmation message to the management node; the confirmation message is used to confirm that the source AMF entity connected to the terminal at this time is the slice corresponding to the optimal AMF entity, and the application program corresponding to the APP-ID in the flow identifier in the URSP corresponding to the source AMF entity is not in an active state (may be in an Idle or disconnected state).

B. The management node records and Stores User Permanent Identifier (SUPI) information of the terminal, when a target AMF entity cannot allocate 5G Globally Unique Temporary UE Identity (5G-GUTI) or loses the SUPI information for the terminal temporarily, a request message needs to be sent to the management node, and the management node sends the terminal SUPI information and allowed NSSAI (allowed NSSAI) information to the target AMF entity. Therefore, The target AMF entity avoids wasting signaling and time by applying for and authenticating The information of The user to a Unified Data Management (UDM) entity.

9. The management node sends a redirection notification to the source AMF entity; wherein redirecting the notification comprises: GUAMI, route pointer, address information of the target AMF entity.

10. The source AMF entity directly transmits the transmission selection of the Non-Access-Stratum (NAS) security context to the target AMF entity, and does not select the mode of back transmission to the gNB. The source AMF entity performs AMF entity redirection, namely sends a Namf _ Communication _ N1MessageNotify message to the target AMF entity, wherein the Namf _ Communication _ N1MessageNotify message comprises the following information: the Radio Access Network ((R) AN, Radio Access Network) is enabled to identify the N2 termination point and NAS security context, and SUPI information of the terminal, etc. The target AMF entity will terminate with the updated N2.

The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.

Fig. 4 is a schematic structural diagram of a management node according to another embodiment of the present application.

As shown in fig. 4, another embodiment of the present application provides a management node, including:

a first receiving module 401, configured to receive user behavior information of a protocol data set unit PDU session carried by each currently connected slice and reported by a terminal, and a cell number of a serving cell where the terminal is currently located; wherein the user behavior information comprises: averaging the length of the continuous time, averaging the established release frequency;

a selecting module 402 for:

selecting an optimal AMF entity for each slice connected with the terminal;

a first sending module 403, configured to send a redirection notification to the source AMF entity; wherein the redirect notification includes: a globally unique AMF identifier GUAMI of the target AMF entity.

In some exemplary embodiments, the first sending module 403 is further configured to:

the first receiving module 401 is further configured to:

In some exemplary embodiments, the selection module 402 is specifically configured to implement the selection of the optimal AMF entity for each slice to which the terminal is connected, in the following manner:

In some exemplary embodiments, the selection module 402 is further configured to:

screening a second AMF entity set which can be shared by N-1 slices connected with the terminal and an independent AMF entity set of the remaining single slice under the condition that a first AMF entity set which can be shared by all slices connected with the terminal cannot be screened;

In some exemplary embodiments, the selecting module 402 is specifically configured to implement AMF entity redirection by determining a slice to which the terminal is connected according to the user behavior information and the cell number of the serving cell, in the following manner:

correspondingly, the selecting module 402 is specifically configured to implement the selecting of the target AMF entity for redirection according to the optimal AMF entity in the following manner:

In some exemplary embodiments, the user behavior information further comprises: session and service continuation mode;

In some exemplary embodiments, the selecting module 402 is specifically configured to implement the selecting of the target AMF entity for redirection according to the optimal AMF entity by the following manners:

The specific implementation process of the management node is the same as the specific implementation process of the AMF entity redirection method applied to the management node in the foregoing embodiment, and is not described here again.

Fig. 5 is a schematic structural component diagram of a terminal according to another embodiment of the present application.

As shown in fig. 5, another embodiment of the present application provides a terminal, including:

a second sending module 501, configured to report, to a management node, user behavior information of a PDU session carried by each slice that is currently connected, and a cell number of a serving cell where the PDU session is currently located; wherein the user behavior information comprises: average continuous time length, average build-up release frequency.

In some exemplary embodiments, the terminal further includes:

a second receiving module 502, configured to receive a redirection message sent by the management node before a protection timeslot for performing AMF entity redirection;

a state holding module 503, configured to hold a CM-CONNECT state in the protection timeslot;

the second sending module 501 is further configured to:

The specific implementation process of the terminal is the same as the specific implementation process of the AMF entity redirection method applied to the terminal in the foregoing embodiment, and is not described here again.

As shown in fig. 6, another embodiment of the present application provides an AMF entity redirection system, including:

a management node 601, configured to:

selecting an optimal AMF entity for each slice connected with the terminal;

a terminal 602 configured to:

The specific implementation process of the AMF entity redirection system is the same as that of the AMF entity redirection method in the foregoing embodiment, and is not described here again.

Each module in the present embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, or may be implemented by a combination of a plurality of physical units. In addition, in order to highlight the innovative part of the present application, a unit that is not so closely related to solving the technical problem proposed by the present application is not introduced in the present embodiment, but it does not indicate that no other unit exists in the present embodiment.

The present embodiments also provide an electronic device, comprising one or more processors; the storage device stores one or more programs thereon, and when the one or more programs are executed by the one or more processors, the one or more processors implement the AMF entity redirection method provided in this embodiment, and in order to avoid repeated description, detailed steps of the AMF entity redirection method are not described herein again.

The present embodiment further provides a computer readable medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the AMF entity redirection method provided in this embodiment, and in order to avoid repeated descriptions, specific steps of the AMF entity redirection method are not described herein again.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Those skilled in the art will appreciate that although some embodiments described herein include some features included in other embodiments instead of others, combinations of features of different embodiments are meant to be within the scope of the embodiments and form different embodiments.

It is to be understood that the above embodiments are merely exemplary embodiments that are employed to illustrate the principles of the present application, and that the present application is not limited thereto. It will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the application, and these changes and modifications are to be considered as the scope of the application.

Claims

1. A redirection method of an access and mobility management function (AMF) entity is applied to a management node, and comprises the following steps:

selecting an optimal AMF entity for each slice connected with the terminal;

2. The AMF entity redirection method according to claim 1, wherein after selecting the target AMF entity for redirection according to the optimal AMF entity, before sending the redirection notification to the source AMF entity, the method further comprises:

3. The AMF entity redirection method according to claim 1 or 2, wherein said selecting an optimal AMF entity for each slice to which the terminal has connected comprises:

4. The AMF entity redirection method according to claim 3, wherein in case that the first AMF entity set that all slices connected to the terminal can share is not screened out, the selecting an optimal AMF entity for each slice connected to the terminal further comprises:

5. The AMF entity redirection method according to claim 1, wherein the determining that a slice to which the terminal is connected according to the user behavior information and the cell number of the serving cell may perform AMF entity redirection comprises:

6. The AMF entity redirection method according to claim 1, wherein the user behavior information further comprises: session and service continuation mode;

7. The AMF entity redirection method according to claim 1, wherein the user behavior information further comprises: session and service continuation mode;

selecting an optimal AMF entity corresponding to the fourth slice as the target AMF entity for redirection; wherein the fourth slice is a slice with the smallest average establishment release frequency of the borne PDU sessions in the slices with the session and service continuity mode of the PDU sessions borne by the slice to which the terminal is connected and the third slice being 1.

8. The AMF entity redirection method according to claim 1, wherein the selecting the target AMF entity for redirection according to the optimal AMF entity comprises:

9. The AMF entity redirection method according to claim 1, wherein the user behavior information further comprises: session and service continuation mode;

10. A redirection method of access and mobility management function (AMF) entity is applied to a terminal, and comprises the following steps:

11. The AMF entity redirection method according to claim 10, further comprising:

maintaining a CM-CONNECT state during said guard time slot;

12. A management node, comprising:

the first receiving module is used for receiving user behavior information of a protocol data set unit (PDU) session borne by each currently connected slice reported by a terminal and a cell number of a current serving cell; wherein the user behavior information comprises: averaging the length of the continuous time, averaging the established release frequency;

a selection module to:

selecting an optimal AMF entity for each slice connected with the terminal;

13. A terminal, comprising:

14. An access and mobility management function, AMF, entity redirection system, comprising:

a management node to:

selecting an optimal AMF entity for each slice connected with the terminal;

a terminal for:

reporting user behavior information of a protocol data set unit (PDU) conversation borne by each slice which is connected currently and a cell number of a serving cell where the PDU conversation is located currently to a management node; wherein the user behavior information comprises: average duration, average build-up release frequency.