Methods, apparatus, equipment and storage media for accessing independent, non-public networks

Abstract

This application provides a method, apparatus, device, and storage medium for accessing an independent non-public network. The method is applied to an Access and Mobility Management Function (AMF) network element and includes: receiving an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network (SNPN) required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of SNPNs subscribed to by the user terminal; and establishing a connection between the user terminal and the SNPN corresponding to the network information in the access request based on the access request. This method enables on-demand access to SNPNs, improves service quality, increases network selection efficiency, and solves the problem of how user terminals access equivalent SNPNs.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device and storage medium for accessing an independent non-public network. Background Technology

[0002] A Stand-alone Non-Public Network (SNPN) is a dedicated network based on the 5G system architecture. Unlike a Public Land Mobile Network (PLMN), an SNPN can provide dedicated services for specific scenarios to enhance user and data security.

[0003] The concept of an equivalent SNPN is inherited from that of an equivalent PLMN, referring to multiple SNPNs of equal status, all of which allow user equipment (UE) to register and conduct services. However, the latest 3rd Generation Partnership Project (3GPP) specifications do not define how user terminals access equivalent SNPNs, meaning the usage of equivalent SNPNs is unclear.

[0004] Therefore, there is an urgent need for a method for user terminals to access an equivalent SNPN. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for accessing an independent, non-public network, to solve the problem of how user terminals can access an independent, non-public network.

[0006] On one hand, this application provides a method for accessing an independent non-public network, the method being applied to an Access and Mobility Management Function (AMF) network element, the method comprising:

[0007] The system receives an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network (SNPN) required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of SNPNs subscribed to by the user terminal;

[0008] Based on the access request, a connection is established between the user terminal and the SNPN corresponding to the network information in the access request.

[0009] Optionally, the equivalent SNPN list is pre-stored in the AMF network element; the method further includes:

[0010] In response to the registration request from the user terminal, the equivalent SNPN list pre-stored in the AMF network element is sent to the user terminal.

[0011] Optionally, the method further includes:

[0012] In response to the registration request from the user terminal, the equivalent SNPN list is obtained from the Unified Data Management (UDM) network element; and the equivalent SNPN list is sent to the user terminal.

[0013] Optionally, obtaining the equivalent SNPN list from the UDM network element includes:

[0014] Send an acquisition request to the UDM network element, wherein the acquisition request is used to indicate the acquisition of the user terminal's subscription information;

[0015] The system receives subscription information returned by the UDM network element, the subscription information including network information of the SNPN signed with the user terminal, and generates the equivalent SNPN list based on the subscription information.

[0016] Optionally, the subscription information further includes Single Network Slice Selection Assist Information (S-NSSAI) subscribed to by the user terminal, and mapping information, wherein the mapping information is a mapping relationship between S-NSSAI and SNPN network information; generating the equivalent SNPN list based on the subscription information includes:

[0017] Parse the mapping information to determine the network information of the SNPN corresponding to S-NSSAI;

[0018] The equivalent SNPN list is generated based on the S-NSSAI contracted with the user terminal and the network information of the SNPN corresponding to the S-NSSAI.

[0019] Optionally, the method further includes:

[0020] In response to the registration request of the user terminal, the generated equivalent SNPN list is sent to the user terminal; wherein, the generated equivalent SNPN list is generated by the AMF network element based on the user terminal's subscription information sent after confirmation by the UDM network element; the user terminal's subscription information is sent to the UDM network element by the Network Capability Opening Function (NEF) network element when the Application Function (AF) network element determines that the user terminal's subscription information has changed.

[0021] Optionally, the equivalent SNPN list also includes an S-NSSAI that is subscribed to by the user terminal, and there is a mapping relationship between the network information of the S-NSSAI and the SNPN in the equivalent SNPN list.

[0022] Optionally, the access request may also include S-NSSAI corresponding to the network information of the SNPN required by the user terminal.

[0023] On the other hand, this application provides an apparatus for accessing an independent, non-public network, comprising:

[0024] A receiving unit is configured to receive an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network (SNPN) required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of SNPNs subscribed to by the user terminal;

[0025] The control unit is used to establish a connection between the user terminal and the SNPN corresponding to the network information in the access request, based on the access request.

[0026] Optionally, the equivalent SNPN list is pre-stored in the AMF network element, and the device further includes a configuration unit, which includes a first configuration module;

[0027] The first configuration module is used to respond to the registration request of the user terminal by sending the equivalent SNPN list pre-stored in the AMF network element to the user terminal.

