Wireless communication method and device, communication equipment, medium and program product

Abstract

The invention provides a wireless communication method and device, communication equipment, a medium and a program product, relates to the technical field of communication, and is used for improving the service continuity of user equipment. The method comprises the following steps: a first AMF sends a query request to a guarantee server under the condition of determining that a main network has a fault; the AMF receives a query response from the guarantee server, wherein the query response carries user information of at least one piece of first UE; the AMF performs first access processing on the at least one first UE based on the user information, and performs second access processing on the at least one second UE; wherein the first access processing comprises the following steps of: immediately starting a flow of accessing at least one first UE to a backup network of the main network; or immediately responding to the access request of at least one first UE; the second access processing comprises the following steps of: delaying to start a flow of accessing at least one second UE to the backup network; or delaying the response to the access request of at least one second UE. The method is applied to a network disaster recovery scene.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to wireless communication methods, apparatus, communication equipment, media and program products. Background Technology

[0002] In 5G cloud-based core networks, disaster recovery is typically achieved through backup methods such as load sharing between network elements (POOL) and 1+1 mutual backup. When a single network element fails, the disaster recovery mechanism enables rapid service recovery.

[0003] In related technologies, operator core network equipment is often deployed in a multi-data center (DC) configuration across large regions, with different DCs within the same region forming a disaster recovery backup relationship. When the primary DC fails, the network switches to network elements on the backup DC to continue providing services. However, during disaster recovery failover, if the fault area is large and there are too many users accessing the network, the backup network is prone to congestion, leading to extended access times for all users. This can result in some key users being unable to access the network in a timely manner, ultimately causing poor service continuity. Summary of the Invention

[0004] This application provides a wireless communication method, apparatus, communication device, medium, and program product for improving the service continuity of user equipment.

[0005] In a first aspect, this application provides a wireless communication method, comprising: a first AMF (Application-Managed Function) sending a query request to a backup server when it determines that a primary network has failed; the query request is used to obtain information of user equipment (UE) with a first access priority that has been pre-registered in the backup server; the first AMF is an AMF in a backup network of the primary network; the first AMF receives a query response from the backup server, the query response carrying user information of at least one first UE; the first AMF performs a first access process on the at least one first UE and a second access process on at least one second UE based on the user information; the at least one second UE is a UE other than the at least one first UE among the UEs that the backup network needs to provide services to; wherein the first access process includes: immediately initiating a process for the at least one first UE to access the backup network; or immediately responding to an access request from the at least one first UE; the second access process includes: delaying the initiation of a process for the at least one second UE to access the backup network; or delaying the response to an access request from the at least one second UE.

[0006] The technical solution provided in this application brings at least the following beneficial effects: In the wireless communication method provided in this application, after determining that the primary network has failed, the AMF first sends a query request to the support server to obtain the user equipment that needs priority access; upon receiving a query response containing user information of the first UE, it performs a first access process on the first UE and a second access process on the second UE. Through this solution, by querying and generating policies through the support server, accurate identification and differentiated scheduling of key users are achieved, ensuring the service continuity of critical business users; secondly, by introducing access control, the access process for at least one first UE requiring priority access is immediately initiated, while the access process for other UEs is delayed, realizing the construction of a priority channel for resource allocation. This effectively avoids network congestion caused by disorderly competition for resources among all users in the early stages of disaster recovery, improving the stability of the core network and the orderly nature of service recovery under extreme failures; by triggering process switching under preset conditions, while prioritizing the service continuity of key users, the access fairness of ordinary users is also taken into account, thereby optimizing the overall service continuity of user equipment.

[0007] One possible implementation is that the above-mentioned delayed start of the access procedure for the at least one second UE includes: under the condition that preset conditions are met, the first AMF starts the access procedure for the at least one second UE; wherein the preset conditions include at least one of the following: the service of the at least one first UE has been restored; the time elapsed since the start of the access procedure for the at least one target UE exceeds a preset waiting time.

[0008] Another possible implementation, wherein the user information mentioned above includes a user identifier and a protection level; the first AMF immediately initiates the process for the at least one first UE to access the backup network of the primary network, including: the first AMF determining an access control policy based on the user information; the first AMF immediately initiating the access process for the at least one first UE to access the backup network based on the access control policy; wherein the access control policy includes the access timing and network resource allocation policy of the at least one first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources, and computing resources.

[0009] Another possible implementation is that the first AMF immediately initiates the process for the at least one first UE to access the backup network of the primary network, including: the first AMF sending a paging indication to the radio access network (RAN) for the at least one first UE, the paging indication containing priority level indication information, the paging indication being used to trigger the RAN to process the paging of the at least one first UE; or, the first AMF sending a non-access stratum (NAS) message to the at least one first UE, the NAS message containing a first indication, the first indication being used to instruct immediate re-registration, the NAS message being used to instruct the at least one first UE to initiate a registration process with the backup network.

[0010] Another possible implementation, wherein the access procedure for the at least one second UE is initiated when the preset conditions are met, includes: the first AMF determining that the service recovery of the at least one first UE is complete when it receives registration completion confirmation messages or first service request messages from all first UEs; and the first AMF initiating the access procedure for the at least one second UE when it determines that the service recovery of the at least one first UE is complete.

[0011] Secondly, this application provides a wireless communication method, comprising: a protection server receiving a query request from a first AMF; the query request being used to obtain information of a user equipment (UE) with a first access priority that has been pre-registered in the protection server; the protection server sending a query response to the first AMF, the query response carrying user information of at least one first UE; wherein the protection server has pre-registered user information of at least one UE with a first access priority.

[0012] The wireless communication method provided in this application, by introducing and deploying an independent backup server, constructs a centralized and precise user priority management and response system, fundamentally solving the problem of existing disaster recovery technologies being unable to provide differentiated services and rapid identification for users. First, the server dynamically aggregates and maintains real-time information on high-priority users (with first access priority) across the entire network through a pre-registration mechanism, forming a global priority view for disaster recovery scenarios. This allows the backup network to quickly and accurately identify the affected key user groups at the outset of a failure, avoiding the processing latency and resource consumption caused by real-time identification in massive access requests. Second, this design decouples the execution of user priority policies from the core network service processing logic. The backup server acts as a lightweight policy data provider, not intervening in specific signaling processes, thereby achieving fine-grained control while ensuring the original processing performance and architectural stability of the core network. Ultimately, this mechanism transforms the network disaster recovery process from a crude takeover focused on network elements and connections to an intelligent scheduling focused on user and service value. It ensures that in extreme failure scenarios, limited recovery resources can be prioritized and used efficiently to guarantee the service continuity of the most important users, significantly improving the reliability of the operator's network, its ability to fulfill service level agreements, and customer experience.

[0013] In one possible implementation, before the assurance server receives a query request from the first AMF, the method further includes: the assurance server receiving a registration request from a second AMF; wherein the registration request is used to register the user information of the at least one first UE to the assurance server, and the user information includes a user identifier and an assurance level; the second AMF is an AMF in the primary network.

[0014] Thirdly, this application provides a wireless communication device, comprising: a transmitting module, a receiving module, and an executing module, wherein: the transmitting module is configured to send a query request to a backup server when a failure is determined in the primary network; the query request is used to obtain information of user equipment (UE) with a first access priority that is pre-registered in the backup server; the receiving module is configured to receive a query response from the backup server, the query response carrying user information of at least one first UE; the executing module is configured to perform a first access process on the at least one first UE and a second access process on at least one second UE based on the user information; the at least one second UE is a UE other than the at least one first UE among the UEs that the backup network needs to provide services to; wherein the first access process includes: immediately initiating a process for the at least one first UE to access the backup network of the primary network; or, immediately responding to the access request of the at least one first UE; the second access process includes: delaying the initiation of a process for the at least one second UE to access the backup network; or, delaying the response to the access request of the at least one second UE.

