A terminal startup registration method, device and equipment

Abstract

The application discloses a terminal startup registration method, device and equipment, and the method comprises the following steps: initiating a pre-registration process of a terminal which is not started up and registered to a second network; receiving subscription data of the terminal which is not started up and registered and fed back by the second network; and initiating a startup registration process of the terminal according to a network state of the terminal. In the above manner, the application enables the terminal to use normal services when a link fault occurs between a park network and a large network to which the terminal belongs.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and specifically to a method, apparatus, and device for powering on and registering a terminal. Background Technology

[0002] In existing lightweight 5GC (5G Core Network) application scenarios, in order to meet the business needs of some vertical industries in specific areas and provide users with a better and more targeted service experience, current solutions typically employ methods such as... Figure 1 The AMF (Access and Mobility Management Function), SMF (Session Management Function), and UPF (User Plane Function) shown are deployed in the campus, while the remaining 5GC network elements are deployed centrally.

[0003] However, this solution has a drawback: if the link between the centralized deployment network and the campus network (i.e., link 1 and link 2) fails, while other network links (i.e., links 3 to 9) are operating normally, users who have not yet powered on and registered to access the network cannot interact with AUSF / UDM (Authentication Server Function / Unified Data Management), and cannot perform authentication, registration, session establishment, and other processes, resulting in a degraded user experience. Summary of the Invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide a terminal power-on registration method, apparatus and device that overcomes or at least partially solves the above problems.

[0005] According to one aspect of the present invention, a method for powering on and registering a terminal is provided, applied to a first network element of a first network, the method comprising:

[0006] Initiate a pre-registration process for terminals that are not yet powered on and registered to the second network;

[0007] Receive the subscription data of the terminal that has not been powered on and registered, fed back from the second network;

[0008] Based on the terminal's network status, initiate the terminal's power-on registration process.

[0009] According to another aspect of the present invention, a terminal power-on registration device is provided, applied to a first network element of a first network, the device comprising:

[0010] The transceiver module is used to initiate a pre-registration process for terminals that have not been powered on and registered to the second network; and to receive the subscription data of the terminals that have not been powered on and registered from the second network.

[0011] The processing module is used to initiate the power-on registration process of the terminal based on the network status of the terminal.

[0012] According to another aspect of the present invention, a computing device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus;

[0013] The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the power-on registration method of the aforementioned terminal.

[0014] According to another aspect of the present invention, a computer storage medium is provided, the storage medium storing at least one executable instruction, the executable instruction causing a processor to perform an operation corresponding to the above-described terminal boot registration method.

[0015] According to the solution provided in the above embodiments of the present invention, the terminal power-on registration method can initiate a pre-registration process for an unregistered terminal to a second network; receive the subscription data of the unregistered terminal fed back by the second network; and initiate the power-on registration process for the terminal according to the network status of the terminal. This solves the problem of inability to interact caused by link failure between the park network and the main network to which the terminal belongs in the centralized deployment mode of AMF+SMF+UPF sinking to the park, and realizes that when the link failure occurs between the park network and the main network to which the terminal belongs, the terminal can be powered on and used normally.

[0016] The above description is merely an overview of the technical solutions of the embodiments of the present invention. In order to better understand the technical means of the embodiments of the present invention and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of the present invention more obvious and understandable, specific implementation methods of the embodiments of the present invention are described below. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0018] Figure 1 This diagram illustrates the structure of a terminal power-on registration method based on an embodiment of the present invention, which utilizes an AMF+SMF+UPF deployment in a suburban park.

[0019] Figure 2 A flowchart of the terminal power-on registration method provided in an embodiment of the present invention is shown;

[0020] Figure 3 A schematic diagram of the pre-registration process in a specific embodiment 1 provided by the present invention is shown;

[0021] Figure 4 This diagram illustrates the authentication process when the network status is normal in a specific embodiment 2 provided by the present invention.

[0022] Figure 5 This diagram illustrates the AMF selection process when the network status is normal in a specific embodiment 2 provided by the present invention.

[0023] Figure 6 This diagram illustrates the power-on registration process when the network status is normal in a specific embodiment 2 provided by the present invention.

[0024] Figure 7 The diagram illustrates the process of establishing a PDU session when the network status is normal in a specific embodiment 3 provided by the present invention.

[0025] Figure 8 This diagram illustrates the authentication process when the network status is abnormal in a specific embodiment 4 provided by the present invention.

[0026] Figure 9 This diagram illustrates the AMF selection process when the network status is abnormal in a specific embodiment 4 provided by the present invention.

[0027] Figure 10 This diagram illustrates the startup registration process when the network status is abnormal in a specific embodiment 4 provided by the present invention.

[0028] Figure 11 The diagram illustrates the process of establishing a PDU session when the network status is abnormal in a specific embodiment 5 provided by the present invention.

[0029] Figure 12 This diagram illustrates the structure of the terminal power-on registration device provided in an embodiment of the present invention.

[0030] Figure 13 A schematic diagram of the structure of a computing device provided in an embodiment of the present invention is shown. Detailed Implementation

[0031] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0032] Figure 2 A flowchart illustrating the terminal power-on registration method provided in an embodiment of the present invention is shown. Figure 1 As shown, the method, applied to the first network element of the first network, includes the following steps:

[0033] Step 21: Initiate a pre-registration process for terminals that have not yet been powered on and registered to the second network;

[0034] Step 22: Receive the subscription data of the terminal that has not been powered on and registered, fed back by the second network;

[0035] Step 23: Initiate the power-on registration process for the terminal based on its network status.

