IP address allocation method, device and electronic device

Abstract

The present application discloses an IP address allocation method, device and electronic device. The method includes: when the session management function SMF entity initiates a power-on registration request to the network management function NFM entity, the corresponding subscription ID range is obtained from the NFM entity; the corresponding IP address segment is obtained from the IP address segment set of the database according to the subscription ID range; the IP address segment is stored in the memory database of the SMF entity, and when a session request from the access and mobility management function AMF entity is received, the corresponding IP address is allocated to the session request from the memory database. The present application solves the technical problem that in a multi-instance SMF scenario, the centralized IP address management method in the related technology is prone to cause message backlogs and service failures, and cannot achieve dynamic load balancing without interrupting the service.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an IP address allocation method, device and electronic device. Background Art

[0002] In the 5G network architecture, the evolution of the core network introduces service-oriented architecture and network function virtualization, aiming to meet the growing user needs and business scenarios by enhancing the flexibility and scalability of network functions. As a key component of the 5G core network, the SMF (Session Management Function) entity is responsible for managing user sessions, including session establishment, modification and release, as well as IP address allocation.

[0003] However, in the deployment scenario of multi-instance SMF, the dynamic IP address allocation method in related technologies faces severe challenges: first, the message processing delay and performance bottleneck caused by centralized address management, especially when the number of user sessions surges, the message backlog is serious, affecting business continuity; second, the lack of effective IP address pool pre-allocation and caching mechanism requires additional interaction for each session establishment, which consumes resources and is inefficient. In addition, when the SMF instance is dynamically expanded, it is difficult to reallocate and manage IP addresses without interrupting services, which limits the flexibility and scalability of the system.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide an IP address allocation method, device and electronic device to at least solve the technical problem that in a multi-instance SMF scenario, the centralized IP address management method in the related technology is prone to cause message backlogs and business failures, and cannot achieve dynamic load balancing without interrupting the business.

[0006] According to one aspect of an embodiment of the present application, an IP address allocation method is provided, including: when a session management function SMF entity initiates a power-on registration request to a network management function NFM entity, obtaining a corresponding subscription ID range from the NFM entity; obtaining a corresponding IP address segment from a set of IP address segments in a database based on the subscription ID range; storing the IP address segment in a memory database of the SMF entity, and when receiving a session request from an access and mobility management function AMF entity, allocating a corresponding IP address to the session request from the memory database.

[0007] Optionally, obtaining the corresponding subscription ID range from the NFM entity, including: when the NFM entity receives the power-on registration request from the SMF entity, dividing the subscription ID range for the SMF entity according to the power-on status of the SMF entity, and sending a subscription ID change notification to the SMF entity; obtaining the subscription ID range based on the subscription ID change notification.

[0008] Optionally, the IP address segment set of the database includes 256 IP address segments obtained by dividing the dynamic IP address pool according to the global subscription ID range.

[0009] Optionally, allocating a corresponding IP address for the session request from the memory database includes: determining an unallocated IP address in the memory database; and allocating a corresponding IP address for the session request from the unallocated IP address.

[0010] Optionally, after allocating the corresponding IP address for the session request from the memory database, the method further includes: determining an allocation status of the memory database, wherein the allocation status is used to represent allocated IP addresses and unallocated IP addresses in the memory database after the corresponding IP address is allocated for the session request; and synchronizing the allocation status to the database.

[0011] Optionally, the method also includes: determining a first subscription ID range corresponding to a first SMF instance, wherein the first SMF instance is any SMF instance in an SMF entity; obtaining a second subscription ID range corresponding to a second SMF instance based on a subscription ID change notification, and updating the first subscription ID range, wherein the second SMF instance is any SMF instance in an SMF entity, a power-on registration time of the first SMF instance is earlier than a power-on registration time of the second SMF instance, and the first subscription ID range is larger than the second subscription ID range.

[0012] Optionally, the method further includes: acquiring an IP address segment corresponding to the first SMF instance from an IP address segment set in a database based on the updated first subscription ID range.

