Service processing method, storage medium, and electronic apparatus

Abstract

Embodiments of the present disclosure provide a service processing method, a storage medium, and an electronic apparatus. The method comprises: receiving a service request message, the service request message carrying a user identifier; by means of a user routing function (URF) component, determining user data routing information corresponding to the user identifier; and, on the basis of the user data routing information and by means of a pre-established internal data channel, sending a service request message to an existing HLR / HSS for processing or a second converged UDM / HSS for processing, the second converged UDM / HSS being one or more converged UDM / HSSs. The problem in the related art of low service processing performance after multiple sets of HLR / HSSs and UDM / HSSs are converged can be solved.

Description

A service processing method, storage medium and electronic device

[0001] Cross-reference to Related Applications

[0002] The present disclosure is based on Chinese Patent Application No. CN2024108454843 entitled "A service processing method, storage medium and electronic device" filed on June 27, 2024, and claiming priority to the same, the disclosure of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] Embodiments of the present disclosure relate to the technical field of wireless communication, in particular to a service processing method, storage medium and electronic device. BACKGROUND

[0004] 2 / 3 / 4G user data of a mobile communication network in a live network is stored in a stock HLR (Home Location Register) / HSS (Home Subscriber Server), the stock HLR / HSS refers to an HLR / HSS for storing original 2 / 3 / 4G user data, its associated systems include an operator BOSS (Business Operation Support System) and a signaling gateway device DRA (Diameter Routing Agent) / STP (Signalling Transfer Point), and the HLR / HSS is generally constructed according to the principle of large-capacity centralization. 5G network user data is stored in a UDM (Unified Data Management), due to the characteristics of inter-network roaming and incomplete network coverage of mobile communication, 2 / 3 / 4 / 5G user data needs to be fused, and UDM and HSS need to be deployed in a fusion mode. In a full-fusion scenario of UDM / HSS fusion equipment and stock HLR / HSS equipment number segments, after multiple sets of equipment are fused into a network, problems such as capacity alarm, high load of some equipment, and low capacity, low load of some equipment may occur.

[0005] For the problem of low service processing performance after multiple sets of HLR / HSS, UDM / HSS are fused in the related art, no solution has been proposed. SUMMARY

[0006] Embodiments of the present disclosure provide a service processing method, storage medium and electronic device to at least solve the problem of low service processing performance after multiple sets of HLR / HSS, UDM / HSS are fused in the related art.

[0007] According to one embodiment of the present disclosure, a service processing method is provided, applied to a first converged UDM / HSS, the method comprising: receiving a service request message, wherein the service request message carries a user identifier; determining, by a deployed URF component, user data routing information corresponding to the user identifier; and sending, based on the user data routing information, the service request message to a stock HLR / HSS or a second converged UDM / HSS for processing via a pre-established internal data channel, wherein the second converged UDM / HSS is one or more converged UDM / HSSs.

[0008] According to another embodiment of the present disclosure, a service processing apparatus is provided, applied to a first converged UDM / HSS, the apparatus comprising: a receiving module configured to receive a service request message, wherein the service request message carries a user identifier; a determining module configured to determine, by a deployed URF component, user data routing information corresponding to the user identifier; and a sending module configured to send, based on the user data routing information, the service request message to a stock HLR / HSS or a second converged UDM / HSS for processing via a pre-established internal data channel, wherein the second converged UDM / HSS is one or more converged UDM / HSSs.

[0009] According to yet another embodiment of the present disclosure, a computer program product is also provided, comprising computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0010] According to yet another embodiment of the present disclosure, a computer-readable storage medium is also provided, having stored therein a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0011] According to yet another embodiment of the present disclosure, an electronic device is also provided, comprising a memory and a processor, the memory having stored therein a computer program, and the processor being configured to execute the computer program to perform the steps in any of the above method embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0012] FIG. 1 is a hardware structure block diagram of a computer device of the service processing method according to an embodiment of the present disclosure;

[0013] FIG. 2 is a flowchart of the service processing method according to an embodiment of the present disclosure;

[0014] FIG. 3 is a structural schematic diagram of device fusion according to an embodiment of the present disclosure;

[0015] FIG. 4 is a flowchart of requesting creation of data according to an embodiment of the present disclosure;