[0036] In this embodiment, a pre-registration is initiated for an unregistered terminal through a first network element of the first network, and the subscription data of the unregistered terminal is received from the second network. When the terminal is registered, the registration process can be initiated based on the network status of the terminal. This solves the problem of no interaction caused by link failure between the park network and the main network to which the terminal belongs in the centralized deployment mode of AMF+SMF+UPF in the park, and enables normal service to be used when the link between the park network and the main network to which the terminal belongs is failed.

[0037] It should be noted that the preferred first network is the sinking campus. The first network here includes the first network element, the second network element, the third network element, and the fourth network element. The preferred first network element is Lite 5GC Proxy (lightweight 5G core network proxy server), the preferred second network element is AMF (access and mobility management function), the preferred third network element is SMF (session management function), and the preferred fourth network element is UPF (user plane function). The preferred second network is the centrally deployed terminal home network (AUSF / UDM, authentication service function / unified data management entity).

[0038] In an optional embodiment of the present invention, step 21 includes:

[0039] Step 211: Based on the preset activation time of the pre-registration process and the pre-configured terminal information of the terminal that has not been powered on for registration, initiate the pre-registration process for the terminal that has not been powered on for registration to the second network.

[0040] In this embodiment, the pre-configured terminal information for unregistered terminals includes at least one of the following: SUPI / GPSI (Subscription Permanent Identifier / Generic Public Subscription Identifier) ​​code data of all unregistered terminals in the first network, configurable time period, date and time of first initiation of the pre-registration process, and time of periodic pre-registration.

[0041] In this process, when the first network element of the first network performs the configurable time period for configuration pre-registration, it counts the SUPI / GPSI code data of the terminals that have been registered and powered on within the period, and calculates the SUPI / GPSI code data of the terminals that have not been registered and powered on, so as to determine the range of terminals that have not been registered and powered on and need to be registered, and preferably generates a list of SUPI / GPSI code data of terminals that have not been registered and powered on within the period.

[0042] The preferred format for the date and time of the first use of the pre-registration process is a date, month, day, hour, and minute, but this application does not limit it to this; the preferred format for the time of periodic pre-registration is a time and minute every day, but this application does not limit it to this either.

[0043] Further, in an optional embodiment of the present invention, step 22 includes:

[0044] Step 221: Send an authentication request for the terminal that has not been powered on and registered to the second network;

[0045] Step 222: Receive authentication vector data fed back by the second network according to the authentication request;

[0046] Step 223: Send a registration request for the terminal that has not been powered on and registered to the second network;

[0047] Step 224: Receive a registration success message from the second network based on the registration request;

[0048] Step 225: Send the first subscription data request of the terminal that has not been powered on and registered to the second network;

[0049] Step 226: Receive the first contract data fed back by the second network based on the contract data request;

[0050] Step 227: Send the second subscription data request of the terminal that has not been powered on and registered to the second network;

[0051] Step 228: Receive the second contract data fed back by the second network based on the contract data request.

[0052] In this embodiment, based on the pre-configured terminal information of the terminal that has not been powered on and registered, the pre-registration process is initiated at the preset activation time of the pre-registration process. Specifically, the first network element simulates the second network element and sends the authentication request of the terminal that has not been powered on and registered to the second network to which the terminal belongs in a preset order. Here, the authentication request of the terminal that has not been powered on and registered can preferably be sent in batches in a preset order.

[0053] After receiving the authentication request, the second network sends the terminal's authentication vector data back to the first network element. The first network element caches the terminal's authentication vector data for use in case of an abnormal link connection between the first and second networks. The first network element no longer sends authentication requests to the terminal, and at this time, the terminal is assumed to be a legitimate user.

[0054] The first network element simulates the second network element and initiates a registration request to the second network corresponding to the terminal that has not been powered on and registered. The second network updates the relevant registration information of the terminal according to the registration request and returns a registration success message to the first network element.

[0055] The first network element sends a first subscription data request to the second network for an unregistered terminal, requesting to obtain the terminal's first subscription data. Preferably, this first subscription data is MM (Mobility Management) subscription data. The second network, based on the first subscription data request, sends the first subscription data back to the first network element. Simultaneously, the first network element preferably subscribes to the terminal's first subscription data from the second network. When the terminal's first subscription data changes, the second network notifies the first network element of the changes. After receiving a registration success message, the first network element no longer forwards the registration success message to the terminal.

[0056] The first network element simulates the second network element to send a second subscription data request to the second network for a terminal that has not been powered on and registered. The request requests the second subscription data of the terminal. The second subscription data is preferably SM (Session Management) subscription data. The second network sends the second subscription data back to the first network element according to the second subscription data request. The first network element simulates the third network element to cache the second subscription data and does not proceed to the next PDU (Protocol Data Unit) session establishment process. Thus, the pre-registration of the terminal that has not been powered on and registered is completed.

[0057] Figure 3 This diagram illustrates the pre-registration process in a specific embodiment 1 provided by the present invention; as shown below. Figure 3As shown in a specific embodiment 1, the private network includes UE (User Equipment, terminal), gNB (NR Node B, NR node, i.e., base station), and a lightweight 5G core network proxy server Lite5GCProxy. The main network includes AUSF / UDM / UDR (Authentication Service Function / Unified Data Management Entity / Unified Data Repository). Parameter settings are configured for the terminals in the private network. Specifically, the SUPI / GPSI (Subscription Permanent Identifier / Generic Public Subscription Identifier) ​​code data of all registered user terminals within the campus where the private network is located are configured. At the same time, a configurable time period is set to determine the range of terminals that need to be pre-registered. Specifically, a list of SUPI / GPSI code data corresponding to terminals under the 5G private network that have not been activated and registered within the period is generated. The date and time of the first activation of the pre-registration process are set, as well as the time for periodic pre-registration. Then, the pre-registration process is initiated to generate a set of authentication vectors and subscription data for terminals that have not been activated and registered.

