Business request processing system, method, electronic device, and storage medium

Abstract

Embodiments of the present application provide a service request processing system, method, electronic device and storage medium. The processing system comprises at least a forwarding node, a first data management node in communication connection with the forwarding node, and a second data management node. Each first data management node is in communication connection with one second data management node through a synchronization channel. The first data management node is configured to store original user data, and the second data management node is configured to store incremental user data corresponding to the original user data.

Description

Technical Field

[0001] This invention relates to the field of network communication technology, and in particular to a service request processing system, a service request processing method, an electronic device, and a computer-readable storage medium. Background Technology

[0002] In mobile communication networks, operators use number segments to classify the geographical locations of different provinces. Each province further subdivides these number segments based on its service volume characteristics, implementing regional management through specific rules. While the user data management system provides unified allocation, it also allows for clear differentiation of geographically assigned numbers. Initially, network data can be managed using a sub-database model based on regional attributes. As the network grows, the database can be continuously fragmented by city. However, for large local networks operating under a municipality model, if a vague number segment management method was used in the early stages of service launch, and the initial database capacity becomes insufficient as the service scales up, a rule-based sub-database fragmentation management model cannot be implemented. Summary of the Invention

[0003] The present invention provides a system, method, electronic device, and computer-readable storage medium for processing business requests, in order to solve or partially solve the problems of poor real-time performance and low reliability in the data query process.

[0004] This invention discloses a service request processing system, which includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node through a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data.

[0005] The forwarding node is used to obtain service requests sent by user terminals, and the service requests include the terminal identifier corresponding to the user terminal.

[0006] The first data management node is configured to return the target user data corresponding to the terminal identifier to the user terminal if user data corresponding to the terminal identifier is found.

[0007] The second data management node is configured to receive the terminal identifier, query the target user data corresponding to the terminal identifier, and return the target user data to the user terminal if no user data corresponding to the terminal identifier is found in the first data management node.

[0008] Optionally, each of the first data management nodes includes a first function implementation node and a first data storage node;

[0009] The first functional implementation node is used to receive the terminal identifier sent by the forwarding node;

[0010] The first data storage node is configured to, if user data corresponding to the terminal identifier is found, return the target user data corresponding to the terminal identifier to the user terminal; if no user data corresponding to the terminal identifier is found, forward the terminal identifier to the second data management node through the synchronization channel.

[0011] Optionally, the first functional implementation node stores routing node information corresponding to all terminal identifiers; wherein,

[0012] The first functional implementation node is used to identify the second data management node corresponding to the terminal identifier based on the routing node information, and send the terminal identifier to the second data management node.

[0013] Optionally, each of the second data management nodes includes a second function implementation node and a second data storage node; wherein,

[0014] The first function implementation node is used to identify the target function implementation node corresponding to the terminal identifier from the second data management node according to the routing node information, and send the terminal identifier to the target data management node;

[0015] The target data management node is used to send the terminal identifier to the corresponding second data storage node;

[0016] The second data storage node is used to query the target user data corresponding to the terminal identifier and return the target user data to the user terminal.

[0017] Optionally, the forwarding node is further configured to obtain the terminal identifier returned by the first data management node and the query failure information for the terminal identifier, and send the terminal identifier to the second data management node according to the query failure information.

[0018] Optionally, the first function implementation node includes a first primary function implementation node and a first backup function implementation node, and the first data storage node includes a first primary data storage node and a first backup data storage node; the second function implementation node includes a second primary function implementation node and a second backup function implementation node, and the second data storage node includes a second primary data storage node and a second backup data storage node.

[0019] Optionally, the forwarding node includes at least one of a network storage function node, a signaling transfer node, and a routing agent node; the first data management node and the second data management node are unified data management function nodes.

[0020] This invention also discloses a method for processing business requests, applied to a business request processing system. The processing system includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node via a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. The method includes:

[0021] The forwarding node obtains the service request sent by the user terminal, and the service request includes the terminal identifier corresponding to the user terminal.

[0022] If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal.

[0023] If no user data corresponding to the terminal identifier is found in the first data management node, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal.

[0024] Optionally, each of the first data management nodes includes a first function implementation node and a first data storage node. The step of returning the target user data corresponding to the terminal identifier to the user terminal if the first data management node finds user data corresponding to the terminal identifier includes:

[0025] The first function enables the node to receive the terminal identifier sent by the forwarding node;

[0026] If the first data storage node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal.

[0027] If the first data storage node cannot find user data corresponding to the terminal identifier, it forwards the terminal identifier to the second data management node through the synchronization channel.

[0028] Optionally, the first functional implementation node stores routing node information corresponding to all terminal identifiers, and further includes:

[0029] The first functional implementation node identifies the second data management node corresponding to the terminal identifier based on the routing node information, and sends the terminal identifier to the second data management node.

[0030] Optionally, each of the second data management nodes includes a second function implementation node and a second data storage node. The first function implementation node identifies the second data management node corresponding to the terminal identifier based on the routing node information and sends the terminal identifier to the second data management node, including:

[0031] The first function implementation node is used to identify the target function implementation node corresponding to the terminal identifier from the second data management node according to the routing node information, and send the terminal identifier to the target data management node;

[0032] Wherein, if no user data corresponding to the terminal identifier is found in the first data management node, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal, including:

[0033] The target data management node sends the terminal identifier to the corresponding second data storage node;

[0034] The second data storage node queries the target user data corresponding to the terminal identifier and returns the target user data to the user terminal.

[0035] Optionally, it also includes:

[0036] The forwarding node obtains the terminal identifier returned by the first data management node and the query failure information for the terminal identifier, and sends the terminal identifier to the second data management node according to the query failure information.

[0037] Optionally, the first function implementation node includes a first primary function implementation node and a first backup function implementation node, and the first data storage node includes a first primary data storage node and a first backup data storage node; the second function implementation node includes a second primary function implementation node and a second backup function implementation node, and the second data storage node includes a second primary data storage node and a second backup data storage node.

[0038] Optionally, the forwarding node includes at least one of a network storage function node, a signaling transfer node, and a routing agent node; the first data management node and the second data management node are unified data management function nodes.

[0039] This invention also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0040] The memory is used to store computer programs;

[0041] When the processor executes a program stored in the memory, it implements the method described in the embodiments of the present invention.

[0042] This invention also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this invention.

[0043] The embodiments of the present invention have the following advantages:

[0044] In this embodiment of the invention, the processing system may include a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node through a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. When a user terminal initiates a service request, the forwarding node can obtain the service request sent by the user terminal. The service request includes a terminal identifier corresponding to the user terminal. If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If the first data management node does not find user data corresponding to the terminal identifier, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal. Thus, by classifying the data management nodes, a unified data forwarding node is provided externally as an entry point for data query, ensuring both the real-time nature and reliability of data query. Attached Figure Description

[0045] Figure 1 This is a structural block diagram of a business request processing system provided in an embodiment of the present invention;

[0046] Figure 2 This is a schematic diagram of the prior art provided in the embodiments of the present invention;

[0047] Figure 3 This is a schematic diagram of the processing system provided in an embodiment of the present invention;

[0048] Figure 4 This is a flowchart of the steps of a service request processing method provided in an embodiment of the present invention;

[0049] Figure 5 This is a block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0050] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0051] As an example, in mobile communication networks, operators divide the geographical locations of each province by number segments. Each province further subdivides the number segments of its various cities based on business volume characteristics, achieving regional management through specific rules. While unified allocation is implemented in the user data management system, regionally assigned numbers can also be clearly distinguished. Initially, network data can be managed using a sub-database model based on regional attributes. As the scale grows, the database can be continuously fragmented by city. However, for large local networks under the municipality model, where a vague number segment management method was used in the early stages of service launch, as the business scale gradually expands and the initial database capacity becomes insufficient, a rule-based sub-database fragmentation management model cannot be implemented. In 4G and 5G mobile networks, the business process includes registration, authentication, and business data subscription query processes. This invention addresses these issues in the field of user data query in mobile communications.