[0016] FIG. 5 is a flowchart of requesting reading or modifying data according to an embodiment of the present disclosure;

[0017] FIG. 6 is a flowchart of requesting migration of data according to an embodiment of the present disclosure;

[0018] FIG. 7 is a flowchart of requesting signaling service according to an embodiment of the present disclosure;

[0019] FIG. 8 is a block diagram of a service processing apparatus according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.

[0021] It should be noted that the terms "first", "second", and the like in the description and claims of the present disclosure and the above-described accompanying drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or sequence.

[0022] The method embodiments provided in the embodiments of the present disclosure can be executed in a computer device or a similar computing apparatus. Taking an example of running on a computer device, FIG. 1 is a hardware structural block diagram of a computer device of a service processing method according to an embodiment of the present disclosure, as shown in FIG. 1, the computer device can include one or more (only one is shown in FIG. 1) processors 102 (the processor 102 can include but is not limited to a processing apparatus such as a microprocessor MCU or programmable logic device) and a memory 104 for storing data, wherein the above-mentioned computer device can further include a transmission device 106 for communication function and an input and output device 108. Those skilled in the art can understand that the structure shown in FIG. 1 is only schematic, which does not limit the structure of the above-mentioned computer device. For example, the computer device can further include more or less components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1.

[0023] The memory 104 can be used to store computer programs, such as software programs of application software and modules, such as a computer program corresponding to the service processing method in the embodiments of the present disclosure. The processor 102 can execute various functions of the application and the single board matching by running the computer program stored in the memory 104, that is, implement the method described above. The memory 104 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, and the remote memory can be connected to the computer device through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0024] The transmission device 106 is configured to receive or send data via a network. The specific examples of the network can include a wireless network provided by a communication provider of the computer device. In one example, the transmission device 106 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is configured to communicate with the Internet in a wireless manner.

[0025] In the present embodiment, a service processing method running on the computer device is provided. FIG. 2 is a flowchart of the service processing method according to the embodiments of the present disclosure. As shown in FIG. 2, the method is applied to a first converged UDM / HSS, and the flow includes the following steps:

[0026] In step S202, a service request message is received, and the service request message carries a user identifier.

[0027] In step S204, a URF component is used to determine user data routing information corresponding to the user identifier.

[0028] In step S206, based on the user data routing information, the service request message is sent to a stock HLR / HSS processor or a second converged UDM / HSS processor through a pre-established internal data channel. The second converged UDM / HSS is one or more converged UDM / HSSs.

[0029] The embodiment of the present disclosure receives a service request message, wherein the service request message carries a user identifier; determines user data routing information corresponding to the user identifier through a deployed user routing function (URF) component; and sends the service request message to a stock HLR / HSS processor or a second converged UDM / HSS processor through a pre-established internal data channel based on the user data routing information, wherein the second converged UDM / HSS is one or more converged UDM / HSSes, and the problem of low service processing performance after multiple sets of HLR / HSSs and UDM / HSSs are converged in the related art can be solved, and the user data access process can be implemented once based on the URF component, thereby improving the service processing performance.

[0030] In an embodiment, the step S204 can specifically include:

[0031] S2041, determining, by the URF component, a number segment type corresponding to the user identifier.

[0032] S2042, acquiring, by the URF component, user data routing information corresponding to the user identifier according to the number segment type.

[0033] In the embodiment of the present disclosure, S2042 can specifically include: in the case of a fixed number segment, querying and acquiring, from a user data routing information list, user data routing information corresponding to the number segment corresponding to the user identifier preconfigured; and in the case of a discrete number segment, configuring the user data routing information corresponding to the user identifier according to the remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, or acquiring the user data routing information corresponding to the number segment corresponding to the user identifier.

[0034] In the embodiment of the present disclosure, the URF component defines the number segment of the user (identifier) into a fixed number segment and a discrete number segment in order to realize efficient user positioning, wherein the fixed number segment is a routing device local direction of the user number segment that is fixed. Data access can be directly performed by reading and writing data configured in the corresponding local direction. When the HLR / HSS and UDM / HSS devices are converged, the respective fixed number segments can be configured according to the capacity of the devices, and the user data is pre-allocated to different devices. The discrete number segment is a routing device local direction of the user number segment that is uncertain, and each discrete number segment supports configuring a default routing local direction.