[0028] Optionally, the configuration unit includes a second configuration module;

[0029] The second configuration module is used to respond to the registration request of the user terminal, obtain the equivalent SNPN list from the Unified Data Management (UDM) network element, and send the equivalent SNPN list to the user terminal.

[0030] Optionally, the second configuration module includes an acquisition module;

[0031] The acquisition module is configured to send an acquisition request to the UDM network element, wherein the acquisition request is used to instruct the acquisition of the user terminal's subscription information; and to receive subscription information returned by the UDM network element, wherein the subscription information includes network information of the SNPN subscribed with the user terminal, and to generate the equivalent SNPN list based on the subscription information.

[0032] Optionally, the subscription information also includes Single Network Slice Selection Assist Information (S-NSSAI) subscribed to by the user terminal, and mapping information, wherein the mapping information is a mapping relationship between S-NSSAI and SNPN network information; the acquisition module includes a generation module;

[0033] The generation module is used to parse the mapping information to determine the network information of the SNPN corresponding to S-NSSAI; and to generate the equivalent SNPN list based on the S-NSSAI subscribed to by the user terminal and the network information of the SNPN corresponding to S-NSSAI.

[0034] Optionally, the configuration unit includes a third configuration module;

[0035] The third configuration module is used to respond to the registration request of the user terminal by sending the generated equivalent SNPN list to the user terminal; wherein the generated equivalent SNPN list is generated by the AMF network element based on the user terminal's subscription information sent after confirmation by the UDM network element; the user terminal's subscription information is sent to the UDM network element by the Network Capability Opening Function (NEF) network element when the Application Function (AF) network element determines that the user terminal's subscription information has changed.

[0036] Optionally, the equivalent SNPN list also includes an S-NSSAI that is subscribed to by the user terminal, and there is a mapping relationship between the network information of the S-NSSAI and the SNPN in the equivalent SNPN list.

[0037] Optionally, the access request may also include S-NSSAI corresponding to the network information of the SNPN required by the user terminal.

[0038] On the other hand, this application also provides an access device, the access device comprising: a processor, and a memory communicatively connected to the processor;

[0039] The memory stores computer-executed instructions;

[0040] The processor executes computer execution instructions stored in the memory to implement the method as described in any of the preceding claims.

[0041] On the other hand, this application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any of the foregoing claims.

[0042] On the other hand, this application also provides a computer program product, including a computer program that, when executed by a processor, is used to implement the method as described in any of the foregoing.

[0043] This application provides a method, apparatus, device, and storage medium for accessing independent non-public networks. The method is applied to an AMF (Advanced Network Provider) network element. It receives an access request from a user terminal, wherein the access request includes network information of the independent non-public network SNPN required by the user terminal. The network information in the access request is one or more from an equivalent SNPN list. The equivalent SNPN list is pre-configured by the AMF network element for the user terminal and includes network information of SNPNs subscribed to by the user terminal. Based on the access request, a connection can be established between the user terminal and the SNPN corresponding to the network information in the access request. Because the access request includes the network information of the SNPN required by the user terminal, and the AMF network element connects to the SNPN according to the user terminal's needs, on-demand access is achieved, improving service quality and network selection efficiency, and solving the problem of how user terminals access equivalent SNPNs. Attached Figure Description

[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0045] Figure 1 A flowchart illustrating a method for accessing an independent, non-public network, provided as an embodiment of this application;

[0046] Figure 2 A signaling flowchart between a UE and an AMF network element is provided as an embodiment of this application;

[0047] Figure 3 This application provides a signaling flowchart for a UE accessing an SNPN.

[0048] Figure 4 This application provides another signaling flowchart for UE accessing SNPN.

[0049] Figure 5 A signaling flowchart for UE parameter updating is provided in an embodiment of this application;

[0050] Figure 6 This application provides another signaling flowchart for UE accessing SNPN.

[0051] Figure 7 A schematic diagram of the structure of a device for accessing an independent, non-public network provided in an embodiment of this application;

[0052] Figure 8 A schematic diagram of the structure of another device for accessing an independent, non-public network provided in an embodiment of this application;

[0053] Figure 9 This is a schematic diagram of the access device provided in an embodiment of this application.

[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0056] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0057] In traditional operator networks, the core network can send a list of equivalent PLMNs containing one or more Public Land Mobile Networks (PLMNs) to the user equipment (UE) during registration. These equivalent PLMNs allow the user equipment to register and conduct business, and the user equipment can choose any of the PLMNs for subsequent use.

