WO2022052875A1

WO2022052875A1 - Terminal cross-region communication method, network element device, and storage medium

Info

Publication number: WO2022052875A1
Application number: PCT/CN2021/116525
Authority: WO
Inventors: 涂小勇; 刘建华; 刘俊羿
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-09-14
Filing date: 2021-09-03
Publication date: 2022-03-17
Also published as: CN114189844A

Abstract

Embodiments of the present application provide a terminal cross-region communication method, network element device, and storage medium, belonging to the field of communications. The method comprises: if a current corresponding first S-NSSAI of a terminal is not a currently allowed available first NSSAI of the terminal, then determining a second S-NSSAI mapped in the first NSSAI; replacing the first S-NSSAI with the second S-NSSAI to achieve cross-region communication of terminals on the basis of the second S-NSSAI.

Description

Terminal cross-region communication method, network element device and storage medium

cross reference

This application is based on the Chinese patent application with the application number "202010963778.8" and the application date is September 14, 2020, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference. Apply.

technical field

The present application relates to the field of communication technologies, and in particular, to a terminal cross-region communication method, a network element device and a storage medium.

Background technique

Network slicing is an on-demand networking method that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice performs logic from the radio access network bearer network to the core network. isolation to suit a wide variety of applications. Each network slice corresponds to a unique S-NSSAI (Single Network Slice Selection Assistance Information) identifier, and network slices can be correctly selected based on the S-NSSAI identifier.

The user terminal can roam across PLMN (Public Land Mobile Network, public land mobile network), or roam in different areas without crossing PLMN, such as roaming in different provinces. Network slicing supports roaming across PLMNs. For roaming not across PLMNs in different regions, the operator plans different non-standard S-NSSAI for the same service in different regions (such as different provinces) instead of standard S-NSSAI. Different, so that the network slicing can not continue to be used, and the user's business execution cannot be guaranteed.

SUMMARY OF THE INVENTION

An embodiment of the present application provides a method for terminal cross-area communication, including: when the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal, determining that the first S-NSSAI is mapped in the first NSSAI The second S-NSSAI; the first S-NSSAI is replaced with the second S-NSSAI, so as to realize the cross-area communication of the terminal based on the second S-NSSAI.

An embodiment of the present application further provides a network element device, where the network element device includes a processor, a memory, a computer program stored in the memory and executable by the processor, and a data bus for realizing connection and communication between the processor and the memory , wherein when the computer program is executed by the processor, the steps of any one of the terminal cross-region communication methods provided in the specification of this application are implemented.

The embodiments of the present application further provide a storage medium for computer-readable storage, where the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the implementation as provided in the specification of the present application. Any one of the steps of a method for a terminal to communicate across regions.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

Figure 1 is a schematic structural diagram of a 5G network architecture;

FIG. 2 is a schematic flowchart 1 of a method for cross-region communication of a terminal according to an embodiment of the present application;

FIG. 3 is a second schematic flowchart of a method for cross-region communication of a terminal according to an embodiment of the present application;

4 is a schematic flowchart of determining the second NSSAI available for the current candidate of the terminal according to an embodiment of the present application;

FIG. 5 is a third schematic flowchart of a method for cross-region communication of a terminal according to an embodiment of the present application;

6 is a flowchart of a registration process when there is no PDU Session provided by an embodiment of the present application;

FIG. 7 is a fourth schematic flowchart of a method for terminal cross-region communication according to an embodiment of the present application;

8 is a flowchart of a registration process when there is a PDU Session provided by an embodiment of the present application;

FIG. 9 is a schematic flowchart five of a method for cross-region communication of a terminal according to an embodiment of the present application;

10 is a flowchart of establishing a PDU session provided by an embodiment of the present application;

FIG. 11 is a schematic structural block diagram of a network element device according to an embodiment of the application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The flowcharts shown in the figures are for illustration only, and do not necessarily include all contents and operations/steps, nor do they have to be performed in the order described. For example, some operations/steps can also be decomposed, combined or partially combined, so the actual execution order may be changed according to the actual situation.

It should be understood that the terms used in the specification of the present application herein are for the purpose of describing particular embodiments only and are not intended to limit the present application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly dictates otherwise.