[0035] Further, in the case that the service request message is used to request to create data, the corresponding user data routing information is configured for the user identity according to the remaining capacity of the inventory HLR / HSS or the second converged UDM / HSS, and the user data routing information is set as the default user data routing information of the number segment corresponding to the user identity; in the case that the service request message is used to request to read or modify data, the user data routing information corresponding to the number segment corresponding to the user identity is acquired; in the case that the service request message is used to request to migrate data, the migrated user data routing information is configured for the user identity according to the remaining capacity of the inventory HLR / HSS or the second converged UDM / HSS.

[0036] In an embodiment, the acquiring of the user data routing information corresponding to the number segment corresponding to the user identity can specifically include: if a routing record corresponding to the user identity is queried, acquiring the user data routing information corresponding to the user identity in the routing record, wherein the routing record is used to record the correspondence between the user identity and the user data routing information; and if the routing record corresponding to the user identity is not queried, acquiring the default user data routing information of the number segment corresponding to the user identity.

[0037] In an embodiment, after the step S206, the method further includes: in the case that the service request message is a signaling service request, reading and writing the user data in the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to the user data routing information corresponding to the user identity through an internal data channel, and returning a service signaling response. If the service request message is a service request, a service acceptance response can be directly returned.

[0038] In an embodiment, the method further includes:

[0039] In the case that the service request message is a service request used to request to create data, after the service request is accepted successfully, a routing record corresponding to the user identity is added through a URF component, and a service acceptance response is returned;

[0040] In the case that the service request is a service request used to request to migrate data, the user data in the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identity is migrated to the converged UDM / HSS corresponding to the migrated user data routing information, and a service acceptance response is returned.

[0041] Further, the user data corresponding to the user identifier is extracted from the inventory HLR / HSS process corresponding to the original user data routing information or the second converged UDM / HSS, the extracted user data is written into the converged UDM / HSS corresponding to the migrated user data routing information, the user data in the inventory HLR / HSS process corresponding to the original user data routing information or the second converged UDM / HSS is deleted, the original user data routing information corresponding to the user identifier is updated to the migrated user data routing information, and a service processing response is returned.

[0042] In an embodiment, the method further includes: establishing an internal routing data channel with the second converged UDM / HSS; and synchronizing, through the internal routing data channel, the user data routing information corresponding to the user identifier to the second converged UDM / HSS, so as to select an alternative from the first converged UDM / HSS when the first converged UDM / HSS fails.

[0043] The URF component is introduced in the embodiments of the present disclosure, the URF component stores user routing information, does not need to store user subscription data information, data is lightweight, and can support storage of a large amount of user routing information. Based on the routing interface of the URF component, the user data access process can be located once, thereby avoiding an inefficient processing mode of repeated attempts between local points of various HLR / HSSs and UDM / HSSs. When a service processing arrives at the converged UDM / HSS, the service processing provides a user routing query function based on the URF, and the user data storage local point is located once, thereby realizing fast service processing and avoiding repeated attempts between local points. When service signaling arrives at the UDM / HSS service module, the service processing provides a user routing query function based on the URF, and the user data storage local point is located once, thereby realizing fast service processing and avoiding repeated Relay forwarding between local points. The remaining capacity of each set of HLR / HSS and UDM / HSS local point devices is subscribed, and the URF component provides a user routing allocation function when a card is opened and a number is dialed, and the data storage local point is dynamically allocated according to the remaining capacity of the existing network device, thereby solving the problem of uneven allocation of capacities of different local point devices and improving the utilization rate of the converged local point devices.

[0044] The embodiments of the present disclosure can be applied to a smooth capacity expansion scenario, the capacity and performance of the inventory HLR / HSS local point have reached a bottleneck, and the old device needs to be replaced, the new user needs to be managed by a cloud-based UDM / HSS, and the inventory HSS and the newly built cloud-based UDM / HSS coexist in the network. The embodiments of the present disclosure can realize smooth capacity expansion, can effectively avoid the risk of the operator initiating a bidding process, and avoid relocation of the inventory device.