[0058] Stand-alone Non-Public Network (SNPN) is a stand-alone non-public network technology introduced by 3GPP in 5G systems. SNPN is completely separate from PLMN. SNPN is mainly used within enterprise, mining, and port campuses to provide dedicated service capabilities for specific scenarios, ensuring network security for users. The concept of equivalent SNPN inherits from that of equivalent PLMN, referring to multiple SNPNs of equal status, all of which are also usable by user terminals. However, the latest 3GPP (R17) specification does not yet explicitly define how user terminals access equivalent SNPNs. That is, a universal method for user terminals to access SNPN is needed to meet the technical requirements of practical applications.

[0059] To address this issue, this application proposes a method for accessing independent, non-public networks. By configuring an equivalent SNPN list for user terminals, when a user terminal requests to use an SNPN, the required SNPN network information is included in the access request, enabling the AMF network element to establish a connection between the user terminal and the SNPN. This approach fundamentally solves the problem of user terminals accessing equivalent SNPNs, while also ensuring the accuracy and speed of the connection between the user terminal and the SNPN.

[0060] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0061] Figure 1 This is a flowchart illustrating a method for accessing an independent non-public network provided in an embodiment of this application. The method provided in this embodiment is applied to an Access and Mobility Management Function (AMF) network element (hereinafter referred to as: AMF network element). The executing entity in this embodiment can be an AMF network element, or it can be a device or system including an AMF network element for accessing an independent non-public network. The following detailed description uses an AMF network element as the executing entity.

[0062] like Figure 1 As shown, the method for accessing an independent, non-public network provided in this embodiment includes:

[0063] S101. Receive an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network SNPN required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of SNPNs subscribed to by the user terminal.

[0064] For example, the user terminal stores an equivalent SNPN list pre-configured for it by the AMF network element. The equivalent SNPN list includes network information of the SNPNs subscribed to by the user terminal. The network information is used to identify and distinguish different SNPNs, and may be, for example, the ID of the SNPN. This application does not impose any restrictions.

[0065] Furthermore, this application does not restrict how the AMF network element configures the equivalent SNPN list for the user terminal. For example, the AMF network element may pre-configure the equivalent SNPN list, or the AMF may obtain it in advance / in real-time from the UDM network element, or other network elements may send it to the AMF in any feasible signaling interaction, etc. The aim is that the user terminal pre-stores the equivalent SNPN list, and when sending an access request, it can carry the network information of the SNPN required for that service.

[0066] For example, once a user terminal has an equivalent SNPN list configured, at any time during subsequent user terminal registration or service provision—that is, when the user terminal needs to use an SNPN—it can select one or more SNPNs from the equivalent SNPN list to request a connection based on its priority settings, preferences, or network broadcast messages. In a specific service scenario, for a user terminal to establish a connection with an SNPN, it needs to send an access request to the AMF network element. This access request includes the network information of one or more SNPNs required for the current service. The access request received by the AMF network element from the user terminal will also include the network information of one or more SNPNs required for the current service.

[0067] S102. Based on the access request, establish a connection between the user terminal and the SNPN corresponding to the network information in the access request.

[0068] For example, when an AMF network element receives network information of one or more SNPNs sent by a user terminal, it can determine the SNPN corresponding to the network information based on the network information in the access request, and establish a connection between the user terminal and the SNPN so that the user terminal can use the SNPN.

[0069] Since the access request includes the network information of the SNPN required by the user terminal, and the AMF network element connects to the SNPN according to the user terminal's needs, on-demand access is achieved, ensuring the accuracy and speed of the connection between the user terminal and the SNPN, improving service quality, and also improving network selection efficiency.

[0070] For example, Figure 2 This document provides a signaling flowchart between a UE and an AMF network element, as illustrated in an embodiment of this application. Figure 2As shown, the UE sends a request message to the AMF carrying the network information of the SNPN it needs; the AMF receives the request message sent by the UE and performs subsequent operations such as route selection and bearer setup for the UE based on the request message, such as establishing a connection between the UE and the SNPN.

[0071] The method for accessing an SNPN provided in this application is applied to an AMF network element. It receives an access request from a user terminal, wherein the access request includes network information of an independent non-public network SNPN required by the user terminal. This network information in the access request is one or more from an equivalent SNPN list. The equivalent SNPN list is pre-configured by the AMF network element for the user terminal and includes network information of SNPNs subscribed to by the user terminal. Based on the access request, a connection can be established between the user terminal and the SNPN corresponding to the network information in the access request. This access method achieves on-demand access because the access request includes the network information of the SNPN required by the user terminal, and the AMF network element connects to the SNPN according to the user terminal's needs. This improves service quality and network selection efficiency, and solves the problem of how user terminals can access equivalent SNPNs.