[0052] One of the core inventive points of this invention lies in its application to the business management methods and data of telecom operators. It primarily addresses a card issuance model adopted by operators that does not differentiate between geographical locations when managing SIM cards. Compared to regionally segmented management models, this model offers greater flexibility and facilitates provincial-level coordination. However, with the continuous expansion of the business, a conflict arises between the number of users and the capabilities of the user data management platform. This invention addresses this conflict by using a split sub-database to provide a unified data query portal, resolving the contradiction from the operations and maintenance side and effectively addressing the operator's user data management and querying needs. Specifically, a corresponding processing system is constructed, which may include forwarding nodes, a first data management node communicating with the forwarding nodes, and a second data management node. Each first data management node communicates with a second data management node through a synchronization channel. The first data management node stores the original user data, and the second data management node stores the incremental user data corresponding to the original user data. When a user terminal initiates a service request, the forwarding node can obtain the service request sent by the user terminal. The service request includes the terminal identifier corresponding to the user terminal. If the first data management node finds the user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If the first data management node does not find the user data corresponding to the terminal identifier, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal. Thus, by classifying the data management nodes, a unified data forwarding node is provided externally as an entry point for data query, ensuring both the real-time nature and reliability of data query.

[0053] To enable those skilled in the art to better understand the technical solutions of the embodiments of the present invention, some technical features involved in the embodiments of the present invention will be explained and described:

[0054] In 5G communication systems, 3GPP (3rd Generation Partnership Project) defines SUPI (Subscription Permanent Identifier), a unique identifier assigned to each SIM card, consistent with 4G's IMSI (International Mobile Subscriber Identity). This authentication between the user and the operator is based on a shared symmetric key. If the IMSI or SUPI is transmitted in plaintext over the radio interface, it could be intercepted and used to identify, locate, and track users. 5G also defines encryption via SCUI (Subscription Concealed Identifier) ​​for transmission.

