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

Abstract

The embodiment of the present invention provides a terminal cross-region communication method, network element device and storage medium, which belong to the field of communication. The method includes: 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 second S-NSSAI mapped by the first S-NSSAI in the first NSSAI; replacing the first S-NSSAI with the second S-NSSAI to realize cross-region communication of the terminal based on the second S-NSSAI. The technical solution of the embodiment of the present invention realizes that when the terminal does not roam across PLMNs in different areas, network slices are available, thereby ensuring the normal execution of user services.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a terminal cross-region communication method, network element equipment and storage medium. Background Art

[0002] 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 is logically isolated from the wireless access network bearer network to the core network to adapt to various types of applications. Each network slice has a unique S-NSSAI (Single Network Slice Selection Assistance Information) identifier, and the network slice can be correctly selected based on the S-NSSAI identifier.

[0003] User terminals can roam across PLMNs (Public Land Mobile Networks) or in different regions without roaming across PLMNs, such as in different provinces. Network slicing supports roaming across PLMNs. For roaming in different regions without roaming across PLMNs, since operators have planned different non-standard S-NSSAIs for the same service in different regions (such as different provinces), network slicing cannot continue to be used, which in turn makes it impossible to guarantee the execution of user services. Summary of the invention

[0004] The main purpose of the embodiments of the present invention is to provide a terminal cross-regional communication method, network element equipment and storage medium, aiming to enable network slicing to be available when the terminal roams in different areas without crossing PLMNs, thereby ensuring the normal execution of user services.

[0005] In a first aspect, an embodiment of the present invention provides a terminal cross-region communication method, including:

[0006] When a first S-NSSAI currently corresponding to the terminal does not belong to a first NSSAI currently allowed to be available by the terminal, determining a second S-NSSAI mapped by the first S-NSSAI in the first NSSAI;

[0007] The first S-NSSAI is replaced with the second S-NSSAI to implement cross-region communication of the terminal based on the second S-NSSAI.

[0008] In a second aspect, an embodiment of the present invention further provides a network element device, comprising a processor, a memory, a computer program stored on the memory and executable by the processor, and a data bus for realizing connection communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of any terminal cross-region communication method provided in the specification of the present invention are realized.

[0009] In a third aspect, an embodiment of the present invention further provides a storage medium for computer-readable storage, characterized in that 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 steps of any terminal cross-region communication method provided in the specification of the present invention.

[0010] An embodiment of the present invention provides a terminal cross-region communication method, a network element device and a storage medium. In the embodiment of the present invention, when the terminal does not roam across PLMNs or across regions, and the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal, the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI is determined, and the first S-NSSAI is replaced with the second S-NSSAI, so that the terminal currently has a network slice corresponding to the second S-NSSAI available, that is, cross-region communication of the terminal is realized, and normal execution of the service is ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 This is a structural diagram of the 5G network architecture;

[0013] Figure 2 A schematic diagram of a flow chart of a terminal cross-region communication method provided by an embodiment of the present invention;

[0014] Figure 3 A schematic diagram of a flow chart of another terminal cross-region communication method provided by an embodiment of the present invention;

[0015] Figure 4 A schematic diagram of a process for determining a second NSSAI currently available as a candidate for the terminal according to an embodiment of the present invention;

[0016] Figure 5 A schematic diagram of a flow chart of another terminal cross-region communication method provided by an embodiment of the present invention;

[0017] Figure 6 A flowchart of a registration process without a PDU Session provided by an embodiment of the present invention;

[0018] Figure 7 A schematic diagram of a flow chart of another terminal cross-region communication method provided by an embodiment of the present invention;

[0019] Figure 8 A flowchart of a registration process with a PDU Session provided by an embodiment of the present invention;

[0020] Fig. 9 A schematic diagram of a flow chart of another terminal cross-region communication method provided by an embodiment of the present invention;

[0021] Fig.10 A flowchart of establishing a PDU session provided by an embodiment of the present invention;

[0022] Fig.11 A schematic block diagram of the structure of a network element device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0024] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.

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

[0026] The embodiment of the present invention provides a terminal cross-region communication method, a network element device and a storage medium. The terminal cross-region communication method can be applied to a network element device, which can be a network element function entity NF such as AMF (Access and Mobility Management function) and NSSF (Network Slice Selection Function) in a 5G network architecture.