[0045] The embodiments of the present disclosure can also be applied to a smooth 5G evolution scenario, user EPC / IMS / 5G data needs to be managed in fusion, the inventory HSS cannot be upgraded to support 5G, and this scenario needs to build a cloud UDM / HSS to smoothly evolve to 5G, and the inventory HSS and the newly built cloud IWF / UDM / HSS coexist in networking. Through the embodiments of the present disclosure, smooth evolution can be realized without equipment relocation, which can effectively avoid the re-tendering initiated by the operator and protect the existing inventory market.

[0046] The embodiments of the present disclosure can also be applied to a smooth VOLTE evolution scenario, the inventory HSS has no IMS network element, and there is no expansion or reconstruction power. At this time, it is also hoped that the existing HSS will continue to allocate numbers. The inventory HSS has an IMS network element, but the capacity is insufficient, and there is no expansion space or expansion power. For the scenario of IMS service demand, through the embodiments of the present disclosure, automatic migration to the newly built V7 UDM / HSS can be realized, and smooth evolution of VoLTE service can be realized.

[0047] The embodiments of the present disclosure can also be applied to a smooth cut-scene, the life cycle of the inventory HSS software and hardware has ended, and the user data needs to be cut off from the inventory HLR / HSS to the fusion UDM / HSS in batches according to the number segment and the scattered number. Through the embodiments of the present disclosure, external dependence can be realized, and the user has no basic perception. The high-risk large-scale user cut-off operation is converted into low-risk user-by-user smooth migration.

[0048] The embodiments of the present disclosure can also combine a super-capacity fusion UDM / HSS. With the advent of the Internet of Everything era, the fusion UDM / HSS potentially exists a massive user data storage demand. At this time, the amount of data that needs to be stored may reach the upper limit of the system software and hardware of a set of fusion UDM / HSS. Through the embodiments of the present disclosure, the combination of multiple sets of fusion UDM / HSS can be realized, and a super-capacity fusion UDM / HSS can be realized.

[0049] The embodiments of the present disclosure establish an internal data access channel between each fusion UDM / HSS and the inventory HLR / HSS, and establish a user routing data layer and an access channel between the fusion UDM / HSS devices. After the reception and service signaling enters the fusion UDM / HSS, it is first located through the URF in the routing layer, and then the internal data access channel can quickly read and write data to complete the reception and service operation. FIG. 3 is a structural schematic diagram of device fusion according to the embodiments of the present disclosure, as shown in FIG. 3, comprising:

[0050] The BOSS 31 is a support system for the operation of the operator's business, which can subscribe to the user 2 / 3 / 4 / 5G related business functions. The communication protocol based on the reception interface between 31 and 33 is SOAP / REST / MML, etc.

[0051] The inventory HLR / HSS 32 provides 2 / 3 / 4G user mobile network user mobility management and authentication function. The internal data channel between 802 and 803 is based on SCTP / TCP construction.

[0052] The fusion HSS / UDM1 33 provides 2 / 3 / 4 / 5G user mobile network user mobility management and authentication function, and the fusion HSS / UDM1 33 contains the URF device 35.

[0053] The fusion HSS / UDM2 34 is optionally deployed and has the same function as the fusion HSS / UDM1 33. The fusion HSS / UDM2 34 contains the URF device 36. Multiple sets of UDM / HSS can constitute a UDM Lake and are deployed in a large-capacity fusion UDM / HSS demand scenario. The internal user data channel and the internal routing data channel between 33 and 34 are based on SCTP / TCP.

[0054] The URF device 35 provides efficient handling or service user routing positioning function through the URF component. The URF routing data is based on the distributed file database storage developed by ZTE. The routing data channel between the URF device 35 and the URF device 36 is based on SCTP.

[0055] The URF device 36 is optional and has the same function as the URF device 35 and is deployed in a large-capacity fusion UDM / HSS demand scenario. The URF data in all fusion UDM / HSS sites is synchronized in real time to ensure data consistency.

[0056] The DRA / STP 37 of the signaling network sends a MAP / Diameter signaling request to the fusion UDM / HSS. The fusion UDM / HSS obtains the routing of user data according to the URF to read and write user data and complete the signaling processing.

[0057] The 5G core network 38 includes other network functions such as AMF / SMF and sends a signaling request to the fusion UDM / HSS. The fusion UDM / HSS obtains the routing of user data according to the URF to read and write user data and complete the signaling processing.