[0013] According to another aspect of an embodiment of the present application, an IP address allocation system is also provided, including a session management function SMF entity, a network management function NFM entity, an access and mobility management function AMF entity and a database, wherein the SMF entity is used to obtain a corresponding subscription ID range from the NFM entity when initiating a power-on registration request to the NFM entity; obtain the corresponding IP address segment from the IP address segment set in the database based on the subscription ID range; store the IP address segment in the memory database of the SMF entity, and when receiving a session request from the AMF entity, allocate the corresponding IP address to the session request from the memory database; the NFM entity is used to divide the subscription ID range for the SMF entity according to the power-on status of the SMF entity when receiving the power-on registration request from the SMF entity, and send a subscription ID change notification to the SMF entity; the AMF entity is used to initiate a session request to the SMF entity; and the database is used to determine the IP address segment set.

[0014] According to another aspect of the embodiment of the present application, an IP address allocation device is also provided, including: a first acquisition module, used to obtain the corresponding subscription ID range from the network management function NFM entity when the session management function SMF entity initiates a power-on registration request to the NFM entity; a second acquisition module, used to obtain the corresponding IP address segment from the IP address segment set of the database based on the subscription ID range; an allocation module, used to store the IP address segment in the memory database of the SMF entity, and when receiving a session request from the access and mobility management function AMF entity, allocate the corresponding IP address to the session request from the memory database.

[0015] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the above-mentioned IP address allocation method.

[0016] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, the non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned IP address allocation method by running the computer program.

[0017] According to another aspect of the embodiments of the present application, a computer program product is also provided, including computer instructions, which implement the above-mentioned IP address allocation method when executed by a processor.

[0018] In an embodiment of the present application, when a power-on registration request is initiated to a network management function NFM entity through a session management function SMF entity, a corresponding subscription ID range is obtained from the NFM entity; a corresponding IP address segment is obtained from a set of IP address segments in a database based on the subscription ID range; the IP address segment is stored in a memory database of the SMF entity, and when a session request from an access and mobility management function AMF entity is received, a corresponding IP address is allocated to the session request from the memory database, thereby achieving the purpose of efficiently avoiding IP conflicts between multiple instance SMFs by dynamically allocating and locally managing IP address segments, thereby achieving the technical effect of improving session processing speed and overall system performance in scenarios with high user volume and dynamic expansion, and further solving the technical problem that in a multi-instance SMF scenario, the centralized IP address management method in the related technology is prone to cause message backlogs and service failures, and cannot achieve dynamic load balancing without interrupting the service. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 is a hardware structure diagram of a computer terminal for implementing an IP address allocation method according to an embodiment of the present application;

[0021] Figure 2 is a flow chart of an IP address allocation method according to an embodiment of the present application;

[0022] Figure 3 is a flow chart of another IP address allocation method according to an embodiment of the present application;

[0023] Figure 4 It is a schematic diagram of a SMF dynamic capacity expansion process according to an embodiment of the present application;

[0024] Figure 5 is a schematic diagram of a dynamic IP allocation module according to an embodiment of the present application;

[0025] Figure 6 It is a structural diagram of an IP address allocation device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] First, some nouns or terms that appear in the process of explaining the embodiments of the present application are subject to the following explanations:

[0029] SMF (Session Management Function): In the 5G network architecture, SMF is the network function responsible for user session management. It is responsible for session establishment, modification and release, as well as IP address allocation for user devices, and is a key component of the 5G core network.

[0030] NFM (Network Function Management): NFM is a management entity in the 5G network. It centrally manages network function instances, such as the power-on and power-off status of SMF instances, and the subscription scope allocation of each instance, to achieve efficient management and dynamic adjustment.

[0031] AMF (Access and Mobility Management Function): AMF is responsible for processing the access request and mobility management of user equipment and is the main interface between user equipment and the 5G network.

[0032] UDM (Unified Data Management): UDM is the network element that manages user subscription data and policy data in the 5G core network. It stores user identity, policy and subscription information for query and use by other network functions such as AMF and SMF.

[0033] DB (Database): In this application, DB refers to a database system used to store and manage IP address pools, allocated IP address information, and other network-related data.

[0034] IP address pool: A collection of available IP addresses for allocation to user devices in the network. In the scenario of dynamic IP allocation, the management and allocation of address pools are crucial.

[0035] Dynamic IP allocation: refers to the process of automatically allocating IP addresses to user devices in the network, rather than pre-fixed allocation.