[0027] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the 5G network architecture. The 5G network architecture includes:

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

[0029] RAN (Radio Access Network) is responsible for air interface resource scheduling and air interface connection management for terminals to access the network.

[0030] AMF (Access and Mobility Management function), a core network control plane entity, is mainly responsible for user mobility management, including: registration and temporary identity allocation; maintenance of idle (IDLE) and connected (CONNECT) states and state migration; switching in the connected state; triggering paging in the user idle state, etc.

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

[0032] UDM (Unified Data Management), a core network control plane entity, belongs to the user server and permanently stores user contract data.

[0033] SMF (Session Management function), a core network control plane entity, is mainly responsible for maintaining PDU (Protocol Data Unit) Session, allocating user IP addresses, and has QoS (Quality of Service) control and billing functions; it caches downlink data packets received when the user is idle and notifies AMF to page the user, etc.

[0034] UPF (User plane function) is a user plane functional entity in the core network. It is responsible for forwarding user data packets and also collects statistics on user data packets for billing and other functions.

[0035] PCF (Policy Control Functionality), a core network control plane entity, is 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 selection policies, QoS rules for user data transmission, and charging rules based on service information, user contract information, and operator configuration information.

[0036] NEF (Network Exposure Function), a core network control plane entity, is responsible for exposing mobile network capabilities to the outside world.

[0037] NRF (NF Repository Function), a core network control plane entity, is responsible for the dynamic registration of service capabilities of network functions and network function discovery.

[0038] NSSF (Network Slice Selection Function), a core network control plane entity, is responsible for selecting the target NSI (Network Slice Instance).

[0039] AF (Application Function), an application entity, is responsible for providing specific services to users.

[0040] Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0041] Please refer to Figure 2 , Figure 2 A schematic diagram of a flow chart of a terminal cross-region communication method provided in an embodiment of the present invention.

[0042] like Figure 2 As shown, the terminal cross-region communication method includes step S101 and step S102.

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

[0044] It should be noted that the terminal includes but is not limited to mobile phones, tablet computers, wearable devices and other electronic devices with communication functions. During the use of the terminal, for example, when performing initial registration or registration update, the NSSAI (Network Slice Selection Assistance Information) currently allowed by the terminal is obtained, and the S-NSSAI (Single Network Slice Selection Assistance Information) currently corresponding to the terminal is detected to determine whether it 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 ease of description, the NSSAI currently allowed 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, detect 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; conversely, if the first S-NSSAI is not the S-NSSAI in the first NSSAI, the first S-NSSAI is not available in the currently accessed AMF or area.

[0045] If the first S-NSSAI is the S-NSSAI in the first NSSAI, communication processes such as terminal registration and session establishment can be implemented based on the first S-NSSAI.

[0046] If the first S-NSSAI is not the S-NSSAI in the first NSSAI, for example, when the terminal does not roam across PLMN (Public Land Mobile Network) regions, such as roaming across different provinces, the first S-NSSAI currently corresponding to the terminal is not available 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, determine the S-NSSAI mapped by the first S-NSSAI in the first NSSAI. For ease of description, the S-NSSAI mapped by the first S-NSSAI in the first NSSAI is referred to as the second S-NSSAI below. That is, the first S-NSSAI is mapped to the second S-NSSAI available in the current access area.

[0047] Step S102: Replace the first S-NSSAI with the second S-NSSAI to implement cross-region communication of the terminal based on the second S-NSSAI.

[0048] After obtaining 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 to implement communication processes such as terminal cross-region registration and session establishment based on the second S-NSSAI.

[0049] In one embodiment, referring to Figure 3 , before step S101 include: step S103 and step S104.

[0050] Step S103: Determine a second NSSAI that is currently a candidate for availability to the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal.

[0051] Get the requested NSSAI (Requested NSSAI) and the subscribed NSSAI (Subscribed NSSAI) corresponding to the terminal. Exemplarily, the terminal initiates the initial registration process, or the terminal initiates the registration update process. The message carries the requested NSSAI and other information corresponding to the terminal. Extract the requested NSSAI carried in the message. Exemplarily, obtain the subscribed NSSAI corresponding to the terminal locally from the AMF; or obtain the subscribed NSSAI corresponding to the terminal from the UDM. The UDM permanently stores user subscription data, including the subscribed NSSAI.