[0072] The following section introduces the access equivalent SNPN scheme provided in this application, using the example of how AMF network elements configure equivalent SNPN lists for user terminals.

[0073] In one example, if the equivalent SNPN list is pre-stored in the AMF network element, then pre-configuring the equivalent SNPN list for the user terminal may include: in response to the user terminal's registration request, sending the equivalent SNPN list pre-stored in the AMF network element to the user terminal.

[0074] For example, the equivalent SNPN list pre-stored in the AMF network element can be either pre-configured in the AMF network element or pre-obtained and stored by the AMF network element from the Unified Data Management (UDM) network element. When the AMF network element receives a registration request from a user terminal, it sends the pre-stored equivalent SNPN list to the user terminal in response to the registration request, so that the user terminal can obtain and store the equivalent SNPN list.

[0075] Since the equivalent SNPN list is pre-stored by the AMF network element, when configuring the equivalent SNPN list for the user terminal, the AMF network element can directly respond to the user terminal's registration request and send the equivalent SNPN list directly to the user terminal without needing to obtain it from other network elements in real time, which improves the response speed. Moreover, the overall configuration process is relatively simple and less prone to errors.

[0076] For example, Figure 3 This is a signaling flowchart for a UE accessing an SNPN, provided as an embodiment of this application. Figure 3 As shown, the interaction process includes the following:

[0077] S301, UE performs the registration process.

[0078] The UE registration process will not be detailed here, but can be found in section 4.2.2.2.2 of 3GPP TS 23.502.

[0079] S302, AMF network element responds to the registration process and sends a response message carrying an equivalent SNPN list to the UE.

[0080] The equivalent SNPN list sent by the AMF network element to the UE can be pre-configured or pre-obtained and stored from any signaling interaction.

[0081] S303, UE stores equivalent SNPN list.

[0082] S304. The UE sends an access request to the AMF network element, carrying network information of one or more SNPNs that it needs.

[0083] Based on the network information of the SNPN, the S305 and AMF network elements establish a connection between the UE and the SNPN, and perform subsequent operations such as route selection and bearer establishment for the UE.

[0084] Steps S301 to S303 can be executed only once. After the UE obtains the equivalent SNPN list, steps S304 and S305 are executed every time the SNPN needs to be used.

[0085] In addition, when the information in the equivalent SNPN list changes, the AMF network element will automatically send the updated equivalent SNPN list to the UE to ensure that the UE stores and uses the SNPN in the latest equivalent SNPN list.

[0086] In this example, since the equivalent SNPN list is pre-stored in the AMF network element, the response speed is relatively fast, the overall configuration process is relatively simple, it is not easy to make mistakes, and the overall response efficiency can be improved.

[0087] In one example, pre-configuring an equivalent SNPN list for a user terminal may also include: in response to a registration request from a user terminal, obtaining an equivalent SNPN list from a unified data management UDM network element; and sending the equivalent SNPN list to the user terminal.

[0088] For example, in this example, the equivalent SNPN list is obtained in real time from the UDM network element by the AMF network element when responding to the user terminal's registration request. When the AMF network element receives the user terminal's registration request, it obtains the equivalent SNPN list from the UDM network element and sends it to the user terminal.

[0089] In this configuration, the equivalent SNPN list can be pre-configured and stored in the UDM network element, and the AMF network element obtains the pre-configured equivalent SNPN list from the UDM network element. This configuration method eliminates the need for the AMF network element to generate the equivalent SNPN list, thus reducing the load on the AMF network element.

[0090] In one example, the UDM network element stores the subscription information between the user terminal and the SNPN. Obtaining the equivalent SNPN list from the Unified Data Management UDM network element may include: sending an acquisition request to the UDM network element, wherein the acquisition request is used to indicate the acquisition of the user terminal's subscription information; and receiving the subscription information returned by the UDM network element, wherein the subscription information includes the network information of the SNPN that the user terminal has signed up with, and generating the equivalent SNPN list based on the subscription information.

[0091] For example, after receiving a registration request from a user terminal, the AMF network element sends a request to the UDM network element to obtain the user terminal's subscription information. After receiving the user terminal's subscription information returned by the UDM network element, it generates an equivalent SNPN list based on the network information of the SNPN that has signed up with the user terminal in the subscription information. The equivalent SNPN list includes the network information of the SNPN that has signed up with the user terminal.