The main purpose of the embodiments of the present application is to provide a terminal cross-area communication method, network element device and storage medium, aiming at realizing that network slices are available when the terminal does not roam across PLMNs in different areas, thereby ensuring normal execution of user services.

The embodiments of the present application provide a method, a network element device, and a storage medium for cross-area communication of a terminal. In the embodiments of the present application, when the terminal does not roam cross-area across PLMNs, the first S-NSSAI currently corresponding to the terminal does not belong to the one that the terminal is currently allowed to use. When the first NSSAI is used, determine the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI, and replace the first S-NSSAI with the second S-NSSAI, so that the terminal currently has the second S-NSSAI corresponding to the second S-NSSAI. Network slicing is available, that is, to realize cross-regional communication of terminals to ensure normal business execution.

Embodiments of the present application provide a method for terminal cross-area communication, a network element device, and a storage medium. Among them, the terminal cross-region communication method can be applied to network element equipment, and the network element equipment can be AMF (Access and Mobility Management function, access and mobility management function), NSSF (Network Slice Selection Function) in the 5G network architecture, network slice selection function) and other network element functional entities NF.

Please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a 5G network architecture. The 5G network architecture includes:

UE (User Equipment, terminal), mainly accesses the 5G network through the wireless air interface and obtains services. The terminal exchanges information with the base station through the air interface, and exchanges information with the AMF of the core network through the NAS (Non-Access Stratum, non-access stratum signaling). .

RAN (Radio Access Network, Radio Access Network) is responsible for air interface resource scheduling of terminal access network and air interface connection management.

AMF (Access and Mobility Management function, access and mobility management function), the core network control plane entity, is mainly responsible for user mobility management, including: registration and temporary identity allocation; maintaining idle (IDLE) and connection (CONNECT) status and status Migration; switching in the connected state; triggering functions such as paging when the user is idle.

AUSF (Authentication Server Function), the core network control plane entity, is mainly responsible for user authentication and authorization to ensure that the user is a legitimate user.

UDM (Unified Data Management, unified data management function), core network control plane entity, home user server, permanent storage of user subscription data.

SMF (Session Management function, session management function), the core network control plane entity, is mainly responsible for maintaining PDU (Protocol Data Unit, protocol data unit) Session, responsible for allocating user IP addresses, with QoS (Quality of Service, quality of service) control and Charging function; the user receives downlink data packets in the idle state, buffers them, and notifies the AMF to page the user and other functions.

UPF (User plane function, user plane function), the core network user plane function entity, is responsible for the forwarding of user data packets, and also collects statistics on user data packets for billing and other functions.

PCF (Policy Control Function), a core network control plane entity, is a functional entity responsible for access and mobility management policies, terminal policies, session management policies and charging rules. This functional entity mainly generates access and mobility management policies, terminal routing policies, QoS rules and charging rules for user data transfer based on service information, user subscription information and operator configuration information.

NEF (Network Exposure Function, capability exposure function), the core network control plane entity, is responsible for the opening of mobile network capabilities to the outside world.

NRF (NF Repository Function, network function library function), the core network control plane entity, is responsible for the dynamic registration of the service capability of the network function and the discovery of the network function.

NSSF (Network Slice Selection Function), the core network control plane entity, is responsible for the selection of the target NSI (Network Slice Instance, network slice instance).

AF (Application Function), an application entity, is responsible for providing users with specific services.

Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and features in the embodiments may be combined with each other without conflict.

Please refer to FIG. 2 , which is a schematic flowchart of a method for cross-region communication of a terminal according to an embodiment of the present application.

As shown in FIG. 2 , the terminal cross-region communication method includes step S101 and step S102.

Step S101: When the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal, determine the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI.

It should be noted that the terminal includes, but is not limited to, electronic devices with communication functions, such as mobile phones, tablet computers, and wearable devices. During the use of the terminal, for example, when performing initial registration or registration update, the currently available NSSAI (Network Slice Selection Assistance Information) of the terminal is obtained, and the current corresponding S-NSSAI (Single Network Slice Network) of the terminal is detected. Whether Slice Selection Assistance Information, single network slice selection assistance information) belongs to the NSSAI currently allowed by the terminal, that is, whether the S-NSSAI currently corresponding to the terminal is available in the currently accessed AMF or area. For convenience of description, the NSSAI currently allowed to be available by the terminal is referred to as the first NSSAI, and the S-NSSAI currently corresponding to the terminal is referred to as the first S-NSSAI. That is, it is detected whether the first S-NSSAI is the S-NSSAI in the first NSSAI. If the first S-NSSAI is the S-NSSAI in the first NSSAI, the first S-NSSAI is available in the currently accessed AMF or area; otherwise, if the first S-NSSAI is not the S-NSSAI in the first NSSAI, Then the first S-NSSAI is unavailable in the currently accessed AMF or area.