[0052] In one embodiment, referring to Figure 4 , step S103 includes: sub-step S1031 and sub-step S1032.

[0053] Sub-step S1031: determine the intersection S-NSSAI of the contracted NSSAI and the requested NSSAI.

[0054] After obtaining the contracted NSSAI and requested NSSAI corresponding to the terminal, the contracted NSSAI is compared with the requested NSSAI to determine the intersection S-NSSAI of the contracted NSSAI and the requested NSSAI, that is, the same S-NSSAI in the contracted NSSAI and the requested NSSAI.

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

[0056] According to the intersection S-NSSAI of the contracted NSSAI and the requested NSSAI, that is, based on the same S-NSSAI in the contracted NSSAI and the requested NSSAI, the NSSAI (Allowed NSSAI1) available for the current candidate of the terminal is generated. For the convenience of description, the NSSAI available for the current candidate of the terminal is referred to as the second NSSAI below. The second NSSAI is composed of the same S-NSSAI in the contracted NSSAI and the requested NSSAI.

[0057] Step S104: If there is an S-NSSAI in the second NSSAI that is currently unavailable to the terminal, map the unavailable S-NSSAI to an S-NSSAI that is currently available to the terminal, and generate the first NSSAI mapped by the second NSSAI.

[0058] Based on the determined second NSSAI, if there is S-NSSAI in the second NSSAI that is unavailable in the AMF or area currently accessed by the terminal, for example, part or all of the S-NSSAI in the second NSSAI is unavailable in the AMF or area currently accessed by the terminal, at this time, based on the PLMN accessed by the terminal, the area currently accessed by the terminal, and the second NSSAI, part or all of the S-NSSAI in the second NSSAI that is unavailable in the AMF or area currently accessed is mapped to an equivalent S-NSSAI available in the AMF or area currently accessed by the terminal, and the S-NSSAI in the second NSSAI that is unavailable in the AMF or area currently accessed is replaced based on the mapped equivalent S-NSSAI available in the AMF or area currently accessed by the terminal to generate the first NSSAI (Allowed NSSAI2) mapped by the second NSSAI.

[0059] In one embodiment, step S104 may include: saving the first NSSAI, the second NSSAI, and a mapping relationship between the first NSSAI and the second NSSAI.

[0060] Exemplarily, AMF saves 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 NSSF, after NSSF generates the first NSSAI mapped to the second NSSAI, it feeds back a network slice information acquisition response message to AMF, which carries the first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI, and AMF saves the first NSSAI, the second NSSAI, and the mapping relationship between the first NSSAI and the second NSSAI.

[0061] In one embodiment, referring to Figure 5 , before step S103, including: step S105 and step S106.

[0062] Step S105: receiving an initial registration message sent by the terminal, or receiving a first registration update message sent by the terminal when the PDUSession is not activated.

[0063] 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, the initial registration message sent by the terminal is received, or the registration update message sent when the terminal does not activate the PDUSession is received. For the sake of 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 below. Among them, the initial registration message and the first registration update message carry information such as the requested NSSAI corresponding to the terminal.

[0064] Step S106: Obtain the requested NSSAI carried in the initial registration message or the first registration update message, and obtain the subscribed NSSAI from the local or UDM.

[0065] Upon receiving the initial registration message or the first registration update message, the requested NSSAI corresponding to the terminal carried in the initial registration message or the first registration update message is obtained. Furthermore, based on the received initial registration message or the first registration update message, the registration process is processed to obtain the contracted NSSAI corresponding to the terminal locally; or, the contracted NSSAI corresponding to the terminal is obtained from the UDM.

[0066] Afterwards, 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, the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI is determined, and the first S-NSSAI is replaced with the second S-NSSAI. The specific operation process is as described in the above embodiments and will not be repeated here.

[0067] After step S102, step S107 is included.

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

[0069] After the first S-NSSAI is replaced with the second S-NSSAI, the registration process is continued, and then a registration acceptance message is sent to the terminal, wherein the registration acceptance message carries the second NSSAI. The terminal implements normal cross-region communication based on the second NSSAI.

