Detailed Description
In order to make the technical problems, technical solutions and advantageous effects to be solved by the present application clearer and clearer, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
First embodiment
To better illustrate the present embodiment, the following describes the problems of the prior art with reference to fig. 1 and 2:
as shown in fig. 1, a schematic diagram of a network architecture of a 5G core network is defined in a 3GPP (3rd Generation Partnership Project) TS 23.501 protocol, and the UDM is located in the HPLMN and has functions of calculating a user authentication vector, user mobility management, and user subscription data management.
Fig. 2 is a schematic diagram of a mobility management operation timing structure of a conventional 5G mobile communication network, which specifically includes:
step 101, each UDM configures user data routing information, when the UDM registers a service to an NRF (Network discovery Function), the UDM carries the user data routing information, the NRF caches the user data routing information to the local, the user data routing information refers to a corresponding relationship between a user number segment or number and a user attribution UDM, and the NRF provides the service registration and service discovery functions;
step 102, a user accesses an NF (Network Function), such as an AMF (Access Management Function)/SMF (Session Management Function), and queries an NRF for UDM address information (e.g., IP address and port) according to a user identifier, such as IMSI (International Mobile Subscriber identity), MSISDN (Mobile Subscriber identity), etc.
Step 103, NRF returns user routing data home UDM address to user access NF.
And step 104, the user access NF sends an operation request to the user data attribution UDM.
And 105, after the UDM processes the operation request, returning an operation response to the NF accessed by the user.
The existing mobility management operation of the 5G mobile communication network has the following problems:
1) the operation and maintenance personnel need to configure user data routing information in a plurality of UDMs, the maintenance workload is large, the configuration of user number sections among the UDMs can be overlapped and collided, in order to reduce the workload of configuring the user data routing information, operators generally adopt the corresponding relation of the user number sections and the UDMs to be planned in advance, the user number sections with large range are configured in the user data routing information, but precious number resources are wasted, and when users change cards/numbers across the UDMs, the user data routing information needs to be changed or the user number sections need to be reserved for changing cards/numbers. The routing information of the user data is inaccurate, the user can not find the accurate UDM when accessing NF, the service operation fails, and the complaint of the user is caused.
2) Before the user access NF processes the mobility management operation related to the UDM, the user access NF and the NRF need to be inquired according to the user number to acquire the UDM, and the processing performance of the user access NF and the NRF is reduced.
Based on the problem of the mobility management operation of the existing 5G mobile communication network, as shown in fig. 3, a first embodiment of the present application provides a user routing method, where the method is used in a UDM, and the method includes:
step S21: and receiving an operation request sent by a user access network function NF.
In this embodiment, the user access NF is a network element of a user access class, such as AMF or SMF. And the user access NF sends an operation request to the UDM according to the address information of the UDM.
The user access NF can inquire the address information of the UDM nearby the network from the NRF, and the NRF returns the address information of the UDM. The address information of the UDM nearby the local network can be acquired from the local configuration, and the UDM does not need to be inquired to the NRF.
In this embodiment, the UDM is a network function defined by the 3GPP TS 23.501 protocol, and provides user authentication and user mobility management functions. The UDM provides all user mobility management services of the network, and determines the UDR where the user data is located, namely the home UDR, according to the automatically maintained user data routing information. The UDMs may be arranged in plurality on a capacity scale or regional basis.
Step S22: and determining an attribution Unified Data Repository (UDR) of the user data.
In this embodiment, the determining the home UDR of the user data includes:
determining the attribution UDR according to User Data Routing information stored in a User Routing Data Center (URDC) queried by a User identifier; or querying the user data routing information cached locally according to the user identification to determine the attribution UDR.
It can be understood that querying locally cached user data routing information can further improve UDM performance.
In this embodiment, the URDC is used to store user data routing information of the correspondence between the user identification and the UDR address (e.g., IP address, port number). The URDC can be independently deployed or can be deployed together with the UDM.
In this embodiment, the user data routing information includes a correspondence between a user identifier and a home UDR.
Step S23: and acquiring user data from the home UDR, and returning an operation response to the user access NF according to the user data.
In this embodiment, the UDR is a unified data storage function defined by the 3GPP TS 23.501 protocol, providing user data storage and management functions. Multiple UDRs may be deployed on a user capacity scale or regional basis. It should be noted that the UDR may be deployed in conjunction with the UDM, and the UDR may also be deployed separately from the UDM, which is not specifically limited herein.
In this embodiment, the acquiring user data from the home UDR includes:
accessing user data of the home UDR; and receiving the user data returned by the home UDR.
To better illustrate the present embodiment, the following describes the user routing process in conjunction with fig. 4-7:
as shown in fig. 4, the user routing system deployed in the HPLMN includes URDC31, UDM32, UDR33, andprovvision 34.
URDC31 for storing user data routing information for the correspondence of user identities and UDR addresses (e.g. IP addresses, port numbers).
UDM32 for providing user authentication, user mobility management functions.
UDR33 for providing user data storage and management functions.
The PROVISION34 is a user data acceptance subsystem, requests to create and store user data in the UDR33, and updates user data routing information in the URDC after successful operations of user number allocation, number selling, card changing and number changing.
Fig. 5 is a schematic diagram of a mobile subscriber routing process, in which:
step 401, the proxy executes service acceptance, and writes user data in the UDR.
Step 402, the proxy accepts successful operations of number allocation, number cancellation, card change and number change services, and notifies the URDC to change the user data routing information. For example: and (4) adding the corresponding relation between the IMSI/MSISDN number of the user and the UDR address when the number is released, deleting the user data routing information when the number is cancelled, and changing the user data routing information when the card is changed or the number is changed.
Step 403, the user accesses the NF to inquire the address information of the UDM of the local network to the NRF.
In step 404, the NRF returns the address information of the UDM of the home network.
In step 405, the user access NF sends an operation request to the local UDM.
And step 406, the UDM queries the URDC according to the user identifier to acquire a home UDR of the user data.
In step 407, the UDM accesses the user data of the home UDR.
In step 408, the UDR returns the user data access results to the UDM.
In step 409, the UDM returns the operation result to the user access NF.
Fig. 6 is a schematic diagram of a mobile roaming user routing process, in which:
step 501, a user accesses a VPLMN network; a user accesses NF to obtain a local network UDM nearby from NRF or local configuration; the user access NF sends an operation request to the local UDM.
Step 502, the UDM queries the URDC according to the user identifier to obtain the UDR to which the user data belongs.
In step 503, the UDM accesses the user data of the home UDR.
In step 504, the UDR returns the user data access results to the UDM.
And step 505, the UDM returns an operation result to the NF accessed by the user.
Fig. 7 is a schematic diagram illustrating a routing process of a mobile subscriber in a home network, wherein:
step 601, accessing a user to an HPLMN network; a user accesses NF to obtain a local network UDM nearby from NRF or local configuration; the user access NF sends an operation request to the local UDM.
Step 602, the UDM queries the URDC according to the user identifier, and obtains the UDR to which the user data belongs.
In step 603, the UDM accesses the user data of the home UDR.
In step 604, the UDR returns the user data access results to the UDM.
In step 605, the UDM returns the operation result to the user access NF.
In one embodiment, the determining a home UDR for user data further comprises:
sending an operation request for changing user data to the attributive UDR through a user data acceptance subsystem; and when the operation of changing the user data is successful, sending a user data routing information updating request to the URDC through the user data receiving subsystem.
In this embodiment, the operation of changing the user data includes at least one of a user number allocation operation, a user number cancellation operation, a user card exchange operation, and a user number exchange operation.
Illustratively, for the user number assignment operation, the URDC needs to add user data routing information; for user number cancellation operation, the URDC needs to delete user data routing information; for a card/number change operation, the URDC needs to modify the user data routing information.
For a better understanding of this embodiment, it is explained below with reference to fig. 8. Fig. 8 is a schematic diagram of a user data routing information updating process, where:
in step 701, the proxy (i.e., the user data acceptance subsystem) writes user data into the UDR, i.e., initiates an operation request (place number, pin number, card change, number change) for changing the user data.
In step 702, the UDR returns a change user data operation response to the proxy.
Step 703, proxy updates the user data routing information of the URDC.
For the number allocation operation, the URDC adds user data routing information;
for the pin operation, the URDC deletes the user data routing information;
for a card/number swap operation, the URDC modifies the user data routing information.
In another embodiment, the determining a home UDR for user data further comprises:
receiving a user data routing information update notification broadcast by the URDC; acquiring the updated user data routing information of the URDC according to the user data routing information updating notice; and storing the acquired user data routing information updated by the URDC to the local cache.
For a better understanding of this embodiment, it is explained below with reference to fig. 9. Fig. 9 is a schematic flow chart of routing information of UDM cache user data, where:
in step 801, after changing the user routing data information, the URDC broadcasts a user routing information change notification to the UDM of the home network.
In step 802, the UDM obtains the latest user routing data information to the URDC.
In step 803, the URDC returns the latest user routing data information to the UDM, which stores the latest user routing data information in a local cache.
According to the user routing method, the user data routing information is centralized in the HPLMN for automatic maintenance, and the user data routing information does not need to be configured in a plurality of UDMs; the operation and maintenance are simplified, the inconsistency between the user data routing information and the user data is avoided, the success rate of service operation is ensured, and the utilization rate of number resources is improved.
Second embodiment
As shown in fig. 10, a second embodiment of the present application provides a user routing method, where the method is used in a user access NF, and the method includes:
step S31: and sending an operation request to the UDM according to the address information of the UDM.
In this embodiment, the UDM is a network function defined by the 3GPP TS 23.501 protocol, and provides user authentication and user mobility management functions. The UDM provides all user mobility management services of the network, and determines the UDR where the user data is located, namely the home UDR, according to the automatically maintained user data routing information. The UDMs may be arranged in plurality on a capacity scale or regional basis.
In one embodiment, the sending an operation request to the UDM according to the address information of the UDM further includes:
acquiring address information of the UDM from NRF; or obtaining the address information of the UDM from local configuration.
Specifically, the user access NF may query the NRF for address information of the UDM in the vicinity of the home network, and the NRF returns the address information of the UDM. The address information of the UDM nearby the local network can be acquired from the local configuration, and the UDM does not need to be inquired to the NRF.
According to the user routing method, the user data routing information is centralized in the HPLMN for automatic maintenance, and the user data routing information does not need to be configured in a plurality of UDMs; the operation and maintenance are simplified, the inconsistency between the user data routing information and the user data is avoided, the success rate of service operation is ensured, and the utilization rate of number resources is improved.
Third embodiment
As shown in fig. 11, a third embodiment of the present application provides a mobile switching center MSC server, which includes: amemory 91, aprocessor 92 and a user routing program stored on thememory 91 and operable on theprocessor 92, wherein the user routing program, when executed by theprocessor 92, is configured to implement the following steps of the user routing method:
receiving an operation request sent by a user access Network Function (NF);
determining an attribution Unified Data Repository (UDR) of user data;
and acquiring user data from the home UDR, and returning an operation response to the user access NF according to the user data.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
inquiring user data routing information stored in a User Routing Data Center (URDC) according to the user identification to determine the attribution UDR; or querying the user data routing information cached locally according to the user identification to determine the attribution UDR.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
sending an operation request for changing user data to the attributive UDR through a user data acceptance subsystem; and when the operation of changing the user data is successful, sending a user data routing information updating request to the URDC through the user data receiving subsystem.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
the operation of changing the user data comprises at least one of user number allocation operation, user number cancellation operation, user card changing operation and user number changing operation.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
receiving a user data routing information update notification broadcast by the URDC; acquiring the updated user data routing information of the URDC according to the user data routing information updating notice; and storing the acquired user data routing information updated by the URDC to the local cache.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
accessing user data of the home UDR; and receiving the user data returned by the home UDR.
Alternatively, the user routing program, when executed by theprocessor 92, is configured to implement the following steps of the user routing method:
according to address information of a Unified Data Management (UDM), sending an operation request to the UDM; so that the UDM receives an operation request sent by the user access NF; determining a home UDR of user data; acquiring user data from the home UDR, and returning an operation response to a user access NF (network controller) according to the user data;
and acquiring the operation response returned by the UDM.
The user routing program, when executed by theprocessor 92, is further configured to implement the steps of the user routing method described below:
acquiring address information of the UDM from a network discovery function (NRF); or obtaining the address information of the UDM from local configuration.
The user routing equipment of the embodiment of the application automatically maintains the user data routing information in a HPLMN in a centralized manner without configuring the user data routing information in a plurality of UDMs; the operation and maintenance are simplified, the inconsistency between the user data routing information and the user data is avoided, the success rate of service operation is ensured, and the utilization rate of number resources is improved.
Fourth embodiment
A fourth embodiment of the present application provides a computer-readable storage medium, which stores a user routing program, and the user routing program is used for implementing the steps of the user routing method according to the first embodiment or the second embodiment when being executed by a processor.
It should be noted that the computer-readable storage medium of this embodiment belongs to the same concept as the method of the first embodiment or the second embodiment, and specific implementation processes thereof are detailed in the method embodiment, and technical features in the method embodiment are applicable in this embodiment, which is not described herein again.
The computer-readable storage medium of the embodiment of the application automatically maintains the user data routing information by centralizing the user data routing information in the HPLMN without configuring the user data routing information in a plurality of UDMs; the operation and maintenance are simplified, the inconsistency between the user data routing information and the user data is avoided, the success rate of service operation is ensured, and the utilization rate of number resources is improved.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and are not intended to limit the scope of the claims of the application accordingly. Any modifications, equivalents and improvements which may occur to those skilled in the art without departing from the scope and spirit of the present application are intended to be within the scope of the claims of the present application.