[0055] UDM: Unified Data Management, used for 3GPP AKA (Authentication and Key Agreement, third-generation mobile communication network authentication, user identification, access authorization, registration, mobility, subscription, SMS management, etc.

[0056] UDR: Unified Data Repository, a unified data warehouse function used by UDM to store or retrieve subscription data and by PCF to store or retrieve policy data.

[0057] NRF: Network Repository Function, supports service registration / deregistration and discovery. NRF receives NF discovery requests from NF instances and provides information about the discovered NF instances; it maintains NF configuration files for available NF instances and the services they support.

[0058] After an NF goes live, it will proactively report its supported capabilities to the NRF, including the number ranges it supports. Other NFs can then use the NRF to find the NF that provides them with the service capabilities. In current network deployments, number range-based NFs include network elements such as UDM, UDR, AUSF, and PCF. Operators can manage the number range information supported by number range-based NFs by including the groupId and supported number range information when planning NF registration.

[0059] DRA: Diameter Routing Agent. DRA nodes are responsible for LTE (Long Term Evolution) Diameter signaling destination address translation and switching, enabling LTE user authentication, location updates, and billing management.

[0060] STP: Signaling Transfer Point. A signaling transfer point is a specialized signaling point that only forwards No. 7 signaling.

[0061] In live network deployments, UDM typically has a two-tier architecture, consisting of FE and UDR. FE (Front End) implements the functions of the UDM functional entity, including protocol processing, service processing, and policy data management.

[0062] Authentication: Verify whether a user has permission to access the 5G network.

[0063] Specifically, refer to Figure 1 This diagram illustrates a structural block diagram of a service request processing apparatus provided in an embodiment of the present invention. The processing system includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node via a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data.

[0064] The forwarding node is used to obtain service requests sent by user terminals, and the service requests include the terminal identifier corresponding to the user terminal.

[0065] The first data management node is configured to return the target user data corresponding to the terminal identifier to the user terminal if user data corresponding to the terminal identifier is found.

[0066] The second data management node is configured to receive the terminal identifier, query the target user data corresponding to the terminal identifier, and return the target user data to the user terminal if no user data corresponding to the terminal identifier is found in the first data management node.

[0067] In this embodiment of the invention, the forwarding node includes at least one of a network storage function node, a signaling transfer node, and a routing proxy node; the first data management node and the second data management node are unified data management function nodes. The processing system can be a system composed of corresponding network elements in a communication network, and can be used to process service requests initiated by user terminals, including processing authentication, user identification, access authorization, registration, mobility, subscription, and SMS management requests initiated by user terminals. The forwarding node in the processing system can receive service requests sent by user terminals, and these service requests may include a corresponding terminal identifier, which can be an encrypted SCUI used to represent a unique user terminal.

[0068] In practical implementation, the forwarding node can forward the terminal identifier to the corresponding data management node, which then responds to the request and returns the corresponding data. (Refer to...) Figure 2 This diagram illustrates a prior art technology provided in an embodiment of the present invention. Solid lines represent the main communication channel, and dashed lines represent backup communication channels. In a common solution, the FE and UDR are mutually bound. User data is stored in different UDRs based on different number segments. For example, data from 460112222000000 to 460112222999999 is stored in UDM1 (UDM may include at least one FE and at least one UDR), and data from 460113333000000 to 460113333999999 is stored in UDM2. The DRA / NRF / STP routes data to the corresponding FE based on the registered number segment FE information and then finds the primary UDR to perform user data query, authentication, subscription, and push. The service delivery platform also points to different UDR database platforms based on number segments. The service delivery platform's function is to obtain user requests for adding, modifying, or deleting number service attributes from the customer management system, convert these requests into instructions, and send them to the UDM UDR to modify the relevant attributes in the UDM database. However, in this situation, when the operator's service allocation system does not differentiate between number segments and writes all data to the same database, the newly allocated number segments may overflow because the database has reached its maximum capacity.

[0069] In this embodiment of the invention, for each first data management node, a corresponding second data management node can be configured as an extended database. The two nodes are connected via a corresponding synchronization channel. For example, by expanding the capacity of the first data management node, a corresponding second data management node can be added to store newly issued numbers. A database synchronization channel is established between the two data management nodes. The path for the business issuance system remains unchanged. If the first data management node can handle the process, it can directly perform modification, deletion, and other instructions. For newly opened numbers, the data is forwarded to the second data management node for processing via the synchronization channel. Furthermore, audits can be performed periodically using the data from the first data management node as a benchmark, updating the data in the second data management node accordingly.

[0070] Each of the first data management nodes includes a first function implementation node and a first data storage node. The first function implementation node can be used to receive the terminal identifier sent by the forwarding node. The first data storage node can be used to return the target user data corresponding to the terminal identifier to the user terminal if the user data corresponding to the terminal identifier is found. If the user data corresponding to the terminal identifier is not found, the terminal identifier is forwarded to the second data management node through the synchronization channel.

[0071] In addition, if the first functional implementation node stores routing node information corresponding to all terminal identifiers, then the first functional implementation node is used to identify the second data management node corresponding to the terminal identifier based on the routing node information, and send the terminal identifier to the second data management node.

[0072] In one optional embodiment, each second data management node includes a second function implementation node and a second data storage node. The first function implementation node can be used to identify the target function implementation node corresponding to the terminal identifier from the second data management node according to the routing node information, and send the terminal identifier to the target data management node. The target data management node can be used to send the terminal identifier to the corresponding second data storage node. Then, the second data storage node can be used to query the target user data corresponding to the terminal identifier and return the target user data to the user terminal.

[0073] Optionally, the forwarding node can also be used to obtain the terminal identifier returned by the first data management node and the query failure information for the terminal identifier, and send the terminal identifier to the second data management node based on the query failure information.

[0074] Optionally, the first function implementation node includes a first primary function implementation node and a first backup function implementation node, and the first data storage node includes a first primary data storage node and a first backup data storage node; the second function implementation node includes a second primary function implementation node and a second backup function implementation node, and the second data storage node includes a second primary data storage node and a second backup data storage node.

[0075] In one example, refer to Figure 3This diagram illustrates a processing system provided in an embodiment of the present invention. Solid lines represent the main communication channel, dashed lines represent backup communication channels, and arrows represent data synchronization. The processing system may include forwarding nodes such as DRA / NRF / STP. The first data management node may consist of UDM1 FE1, UDM1 FE2, UDM1 UDR1, and UDM1 UDR2. The second data management node may consist of UDM2 FE1, UDM2 FE2, UDM2 UDR1, and UDM2 UDR2. UDM1 UDR2 can serve as a backup data storage node for UDM1 UDR1 within the same data management node. Similarly, UDM2 UDR2 can serve as a backup data storage node for UDM2 UDR1 within the same data management node. UDM2 UDR1 can serve as an extended data storage node for UDM1 UDR1, and data is connected through corresponding synchronization channels. The user data management system is expanded by adding UDM2 UDR. UDM1 UDR is the existing database, and UDM2 is a new platform used to store newly issued numbers. UDRs establish a database synchronization channel to maintain the same path for the service provisioning system. UDM1 UDR receives service provisioning instructions and directly processes modification and deletion instructions for numbers already belonging to its platform. Newly opened accounts are forwarded to UDM2 UDR for processing through the synchronization channel between the two UDRs. A routing node module is added to UDM1 UDR to store routing node information for all numbers. Periodic audits are performed using UDM1 UDR's data as a benchmark. UDM2 UDR updates user data routing node information. Regarding user routing data, since each UDR stores all routing data, service requests from UDM1FE1 are processed directly if the user data belongs to UDM1 UDR. If it belongs to UDM2 UDR, UDM1 UDR returns the routing node information of the UDR to which the user belongs. The mapping relationship between routing node information and the corresponding UDM2 FE is configured in UDM1 FE. You can also set up partition configurations in UDM1 UDR or FE to identify the UDR to which a user belongs. You can configure the GT, hostname, or 5G service address of the FE that forwards to the corresponding partition. Users belonging to the UDM2 UDR partition can be forwarded to the corresponding UDM2 FE through UDM1 FE. They can be directly connected or forwarded to any UDM FE through DRA, STP, or NRF.

[0076] By constructing a corresponding processing system, user terminals can query user data and route and forward the corresponding data during the processes of attaching, registering, and establishing sessions. By classifying data management nodes and providing unified data forwarding nodes as entry points for data queries, both the real-time nature and reliability of data queries are guaranteed.

[0077] In this embodiment of the invention, the processing system may include a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node through a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. When a user terminal initiates a service request, the forwarding node can obtain the service request sent by the user terminal. The service request includes a terminal identifier corresponding to the user terminal. If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If the first data management node does not find user data corresponding to the terminal identifier, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal. Thus, by classifying the data management nodes, a unified data forwarding node is provided externally as an entry point for data query, ensuring both the real-time nature and reliability of data query.

[0078] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, an example is provided below for illustration:

[0079] During the registration process of a terminal with a 4G or 5G base station, the registration authentication data and subscription information activated in the UDM are required. The registration process is as follows: First, the terminal initiates a registration request. The wireless network forwards the registration request to the AMF (Authentication Management Function). Upon receiving the registration request, the AMF finds the corresponding AFS (Authentication Server Function) that can provide the service based on the routing information registered on the NRF and initiates an authentication request. After the AFS completes the comparison of the terminal, it returns a successful response to the AMF. The AMF then initiates registration with the UDM, such as registration for terminal connection management, retrieves subscription parameters, and can also subscribe to the UDM's subscription information management. If there are changes to the terminal data, data or permission changes can be initiated in real time.

[0080] In this embodiment, when the UDM registers SUPI number data with the NRF, it still registers in the original way, and each UDM's FE can process all number segment data in its entirety. When any user terminal registers, it is randomly assigned to a UDM FE in the network. The FE checks its local UDR data. If the UDR determines that the number is not in its database, it returns a result code and the corresponding number's routing information to the FE via an internal protocol. Based on the mapping between routing information and IP addresses in the configuration file, the FE forwards the authentication request or subscription data request message to the corresponding FE, which then forwards it to the corresponding UDR for data querying.

[0081] The UDR databases of the two UDMs can use database synchronization technology to ensure that newly added data during the service deployment process can be correctly forwarded to other sub-databases.

[0082] Reference Figure 4 This diagram illustrates a flowchart of a service request processing method provided in an embodiment of the present invention. Applied to a service request processing system, the system includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node via a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. Specifically, the method may include the following steps:

[0083] Step 401: The forwarding node obtains the service request sent by the user terminal, and the service request includes the terminal identifier corresponding to the user terminal;

[0084] Step 402: If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal.

[0085] Step 403: If no user data corresponding to the terminal identifier can be found in the first data management node, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal.

[0086] In one optional embodiment, each of the first data management nodes includes a first function implementation node and a first data storage node. The step of returning the target user data corresponding to the terminal identifier to the user terminal if the first data management node finds user data corresponding to the terminal identifier includes:

[0087] The first function enables the node to receive the terminal identifier sent by the forwarding node;

[0088] If the first data storage node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal.

[0089] If the first data storage node cannot find user data corresponding to the terminal identifier, it forwards the terminal identifier to the second data management node through the synchronization channel.

[0090] In one optional embodiment, the first functional implementation node stores routing node information corresponding to all terminal identifiers, and further includes:

[0091] The first functional implementation node identifies the second data management node corresponding to the terminal identifier based on the routing node information, and sends the terminal identifier to the second data management node.

[0092] In one optional embodiment, each of the second data management nodes includes a second function implementation node and a second data storage node. The first function implementation node identifies the second data management node corresponding to the terminal identifier based on the routing node information, and sends the terminal identifier to the second data management node, including:

[0093] The first function implementation node is used to identify the target function implementation node corresponding to the terminal identifier from the second data management node according to the routing node information, and send the terminal identifier to the target data management node;

[0094] Wherein, if no user data corresponding to the terminal identifier is found in the first data management node, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal, including:

[0095] The target data management node sends the terminal identifier to the corresponding second data storage node;

[0096] The second data storage node queries the target user data corresponding to the terminal identifier and returns the target user data to the user terminal.

[0097] In one alternative embodiment, it further includes:

[0098] The forwarding node obtains the terminal identifier returned by the first data management node and the query failure information for the terminal identifier, and sends the terminal identifier to the second data management node according to the query failure information.

[0099] In one optional embodiment, the first function implementation node includes a first primary function implementation node and a first backup function implementation node, and the first data storage node includes a first primary data storage node and a first backup data storage node; the second function implementation node includes a second primary function implementation node and a second backup function implementation node, and the second data storage node includes a second primary data storage node and a second backup data storage node.

[0100] In one optional embodiment, the forwarding node includes at least one of a network storage function node, a signaling transfer node, and a routing proxy node; the first data management node and the second data management node are unified data management function nodes.

[0101] In this embodiment of the invention, the processing system may include a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node is communicatively connected to a second data management node through a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. When a user terminal initiates a service request, the forwarding node can obtain the service request sent by the user terminal. The service request includes a terminal identifier corresponding to the user terminal. If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If the first data management node does not find user data corresponding to the terminal identifier, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal. Thus, by classifying the data management nodes, a unified data forwarding node is provided externally as an entry point for data query, ensuring both the real-time nature and reliability of data query.

[0102] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0103] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0104] In addition, this invention also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the above-described service request processing method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0105] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described method embodiment for processing business requests and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0106] Figure 5 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0107] The electronic device 500 includes, but is not limited to, components such as: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510, and a power supply 511. Those skilled in the art will understand that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device. An electronic device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, mobile phones, tablet computers, laptops, PDAs, in-vehicle terminals, wearable devices, and pedometers.