[0070] Reference Figure 6 , Figure 6 This is a flowchart of the registration process when there is no PDU Session. The specific process is as follows:

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

[0072] A2): AMF handles the registration process, and AMF obtains the Subscribed NSSAI locally, or AMF obtains the Subscribed NSSAI and other information from UDM.

[0073] A3): AMF sends a network slice information request message to NSSF, which carries information such as requested NSSAI, subscribed NSSAI, Serving PLMN (i.e. the PLMN currently accessed by the UE), and the currently accessed area.

[0074] A4): NSSF obtains the intersection of the requested NSSAI and the contracted NSSAI to determine the second NSSAI (Allowed NSSAI1).

[0075] A5): NSSF finds that part or all of the S-NSSAI in the second NSSAI is not available in the currently accessed AMF or area. Based on the currently accessed PLMN, the currently accessed area, and the second NSSAI, NSSF maps part or all of the S-NSSAI in the second NSSAI that is not available in the currently accessed AMF or area to an equivalent S-NSSAI that is available in the AMF or area currently accessed by the UE according to local policy, and uses the mapped S-NSSAI to replace part or all of the S-NSSAI in the second NSSAI that is not available in the currently accessed AMF or area to form the first NSSAI (Allowed NSSAI2). NSSF determines whether redirection is required based on the first NSSAI and other information.

[0076] A6): NSSF returns a network slice information acquisition response message to AMF, which carries information such as the first NSSAI, the second NSSAI and their mapping relationship.

[0077] A7): AMF saves the first NSSAI, the second NSSAI and their mapping relationship.

[0078] A8): In addition to interacting with the UE, the AMF uses the first NSSAI as the currently allowed NSSAI of the UE, for example, to determine whether redirection is required based on the first NSSAI.

[0079] A9): The AMF continues to process the registration process.

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

[0081] In one embodiment, referring to Figure 7 , before step S103, including: step S108 and step S109.

[0082] Step S108: Receive a second registration update message sent by the terminal when the PDU Session has been activated.

[0083] When the terminal is registered and the PDU Session is activated, when the terminal initiates the registration update process, the registration update message sent by the terminal is received. For the 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. The second registration update message carries information such as the requested NSSAI corresponding to the terminal.

[0084] Step S109: Obtain the requested NSSAI carried in the second registration update message, and obtain the subscribed NSSAI from the local or UDM.

[0085] When receiving the second registration update message, the request NSSAI corresponding to the terminal carried in the second registration update message is obtained. And based on the received second registration update message, the registration process is processed to obtain the contract NSSAI corresponding to the terminal from the local; or, the contract NSSAI corresponding to the terminal is obtained from the UDM.

[0086] Afterwards, 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, the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI is determined, and the first S-NSSAI is replaced with the second S-NSSAI. The specific operation process is as described in the above embodiments and will not be repeated here.

[0087] After step S102, step S110 is included.

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

[0089] After the first S-NSSAI is replaced with the second S-NSSAI, the S-NSSAI of the activated PDU Session is updated to the second S-NSSAI, that is, the second S-NSSAI is subsequently used as the S-NSSAI of the activated PDU Session.

[0090] Afterwards, the registration process is continued, and then a registration acceptance message is sent to the terminal, wherein the registration acceptance message carries the second NSSAI. The terminal implements normal cross-region communication based on the second NSSAI.

[0091] Reference Figure 8 , Figure 8 This is a flowchart of the registration process when there is a PDU Session. The specific process is as follows:

[0092] B1): The UE has registered and activated the PDU Session. The UE initiates the registration update process, and the message carries information such as requested NSSAI.

[0093] B2): AMF handles the registration process, AMF obtains the Subscribed NSSAI locally, or AMF obtains the Subscribed NSSAI and other information from UDM.

[0094] B3): AMF sends a network slice information request message to NSSF, which carries information such as requested NSSAI, subscribed NSSAI, Serving PLMN (i.e. the PLMN currently accessed by the UE), and the currently accessed area.

[0095] B4): NSSF obtains the intersection of the requested NSSAI and the contracted NSSAI to determine the second NSSAI (Allowed NSSAI1).