If the first S-NSSAI is an S-NSSAI in the first NSSAI, communication processes such as terminal registration and session establishment may be implemented based on the first S-NSSAI.

If the first S-NSSAI is not the S-NSSAI in the first NSSAI, for example, when the terminal does not roam across PLMNs (Public Land Mobile Network, public land mobile networks) across regions, such as roaming across different provinces, the current corresponding The first S-NSSAI is unavailable in the current access area, and the first S-NSSAI does not belong to the first NSSAI, that is, the first S-NSSAI is not the S-NSSAI in the first NSSAI. At this time, the S-NSSAI mapped by the first S-NSSAI in the first NSSAI is determined. For convenience of description, the S-NSSAI mapped by the first S-NSSAI in the first NSSAI is hereinafter referred to as the second S-NSSAI. That is, the first S-NSSAI is mapped to the second S-NSSAI available in the current access area.

Step S102 , replacing the first S-NSSAI with the second S-NSSAI, so as to realize cross-region communication of the terminal based on the second S-NSSAI.

After obtaining the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI, replace the first S-NSSAI with the second S-NSSAI to realize cross-region registration and establishment of the terminal based on the second S-NSSAI Sessions and other communication processes.

In one embodiment, referring to FIG. 3 , before step S101 , it includes: step S103 and step S104 .

Step S103: Determine the second NSSAI available for the terminal's current candidate according to the terminal's contracted NSSAI and the terminal's request NSSAI.

Obtain the request NSSAI (Requested NSSAI) corresponding to the terminal and the subscription NSSAI (Subscribed NSSAI) corresponding to the terminal. Exemplarily, the terminal initiates an initial registration process, or the terminal initiates a registration update process, the message carries information such as the request NSSAI corresponding to the terminal, and the request NSSAI carried in the message is extracted. Exemplarily, the subscription NSSAI corresponding to the terminal is obtained locally from the AMF; or the subscription NSSAI corresponding to the terminal is obtained from the UDM, and the UDM permanently stores user subscription data, including the subscription NSSAI.

In one embodiment, referring to FIG. 4 , step S103 includes sub-step S1031 and sub-step S1032.

Sub-step S1031: Determine the intersection S-NSSAI of the subscription NSSAI and the request NSSAI.

After obtaining the contracted NSSAI and the requesting NSSAI corresponding to the terminal, the contracted NSSAI and the requesting NSSAI are compared to determine the intersection S-NSSAI of the contracted NSSAI and the requesting NSSAI, that is, the same S-NSSAI in the contracted NSSAI and the requesting NSSAI.

Sub-step S1032: Determine the second NSSAI according to the intersection S-NSSAI.

According to the intersection S-NSSAI of the subscription NSSAI and the request NSSAI, that is, based on the same S-NSSAI in the subscription NSSAI and the request NSSAI, the NSSAI available for the terminal's current candidate (Allowed NSSAI1) is generated. For convenience of description, the NSSAI available for the current candidate of the terminal is hereinafter referred to as the second NSSAI. The second NSSAI consists of the same S-NSSAI in the contracting NSSAI and the requesting NSSAI.

Step S104 , if there is an S-NSSAI in the second NSSAI and the terminal is currently unavailable, map the unavailable S-NSSAI to the currently available S-NSSAI of the terminal, and generate a first NSSAI mapped by the second NSSAI.