[0092] In this example, the UDM network element sends the user terminal's subscription information with the SNPN to the AMF network element, which then generates an equivalent SNPN list based on this information. Since the subscription information sent by the UDM network element is the latest, the resulting equivalent SNPN list is also up-to-date, improving its real-time effectiveness.

[0093] In one example, the subscription information also includes Single Network Slice Selection Auxiliary Information (S-NSSAI) subscribed to by the user terminal, and mapping information, where the mapping information is the mapping relationship between S-NSSAI and SNPN network information; then, an equivalent SNPN list is generated based on the subscription information, including:

[0094] Parse the mapping information to determine the network information of the SNPN corresponding to S-NSSAI; and generate an equivalent SNPN list based on the S-NSSAI subscribed to with the user terminal and the network information of the SNPN corresponding to S-NSSAI.

[0095] For example, if the subscription information of the user terminal returned by the UDM network element also includes the S-NSSAI subscribed to by the user terminal, and the mapping information between the network information of the S-NSSAI and the subscribed SNPN, then when the AMF generates an equivalent SNPN list based on the subscription information, it needs to first parse the mapping information to determine the network information of the SNPN corresponding to the S-NSSAI, and then generate the equivalent SNPN list. The equivalent SNPN list includes the network information of the SNPN subscribed to by the user terminal, as well as the S-NSSAI subscribed to by the user terminal.

[0096] The mapping relationship between S-NSSAI and SNPN network information can be a 1:1 mapping or a 1:n mapping, meaning that one S-NSSAI can correspond to one or more SNPN network information. Furthermore, the number of S-NSSAIs subscribed to by the user terminal can be one or more; this application does not impose any restrictions. A set of one or more S-NSSAIs is called an NSSAI. The 1:1 or 1:n mapping between S-NSSAI and SNPN network information can be performed by the UDM network element, or by the Operation, Management and Maintenance (OAM) network element or other network elements, and then sent to the UDM network element.

[0097] For example, since the encoding of S-NSSAI is defined as 8 bits of SST (mandatory) + 24 bits of SD (optional), and bits 0-127 of SST are reserved standard values, while bits 128-255 are custom values, when binding the SNPN subscribed to by the user terminal with the S-NSSAI subscribed to by the user terminal, that is, establishing a mapping relationship between the two, corresponding values ​​can be designed in bits 128-255 of SST to represent the SNPN subscribed to by the user terminal; or corresponding values ​​can be designed in SD to represent the SNPN subscribed to by the user terminal; or certain values ​​can be set in both to represent the SNPN subscribed to by the user terminal. This application does not impose any restrictions, as long as it is ensured that all SNPN subscribed to by the user terminal are bound to the subscribed S-NSSAI.

[0098] In this example, the subscription information includes not only the SNPN's network information, but also the Single Network Slice Selection Auxiliary Information (S-NSSAI) subscribed to by the user terminal, as well as mapping information. Therefore, the resulting equivalent SNPN list also includes the S-NSSAI subscribed to by the user terminal. This scheme provides more feasible methods for subsequently determining and establishing the connection between the user terminal and the SNPN. In practical applications, one or more of these methods can be selected according to actual needs, improving the overall practicality of the scheme.

[0099] For example, Figure 4 This is another signaling flowchart for UE accessing SNPN provided in an embodiment of this application. Figure 4As shown, the interaction process includes the following:

[0100] The S401 and UDM network elements will perform 1:1 or 1:n mapping of the network information of the S-NSSAI and SNPN signed with the UE, generate mapping information, and store it in the UDM network element.

[0101] S402, The UE sends a registration request message carrying the NSSAI request to the AMF network element.

[0102] S403, the AMF network element sends a request to the UDM network element to obtain the UE's subscription information.

[0103] S404, UDM network element returns UE subscription information to AMF network element, which includes network information of SNPN signed with UE, S-NSSAI signed with UE, and mapping information.

[0104] S405 and AMF network element parsing mapping information are used to determine the network information of the SNPN corresponding to S-NSSAI and generate an equivalent SNPN list.

[0105] S406, the AMF network element sends a response message to the UE that includes an equivalent SNPN list in response to the registration request.

[0106] S407, UE stores equivalent SNPN list.

[0107] S408, the UE sends an access request to the AMF network element, carrying network information of one or more SNPNs that it needs.