[0036] In order to solve the problem of poor IP address allocation efficiency in the related art, the present application embodiment provides an IP address allocation method, which can be run on Figure 1 In the computer terminal shown, the computer terminal is described below.

[0037] The IP address allocation method embodiment provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal for implementing an IP address allocation method. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0038] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the IP address allocation method in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned IP address allocation method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via 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 combinations thereof.

[0040] The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 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 module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0041] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0042] It should be noted that, in some optional embodiments, the above Figure 1 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0043] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of an IP address allocation method. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0044] Figure 2 is a flow chart of an IP address allocation method according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0045] Step S202, when the session management function SMF entity initiates a power-on registration request to the network management function NFM entity, the corresponding subscription ID range is obtained from the NFM entity.

[0046] In the above step S202, when the SMF entity (including one or more SMF instances) starts, it sends a power-on registration request to the NFM entity, indicating that it is ready to join the network and start processing user sessions. After receiving this request, NFM will dynamically plan and allocate a subscription ID range to the corresponding SMF instance based on the instance status of the SMF in the current system. The allocation of the subscription ID range is based on a preset ID interval (for example, 1 to 256). NFM ensures that each SMF instance obtains a unique ID range to avoid conflicts in subsequent IP address allocation.

[0047] Step S204: Obtain the corresponding IP address segment from the IP address segment set in the database according to the subscription ID range.

[0048] In the above step S204, after obtaining the subscription ID range, SMF will search and load the corresponding IP address segment in the database (DB) according to this range. It should be noted that the IP address pool in the DB has been divided into multiple segments that match the subscription ID range, and each segment contains a certain number of IP addresses. In this way, each SMF instance can manage an independent IP address segment instead of the entire IP address pool, reducing network communication and resource competition during address allocation.

[0049] Step S206, stores the IP address segment in the memory database of the SMF entity, and when receiving a session request from the access and mobility management function AMF entity, allocates the corresponding IP address to the session request from the memory database.

[0050] In the above step S206, SMF loads and stores the IP address segments obtained from the database into its own memory database, thus realizing local caching of IP address segments. Subsequently, when the AMF entity initiates a session request to SMF, SMF can directly search for unassigned IP addresses in its memory database and assign an IP address to the requested session without interacting with the external database again. This optimization greatly improves the efficiency of IP address allocation, reduces latency, and increases the speed of establishing user sessions and the responsiveness of the entire system.

[0051] In addition, after allocating IP addresses, SMF will asynchronously synchronize the allocation information to the remote database to ensure the update and consistency of the global address pool. If you need to dynamically expand SMF, that is, add more SMF instances to the system, NFM will reallocate the subscription ID and the corresponding IP address segment, and the old SMF instance will update its own IP address segment information, and the newly added SMF instance will load the new IP address segment, achieving smooth load balancing and performance improvement of the system, while ensuring business continuity and the correctness of IP address allocation.

[0052] Through the above steps S202 to S206, the purpose of efficiently avoiding IP conflicts between multi-instance SMFs is achieved by dynamically allocating and locally managing IP address segments, thereby achieving the technical effect of improving session processing speed and overall system performance in scenarios with high user volume and dynamic expansion, and further solving the technical problem that in multi-instance SMF scenarios, the centralized IP address management method in related technologies is prone to cause message backlogs and business failures, and cannot achieve dynamic load balancing without interrupting business.

[0053] Figure 3 FIG. 1 is a flow chart of another IP address allocation method according to an embodiment of the present application. Figure 3 The figure shows how the system optimizes the dynamic IP allocation process of SMF by adjusting the dynamic subscription ID range and managing the local IP address segment when SMF is powered on and registered. Specifically:

[0054] First, after SMF sends a power-on request to NFM, NFM immediately reallocates the subscription ID range according to the instance status of SMF in the current system, and communicates the new range information to all SMF instances through subscription ID change notifications. Subsequently, the SMF instance obtains the IP address segment that belongs to this range from the database (DB) based on the received subscription ID range, and stores it in the local memory database to achieve localized management of the IP address segment. When a session is created, AMF sends a session request to SMF, and SMF searches for and allocates a suitable dynamic IP address to the user session in the local memory database, and asynchronously updates the IP usage record in the DB.