[0015] In one possible implementation, in some embodiments, the above-mentioned execution module is specifically used to initiate an access process for at least one second UE when preset conditions are met. The preset conditions include at least one of the following: at least one first UE service has been restored; the time elapsed since the start of the access procedure for at least one target UE exceeds the preset waiting time.

[0016] Another possible implementation is that the aforementioned user information includes a user identifier and a protection level; the aforementioned execution module is specifically used for the first AMF to determine an access control policy based on the user information; and based on the access control policy, to immediately initiate an access procedure for at least one first UE to access the backup network; wherein, the access control policy includes an access timing and network resource allocation policy for at least one first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources, and computing resources.

[0017] Another possible implementation is that the aforementioned execution module is specifically used to send a paging indication to the Radio Access Network (RAN) for at least one first UE, the paging indication containing priority level indication information, the paging indication being used to trigger the RAN to process the paging of at least one first UE; or, to send a Non-Access Stratum (NAS) message to at least one first UE, the NAS message containing a first indication, the first indication being used to instruct immediate re-registration, the NAS message being used to instruct at least one first UE to initiate a registration process to the backup network.

[0018] Another possible implementation is that the above-mentioned execution module is specifically used to determine that at least one first UE has completed service recovery upon receiving registration completion confirmation messages or first service request messages from all first UEs; and to initiate an access process for at least one second UE upon determining that at least one first UE has completed service recovery.

[0019] Fourthly, this application provides a wireless communication device, comprising: a receiving module and a transmitting module, wherein: the receiving module is configured to receive a query request from a first AMF; the query request is configured to obtain information of a user equipment (UE) with a first access priority that has been pre-registered in a security server; the transmitting module is configured to send a query response to the first AMF, the query response carrying user information of at least one first UE; wherein the security server has pre-registered user information of at least one UE with a first access priority.

[0020] In one possible implementation, the receiving module is further configured to receive a registration request from a second AMF. The registration request is used to register user information of at least one first UE to the protection server. The user information includes a user identifier and a protection level.

[0021] Fifthly, this application provides an electronic device, which can be a communication device; the electronic device includes: a processor and a memory; the memory stores instructions executable by the processor; when the processor is configured to execute the instructions, the electronic device implements the methods of the first or second aspect described above.

[0022] In a sixth aspect, this application provides a computer-readable storage medium comprising: computer software instructions; which, when executed in an electronic device, cause the electronic device to implement the methods described in the first or second aspect.

[0023] In a seventh aspect, this application provides a computer program product comprising a computer program; when the computer program is run in an electronic device, the electronic device causes the electronic device to implement the methods of the first or second aspect described above.

[0024] The beneficial effects of the second to seventh aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description

[0025] Figure 1A A schematic diagram illustrating the application environment of a wireless communication method provided in an embodiment of this application; Figure 1B A schematic diagram of the architecture of a network disaster recovery system provided in this application embodiment; Figure 2A flowchart illustrating a wireless communication method provided in an embodiment of this application; Figure 3 A flowchart illustrating another wireless communication method provided in an embodiment of this application; Figure 4A A flowchart illustrating the process by which the AMF registers UE information with the support server in a wireless communication method provided in this application embodiment; Figure 4B A flowchart illustrating the process by which the AMF registers user information of at least one first UE with the protection server, as provided in this embodiment of the application; Figure 5 A flowchart illustrating another wireless communication method provided in an embodiment of this application; Figure 6 A flowchart illustrating another wireless communication method provided in an embodiment of this application; Figure 7 A system architecture diagram of a wireless communication system provided in this application embodiment; Figure 8 This is a schematic diagram of the structure of a wireless communication device provided in an embodiment of this application; Figure 9 This is a schematic diagram of another wireless communication device provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] The wireless communication methods, apparatus, communication devices, media, and program products provided in this application will now be described in detail with reference to the accompanying drawings.

[0027] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0028] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0029] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0030] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0031] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.

[0032] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0033] The 5G cloud-based core network supports different backup methods such as load sharing (POOL) and 1+1 mutual backup. The appropriate backup and disaster recovery method is determined based on the network element type. When a single network element fails, the network element's disaster recovery mechanism is fully utilized to achieve rapid service recovery across network elements. With the deployment of hot standby functionality in AMF / MME, SMF / GW-C, and UPF / GW-U network elements, takeover efficiency is further improved, enabling smooth takeover without terminal reconnection.

[0034] Currently, most operators deploy 4G / 5G core network equipment using a multi-datacenter (DC) architecture across large regions, with different DCs within the same region forming a disaster recovery backup. When a network element or all devices in a DC fail, the network switches to the network elements on the backup DC to continue providing services to users. Generally, during the switchover process, if the fault affects a large area or there are too many users accessing the network, congestion may occur on the backup network. This forces the network to activate congestion control, resulting in longer access times for some users and causing a period of unavailability of the operator's network.

[0035] Currently, disaster recovery and congestion control cannot achieve user classification management, and key users or whitelisted users cannot quickly restore their services during the disaster recovery process.

[0036] The wireless communication method provided in this application can be applied to scenarios where service disaster recovery is performed after a core network failure.

[0037] For example, the embodiments of this application can be applied to 4G / 5G core networks deployed using a regional multi-datacenter (DC) approach. In this scenario, different DCs within the same region form a primary / backup disaster recovery relationship. When the primary DC fails, services need to be switched to the backup DC to provide continuous service to users.

[0038] In existing technologies, disaster recovery and failover processes typically employ a uniform access handling strategy for all User Equipment (UEs). When the fault scope is large and the number of UEs needing to access the backup DC is too high, the access network elements (such as AMF) of the backup DC may face signaling storms and resource congestion, forcing the activation of congestion control mechanisms. This results in delays in the access process for all UEs, extending service recovery time.

[0039] Thus, existing technologies cannot provide differentiated services to users during disaster recovery, especially failing to guarantee service continuity for high-priority users (such as key users, users with high service level agreements (SLAs), or emergency communication users). In the event of backup network congestion, high-priority users face the same access latency as ordinary users, and their critical services cannot be quickly restored.

[0040] To address the aforementioned technical problems, this application provides a wireless communication method, apparatus, communication device, medium, and program product.

[0041] The embodiments provided in this application will now be described in detail with reference to the accompanying drawings.

[0042] Figure 1A This is a schematic diagram illustrating an application environment for a wireless communication method provided in an embodiment of this application. The wireless communication method provided in this application can be applied to, for example... Figure 1A The application environment shown in Figure 1 includes a wireless communication device 101 and a front-end device 102. The wireless communication device 101 and the front-end device 102 are interconnected.

[0043] In some embodiments, the wireless communication device 101 may be a server cluster consisting of multiple servers, a single server, a computer, or a processor or processing chip in a server or computer, etc. This application does not limit the specific device form of the wireless communication device 101. Figure 1A The example shown is a single server using wireless communication device 101.

[0044] In some embodiments, the front-end device 102 can be a device with wireless transceiver capabilities, such as a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. This application embodiment does not limit the specific device form of the front-end device 102. Figure 1A The example shown is a mobile phone, with the front-end device 102 as the illustration.