[0096] B5): NSSF finds that part or all of the S-NSSAI in the second NSSAI is not available in the currently accessed AMF or area. Based on the currently accessed PLMN, the currently accessed area, and the second NSSAI, NSSF maps part or all of the S-NSSAI in the second NSSAI that is not available in the currently accessed AMF or area to an equivalent S-NSSAI that is available in the AMF or area currently accessed by the UE according to local policy, and uses the mapped S-NSSAI to replace part or all of the S-NSSAI in the second NSSAI that is not available in the currently accessed AMF or area to form the first NSSAI (Allowed NSSAI2). NSSF determines whether redirection is required based on the first NSSAI and other information.

[0097] B6): NSSF returns a network slice information acquisition response message to AMF, which carries information such as the first NSSAI, the second NSSAI and their mapping relationship.

[0098] B7): AMF saves the first NSSAI, the second NSSAI and their mapping relationship.

[0099] B8): In addition to interacting with the UE, the AMF uses the first NSSAI as the currently allowed NSSAI of the UE, for example, to determine whether redirection is required based on the first NSSAI.

[0100] B9): AMF determines that the first S-NSSAI corresponding to the activated PDU Session is not in the first NSSAI (AllowedNSSAI2).

[0101] B10): AMF replaces the first S-NSSAI of the PDU Session with the second S-NSSAI corresponding to the first NSSAI.

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

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

[0104] B13): SMF subsequently uses the second S-NSSAI as the S-NSSAI of the PDU Session to update other network element function entities NF.

[0105] B14): The AMF continues to process the registration process.

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

[0107] In one embodiment, referring to Fig. 9 , before step S101, including: step S111 and step S112.

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

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

[0110] 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 acquired.

[0111] If the first S-NSSAI is not the NSSAI in the first NSSAI, the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI is determined, and the first S-NSSAI is replaced with the second S-NSSAI. The specific operation process is as described in the above embodiments and will not be repeated here.

[0112] After step S102, step S113 is included.

[0113] Step S113: Establish a PDU Session based on the second S-NSSAI.

[0114] After the first S-NSSAI is replaced with the second S-NSSAI, the second S-NSSAI is used as the request S-NSSAI carried by the terminal to establish a PDU Session.

[0115] In one embodiment, after the PDU Session is established based on the second S-NSSAI, the 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 message carries information such as the first S-NSSAI and the second S-NSSAI. The SMF feeds back a PDU session establishment acceptance message based on the first S-NSSAI, wherein the PDU session establishment acceptance message carries the first S-NSSAI. Upon receiving the PDU session establishment acceptance message fed back by the SMF, a PDU session request message including the PDU session establishment acceptance message is sent to the RAN to establish the PDU session.

[0116] Reference Fig.10 , Fig.10 The flowchart for establishing a PDU session is as follows:

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

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

[0119] C3): AMF replaces the first S-NSSAI with the second S-NSSAI corresponding to the first NSSAI.

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

[0121] C5): AMF selects SMF based on the second S-NSSAI, DNN (Data Network Name) and other information.

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

[0123] C7): SMF obtains the subscription data from UDM and uses the first S-NSSAI to match the Subscribed NSSAI in the subscription data.

[0124] C8): SMF returns a PDU session establishment response message to AMF.

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

[0126] C10): SMF selects UPF based on the second S-NSSAI and other information, and completes session creation to UPF, such as N4 PDU session creation.

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

[0128] C12): SMF sends an N1N2 message transfer message to AMF, carrying an N2 PDU session request message and a PDU session establishment acceptance message.

[0129] C13): AMF sends a PDU session request message to RAN, such as an N2 PDU session request message, which includes a PDU session establishment accept message.

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

[0131] The terminal cross-region communication method provided in the above embodiment, when the terminal does not roam across PLMNs or across regions, and the first S-NSSAI currently corresponding to the terminal does not belong to the first NSSAI currently allowed to be available by the terminal, determines the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI, and replaces the first S-NSSAI with the second S-NSSAI, so that the terminal currently has a network slice corresponding to the second S-NSSAI available, that is, cross-region communication of the terminal is realized, ensuring normal execution of the service.