[0108] Based on the network information of the SNPN, the S409 and AMF network elements establish a connection between the UE and the SNPN, and perform subsequent operations such as route selection and bearer establishment for the UE.

[0109] Steps S401 to S407 can be executed only once. After the UE obtains the equivalent SNPN list, steps S408 and S409 are executed every time the SNPN needs to be used.

[0110] In the example, if the UDM network element detects a change in the information subscribed to by the UE, the UDM network element will automatically perform an update operation. For example, Figure 5 This is a signaling flowchart for UE parameter updating provided in an embodiment of this application. Figure 5 As shown, the update process is as follows:

[0111] When the S501 and UDM network elements detect changes in the UE's subscribed information, they remap the updated S-NSSAI and the updated SNPN network information subscribed to by the UE, generate new mapping information, store it, and send it to the AMF network element.

[0112] S502, Perform the UE parameter update process.

[0113] The UE parameter update process will not be detailed here, but can be found in section 4.20.2 of 3GPP TS 23.502.

[0114] S503, UE stores the updated equivalent SNPN list.

[0115] After the update is completed, when the UE registers or uses SNPN for services in the future, the request information will also carry the network information of the SNPN in the updated equivalent SNPN list.

[0116] In one example, the pre-configured equivalent SNPN list for the user terminal may also include:

[0117] In response to a user terminal's registration request, the generated equivalent SNPN list is sent to the user terminal. The generated equivalent SNPN list is generated by the AMF network element based on the user terminal's subscription information sent after confirmation by the UDM network element. The user terminal's subscription information is sent to the UDM network element by the Network Capability Opening Function (NEF) network element when the Application Function (AF) network element determines that the user terminal's subscription information has changed.

[0118] For example, when the AF network element detects a change in the user terminal's subscription information, it sends a request message carrying the user terminal's subscription information to the NEF network element, invoking the NEF network element's create / update / delete services. The NEF network element then forwards the request to the UDM network element, invoking the UDM network element's create / update / delete services. The UDM checks the user terminal's subscription information and then sends it to the AMF network element. The AMF network element performs create / update / delete processing based on the subscription information to obtain an equivalent SNPN list. Subsequently, when configuring the equivalent SNPN list for the user terminal, the AMF network element can respond to the user's registration request by sending the equivalent SNPN list to the user terminal.

[0119] The AF network element invokes one or more of the NEF network element's creation, update, or deletion services based on changes in the subscription information. For example, if it is the first trigger, the creation service can be invoked; if new subscription information is added, the update service can be invoked; if some information is deleted from the subscription information, the deletion service can be invoked, and so on. This application does not impose any restrictions.

[0120] This example provides yet another way to pre-configure an equivalent SNPN list for user terminals, improving the overall usability of the solution.

[0121] For example, Figure 6 This is another signaling flowchart for UE accessing SNPN provided in an embodiment of this application. Figure 6 As shown, the interaction process includes the following:

[0122] S601. When the AF network element discovers that the UE's subscription information has changed, the AF network element sends a request message carrying the UE's subscription information to the NEF network element and calls the NEF network element's creation / update / deletion services.

[0123] The contract information includes network information of the SNPN signed with the UE, and may also include S-NSSAI signed with the UE, as well as mapping information representing the mapping relationship between the network information of S-NSSAI and SNPN.

[0124] S602 and NEF network elements will forward the request information carrying the UE's subscription information to the UDM network element and invoke the UDM network element's creation / update / deletion services.

[0125] S603 and UDM network elements check the UE's subscription information and send it to the AMF network element.

[0126] S604 and AMF network elements perform services such as creation / update / deletion, and generate and store an equivalent SNPN list based on the subscription information.

[0127] S605 and UE perform the registration process.

[0128] For details on the UE registration process, please refer to section 4.2.2.2.2 of 3GPP TS 23.502.

[0129] The S606 and AMF network element respond to the registration process by sending a response message carrying an equivalent SNPN list to the UE.

[0130] S607, UE stores equivalent SNPN list.

[0131] S608, the UE sends an access request to the AMF network element, carrying network information of one or more SNPNs that it needs.

[0132] Based on the network information of the SNPN, the S609 and AMF network elements establish a connection between the UE and the SNPN, and perform subsequent operations such as route selection and bearer establishment for the UE.

[0133] Steps S601 to S607 can be executed only once. After the UE obtains the equivalent SNPN list, steps S608 and S609 are executed every time the SNPN needs to be used.