[0045] In some embodiments, after determining that the primary network (or primary data center) has failed, the wireless communication device 101 executes the disaster recovery processing method provided in this application embodiment. For example, when determining that the primary network has failed, the wireless communication device 101 sends a query request to the support server; the query request is used to obtain information about user equipment (UE) with a first access priority that has been pre-registered in the support server; the AMF receives a query response from the support server, the query response carrying user information of at least one high-priority front-end device 102; based on the user information, the wireless communication device 101 performs a first access process on at least one front-end device 102 and a second access process on at least one ordinary-priority front-end device; the at least one ordinary-priority front-end device is a front-end device other than at least one high-priority front-end device among the front-end devices that the backup network needs to provide services to; wherein, the first access process includes: immediately initiating the process of at least one high-priority front-end device accessing the backup network of the primary network; or, immediately responding to the access request of at least one high-priority front-end device; the second access process includes: delaying the initiation of the process of at least one ordinary-priority front-end device accessing the backup network; or, delaying the response to the access request of at least one ordinary-priority front-end device.

[0046] It should be noted that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0047] Figure 1B This is a schematic diagram of the architecture of a network disaster recovery system provided in an embodiment of this application. Figure 1BAs shown, the system is deployed within a single region, employing a dual-datacenter disaster recovery architecture with mutual backup, and incorporating a backup server to prioritize and protect users. This architecture primarily includes the following components: (1) Data Centers (DC1 and DC2): Among them, DC1 (primary data center) and DC2 (backup data center) are mirrored backups, meaning that the two maintain synchronization or near real-time synchronization in terms of network functions and user data. If either data center fails, the other data center can take over all or part of the business, achieving disaster recovery in a different location.

[0048] For example, each data center deploys a complete set of core network control plane elements, including: AMF (Access and Mobility Management Function): responsible for terminal access, mobility management, and registration processes; SMF (Session Management Function): responsible for the establishment, modification, and release of user plane sessions; UPF (User Plane Function): responsible for data packet forwarding, located on the access province side, and can actually be deployed across data centers or configured by region; UDM (Unified Data Management): stores user subscription data and identity identifiers; PCF (Policy Control Function): provides policy rules to guide AMF and SMF in performing priority control; NRF (Network Storage Function): supports network element service registration and discovery; NSSF (Network Slice Selection Function): assists in selecting network slice instances; NEF (Network Open Function): supports capability opening and interaction with external systems.

[0049] (2) Safeguard server (i.e., safeguard access server): The protection server, as a newly introduced independent network element in this application, does not belong to any data center and is typically deployed at the regional level, accessible to both DC1 and DC2. Its core functions are: during initial user registration, receiving and storing user identifiers and protection level information from the AMF; and during disaster recovery failover, receiving query requests from the AMF in the backup DC, returning a list of registered high-priority users, and providing a basis for differentiated access control.

[0050] It should be noted that the guarantee server in this application embodiment can be replaced by a guarantee access server.

[0051] (3) Access Province This represents the area where the wireless network accessed by the terminal is located and the User Plane Gateway (UPF). As a data forwarding anchor point, the UPF can be deployed in the access province as needed and collaborate with the Control Plane Network Element (SMF) across domains.

[0052] The following is an overview of the working logic of the above architecture: For example, during normal operation: the user terminal accesses DC1 (primary DC) through the access province. After the AMF completes user registration, if it identifies that the user has a high protection level, it will register the user's information to the protection server.

[0053] For example, when disaster recovery is triggered: when DC1 fails, before starting the disaster recovery process, the AMF of DC2 first queries the protection server for the list of users who need to be prioritized for access.

[0054] For example, based on the query results, DC2 prioritizes fast access for high-priority users and postpones or delays access for ordinary users, thereby ensuring the business continuity of key users in congested scenarios.

[0055] It should be noted that this architecture is applicable to communication systems that require high reliability and service tier guarantees, such as 5G cloud-based core networks and IMS networks.

[0056] See Figure 2 This is a flowchart illustrating a wireless communication method provided in an embodiment of this application. Figure 2 As shown, the wireless communication method provided in this application specifically includes the following steps 201 to 205.

[0057] Step 201: If the first AMF determines that the primary network has failed, it sends a query request to the support server.

[0058] The aforementioned query request is used to obtain information about user equipment (UE) that has been pre-registered in the security server and has the first access priority.

[0059] In some embodiments of this application, the primary network and the backup network constitute a disaster recovery relationship, such as the same set of core network function instances deployed in different data centers (DCs).

[0060] In some embodiments of this application, the first AMF mentioned above is the AMF in the backup network. Determining that the primary network has failed can be achieved through mechanisms such as service status discovery of the Network Storage Function (NRF), heartbeat detection timeout between the primary network element and the network storage function, or receiving fault notifications from the operation and maintenance management system.

[0061] In some embodiments of this application, the aforementioned protection server is a functional entity or service platform deployed independently of the core network service plane, used to provide user priority identification services in disaster recovery scenarios. It stores information on user equipment actively registered by the network side (such as the AMF) and marked as having high priority during normal network operation. "First access priority" is relative to ordinary priority (or default priority) and is used to identify user groups that need priority access protection in resource-constrained or fault recovery scenarios, such as VIP customers, IoT devices undertaking critical tasks (such as emergency communication vehicles), or users who have signed high-level service agreements (SLAs).

[0062] For example, in the 5G core network, the primary data center DC1 experiences a complete outage due to a power failure. The AMF (Active Network Provider) of the backup data center DC2 detects through NRF (Network Response Function) that all network element instances in DC1 have become unavailable, thus determining that the primary network has failed. Subsequently, the AMF of DC2 sends a query request to the independently deployed backup server, requesting to obtain a list of all users pre-registered on the server with the highest priority.

[0063] Step 202: Ensure the server receives query requests from the first AMF.

[0064] Among them, the aforementioned security server pre-registered user information of at least one UE with the first access priority.

[0065] In some embodiments of this application, if there are registered high-priority users in the security server, the information of these users will be returned in the query response.

[0066] In some embodiments of this application, the aforementioned user information includes at least an identifier that can uniquely identify the user (such as SUPI, MSISDN), and may also include information such as the user's specific protection level and subscription priority policy identifier. If no such user exists, the response may be empty or carry a specific instruction.

[0067] For example, after querying the local database, the assurance server finds that there are currently 100 critical assurance users registered in this fault zone. The assurance server encapsulates the SUPI and assurance level "Platinum" of these users in the query response and sends it to the AMF of DC2.

[0068] Step 203: Ensure the server sends a query response to the first AMF.

[0069] The query response mentioned above carries user information of at least one first UE.

[0070] Step 204: The first AMF receives the query response from the assurance server.

[0071] Step 205: Based on the above user information, the first AMF performs a first access process on at least one first UE and a second access process on at least one second UE.

[0072] Among them, at least one second UE is a UE other than at least one first UE among the UEs that the backup network needs to provide services for.

[0073] In some embodiments of this application, the first access process described above includes: immediately initiating a process for at least one first UE to access the backup network of the primary network; or, immediately responding to the access request of at least one first UE.

[0074] In some embodiments of this application, the second access process includes: delaying the initiation of a process for at least one second UE to access the backup network; or delaying the response to an access request from at least one second UE.

[0075] In some embodiments of this application, the first AMF divides the users to be accessed into two groups based on the received user information: a first UE (i.e., high-priority users or users requiring special protection) and a second UE (i.e., other ordinary users). Subsequently, different access control logic is executed for these two groups.

[0076] It should be noted that the first access processing and the second access processing differ in terms of access timeliness and resource guarantee. This processing is a network control behavior actively implemented on the AMF side, rather than depending on the UE's request order.

[0077] For example, DC2's AMF identifies 100 UEs as the first UE group based on the received list of 100 users requiring priority protection (SUPI). Simultaneously, hundreds of thousands of ordinary users are expected to need to access DC2 from the faulty area; these users are identified as the second UE group. The AMF will initiate different processing procedures for these two groups.

[0078] In some embodiments of this application, during the initial stage of disaster recovery and failover, the AMF takes proactive measures to guide or trigger the access process of these first UEs without waiting for them to initiate access requests, such as proactively initiating paging.