[0108] It should be understood that, in this embodiment of the invention, the radio frequency unit 501 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 510; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 501 can also communicate with networks and other devices through a wireless communication system.

[0109] The electronic device provides users with wireless broadband internet access through the network module 502, such as helping users send and receive emails, browse web pages, and access streaming media.

[0110] The audio output unit 503 can convert audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into audio signals and output them as sound. Furthermore, the audio output unit 503 can also provide audio output related to specific functions performed by the electronic device 500 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, and a receiver, etc.

[0111] Input unit 504 is used to receive audio or video signals. Input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 506. The image frames processed by GPU 5041 can be stored in memory 509 (or other storage media) or transmitted via radio frequency unit 501 or network module 502. Microphone 5042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 501 in telephone call mode.

[0112] The electronic device 500 also includes at least one sensor 505, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 5051 according to the ambient light level, and the proximity sensor can turn off the display panel 5051 and / or backlight when the electronic device 500 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the posture of the electronic device (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 505 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0113] The display unit 506 is used to display information input by the user or information provided to the user. The display unit 506 may include a display panel 5051, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0114] User input unit 507 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of electronic devices. Specifically, user input unit 507 includes a touch panel 5071 and other input devices 5072. Touch panel 5071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 5071). Touch panel 5071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 510, which receives and executes commands from the processor 510. In addition, touch panel 5071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 5071, user input unit 507 may also include other input devices 5072. Specifically, other input devices 5072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0115] Furthermore, the touch panel 5071 can cover the display panel 5051. When the touch panel 5071 detects a touch operation on or near it, it transmits the information to the processor 510 to determine the type of touch event. Subsequently, the processor 510 provides corresponding visual output on the display panel 5051 according to the type of touch event. It is understood that in one embodiment, the touch panel 5071 and the display panel 5051 are implemented as two independent components to realize the input and output functions of the electronic device. However, in some embodiments, the touch panel 5071 and the display panel 5051 can be integrated to realize the input and output functions of the electronic device. The specific implementation is not limited here.