[0132] See also Fig.11 , Fig.11 A schematic block diagram of the structure of a network element device provided in an embodiment of the present invention.

[0133] like Fig.11 As shown, the network element device 300 includes a processor 301 and a memory 302, and the processor 301 and the memory 302 are connected via a bus 303, such as an I2C (Inter-integrated Circuit) bus.

[0134] Specifically, the processor 301 is used to provide computing and control capabilities to support the operation of the entire network element device. The processor 301 can be a central processing unit (CPU), and the processor 301 can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0135] Specifically, the memory 302 may be a Flash chip, a read-only memory (ROM) disk, an optical disk, a USB flash drive, or a mobile hard disk.

[0136] Those skilled in the art will understand that Fig.11 The structure shown in the figure is only a block diagram of a partial structure related to the embodiment of the present invention, and does not constitute a limitation on the network element device to which the embodiment of the present invention is applied. The specific server may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0137] The processor is used to run a computer program stored in the memory, and implement any one of the terminal cross-region communication methods provided by the embodiments of the present invention when executing the computer program.

[0138] In one embodiment, the processor is used to run a computer program stored in the memory, and implements the following steps when executing the computer program:

[0139] When a first S-NSSAI currently corresponding to the terminal does not belong to a first NSSAI currently allowed to be available by the terminal, determining a second S-NSSAI mapped by the first S-NSSAI in the first NSSAI;

[0140] The first S-NSSAI is replaced with the second S-NSSAI to implement cross-region communication of the terminal based on the second S-NSSAI.

[0141] In one embodiment, 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, the processor is used to implement before determining the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI:

[0142] Determine, according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, a second NSSAI that is currently a candidate for availability of the terminal;

[0143] If there is an S-NSSAI in the second NSSAI that is currently unavailable to the terminal, the unavailable S-NSSAI is mapped to an S-NSSAI that is currently available to the terminal, and the first NSSAI mapped to the second NSSAI is generated.

[0144] In one embodiment, when the processor implements determining the second NSSAI that is currently available as a candidate for the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, it is configured to implement:

[0145] Determine an intersection S-NSSAI of the contracted NSSAI and the requested NSSAI;

[0146] The second NSSAI is determined according to the intersection S-NSSAI.

[0147] In one embodiment, after implementing the generating of the first NSSAI mapped to the second NSSAI, the processor is configured to implement:

[0148] The first NSSAI, the second NSSAI, and a mapping relationship between the first NSSAI and the second NSSAI are saved.

[0149] In one embodiment, before implementing the step of determining the second NSSAI that is currently a candidate for availability of the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, the processor is configured to implement:

[0150] Receiving an initial registration message sent by the terminal, or receiving a first registration update message sent by the terminal when the PDU Session is not activated;

[0151] Obtain the requested NSSAI carried in the initial registration message or the first registration update message, and obtain the subscribed NSSAI from a local or UDM;

[0152] After implementing the replacing of the first S-NSSAI with the second S-NSSAI, the processor is configured to implement:

[0153] Send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI.

[0154] In one embodiment, before implementing the step of determining the second NSSAI that is currently available as a candidate for the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, the processor is configured to implement:

[0155] Receiving a second registration update message sent by the terminal when the PDU Session has been activated;

[0156] Obtain the requested NSSAI carried in the second registration update message, and obtain the subscribed NSSAI from a local or UDM;

[0157] After implementing the replacing of the first S-NSSAI with the second S-NSSAI, the processor is configured to implement:

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

[0159] In one embodiment, 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, the processor determines that before the second S-NSSAI mapped by the first S-NSSAI in the first NSSAI is implemented:

[0160] Receiving a PDU Session establishment request message sent by the terminal;

[0161] Obtaining the first S-NSSAI carried in the request message;

[0162] After implementing the replacing of the first S-NSSAI with the second S-NSSAI, the processor is configured to implement:

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

[0164] In one embodiment, after implementing the establishment of the PDU Session based on the second S-NSSAI, the processor is configured to implement:

[0165] According to the second S-NSSAI, select SMF;

[0166] Send a PDU session establishment request message to the SMF;