[0079] In some embodiments of this application, when the first UE actively initiates an access request (such as a registration request), the AMF processes it before the second UE's request, for example, by placing it in a high-priority processing queue. Both methods can achieve rapid service recovery for the first UE.

[0080] In some embodiments of this application, the AMF does not actively trigger access from ordinary users, for example, by not processing their paging or delaying related processes for a period of time.

[0081] In some embodiments of this application, when an access request from a regular user arrives, the AMF intentionally extends its processing time, places it in a low-priority queue to wait, or temporarily rejects the request and asks it to retry later. The purpose is to free up and reserve sufficient network processing resources (such as signaling processing capacity and transmission resources) for the access of the first UE, and to avoid signaling storms causing delays or blockages in the access of all users (including high-priority users).

[0082] For example, for the first 100 UEs, the AMF immediately contacts these UEs proactively through a paging process, triggering them to register with DC2. At the same time, for the registration requests from the second UEs that begin to flood in, the AMF temporarily caches them in a delayed processing queue, without immediately performing the core authentication and registration process.

[0083] The following example illustrates the wireless communication method provided in this application through a core network cross-data center disaster recovery scenario.

[0084] For example, suppose 5GC core networks are deployed in two geographically different data centers (DC1 and DC2) to form a mutual backup. A natural disaster occurs in the city where DC1 is located, causing the entire data center to fail. DC2's AMF (AMF-in-DC2) detects a heartbeat interruption with DC1, determines that the primary network has failed, and initiates disaster recovery failover. AMF-in-DC2 first sends a query request to the independently deployed key user protection platform (i.e., the protection server). The protection server returns a list of "emergency protection users" in the current failure area, including the identifiers of 50 emergency command vehicles and 5G CPE devices (first UEs) in important hospitals. Then, based on the list, AMF-in-DC2 immediately initiates emergency paging to these 50 first UEs via the wireless network and prioritizes their returned registration requests, quickly restoring their network connection. Simultaneously, millions of public users originally served by DC1 (second UEs) begin attempting to access DC2. AMF-in-DC2 delays the access requests of these users, for example, temporarily replying with "Network congestion, please try again later," or placing their signaling in a waiting queue.

[0085] Thus, despite limited resources in DC2, 50 critical first-time UEs had their services restored within minutes, ensuring uninterrupted emergency communication. Service restoration for public users proceeded systematically after the critical user support was completed.

[0086] This solution introduces a protection server to identify critical users and execute "immediate processing," opening a protected access channel for core user groups and fundamentally avoiding the problem of access failure during congestion. It achieves intelligent and differentiated scheduling of network resources in fault scenarios: this solution transforms the service layer concept of "user priority" into a network layer "access control policy." As the core of the control plane, AMF can dynamically determine the order of access processing and resource allocation based on externally input user information, ensuring that limited fault recovery resources are prioritized for protecting the most important services, improving the overall utilization efficiency and value of network resources. It enhances the service level agreement (SLA) assurance capabilities of operator networks: providing differentiated fault recovery services for high-value users or critical services is key to improving operator competitiveness and brand image. This solution provides a practical and automated technical means to fulfill high-level SLA commitments, ensuring the continuity of critical services even under extreme network failures.

[0087] In some embodiments of this application, the process of delaying the initiation of the access procedure for at least one second UE in step 205 above may include the following step A1: Step A1: If the preset conditions are met, the first AMF initiates the access procedure for at least one second UE.

[0088] The aforementioned preset conditions include at least one of the following: at least one first UE service has been restored; the elapsed time since the start of the access procedure for at least one target UE exceeds the preset waiting time.

[0089] In some embodiments of this application, the first AMF determines whether the preset conditions for initiating the access procedure for the second UE are met.

[0090] In some embodiments of this application, "at least one first UE service recovery completed" means that the first UE group has been successfully accepted by the backup network and the service channel is ready. Specific criteria for determination may include: all identified first UEs have completed the registration process on the backup network; or, all first UEs have successfully established at least one PDU session. This ensures that the priority protection objective has been substantially achieved.

[0091] For example, the AMF maintains a list of first UEs, and marks each successfully registered first UE in the list. When all first UEs in the list are in the "registered" or "attached" status, the service recovery of the first UEs is considered complete.

[0092] In some embodiments of this application, if the elapsed time from the initiation of the access procedure for at least one first UE exceeds a preset waiting time, this condition serves as a protection mechanism to prevent the entire process from being "stuck" due to individual first UEs failing to access the network due to terminal malfunctions, poor wireless environment, or other reasons. The aforementioned preset waiting time can be configured based on factors such as network policies and service tolerance, for example, 5 minutes or 10 minutes. After the timeout, regardless of whether all first UEs have recovered, processing of the second UE begins to balance the overall recovery progress.

[0093] For example, the preset waiting time is 8 minutes. The AMF starts timing after initiating paging of the first UE. After 8 minutes, even if two of the first UEs still fail to connect successfully, the AMF determines that the condition is met and begins processing the second UE.

[0094] It should be noted that the delayed processing of the second UE is not an indefinite suspension, but a controlled and temporary state. AMF needs to continuously monitor preset triggering conditions to determine when to end the delayed processing of the second UE and begin the normal disaster recovery access process. This ensures the effectiveness and timeliness of prioritizing the protection of the first UE, while avoiding excessively long service interruptions for the second UE due to excessive delays.

[0095] In some embodiments of this application, the AMF switches its operating mode when any of the above conditions are met. For previously delayed second UE access requests, the AMF begins to retrieve and process them from the buffer queue; for new second UE access requests, the AMF switches to normal response mode. At this time, the network enters a regular, non-differentiated disaster recovery phase.

[0096] For example, when the AMF detects that all 100 users requiring priority protection (the first UE) have completed registration, it immediately releases the delayed processing queue, begins to process the backlog of ordinary user (second UE) registration requests in sequence, and resumes normal response to new ordinary user access requests.

[0097] In this embodiment of the application, by setting conditions for switching from the priority protection phase to the full recovery phase, the network status is prevented from being in an atypical mode for a long time, a smooth and controllable transition of the disaster recovery phase is achieved, the thoroughness of priority protection is ensured, indefinite waiting due to individual anomalies is prevented, the rights of most ordinary users to restore their services within a reasonable time are protected, and a good balance is achieved between efficiency and fairness.

[0098] In some embodiments of this application, the aforementioned user information includes a user identifier and a protection level; exemplarily, the process in step 205 above, in which the first AMF immediately initiates the process of at least one first UE accessing the backup network of the primary network, may include the following steps B1 and B2: Step B1: The first AMF determines the access control policy based on user information.

[0099] Step B2: The first AMF immediately initiates the access procedure for at least one first UE to access the backup network based on the access control policy.

[0100] The access control strategy mentioned above includes at least one access timing and network resource allocation strategy for a first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources and computing resources.

[0101] In some embodiments of this application, the AMF formulates differentiated scheduling strategies, i.e., access control strategies, for its group based on protection level information.

[0102] For example, the protection levels can be: Level 1 - Emergency Communication, Level 2 - Important Customers, Level 3 - General Priority) which are used to perform secondary sorting and resource differentiation within the priority group.

[0103] For example, the user information received by the AMF includes 50 "Level 1 - Emergency" users and 50 "Level 2 - Gold" users. Based on this information, the AMF formulates a strategy: first access all "Level 1" users, and then access "Level 2" users; and during access, higher signaling processing bandwidth is reserved for "Level 1" users.

[0104] In some embodiments of this application, the first AMF executes the access procedure for the first UE according to the established strategy, so that even within the first UE group, the allocation of resources can reflect the difference in priority, and achieve hierarchical priority protection.