[0058] The pre-registration process specifically includes:

[0059] (1-1) Based on the statistics of the unregistered terminals in the lightweight 5G core network proxy server Lite 5GCProxy, the AMF simulates the access and mobility management function to initiate the authentication process to AUSF / UDM / UDR in batches, that is, to send authentication requests.

[0060] (1-2) AUSF / UDM / UDR sends a set of authentication vector data of the terminal to Lite 5GCProxy;

[0061] (1-3) After receiving the authentication vector data from the terminal, Lite 5GCProxy caches the authentication vector data from the terminal and does not forward the authentication request to the terminal, and assumes that the terminal is a legitimate user terminal.

[0062] (1-4) Lite 5GCProxy sends registration requests to AUSF / UDM / UDR for terminals that have not been powered on and registered;

[0063] (1-5) After AUSF / UDM / UDR updates the terminal-related registration information, it returns a registration success message to Lite 5GCProxy;

[0064] (1-6) Lite 5GCProxy initiates a request to AUSF / UDM / UDR to obtain MM subscription data; AUSF / UDM / UDR sends MM subscription data back to Lite 5GCProxy based on the first subscription data request; Lite 5GCProxy subscribes to the terminal's first subscription data from AUSF / UDM / UDR, and when the terminal's user MM subscription data changes, AUSF / UDM / UDR notifies Lite 5GCProxy of the changed MM subscription data;

[0065] (1-7) After receiving the MM signing data sent by AUSF / UDM / UDR, Lite 5GCProxy does not send a registration success message to the terminal, and completes the pre-registration process of the terminal.

[0066] (1-8) Lite 5GCProxy simulates the session management function. SMF sends an SM subscription data request to AUSF / UDM / UDR; AUSF / UDM / UDR sends SM subscription data back to Lite 5GCProxy;

[0067] (1-9) Lite 5GCProxy receives AUSF / UDM / UDR and simulates SMF to cache the SM subscription data of terminals that have not been powered on and registered, and does not proceed to the next PDU session establishment process.

[0068] In an optional embodiment of the present invention, step 23 includes:

[0069] Step 23-1: When the network status of the terminal is normal, delete the cached authentication vector data of the terminal and initiate an authentication process request to the second network.

[0070] Step 23-2: Delete the subscription data of the terminal, initiate the selection process of the second network element to the second network, and the second network element requests and subscribes to the network slice identifier provided by the terminal to obtain the selection result of the second network element of the terminal;

[0071] Step 23-3: Delete the first subscription data of the terminal, initiate registration with the second network, and the second network element sends a registration response to the terminal.

[0072] In this embodiment, when the network status of the terminal is normal, the power-on registration process for unregistered users includes: the terminal authentication process, the second network element selection process, and the terminal registration process.

[0073] Optionally, when the terminal's network status is normal, the authentication process includes:

[0074] The terminal initiates a power-on registration with the base station. The base station selects a second network element based on the network slice identifier. This second network element processes the power-on registration request message from the terminal and initiates an authentication process request to the first network element to which the terminal belongs. At this time, the first network element judges the current network status. When the terminal's network status is normal, that is, when the link connection between the first network element and the second network to which the terminal belongs is normal, the first network element deletes the cached authentication vector data of the terminal and simulates the second network element to initiate an authentication process request to the second network. The second network returns the authentication vector data to the first network element according to the authentication process request. The first network element receives the authentication vector data and forwards it to the second network element. The process involves forwarding data; the second network element sends the RAND (random number) and AUTN (authentication token) from the authentication vector data to the terminal; the terminal returns the calculated RES* (return value) to the second network element, which performs roaming authentication on the terminal and forwards the RES* (return value) to the first network element; the first network element forwards the RES* (return value) to the second network again; in the second network, the RES* (return value) is compared with the XRES* (expected user response value) generated by the second network itself; if the expected user response value and the return value are the same, the authentication success result is fed back to the second network element, and a security context is established between the second network element and the terminal.

[0075] Optionally, when the terminal's network status is normal, the selection process for the second network element includes:

[0076] The first network element receives a request from the second network element to download network slice subscription data. At this time, the first network element assesses the current network status. If the terminal's network status is normal (i.e., the link between the first network element and the terminal's second network is normal), the first network element deletes the terminal's first subscription data and simulates the second network element initiating a request to download network slice subscription data to the second network. The second network element obtains the allowed network slice identifier based on the network slice identifier requested and subscribed to by the terminal, and obtains the target second network element based on pre-configured network slice selection data or NSSF (Network Slice Selection Function). The target second network element and the second network element are compared. If their selections are the same, the terminal's second network element selection result is obtained as the second network element. If their selections are different, the base station is instructed to redirect to the target second network element.

[0077] Optionally, when the terminal's network status is normal, the terminal registration process includes:

[0078] The second network element initiates a registration request to the first network element. At this time, the first network element judges the current network status. If the terminal's network status is normal, it deletes the terminal's first subscription data and initiates registration with the second network. The second network forwards the registration success message to the second network element through the first network element. The second network element forwards the first subscription data request to the second network element through the first network element. The second network forwards the first subscription data to the second network element through the first network element. The second network element sends the first subscription data request of the terminal to the second network element through the first network element. When the first subscription data changes, the second network notifies the first network element of the changed first subscription data, and the first network element forwards it to the second network element. Finally, the second network element sends a registration acceptance response to the terminal.