[0055] This process not only dynamically adjusts the allocation of IP address segments when SMF instances are added to avoid IP conflicts, but also greatly improves the efficiency of IP allocation through local processing, reduces dependence on external databases, and enhances the performance and reliability of the overall network. The efficient collaboration between NFM and SMF, as well as the combination of local IP address segment management and asynchronous database updates, together constitute the core of this innovative dynamic IP allocation optimization mechanism, which aims to solve the bottleneck problem of centralized address allocation in multi-instance SMF scenarios and improve session creation speed and system load balancing capabilities. The following is a detailed description.

[0056] In the above step S202, the corresponding subscription ID range is obtained from the NFM entity, including: when the NFM entity receives the power-on registration request of the SMF entity, it divides the subscription ID range for the SMF entity according to the power-on status of the SMF entity, and sends a subscription ID change notification to the SMF entity; the subscription ID range is obtained according to the subscription ID change notification.

[0057] In the embodiment of the present application, the NFM entity plays a core role in network resource management, and realizes efficient management of IP addresses in a multi-instance SMF environment by dynamically adjusting and allocating subscription ID ranges. When the SMF entity starts and registers with the power-on, NFM will intelligently re-plan the subscription ID range based on the total number and status of instances in the SMF in the current network to ensure that each SMF instance has an independent ID segment, thereby avoiding IP address allocation conflicts. Subsequently, NFM sends a subscription ID change notification to all affected SMF instances, and the SMF instance updates the local subscription ID and IP address management information according to the notification content. In this way, the SMF instance can quickly and accurately manage and allocate IP addresses in local memory, while maintaining global consistency by asynchronously updating the DB, significantly improving the session processing speed and the overall performance of the system.

[0058] Optionally, the IP address segment set of the database includes 256 IP address segments obtained by dividing the dynamic IP address pool according to the global subscription ID range.

[0059] In an embodiment of the present application, the IP address segment set of the database is designed to divide the dynamic IP address pool into 256 independent IP address segments based on the global subscription ID range (1 to 256). This design is intended to cooperate with the dynamic management of SMF instances by the NFM entity. By subdividing the address pool by subscription ID range, each SMF instance can be assigned to an exclusive address segment, and the IP addresses within this segment are only managed and allocated by the instance. When the SMF instance is powered on or the system is dynamically expanded or reduced, NFM will update the address segment information in the database based on the latest subscription ID allocation, and notify each SMF instance to load or update the address segment it manages.

[0060] In the above step S206, the corresponding IP address is allocated to the session request from the memory database, including: determining an unallocated IP address in the memory database; and allocating the corresponding IP address to the session request from the unallocated IP address.

[0061] In an embodiment of the present application, when the SMF entity receives a session creation request, it will use a localized memory database to allocate IP addresses to improve processing efficiency. The specific steps include first searching the memory database for unallocated IP address information, which is the exclusive IP address segment loaded by the SMF during the power-on registration process according to the subscription ID range obtained from the NFM. The use of the memory database makes the IP address search and allocation process almost instantaneous, greatly reducing processing delays. Subsequently, the SMF selects a suitable address from the unallocated IP address pool and directly allocates it to the new session request. This process is performed in local memory, avoiding real-time interaction with an external database, significantly improving the speed of session creation and the overall performance of the system.

[0062] Optionally, after allocating the corresponding IP address for the session request from the memory database, the method further includes: determining an allocation status of the memory database, wherein the allocation status is used to represent allocated IP addresses and unallocated IP addresses in the memory database after the corresponding IP address is allocated for the session request; and synchronizing the allocation status to the database.

[0063] In an embodiment of the present application, SMF not only allocates IP addresses for session requests in the local memory database, but also monitors and manages the allocation status of the memory database in real time after allocation. The allocation status contains the allocated IP address information and the currently unallocated IP address resources, which is crucial for subsequent session management and dynamic adjustment of IP addresses. SMF will ensure that unused IP addresses are selected for each allocation based on the allocation status, thereby avoiding duplicate allocation and conflicts. Furthermore, after completing the local allocation of IP addresses, SMF will synchronize the latest allocation status to the centralized database through an asynchronous mechanism. This operation ensures the consistency and accuracy of global IP address management. The allocation status synchronized to the database provides the latest IP address usage for other SMF instances and NFM, so that the system can dynamically adjust the allocation of IP address pools, especially when the SMF instance is dynamically expanded or reduced or the system is load balanced, it can quickly and accurately reflect and adapt to changes in the network environment, thereby maintaining efficient session management and improving user service experience.