[0105] In some embodiments of this application, the above strategy includes the following: Strategy Content 1: Access Timing.

[0106] For example, the first UE with a higher protection level will be assigned an earlier access sequence. The AMF can trigger the access procedures of the first UEs of different levels in batches, in descending order of level. For example, in the first time window (such as the first 30 seconds), the AMF will only trigger paging for "Level 1" users; after the access requests of these users arrive and begin to be processed, paging for "Level 2" users will be triggered.

[0107] Strategy Content 2: Network Resource Allocation Strategy.

[0108] For example, the first UE with a higher protection level will be allocated higher priority network resources, including: Signaling processing resources: AMF's CPU, memory, etc., are reflected in its higher processing priority when handling signaling processes such as registration and session establishment.

[0109] Transmission bandwidth resources: bandwidth reservations or priority markings (such as higher QCI levels) for user plane (UPF) or N3 / N9 interfaces.

[0110] Computing resources: This refers to the computing power required for network data analysis, strategy decision-making, and other tasks.

[0111] For example, within the AMF, the highest processing priority is set for signaling messages of "Level 1" users to ensure that their registration process is not blocked by signaling from other users. Simultaneously, the SMF / UPF is notified to reserve bandwidth for the session that this user will be establishing.

[0112] In this embodiment, by binding the protection level with specific timing and resource policies, resource allocation becomes more data-driven, avoiding the internal unfairness or inefficiency that may result from a "one-size-fits-all" approach. Users at different levels receive differentiated services consistent with their commitments, improving the scientific nature and fairness of network resource scheduling.

[0113] In some embodiments of this application, the process of the first AMF immediately initiating the access of at least one first UE to the backup network of the primary network in step 205 above may include the following steps C1 and / or C2: Step C1: The first AMF sends a paging instruction to the radio access network RAN ​​for at least one first UE.

[0114] The paging indication includes priority level indication information and is used to trigger RAN processing of paging for at least one first UE.

[0115] Step C2: The first AMF sends a Non-Access Stratum (NAS) message to at least one first UE, the NAS message containing a first indication.

[0116] The first instruction mentioned above is used to instruct immediate re-registration, and the NAS message is used to instruct at least one first UE to initiate a registration process to the backup network.

[0117] In some implementations of this application, the first AMF actively triggers the first UE to access the backup network of the primary network through paging.

[0118] In some embodiments of this application, the first AMF generates a paging message (paging knowledge), which includes not only the identifier of the paged UE, but also priority level indication information (such as a priority bit or priority tag). This paging indication is sent to the RAN (gNB) in the area where the UE is located via the N2 interface. The priority level indication information is used to inform the RAN that this paging has high priority, and the RAN should prioritize scheduling and sending this paging message on the air interface, potentially preempting radio resources reserved for ordinary paging.

[0119] For example, the AMF sends a paging message to the RAN with the paging ID "VIP-User-001" and sets "priority: high" in the message extension field. Upon receiving the message, the RAN places it in the high-priority paging queue.

[0120] In some embodiments of this application, after receiving a paging message carrying a priority level indication, the RAN adjusts its air interface scheduling behavior according to the indication. For example, it may prioritize sending the paging message at the paging occupancy; or use a more reliable modulation and coding scheme (MCS); or broadcast a special indication in a system message to alert high-priority UEs to listen. When the first UE receives the paging message, it triggers a service request procedure to begin accessing the backup network.

[0121] For example, the RAN prioritizes paging "VIP-User-001" on the next available paging channel. Upon receiving this, the UE immediately initiates a service request, which is routed to the AMF of DC2, thereby beginning the registration process.

[0122] In some implementations of this application, the first AMF directly instructs the first UE to access the backup network of the primary network via NAS messages.

[0123] In some embodiments of this application, the first AMF constructs a downlink NAS message (e.g., “DL NAS TRANSPORT” or a specific “Configuration Update Command”) in which a first instruction (such as a specific cause value or information element) is embedded, which explicitly commands the UE to immediately perform re-registration to the current (backup) network or restore the connection.

[0124] For example, the AMF sends a NAS message to a first UE in an RRC-Inactive state via an existing N1 signaling connection, with the message carrying the "Registration Required" reason value.

[0125] In some embodiments of this application, the UE's NAS layer parses the message, identifies the "first instruction," and then follows the network command to proactively initiate a Registration Request process. Since this request is initiated by the UE after receiving a clear instruction, it has the highest degree of intent clarity and will be processed with priority by the AMF.

[0126] For example, after receiving the instruction, the NAS layer of the UE immediately triggers the RRC connection recovery and sends an RRC message carrying the registration type to the network, thereby initiating registration with DC2.

[0127] It should be noted that this method is applicable to scenarios where the AMF knows that the first UE has maintained a signaling connection with the network (such as being in RRC-Inactive or idle state but with context preserved).

[0128] In this embodiment, paging can provide a wider coverage, reaching all UEs in the powered-on state; NAS command method is precise and fast, suitable for existing associated UEs; or by transmitting priority indication from the core network to the radio access network, air interface resource scheduling is aligned with the core network guarantee strategy. This avoids the bottleneck problem of priority processing on the core network side, but delays on the air interface side due to resource contention, thus achieving end-to-end priority guarantee.

[0129] In some embodiments of this application, the wireless communication method provided in this application may further include steps 206 to 208: Step 206: The second AMF receives user subscription data from the UDM.

[0130] The aforementioned user subscription data includes user information for at least one first UE.

[0131] Step 207: The second AMF sends a registration request to the security server.

[0132] The aforementioned registration request is used to register the user information of at least one first UE to the security server.

[0133] Step 208: Ensure the server receives the registration request from the second AMF.

[0134] In some embodiments of this application, the aforementioned user information includes a user identifier and a protection level.

[0135] In some embodiments of this application, the second AMF is the AMF in the primary network.

[0136] It should be noted that this step describes the source and timing of high-priority user information. In a 5G network, the UDM is the authoritative database storing user subscription data. When a UE performs initial registration or periodic registration updates in a normal network (primary network), the AMF serving it will obtain the user's subscription data from the UDM through the Nudm_SDM_Get service.

[0137] In this embodiment, a protection level or priority identifier field is configured for a specific user in the UDM. This field, as part of the user's subscription data, is sent from the UDM to the AMF during the registration process.

[0138] For example, user A is a priority customer, and their UDM contract data is set to "servicePriority:Gold". When user A registers normally on DC1, the contract data obtained by DC1's AMF from the UDM will include the information "servicePriority: Gold".

[0139] In some embodiments of this application, when the AMF (the AMF in the primary network or the AMF in the backup network) obtains user subscription data containing a high-priority identifier from the UDM, it will proactively register the user's core identifier (such as SUPI) and protection level information to an independent protection server through a dedicated interface (such as N protection server_UEM_Register).

[0140] For example, after successfully completing the registration process for user A, AMF immediately sends a registration request to the protection server. The registration request carries user A's identification information and protection level, and the protection server stores this information in the database.

[0141] In this embodiment, when a user equipment registers with the UDM, the registration information of the user equipment that needs to be prioritized for protection is registered with the protection server to aggregate and query the user information of the users who need to be prioritized for protection. This enables the dynamic and accurate collection and registration of disaster recovery protection information, laying a solid data foundation for precise disaster recovery protection.

[0142] For example, in conjunction with the above Figure 2 ,like Figure 3 As shown, steps 206 to 208 can be performed before step 201.

[0143] It should be noted that steps 206 to 208 can also be executed after step 201. This application embodiment does not limit the timing of the execution of steps 206 to 208.