[0079] Figure 4 This diagram illustrates the authentication process when the network status is normal in a specific embodiment 2 provided by the present invention. Figure 5 This diagram illustrates the AMF selection process when the network status is normal in a specific embodiment 2 provided by the present invention. Figure 6 This diagram illustrates the power-on registration process when the network status is normal in a specific embodiment 2 provided by the present invention; as shown below. Figures 4 to 6 As shown, in a specific embodiment 2, when the network status is normal, the private network includes the UE terminal, gNB base station, Lite 5GCProxy lightweight 5G core network proxy server, and AMF access and mobility management function, while the main network includes AUSF / UDM / UDR. The authentication process specifically includes:

[0080] (2-1-1) The terminal UE initiates the power-on registration process to the base station;

[0081] (2-1-2) The base station gNB selects the Access and Mobility Management Function (AMF) based on the network slice identifier of the terminal;

[0082] (2-1-3) The Mobility Management Function (AMF) initiates the terminal authentication process to the lightweight 5G core network proxy server Lite5GCProxy;

[0083] (2-1-4) When the authentication service function / unified data management entity AUSF / UDM link to which the terminal UE belongs is normal, that is, when the link connection between the private network and the main network is normal, clear the cached authentication vector data of the terminal UE.

[0084] (2-1-5) Lite 5GCProxy simulates AMF initiating an authentication process for key objects to AUSF / UDM / UDR;

[0085] (2-1-6) AUSF / UDM / UDR sends a set of authentication vector data of the terminal UE to Lite 5GCProxy;

[0086] (2-1-7) Lite 5GCProxy forwards a set of authentication vector data of the terminal UE to AMF;

[0087] (2-1-8) The AMF sends the random number RAND and the authentication token AUTN from a set of authentication vector data obtained from AUSF / UDM to the terminal. After the terminal completes the authentication, it sends the return value RES* back to the AMF.

[0088] (2-1-9) After AMF performs roaming location authentication on the terminal, it forwards the return value RES* to Lite5GCProxy;

[0089] (2-1-10) Lite 5GCProxy forwards RES* to AUSF / UDM / UDR;

[0090] (2-1-11) AUSF / UDM / UDR compares the received return value RES* with the expected user response value XRES* generated by itself. If the authentication is successful, it returns the authentication success result to Lite 5GCProxy.

[0091] (2-1-12) Establish a security context between the AMF and the terminal;

[0092] The selection process for AMF specifically includes:

[0093] (2-2-1) AMF sends a request to Lite 5GCProxy to download network slice subscription data;

[0094] (2-2-2) When the AUSF / UDM link to which the terminal UE belongs is normal, that is, when the link connection between the private network and the main network is normal, delete the cached subscription data of the terminal UE.

[0095] (2-2-3) Lite 5GCProxy simulates AMF initiating a request to AUSF / UDM / UDR to download network slice subscription data;

[0096] (2-2-4) AUSF / UDM / UDR provides Lite5GCProxy with the Subscribed Network Slice ID (Subscribed S-NSSAII) based on the request to download the subscribed network slice data.

[0097] (2-2-5) Lite 5GCProxy simulates AUSF / UDM to provide Subscribed S-NSSAII to AMF;

[0098] (2-2-6) The AMF obtains the allowed network slice identifier number Allowed NSSAI based on the network slice identifier number requested by the terminal UE and the Subscribed S-NSSAI, and completes the selection of the target AMF according to the pre-configured network slice selection data or in cooperation with the network slice selection function entity NSSF. If the target AMF is not the current AMF, the base station gNB is instructed to redirect the terminal UE registration request to the target AMF.

[0099] The specific steps of the startup and registration process include:

[0100] (2-3-1) AMF sends a registration request to Lite 5GCProxy;

[0101] (2-3-2) When Lite 5GCProxy determines that the AUSF / UDM link to which the terminal belongs is normal, that is, when the link connection between the private network and the main network is normal, it deletes the cached MM subscription data of the terminal UE.

[0102] (2-3-3) Lite 5GCProxy simulates AMF sending a registration request to AUSF / UDM / UDR;

[0103] (2-3-4) After AUSF / UDM / UDR updates the registration information related to the terminal UE, it returns a registration success message to Lite5GCProxy;

[0104] (2-3-5) Lite 5GCProxy forwards the registration success message to AMF;

[0105] (2-3-6) AMF forwards the terminal's MM subscription data request to AUSF / UDM through Lite 5GCProxy; AUSF / UDM sends the MM subscription data back to Lite 5GCProxy; and Lite5GCProxy forwards the MM subscription data to AMF;

[0106] (2-3-7) The AMF sends a request for the subscription terminal's MM subscription data to the AUSF / UDM / UDR through the Lite 5GCProxy; when the terminal's MM subscription data changes, the AUSF / UDM / UDR sends a notification of the change to the Lite5GCProxy, the Lite 5GCProxy forwards the notification to the AMF, and finally the AMF sends a registration response to the terminal.

[0107] In an optional embodiment of the present invention, after step 23, the method further includes:

[0108] Steps 23-4: Forward the protocol data unit session request of the third network element to the second network, delete the cached second subscription data of the terminal, and receive the latest second subscription data fed back by the second network;

[0109] Step 23-5: Forward the latest second contract data to the third network element, and establish a protocol data unit session bearer through the third network element;

[0110] Step 23-6: Update the protocol data unit session information of the third network element to the second network.