[0058] When opening a card / number, the storage routing direction of new data needs to be confirmed according to the remaining capacity of the equipment. After the opening of the card / number is successful, if the allocated routing is consistent with the default routing direction, the URF does not need to generate a routing record; if the allocated routing is inconsistent with the default routing direction, the URF needs to generate a routing record.

[0059] In data access, the URF first confirms the access station by querying the routing record, and if it exists, it directly reads and writes user data processing services through the data access channel. If the routing record does not exist, it reads and writes user data processing services through the default routing station of the discrete number segment where the user is located. On the basis of ensuring accurate positioning of user routing, the storage of routing records is reduced.

[0060] FIG. 4 is a flowchart of a request to create data according to an embodiment of the present disclosure, as shown in FIG. 4, including:

[0061] Step S401, the BOSS sends a card opening / number releasing acceptance instruction to the fusion UDM / HSS;

[0062] Step S402, the fusion UDM / HSS, through the URF component, allocates user data routing information (routing station) of the card opening / number releasing according to the number segment type of the user identifier;

[0063] Specifically, according to the number segment type determined by the user identifier in the acceptance instruction, if it is a fixed number segment, it means that the data distribution is configured in advance, and the user data routing information of the data storage is directly allocated based on the configuration; if it is a discrete number segment, through the URF component, based on the remaining capacity of the fusion UDM / HSS and the inventory HLR / HSS collected periodically, the data is preferentially allocated to the storage with larger remaining capacity, and if the remaining capacity of the inventory HLR / HSS is insufficient, it is allocated to the inventory HLR / HSS.

[0064] Step S403, send the acceptance instruction to the inventory HLR / HSS corresponding to the user data routing information through the internal data channel for execution;

[0065] Step S404, after the card opening / number releasing acceptance is successful, write the routing record of the new card / number through the URF component;

[0066] Step S405, return the acceptance response to the BOSS.

[0067] FIG. 5 is a flowchart of a request to read or modify data according to an embodiment of the present disclosure, as shown in FIG. 5, including:

[0068] Step S501, the BOSS sends a normal acceptance instruction (i.e., for requesting to read or modify data) to the fusion UDM / HSS;

[0069] Step S502, the fusion UDM / HSS, through the URF component, queries the user data routing information according to the user identifier;

[0070] Specifically, according to the user identifier in the acceptance instruction, the number segment type defined by the identifier is confirmed; if it is a fixed number segment, it means that the data distribution is predefined, and the user data routing information of the data storage is directly allocated based on the configuration; if it is a discrete number segment, the URF component first queries the routing record through the user identifier, and if the query is successful, the user data routing information in the routing record is used; if the query fails, the default user data routing information configured by the number segment is returned.

[0071] Step S503, the converged UDM / HSS sends the acceptance instruction to the inventory HLR / HSS corresponding to the user data routing information through an internal data channel for execution;

[0072] Step S504, the converged UDM / HSS returns an acceptance response to the BOSS.

[0073] FIG. 6 is a flowchart of requesting migration data according to an embodiment of the present disclosure, as shown in FIG. 6, comprising:

[0074] Step S601, the BOSS sends a data migration instruction to the converged UDM / HSS;

[0075] Step S602, the converged UDM / HSS queries the user data routing information according to the user identifier through the URF component, and allocates new user data routing information of the converged UDM / HSS;

[0076] Step S603, the converged UDM / HSS acquires the user data in the inventory HLR / HSS through an internal data channel;

[0077] Step S604, the converged UDM / HSS writes the user data of the inventory HLR / HSS into the new converged UDM / HSS;

[0078] Step S605, the converged UDM / HSS updates the migrated user data routing information through the URF component;

[0079] Step S606, the converged UDM / HSS deletes the user data in the inventory HLR / HSS;

[0080] Step S607, the converged UDM / HSS returns an acceptance response to the BOSS.

[0081] FIG. 7 is a flowchart of requesting signaling service according to an embodiment of the present disclosure, as shown in FIG. 7, comprising:

[0082] Step S701, the STP / DRA / AMF sends a signaling service request to the converged UDM / HSS;

[0083] Step S702, the converged UDM / HSS queries the user data routing information according to the user identifier through the URF component;

[0084] In step S703, the converged UDM / HSS reads and writes user data through an internal data channel to complete signaling service processing.