Based on the determined second NSSAI, if there is an S-NSSAI in the second NSSAI that is not available in the AMF or area currently accessed by the terminal, for example, part or all of the S-NSSAI in the second NSSAI is in the AMF currently accessed by the terminal Or the area is unavailable. At this time, based on the PLMN accessed by the terminal, the area currently accessed by the terminal, and the second NSSAI, some or all of the S-NSSAI in the second NSSAI that are not available in the currently accessed AMF or area are used. , mapped to the equivalent S-NSSAI available in the AMF or area currently accessed by the terminal, based on the mapped equivalent S-NSSAI available in the AMF or area currently accessed by the terminal to replace the second NSSAI in the current access The incoming AMF or the S-NSSAI not available in the area generates the first NSSAI (Allowed NSSAI2) mapped by the second NSSAI.

In an embodiment, after step S104, the step may include: saving the first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI.

Exemplarily, the AMF stores the first NSSAI (Allowed NSSAI2), the second NSSAI (Allowed NSSAI1), and the mapping relationship between the first NSSAI and the second NSSAI. For example, in an instance where the method is applied to an NSSF, after generating the first NSSAI mapped to the second NSSAI, the NSSF feeds back a response message for obtaining network slice information to the AMF, where the message carries the first NSSAI, the second NSSAI, and the first NSSAI As for the mapping relationship with the second NSSAI, the AMF stores the first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI.

In one embodiment, referring to FIG. 5 , before step S103 , it includes: step S105 and step S106 .

Step S105: Receive the initial registration message sent by the terminal, or the first registration update message sent when the terminal does not activate the PDU Session.

When the terminal initiates registration, for example, the terminal initiates the initial registration process, or the terminal initiates the registration update process when the PDU Session is not activated, receives the initial registration message sent by the terminal, or receives the registration update message sent when the terminal does not activate the PDU Session. For ease of description, the registration update message sent when the terminal does not activate the PDU Session is referred to as the first registration update message hereinafter. The initial registration message and the first registration update message carry information such as the request NSSAI corresponding to the terminal.

Step S106: Obtain the request NSSAI carried in the initial registration message or the first registration update message, and obtain the subscription NSSAI from the local or UDM.

When receiving the initial registration message or the first registration update message, obtain the request NSSAI corresponding to the terminal carried in the initial registration message or the first registration update message. And, based on the received initial registration message or the first registration update message, the registration process is processed, and the subscription NSSAI corresponding to the terminal is obtained locally; or the subscription NSSAI corresponding to the terminal is obtained from the UDM.

After that, according to the contracted NSSAI and the requested NSSAI, the second NSSAI is determined, and the first NSSAI mapped by the second NSSAI is determined. If the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI, it is determined that the first S-NSSAI is in For the second S-NSSAI mapped in the first NSSAI, replace the first S-NSSAI with the second S-NSSAI. The specific operation process is the same as that in the above-mentioned embodiments, which will not be repeated here.

After step S102, step S107 is included.

Step S107: Send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI.

After replacing the first S-NSSAI with the second S-NSSAI, continue processing the registration process, and then send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI. The terminal implements normal cross-area communication based on the second NSSAI.

Referring to Figure 6, Figure 6 is a flowchart of the registration process when there is no PDU Session, and the specific process is as follows:

A1): The UE (terminal) initiates the initial registration process, or initiates the registration update process when the PDU Session is not activated, and the message carries information such as Requested NSSAI (Requested NSSAI).

A2): The AMF processes the registration process, and the AMF obtains the subscribed NSSAI (Subscribed NSSAI) locally, or the AMF obtains the subscribed NSSAI and other information from the UDM.

A3): AMF sends a request message for obtaining network slice information to NSSF. The request message carries information such as request NSSAI, subscription NSSAI, Serving PLMN (ie, the PLMN currently accessed by the UE), and the currently accessed area.

A4): The NSSF takes the intersection of the request NSSAI and the contracted NSSAI to determine the second NSSAI (Allowed NSSAI1).

A5): The NSSF finds that some or all of the S-NSSAIs in the second NSSAI are not available in the currently accessed AMF or area. In the second NSSAI, part or all of the S-NSSAI that is not available in the currently accessed AMF or area is mapped to the equivalent S-NSSAI available in the AMF or area currently accessed by the UE, and the mapped S-NSSAI is used to replace Part or all of the S-NSSAI that is unavailable in the currently accessed AMF or area in the second NSSAI forms the first NSSAI (Allowed NSSAI2). The NSSF determines whether redirection is required based on the first NSSAI and the like.