[0111] This embodiment describes the process of establishing a PDU (Protocol Data Unit) session when the network status is normal. The terminal sends a PDU session request to the second network element, which forwards the request to the third network element. The third network element sends a second subscription data request to the first network element and forwards the PDU session request back to the second network. The first network element checks the current network status. If the network status is normal, the first network element deletes the cached second subscription data of the terminal and receives the second subscription data returned by the second network, then forwards it to the third network element. The third network element controls the fourth network element and interacts with the second network element to establish a PDU session bearer for the terminal. The third network element updates the terminal's PDU session information to the second network through the first network element. Here, the third network element is preferably an SMF (Session Management Function).

[0112] It should be noted that the protocol data unit session information here includes SUPI, DNN (Data Network Name), PDU (Protocol Data Unit) session ID (Identity document), and SMF ID (Identity document).

[0113] Figure 7 This illustrates a flowchart of establishing a PDU session when the network status is normal in a specific embodiment 3 provided by the present invention; as shown below. Figure 7 As shown in a specific embodiment 3, when the network status is normal, the private network includes the terminal UE, the base station gNB, the lightweight 5G core network proxy server Lite5GCProxy, the access and mobility management function AMF, and the session management function SMF. The main network includes AUSF / UDM / UDR. The process of establishing a PDU session specifically includes:

[0114] (3-1) The terminal UE initiates a request to the AMF;

[0115] (3-2) The AMF forwards the PDU session establishment request to the SMF;

[0116] (3-3) SMF sends a request for SM subscription data to Lite 5GCProxy; Lite 5GCProxy then forwards the request for SM subscription data to UDM / UDR;

[0117] (3-4) When Lite 5GCProxy determines that the main network link to which the terminal UE belongs is normal, it clears the SM subscription data of the terminal UE.

[0118] (3-5) UDM / UDR sends the feedback SM contract data to SMF through Lite 5GCProxy;

[0119] (3-6) The SMF controls the UPF (User Plane Function) and completes relevant interactions with the AMF to establish a PDU bearer for the UE terminal;

[0120] (3-7) Update PDU session information.

[0121] In an optional embodiment of the present invention, step 23 includes:

[0122] Step 23-7: When the network status of the terminal is abnormal, receive the authentication vector request initiated by the second network element and send the cached authentication vector data of the terminal to the second network element.

[0123] Step 23-8: Receive the return value fed back by the second network element based on the authentication vector data, and compare the return value with the pre-generated expected user response value to obtain the authentication result;

[0124] Step 23-9: Receive the download network slice subscription data request initiated by the second network element, and provide the second network element with the subscription network slice identifier of the terminal;

[0125] Step 23-10: The second network element obtains the selection result of the second network element of the terminal based on the network slice identifier request provided by the terminal and the subscribed network slice identifier;

[0126] Step 23-11: Receive the registration request initiated by the second network element and return a registration success message to the second network element;

[0127] Step 23-12: Receive the first contract data request sent by the second network element, and send the first contract data back to the second network element;

[0128] Step 23-13: The second network element sends a registration response to the terminal.

[0129] In this embodiment, when the network status of the terminal is abnormal, the power-on registration process for unregistered users includes: the terminal authentication process, the second network element selection process, and the terminal registration process.

[0130] Optionally, when the terminal's network status is abnormal, the authentication process includes:

[0131] The terminal initiates initial registration by sending a power-on registration process to the base station. The base station selects a second network element based on the network slice identifier. The second network element processes the registration request message and sends an authentication vector request for the terminal to the first network element to which it belongs. It should be noted that in abnormal network conditions, the second network element treats the first network element as a second network in normal conditions for interaction. Since the first network element stores relevant terminal data during pre-registration, it can still complete the power-on registration of the terminal even in abnormal network conditions. The first network element assesses the current network status; if it detects an abnormal link with the second network or that the second network is unavailable, the first network element determines that an abnormality handling mechanism should be initiated. The authentication vector data of the pre-registered cached terminal is fed back to the second network element; the second network element sends the random number RAND and authentication token AUTN from the authentication vector data obtained from the first network element to the terminal. After the terminal completes authentication, it returns the calculated return value RES* to the second network element; the second network element performs roaming location authentication on the terminal and then forwards the return value RES* to the first network element; the first network element compares the received return value RES* with its own generated expected user response value XRES*. If they are the same, the terminal authentication is successful, and the first network element feeds back the authentication result to the second network element; furthermore, a security context is established between the second network element and the terminal.

[0132] Optionally, when the terminal's network status is abnormal, the selection process for the second network element includes:

[0133] The second network element initiates a request to the first network element to download the network slice subscription data. At this time, the first network element judges the current network status. When it detects an abnormal link between the terminal and the second network or that the second network is unavailable, the first network element activates the abnormal handling mechanism. The first network element simulates the second network and provides the terminal's subscribed network slice identifier to the second network element. The second network element obtains the allowed network slice identifier based on the network slice identifier request provided by the terminal and the subscribed network slice identifier obtained from the first network element. Based on the pre-configured network slice selection data or NSSF, it obtains the target second network element. The target second network element and the second network element are compared. If the selections of the second network element and the target second network element are the same, the terminal's selected second network element is taken as the second network element. If the selections of the second network element and the target second network element are different, the base station is instructed to redirect to the target second network element, that is, the target second network element is taken as the selection result.

[0134] Optionally, when the terminal's network status is abnormal, the terminal's power-on registration process includes:

[0135] The second network element sends a registration request to the first network element; the first network element judges the current network status, and when it detects an abnormal link between itself and the second network to which the terminal belongs or when the second network is unavailable, the first network element initiates an abnormality handling mechanism; the first network element compares and processes the pre-registered subscription information and returns a registration success message to the second network element; the second network element sends a first subscription data request to the first network element, and sends the first subscription data back to the second network element; when the first subscription data changes, the first network element notifies the second network element of the changed first subscription data, and finally the second network element sends a registration response to the terminal.