[0144] In some embodiments of this application, step A1 may include steps D1 and D2: Step D1: Upon receiving registration completion confirmation messages or first service request messages from all first UEs, the first AMF determines that at least one first UE has completed service recovery.

[0145] Step D2: If the first AMF determines that the service of at least one first UE has been restored, it initiates the access procedure for at least one second UE.

[0146] In some embodiments of this application, the registration completion confirmation message refers to the Registration Complete message, which is the UE's reply to the RegistrationAccept message sent by the AMF. This signifies that the control plane signaling process between the UE and the network has been fully established, and the UE has been formally accepted and its context rebuilt on the backup network side. When the AMF confirms that every UE in the first UE list obtained from the assurance server has completed this complete registration handshake, it can determine that the control plane recovery is complete.

[0147] For example, the AMF queries and finds that there are 10 initial UEs, and initiates and tracks the registration process of each of these 10 UEs one by one. When the "Registration Complete" message is received from the 10th UE, the condition is met.

[0148] In some embodiments of this application, the initial service request message refers to the "PDU Session Establishment Request" message sent by the UE after completing registration to establish a user plane connection. This signifies that the UE not only has a control plane ready but has also begun attempting to resume actual service data flow, making it an indicator closer to the essence of "service recovery." When the AMF receives initial service requests from all first UEs in the list, it can determine that the service recovery process has substantially started.

[0149] For example, among the 10 first UEs mentioned above, 8 initiated PDU session establishment requests immediately after registration, which were received by the AMF. For the remaining 2 UEs that may not have service needs temporarily, the AMF can make a comprehensive judgment by combining the timeout mechanism or by assuming that their service recovery (zero service) has been completed.

[0150] It should be noted that once the protection target of the first group of UEs is determined to have been achieved based on the above-mentioned clear criteria, the AMF will immediately perform a state switch, release resources, start processing the access request of the second UE, and enter the full recovery phase.

[0151] In this embodiment, the concept of service recovery completion is defined as a specific signaling event (registration completion or session establishment request) that can be accurately observed and counted by the network. This simplifies and makes the automated judgment logic of the AMF (Application Management Function) simple and reliable, avoiding the ambiguity and potential errors caused by manually defining "recovery," and providing clear and unambiguous criteria for determining service recovery completion. By requiring all first UEs to reach the predetermined state, this ensures that the priority protection strategy is executed without fail, eliminating the risk that the overall protection effect will be affected by the failure of individual users to recover, and ensuring the quality of priority protection.

[0152] The following describes a specific embodiment of the process by which the AMF registers UE information with the support server in a wireless communication method provided in this application. The process is as follows: Figure 4A As shown, the specific process is as follows: Step 11: Backup the network and start disaster recovery failover.

[0153] For example, when a core network failure occurs and disaster recovery switching is required, the backup network initiates disaster recovery switching.

[0154] For example, the backup network first detects the failure of the primary network through NRF discovery, real-time data synchronization, heartbeat, etc., and may carry out a disaster recovery and failover process.

[0155] Step 12: The first AMF first queries the support server.

[0156] For example, a backup server is pre-built for user authentication in fault recovery and failover scenarios.

[0157] For example, the backup network AMF element first queries the support server to confirm whether there are any users requiring support in the current network. If no such users exist, normal disaster recovery failover is performed. If there are several users requiring priority support, requests are proactively sent to these users via handover, paging, or other means to take over services or register them, ensuring smooth access for these users. After the backup network completes access for all key users, it initiates the normal disaster recovery failover process to handle the registration and access of other users.

[0158] For example, after the key user (i.e. the user equipment with the first priority) is identified by the UDM, the identification is sent to the AMF and the terminal; when the AMF receives the registration message carrying the key user identification, it also registers with the protection server and notifies the user code number, protection level and other information.

[0159] It should be noted that, under normal circumstances, after the initial registration is completed, users will have no difference in mobility updates, basic services, etc., compared to ordinary users.

[0160] Step 13: Determine if there are any users on the current network who require protection.

[0161] For example, if not, proceed to step 14; if yes, proceed to steps 15 and 16.

[0162] Step 14: Perform disaster recovery failover as normal.

[0163] Step 15: Initiate access requests to key users.

[0164] For example, if there are users who need to be given priority protection (i.e., user equipment with the highest priority), the AMF of the backup network will proactively send requests to these key users through handover, paging, or other means to take over their services or register them, so as to ensure that they can successfully access the backup network.

[0165] Step 16: After all key users have registered, complete the disaster recovery and failover for the remaining users.

[0166] For example, after the backup network completes the access of all key users, it then initiates the normal disaster recovery and failover process to handle the registration and access of other ordinary users (i.e., second-priority user equipment).

[0167] It should be noted that the information of the aforementioned users requiring priority protection (i.e., user equipment with the highest priority) is pre-managed. For example, key users are identified through a subscription identifier on the Unified Data Management (UDM) network element. This identifier (including user priority information) is sent to the AMF and the terminal during user registration. When the AMF receives a registration message carrying the key user identifier, it simultaneously registers with the protection server, notifying the user of their code number, protection level, and other information. Under normal circumstances, after the initial registration is completed, the user's mobility update, basic service, and other processes are no different from those of ordinary users.

[0168] The following is an exemplary description of the process by which the AMF registers user information of at least one first UE with the assurance server. For example, as shown... Figure 4B As shown, the registration process may include the following steps: Step 21: The UE sends a registration request to the RAN.

[0169] Step 22: RAN performs AMF selection.

[0170] Step 23: The RAN sends a registration request to the AMF.

[0171] For example, the RAN sends a registration request to the selected AMF.

[0172] Step 24: AMF performs AUSF selection.

[0173] For example, the AMF can be the second AMF mentioned above.

[0174] Step 25: Perform the authentication and security process.

[0175] For example, the AMF works in conjunction with the Authentication Server Function (AUSF) and the UE to complete two-way authentication and the establishment of security keys.

[0176] Step 26: AMF performs UDM selection.

[0177] Step 27a: AMF initiates user context management registration with UDM.

[0178] For example, the AMF registers its service relationship with the UE in the UDM through the Nudm_UECM_Registration service operation.

[0179] Step 27b: AMF obtains user contract data from UDM.

[0180] For example, the AMF obtains the UE's subscription data from the UDM through the Nudm_SDM_Get service operation, which includes the user's priority identifier (such as the protection level).

[0181] Step 27c: AMF subscriber subscription data update.

[0182] For example, the AMF subscribes to the UDM for change notifications of the UE's subscribed data through the Nudm_SDM_Subscribe service operation.

[0183] Step 27d: AMF sends a registration request to the assurance server.

[0184] For example, after obtaining user subscription data from the UDM, if the AMF identifies the UE as a user requiring priority protection (e.g., the subscription data contains a high-priority identifier), it simultaneously sends a registration request to the protection server. This registration request is used to register the UE's user information (including at least the user's permanent identifier and protection level) with the protection server.

[0185] Step 28: AMF performs PCF selection.

[0186] Step 29: Establish policy associations during the registration process.

[0187] For example, the AMF establishes a policy association with the selected PCF to obtain the UE's access and session management policies.

[0188] Step 30: The AMF sends a registration acceptance message to the UE.

[0189] For example, the AMF sends a Registration Accept message to the UE via the RAN to notify the UE that registration was successful.

[0190] Step 31: The UE sends a registration completion message to the AMF.

[0191] For example, the UE sends a Registration Complete message to the AMF to confirm that the registration process has been completed.

[0192] In this embodiment of the application, the above process ensures that the user's priority information is obtained by the AMF during the normal registration phase and is simultaneously registered to an independent protection server, thereby laying a data foundation for differentiated priority access for users in subsequent disaster recovery and failover scenarios.