[0085] In step S704, the converged UDM / HSS returns a signaling service response to the STP / DRA / AMF.

[0086] The embodiments of the present disclosure further provide a service processing apparatus. FIG. 8 is a block diagram of a service processing apparatus according to an embodiment of the present disclosure. As shown in FIG. 8, the apparatus is applied to a first converged UDM / HSS and includes:

[0087] A receiving module 82 is configured to receive a service request message, wherein the service request message carries a user identifier.

[0088] A determining module 84 is configured to determine user data routing information corresponding to the user identifier through a user routing function (URF) component.

[0089] A sending module 86 is configured to send the service request message to a stock HLR / HSS or a second converged UDM / HSS for processing through a pre-established internal data channel based on the user data routing information, wherein the second converged UDM / HSS is one or more converged UDM / HSSs.

[0090] In an embodiment, the determining module 84 includes:

[0091] A determining sub-module is configured to determine a number segment type corresponding to the user identifier through the URF component.

[0092] An obtaining sub-module is configured to obtain the user data routing information corresponding to the user identifier according to the number segment type through the URF component.

[0093] In an embodiment, the obtaining sub-module includes:

[0094] An obtaining unit is configured to, in a case where the number segment type is a fixed number segment, query and obtain, from a user data routing information list, user data routing information corresponding to a number segment corresponding to the user identifier which is pre-configured.

[0095] A configuring unit is configured to, in a case where the number segment type is a discrete number segment, configure corresponding user data routing information for the user identifier according to a remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, or obtain user data routing information corresponding to a number segment corresponding to the user identifier.

[0096] In an embodiment, the configuration unit is further configured to, in a case where the service request message is used to request creation of data, configure corresponding user data routing information for the user identifier according to the remaining capacity of the inventory HLR / HSS or the second converged UDM / HSS, and set the user data routing information as default user data routing information corresponding to the number segment of the user identifier; in a case where the service request message is used to request reading or modification of data, acquire user data routing information corresponding to the number segment of the user identifier; and in a case where the service request message is used to request migration of data, configure migrated user data routing information for the user identifier according to the remaining capacity of the inventory HLR / HSS or the second converged UDM / HSS.

[0097] In an embodiment, the configuration unit is further configured to, if the routing record corresponding to the user identifier is queried, acquire user data routing information corresponding to the user identifier in the routing record, wherein the routing record is used to record the correspondence between a user identifier and user data routing information; and if the routing record corresponding to the user identifier is not queried, acquire default user data routing information of the number segment of the user identifier.

[0098] In an embodiment, the apparatus further comprises:

[0099] The read-write module is configured to, in a case where the service request message is a signaling service request, read and write user data in the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to the user data routing information corresponding to the user identifier through the internal data channel, and return a service signaling response.

[0100] In an embodiment, the apparatus further comprises:

[0101] The adding module is configured to, in a case where the service request message is an accepted service request used to request creation of data, add, after the accepted service request is accepted successfully, a routing record corresponding to the user identifier through the URF, and return a service acceptance response.

[0102] The migration module is configured to, in a case where the accepted service request is an accepted service request used to request migration of data, migrate user data in the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to original user data routing information of the user identifier to a converged UDM / HSS corresponding to migrated user data routing information, and return a service acceptance response.

[0103] The migration module is further configured to extract user data from the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identifier, write the extracted user data into the converged UDM / HSS corresponding to the migrated user data routing information, delete the user data in the inventory HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information, and update the original user data routing information corresponding to the user identifier to the migrated user data routing information, and return a service response.

[0104] In an embodiment, the apparatus further comprises:

[0105] The establishing module is configured to establish an internal routing data channel with the second converged UDM / HSS.

[0106] The synchronizing module is configured to synchronize the user data routing information corresponding to the user identifier to the second converged UDM / HSS through the internal routing data channel.

[0107] Embodiments of the present disclosure further provide a computer program product comprising computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0108] Embodiments of the present disclosure further provide a computer readable storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0109] In an example embodiment, the above computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0110] Embodiments of the present disclosure further provide an electronic device comprising a memory having stored therein a computer program and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.

[0111] In an example embodiment, the above electronic device can further comprise a transmission device connected to the processor and an input / output device connected to the processor.