[0136] Figure 8 This diagram illustrates the authentication process when the network status is abnormal in a specific embodiment 4 provided by the present invention. Figure 9 This diagram illustrates the AMF selection process when the network status is abnormal in a specific embodiment 4 provided by the present invention. Figure 10 This illustration shows a schematic diagram of the power-on registration process when the network status is abnormal in a specific embodiment 4 provided by the present invention; as follows: Figures 8 to 10 As shown in a specific embodiment 4, when the network status is abnormal, the private network includes the terminal UE, the base station gNB, the lightweight 5G core network proxy server Lite 5GCProxy, and the access and mobility management function AMF. The authentication process specifically includes:

[0137] (4-1-1) The terminal UE initiates the power-on registration process to the base station gNB;

[0138] (4-1-2) The base station gNB selects the Access and Mobility Management Function (AMF) based on the network slice identifier;

[0139] (4-1-3) The AMF processes the registration request message and initiates an authentication vector request for the powered-on user to the Lite 5GC Proxy to which the terminal UE belongs;

[0140] (4-1-4) Lite 5GC Proxy judges the current network status. When it detects that the Authentication Service Function / Unified Data Management Entity AUSF / UDM link with the UE is abnormal or AUSF / UDM is unavailable, Lite 5GC Proxy will start the abnormal handling mechanism.

[0141] (4-1-5) Lite 5GC Proxy feeds back the authentication vector data of the pre-registered cached terminals to AMF;

[0142] (4-1-6) The AMF sends the random number RAND and the authentication token AUTN from the authentication vector data obtained from the Lite 5GC Proxy to the terminal UE; after the terminal UE completes authentication, it returns the calculated return value RES* to the AMF;

[0143] (4-1-7) After AMF performs roaming location authentication on the terminal UE, it forwards the return value RES* to Lite 5GCProxy;

[0144] (4-1-8) Lite 5GC Proxy compares the received return value RES* with the expected user response value XRES* generated by itself. If they are the same, the authentication of the user terminal is successful, and Lite 5GC Proxy sends the authentication result to AMF as successful.

[0145] (4-1-9) Establish a security context between the AMF and the UE.

[0146] The selection process for AMF specifically includes:

[0147] (4-2-1) AMF sends a request to Lite 5GC Proxy to download network slice subscription data;

[0148] (4-2-2) Lite 5GC Proxy judges the current network status. When it detects that the Authentication Service Function / Unified Data Management Entity AUSF / UDM link with the terminal UE is abnormal or AUSF / UDM is unavailable, Lite 5GC Proxy will start the abnormal handling mechanism.

[0149] (4-2-3) Lite 5GC Proxy simulates AUSF / UDM and provides AMF with a pre-registered cached Subscribed Network Slice ID (S-NSSAI).

[0150] (4-2-4) The AMF obtains the allowed network slice identifier number Allowed NSSAI based on the network slice identifier number requested by the terminal UE and the Subscribed S-NSSAI obtained from the Lite5GC Proxy, and completes the selection of the target AMF according to the pre-configured network slice selection data or in cooperation with the NSSF. If the target AMF is not the originally selected AMF, the base station gNB is instructed to redirect the terminal UE registration request to the target AMF.

[0151] The terminal's power-on registration process specifically includes:

[0152] (4-3-1) AMF sends a registration request to Lite 5GC Proxy;

[0153] (4-3-2) Lite 5GC Proxy judges the current network status. When it detects that the Authentication Service Function / Unified Data Management Entity AUSF / UDM link with the terminal UE is abnormal or AUSF / UDM is unavailable, Lite 5GC Proxy will start the abnormal handling mechanism.

[0154] (4-3-3) Lite5GCProxy compares the pre-registered contract information and returns a registration success message to AMF;

[0155] (4-3-4) The AMF sends a MM subscription data request to Lite5GCProxy, and Lite5GCProxy returns the UE's MM subscription data to the AMF; the AMF subscribes to the UE's user subscription data from Lite5GCProxy, and when the UE's MM subscription data changes, Lite5GCProxy notifies the AMF of the changed MM subscription data;

[0156] (4-3-5) The AMF sends a response to the UE accepting the registration.

[0157] In an optional embodiment of the present invention, after step 23, the method further includes:

[0158] Steps 23-14: Receive the request to obtain the second contract data sent by the third network element, and return the cached second contract data to the third network element;

[0159] Steps 23-15: Establish protocol data unit session bearer through the third network element;

[0160] Step 23-16: Receive the updated protocol data unit session information from the third network element.

[0161] This embodiment describes the process of establishing a PDU session when the network status is abnormal. The terminal sends a Protocol Data Unit Session Request to the second network element, which forwards the request to the third network element. The third network element sends a second subscription data request to the first network element. The first network element determines the current network status, and if the network status is abnormal, it sends the cached second subscription data of the terminal to the third network element. The third network element controls the fourth network element and interacts with the second network element to establish a Protocol Data Unit Session bearer for the terminal. The third network element updates the terminal's Protocol Data Unit Session information to the second network through the first network element.

[0162] Figure 11 This illustrates a flowchart of establishing a PDU session when the network status is abnormal in a specific embodiment 5 provided by the present invention; as shown below. Figure 11 As shown in a specific embodiment 5, when the network status is normal, the private network includes a UE terminal, a gNB base station, a lightweight 5G core network proxy server Lite5GCProxy, an access and mobility management function (AMF), and a session management function (SMF). The process for establishing a PDU session specifically includes:

[0163] (5-1) The terminal UE sends a Protocol Data Unit (PDU) session establishment request to the AMF;