[0193] Figure 5 A flowchart illustrating another wireless communication method provided in this application embodiment is shown below. Figure 5 As shown, the wireless communication method may include the following steps 501 to 503: Step 501: If the first AMF determines that the primary network has failed, it sends a query request to the support server.

[0194] The aforementioned query request is used to obtain information about user equipment (UE) with the first access priority that has been pre-registered in the security server; Step 502: The first AMF receives a query response from the assurance server.

[0195] The query response mentioned above carries user information of at least one first UE.

[0196] Step 503: The first AMF performs a first access process on at least one first UE and a second access process on at least one second UE based on user information.

[0197] Among them, at least one second UE is a UE other than at least one first UE among the UEs that the backup network needs to provide services for.

[0198] The first access process includes: immediately initiating a process for at least one first UE to access the backup network of the primary network; or immediately responding to the access request of at least one first UE.

[0199] The second access process includes: delaying the initiation of a process for at least one second UE to access the backup network; or delaying the response to an access request from at least one second UE.

[0200] In some embodiments of this application, the process of delaying the initiation of the access procedure for at least one second UE in step 503 above may include the following step 503a: Step 503a: If the preset conditions are met, the first AMF initiates an access procedure for at least one second UE.

[0201] The preset conditions include at least one of the following: at least one first UE service has been restored; the time elapsed since the start of the access procedure for at least one target UE exceeds the preset waiting time.

[0202] In some embodiments of this application, the aforementioned user information includes a user identifier and a protection level; exemplarily, the process in step 503 where the first AMF immediately initiates the procedure for at least one first UE to access the backup network of the primary network may include steps 503b1 and 503b2: Step 503b1: The first AMF determines the access control policy based on user information; Step 503b2: The first AMF immediately initiates the access procedure for at least one first UE to access the backup network based on the access control policy.

[0203] The access control policy includes at least one access timing and network resource allocation policy for a first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources and computing resources.

[0204] In some embodiments of this application, the process of the AMF immediately initiating the access of at least one first UE to the backup network of the primary network in step 503 above may include the following steps 503c1 and / or 503c2: Step 503c1: The first AMF sends a paging instruction to the radio access network RAN ​​for at least one first UE.

[0205] The paging indication includes priority level indication information, and the paging indication is used to trigger RAN processing of paging for at least one first UE; or, Step 503c2: The first AMF sends a Non-Access Stratum (NAS) message to at least one first UE.

[0206] The NAS message contains a first instruction, which is used to instruct immediate re-registration. The NAS message is used to instruct at least one first UE to initiate a registration process to the backup network.

[0207] In some embodiments of this application, step 503a may include steps 503a1 and 503a2: Step 503a1: Upon receiving registration completion confirmation messages or initial service request messages from all first UEs, the first AMF determines that at least one first UE has completed service recovery; Step 503a2: First, if it is determined that the service of at least one first UE has been restored, the access procedure for at least one second UE is initiated.

[0208] It should be noted that, for Figure 5 For explanations of the corresponding embodiments, please refer to the relevant descriptions of the embodiments above, which will not be repeated here.

[0209] Figure 6 A flowchart illustrating another wireless communication method provided in this application embodiment is shown below. Figure 6 As shown, the wireless communication method may include the following steps 601 and 602: Step 601: Ensure the server receives query requests from the first AMF.

[0210] The aforementioned query request is used to obtain information about user equipment (UEs) with the first access priority that have been pre-registered in the assurance server. The first AMF mentioned above is the AMF in the backup network.

[0211] Step 602: Ensure the server sends a query response to the first AMF.

[0212] The query response mentioned above carries user information of at least one first UE.

[0213] Among these measures, the server ensures that it has pre-registered user information for at least one UE with the highest access priority.

[0214] In some embodiments of this application, prior to step 601 above, the wireless communication method provided in this application may further include the following step 603: Step 603: Ensure the server receives the registration request from the second AMF.

[0215] The aforementioned registration request is used to register the user information of at least one first UE to the protection server. The user information includes the user identifier and the protection level.

[0216] It should be noted that, for Figure 6 For explanations of the corresponding embodiments, please refer to the relevant descriptions of the embodiments above, which will not be repeated here.

[0217] Figure 7The present application provides a system architecture diagram of a wireless communication system 700, which may include: a query request sending module 701, a query request receiving module 702, a query response sending module 703, a query response receiving module 704, and an access processing module 705.

[0218] The query request sending module 701 is used to send a query request to the support server when it is determined that the primary network has failed. The query request is used to obtain information of user equipment (UE) with first access priority that has been pre-registered in the support server, and is applied to the relevant schemes of steps 201 and 201 above.

[0219] The query request receiving module 702 is used to receive query requests from AMF.

[0220] The query response sending module 703 is used to send a query response to the AMF, and the query response carries user information of at least one first UE.

[0221] The query response receiving module 704 is used to receive query responses from the security server.

[0222] The access processing module 705 is configured to perform a first access process on at least one first UE and a second access process on at least one second UE based on user information; the at least one second UE is a UE other than at least one first UE among the UEs that need to provide services to the backup network; wherein the first access process includes: immediately initiating the process of at least one first UE accessing the backup network of the primary network; or, immediately responding to the access request of at least one first UE; the second access process includes: delaying the initiation of the process of at least one second UE accessing the backup network; or, delaying the response to the access request of at least one second UE.

[0223] It should be noted that for a detailed explanation of the steps performed by each module and their beneficial effects, please refer to the description in the above embodiments, which will not be repeated here.

[0224] As can be seen, the above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the embodiments of this application provide corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0225] This application embodiment can divide the wireless communication device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0226] In some embodiments, this application also provides a wireless communication device. The wireless communication device may include one or more functional modules for implementing the wireless communication method of the above method embodiments.

[0227] For example, Figure 8 This is a schematic diagram of the structure of a wireless communication device provided in an embodiment of this application. Figure 8 As shown, the wireless communication device 800 includes a transmitting module 801, a receiving module 802, and an execution module 803, wherein: The sending module 801 is used to send a query request to the support server when it is determined that the primary network has failed; the query request is used to obtain information of user equipment (UE) with first access priority that has been pre-registered in the support server. The receiving module 802 is used to receive a query response from the protection server, wherein the query response carries user information of at least one first UE; The execution module 803 is used to perform a first access process on at least one first UE and a second access process on at least one second UE based on user information; the at least one second UE is a UE other than at least one first UE among the UEs that need to provide services to the backup network. The first access process includes: immediately initiating a process for at least one first UE to access the backup network of the primary network; or immediately responding to the access request of at least one first UE. The second access process includes: delaying the initiation of a process for at least one second UE to access the backup network; or delaying the response to an access request from at least one second UE.

[0228] In some embodiments, the execution module described above is specifically used to initiate an access process for at least one second UE when preset conditions are met. The preset conditions include at least one of the following: at least one first UE service has been restored; the time elapsed since the start of the access procedure for at least one target UE exceeds the preset waiting time.

[0229] In other embodiments, the aforementioned user information includes a user identifier and a protection level; the aforementioned execution module is specifically used for the first AMF to determine an access control policy based on the user information; and based on the access control policy, to immediately initiate an access procedure for at least one first UE to access the backup network; wherein, the access control policy includes an access timing and network resource allocation policy for at least one first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources, and computing resources.

[0230] In some other embodiments, the execution module is specifically used to send a paging indication to the radio access network (RAN) for at least one first UE, the paging indication including priority level indication information, the paging indication being used to trigger the RAN to process the paging of at least one first UE; or, to send a non-access stratum (NAS) message to at least one first UE, the NAS message including a first indication, the first indication being used to instruct immediate re-registration, the NAS message being used to instruct at least one first UE to initiate a registration process to the backup network.