[0116] Interface unit 508 serves as an interface for connecting external devices to electronic device 500. For example, external devices may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 508 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more components within electronic device 500, or it can be used to transmit data between electronic device 500 and external devices.

[0117] The memory 509 can be used to store software programs and various data. The memory 509 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0118] The processor 510 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 509, and by calling data stored in the memory 509, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. The processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 510.

[0119] The electronic device 500 may also include a power supply 511 (such as a battery) that supplies power to various components. Preferably, the power supply 511 can be logically connected to the processor 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system.

[0120] In addition, the electronic device 500 includes some functional modules not shown, which will not be described in detail here.

[0121] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0122] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0123] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

[0124] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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 implementations should not be considered beyond the scope of this invention.

[0125] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0126] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0127] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0128] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0129] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0130] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A system for processing business requests, characterized in that, The processing system is suitable for operators using a non-regional card issuance model when managing card numbers. The system includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node communicates with a second data management node via a synchronization channel. The first data management node stores original user data, and the second data management node stores incremental user data corresponding to the original user data. Periodic audits are performed using the data from the first data management node as a benchmark, and the data in the second data management node is updated accordingly. The forwarding node is used to obtain service requests sent by user terminals, and the service requests include the terminal identifier corresponding to the user terminal. The first data management node is configured to return the target user data corresponding to the terminal identifier to the user terminal if user data corresponding to the terminal identifier is found. The second data management node is configured to receive the terminal identifier, query the target user data corresponding to the terminal identifier, and return the target user data to the user terminal if no user data corresponding to the terminal identifier is found in the first data management node. Each of the first data management nodes includes a first function implementation node and a first data storage node; The first functional implementation node is used to receive the terminal identifier sent by the forwarding node; The first data storage node is configured to, if user data corresponding to the terminal identifier is found, return the target user data corresponding to the terminal identifier to the user terminal; if user data corresponding to the terminal identifier is not found, forward the terminal identifier to the second data management node through the synchronization channel. The first functional implementation node stores routing node information corresponding to all terminal identifiers; wherein... The first functional implementation node is used to identify the second data management node corresponding to the terminal identifier based on the routing node information, and send the terminal identifier to the second data management node.