[0064] Optionally, the above method also includes: determining a first subscription ID range corresponding to the first SMF instance, wherein the first SMF instance is any SMF instance in the SMF entity; obtaining a second subscription ID range corresponding to the second SMF instance based on the subscription ID change notification, and updating the first subscription ID range, wherein the second SMF instance is any SMF instance in the SMF entity, the power-on registration time of the first SMF instance is earlier than the power-on registration time of the second SMF instance, and the first subscription ID range is larger than the second subscription ID range.

[0065] Furthermore, the IP address segment corresponding to the first SMF instance is obtained from the IP address segment set of the database based on the updated first subscription ID range.

[0066] Figure 4 Schematic diagram of a SMF dynamic expansion process according to an embodiment of the present application. Figure 4 As shown, the core of dynamic expansion lies in the dynamic adjustment of the SMF instance subscription ID range by NFM, as well as the interaction between the new and old SMFs and the database (DB), so as to ensure the efficiency and consistency of IP address allocation.

[0067] Specifically, the process starts with the new SMF instance (i.e., the second SMF instance, SMF_NEW) being powered on to notify NFM, and NFM then replans and communicates the new scope information to all SMF instances (e.g., Figure 4 SMF and SMF_NEW in it). The new SMF instance loads the corresponding IP address segment from the DB according to the assigned subscription ID range (the second subscription ID range). At the same time, the old SMF instance (i.e., the first SMF instance mentioned above) also needs to update the IP address segment information it manages, that is, update the first subscription ID range corresponding to the old SMF instance, and obtain the new IP address segment information from the IP address segment set of the database according to the updated first subscription ID range. During the dynamic expansion process, whether it is a new SMF instance or an old SMF instance, when receiving a session request from AMF, it can quickly allocate an IP address in the local memory and asynchronously update the allocation record in the DB. This mechanism effectively supports the dynamic expansion and contraction of SMF, ensures the system's rapid response and high concurrent processing capabilities when the number of user sessions increases, while avoiding IP conflicts and maintaining the continuity and quality of network services.

[0068] Figure 5 Schematic diagram of a dynamic IP allocation module according to an embodiment of the present application. Figure 5As shown, NFM includes a subscription ID management module and a subscription change notification module, which are responsible for managing the subscription ID and power-on and power-off status of all SMF instances to ensure dynamic allocation and load balancing. AMF / UPF includes a user session management module, which forwards the session request to the corresponding SMF instance when the user device initiates the session request. DB includes a dynamic IP configuration storage module for generating an IP address segment set. SMF includes a subscription management change module and an IP address segment management module, wherein each SMF instance can obtain its own IP address segment from the IP address segment set of DB according to the subscription ID range assigned by NFM, and store it in the local memory database for efficient management. When receiving a session request forwarded by AMF, the SMF instance can quickly allocate an IP address in the local memory, and then asynchronously update the usage record in the database, ensuring the accuracy and global consistency of the address allocation. As the information storage center of the entire system, the database module maintains the configuration and usage status of all dynamic IP addresses.

[0069] In the embodiment of the present application, the subscription ID range of the SMF instance is dynamically managed through NFM, and the segmented localization of the IP address pool is realized. This method not only avoids the common conflicts and blocking problems in traditional centralized IP address allocation, but also significantly improves the performance and efficiency of session creation through asynchronous database updates. Especially in the dynamic expansion scenario, the newly added SMF instance can quickly obtain and manage the IP address segment that is exclusive to its subscription ID range, seamlessly integrate into the existing system, achieve load balancing, effectively solve the performance bottleneck caused by the surge in user sessions, and improve the overall throughput of the system and the quality of business services.

[0070] According to an embodiment of the present application, an IP address allocation device is provided. It should be noted that the IP address allocation device of the embodiment of the present application can be used to execute the IP address allocation method provided in the embodiment of the present application. The IP address allocation device provided in the embodiment of the present application is introduced below.

[0071] Figure 6 1 is a structural diagram of an IP address allocation device provided according to an embodiment of the present application. Figure 6 As shown, the device comprises:

[0072] A first acquisition module 60 is used to acquire a corresponding subscription ID range from a network management function NFM entity when a session management function SMF entity initiates a power-on registration request to the NFM entity;

[0073] A second acquisition module 62, configured to acquire a corresponding IP address segment from the IP address segment set in the database according to the subscription ID range;

[0074] The allocation module 64 is used to store the IP address segment in the memory database of the SMF entity, and when receiving a session request from the access and mobility management function AMF entity, allocate the corresponding IP address to the session request from the memory database.

[0075] Through the first acquisition module 60, the second acquisition module 62 and the allocation module 64 in the above-mentioned IP address allocation device, the purpose of efficiently avoiding IP conflicts between multi-instance SMFs is achieved by dynamically allocating and locally managing IP address segments, thereby achieving the technical effect of improving session processing speed and overall system performance in scenarios with high user volume and dynamic expansion, and further solving the technical problem that in multi-instance SMF scenarios, the centralized IP address management method in related technologies is prone to cause message backlogs and business failures, and cannot achieve dynamic load balancing without interrupting business.

[0076] In the IP address allocation device provided in the embodiment of the present application, the first acquisition module is also used for the NFM entity to divide the subscription ID range for the SMF entity according to the power-on status of the SMF entity when receiving the power-on registration request of the SMF entity, and to send a subscription ID change notification to the SMF entity; and to obtain the subscription ID range based on the subscription ID change notification.

[0077] In the IP address allocation device provided in the embodiment of the present application, the allocation module is also used to determine the unallocated IP addresses in the memory database; and allocate corresponding IP addresses to session requests from the unallocated IP addresses.

[0078] The IP address allocation device provided in the embodiment of the present application also includes a synchronization module 66, which is used to determine the allocation status of the memory database, wherein the allocation status is used to represent the allocated IP addresses and unallocated IP addresses in the memory database after the corresponding IP address is allocated to the session request; the allocation status is synchronized to the database.

[0079] The IP address allocation device provided in the embodiment of the present application also includes an update module 68, which is used to determine a first subscription ID range corresponding to a first SMF entity, wherein the first SMF entity is any one of the SMF entities; obtain a second subscription ID range corresponding to the second SMF entity based on a subscription ID change notification, and update the first subscription ID range, wherein the second SMF entity is any one of the SMF entities, the power-on registration time of the first SMF entity is earlier than the power-on registration time of the second SMF entity, and the first subscription ID range is larger than the second subscription ID range.

[0080] In the IP address allocation device provided in the embodiment of the present application, the update module is also used to obtain the IP address segment corresponding to the first SMF entity from the IP address segment set of the database according to the updated first subscription ID range.

[0081] An embodiment of the present application also provides an IP address allocation system, including a session management function SMF entity, a network management function NFM entity, an access and mobility management function AMF entity and a database, wherein the SMF entity is used to obtain a corresponding subscription ID range from the NFM entity when initiating a power-on registration request to the NFM entity; obtain a corresponding IP address segment from the IP address segment set of the database based on the subscription ID range; store the IP address segment in the memory database of the SMF entity, and when receiving a session request from the AMF entity, allocate a corresponding IP address to the session request from the memory database; the NFM entity is used to divide the subscription ID range for the SMF entity according to the power-on status of the SMF entity when receiving the power-on registration request from the SMF entity, and send a subscription ID change notification to the SMF entity; the AMF entity is used to initiate a session request to the SMF entity; and the database is used to determine the IP address segment set.

[0082] It should be noted that the above IP address allocation system is used to execute Figure 2 The IP address allocation method shown in the figure, therefore the relevant explanations in the above IP address allocation method are also applicable to the IP address allocation system, and will not be repeated here.

[0083] An embodiment of the present application also provides an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute and implement the above-mentioned IP address allocation method.

[0084] It should be noted that the above electronic equipment is used to execute Figure 2 The IP address allocation method shown, therefore the relevant explanations in the above IP address allocation method are also applicable to the electronic device and will not be repeated here.

[0085] An embodiment of the present application also provides a non-volatile storage medium, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned IP address allocation method by running the computer program.

[0086] It should be noted that the above non-volatile storage medium is used to execute Figure 2 The IP address allocation method shown, therefore the relevant explanations in the above IP address allocation method are also applicable to the non-volatile storage medium, and will not be repeated here.