[0164] (5-2) The AMF sends a Protocol Data Unit (PDU) session establishment request to the SMF;

[0165] (5-3) SMF sends an SM subscription data request to Lite 5GC Proxy;

[0166] (5-4) Lite 5GC Proxy judges the current network status. When it detects that the AUSF / UDM link to which the terminal UE belongs is abnormal or that the AUSF / UDM is unavailable, Lite 5GC Proxy determines to start the abnormal handling mechanism.

[0167] (5-5) Lite 5GC Proxy returns the SM subscription data cached during pre-registration to SMF;

[0168] (5-6) The SMF controls the UPF and completes relevant interactions with the AMF to establish a PDU bearer for the terminal UE;

[0169] (5-7) SMF updates the UE's PDU session information to Lite 5GC Proxy.

[0170] The embodiments of the present invention initiate a pre-registration process for terminals that have not been powered on and registered to a second network; receive the subscription data of the terminals that have not been powered on and registered from the second network; and initiate a power-on registration process for the terminals based on their network status; thereby enabling normal service to be used when there is a link failure in the campus network and the home network.

[0171] Figure 12 A schematic diagram of the terminal power-on registration device provided in an embodiment of the present invention is shown. Figure 12 As shown, the device 120 includes:

[0172] The transceiver module 121 is used to initiate a pre-registration process for terminals that have not been powered on and registered to the second network; and to receive the subscription data of the terminals that have not been powered on and registered from the second network.

[0173] The processing module 122 is used to initiate the power-on registration process of the terminal based on the network status of the terminal.

[0174] Optionally, a pre-registration process is initiated with the second network for terminals that are not yet powered on and registered, including:

[0175] Based on the preset activation time of the pre-registration process and the pre-configured terminal information of the unregistered terminal, the pre-registration process for the unregistered terminal is initiated to the second network.

[0176] Optionally, receiving and saving the subscription data of the unregistered terminal fed back by the second network includes:

[0177] Send an authentication request to the second network for the terminal that has not been powered on and registered;

[0178] Receive authentication vector data fed back by the second network in accordance with the authentication request;

[0179] Send a registration request from the terminal that has not been powered on and registered to the second network;

[0180] Receive a registration success message from the second network based on the registration request;

[0181] Send the first subscription data request of the terminal that has not been powered on and registered to the second network;

[0182] Receive the first signing data fed back by the second network based on the signing data request;

[0183] Send a second subscription data request to the second network for the terminal that has not been powered on and registered;

[0184] Receive the second contract data that the second network has requested in response to the contract data request.

[0185] Optionally, based on the network status of the terminal, initiate the power-on registration process for the terminal, including:

[0186] When the network status of the terminal is normal, delete the cached authentication vector data of the terminal and initiate an authentication process request to the second network.

[0187] The terminal's subscription data is deleted, and a second network element selection process is initiated to the second network. The second network element requests and subscribes to the network slice identifier provided by the terminal to obtain the terminal's second network element selection result.

[0188] The first subscription data of the terminal is deleted, registration is initiated to the terminal, and the second network element sends a registration response to the terminal.

[0189] Optionally, after initiating the power-on registration process for the terminal based on its network status, the process further includes:

[0190] Forward the protocol data unit session request of the third network element to the second network, delete the cached second subscription data of the terminal, and receive the latest second subscription data fed back by the second network;

[0191] The latest second contract data is forwarded to the third network element, and a protocol data unit session bearer is established through the third network element;

[0192] Update the protocol data unit session information of the third network element to the second network.

[0193] Optionally, based on the network status of the terminal, initiate the power-on registration process for the terminal, including:

[0194] When the network status of the terminal is abnormal, it receives the authentication vector request initiated by the second network element and sends the cached authentication vector data of the terminal to the second network element.

[0195] The system receives the return value fed back by the second network element based on the authentication vector data, and compares the return value with the pre-generated expected user response value to obtain the authentication result.

[0196] Receive the network slice subscription data download request initiated by the second network element, and provide the second network element with the terminal's subscribed network slice identifier;

[0197] The second network element obtains the selection result of the terminal's second network element based on the network slice identifier request provided by the terminal and the subscribed network slice identifier;

[0198] Receive the registration request initiated by the second network element and return a registration success message to the second network element;

[0199] Receive the request to acquire the second network element's contract data, and send the first contract data back to the second network element;

[0200] The second network element sends a registration response to the terminal.

[0201] Optionally, after initiating the power-on registration process for the terminal based on its network status, the process includes:

[0202] Receive the request to obtain the second contract data sent by the third network element, and return the cached second contract data to the third network element;

[0203] Establish protocol data unit session bearers through third network elements;

[0204] Receive protocol data unit session information updated by the third network element.

[0205] It should be noted that this device is the same as the method described above. All implementations in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effect.

[0206] This invention provides a non-volatile computer storage medium storing at least one executable instruction that can execute the terminal boot registration method in any of the above method embodiments.

[0207] Figure 13 The diagram shows a structural schematic of a computing device provided in an embodiment of the present invention. The specific embodiments of the present invention do not limit the specific implementation of the computing device.

[0208] like Figure 13 As shown, the computing device may include a processor, a communications interface, memory, and a communications bus.

[0209] The processor, communication interface, and memory communicate with each other via a communication bus. The communication interface is used to communicate with other network elements, such as clients or other servers. The processor executes programs, specifically the relevant steps in the above-described embodiment of the power-on registration method for a computing device terminal.

[0210] Specifically, the program may include program code, which includes computer operation instructions.

[0211] The processor may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The computing device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0212] Memory is used to store programs. Memory may include high-speed RAM, and may also include non-volatile memory, such as at least one disk drive.