[0231] In some other embodiments, the execution module is specifically used to determine that at least one first UE has completed service recovery upon receiving registration completion confirmation messages or first service request messages from all first UEs; and to initiate an access process for at least one second UE upon determining that at least one first UE has completed service recovery.

[0232] For example, Figure 9 This is a schematic diagram of another wireless communication device provided in an embodiment of this application. Figure 9 As shown, the wireless communication device 900 includes a receiving module 901 and a transmitting module 902, wherein: The receiving module 901 is used to receive a query request from the first AMF; the query request is used to obtain information of a user equipment (UE) with a first access priority that has been pre-registered in the assurance server; the sending module 902 is used to send a query response to the first AMF, the query response carrying user information of at least one first UE; wherein, the assurance server has pre-registered user information of at least one UE with a first access priority.

[0233] In some embodiments, the receiving module is further configured to receive a registration request from a second AMF, the registration request being used to register user information of at least one first UE to the protection server, the user information including user identifier and protection level.

[0234] It should be noted that wireless communication devices can implement all the processes implemented in the above method embodiments and achieve the same beneficial effects. To avoid repetition, they will not be described again here.

[0235] In the case of implementing the functions of the integrated modules described above in hardware, this application provides a possible structural schematic diagram of an electronic device involved in the above embodiments. For example... Figure 10 As shown, the electronic device 90 includes a processor 92, a communication interface 93, and a bus 94. Optionally, the electronic device 90 may also include a memory 91. This electronic device can be a communication device.

[0236] Processor 92 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0237] Communication interface 93 is used to connect with other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0238] The memory 91 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0239] In one possible implementation, the memory 91 can exist independently of the processor 92. The memory 91 can be connected to the processor 92 via a bus 94 and is used to store instructions or program code. When the processor 92 calls and executes the instructions or program code stored in the memory 91, it can implement the wireless communication method provided in the embodiments of this application.

[0240] In another possible implementation, memory 91 can also be integrated with processor 92.

[0241] Bus 94 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 94 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0242] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.

[0243] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware. The program can be stored in the aforementioned computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be any of the foregoing embodiments or memory. The aforementioned computer-readable storage medium can also be an external storage device of the aforementioned service invocation device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the aforementioned service invocation device. Further, the aforementioned computer-readable storage medium can include both internal storage units of the aforementioned service invocation device and external storage devices. The aforementioned computer-readable storage medium is used to store the aforementioned computer program and other programs and data required by the aforementioned service invocation device. The aforementioned computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0244] This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform any of the wireless communication methods provided in the above embodiments.

[0245] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless communication method, characterized in that, include: When the primary access and mobility management function (AMF) determines that the primary network has failed, it sends a query request to the support server. The query request is used to obtain information about a user equipment (UE) with a first access priority that has been pre-registered in the security server; The first AMF is the AMF in the backup network of the primary network; The first AMF receives a query response from the protection server, the query response carrying user information of at least one first UE; Based on the user information, the first AMF performs a first access process on the at least one first UE and a second access process on the at least one second UE; The at least one second UE is a UE other than the at least one first UE among the UEs that the backup network needs to provide services for; The first access process includes: immediately initiating the process of the at least one first UE accessing the backup network; or, immediately responding to the access request of the at least one first UE. The second access process includes: delaying the initiation of the process for the at least one second UE to access the backup network; or delaying the response to the access request of the at least one second UE.

2. The method according to claim 1, characterized in that, The delayed start access procedure for the at least one second UE includes: Under the condition that the preset conditions are met, the first AMF initiates the access procedure for the at least one second UE; The preset conditions include at least one of the following: the service recovery of the at least one first UE is completed; the time elapsed since the start of the access procedure for the at least one target UE exceeds the preset waiting time.

3. The method according to claim 1, characterized in that, The user information includes a user identifier and a protection level; the first AMF immediately initiates the process for the at least one first UE to access the backup network of the primary network, including: The first AMF determines the access control policy based on the user information; Based on the access control policy, the first AMF immediately initiates the access procedure for at least one first UE to access the backup network; The access control policy includes the access timing and network resource allocation policy for at least one first UE; the first UE with a higher protection level is allocated an earlier access timing and / or higher priority network resources; the network resources include at least one of signaling processing resources, transmission bandwidth resources, and computing resources.

4. The method according to claim 1, characterized in that, The first AMF immediately initiates the process of the at least one first UE accessing the backup network of the primary network, including: The first AMF sends a paging indication to the radio access network (RAN) for the at least one first UE. The paging indication includes priority level indication information, and the paging indication is used to trigger the RAN to process the paging of the at least one first UE; or, The first AMF sends a Non-Access Stratum (NAS) message to the at least one first UE. The NAS message contains a first indication, which is used to instruct the at least one first UE to immediately perform re-registration. The NAS message is used to instruct the at least one first UE to initiate a registration process with the backup network.

5. The method according to claim 2, characterized in that, The step of initiating an access procedure for the at least one second UE when preset conditions are met includes: Upon receiving registration completion confirmation messages or initial service request messages from all first UEs, the first AMF determines that the service recovery of at least one first UE has been completed. If the first AMF determines that the service of the at least one first UE has been restored, it initiates the access procedure for the at least one second UE.

6. A wireless communication method, characterized in that, include: Ensure the server receives query requests from the first AMF; The query request is used to obtain information about a user equipment (UE) with a first access priority that has been pre-registered in the security server; The protection server sends a query response to the first AMF, and the query response carries user information of at least one first UE. The security server pre-registers user information for at least one UE with a first access priority.

7. The method according to claim 6, characterized in that, Before the security server receives a query request from the first AMF, it also includes: The security server receives a registration request from the second AMF; The registration request is used to register the user information of at least one first UE to the protection server, and the user information includes a user identifier and a protection level; the second AMF is the AMF in the primary network.

8. A wireless communication device, characterized in that, include: The module consists of a sending module, a receiving module, and an execution module, among which: The sending module is configured to send a query request to the support server when it is determined that the primary network has failed; the query request is used to obtain information of user equipment (UE) with a first access priority that has been pre-registered in the support server. The receiving module is used to receive a query response from the protection server, wherein the query response carries user information of at least one first UE; The execution module is configured to perform a first access process on the at least one first UE and a second access process on the at least one second UE based on the user information; the at least one second UE is a UE other than the at least one first UE among the UEs that the backup network needs to provide services for. The first access process includes: immediately initiating the process of the at least one first UE accessing the backup network of the primary network; or immediately responding to the access request of the at least one first UE. The second access process includes: delaying the initiation of the process for the at least one second UE to access the backup network; or delaying the response to the access request of the at least one second UE.

9. A wireless communication device, characterized in that, The device includes: a receiving module and a transmitting module, wherein: The receiving module is configured to receive a query request from the first AMF; the query request is used to obtain information about a user equipment (UE) with a first access priority that has been pre-registered in the assurance server. The sending module is used to send a query response to the first AMF, wherein the query response carries user information of at least one first UE; The security server pre-registers user information for at least one UE with a first access priority.

10. A communication device, characterized in that, The device includes a processor and a memory, the processor being coupled to the memory; the memory is used to store computer instructions, which are loaded and executed by the processor to enable the computer device to implement the wireless communication method as described in any one of claims 1 to 5, or to implement the wireless communication method as described in claim 6 or 7.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the wireless communication method as described in any one of claims 1 to 5, or to implement the wireless communication method as described in claim 6 or 7.

12. A computer program product, characterized in that, The computer program product includes a computer program that, when run in an electronic device, causes the electronic device to implement the wireless communication method as described in any one of claims 1 to 5, or to implement the wireless communication method as described in claim 6 or 7.

Images