[0167] When the PDU session establishment acceptance message fed back by the SMF is received, a PDU session request message including the PDU session establishment acceptance message is sent to the RAN to establish the PDU session.

[0168] It should be noted that technical personnel in the relevant field can clearly understand that for the convenience and conciseness of description, the specific working process of the network element device described above can refer to the corresponding process in the aforementioned terminal cross-region communication method embodiment, and will not be repeated here.

[0169] An embodiment of the present invention also provides a storage medium for computer-readable storage, wherein 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 steps of any terminal cross-region communication method provided in the description of the embodiment of the present invention.

[0170] The storage medium may be an internal storage unit of the network element device described in the foregoing embodiment, such as a hard disk or 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, a smart media card (SMC), a secure digital (SD) card, a flash card, etc., equipped on the network element device.

[0171] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In a hardware embodiment, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are 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 tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain 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 may include any information delivery media.

[0172] It should be understood that the term "and / or" used in the present specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system including the element.

[0173] The serial numbers of the embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A terminal cross-region communication method, characterized in that: include: When a first S-NSSAI currently corresponding to the terminal does not belong to a first NSSAI currently allowed to be available by the terminal, determining a second S-NSSAI mapped by the first S-NSSAI in the first NSSAI; replacing the first S-NSSAI with the second S-NSSAI, so as to implement cross-region communication of the terminal based on the second S-NSSAI; Before determining a second S-NSSAI mapped by the first S-NSSAI in the first NSSAI, the method includes: Determine an intersection S-NSSAI of a subscribed NSSAI of the terminal and a requested NSSAI of the terminal, and determine a second NSSAI that is currently a candidate for the terminal according to the intersection S-NSSAI; If there is an S-NSSAI in the second NSSAI that is currently unavailable to the terminal, the unavailable S-NSSAI is mapped to an S-NSSAI that is currently available to the terminal, and the first NSSAI mapped to the second NSSAI is generated.

2. The terminal cross-region communication method according to claim 1, characterized in that: After generating the first NSSAI mapped to the second NSSAI, the method further comprises: The first NSSAI, the second NSSAI, and a mapping relationship between the first NSSAI and the second NSSAI are saved.

3. The terminal inter-regional communication method according to claim 1 or 2, characterized in that: Before determining the second NSSAI that is currently available as a candidate for the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, the method includes: Receiving an initial registration message sent by the terminal, or receiving a first registration update message sent by the terminal when the PDU Session is not activated; Obtain the requested NSSAI carried in the initial registration message or the first registration update message, and obtain the subscribed NSSAI from a local or UDM; After the replacing the first S-NSSAI with the second S-NSSAI, the method further comprises: Send a registration acceptance message to the terminal, where the registration acceptance message carries the second NSSAI.

4. The terminal cross-region communication method according to claim 1 or 2, characterized in that: Before determining the second NSSAI that is currently available as a candidate for the terminal according to the subscribed NSSAI of the terminal and the requested NSSAI of the terminal, the method includes: Receiving a second registration update message sent by the terminal when the PDU Session has been activated; Obtain the requested NSSAI carried in the second registration update message, and obtain the subscribed NSSAI from a local or UDM; After the replacing the first S-NSSAI with the second S-NSSAI, the method further comprises: Update the S-NSSAI corresponding to the activated PDU Session to the second S-NSSAI.

5. The terminal cross-region communication method according to claim 1, characterized in that: 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 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 the replacing the first S-NSSAI with the second S-NSSAI, the method further comprises: Based on the second S-NSSAI, a PDU Session is established.

6. The terminal cross-region communication method according to claim 5, characterized in that: After the PDU Session is established based on the second S-NSSAI, the method includes: According to the second S-NSSAI, select SMF; Send a PDU session establishment request message to the SMF; When the PDU session establishment acceptance message fed back by the SMF is received, a PDU session request message including the PDU session establishment acceptance message is sent to the RAN to establish the PDU session.

7. A network element device, characterized in that: 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 communication between the processor and the memory, wherein when the computer program is executed by the processor, the steps of the terminal cross-area communication method as described in any one of claims 1 to 6 are realized.

8. A storage medium for computer-readable storage, characterized in that: 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 steps of the method for inter-regional communication of a terminal according to any one of claims 1 to 6.

Images