[0134] Furthermore, regardless of how the AMF network element pre-configures the equivalent SNPN list for the user terminal, the equivalent SNPN list includes not only the network information of the SNPN subscribed to by the user terminal, but also the S-NSSAI subscribed to by the user terminal. There is a mapping relationship between the S-NSSAI and the network information of the SNPN in the equivalent SNPN list. Therefore, when the user terminal sends a registration request to the AMF network element to obtain the equivalent SNPN list, it can also include the request information of the S-NSSAI corresponding to the network information of the SNPN.

[0135] For example, when the equivalent SNPN list also includes the S-NSSAI that is subscribed to by the user terminal, the access request sent by the user terminal may also include the S-NSSAI. The AMF network element can determine the network information of the SNPN corresponding to the S-NSSAI based on the mapping relationship between the network information of the S-NSSAI and the SNPN, and then determine and establish the connection between the user terminal and the SNPN.

[0136] This application provides several methods for pre-configuring equivalent SNPN lists for user terminals. In practical applications, one or more of these methods can be selected according to actual needs, and the above methods can also be combined with each other.

[0137] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0138] Figure 7 This is a schematic diagram of a device for accessing an independent, non-public network, provided as an embodiment of this application. Figure 7 As shown, the device 70 for accessing an independent non-public network in this embodiment includes: a receiving unit 701 and a control unit 702.

[0139] The receiving unit 701 is used to receive an access request sent by a user terminal. The access request includes network information of an independent non-public network (SNPN) required by the user terminal. The network information in the access request is one or more from an equivalent SNPN list. The equivalent SNPN list is pre-configured by the AMF network element for the user terminal and includes network information of SNPNs that have signed up with the user terminal.

[0140] The control unit 702 is used to establish a connection between the user terminal and the SNPN corresponding to the network information in the access request, based on the access request.

[0141] Figure 8 This is a schematic diagram illustrating the structure of another device for accessing an independent, non-public network, provided as an embodiment of this application. (See attached diagram.) Figure 8 As shown, the device 80 for accessing an independent non-public network in this embodiment includes: a receiving unit 801 and a control unit 802.

[0142] The receiving unit 801 is used to receive an access request sent by a user terminal. The access request includes network information of an independent non-public network (SNPN) required by the user terminal. The network information in the access request is one or more from an equivalent SNPN list. The equivalent SNPN list is pre-configured by the AMF network element for the user terminal and includes network information of SNPNs that have signed up with the user terminal.

[0143] The control unit 802 is used to establish a connection between the user terminal and the SNPN corresponding to the network information in the access request, based on the access request.

[0144] In one example, the equivalent SNPN list is pre-stored in the AMF network element, and the device 80 also includes a configuration unit 803, which includes a first configuration module 8031.

[0145] The first configuration module 8031 ​​is used to respond to the user terminal's registration request by sending the equivalent SNPN list pre-stored in the AMF network element to the user terminal.

[0146] In one example, configuration unit 803 includes a second configuration module 8032.

[0147] The second configuration module 8032 is used to respond to the user terminal's registration request, obtain the equivalent SNPN list from the Unified Data Management (UDM) network element, and send the equivalent SNPN list to the user terminal.

[0148] In one example, the second configuration module 8032 includes the acquisition module 10.

[0149] The acquisition module 10 is used to send an acquisition request to the UDM network element, wherein the acquisition request is used to indicate the acquisition of the user terminal's subscription information; and to receive the subscription information returned by the UDM network element, wherein the subscription information includes the network information of the SNPN signed with the user terminal, and to generate an equivalent SNPN list based on the subscription information.

[0150] In one example, the subscription information also includes Single Network Slice Selection Auxiliary Information (S-NSSAI) signed with the user terminal, as well as mapping information, which is the mapping relationship between S-NSSAI and SNPN network information; the acquisition module 10 includes a generation module 100.

[0151] The generation module 100 is used to parse the mapping information and determine the network information of the SNPN corresponding to S-NSSAI; and to generate an equivalent SNPN list based on the S-NSSAI subscribed to with the user terminal and the network information of the SNPN corresponding to S-NSSAI.

[0152] In one example, configuration unit 803 includes a third configuration module 8033.

[0153] The third configuration module 8033 is used to respond to the user terminal's registration request by sending the generated equivalent SNPN list to the user terminal; wherein, the generated equivalent SNPN list is generated by the AMF network element based on the user terminal's subscription information sent after confirmation by the UDM network element; the user terminal's subscription information is sent to the UDM network element by the Network Capability Opening Function (NEF) network element when the Application Function (AF) network element determines that the user terminal's subscription information has changed.

