Business processing method, storage medium and electronic device

Abstract

The embodiment of the invention provides a service processing method, a storage medium and an electronic device, and the method comprises the steps: receiving a service request message which carries a user identifier; determining user data routing information corresponding to the user identifier through a user routing function (URF) component; the service request message is sent to a stock HLR / HSS to be processed or a second fusion UDM / HSS to be processed through a pre-established internal data channel based on user data routing information, the second fusion UDM / HSS is one or more fusion UDM / HSS, the problem that in the related technology, after multiple sets of HLR / HSS and UDM / HSS are fused, the service processing performance is low can be solved, and the service processing efficiency is improved based on the URF component. One-time positioning can be achieved in the user data access process, and the service processing performance is improved.

Description

TECHNICAL FIELD

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

[0002] 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 used to store original 2 / 3 / 4G user data, its associated system includes an operator BOSS (Business Operation Support System) and a signaling gateway device DRA (Diameter Routing Agent) / STP (Signaling 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 the UDM and the 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.

[0003] 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

[0004] Embodiments of the present application provide a service processing method, a storage medium and an 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.

[0005] According to an embodiment of the present application, a service processing method is provided, applied to a first fusion UDM / HSS, and the method comprises:

[0006] receiving a service request message, wherein the service request message carries a user identifier;

[0007] determine, by a deployed User Routing Function (URF) component, user data routing information corresponding to the user identifier;

[0008] send, based on the user data routing information, the service request message to a legacy 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 another embodiment of the present application, a service processing apparatus is provided, applied to a first converged UDM / HSS, the apparatus comprising:

[0010] a receiving module configured to receive a service request message, wherein the service request message carries a user identifier;

[0011] a determining module configured to determine, by a deployed URF component, user data routing information corresponding to the user identifier;

[0012] a sending module configured to send, based on the user data routing information, the service request message to a legacy 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.

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

[0014] According to still another embodiment of the present application, a computer readable storage medium is provided, wherein the storage medium stores a computer program, and the computer program is configured to execute the steps in any of the above method embodiments when running.

[0015] According to still another embodiment of the present application, an electronic device is provided, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any of the above method embodiments.

[0016] The embodiment of the present application 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 method can solve the problem of low service processing performance after multiple sets of HLR / HSS and UDM / HSS are converged in the related art, and the user data access process can be implemented once based on the URF component, thereby improving the service processing performance. BRIEF DESCRIPTION OF DRAWINGS

[0017] Figure 1 is a hardware structure block diagram of a computer device of a service processing method according to an embodiment of the present application;

[0018] Figure 2 is a flowchart of a service processing method according to an embodiment of the present application;

[0019] Figure 3 is a structure diagram of device convergence according to an embodiment of the present application;

[0020] Figure 4 is a flowchart of a request to create data according to an embodiment of the present application;

[0021] Figure 5 is a flowchart of a request to read or modify data according to an embodiment of the present application;

[0022] Figure 6 is a flowchart of a request to migrate data according to an embodiment of the present application;

[0023] Figure 7 is a flowchart of a request for signaling service according to an embodiment of the present application;

[0024] Figure 8 is a block diagram of a service processing apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

[0027] The method embodiments provided in the embodiments of the present application can be executed in a computer device or a similar computing device. Taking an example of running on a computer device,Figure 1 is a hardware structure block diagram of a computer device of a service processing method of an embodiment of the present application, as shown in the figure, the computer device can include one or more (only one is shown in the figure) processors 102 (the processor 102 can include but is not limited to a processing device 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 the figure 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 the figure, or have a different configuration from that shown in the figure. Figure 1 Figure 1 Figure 1 Figure 1 Figure 1

[0028] The memory 104 can be used to store computer programs, for example, software programs of application software and modules, such as the computer program corresponding to the service processing method in the embodiment of the present application. The processor 102 performs various functional applications and single board matching by running the computer program stored in the memory 104, that is, implements the above-mentioned method. 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, which can be connected to the computer device through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0029] The transmission device 106 is used to receive or send data via a network. The specific examples of the above-mentioned 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 (Network Interface Controller, 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 (Radio Frequency, RF) module, which is used to communicate with the Internet in a wireless manner.

[0030] In the embodiment, a service processing method running on the above-mentioned computer device is provided, Figure 2 is a flow chart of the service processing method according to the embodiment of the present application, as shown in the figure, applied to a first converged UDM / HSS, the flow includes the following steps: Figure 2

[0031] ​​​​​​Step S202, receiving a service request message, wherein the service request message carries a user identifier;

[0032] Step S204, determining, by a URF component, user data routing information corresponding to the user identifier;

[0033] Step S206, 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, wherein the second converged UDM / HSS is one or more converged UDM / HSS.

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

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

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

[0037] In the embodiment, 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 a number segment corresponding to the user identifier, which is pre-configured; in the case of a discrete number segment, configuring the user data routing information corresponding to the user identifier according to a 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.

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

[0039] 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.

[0040] 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.

[0041] 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.

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

[0043] 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;

[0044] 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.

[0045] 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.

[0046] 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.

[0047] Embodiments of the present application introduce a URF component, which stores user routing information and does not need to store user subscription data information, is lightweight in data, and can support storage of a large amount of user routing information. Based on a routing interface of the URF component, a user data access process can achieve one-time positioning, thereby avoiding inefficient processing modes that need to be repeatedly attempted between various HLR / HSSs and UDM / HSSs. When a service processing arrives at a converged UDM / HSS, the service processing is based on a user routing query function provided by the URF to one-time position to a storage location of user data, thereby achieving fast service processing without repeated attempts between various locations. When service signaling arrives at a UDM / HSS service module, the service processing is based on a user routing query function provided by the URF to one-time position to a storage location of user data, thereby achieving fast service processing without repeated Relay forwarding between various locations. The remaining capacity of each set of HLR / HSS and UDM / HSS location devices is subscribed, and the URF component provides a user routing allocation function when a card is opened and a number is released, and dynamically allocates a data storage location according to the remaining capacity of the existing network device, thereby solving the problem of uneven allocation of capacities of different location devices and improving the utilization rate of the converged location device.

[0048] Embodiments of the present application can be applied to a smooth capacity expansion scenario, in which inventory HLR / HSS location capacities and performances have reached a bottleneck and old devices need to be replaced, new cloud-based UDM / HSS devices need to be built to manage new users, and inventory HSSs and newly-built cloud-based UDM / HSSs coexist in a network. Through embodiments of the present application, smooth capacity expansion can be achieved, and the risk of relocation of inventory devices can be avoided.

[0049] The embodiment of the application can also be applied to a smooth 5G evolution scenario, user EPC / IMS / 5G data needs to be managed in an integrated manner, the inventory HSS cannot be upgraded to support 5G, and this scenario needs to build a cloud-based UDM / HSS to smoothly evolve to 5G, and the inventory HSS and the newly built cloud-based IWF / UDM / HSS coexist in a mixed network. The embodiment of the application can achieve smooth evolution without equipment relocation, and can effectively avoid the re-tendering initiated by the operator and protect the existing inventory market.

[0050] The embodiment of the application 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 motivation. At this time, it is also desired to continue to allocate numbers using the existing HSS. The inventory HSS has an IMS network element, but the capacity is insufficient, and there is no expansion space or expansion motivation. For the scenario of IMS service demand, the embodiment of the application can achieve automatic migration to the newly built V7 UDM / HSS, and realize smooth evolution of VoLTE services.

[0051] The embodiment of the application can also be applied to a smooth cut-over scenario. The life cycle of the inventory HSS software and hardware has almost ended, and it is necessary to batch cut over user data to the integrated UDM / HSS according to number segments and scattered numbers. The embodiment of the application can realize external independence and user basic non-perception, and convert high-risk bulk user cut-over operations into low-risk user-by-user smooth migration.

[0052] The embodiment of the application can also combine a super-capacity integrated UDM / HSS. With the advent of the Internet of Everything era, the integrated UDM / HSS potentially has massive user data storage requirements. 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 integrated UDM / HSS. The embodiment of the application can achieve the combination of multiple sets of integrated UDM / HSS, and realize a super-capacity integrated UDM / HSS.

[0053] The embodiment of the application establishes an internal data access channel between each integrated UDM / HSS and the inventory HLR / HSS, and establishes a user routing data layer and an access channel between the integrated UDM / HSS devices. After the reception and service signaling enters the integrated UDM / HSS, it is first located through the URF in the routing layer, and then the internal data access channel can be quickly read and written to complete the reception and service operation. Figure 3 It is a structural schematic diagram of the device integration according to the embodiment of the application, as shown in Figure 3 , comprising:

[0054] The BOSS 31 is a support system for the operation of the operator's business, and can sign up for 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.

[0055] 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.

[0056] The fusion HSS / UDM 133 provides 2 / 3 / 4 / 5G user mobile network user mobility management and authentication function, and the fusion HSS / UDM 133 comprises a URF device 35.

[0057] The fusion HSS / UDM 234 is optionally deployed and has the same function as the fusion HSS / UDM 133. The fusion HSS / UDM 234 comprises a URF device 36. Multiple sets of UDM / HSS can constitute a UDM Lake and are deployed in a super 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.

[0058] The URF device 35 provides efficient handling or service user routing positioning function through a URF component. The URF routing data is based on a 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.

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

[0060] 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 signaling processing.

[0061] The 5G core network 38 comprises 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 signaling processing.

[0062] When opening a card / number, the storage routing area 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 area, the URF does not need to generate a routing record. If the allocated routing is inconsistent with the default routing area, the URF needs to generate a routing record.

[0063] During data access, the URF first checks the access direction by querying the routing record. If the record 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 direction of the user's discrete number segment. This approach ensures accurate user routing while minimizing the storage of routing records.

[0064] Figure 4 This is a flowchart illustrating the creation of data according to an embodiment of this application, such as... Figure 4 As shown, it includes:

[0065] Step S401: BOSS sends an activation / number release application instruction to the fused UDM / HSS;

[0066] Step S402: Integrate UDM / HSS and, through the URF component, allocate user data routing information (routing direction) for SIM card activation / number release based on the number segment type of the user identifier;

[0067] Specifically, the number segment type defined by the identifier is determined according to the user representation in the acceptance instruction. If it is a fixed number segment, it means that the data distribution is configured and predefined, and the user data routing information for data storage is directly allocated based on the configuration. If it is a discrete number segment, the URF component is used to allocate the data to the storage with larger remaining capacity based on the remaining capacity of the periodically collected converged UDM / HSS and existing HLR / HSS. If the remaining capacity of the existing HLR / HSS is less, the data is allocated to the existing HLR / HSS.

[0068] Step S403: Send the acceptance instruction to the existing HLR / HSS corresponding to the user data routing information through the internal data channel for execution;

[0069] Step S404: After successful card opening / number issuance, the routing record for the new card / number is written through the URF component;

[0070] Step S405: Return an acceptance response to BOSS.

[0071] Figure 5 This is a flowchart illustrating the request to read or modify data according to an embodiment of this application, such as... Figure 5 As shown, it includes:

[0072] Step S501: BOSS sends a normal acceptance instruction (i.e., used to request to read or modify data) to the fused UDM / HSS.

[0073] Step S502: Integrate UDM / HSS and query user data routing information based on user identifier through the URF component;

[0074] Specifically, the number segment type defined by the user identifier in the acceptance instruction is confirmed. If it is a fixed number segment, it means that the data distribution is predefined, and the user data routing information for 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. If the query is successful, the user data routing information in the routing record is used. If the query is unsuccessful, the default user data routing information configured for the number segment is returned.

[0075] Step S503: The integrated UDM / HSS sends the acceptance instruction to the existing HLR / HSS corresponding to the user data routing information through the internal data channel for execution;

[0076] Step S504: The UDM / HSS is integrated to return an acceptance response to the BOSS.

[0077] Figure 6 This is a flowchart of the request migration data according to an embodiment of this application, such as... Figure 6 As shown, it includes:

[0078] Step S601: BOSS sends a data migration instruction to the fused UDM / HSS;

[0079] Step S602: In the fusion of UDM / HSS, the user data routing information is queried based on the user identifier through the URF component, and new user data routing information for the fusion of UDM / HSS is allocated.

[0080] Step S603: The UDM / HSS is integrated to obtain user data from the existing HLR / HSS through the internal data channel;

[0081] Step S604: The merged UDM / HSS writes the user data from the existing HLR / HSS into the new merged UDM / HSS;

[0082] Step S605: The UDM / HSS is integrated to update the routing information of migrated user data through the URF component;

[0083] Step S606: Merge UDM / HSS to delete user data from existing HLR / HSS;

[0084] Step S607: The UDM / HSS is integrated to return an acceptance response to the BOSS.

[0085] Figure 7 This is a flowchart of the request signaling service according to an embodiment of this application, such as... Figure 7 As shown, it includes:

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

[0087] Step S702: Integrate UDM / HSS and query user data routing information based on user identifier through the URF component;

[0088] Step S703: The UDM / HS integrates user data through the internal data channel to complete signaling service processing;

[0089] Step S704: The UDM / HSS merges and returns a signaling service response to the STP / DRA / AMF.

[0090] This application also provides a business processing apparatus. Figure 8 This is a block diagram of a service processing apparatus according to an embodiment of this application, such as... Figure 8 As shown, the device, applied to a first fusion UDM / HSS, includes:

[0091] The receiving module 82 is used to receive a service request message, wherein the service request message carries a user identifier;

[0092] The determination module 84 is used to determine the user data routing information corresponding to the user identifier through the user routing function URF component;

[0093] The sending module 86 is used to send the service request message to the existing HLR / HSS processing or the second converged UDM / HSS 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 / HSS.

[0094] In one embodiment, the determining module 84 includes:

[0095] The determination submodule is used to determine the number segment type corresponding to the user identifier through the URF component;

[0096] The acquisition submodule is used to obtain user data routing information corresponding to the user identifier based on the number segment type through the URF component.

[0097] In one embodiment, the acquisition submodule includes:

[0098] The acquisition unit is used to query and obtain the user data routing information corresponding to the number segment corresponding to the user identifier from the user data routing information list when the number segment type is a fixed number segment;

[0099] The configuration unit is used to configure corresponding user data routing information for the user identifier based on the remaining capacity of the existing HLR / HSS or the second converged UDM / HSS when the number segment type is a discrete number segment, or to obtain user data routing information corresponding to the number segment corresponding to the user identifier.

[0100] In one embodiment, the configuration unit is further configured to: when the service request message is for requesting data creation, configure corresponding user data routing information for the user identifier based on the remaining capacity of the existing HLR / HSS or the second converged UDM / HSS, and set the user data routing information as the default user data routing information for the number segment corresponding to the user identifier; when the service request message is for requesting to read or modify data, obtain the user data routing information corresponding to the number segment corresponding to the user identifier; and when the service request message is for requesting to migrate data, configure migrated user data routing information for the user identifier based on the remaining capacity of the existing HLR / HSS or the second converged UDM / HSS.

[0101] In one embodiment, the configuration unit is further configured to, if a routing record corresponding to the user identifier is found, obtain user data routing information corresponding to the user identifier in the routing record, wherein the routing record is used to record the correspondence between the user identifier and the user data routing information; if no routing record corresponding to the user identifier is found, obtain default user data routing information for the number segment corresponding to the user identifier.

[0102] In one embodiment, the device further includes:

[0103] The read / write module is used to read and write user data in the existing HLR / HSS processing or the second converged UDM / HSS corresponding to the user identifier through the internal data channel when the service request message is a signaling service request, and return a service signaling response.

[0104] In one embodiment, the device further includes:

[0105] The module is used to add a routing record corresponding to the user identifier through the URF after the acceptance of the service request is successful, when the service request message is an acceptance service request for requesting data creation, and then return a service acceptance response.

[0106] The migration module is used to migrate the user data in the existing HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information corresponding to the user identifier to the converged UDM / HSS corresponding to the migrated user data routing information when the accepted service request is an accepted service request for requesting migration data, and return a service acceptance response.

[0107] The migration module is further configured to extract user data from the existing 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 existing HLR / HSS processing or the second converged UDM / HSS corresponding to the original user data routing information; update the original user data routing information corresponding to the user identifier to the migrated user data routing information, and return a service acceptance response.

[0108] In one embodiment, the device further includes:

[0109] Establishment module, used to establish an internal routing data channel with the second fused UDM / HSS;

[0110] The synchronization module is used to synchronize the user data routing information corresponding to the user identifier to the second fused UDM / HSS through the internal routing data channel.

[0111] This application also provides a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0112] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0113] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0114] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0115] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0116] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0117] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0118] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A service processing method characterized by, The method applied to a first converged unified data management / home subscriber server (UDM / HSS) comprises: receiving a service request message, wherein the service request message carries a user identifier; determining, by a user routing function (URF) component, user data routing information corresponding to the user identifier; 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 identifier comprises: determining, by the URF component, a number segment type corresponding to the user identifier; obtaining, by the URF component, the user data routing information corresponding to the user identifier 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 identifier 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 user data routing information list, user data routing information corresponding to a number segment corresponding to the user identifier, 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 identifier 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 identifier.

4. The method of claim 3, wherein, The configuring of 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 the obtaining of the user data routing information corresponding to the number segment corresponding to the user identifier 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 identifier 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 identifier; 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 identifier; 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 of the user identifier.

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

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 received service request for requesting to create data, after the received 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 received service request is a received 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, characterized in that, The storage medium has stored therein a computer program, wherein the computer program is configured to execute the method recited in any one of claims 1 to 8 when executed.

10. An electronic device, comprising: The apparatus comprises a memory and a processor, the memory has stored therein a computer program, and the processor is configured to execute the computer program to execute the method recited in any one of claims 1 to 8.

Images