[0112] Specific examples in the present embodiment can refer to the examples described in the above embodiments and example implementations, which will not be described herein again.

[0113] It should be apparent to those skilled in the art that the modules or steps of the present disclosure described above can be implemented with general computing devices, which can be centralized on a single computing device or distributed on a network of multiple computing devices, which can be implemented with program codes executable by the computing devices, so that they can be stored in storage devices and executed by the computing devices, and in some cases, the steps shown or described can be executed in different orders than shown, or they can be made into individual integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0114] The preferred embodiments of the present disclosure are described above, but the present disclosure is not limited to the above. Those skilled in the art can make various modifications and changes to the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A service processing method applied to a first converged unified data management / home subscriber server (UDM / HSS), the method comprising: receiving a service request message, wherein the service request message carries a user identity; determining, by a user routing function (URF) component, user data routing information corresponding to the user identity; sending, based on the user data routing information, the service request message to a stock home location register / home location register (HLR / HSS) or a second converged UDM / HSS for processing, wherein the second converged UDM / HSS is one or more converged UDM / HSSs.

2. The method of claim 1, wherein, The determining, by the URF component, of the user data routing information corresponding to the user identity comprises: determining, by the URF component, a number segment type corresponding to the user identity; obtaining, by the URF component, the user data routing information corresponding to the user identity according to the number segment type.

3. The method of claim 2, wherein, The obtaining of the user data routing information corresponding to the user identity according to the number segment type comprises: in a case where the number segment type is a fixed number segment, querying and obtaining, from a list of user data routing information, user data routing information corresponding to a number segment corresponding to the user identity, which is pre-configured; in a case where the number segment type is a discrete number segment, configuring the user data routing information corresponding to the user identity according to a remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, or obtaining the user data routing information corresponding to the number segment corresponding to the user identity.

4. The method of claim 3, wherein, The configuring of the user data routing information corresponding to the user identity according to the remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, or the obtaining of the user data routing information corresponding to the number segment corresponding to the user identity comprises: in a case where the service request message is used to request creation of data, configuring the user data routing information corresponding to the user identity according to the remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, and setting the user data routing information as default user data routing information of the number segment corresponding to the user identity; in a case where the service request message is used to request reading or modification of data, obtaining the user data routing information corresponding to the number segment corresponding to the user identity; in a case where the service request message is used to request migration of data, configuring, according to the remaining capacity of the stock HLR / HSS or the second converged UDM / HSS, user data routing information after migration for the user identity.

5. The method of claim 3 or 4, wherein, The obtaining of the user data routing information corresponding to the number segment corresponding to the user identity comprises: if a routing record corresponding to the user identity is queried, obtaining user data routing information corresponding to the user identity in the routing record, wherein the routing record is used to record a correspondence between a user identity and user data routing information; if the routing record corresponding to the user identity is not queried, obtaining default user data routing information of the number segment corresponding to the user identity.

6. The method of claim 1, wherein, After routing the service request message to the legacy HLR / HSS processing or the second converged UDM / HSS processing through the pre-established internal data channel based on the user data routing information, the method further comprises: In the case that the service request message is a signaling service request, reading and writing user data in the legacy HLR / HSS processing or the second converged UDM / HSS corresponding to the user data routing information corresponding to the user identification through the internal data channel, and returning a service signaling response.

7. The method of claim 1, wherein, The method further comprises: In the case that the service request message is a service request for requesting to create data, after the service request is accepted successfully, adding a routing record corresponding to the user identification through the URF component, and returning a service acceptance response; In the case that the service request is a service request for requesting to migrate data, migrating user data in the legacy HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identification to the converged UDM / HSS corresponding to the migrated user data routing information, and returning a service acceptance response.

8. The method of claim 7, wherein, Migrating user data in the legacy HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identification to the converged UDM / HSS corresponding to the migrated user data routing information comprises: extracting user data from the legacy HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identification; writing the extracted user data into the converged UDM / HSS corresponding to the migrated user data routing information; deleting user data in the legacy HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information; updating the original user data routing information corresponding to the user identification to the migrated user data routing information, and returning a service acceptance response.

9. A computer-readable storage medium having stored therein a computer program, wherein, The computer program is configured to execute the method described in any one of claims 1 to 8 when running. 10.An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to perform the method described in any one of claims 1 to 8.

Images