A6): The NSSF returns a network slice information acquisition response message to the AMF, where the response message carries information such as the first NSSAI, the second NSSAI and their mapping relationships.

A7): The AMF stores the first NSSAI, the second NSSAI and their mapping relationships.

A8): In addition to interacting with the UE, the AMF takes the first NSSAI as the currently available NSSAI of the UE, for example, determines whether redirection is required according to the first NSSAI or the like.

A9): The AMF continues to process the registration process.

A10): The AMF sends a registration acceptance message to the UE, and the registration acceptance message carries the second NSSAI.

In an embodiment, referring to FIG. 7 , before step S103 , it includes: step S108 and step S109 .

Step S108: Receive the second registration update message sent when the terminal has activated the PDU Session.

When the terminal has been registered and the PDU Session has been activated, when the terminal initiates the registration update process, it receives the registration update message sent by the terminal. For convenience of description, the registration update message sent when the terminal has activated the PDU Session is referred to as the second registration update message below. The second registration update message carries information such as the request NSSAI corresponding to the terminal.

Step S109: Obtain the request NSSAI carried in the second registration update message, and obtain the subscription NSSAI from the local or UDM.

When receiving the second registration update message, obtain the request NSSAI corresponding to the terminal carried in the second registration update message. And, based on the received second registration update message, the registration process is processed, and the subscription NSSAI corresponding to the terminal is obtained locally; or the subscription NSSAI corresponding to the terminal is obtained from the UDM.

After that, according to the contracted NSSAI and the requested NSSAI, the second NSSAI is determined, and the first NSSAI to which the second NSSAI is mapped is determined. If the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI, it is determined that the first S-NSSAI is in For the second S-NSSAI mapped in the first NSSAI, replace the first S-NSSAI with the second S-NSSAI. The specific operation process is the same as that in the above-mentioned embodiments, which is not repeated here.

After step S102, step S110 is included.

Step S110: Update the S-NSSAI corresponding to the activated PDU Session to the second S-NSSAI.

After replacing the first S-NSSAI with the second S-NSSAI, update the S-NSSAI of the activated PDU Session to the second S-NSSAI, that is, use the second S-NSSAI as the S-NSSAI of the activated PDU Session subsequently. - NSSAI.

After that, continue to process the registration process, and then send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI. The terminal implements normal cross-area communication based on the second NSSAI.

Referring to Figure 8, Figure 8 is a flowchart of the registration process when there is a PDU Session, and the specific process is as follows:

B1): The UE has been registered and the PDU Session has been activated. The UE initiates the registration update process, and the message carries information such as Requested NSSAI (Requested NSSAI).

B2): The AMF processes the registration process, the AMF obtains the subscribed NSSAI (Subscribed NSSAI) locally, or the AMF obtains the subscribed NSSAI and other information from the UDM.

B3): AMF sends a request message for obtaining network slice information to NSSF, the request message carries information such as request NSSAI, subscription NSSAI, Serving PLMN (ie the PLMN currently accessed by the UE), and currently accessed area.

B4): The NSSF takes the intersection of the requesting NSSAI and the contracting NSSAI, and determines the second NSSAI (Allowed NSSAI1).

B5): The NSSF finds that some or all of the S-NSSAIs in the second NSSAI are not available in the currently accessed AMF or area. In the second NSSAI, part or all of the S-NSSAI that is not available in the currently accessed AMF or area is mapped to the equivalent S-NSSAI available in the AMF or area currently accessed by the UE, and the mapped S-NSSAI is used to replace Part or all of the S-NSSAI that is unavailable in the currently accessed AMF or area in the second NSSAI forms the first NSSAI (Allowed NSSAI2). The NSSF determines whether redirection is required based on the first NSSAI and the like.

B6): The NSSF returns a network slice information acquisition response message to the AMF, where the response message carries information such as the first NSSAI, the second NSSAI and their mapping relationships.

B7): The AMF stores the first NSSAI, the second NSSAI and their mapping relationships.

B8): In addition to interacting with the UE, the AMF takes the first NSSAI as the currently available NSSAI of the UE, for example, determines whether redirection is required according to the first NSSAI or the like.

B9): AMF determines that the first S-NSSAI corresponding to the activated PDU Session is not in the first NSSAI (Allowed NSSAI2).