[0087] An embodiment of the present application also provides a computer program product, including computer instructions, which implement the above-mentioned IP address allocation method when executed by a processor.

[0088] It should be noted that the above-mentioned computer program product is used to execute Figure 2 The IP address allocation method shown in the figure, therefore the relevant explanations and instructions in the above IP address allocation method are also applicable to the computer program product and will not be repeated here.

[0089] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0090] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0091] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0092] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0093] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0094] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0095] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for allocating an IP address, characterized in that: include: When the session management function SMF entity initiates a power-on registration request to the network management function NFM entity, the corresponding subscription ID range is obtained from the NFM entity; Obtaining a corresponding IP address segment from the IP address segment set in the database according to the subscription ID range; The IP address segment is stored in the memory database of the SMF entity, and when a session request from the access and mobility management function AMF entity is received, a corresponding IP address is allocated to the session request from the memory database.

2. The method according to claim 1, characterized in that: Obtaining a corresponding subscription ID range from the NFM entity includes: When the NFM entity receives the power-on registration request of the SMF entity, it divides the subscription ID range for the SMF entity according to the power-on status of the SMF entity, and sends a subscription ID change notification to the SMF entity; The subscription ID range is obtained according to the subscription ID change notification.

3. The method according to claim 1, characterized in that The IP address segment set of the database includes 256 IP address segments obtained by dividing the dynamic IP address pool according to the global subscription ID range.

4. The method according to claim 1, characterized in that Allocating a corresponding IP address for the session request from the memory database includes: Determining unassigned IP addresses in the in-memory database; A corresponding IP address is allocated to the session request from the unallocated IP addresses.

5. The method according to claim 4, characterized in that After allocating the corresponding IP address for the session request from the memory database, the method further includes: Determining an allocation state of the memory database, wherein the allocation state is used to represent an allocated IP address and an unallocated IP address in the memory database after the corresponding IP address is allocated to the session request; The allocation status is synchronized to the database.

6. The method according to claim 1, characterized in that The method further comprises: Determine a first subscription ID range corresponding to a first SMF instance, wherein the first SMF instance is any one SMF instance in the SMF entity; Obtain a second subscription ID range corresponding to the second SMF instance based on the subscription ID change notification, and update the first subscription ID range, wherein the second SMF instance is any SMF instance in the SMF entity, the power-on registration time of the first SMF instance is earlier than the power-on registration time of the second SMF instance, and the first subscription ID range is larger than the second subscription ID range.

7. The method according to claim 6, characterized in that The method further comprises: The IP address segment corresponding to the first SMF instance is obtained from the IP address segment set of the database according to the updated first subscription ID range.

8. An IP address allocation system, characterized in that: It includes a session management function SMF entity, a network management function NFM entity, an access and mobility management function AMF entity and a database, wherein: The SMF entity is used to obtain the corresponding subscription ID range from the NFM entity when initiating a power-on registration request to the NFM entity; obtain the corresponding IP address segment from the IP address segment set of the database according to the subscription ID range; store the IP address segment in the memory database of the SMF entity, and when receiving the session request of the AMF entity, allocate the corresponding IP address to the session request from the memory database; The NFM entity is used to divide the subscription ID range for the SMF entity according to the power-on status of the SMF entity when receiving the power-on registration request of the SMF entity, and send a subscription ID change notification to the SMF entity; The AMF entity is used to initiate a session request to the SMF entity; The database is used to determine the IP address segment set.

9. An IP address allocation device, characterized in that: include: A first acquisition module is used to acquire a corresponding subscription ID range from a network management function NFM entity when a session management function SMF entity initiates a power-on registration request to the NFM entity; A second acquisition module, configured to acquire a corresponding IP address segment from an IP address segment set in a database according to the subscription ID range; An allocation module is used to store the IP address segment in the memory database of the SMF entity, and when receiving a session request from the access and mobility management function AMF entity, allocate a corresponding IP address to the session request from the memory database.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; The processor is connected to the memory and is used to execute the IP address allocation method described in any one of claims 1 to 8.

11. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the IP address allocation method according to any one of claims 1 to 8 by running the computer program.

12. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the IP address allocation method described in any one of claims 1 to 8 is implemented.

Images