2. The processing system according to claim 1, characterized in that, Each of the second data management nodes includes a second function implementation node and a second data storage node; wherein, The first function implementation node is used to identify the target function implementation node corresponding to the terminal identifier from the second data management node according to the routing node information, and send the terminal identifier to the target data management node; The target data management node is used to send the terminal identifier to the corresponding second data storage node; The second data storage node is used to query the target user data corresponding to the terminal identifier and return the target user data to the user terminal.

3. The processing system according to claim 1, characterized in that, The forwarding node is also used to obtain the terminal identifier returned by the first data management node and the query failure information for the terminal identifier, and send the terminal identifier to the second data management node according to the query failure information.

4. The processing system according to claim 2, characterized in that, The first function implementation node includes a first primary function implementation node and a first backup function implementation node, and the first data storage node includes a first primary data storage node and a first backup data storage node; the second function implementation node includes a second primary function implementation node and a second backup function implementation node, and the second data storage node includes a second primary data storage node and a second backup data storage node.

5. The processing system according to any one of claims 1-4, characterized in that, The forwarding node includes at least one of the following: a network storage function node, a signaling transfer node, and a routing proxy node; the first data management node and the second data management node are unified data management function nodes.

6. A method for processing business requests, characterized in that, A processing system for business requests, applicable to operators using a non-regional card issuance model when managing card numbers, includes at least a forwarding node, a first data management node communicatively connected to the forwarding node, and a second data management node. Each first data management node communicates with a second data management node via a synchronization channel. The first data management node stores raw user data, and the second data management node stores incremental user data corresponding to the raw user data. Periodic audits are performed using the data from the first data management node as a benchmark, and the data in the second data management node is updated accordingly. The method includes: The forwarding node obtains the service request sent by the user terminal, and the service request includes the terminal identifier corresponding to the user terminal. If the first data management node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If no user data corresponding to the terminal identifier is found in the first data management node, the second data management node receives the terminal identifier, queries the target user data corresponding to the terminal identifier, and returns the target user data to the user terminal. Each of the first data management nodes includes a first function implementation node and a first data storage node, including: The first functional implementation node receives the terminal identifier sent by the forwarding node; If the first data storage node finds user data corresponding to the terminal identifier, it returns the target user data corresponding to the terminal identifier to the user terminal. If the first data storage node cannot find user data corresponding to the terminal identifier, the terminal identifier is forwarded to the second data management node through the synchronization channel; The first functional implementation node stores routing node information corresponding to all terminal identifiers, and also includes: The first functional implementation node identifies the second data management node corresponding to the terminal identifier based on the routing node information, and sends the terminal identifier to the second data management node.

7. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is used to store computer programs; When the processor executes a program stored in the memory, it implements the method as described in claim 6.

8. A computer-readable storage medium having instructions stored thereon that, when executed by one or more processors, cause the processors to perform the method of claim 6.

Images