B10): AMF replaces the first S-NSSAI of the PDU Session with the corresponding second S-NSSAI in the first NSSAI.

B11): The AMF subsequently uses the second S-NSSAI as the S-NSSAI of the activated PDU Session.

B12): AMF notifies SMF that the S-NSSAI of its PDU Session is updated to the second S-NSSAI.

B13): The SMF subsequently uses the second S-NSSAI as the S-NSSAI of the PDU Session to update other network element functional entities NF.

B14): The AMF continues to process the registration process.

B15): The AMF sends a registration acceptance message to the UE, and the registration acceptance message carries the second NSSAI.

In an embodiment, referring to FIG. 9 , before step S101 , it includes: step S111 and step S112 .

Step S111: Receive a PDU Session establishment request message sent by the terminal.

Step S112: Obtain the first S-NSSAI carried in the request message.

When establishing a PDU session, the terminal sends a PDU Session establishment request message, wherein the PDU Session establishment request message carries information such as the first S-NSSAI. By receiving the PDU Session establishment request message sent by the terminal, the first S-NSSAI carried in the PDU Session establishment request message is obtained.

If the first S-NSSAI is not the NSSAI in the first NSSAI, determine the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI, and replace the first S-NSSAI with the second S-NSSAI. The specific operation process is the same as that in the above-mentioned embodiments, which is not repeated here.

After step S102, step S113 is included.

Step S113, based on the second S-NSSAI, establish a PDU Session.

After replacing the first S-NSSAI with the second S-NSSAI, use the second S-NSSAI as the request S-NSSAI carried by the terminal to establish a PDU Session.

In one embodiment, after the PDU Session is established based on the second S-NSSAI, a corresponding SMF is selected according to the second S-NSSAI, and a PDU session establishment request message is sent to the selected SMF, wherein the PDU session establishment request The message carries information such as the first S-NSSAI and the second S-NSSAI. The SMF feeds back a PDU session establishment accept message based on the first S-NSSAI, where the PDU session establishment accept message carries the first S-NSSAI. When receiving the PDU session establishment accept message fed back by the SMF, a PDU session request message including the PDU session establishment accept message is sent to the RAN to establish the PDU session.

Referring to FIG. 10, FIG. 10 is a flowchart of establishing a PDU session, and the specific process is as follows:

C1): The UE sends a PDU Session establishment request message, and the message carries information such as the first S-NSSAI (Requested S-NSSAI).

C2): AMF finds that the first S-NSSAI is not in the first NSSAI, but is in the second NSSAI.

C3): The AMF replaces the first S-NSSAI with the corresponding second S-NSSAI in the first NSSAI.

C4): The AMF subsequently uses the second S-NSSAI as the first S-NSSAI carried by the UE to establish a PDU Session.

C5): AMF selects SMF according to the second S-NSSAI, DNN (Data Network Name) and other information.

C6): AMF sends a PDU session establishment request message to SMF, carrying information such as the first S-NSSAI and the second S-NSSAI.

C7): The SMF obtains the subscription data from the UDM, and uses the first S-NSSAI to match the subscription NSSAI (Subscribed NSSAI) in the subscription data.

C8): The SMF returns a PDU session establishment response message to the AMF.

C9): When the SMF selects the PCF and obtains the SM Policy (session management policy) from the PCF, the SMF provides the PCF with the second S-NSSAI.

C10): The SMF selects a UPF based on information such as the second S-NSSAI, and completes session creation to the UPF, such as N4PDU session creation.

C11): SMF constructs an N2PDU session request message, carrying the second S-NSSAI; SMF constructs a PDU session establishment accept message, carrying the first S-NSSAI.

C12): The SMF sends an N1N2 messaging message to the AMF, carrying an N2PDU session request message and a PDU session establishment accept message.

C13): The AMF sends a PDU session request message to the RAN, such as an N2PDU session request message, which includes a PDU session establishment accept message.

C14): AMF continues to process the PDU Session establishment process until the process ends.