[0213] Specifically, the program can be used to cause the processor to execute the terminal power-on registration method in any of the above method embodiments. The specific implementation of each step in the program can be found in the corresponding descriptions of the steps and units in the above terminal power-on registration method embodiments, and will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.

[0214] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, the embodiments of the present invention are not directed to any particular programming language. It should be understood that the embodiments of the present invention described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of the embodiments of the present invention.

[0215] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0216] Similarly, it should be understood that, in order to streamline the embodiments of the invention and aid in understanding one or more of the various inventive aspects, features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof in the above description of exemplary embodiments of the invention. However, this disclosure should not be construed as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0217] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0218] Furthermore, those skilled in the art will understand that although some embodiments herein include certain features included in other embodiments but not others, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0219] The various component embodiments of the present invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The embodiments of the present invention can also be implemented as device or apparatus programs (e.g., computer programs and computer program products) for performing part or all of the methods described herein. Such programs implementing the embodiments of the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0220] It should be noted that the above embodiments are illustrative of the present invention and not restrictive of the invention, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Embodiments of the present invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. A method for powering on and registering a terminal, characterized in that, The method, applied to a first network element of a first network, includes: Initiate a pre-registration process for terminals that are not yet powered on and registered to the second network; Receive the subscription data of the terminal that has not been powered on and registered, fed back from the second network; Based on the terminal's network status, the system initiates the terminal's power-on registration process. Specifically, when the terminal's network status is abnormal, the system receives an authentication vector request initiated by a second network element and sends the cached authentication vector data of the terminal to the second network element. It receives a return value from the second network element based on the authentication vector data and compares the return value with a pre-generated expected user response value to obtain an authentication result. The system also receives a request from the second network element to download network slice subscription data and provides the second network element with the terminal's subscribed network slice identifier. The second network element, based on the network slice identifier request provided by the terminal and the subscribed network slice identifier, obtains the terminal's selection result from the second network element. The system receives a registration request from the second network element and returns a registration success message to the second network element. It also receives a first subscription data request sent by the second network element and returns the first subscription data to the second network element. Finally, the second network element sends a registration acceptance response to the terminal.

2. The terminal power-on registration method according to claim 1, characterized in that, The pre-registration process for terminals that are not yet powered on and registered is initiated to the second network, including: Based on the preset activation time of the pre-registration process and the pre-configured terminal information of the unregistered terminal, the pre-registration process for the unregistered terminal is initiated to the second network.

3. The terminal power-on registration method according to claim 1, characterized in that, Receive and save the subscription data of the unregistered terminal fed back by the second network, including: Send an authentication request to the second network for the terminal that has not been powered on and registered; Receive authentication vector data fed back by the second network in accordance with the authentication request; Send a registration request from the terminal that has not been powered on and registered to the second network; Receive a registration success message from the second network based on the registration request; Send the first subscription data request of the terminal that has not been powered on and registered to the second network; Receive the first signing data fed back by the second network based on the signing data request; Send a second subscription data request to the second network for the terminal that has not been powered on and registered; Receive the second contract data that the second network has requested in response to the contract data request.

4. The terminal power-on registration method according to claim 3, characterized in that, Based on the network status of the terminal, initiate the power-on registration process for the terminal, including: When the network status of the terminal is normal, delete the cached authentication vector data of the terminal and initiate an authentication process request to the second network. The terminal's subscription data is deleted, and a second network element selection process is initiated to the second network. The second network element requests and subscribes to the network slice identifier provided by the terminal to obtain the terminal's second network element selection result. The terminal's first subscription data is deleted, and a registration is initiated with the second network. The second network element then sends a registration response to the terminal.

5. The terminal power-on registration method according to claim 4, characterized in that, After initiating the power-on registration process for the terminal based on its network status, the process further includes: Forward the protocol data unit session request of the third network element to the second network, delete the cached second subscription data of the terminal, and receive the latest second subscription data fed back by the second network; The latest second contract data is forwarded to the third network element, and a protocol data unit session bearer is established through the third network element; Update the protocol data unit session information of the third network element to the second network.

6. The terminal power-on registration method according to claim 1, characterized in that, After initiating the power-on registration process for the terminal based on its network status, the process further includes: Receive the request to obtain the second contract data sent by the third network element, and return the cached second contract data to the third network element; Establish protocol data unit session bearers through third network elements; Receive protocol data unit session information updated by the third network element.

7. A terminal power-on registration device, characterized in that, The device, applied to a first network element of a first network, includes: The transceiver module is used to initiate a pre-registration process for terminals that have not been powered on and registered to the second network; and to receive the subscription data of the terminals that have not been powered on and registered from the second network. The processing module is used to initiate the power-on registration process of the terminal based on the terminal's network status. Specifically, when the terminal's network status is abnormal, the module receives an authentication vector request initiated by a second network element and sends the cached authentication vector data of the terminal to the second network element; receives a return value from the second network element based on the authentication vector data and compares the return value with a pre-generated expected user response value to obtain an authentication result; receives a request to download network slice subscription data initiated by the second network element and provides the second network element with the terminal's subscribed network slice identifier; the second network element obtains the terminal's selection result based on the network slice identifier request provided by the terminal and the subscribed network slice identifier; receives a registration request initiated by the second network element and returns a registration success message to the second network element; receives a first subscription data request sent by the second network element and returns the first subscription data to the second network element; and the second network element sends a registration response to the terminal.

8. A computing device, comprising: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the power-on registration method of the terminal as described in any one of claims 1-6.

9. A computer storage medium storing at least one executable instruction that causes a processor to perform an operation corresponding to the power-on registration method of a terminal as described in any one of claims 1-6.

Images