[0154] In one example, the equivalent SNPN list also includes the S-NSSAI subscribed to by the user terminal, and there is a mapping relationship between the network information of the S-NSSAI and the SNPN in the equivalent SNPN list.

[0155] In one example, the access request also includes the S-NSSAI corresponding to the network information of the SNPN required by the user terminal.

[0156] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. These modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented in software via processing element calls, while others are implemented in hardware. Furthermore, they can be stored as program code in the device's memory, and the data processing modules can be called and executed by a specific processing element. The implementation of other modules is similar. These modules can be fully or partially integrated together, or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0157] Figure 9 This is a schematic diagram of the access device provided in an embodiment of this application. Figure 9 As shown, the access device 90 includes a processor 901 and a memory 902 that is communicatively connected to the processor.

[0158] The memory 902 stores computer-executable instructions; the processor 901 executes the computer-executable instructions stored in the memory 902 to implement the method as described above.

[0159] In the specific implementation of the aforementioned electronic device, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0160] This application also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, are used to implement the methods described in any of the foregoing embodiments.

[0161] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to computer instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0162] This application also provides a computer program product, including a computer program that, when executed by a processor, is used to implement the method as described in any of the foregoing embodiments.

[0163] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0164] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for accessing an independent, non-public network, characterized in that, The method is applied to Access and Mobility Management Function (AMF) network elements, and the method includes: The system receives an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network (SNPN) required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of multiple SNPNs that have signed contracts with the user terminal, are of equal status, and all allow the user terminal to register and execute services; Based on the access request, a connection is established between the user terminal and the SNPN corresponding to the network information in the access request; The equivalent SNPN list is pre-stored in the AMF network element; the method further includes: in response to the registration request of the user terminal, sending the equivalent SNPN list pre-stored in the AMF network element to the user terminal; Alternatively, in response to the registration request from the user terminal, the equivalent SNPN list is obtained from the Unified Data Management (UDM) network element; and the equivalent SNPN list is sent to the user terminal. Alternatively, in response to the user terminal's registration request, the generated equivalent SNPN list is sent to the user terminal; wherein the generated equivalent SNPN list is generated by the AMF network element based on the user terminal's subscription information sent after confirmation by the UDM network element; the user terminal's subscription information is sent to the UDM network element by the Network Capability Opening Function (NEF) network element when the Application Function (AF) network element determines that the user terminal's subscription information has changed.

2. The method according to claim 1, characterized in that, Obtaining the equivalent SNPN list from the UDM network element includes: Send an acquisition request to the UDM network element, wherein the acquisition request is used to indicate the acquisition of the user terminal's subscription information; The system receives subscription information returned by the UDM network element, the subscription information including network information of the SNPN signed with the user terminal, and generates the equivalent SNPN list based on the subscription information.

3. The method according to claim 2, characterized in that, The subscription information also includes Single Network Slice Selection Assist Information (S-NSSAI) subscribed to by the user terminal, and mapping information, wherein the mapping information is the mapping relationship between S-NSSAI and SNPN network information; The step of generating the equivalent SNPN list based on the contract information includes: Parse the mapping information to determine the network information of the SNPN corresponding to S-NSSAI; The equivalent SNPN list is generated based on the S-NSSAI contracted with the user terminal and the network information of the SNPN corresponding to the S-NSSAI.

4. The method according to any one of claims 1-3, characterized in that, The equivalent SNPN list also includes S-NSSAIs that are subscribed to by the user terminal, and there is a mapping relationship between the network information of the S-NSSAIs and the SNPNs in the equivalent SNPN list.

5. The method according to claim 4, characterized in that, The access request also includes S-NSSAI corresponding to the network information of the SNPN required by the user terminal.

6. An apparatus for accessing an independent, non-public network, wherein the apparatus is used to implement the method for accessing an independent, non-public network as described in any one of claims 1-5, characterized in that, The device includes: A receiving unit is configured to receive an access request sent by a user terminal, wherein the access request includes network information of an independent non-public network (SNPN) required by the user terminal, and the network information in the access request is one or more from an equivalent SNPN list; the equivalent SNPN list is pre-configured by the AMF network element for the user terminal, and the equivalent SNPN list includes network information of SNPNs subscribed to by the user terminal; The control unit is used to establish a connection between the user terminal and the SNPN corresponding to the network information in the access request, based on the access request.

7. An access device, characterized in that, The access device includes: a processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-5.

Images