The terminal cross-area communication method provided by the above embodiment, when the terminal does not roam across the PLMN cross-area, and the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI that the terminal is currently allowed to use, it is determined that the first S-NSSAI is in the first S-NSSAI. A second S-NSSAI mapped in the NSSAI, and the first S-NSSAI is replaced by the second S-NSSAI, so that the terminal currently has the network slice corresponding to the second S-NSSAI available, that is, the cross-regional communication of the terminal is realized, Make sure the business is running properly.

Please refer to FIG. 11. FIG. 11 is a schematic structural block diagram of a network element device provided by an embodiment of the present application.

As shown in FIG. 11 , the network element device 300 includes a processor 301 and a memory 302, and the processor 301 and the memory 302 are connected through a bus 303, such as an I2C (Inter-integrated Circuit) bus.

Specifically, the processor 301 is configured to provide computing and control capabilities, and support the operation of the entire network element device. The processor 301 can be a central processing unit (Central Processing Unit, CPU), and the processor 301 can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC) ), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Wherein, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor or the like.

Specifically, the memory 302 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, a mobile hard disk, and the like.

Those skilled in the art can understand that the structure shown in FIG. 11 is only a block diagram of a partial structure related to the solution of the embodiment of the present application, and does not constitute a limitation on the network element equipment to which the solution of the embodiment of the present application is applied. A particular server may include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

The processor is configured to run the computer program stored in the memory, and implement any one of the terminal cross-region communication methods provided in the embodiments of the present application when the computer program is executed.

In one embodiment, the processor is configured to run a computer program stored in the memory, and implement the following steps when executing the computer program:

When the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI that the terminal is currently allowed to use, determining the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI;

The first S-NSSAI is replaced with the second S-NSSAI, so as to realize the cross-area communication of the terminal based on the second S-NSSAI.

In one embodiment, the processor determines the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI when the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal. Before NSSAI, used to implement:

According to the contracted NSSAI of the terminal and the requested NSSAI of the terminal, determine the second NSSAI currently available for the terminal candidate;

If there is an S-NSSAI in the second NSSAI and the terminal is currently unavailable, the unavailable S-NSSAI is mapped to the currently available S-NSSAI of the terminal, and the first NSSAI mapped by the second NSSAI is generated.

In one embodiment, when the processor determines the second NSSAI available for the terminal's current candidate according to the terminal's subscription NSSAI and the terminal's request NSSAI, the processor is configured to:

Determine the intersection S-NSSAI of the contracted NSSAI and the requested NSSAI;

According to the intersection S-NSSAI, the second NSSAI is determined.

In one embodiment, after implementing the first NSSAI for generating the second NSSAI mapping, the processor is configured to implement:

The first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI are stored.

In an embodiment, before the processor determines the second NSSAI available for the terminal's current candidate according to the terminal's subscription NSSAI and the terminal's request NSSAI, the processor is configured to:

The initial registration message sent by the receiving terminal, or the first registration update message sent when the receiving terminal does not activate the PDU Session;

Obtain the request NSSAI carried in the initial registration message or the first registration update message, and obtain the subscription NSSAI from the local or UDM;

After replacing the first S-NSSAI with the second S-NSSAI, the processor is configured to implement:

A registration acceptance message is sent to the terminal, and the registration acceptance message carries the second NSSAI.

receiving the second registration update message sent when the terminal has activated the PDU Session;

Obtain the request NSSAI carried in the second registration update message, and obtain the subscription NSSAI from the local or UDM;

Update the S-NSSAI corresponding to the activated PDU Session to the second S-NSSAI.

Receive the PDU Session establishment request message sent by the terminal;

obtaining the first S-NSSAI carried in the request message;

Based on the second S-NSSAI, a PDU Session is established.

In one embodiment, after the processor establishes the PDU Session based on the second S-NSSAI, the processor is configured to implement:

According to the second S-NSSAI, select SMF;

Send a PDU session establishment request message to the SMF;

When receiving the PDU session establishment accept message fed back by the SMF, a PDU session request message including the PDU session establishment accept message is sent to the RAN to establish the PDU session.

It should be noted that those skilled in the art can clearly understand that, for the convenience and brevity of the description, for the specific working process of the network element device described above, reference may be made to the corresponding process in the foregoing embodiments of the terminal cross-region communication method. This will not be repeated here.

The embodiments of the present application further provide a storage medium for computer-readable storage, where the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the embodiments of the present application. Steps of any terminal cross-region communication method provided in the specification.

The storage medium may be an internal storage unit of the network element device in the foregoing embodiment, such as a hard disk or a memory of the network element device. The storage medium may also be an external storage device of the network element device, such as a plug-in hard disk equipped on the network element device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, and a flash memory card (Flash card). Card), etc.

Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, functional modules/units in the systems, and devices can be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware embodiments, 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 composed of several physical components Components execute cooperatively. Some or all 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). As known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules or other data flexible, removable and non-removable media. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store 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 can include any information delivery media, as is well known to those of ordinary skill in the art .

It should be understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items. It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or system comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or system. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments. The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or modifications within the technical scope disclosed in the present application. Replacement, these modifications or replacements should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A terminal cross-region communication method, comprising:

When the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI that the terminal is currently allowed to use, determining the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI;

The first S-NSSAI is replaced with the second S-NSSAI, so as to implement cross-area communication of the terminal based on the second S-NSSAI.
The method for terminal cross-area communication according to claim 1, wherein the first S-NSSAI is determined when the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal Before the second S-NSSAI mapped in the first NSSAI, it includes:

According to the subscription NSSAI of the terminal and the request NSSAI of the terminal, determine the second NSSAI currently available for the terminal candidate;

If there is an S-NSSAI in the second NSSAI because the terminal is currently unavailable, the unavailable S-NSSAI is mapped to the currently available S-NSSAI of the terminal, and all the mappings of the second NSSAI are generated. Describe the first NSSAI.
The method for terminal cross-area communication according to claim 2, wherein the determining the second NSSAI available to the terminal's current candidate according to the terminal's subscription NSSAI and the terminal's request NSSAI comprises:

determining the intersection S-NSSAI of the contracted NSSAI and the requested NSSAI;

The second NSSAI is determined according to the intersection S-NSSAI.
The method for terminal cross-area communication according to claim 2 or 3, wherein after the generating the first NSSAI mapped to the second NSSAI, the method comprises:

The first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI are saved.
The method for terminal cross-area communication according to any one of claims 2 to 4, wherein, before determining the second NSSAI available to the terminal's current candidate according to the terminal's subscription NSSAI and the terminal's request NSSAI, include:

Receive the initial registration message sent by the terminal, or receive the first registration update message sent when the terminal does not activate the PDU Session;

Obtain the request NSSAI carried in the initial registration message or the first registration update message, and obtain the subscription NSSAI from the local or UDM;

After replacing the first S-NSSAI with the second S-NSSAI, including:

Send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI.
The method for terminal cross-area communication according to any one of claims 2 to 4, wherein, before determining the second NSSAI available to the terminal's current candidate according to the terminal's subscription NSSAI and the terminal's request NSSAI, include:

receiving the second registration update message sent when the terminal has activated the PDU Session;

obtaining the request NSSAI carried in the second registration update message, and obtaining the subscription NSSAI from the local or UDM;

After replacing the first S-NSSAI with the second S-NSSAI, including:

The S-NSSAI corresponding to the activated PDU Session is updated to the second S-NSSAI.
The method for terminal cross-area communication according to any one of claims 1 to 6, wherein when the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal, determining the The first S-NSSAI before the second S-NSSAI mapped in the first NSSAI includes:

receiving a PDU Session establishment request message sent by the terminal;

obtaining the first S-NSSAI carried in the request message;

After replacing the first S-NSSAI with the second S-NSSAI, including:

Based on the second S-NSSAI, a PDU Session is established.
The method for terminal cross-area communication according to claim 7, wherein after the PDU Session is established based on the second S-NSSAI, the method comprises:

According to the second S-NSSAI, selecting an SMF;

sending a PDU session establishment request message to the SMF;

When receiving the PDU session establishment accept message fed back by the SMF, a PDU session request message including the PDU session establishment accept message is sent to the RAN to establish a PDU session.
A network element device comprising a processor, a memory, a computer program stored on the memory and executable by the processor, and a computer program for realizing the connection between the processor and the memory A communication data bus, wherein the computer program, when executed by the processor, implements the steps of the terminal cross-region communication method according to any one of claims 1 to 8.
A storage medium for computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize any one of claims 1 to 8 The steps of a method for a terminal cross-region communication.