Interface address allocation method and device

Abstract

The present application relates to the technical field of communications, and provides an interface address allocation method and device, for use in configuring network function (NF) interfaces in a distributed network. The method comprises: by means of a first message, a service address allocation proxy function entity can request a network management function entity to allocate an address to an interface, and the network management function entity can allocate an address to the interface on the basis of the first message, and send address information to the service address allocation proxy function entity; and when the service address allocation proxy function entity sends the address information to a service interface automation system, the service interface automation system can automatically generate an interface configuration of a first NF on the basis of the received address information. Therefore, an interface address can be automatically obtained and configured, so that manual planning and configuration of the addresses of interfaces in an NF deployment phase can be avoided, thereby improving the efficiency of configuring the interface addresses, and realizing the configuration of NF interfaces in the distributed network.

Description

Interface address allocation method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 28, 2023, with application number 202311851417.4 and application name “Interface Address Allocation Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a method and device for allocating interface addresses. Background Art

[0003] The sixth-generation mobile communication standard (6G) is evolving from centralized to distributed networks, resulting in the entire network being composed of a vast number of distributed networks. The application scenarios of these distributed networks are gradually expanding from industrial applications to daily life, sports, and entertainment. These new scenarios require distributed networks to be able to deploy rapidly, reducing deployment time from months to days, hours, or even minutes.

[0004] Distributed network deployment involves network function (NF) deployment and NF interface configuration. Currently, NF interface configuration requires planning by operators or third parties, but this approach may not be suitable for distributed networks. Therefore, how to configure NF interfaces in distributed networks is a hot topic of discussion. Summary of the Invention

[0005] The embodiments of the present application provide a method and apparatus for allocating an interface address, for configuring a NF interface in a distributed network.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, an interface address allocation method is provided, comprising: a service address allocation proxy function entity sending a first message to a network management function entity, the first message being used to request address allocation for an interface of at least one interface type of a first network function; the service address allocation proxy function entity receiving a second message from the network management function entity, the second message being used to indicate address information of an interface of at least one interface type; and the service address allocation proxy function entity sending the address information to a service interface automation system.

[0008] Based on the method of the first aspect, the service address allocation proxy functional entity can request, via a first message, the network management functional entity to allocate an address for the interface. The network management functional entity can then allocate an address for the interface based on the first message and send the address information to the service address allocation proxy functional entity. After the service address allocation proxy functional entity sends the address information to the service interface automation system, the service interface automation system can automatically generate the interface configuration for the first network function based on the received address information. This enables automatic acquisition and configuration of interface addresses, eliminating the need for manual planning and configuration of each interface's address during the NF deployment phase. This improves the efficiency of interface address configuration and enables configuration of NF interfaces in a distributed network.

[0009] In one possible design, the method described in the first aspect further includes: a service address allocation proxy functional entity receiving a third message from a service interface automation system, the third message being used to request address allocation for at least one interface type; and the service address allocation proxy functional entity sending a first message to a network management functional entity, including: the service address allocation proxy functional entity sending the first message to the network management functional entity based on the third message. It is understood that the service interface automation system can trigger the service address allocation proxy functional entity to send the first message to the network management functional entity through the third message based on actual conditions, such as after NF deployment. In this way, the service address allocation proxy functional entity can be automatically triggered to obtain the address of at least one interface type of the first network function.

[0010] In one possible design, the first message specifically requests allocation of a preset number of addresses to interfaces of at least one interface type of the first network function, and the address information indicates the preset number of addresses. This allows for flexible configuration of the number of addresses required for each interface of the at least one interface type based on actual circumstances, and enables allocation of the required number of addresses to each interface of the at least one interface type, achieving on-demand allocation.

[0011] Optionally, the first message includes at least one of the following: information indicating a first network function, information indicating at least one interface type, or information indicating a preset number.

[0012] Optionally, the second message includes at least one of the following: information indicating the first network function, information indicating at least one interface type, or address information.

[0013] In one possible design, the second message further indicates a validity period, which is the period during which the address indicated by the address information is permitted to be used. The service address allocation proxy functional entity sending the address information to the service interface automation system includes: the service address allocation proxy functional entity sending the address information and the validity period to the service interface automation system. This allows the first functional entity to determine the expiration time of the address indicated by the address information based on the validity period, facilitating processing before the address expires, such as requesting continued use of the address, thereby avoiding service errors after the address expires.

[0014] In one possible design, the address information includes at least one interface address and first network planning information, where the first network planning information indicates information about the network on which the at least one interface address resides. It will be appreciated that there is a corresponding relationship between the at least one interface address and the first network planning information, i.e., the at least one interface address is an address within the network indicated by the first network planning information. This ensures that, when multiple networks include the same interface address, a unique interface address can be determined using the first network planning information.

[0015] Optionally, the first network planning information is any one of the following: an Internet Protocol (IP) domain name, or a virtual private network (VPN). It is understood that in other network planning, the first network planning information may also be other information for indicating a network, which may be flexibly set according to actual conditions.

[0016] In one design, the service address allocation proxy function sends address information to the service interface automation system, including: the service address allocation proxy function determines that the address information can be used, then sends the address information to the service interface automation system. This avoids situations where an address becomes unavailable after being configured based on the address information, thereby avoiding service errors and the additional overhead incurred by the service address allocation proxy function and the service interface automation system in re-acquiring address information.

[0017] In one possible design scheme, the method described in the first aspect further includes: when the address indicated by the address information becomes invalid, the service address allocation proxy function entity sends a fourth message to the network management function entity, and the fourth message is used to request to continue to allocate the address indicated by the address information to the interface of at least one interface type of the first network function. It can be understood that the above-mentioned address expiration refers to when the address is about to expire, such as when the usage period of the address indicated by the address information is about to reach the valid period of the address. In this way, it can be ensured that the interface of at least one interface type of the first network function has a usable address, avoiding the occurrence of the address configured by the interface, resulting in service errors, etc.

[0018] Optionally, the fourth message includes at least one of the following: information indicating the first network function, information indicating an interface of at least one interface type, or address information.

[0019] In a second aspect, an interface address allocation method is provided, which includes: a network management function entity receives a first message from a business address allocation agent function entity, the first message being used to request address allocation for an interface of at least one interface type of a first network function; the network management function entity sends a second message to the business address allocation agent function entity based on the first message, the second message being used to indicate address information of an interface of at least one interface type.

[0020] In a possible design scheme, the first message is specifically used to request allocation of a preset number of addresses for interfaces of at least one interface type of the first network function, and the address information is used to indicate the preset number of addresses.

[0021] Optionally, the first message includes at least one of the following: information indicating a first network function, information indicating at least one interface type, or information indicating a preset number.

[0022] Optionally, the second message includes at least one of the following: information indicating the first network function, information indicating at least one interface type, or address information.

[0023] In one possible design, before the network management function entity receives the first message from the service address allocation proxy function entity, the method described in the second aspect further includes: the network management function entity sends a fifth message to the service network management center, the fifth message being used to obtain the address network segment corresponding to the interface of the first interface type, the first interface type including the interface type of the interface determined to be deployed, and at least one interface type of the first network function belonging to the first interface type; the network management function entity receives a sixth message from the service network management center, the sixth message being used to indicate the address network segment information corresponding to the interface of the first interface type; and the network management function entity sends a second message to the service address allocation proxy function entity based on the first message, including: the network management function entity sends the second message to the service address allocation proxy function entity based on the first message and the sixth message. In other words, the network management function entity can pre-acquire the address network segment corresponding to the interface of the first interface type, thereby ensuring that there are sufficient addresses to allocate addresses to each interface.

[0024] In one possible design, before the network management function entity receives the first message from the service address allocation proxy function entity, the method according to the second aspect further includes: the network management function entity receives a seventh message from the topology orchestrator, the seventh message being used to indicate address segment information corresponding to an interface of a second interface type, the second interface type including all interface types corresponding to the planned network, and at least one interface type of the first network function belonging to the second interface type; the network management function entity sending a second message to the service address allocation proxy function entity based on the first message, including: the network management function entity sending the second message to the service address allocation proxy function entity based on the first message and the seventh message. It is understood that when the address scale required for deployment to the edge network or distributed network has been determined, the topology orchestrator can send relevant information about each planned interface (such as the interface type, the address segment corresponding to the interface of each interface type, etc.) to the network management function entity, so that the network management function entity can directly use this relevant information when subsequently allocating addresses to the interfaces, without the network management function entity having to request the address segment corresponding to the interface of each interface type from the service network management center, thereby reducing the communication overhead of the network management function entity.

[0025] Optionally, the method described in the second aspect further includes: the network management function entity sending an eighth message to the edge gateway based on the sixth message or the seventh message, where the eighth message is used to request configuration of the segment routing corresponding to the address segment information. In other words, after receiving the address segment corresponding to the interface of each interface type, the network management function entity can configure the corresponding segment routing based on the address segment. In this way, automatic configuration of network routing can be achieved, avoiding manual configuration of segment routing, thereby improving the efficiency of configuring segment routing.

[0026] Optionally, the address segment information includes at least one interface address segment and second network planning information, where the second network planning information indicates information about the network in which the at least one interface address segment resides. It is understood that the at least one interface address segment and the second network planning information have a corresponding relationship, i.e., the interface address segment is an address segment in the second network planning information. In this way, a network can be determined using the second network planning information, and each address within the network can be determined using the address segment.

[0027] In a possible design, the address information includes at least one interface address and first network planning information, where the first network planning information is used to indicate information about a network where the interface address is located.

[0028] Optionally, the first network planning information is any one of the following: an Internet Protocol IP domain name, or a virtual private network VPN.

[0029] In addition, the technical effects of the method described in the second aspect can also refer to the technical effects of the method described in the first aspect, and will not be repeated here.

[0030] In a third aspect, an interface address allocation method is provided, the method comprising: a business interface automation system receiving address information from a business address allocation agent function entity, the address information being used to indicate an address allocated to an interface of at least one interface type of a first network function; and the business interface automation system generating an interface configuration of the first network function based on the address information.

[0031] In one possible design scheme, before the service interface automation system receives address information from the service address allocation proxy functional entity, the method described in the third aspect also includes: the service interface automation system sends a third message to the service address allocation proxy functional entity, and the third message is used to request that an address be allocated to an interface of at least one interface type of the first network function.

[0032] Optionally, the third message is used to request allocation of a preset number of addresses to interfaces of at least one interface type, and the address information is used to indicate the preset number of addresses. In this way, the number of addresses required for each interface of the at least one interface type can be flexibly set according to actual circumstances, and the required number of addresses can be allocated to each interface of the at least one interface type, achieving on-demand allocation.

[0033] In a possible design, the address information includes at least one interface address and first network planning information, where the first network planning information is used to indicate information about a network where the interface address is located.

[0034] Optionally, the first network planning information is any one of the following: an Internet Protocol IP domain name, or a virtual private network VPN.

[0035] In addition, the technical effects of the method described in the third aspect can also refer to the technical effects of the method described in the first aspect, and will not be repeated here.

[0036] In a fourth aspect, an interface address allocation method is provided, which includes: a service address allocation agent function entity sends a first message to a network management function entity, the first message being used to request continued use of a first address allocated to an interface of a first interface type for a first network function; the service address allocation agent function entity receives a second message from the network management function entity, the second message being used to allocate a second address to an interface of the first interface type.

[0037] Based on the method of the fourth aspect, the service address allocation proxy functional entity can request the network management functional entity to allocate the first address when the first address is about to expire. After receiving the request, the network management functional entity can allocate a second address to the service address allocation proxy functional entity. This can prevent the interface of the first interface type of the first network function from being unable to use the first address and having no available address after the first address expires, thereby avoiding service errors caused by the interface having no available address.

[0038] In one possible design, the first message includes at least one of the following: information indicating the first network function, information indicating the first interface type, or information indicating the first address.

[0039] In one possible design, the second message includes at least one of the following: information indicating the first network function, information indicating the first interface type, or information indicating the second address.

[0040] In one possible design, the second message further indicates a validity period, which is the duration during which the second address is permitted to be used. This allows the first functional entity to determine the expiration date of the address indicated by the address information based on the validity period, facilitating processing before the address expires, such as continuing to request use of the address. This avoids service errors after the address expires.

[0041] In one possible design, the method described in aspect 4 further includes: the service address allocation proxy function entity sending a third message to the service interface automation system, the third message being used to request that the first address be updated to a second address. In other words, when the second address differs from the first address, the service address allocation proxy function can request the service interface automation system to perform an address update, i.e., reconfigure the address for the interface of the first interface type of the first network function. This ensures normal service operation.

[0042] Optionally, the third message includes at least one of the following: information indicating the first interface type, information indicating the first address, or information indicating the second address.

[0043] In one possible design scheme, before the service address allocation proxy function entity sends the first message to the network management function entity, the method described in the fourth aspect also includes: the service address allocation proxy function entity receives a fourth message from the service interface automation system, the fourth message being used to request allocation of the first address; and the service address allocation proxy function entity sends the first message to the network management function entity, including: the service address allocation proxy function entity sends the first message to the network management function entity based on the fourth message. It can be understood that the first network function needs to keep the interface address unchanged after restarting. In this case, after reading the configuration data, the service interface automation system can trigger the service address allocation proxy function entity to request allocation of the first address through the fourth message to ensure that the first address is available.

[0044] Optionally, the fourth message includes at least one of the following: information indicating the first interface type, or information indicating the first address.

[0045] In a fifth aspect, an interface address allocation method is provided, which includes: a network management function entity receives a first message from a business address allocation agent function entity, the first message being used to request continued use of a first address allocated to an interface of a first interface type for a first network function; the network management function entity sends a second message to the business address allocation agent function entity based on the first message, the second message being used to allocate a second address to an interface of the first interface type.

[0046] In one possible design, the first message includes at least one of the following: information indicating the first network function, information indicating the first interface type, or information indicating the first address.

[0047] In one possible design, the second message includes at least one of the following: information indicating the first network function, information indicating the first interface type, or information indicating the second address.

[0048] In one possible design, the second message further indicates a validity period, which is the duration during which the second address is permitted to be used. This allows the first functional entity to determine the expiration date of the address indicated by the address information based on the validity period, facilitating processing before the address expires, such as continuing to request use of the address, thereby avoiding service errors after the address expires.

[0049] In addition, the technical effects of the method described in the fifth aspect can also refer to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0050] In a sixth aspect, an interface address allocation method is provided, the method comprising: a business interface automation system receives a third message from a business address allocation agent function entity, the third message being used to request that a first address corresponding to an interface of a first interface type of a first network function be updated to a second address; the business interface automation system updates the first address to the second address according to the third message.

[0051] In one possible design, the third message includes at least one of the following: information indicating the first interface type, information indicating the first address, or information indicating the second address.

[0052] In one possible design scheme, before the service interface automation system receives the third message from the service address allocation agent functional entity, the method described in the sixth aspect also includes: the service interface automation system sends a fourth message to the service address allocation agent functional entity, and the fourth message is used to request allocation of the first address.

[0053] Optionally, the fourth message includes at least one of the following: information indicating the first interface type, or information indicating the first address.

[0054] In addition, the technical effects of the method described in the sixth aspect can also refer to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0055] In the seventh aspect, an interface address allocation method is provided, which includes: a business address allocation agent functional entity executes the method described in the first aspect, and a network management functional entity executes the method described in the second aspect; or, a business address allocation agent functional entity executes the method described in the first aspect, a network management functional entity executes the method described in the second aspect, and a business interface automation system executes the method described in the third aspect.

[0056] In addition, the technical effects of the method described in the seventh aspect can also refer to the technical effects of the methods described in the first to third aspects, and will not be repeated here.

[0057] In the eighth aspect, an interface address allocation method is provided, which includes: a business address allocation agent functional entity executes the method described in the fourth aspect, and a network management functional entity executes the method described in the fifth aspect; or, a business address allocation agent functional entity executes the method described in the fourth aspect, a network management functional entity executes the method described in the fifth aspect, and a business interface automation system executes the method described in the sixth aspect.

[0058] In addition, the technical effects of the method described in aspect 8 can also refer to the technical effects of the methods described in aspects 4 to 6, and will not be repeated here.

[0059] In a ninth aspect, a communication device is provided. The communication device includes: a module for executing the method described in any one of aspects 1 to 6, such as a transceiver module and a processing module. For example, the transceiver module is configured to indicate the transceiver function of the communication device, and the processing module is configured to perform functions of the communication device other than the transceiver function.

[0060] Optionally, the transceiver module may include a sending module and a receiving module, wherein the sending module is used to implement the sending function of the communication device described in the ninth aspect, and the receiving module is used to implement the receiving function of the communication device described in the ninth aspect.

[0061] Optionally, the communication device described in the ninth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute the method described in any one of the first to sixth aspects.

[0062] It can be understood that the communication device described in the ninth aspect can be a network device, or a chip (system) or other parts or components that can be set in the network device, or a device that includes the network device. This application does not limit this.

[0063] In addition, the technical effects of the communication device described in the ninth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first to sixth aspects, and will not be repeated here.

[0064] In a tenth aspect, a communication device is provided, comprising: a processor, wherein when the processor executes computer instructions, the communication device executes the method described in any possible implementation manner of the first to sixth aspects.

[0065] In one possible design solution, the communication device described in the tenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the tenth aspect to communicate with other communication devices.

[0066] In one possible design, the communication device described in aspect 10 may further include a memory. The memory may be integrated with the processor or provided separately. The memory may be used to store the computer program and / or data involved in the method described in any one of aspects 1 to 6.

[0067] In an embodiment of the present application, the communication device described in the tenth aspect can be the network device described in any one of the first to sixth aspects, or a chip (system) or other parts or components that can be set in the network device, or a device that includes the network device.

[0068] In addition, the technical effects of the communication device described in the tenth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first aspect to the sixth aspect, and will not be repeated here.

[0069] In an eleventh aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, so that the communication device performs the method described in any possible implementation of the first to sixth aspects.

[0070] In one possible design solution, the communication device described in the eleventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the eleventh aspect to communicate with other communication devices.

[0071] In an embodiment of the present application, the communication device described in the eleventh aspect can be the network device described in any one of the first to sixth aspects, or a chip (system) or other parts or components that can be set in the network device, or a device that includes the network device.

[0072] In addition, the technical effects of the communication device described in the eleventh aspect can refer to the technical effects of the method described in any one of the implementation methods of the first aspect to the sixth aspect, and will not be repeated here.

[0073] In the twelfth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the method described in any one of the implementation methods of the first to sixth aspects.

[0074] In one possible design solution, the communication device described in aspect 12 may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in aspect 12 to communicate with other communication devices.

[0075] In an embodiment of the present application, the communication device described in aspect 12 may be the network device described in any one of aspects 1 to 6, or a chip (system) or other parts or components that may be set in the network device, or a device that includes the network device.

[0076] In addition, the technical effects of the communication device described in the twelfth aspect can refer to the technical effects of the method described in any one of the implementation methods of the first to sixth aspects, and will not be repeated here.

[0077] In a thirteenth aspect, a communication chip is provided, in which instructions are stored. When the chip runs on a communication device, the method described in any one of the implementation methods of the first to sixth aspects is implemented.

[0078] In the fourteenth aspect, a communication chip is provided, comprising: a logic circuit and a communication interface, wherein the logic circuit is used to execute computer instructions, and the communication interface is used for the communication chip to communicate with other devices or chips, and when the logic circuit executes the computer instructions, the method described in any one of the implementation methods of the first to sixth aspects is implemented.

[0079] In a fifteenth aspect, a communication system is provided, which includes at least one of the following: a service address allocation agent function entity for executing the method described in the first aspect, a network management function entity for executing the method described in the second aspect, or a service interface automation system for executing the method described in the third aspect.

[0080] In the sixteenth aspect, a communication system is provided, which includes at least one of the following: a service address allocation agent function entity for executing the method described in the fourth aspect, a network management function entity for executing the method described in the fifth aspect, or a service interface automation system for executing the method described in the sixth aspect.

[0081] In the seventeenth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are run on a computer, the computer executes the method described in any possible implementation method of the first to sixth aspects.

[0082] In the eighteenth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed on a computer, enables the computer to execute the method described in any one of the possible implementations of aspects one to six. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] FIG1 is a schematic diagram of a deployment process of a network function NF provided in an embodiment of the present application;

[0084] FIG2 is a schematic diagram of interface docking provided in an embodiment of the present application;

[0085] FIG3 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application;

[0086] FIG4 is a second schematic diagram of the architecture of the communication system provided in an embodiment of the present application;

[0087] FIG5 is a third schematic diagram of the architecture of the communication system provided in an embodiment of the present application;

[0088] FIG6 is a flow chart of a method for allocating interface addresses according to an embodiment of the present application;

[0089] FIG7 is a second flow chart of the interface address allocation method provided in an embodiment of the present application;

[0090] FIG8 is a third flow chart of the interface address allocation method provided in an embodiment of the present application;

[0091] FIG9 is a fourth flow chart of the interface address allocation method provided in an embodiment of the present application;

[0092] FIG10 is a fifth flow chart of the interface address allocation method provided in an embodiment of the present application;

[0093] FIG11 is a sixth flow chart of the interface address allocation method provided in an embodiment of the present application;

[0094] FIG12 is a first structural diagram of a communication device provided in an embodiment of the present application;

[0095] FIG13 is a second structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] For ease of understanding, the technical terms involved in the embodiments of this application are first introduced below.

[0097] 1.NF deployment process

[0098] As shown in Figure 1, the NF deployment process primarily includes: network planning and design, transmission network configuration, automated network configuration, NF deployment, NF interface configuration and docking, and service function configuration. Network planning and design involves planning and designing the entire network, such as the interface types and the corresponding interface address segments. In the future, network planning and design automation will be achieved through intent-based or artificial intelligence (AI) self-intelligence. Automated transmission network configuration can be achieved using software-defined networking (SDN) technology, which involves automating the transmission network by issuing network configuration commands to the SDN controller. Automated network configuration and NF deployment can be achieved using technologies such as management and orchestration (MANO) and network function virtualization infrastructure (NFVI). NF interface configuration and docking, also known as service interface configuration and docking, involves address planning and configuration of NF interfaces (such as the N2 interface and the N4 interface), as well as docking with the corresponding NF. Business function configuration involves starting different NF functions according to different scenarios, and this business function configuration requires manual planning.

[0099] 2.NF interface configuration and connection

[0100] During NF interface configuration and docking, the service interface Internet Protocol (IP) address must be manually planned. Based on the network-wide virtual private network (VPN) plan, the interface IP address and corresponding VPN configuration must be manually distributed to and from the NF. Depending on the interface docking method, docking can be accomplished by locally configuring the peer IP address, automatically discovering the peer interface IP address using a service-based architecture (SBA), or acting as a server and waiting for the peer device to initiate the link establishment process.

[0101] As shown in Figure 2, the following example illustrates the connection between the session management function (SMF) and the user plane function (UPF) over the N4 interface. The entire configuration process required on the SMF is as follows:

[0102] S201, obtain the VPN plan of the N4 interface from the operator's overall network plan, that is, VPN-N4 (denoted as VPN#1).

[0103] S202, allocate an IP address (recorded as IP address #1) to the SMF from the IP address segment reserved by the operator for the N4 interface, that is, the IP address #1 is used as the local address of the N4 interface of the SMF.

[0104] SMF is typically deployed in a data center or provincial network center. After allocating an IP address, you need to configure the network segment routing for that IP address on the edge gateway in the data center or provincial network center.

[0105] S203, configure IP address #1 and VPN #1 of the N4 interface on the SMF.

[0106] After configuring IP address #1 and VPN #1 for the N4 interface, you can also configure the application layer information for the N4 interface.

[0107] S204, SMF actively publishes the N4 interface address route.

[0108] After the edge gateway receives the IP message sent to IP address #1, it can directly forward it to the SMF for processing.

[0109] S205, SMF receives the N4 interface link establishment request message initiated by UPF and completes the establishment of the N4 interface link.

[0110] The above describes the current configuration process for NF interfaces. As you can see, 6G networks are evolving from centralized to distributed networks, resulting in the entire network consisting of a vast number of distributed networks. The application scenarios of these distributed networks are gradually expanding from industrial applications to lifestyles, sports, and entertainment. These new scenarios require distributed networks to be rapidly deployed, reducing deployment time from months to days, hours, or even minutes.

[0111] Distributed network deployment involves configuring NF interfaces. Currently, NF interface configuration requires manual planning by operators or third parties, making it inefficient and unsuitable for distributed networks. Therefore, configuring NF interfaces in distributed networks is a hot topic of discussion.

[0112] To address the above technical issues, the present application proposes the following technical solutions to implement configuration of NF interfaces in a distributed network.

[0113] The technical solution in this application will be described below with reference to the accompanying drawings.

[0114] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, such as new radio (NR) systems, and communication systems evolved after 5G, such as sixth generation (6G) mobile communication systems. They can also be applied to wireless fidelity (WiFi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, and Internet of Vehicles communication systems.

[0115] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0116] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0117] In the embodiments of the present application, "information", "signal", "message", "channel" and "signaling" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. "of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are matched. In addition, the " / " mentioned in this application can be used to express an "or" relationship.

[0118] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0119] To facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail using the communication system shown in Figure 3 as an example. For example, Figure 3 is a schematic diagram of the architecture of a communication system applicable to the interface address allocation method provided in the embodiments of the present application.

[0120] As shown in FIG3 , the communication system includes: a service address allocation agent functional entity and a network management functional entity.

[0121] Optionally, the communication system may further include a service interface automation system.

[0122] The above communication system can be used in different communication system architectures. In different architectures, the above network management functional entity can be different functional entities. They are introduced below.

[0123] As shown in Figure 4, the system architecture shown in Figure 4 includes: a topology orchestrator, a business network management center, a business network edge agent functional entity, a business address allocation agent functional entity, a business interface automation system, a NF deployment agent functional entity, an edge gateway, a topology management system, and a cloud infrastructure.

[0124] The topology orchestrator can be used to manage network topology planning information (such as interface subnet planning, service interface IP segment planning, etc.) and trigger the automatic deployment of NFs on the edge network.

[0125] The business network management center can be used to provide network-wide interface address management functions, maintain network-wide business IP subnet division, IP network segment division, and maintain interface address information allocated to each edge network.

[0126] The business network edge agent functional entity can be used to provide NF with the functions of allocating addresses and obtaining VPNs based on interface types, as well as providing address leasing functions based on NF's identity (ID). In the network slicing or distributed network subnet (core network) scenario, the business network edge agent functional entity has two deployment methods: Method 1 is shared deployment, that is, all slices or subnets share a business network edge agent functional entity. In this case, the message interface provided by the business network edge agent functional entity to the outside needs to carry the ID of the network slice or the ID of the subnet; Method 2 is independent deployment, that is, each network slice or subnet has an independent business network edge agent. In this case, the message interface provided by the business network edge agent functional entity to the outside does not need to carry the ID of the network slice or the ID of the subnet.

[0127] The business address allocation agent can be used to apply for interface addresses from the business network edge agent functional entity on behalf of the NF when the NF is deployed and initially configured, and to renew the addresses from the business network edge agent functional entity regularly, and to release the interface addresses to the business network edge agent functional entity when the NF goes offline.

[0128] The service interface automation system can be used to generate the NF interface configuration based on the obtained interface address, store the configuration in a persistent medium such as a file or data, and publish the service interface IP route. It is understood that the IP route publication method can adopt a dynamic route publication method, such as publishing host routes through the Border Gateway Protocol (BGP).

[0129] The NF deployment agent functional entity can be used to receive NF deployment information, such as NF function pre-configuration, NF supported interface information, etc., and notify the service network edge agent functional entity to apply to the service network management center for the interface address segment required by the NF.

[0130] The edge gateway can be used to provide interface address routing functions.

[0131] A topology management system manages NF topology information within the network. NFs can automatically discover the interface addresses of target NFs through the topology management system, enabling link-level inter-NF connectivity. In 5G (fifth-generation mobile communication technology) networks, the topology management system can be considered equivalent to a network repository function (NRF).

[0132] Cloud infrastructure can be used to provide basic computing, storage, network resources, etc.

[0133] It can be understood that the topology orchestrator and the business network management center can be deployed in a cloud service (region) area. The cloud service region domain can be an operator data center, which can be used for end-to-end business network orchestration and management. The business network edge agent functional entity, the business address allocation agent functional entity, the business interface automation system, the NF deployment agent functional entity, the edge gateway, the topology management system and the cloud infrastructure can be deployed in the edge area. The edge area is usually an edge network. The business address allocation agent functional entity and the business address allocation agent functional entity can be set in the NF, that is, different NFs can include a business address allocation agent functional entity and a business address allocation agent functional entity. In addition, in the system architecture shown in Figure 4, the network management functional entity in the embodiment of the present application can be the above-mentioned business network edge agent functional entity.

[0134] As shown in Figure 5 , the system architecture includes a service interface automation system, a service address allocation proxy functional entity, and a DCHP server. The service interface automation system and the service address allocation proxy functional entity can be described above and will not be further described here. The DCHP server can be a DCHPv4 server or a DCHPv6 server. For details, please refer to the prior art and will not be further described here. In the system architecture shown in Figure 5 , the network management functional entity in the embodiments of the present application can be the aforementioned DCHP server.

[0135] It is understood that the "functional entity" mentioned in the embodiments of the present application is merely an exemplary expression and can be replaced by any other possible expression, such as "module" or "logical function module," without limitation. Furthermore, the "NF" mentioned in the embodiments of the present application can also be replaced by "network element."

[0136] In a communication system, a service address allocation proxy function can request an address from a network management function to allocate an address for an interface. After receiving the address information allocated by the network management function, the service address allocation proxy function can send the address information to a service interface automation system, which then generates a corresponding configuration based on the address information. This allows for automatic acquisition and configuration of address information, eliminating the need for manual acquisition, improving the efficiency of address information acquisition, and enabling configuration of NF interfaces in distributed networks.

[0137] It can be understood that FIG3 is a simplified schematic diagram for ease of understanding, and the communication system may also include other network devices and / or other terminal devices, which are not shown in FIG3 .

[0138] For ease of understanding, the interface address allocation method provided in the embodiment of the present application will be specifically described below with reference to Figures 6 to 11.

[0139] Figure 6 is a flow chart of the interface address allocation method provided by an embodiment of the present application. This method can be applied to the interaction between the service address allocation proxy function entity and the network management function entity in the above communication system.

[0140] As shown in Figure 6, the process of the interface address allocation method is as follows:

[0141] S601: A service address allocation proxy function entity sends a first message to a network management function entity. Correspondingly, the network management function entity receives the first message from the service address allocation proxy function entity.

[0142] The first message may be used to request allocation of an address for an interface of at least one interface type of the first network function.

[0143] The first network function may be a functional entity where the service address allocation proxy functional entity is located, that is, the service address allocation proxy functional entity may be deployed in the first network function.

[0144] The above-mentioned interface types may include interface types in the 3rd Generation Partnership Project (3GPP), such as N2 interface, N4 interface, service-based interface (SBI), N3 interface, N9 interface, S11 interface, S5 interface, S8 interface, etc. Each interface can refer to the existing technology and will not be described in detail here. It is understood that the interface type may also include various interface types in future communication systems. The interface of at least one interface type may be an interface for which an address needs to be configured in the first network function.

[0145] The above-mentioned address can be used to indicate each interface in the interface of at least one interface type, that is, each interface in the interface of the at least one interface type can be determined by the address. The address can be an interface address, such as an IP address, or it can be an interface address and network planning information (recorded as network planning information #1) used to indicate the network where the interface address is located. The network planning information #1 can be an IP domain name, or a VPN, or other information used to indicate the network in network planning. Exemplarily, the above-mentioned address can be an IP address, or an IP address and an IP domain name, or an IP address and a VPN, and the specific address can be determined according to actual conditions. For example, when the IP addresses included in each network are different, the above-mentioned address can be an IP address, that is, a unique interface can be determined by the IP address; or, when there are different networks including the same IP address, the above-mentioned address can be an IP address and an IP domain name, that is, the network can be indicated by the IP domain name, and the IP address is in the network; or, the above-mentioned address can be an IP address and a VPN, that is, the network can be indicated by the VPN, and the IP address is in the network.

[0146] The first message may include at least one of the following: information indicating the first network function, or information indicating at least one interface type. The information indicating the first network function may be the ID of the first network function, such as a universally unique identifier (UUID) or a fully qualified domain name (FQDN) corresponding to the first network function, or may be pre-set or protocol-predefined information for representing the first network function. The information indicating at least one interface type may be the at least one interface type, such as an N2 interface, an N4 interface, etc. The interface type may be an integer or a string, and requires global addressing. The information indicating at least one interface type may also be pre-set or protocol-predefined information for representing each interface type of the at least one interface type. By carrying the information indicating the first network function and the information indicating at least one interface type in the first message, it is possible to request that an address be allocated to an interface of at least one interface type of the first network function.

[0147] It is understood that when there are multiple interfaces in the first network function that require address configuration, the service address allocation proxy function entity may send the first message once or multiple times. That is, the service address allocation proxy function entity may send the first message once, requesting address allocation for the multiple interfaces; or the service address allocation proxy function entity may send the first message multiple times, each of the multiple first messages requesting address allocation for at least some of the multiple interfaces.

[0148] Furthermore, each interface of the at least one interface type can request allocation of at least one address. There are various ways to request allocation of at least one address, such as by presetting or predefining the number of addresses allocated to each interface, or by indicating the number of addresses allocated to each interface via a first message. These are described below.

[0149] Case 1.1: The number of addresses allocated to each interface is pre-defined by the default settings or the protocol.

[0150] The number of addresses requested by each interface can be predefined by the protocol or pre-set in the network management function entity. In other words, the number of addresses corresponding to each interface can be pre-set or pre-defined by the protocol, so that after receiving the first message, the network management function entity can allocate addresses corresponding to the number of addresses to each interface of at least one interface type. It will be understood that the number of addresses corresponding to each interface can be determined based on actual circumstances, that is, the same or different numbers of addresses can be set for each interface based on actual circumstances.

[0151] For example, it is preset in the network management function entity that each interface requesting address allocation is allocated one address. In this case, after receiving the first message, the network management function entity can allocate one address to each interface indicated by the first message.

[0152] For another example, it is preset in the network management function entity to allocate n addresses to the first N interfaces among the interfaces requesting address allocation, and to allocate s addresses to the other interfaces except the first N interfaces. At this time, after receiving the first message, the network management function entity can allocate n addresses to the first N interfaces among the interfaces indicated by the first message, and allocate s addresses to the other interfaces except the first N interfaces among the interfaces indicated by the first message, where N is an integer greater than or equal to 1, and n and s are both positive integers, and n and s are different.

[0153] Case 1.2: The number of addresses allocated to each interface is indicated by the first message.

[0154] The first message may specifically request that a preset number of addresses be allocated to at least one interface type of the first network function. In other words, the first message may indicate the number of addresses to be allocated to each interface of the at least one interface type. It will be appreciated that the number of addresses to be allocated to each interface may be the same or different, and may be flexibly set based on actual circumstances.

[0155] For example, if the first message requests that two addresses be allocated to both the N4 interface and the N2 interface, then upon receiving the first message, the network management function entity may allocate two addresses to each interface indicated by the first message. Alternatively, if the first message requests that two addresses be allocated to the N4 interface and four addresses to the N2 interface, then upon receiving the first message, the network management function entity may allocate two addresses to the N4 interface indicated by the first message and four addresses to the N2 interface.

[0156] In this case, the first message may include at least one of the following: information indicating the first network function, information indicating at least one interface type, or information indicating a preset number. The information indicating the first network function and the information indicating at least one interface type can be specifically described above and are not further described here. The information indicating the preset number can be the number of addresses corresponding to each interface of the at least one interface type, or can be pre-set or protocol-defined information indicating the number of addresses corresponding to each interface. The specific information can be set based on actual circumstances.

[0157] The above content introduces the first message. It can be understood that when the network management function entity is a dynamic host configuration protocol (DHCP) v4 server, the first message can reuse the DHCP discovery message; when the network management function entity is a DHCPv6 server, the first message can reuse the DCHP solicitation message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option and the NF ID option. The interface type address allocation option can be used to indicate each interface type, which may include information elements such as option code (option-code), option length (option-len), and interface type (interface type). For specific information about each information element, please refer to Table 1 below. The NF ID option can be used to indicate the NF, which may include information elements such as option code (option-code), option length (option-len), and ID. For specific information about each information element, please refer to Table 2 below.

[0158] Table 1

[0159] Table 2

[0160] It will be appreciated that after adding the interface type address allocation option and the NF ID option, the newly added interface type address allocation option can be used to indicate at least one of the aforementioned interface types, and the NF ID option can be used to indicate the aforementioned first network function. That is, a DHCP discover message can include the interface type address allocation option and / or the NF ID option. A DCHP solicit message can also include the interface type address allocation option and / or the NF ID option. Furthermore, if an interface requires multiple addresses, multiple DHCP discover messages or DCHP solicit messages can be sent, with each DHCP discover message or DCHP solicit message requesting the allocation of a single address for the interface.

[0161] S602: The network management function entity sends a second message to the service address allocation proxy function entity. Correspondingly, the service address allocation proxy function entity receives the second message from the network management function entity.

[0162] The second message may be used to indicate address information of an interface of at least one interface type.

[0163] Address information can be used to indicate the address assigned to an interface of at least one interface type. The address information can include at least one interface address, such as at least one IP address, and can also include at least one interface address and first network planning information. The first network planning information can be used to indicate information about the network on which the at least one interface address resides. It is understood that the first network planning information can include network planning information corresponding to each of the at least one interface address, and the network planning information corresponding to each of the at least one interface address can be the same or different. The specific configuration can be based on actual circumstances. For example, if the at least one interface address includes interface address #a1, interface address #a2, and interface address #a3, the first network planning information can include network planning information #a1 corresponding to interface address #a1, network planning information #a2 corresponding to interface address #a2, and network planning information #a3 corresponding to interface address #a3. The first network planning information can be an IP domain name or VPN. In other different network plans, such as networks that do not use IP domain names or VPNs, the IP domain name and VPN can be replaced with information in the network plan that indicates the network. In addition, the address information includes information related to network planning. For example, if the interface addresses in each network are unique, the address information may include at least one interface address, meaning a unique interface can be determined based on the interface address. For another example, if the interface addresses in each network are unique, the address information may include at least one interface address and the first network planning information, meaning a unique interface can be determined based on the interface address and the first network planning information. It is understood that an IP domain name or VPN can be represented by a string.

[0164] The second message may include at least one of the following: information indicating the first network function, information indicating at least one interface type, or address information. The information indicating the first network function and the information indicating at least one interface type can be described in detail in "S601" above and will not be repeated here. The address information may include the interface address corresponding to each interface of the at least one interface type. The interface address may be one or more. If there are multiple interface addresses, the addresses may be sent in a list.

[0165] For example, as shown in Table 3, at least one interface type includes an N2 interface, an N3 interface, and an N4 interface. The address assigned to the N2 interface is interface address #1 in VPN#1, the address assigned to the N3 interface is interface address #2 in VPN#2 and interface address #3 in VPN#3, and the address assigned to the N4 interface is interface address #4 in VPN#4 and interface address #5 in VPN#2.

[0166] Table 3

[0167] After receiving the first message, the network management function entity can allocate addresses to each interface of at least one interface type, and after allocating the addresses, it can indicate to the network management function entity through a second message the addresses allocated to each interface of the at least one interface type, that is, the above-mentioned address information.

[0168] It is understood that the network management function entity may allocate a preset number of addresses to each interface of at least one interface type. The number of addresses allocated to each interface of at least one interface type is related to a preset number of addresses, a number of addresses predefined by the protocol, or a number of addresses indicated in the first message. These are described below.

[0169] Regarding the above situation 1.1: If the number of addresses allocated to each interface has been preset or predefined by the protocol, the network management function entity can allocate a corresponding number of addresses to each interface based on the number of addresses.

[0170] Regarding the above situation 1.2: if the number of addresses allocated to each interface is indicated by the first message, the network management function entity may allocate a corresponding number of addresses to each interface according to the preset number indicated by the first message. In this case, the address information is used to indicate the preset number of addresses.

[0171] The above content introduces that the network management function entity allocates a preset number of addresses to each interface of at least one interface type under different circumstances. It can be understood that the second message can also be used to indicate the validity period. The validity period can be the period during which the address indicated by the address information can be allowed to be used, that is, the validity period can be the period during which each interface of at least one interface type can use the allocated address. The validity period can be at the hour level, minute level, second level, etc., and can be set according to actual conditions. In addition, each address allocated by the network management function entity to each interface of at least one interface type corresponds to a validity period, so as to indicate the period during which the address can be allowed to be used through the validity period. The validity periods corresponding to each address can be the same, such as 20 hours (h), or can be different, and can be set according to actual conditions.

[0172] The second message may also include information indicating the validity period, such as a specific value of the validity period, in which case the validity period may be represented by an integer, or pre-set information indicating the validity period, etc. It is understood that the "validity period" mentioned in the embodiments of the present application is merely an exemplary expression, and "validity period" may be replaced by any possible expression, such as "lease period" or "usage period", without limitation.

[0173] The above content introduces the second message. It can be understood that when the network management function entity is a DHCPv4 server, the second message can reuse the DHCP offer (OFFER) message; when the network management function entity is a DHCPv6 server, the second message can reuse the DCHP notification (ADVERTISE) message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option, the IP domain name option of the IP address, the VPN option of the IP address, and the NF ID option. The interface type address allocation option and the NF ID option can refer to the relevant introduction of the aforementioned "S601" and will not be repeated here. The IP domain name option of the IP address can include information elements such as option code, option length, IP domain name (IP domain), and the specific information of each information element can be referred to in Table 4 below. The VPN option of the IP address can include information elements such as option code, option length, VPN, and the specific information of each information element can be referred to in Table 5 below.

[0174] Table 4

[0175] Table 5

[0176] After adding the interface type address allocation option, IP address IP domain name option, IP address VPN option, and NF ID option, the newly added interface type address allocation option can be used to indicate at least one of the aforementioned interface types, the NF ID option can be used to indicate the aforementioned first network function, and the IP address IP domain name option or VPN option can be used to indicate the network on which the IP address resides. That is, a DHCP offer message can include at least one of the following: interface type address allocation option, IP address IP domain name option (or IP address VPN option), NF ID option, or IP address. A DHCP notify message can include at least one of the following: interface type address allocation option, IP address IP domain name option (or IP address VPN option), NF ID option, or IP address. It is understood that the aforementioned address information can be represented by the IP domain name option (or IP address VPN option) and IP address.

[0177] S603: The service address allocation proxy function entity sends address information to the service interface automation system. Correspondingly, the service interface automation system receives the address information from the service address allocation proxy function entity.

[0178] For the address information, please refer to the related introduction of "S602" above, which will not be repeated here.

[0179] If the second message also indicates a validity period, the service address allocation proxy function entity sending the address information to the service interface automation system may specifically include: the service address allocation proxy function entity sending the address information and the validity period to the service interface automation system. In response, the service interface automation system receives the address information and the validity period from the service address allocation proxy function entity. In other words, the validity period may be sent to the service interface automation system, allowing the service interface automation system to determine, based on the validity period, when the address of the interface is about to expire and take appropriate action, such as requesting that the address continue to be allocated for the interface.

[0180] It is understandable that the service address allocation proxy functional entity may further send information indicating at least one interface type to the service interface automation system, and match each address indicated by the address information with each interface, thereby ensuring that the service interface automation system can accurately determine which addresses are allocated to which interfaces after receiving the address information, thereby avoiding address configuration errors and the like.

[0181] S604: The service interface automation system generates an interface configuration for the first network function according to the address information.

[0182] That is, the service interface automation system may generate an interface address configuration of the first network function according to the address information, and save the interface configuration, such as saving the configuration to a persistent medium.

[0183] Furthermore, after the service interface automation system generates the interface address configuration, it can also publish the interface address host route to the network through dynamic route advertisement, such as through BGP. It is understood that the physical network port used by the service interface of the first network function is typically a physical network. When the first network function starts, the IP address of the physical network port can be dynamically obtained through automated mechanisms such as NFVI. Furthermore, after startup, the first network function can obtain the address of the peer NF through the topology management system to complete service interface connection.

[0184] In summary, in the embodiments of the present application, when it is necessary to obtain the addresses of each interface, the service address allocation agent entity can request the network management function entity to allocate an address for at least one interface type of the first network function. The network management function entity can allocate the address based on the request and send the allocated address information to the service address allocation agent entity, so that the service address allocation agent entity sends the address information to the service interface automation system, so that the service interface automation system can perform address configuration based on the address information. In this way, the address of the interface can be automatically acquired and configured during NF deployment, thereby avoiding manual address acquisition and configuration, improving the efficiency of configuring address information, and realizing the configuration of NF interfaces in a distributed network.

[0185] Optionally, in combination with the above embodiment, before the service address allocation proxy functional entity sends the first message to the network management functional entity, the interface address allocation method may further include: the service interface automation system sends a third message to the service address allocation proxy functional entity, and the service address allocation proxy functional entity accordingly receives the third message from the service interface automation system, the third message being used to request address allocation for at least one interface type of the first network function; and the service address allocation proxy functional entity sending the first message to the network management functional entity may specifically include: the service address allocation proxy functional entity sending the first message to the network management functional entity based on the third message. In other words, the service interface automation system may send a request to the service address allocation proxy to allocate an interface of at least one interface type, thereby triggering the service address allocation proxy functional entity to obtain the request for at least one interface type from the network management functional entity.

[0186] The third message may include information indicating at least one interface type. For details, please refer to the aforementioned related description and will not be repeated here. It is understood that the service interface automation system and the service address allocation proxy functional entity may be located within the first network function. In this case, the third message sent by the service interface automation system to the service address allocation proxy functional entity may not include information indicating the first network function. It is also understood that when multiple interface types require address allocation, the service interface automation system may request address allocation for each interface type at a time, i.e., may send the third message multiple times; alternatively, the service interface automation system may request address allocation for multiple interface types, i.e., may send the third message once.

[0187] In addition, with respect to the above situation 1.2: the third message can be specifically used to request that a preset number of addresses be allocated to interfaces of at least one interface type, that is, the third message can indicate the number of addresses that need to be allocated to each interface of at least one interface type. For details, please refer to the aforementioned related introduction and will not be repeated here. In this case, the third message can include at least one of the following: information for indicating at least one interface type, or information for indicating a preset number. For details, please refer to the aforementioned related introduction and will not be repeated here. That is to say, when the third message includes information for indicating at least one interface type and information for indicating a preset number, a request can be made to the service address allocation agent functional entity to allocate a preset number of addresses to interfaces of at least one interface type.

[0188] Optionally, in combination with the above embodiment, after the business interface automation system receives the address information from the business address allocation agent functional entity, the above interface address allocation method may further include: when the address indicated by the address information is invalid, the business address allocation agent functional entity sends a fourth message to the network management functional entity, and accordingly, the network management functional entity receives the fourth message from the business address allocation agent functional entity, and the fourth message is used to request to continue to allocate the address indicated by the address information to the interface of at least one interface type of the first network function; the network management functional entity allocates the address indicated by the address information to the interface of at least one interface type of the first network function based on the fourth message.

[0189] The fourth message may include at least one of the following: information indicating the first network function, information indicating an interface of at least one interface type, or address information. For details, please refer to the aforementioned "S601" and "S602" related introductions, which will not be repeated here.

[0190] When the address indicated by the address information is about to expire, for example, when the usage period of the address indicated by the address information is about to reach the validity period of the address, the service address allocation proxy function entity may request the network management function entity to continue to allocate the address indicated by the address information to at least one interface type of the first network function. In this way, the service address allocation proxy function entity can request to continue to use the address before the address expires, thereby ensuring normal service operation.

[0191] It is understood that after the network management function entity assigns the address indicated by the address information to the interface of at least one interface type of the first network function according to the fourth message, the network management function entity may also send a message to the service address allocation proxy function entity indicating that the address indicated by the address information has been assigned, so that the service address allocation proxy function entity can perform subsequent operations based on the message, such as updating the validity period of the address indicated by the address information. In addition, if the address indicated by the address information assigned to the interface of at least one interface type of the first network function has been assigned to another interface, the network management function entity may assign another address, such as address #a1, to the interface and send specific information about address #a1 to the service address allocation proxy function entity so that the interface uses address #a1 after the address indicated by the address information expires. The specific information may include at least one of the following information about address #a1: IP address, IP domain name, VPN, or validity period. Each of these information can be referred to in the above related description and will not be repeated here.

[0192] It can also be understood that when the network management function entity is a DHCPv4 server, the fourth message can reuse a DHCP request (REQUEST) message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option, the IP domain name option for the IP address, the VPN option for the IP address, and the NF ID option. For details, please refer to the relevant introduction of "S602" above, which will not be repeated here. After the new DHCP option definitions are added, the DHCP request message can include at least one of the following: the interface type address allocation option, the IP domain name option for the IP address (or the VPN option for the IP address), the NF ID option, or the IP address. In other words, the NF ID option can be used to indicate the first functional entity, and the IP address and the IP domain name option for the IP address (or the VPN option for the IP address) can be used to indicate address information.

[0193] When the network management function entity is a DHCPv6 server, the fourth message can reuse the DHCPv6 update (RENEW) message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option, the IP domain name option of the IP address, the VPN option of the IP address, and the NF ID option. For details, please refer to the relevant introduction of "S602" above, which will not be repeated here. After the new DHCP option definitions are added, the DHCPv6 update message can include at least one of the following: the interface type address allocation option, the IP domain name option of the IP address (or the VPN option of the IP address), the NF ID option, or the IP address. That is, the NF ID option can be used to indicate the first functional entity, and the IP address and the IP domain name option of the IP address (or the VPN option of the IP address) can be used to indicate the address information.

[0194] Optionally, in combination with the above embodiment, before the network management function entity receives the first message from the service address allocation proxy function entity, the network management function entity may configure the address segment corresponding to each interface type in the at least one interface type. The address segment may be an interface address segment, or may be an interface address segment and network planning information (recorded as network planning information #2) used to indicate the network where the interface address segment is located. The network planning information #2 may be an IP domain name, or a VPN, or other information used to indicate a network in network planning. Exemplarily, the address segment may be an IP address segment, or an IP address segment and an IP domain name, or an IP address segment and a VPN. For example, when the IP addresses included in each network are different, the address segment may be an IP address segment; for another example, when the same IP address is included in different networks, the address may be an IP address segment and an IP domain name; or, the address may be an IP address segment and a VPN.

[0195] The method by which the network management functional entity configures address segments can be set based on actual circumstances. For example, when the address scale of the deployed network is uncertain, the network management functional entity can request the address segments corresponding to each of the at least one interface type from the NF deployment agent functional entity upon determining that the address segments corresponding to each of the at least one interface type will be needed in the future. When the address scale of the deployed network is determined, the topology orchestrator can send all the interface types planned in the network and the address segments corresponding to the interface type pairs to the network management functional entity for subsequent use by the network management functional entity. The following describes different scenarios.

[0196] Case 2.1: The address scale of the deployed network is uncertain.

[0197] In this case, the topology orchestrator can send the network address planning details, such as the address segments corresponding to each planned interface, to the business network management center. Specifically, the message sent by the topology orchestrator to the business network management center can include at least one of the following: information indicating the interface type of the planned interface or information about the address segments of the planned interface. This allows the business network management center to store the planned network information, allowing subsequent network management functions to obtain the required interface address segments from the business network management center.

[0198] The topology orchestrator may deploy at least one NF at a designated edge site or data center, and the at least one NF includes a first network function. That is, the topology orchestrator may send at least one of the following information to the NF deployment agent functional entity: information indicating the NF type of at least one NF, a software image, or an initial configuration. The NF type may be an NF type in 3GPP, such as SMF, UPF, etc., and the NF type includes a type corresponding to the first network function. It is understood that in future communication systems, other NF types may also be used without limitation. The software image may be software running on the cloud infrastructure of the edge network. For details, please refer to the prior art and will not be described in detail here. The initial configuration may be business function configuration data determined according to different application scenarios. For details, please refer to the prior art and will not be described in detail here.

[0199] After deploying NFs at designated edge sites or data centers, the NF deployment agent functional entity may, based on at least one NF deployed by the topology orchestrator, send a message indicating a first interface type to the network management functional entity, thereby indicating which NF interfaces the network management functional entity needs to support. In other words, the first interface type is the interface type of each interface that needs to be deployed in the deployed NF, and the first interface type belongs to the interface type of the aforementioned planned interfaces. After receiving the message indicating the first interface type, if the network management functional entity does not have sufficient addresses to allocate to interfaces of the first interface type, it may send a fifth message to the service network management center to request the address network segment corresponding to the interfaces of the first interface type.

[0200] Specifically, before the network management function entity receives the first message from the business address allocation agent function entity, the above-mentioned interface address allocation method may also include: the network management function entity sends a fifth message to the business network management center, and accordingly, the business network management center receives the fifth message from the network management function entity, the fifth message is used to obtain the address segment corresponding to the interface of the first interface type, the first interface type includes the interface type of the interface determined to be deployed, and at least one interface type of the first network function belongs to the first interface type; the business network management center sends a sixth message to the network management function entity, and accordingly, the network management function entity receives the sixth message from the business network management center, the sixth message is used to indicate the address segment information corresponding to the interface of the first interface type; the above-mentioned network management function entity sends a second message to the business address allocation agent function entity based on the first message, which may specifically include: the network management function entity sends a second message to the business address allocation agent function entity based on the first message and the sixth message.

[0201] The address segment information may include at least one interface address segment, or at least one interface address segment and second network planning information. The second network planning information may be used to indicate the network to which each interface address segment in the at least one interface address segment resides. It is understood that the second network planning information may include network planning information for each interface address segment in the at least one interface address segment. The network planning information for each interface address segment in the at least one interface address segment may be the same or different, and may be specifically configured based on actual circumstances. For example, to indicate that an interface address segment includes interface address segment #b1, address segment #b2, and address segment #b3, the second network planning information may include network home information #b1 corresponding to address segment #b1, network home information #b2 corresponding to address segment #b2, and network home information #b3 corresponding to address segment #b3. The second network planning information may be an IP domain name or VPN. In other different network plans, such as networks that do not use IP domain names or VPNs for planning, the IP domain name and VPN may be replaced with information in the network plan that indicates the network. In addition, the information included in the address segment can be set according to actual conditions. For example, when the interface addresses in each network are not repeated, the address segment information can be at least one interface address segment; for example, when the interface addresses in each network are repeated, the address segment information can include at least one interface address segment and the second network planning information.

[0202] The fifth message may include information indicating the first interface type. The information indicating the first interface type may be each interface type in the first interface type, or may be information pre-set or pre-defined by a protocol to indicate each interface type in the first interface type.

[0203] The sixth message may include at least one of the following: information indicating the first interface type, or address segment information, for details of which reference may be made to the above related introductions and will not be repeated here. It is understood that each interface type in the first interface type corresponds to an address segment.

[0204] The network management function entity can obtain the address segment information corresponding to the interface of the first interface type from the business network management center. When the business address allocation agent function entity requests to allocate an address for an interface of at least one interface type, it can allocate an address for the interface of the at least one interface type based on the address segment information corresponding to the interface of the first interface type and the first message.

[0205] It is understandable that if the network management function entity has enough addresses for the NF to be deployed, there is no need to perform the above step of obtaining the address segment information corresponding to the first interface type. In other words, in this case, the network management function entity can use local addresses to allocate addresses to each interface.

[0206] After the network management function entity receives the sixth message from the business network management center, the above-mentioned interface address allocation method may also include: the network management function entity sends an eighth message to the edge gateway based on the sixth message, and accordingly, the edge gateway receives the eighth message from the network management function entity, and the eighth message is used to request the configuration of the segment route corresponding to the address segment information.

[0207] The eighth message may include address segment information. The edge gateway may configure segment routing according to the address segment information with reference to the existing technology, which will not be described in detail here.

[0208] Case 2.2: The address scale of the deployed network is determined.

[0209] In this case, the topology orchestrator can send relevant information of all interface types corresponding to the planned network to the network management function entity. Specifically, before the network management function entity receives the first message from the service address allocation proxy function entity, the above-mentioned interface address allocation method can also include: the topology orchestrator sends a seventh message to the network management function entity, and accordingly, the network management function entity receives the seventh message from the topology orchestrator, the seventh message is used to indicate the address segment information corresponding to the interface of the second interface type, the second interface type includes all interface types corresponding to the planned network, and at least one interface type of the first network function belongs to the second interface type; the above-mentioned network management function entity sends the second message to the service address allocation proxy function entity according to the first message, which can specifically include: the network management function entity sends the second message to the service address allocation proxy function entity according to the first message and the seventh message.

[0210] The second interface type may include at least one interface type, and may be sent to the network management function entity by the topology orchestrator.

[0211] The seventh message may include at least one of the following: information indicating the second interface type, or address segments corresponding to each interface type in the second interface type.

[0212] For address segment information, please refer to the relevant introduction in "Case 2.1" above and will not be repeated here.

[0213] In case 2.2, the topology planner may send relevant information of all interfaces in the network plan to the network management function entity in advance, so that the network management function entity can allocate addresses to each interface based on the relevant information.

[0214] After the network management function entity receives the seventh message from the topology orchestrator, the above-mentioned interface address allocation method may also include: the network management function entity sends an eighth message to the edge gateway based on the seventh message, and accordingly, the edge gateway receives the eighth message from the network management function entity, and the eighth message is used to request the configuration of the segment route corresponding to the address segment information.

[0215] The eighth message may include address segment information. The edge gateway may configure segment routing according to the address segment information with reference to the existing technology, which will not be described in detail here.

[0216] Optionally, in conjunction with the above embodiment, the service address allocation proxy function entity sending the address information to the service interface automation system may specifically include: upon determining that the address information can be used, the service address allocation proxy function entity sending the address information to the service interface automation system. This ensures that all addresses configured for each interface of at least one interface type can be used, thereby ensuring normal service operation.

[0217] The service address allocation proxy function entity may confirm whether the address information can be used by sending a request message to the network management function entity to confirm whether the address information can be used. Specifically, after the service address allocation proxy function entity receives the second message from the network management function entity, the above-mentioned interface address allocation method may further include: the service address allocation proxy function entity sending a ninth message to the network management function entity, and the network management function entity correspondingly receives the ninth message from the service address allocation proxy function entity, the ninth message being used to request whether the address information can be used; and the network management function entity sending a tenth message to the service address allocation proxy function entity based on the ninth message, and the service address allocation proxy function entity correspondingly receives the tenth message from the network management function entity, the tenth message being used to indicate that the address information can be used.

[0218] The ninth message may include at least one of the following: information indicating the first functional entity, or address information. For details, refer to the aforementioned related description. The tenth message may be an acknowledgment message, which may include information indicating acknowledgment, such as an ACK character. In other words, after receiving the second message, the service address allocation agent functional entity may confirm with the network management functional entity whether the address information is available.

[0219] It can be understood that when the network management function entity is a DHCPv4 server, the ninth message can reuse the DHCP request message, and the tenth message can reuse the DHCP ACK message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option, the IP domain name option of the IP address, the VPN option of the IP address, and the NF ID option. For details, please refer to the relevant introduction of "S602" above, which will not be repeated here. After the new DHCP option definition is added, the DHCP request message can include at least one of the following: the interface type address allocation option, the IP domain name option of the IP address (or the VPN option of the IP address), the NF ID option, or the IP address. That is, the NF ID option can be used to indicate the first functional entity, and the IP address and the IP domain name option of the IP address (or the VPN option of the IP address) can be used to indicate the address information.

[0220] When the network management function entity is a DHCPv6 server, the ninth message can reuse the DHCPv6 request message, and the tenth message can reuse the DHCPv6 acknowledgement (REPLY) message. In this case, new DHCP option definitions can be added, such as the interface type address allocation option, the IP domain name option of the IP address, the VPN option of the IP address, and the NF ID option. For details, please refer to the relevant introduction of "S602" above, which will not be repeated here. After the new DHCP option definitions are added, the DHCPv6 request message can include at least one of the following: the interface type address allocation option, the IP domain name option of the IP address (or the VPN option of the IP address), the NF ID option, or the IP address. That is, the NF ID option can be used to indicate the first functional entity, and the IP address and the IP domain name option of the IP address (or the VPN option of the IP address) can be used to indicate the address information.

[0221] Scenario 1:

[0222] Figure 7 is a second flow diagram of the interface address allocation method provided in an embodiment of the present application. This method is applicable to the aforementioned communication system and primarily involves interaction between a service address allocation proxy functional entity and a service network edge proxy functional entity. In scenario 1, when the address scale of the network that the service address allocation proxy functional entity can deploy is uncertain, the service address allocation proxy functional entity requests the network management functional entity to allocate an address for at least one interface type of the first network function. The network management functional entity may allocate an address for at least one interface type of the first network function.

[0223] As shown in Figure 7, the process of the interface address allocation method is as follows:

[0224] S701: The topology orchestrator sends a message #1 to the service network management center. Correspondingly, the network management center receives the message #1 from the topology orchestrator.

[0225] Message #1 can be used to indicate the address network segment of an interface of a first interface type, where the first interface type includes the interface type of the interface to be deployed. Message #1 can include at least one of the following: information indicating the first interface type, or the address network segment of the first interface type. For details, please refer to the relevant description of the embodiment shown in Figure 6 above, and will not be repeated here.

[0226] S702: The service network management center sends a first confirmation message to the topology orchestrator according to message #1. Correspondingly, the topology orchestrator receives the first confirmation message from the service network management center.

[0227] After receiving message #1, the service network management center may save the relevant information of the network address planning, that is, the address segment of the interface of the first interface type mentioned above, and may return a first confirmation message.

[0228] S703: The topology orchestrator sends message #2 to the NF deployment agent functional entity. Correspondingly, the NF deployment agent functional entity receives message #2 from the topology orchestrator.

[0229] Message #2 is used to indicate the deployment of at least one NF, where the at least one NF includes a first network function. Message #2 may include at least one of the following: information indicating the NF type of the at least one NF, a software image, or an initial configuration. For details, please refer to the relevant description of the embodiment shown in FIG. 6 , and will not be repeated here.

[0230] S704: The NF deployment agent function entity sends message #3 to the service network edge agent function entity. Correspondingly, the service network edge agent function entity receives message #3 from the NF deployment agent function entity.

[0231] Message #3 is used to indicate the interface type of at least one deployed NF. That is, after deploying the at least one NF, addresses must be allocated for the interfaces of the at least one NF. Thus, upon receiving message #3, the service network edge agent functional entity can confirm whether it has sufficient addresses for allocation. If sufficient addresses are available for allocation, there is no need to request the service network center for the address segments of interfaces of each interface type; local addresses can be directly used for allocation. If insufficient addresses are available for allocation, the service network center can be requested for the address segments of interfaces of each interface type, and addresses can be allocated based on these address segments.

[0232] S705: The service network edge agent function entity sends a second confirmation message to the NF deployment agent function entity according to message #3. Correspondingly, the service network edge agent function entity receives the second confirmation message from the NF deployment agent function entity.

[0233] That is, the service network edge agent function entity may notify the NF deployment agent function entity that message #3 has been received through the second confirmation message.

[0234] S706: The service network edge agent function entity sends message #4 to the service network management center. Correspondingly, the service network management center receives message #4 from the service network edge agent function entity.

[0235] Message #4 may be the fifth message in the embodiment shown in Figure 6. The specific implementation of S706 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0236] S707: The service network management center sends message #5 to the service network edge agent function entity according to message #4. Correspondingly, the service network edge agent function entity receives message #5 from the service network management center.

[0237] Message #5 may be the sixth message in the embodiment shown in Figure 6. The specific implementation of S707 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0238] S708: The service network edge proxy function entity sends message #6 to the edge gateway according to message #5. Correspondingly, the edge gateway receives message #5 from the service network edge proxy function entity.

[0239] Message #6 may be the eighth message in the embodiment shown in Figure 6. The specific implementation of S708 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0240] S709: The NF deployment agent functional entity deploys at least one NF.

[0241] That is, the NF deployment agent functional entity can complete operations such as deploying related resources of at least one NF (such as virtual machines, central processing units (CPUs), memory, disks, network bandwidth, and other resources), loading software images, and starting NF software. For details, please refer to the existing technology and will not be repeated here.

[0242] S710: The service interface automation system sends a message #6 to the service address allocation proxy function entity. Correspondingly, the service address allocation proxy function entity receives the message #6 from the service interface automation system.

[0243] Message #6 may be the third message in the embodiment shown in Figure 6. The specific implementation of S710 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0244] S711: The service address allocation proxy function entity sends message #7 to the service network edge proxy function entity according to message #6. Correspondingly, the service network edge proxy function entity receives message #7 from the service address allocation proxy function entity.

[0245] Message #7 may be the first message in the embodiment shown in Figure 6. The specific implementation of S711 may refer to the related introduction of "S601" above, which will not be repeated here.

[0246] S712: The service network edge proxy function entity sends message #8 to the service address allocation proxy function entity according to message #7. Correspondingly, the service address allocation proxy function entity receives message #8 from the service network edge proxy function entity.

[0247] Message #8 may be the second message in the embodiment shown in Figure 6. The specific implementation of S712 may refer to the related introduction of "S602" above, which will not be repeated here.

[0248] S713: The service address allocation proxy function entity sends message #9 to the service interface automation system according to message #8. Correspondingly, the service interface automation system receives message #9 from the service address allocation proxy function entity.

[0249] Message #9 may be used to indicate the address information of at least one interface type. The specific implementation of S713 may refer to the related introduction of the aforementioned "S603", which will not be repeated here.

[0250] S714 , the service interface automation system generates an interface configuration for the first network function according to message # 9 .

[0251] For the specific implementation of S714, please refer to the relevant introduction of "S604" mentioned above, which will not be repeated here.

[0252] S715: The service interface automation system publishes the interface host address route.

[0253] For the specific implementation of S715, reference may be made to the relevant introduction in the embodiment shown in FIG6 , which will not be described again here.

[0254] It is understood that the specific implementation of S701-S715 can refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here. In this case, the service network edge agent functional entity in scenario 1 can be the network management functional entity in the embodiment shown in Figure 6.

[0255] Scenario 2:

[0256] Figure 8 is a third flow diagram of the interface address allocation method provided in an embodiment of the present application. This method is applicable to the aforementioned communication system and primarily involves interaction between a service address allocation proxy functional entity and a service network edge proxy functional entity. In scenario 2, when the address scale of the network in which the service address allocation proxy functional entity can be deployed is determined, the service address allocation proxy functional entity requests the network management functional entity to allocate an address for at least one interface type of the first network function. The network management functional entity may allocate an address for at least one interface type of the first network function.

[0257] As shown in Figure 8, the process of the interface address allocation method is as follows:

[0258] S801: The topology orchestrator sends a message #1 to the NF deployment agent functional entity. In response, the NF deployment agent functional entity receives the message #1 from the topology orchestrator.

[0259] Message #1 is used to indicate the deployment of at least one NF, where the at least one NF includes a first network function. Message #1 may include at least one of the following: information indicating the NF type, a software image, or an initial configuration of the at least one NF. For details, refer to the description of the embodiment shown in FIG. 6 , and will not be repeated here.

[0260] S802: The topology orchestrator sends message #2 to the service network edge proxy function entity. Correspondingly, the service network edge proxy function entity receives message #2 from the topology orchestrator.

[0261] Message #2 may be the seventh message in the embodiment shown in Figure 6. The specific implementation of S802 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0262] S803: The service network edge proxy function entity sends message #3 to the edge gateway according to message #2. Correspondingly, the edge gateway receives message #3 from the service network edge proxy function entity.

[0263] Message #3 may be the eighth message in the embodiment shown in Figure 6. The specific implementation of S803 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0264] S804: The NF deployment agent functional entity deploys at least one NF.

[0265] For S804, please refer to the relevant introduction of "S709" mentioned above, which will not be repeated here.

[0266] S805: The service interface automation system sends message #4 to the service address allocation proxy function entity. Correspondingly, the service address allocation proxy function entity receives message #4 from the service interface automation system.

[0267] Message #4 may be the third message in the embodiment shown in Figure 6. The specific implementation of S805 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0268] S806: The service address allocation proxy function entity sends message #5 to the service network edge proxy function entity according to message #4. Correspondingly, the service network edge proxy function entity receives message #5 from the service address allocation proxy function entity.

[0269] Message #5 may be the first message in the embodiment shown in Figure 6. The specific implementation of S806 may refer to the related introduction of "S601" above, which will not be repeated here.

[0270] S807: The service network edge proxy function entity sends message #6 to the service address allocation proxy function entity according to message #5. Correspondingly, the service address allocation proxy function entity receives message #6 from the service network edge proxy function entity.

[0271] Message #6 may be the second message in the embodiment shown in Figure 6. The specific implementation of S807 may refer to the related introduction of "S602" above, which will not be repeated here.

[0272] S808: The service address allocation proxy function entity sends message #7 to the service interface automation system according to message #6. Correspondingly, the service interface automation system receives message #7 from the service address allocation proxy function entity.

[0273] Message #7 may be used to indicate the address information of at least one interface type. The specific implementation of S808 may refer to the related introduction of "S603" above, which will not be repeated here.

[0274] S809 , the service interface automation system generates an interface configuration for the first network function according to message #7.

[0275] The specific implementation of S809 can refer to the relevant introduction of the aforementioned "S604", which will not be repeated here.

[0276] S810: The service interface automation system publishes the interface host address route.

[0277] For the specific implementation of S810, reference may be made to the relevant introduction in the embodiment shown in FIG6 , which will not be described in detail here.

[0278] It is understood that the specific implementation of S801-S810 can refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here. In this case, the service network edge agent functional entity in scenario 2 is the network management functional entity in the embodiment shown in Figure 6.

[0279] Scenario 3:

[0280] Figure 9 is a fourth flow diagram of the interface address allocation method provided in an embodiment of the present application. This method is applicable to the aforementioned communication system and primarily involves interaction between a service address allocation proxy functional entity and a DHCPv4 server. In scenario 3, the service address allocation proxy functional entity may request the DHCPv4 server to allocate an address for at least one interface type of a first network function. The DHCPv4 server may allocate an address for at least one interface type of the first network function based on the request.

[0281] As shown in Figure 9, the process of the interface address allocation method is as follows:

[0282] S901: The service interface automation system sends an interface address allocation request message to a service address allocation proxy functional entity. Correspondingly, the service address allocation proxy functional entity receives the interface address allocation request message from the service interface automation system.

[0283] The interface address allocation request message may be the third message in the embodiment shown in Figure 6. The specific implementation of S901 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0284] S902: The service address allocation proxy function entity sends a DHCP discover message to the DHCPv4 server according to the interface address allocation request message. Correspondingly, the DHCPv4 server receives the DHCP discover message from the service address allocation proxy function entity.

[0285] S903: The DHCPv4 server sends a DHCP offer message to the service address allocation proxy function entity according to the DHCP discover message. Correspondingly, the service address allocation proxy function entity receives the DHCP offer message from the DHCPv4 server.

[0286] S904: The service address allocation agent function entity sends a DHCP request message to the DHCPv4 server according to the DHCP offer message. Correspondingly, the DHCPv4 server receives the DHCP request message from the service address allocation agent function entity.

[0287] S905: The DHCPv4 server sends a DHCP confirmation message to the service address allocation proxy function entity according to the DHCP request message. Correspondingly, the service address allocation proxy function entity receives the DHCP confirmation message from the DHCPv4 server.

[0288] S906: The service address allocation proxy function entity sends an interface address allocation result message to the service interface automation system according to the DHCP offer message and the DHCP acknowledgement message. Correspondingly, the service interface automation system receives the interface address allocation result message from the service address allocation proxy function entity.

[0289] The interface address allocation result message may be used to indicate the address information of an interface of at least one interface type. The specific implementation of S906 may refer to the related introduction of the aforementioned "S603", which will not be repeated here.

[0290] It is understood that the specific implementation of S901-S906 can refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here. In this case, the DHCPv4 server in scenario 3 is the network management function entity in the embodiment shown in Figure 6.

[0291] Scenario 4:

[0292] Figure 10 is a flowchart diagram of the fifth embodiment of the interface address allocation method provided in an embodiment of the present application. This method is applicable to the aforementioned communication system and primarily involves interaction between a service address allocation proxy functional entity and a DHCPv6 server. In scenario 4, the service address allocation proxy functional entity may request the DHCPv6 server to allocate an address for at least one interface type of the first network function. The DHCPv6 server may allocate an address for at least one interface type of the first network function based on the request.

[0293] As shown in Figure 10, the process of the interface address allocation method is as follows:

[0294] S1001: The service interface automation system sends an interface address allocation request message to a service address allocation proxy functional entity. Correspondingly, the service address allocation proxy functional entity receives the interface address allocation request message from the service interface automation system.

[0295] The interface address allocation request message may be the third message in the embodiment shown in Figure 6. The specific implementation of S1001 may refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here.

[0296] S1002: The service address allocation proxy function entity sends a DHCPv6 solicitation message to the DHCPv6 server according to the interface address allocation request message. Correspondingly, the DHCPv6 server receives the DHCPv6 solicitation message from the service address allocation proxy function entity.

[0297] S1003: The DHCPv6 server sends a DHCPv6 notify message to the service address allocation proxy function entity according to the DHCPv6 solicit message. Correspondingly, the service address allocation proxy function entity receives the DHCPv6 notify message from the DHCPv6 server.

[0298] S1004: The service address allocation proxy function entity sends a DHCPv6 request message to the DHCPv6 server according to the DHCPv6 notification message. Correspondingly, the DHCPv6 server receives the DHCPv6 request message from the service address allocation proxy function entity.

[0299] S1005: The DHCPv6 server sends a DHCPv6 reply message to the service address allocation proxy function entity according to the DHCPv6 request message. Correspondingly, the service address allocation proxy function entity receives the DHCPv6 reply message from the DHCPv6 server.

[0300] S1006: The service address allocation proxy function entity sends an interface address allocation result message to the service interface automation system based on the DHCPv6 reply message and the DHCPv6 notification message. Correspondingly, the service interface automation system receives the interface address allocation result message from the service address allocation proxy function entity.

[0301] The interface address allocation result message may be used to indicate the address information of an interface of at least one interface type. The specific implementation of S1006 may refer to the related introduction of the aforementioned "S603", which will not be repeated here.

[0302] It is understood that the specific implementation of S1001-S1006 can refer to the relevant introduction in the embodiment shown in Figure 6 above, and will not be repeated here. In this case, the DHCPv6 server in scenario 4 is the network management function entity in the embodiment shown in Figure 6.

[0303] Figure 11 is a flowchart of the sixth method for allocating an interface address provided by an embodiment of the present application. This method can be applied to the interaction between the service address allocation proxy function entity and the network management function entity in the above communication system.

[0304] As shown in Figure 11, the process of the interface address allocation method is as follows:

[0305] S1101: A service address allocation proxy function entity sends a first message to a network management function entity. Correspondingly, the network management function entity receives the first message from the service address allocation proxy function entity.

[0306] The first message may be used to request to continue using the first address allocated to the interface of the first interface type of the first network function, and the first message may be called a lease renewal message.

[0307] The first interface type may include at least one interface type, which may be at least one interface type in 3GPP, such as at least one interface type among N2 interface, N4 interface, SBI interface, N3 interface, N9 interface, S11 interface, S5 interface, and S8 interface, and may also be at least one interface type in a future communication system.

[0308] The first address may be an address assigned to an interface of the first interface type, that is, the interface of the first interface type may be determined by the first address. The first address may include at least one interface address, such as at least one IP address, or may include at least one interface address and first network planning information for indicating the network where the at least one interface address is located. It is understandable that the first network planning information may include network planning information corresponding to each interface address in the at least one interface address, and the network planning information corresponding to each interface address in the at least one interface address may be the same or different, and may be specifically set according to actual conditions. For example, at least one interface address includes interface address #c1 and interface address #c2, and the first network planning information may include network planning information #c1 corresponding to interface address #c1 and network planning information #c2 corresponding to interface address #c2. The first network planning information may be an IP domain name, or a VPN, or other information used to indicate a network in network planning. Exemplarily, the first address can be at least one IP address, or at least one IP address and an IP domain name, or at least one IP address and a VPN. The specific address can be determined based on actual conditions. For example, when the IP addresses included in each network are different, the first address can be at least one IP address; for example, when the same IP address is included in different networks, the first address can be at least one IP address and an IP domain name; or, the first address can be at least one IP address and a VPN.

[0309] The first message may include at least one of the following: information indicating the first network function, information indicating the first interface type, or information indicating the first address. The information indicating the first network function can refer to the relevant introduction of the aforementioned "S601" and will not be repeated here. The information indicating the first interface type can be the various interface types included in the first interface type, such as N2 interface, N4 interface, etc.; it can also be pre-set or protocol-predefined information for representing each interface type in the first interface type. The information indicating the first address may include the above-mentioned at least one interface address and / or the first network planning information, and can also be pre-set or protocol-predefined information for representing the first address.

[0310] The service address allocation proxy function entity sends a first message to the network management function entity, requesting the network management function entity to allocate a first address to an interface of a first interface type of a first network function, ie, to continue to renew the lease of the first address.

[0311] S1102: The network management function entity sends a second message to the service address allocation proxy function entity according to the first message. Correspondingly, the service address allocation proxy function entity receives the second message from the network management function entity.

[0312] The second message is used to assign a second address to an interface of the first interface type. The second address can be the same as or different from the first address. For example, when the first address is available, the network management function entity can assign the first address to an interface of the first interface type of the first network function. Alternatively, when the first address has been assigned to another interface, the network management function entity can assign the second address, i.e., an address other than the first address, to an interface of the first interface type of the first network function. It will be understood that the second address can include at least one interface address, and the number of interface addresses included in it is the same as the number of interface addresses included in the first address.

[0313] The second message may include at least one of the following: information for indicating the first network function, information for indicating the first interface type, or information for indicating the second address. The information for indicating the first network function and the information for indicating the first interface type can refer to the relevant introduction of the aforementioned "S1101", which will not be repeated here. The information for indicating the second address can be the second interface address and / or the second network planning information. The second interface address is similar to the first interface address, and the two can be the same or different. The second interface address can refer to the relevant introduction of the first interface address, which will not be repeated here; the second network planning information is similar to the first network planning information, and the two can be the same or different. The second network planning information can refer to the relevant introduction of the first network planning information, which will not be repeated here. The information for indicating the second address can also be pre-set or protocol-predefined information for representing the second address.

[0314] After receiving the first message, the network management function entity may determine whether the first address is available, that is, the first address is not allocated to another interface. If the first address is available, the network management function entity may continue to allocate the first address to the interface of the first interface type of the first network function, that is, the renewal is successful. If the first address is unavailable, the network management function entity may allocate another address, such as the second address, to the interface of the first interface type of the first network function, that is, the renewal fails.

[0315] The second message can also be used to indicate the effective duration, which is the duration during which the second address can be allowed to be used. That is, the effective duration can be the duration during which the interface of the first interface type of the first network function can use the second address. For the effective duration, please refer to the relevant introduction of "S602" above, which will not be repeated here. In this case, the second message can also include information for indicating the effective duration, such as the specific value of the effective duration, or pre-set information for indicating the effective duration, etc. It can be understood that the "effective duration" mentioned in the embodiment of the present application is only an exemplary expression, and the "effective duration" can also be replaced by any possible expression, such as "lease duration" or "usage duration", etc., without limitation.

[0316] In summary, in an embodiment of the present application, the service address allocation agent function entity can allocate a second address to the interface by sending a message to the network management function entity requesting to continue using the first address allocated to the interface of the first interface type of the first network function when the first address is about to expire, thereby avoiding the situation where the first network function cannot use the first address after the first address expires, resulting in service errors.

[0317] It can be understood that if the network management function entity does not receive the above-mentioned first message after the usage time of the first address reaches the validity time of the first address, the network management function entity may release the first address.

[0318] Optionally, in combination with the above embodiment, after receiving the second message from the network management function entity, the service address allocation proxy entity may determine whether the second address indicated in the second message is the same as the first address. If the second address is different from the first address, it can be considered that the network management function entity has reassigned an address to the interface of the first interface type of the first network function. In this case, the service address allocation proxy entity may notify the service interface automation system to update the interface address, i.e., update the address of the interface of the first interface type of the first network function to the second address.

[0319] Specifically, after the service address allocation proxy function entity receives the second message from the network management function entity, the above-mentioned interface address allocation method may further include: the service address allocation proxy function entity sends a third message to the service interface automation system; accordingly, the service interface automation system receives the third message from the service address allocation proxy function entity (S1103 in Figure 11), where the third message is used to request that the first address corresponding to the interface of the first interface type of the first network function be updated to the second address; and the service interface automation system updates the first address to the second address according to the third message (S1104 in Figure 11).

[0320] The third message may include at least one of the following: information indicating the first interface type, information indicating the first address, or information indicating the second address. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0321] It can be understood that the business interface automation system can reconfigure the address of the interface (i.e., the second address) after the address of the interface of the first interface type of the first network function changes, and can also trigger the link establishment process with the opposite device, i.e., re-establish the interface link with the opposite device.

[0322] Optionally, in combination with the above embodiment, the business address allocation agent functional entity may send a first message to the network management functional entity when the first address becomes invalid. When the first address becomes invalid can be understood as when the first address is about to become invalid, such as when the usage time of the first address is about to reach the valid time of the first address. There are many ways for the business address allocation agent functional entity to determine the time point for sending the first message, such as: the business address allocation agent functional entity may start a timer when the first address starts to be used, and when the timer time is about to reach the valid time of the first address, send the first message to the network management functional entity; for example: the time point when the first address is about to become invalid can be calculated based on the valid time of the first address, and the first message is sent to the network management functional entity at that time point. The way in which the business address allocation agent functional entity determines the time point for sending the first message can be determined based on actual conditions, and the embodiments of the present application do not impose any restrictions on this.

[0323] Optionally, in combination with the above embodiment, the service address allocation proxy function entity may send a first message to the network management function entity upon receiving a message from the service interface automation system requesting to obtain the first address.

[0324] Specifically, before the business address allocation agent functional entity sends the first message to the network management functional entity, the above-mentioned interface address allocation method may also include: the business interface automation system sends a fourth message to the business address allocation agent functional entity, and accordingly, the business address allocation agent functional entity receives the fourth message from the business interface automation system (S1100 in Figure 11), and the fourth message is used to request allocation of the first address; the above-mentioned business address allocation agent functional entity sends the first message to the network management functional entity, including: the business address allocation agent functional entity sends the first message to the network management functional entity based on the fourth message.

[0325] The fourth message may include at least one of the following: information indicating the first interface type, or information indicating the first address. For details, please refer to the above-mentioned related introduction and will not be repeated here.

[0326] It can be understood that after the first network function is restarted, such as after the first network function fails and is restarted, the interface address needs to remain unchanged. At this time, the business interface automation system can read the configuration information from the location where the configuration data is stored (such as a persistent medium), and the configuration information can include information such as the address of the interface of the first interface type is the first address; and send a fourth message to the business address allocation agent function entity to request the allocation of the first address. After receiving the fourth message, the business address allocation agent function entity can request the network management function entity to continue to allocate the first address for the interface of the first interface type of the first network function according to the fourth message. In this way, after the first network function is restarted, an available address can be provided for the interface of the first interface type in the first network function, avoiding the situation where the address is unavailable, resulting in business errors.

[0327] In addition, the embodiment shown in Figure 6 and the embodiment shown in Figure 11 can be used in combination, such as first assigning an address to an interface of at least one interface type, and then requesting to continue using the address when the address is about to expire. The specific settings can be made according to actual conditions without any restrictions.

[0328] The interface address allocation method provided by the embodiment of the present application is described in detail above in conjunction with Figures 6 to 11. The communication device for executing the interface address allocation method provided by the embodiment of the present application is described in detail below in conjunction with Figures 12 and 13.

[0329] Figure 12 is a structural diagram of a communication device according to an embodiment of the present application. As shown in Figure 12, the communication device 1200 includes a transceiver module 1201 and a processing module 1202. For ease of illustration, Figure 12 only shows the main components of the communication device.

[0330] The transceiver module 1201 is used to perform the transceiver function of the method shown in FIG. 6 to FIG. 11 , and the processing module 1202 is used to perform other functions of the method shown in FIG. 6 to FIG. 11 except the transceiver function.

[0331] Optionally, the transceiver module 1201 may include a sending module (not shown in FIG12 ) and a receiving module (not shown in FIG12 ). The sending module is used to implement the sending function of the communication device 1200 , and the receiving module is used to implement the receiving function of the communication device 1200 .

[0332] Optionally, the communication device 1200 may further include a storage module (not shown in FIG. 12 ) storing a program or instruction. When the processing module 1202 executes the program or instruction, the communication device 1200 may perform the functions of the network device (e.g., the service address allocation agent function entity or the network management function entity) in the methods shown in FIG. 6 to FIG. 11 in the above-mentioned method.

[0333] It can be understood that the communication device 1200 can be a network device, a chip (system) or other parts or components that can be set in the network device, or a device that includes a network device. This application does not limit this.

[0334] In addition, the technical effects of the communication device 1200 can refer to the technical effects of the interface address allocation method shown in Figures 6 to 11, and will not be repeated here.

[0335] Figure 13 is a second structural diagram of a communication device provided in an embodiment of the present application. Exemplarily, the communication device may be a network device, or a chip (system) or other component or assembly that can be provided in a network device. As shown in Figure 13, the communication device 1300 may include a processor 1301. Optionally, the communication device 1300 may further include a memory 1302 and / or a transceiver 1303. The processor 1301 is coupled to the memory 1302 and the transceiver 1303, such as by a communication bus.

[0336] The following is a detailed introduction to the various components of the communication device 1300 with reference to FIG13:

[0337] The processor 1301 is the control center of the communication device 1300 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1301 can be one or more CPUs, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0338] Optionally, the processor 1301 can execute various functions of the communication device 1300 by running or executing software programs stored in the memory 1302 and calling data stored in the memory 1302, such as executing the interface address allocation method shown in Figures 6 to 11 above.

[0339] In a specific implementation, as an embodiment, the processor 1301 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG13 .

[0340] In a specific implementation, as an embodiment, the communication device 1300 may also include multiple processors, such as the processor 1301 and the processor 1304 shown in FIG13 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0341] Among them, the memory 1302 is used to store the software program for executing the solution of this application, and the execution is controlled by the processor 1301. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0342] Alternatively, the memory 1302 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1302 may be integrated with the processor 1301 or exist independently and be coupled to the processor 1301 via an interface circuit (not shown in FIG. 13 ) of the communication device 1300. This embodiment of the present application does not specifically limit this.

[0343] Transceiver 1303 is used for communication with other communication devices. For example, if communication device 1300 is a terminal, transceiver 1303 can be used to communicate with a network device or another terminal device. For another example, if communication device 1300 is a network device, transceiver 1303 can be used to communicate with a terminal or another network device.

[0344] Optionally, the transceiver 1303 may include a receiver and a transmitter (not shown separately in FIG13 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a sending function.

[0345] Optionally, the transceiver 1303 can be integrated with the processor 1301, or can exist independently and be coupled to the processor 1301 through the interface circuit of the communication device 1300 (not shown in Figure 13). This embodiment of the present application does not specifically limit this.

[0346] It is understandable that the structure of the communication device 1300 shown in FIG13 does not constitute a limitation on the communication device, and an actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0347] In addition, the technical effects of the communication device 1300 can refer to the technical effects of the methods described in the above method embodiments, and will not be repeated here.

[0348] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0349] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0350] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0351] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0352] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0353] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0354] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0355] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0356] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 devices or units, which can be electrical, mechanical or other forms.

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

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

[0359] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0360] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An interface address allocation method, characterized in that, The method includes: The service address allocation proxy function entity sends a first message to the network management function entity, where the first message is used to request to allocate addresses for interfaces of at least one interface type of the first network function; The service address allocation proxy function entity receives a second message from the network management function entity, where the second message is used to indicate the address information of the interfaces of the at least one interface type; The service address allocation proxy function entity sends the address information to the service interface automation system.

2. The method according to claim 1, wherein The method further includes: The service address allocation proxy function entity receives a third message from the service interface automation system, where the third message is used to request to allocate addresses for the interfaces of the at least one interface type; The service address allocation proxy function entity sends a first message to the network management function entity, including: The service address allocation proxy function entity sends the first message to the network management function entity according to the third message.

3. The method according to claim 1 or 2, characterized in that, The first message is specifically used to request to allocate a preset number of addresses for interfaces of at least one interface type of the first network function, and the address information is used to indicate the preset number of addresses.

4. The method according to any one of claims 1 to 3, characterized in that, The second message is further used to indicate a valid duration, where the valid duration is the duration for which the addresses indicated by the address information can be allowed to be used. The service address allocation proxy function entity sends the address information to the service interface automation system, including: The service address allocation proxy function entity sends the address information and the valid duration to the service interface automation system.

5. The method according to any one of claims 1-4, characterized in that, The address information includes at least one interface address and first network planning information, where the first network planning information is used to indicate information about the network where the at least one interface address is located.

6. The method according to any one of claims 1-5, characterized in that, The service address allocation proxy function entity sends the address information to the service interface automation system, including; The service address allocation proxy function entity sends the address information to the service interface automation system when it determines that the address information can be used.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: When the addresses indicated by the address information become invalid, the service address allocation proxy function entity sends a fourth message to the network management function entity, where the fourth message is used to request to continue to allocate the addresses indicated by the address information for interfaces of at least one interface type of the first network function.

8. A method for allocating interface addresses, characterized in that, The method includes: The network management function entity receives a first message from the service address allocation proxy function entity, where the first message is used to request to allocate addresses for interfaces of at least one interface type of the first network function; The network management function entity sends a second message to the service address allocation proxy function entity according to the first message, where the second message is used to indicate the address information of the interfaces of the at least one interface type.

9. The method according to claim 8, wherein The first message is specifically used to request to allocate a preset number of addresses for interfaces of at least one interface type of the first network function, and the address information is used to indicate the preset number of addresses.

10. The method according to claim 8 or 9, characterized in that, Before the network management function entity receives the first message from the service address allocation proxy function entity, the method further includes: The network management function entity sends a fifth message to the service network management center. The fifth message is used to obtain the address network segment corresponding to the interface of the first interface type. The first interface type includes the interface types of the interfaces determined to be deployed, and at least one interface type of the first network function belongs to the first interface type; The network management function entity receives a sixth message from the service network management center. The sixth message is used to indicate the address network segment information corresponding to the interface of the first interface type; The network management function entity sends a second message to the service address allocation proxy function entity according to the first message, including: The network management function entity sends the second message to the service address allocation proxy function entity according to the first message and the sixth message.

11. The method according to claim 8 or 9, characterized in that, Before the network management function entity receives the first message from the service address allocation proxy function entity, the method further includes: The network management function entity receives a seventh message from the topology orchestrator. The seventh message is used to indicate the address network segment information corresponding to the interface of the second interface type. The second interface type includes all interface types corresponding to the planned network, and at least one interface type of the first network function belongs to the second interface type; The network management function entity sends a second message to the service address allocation proxy function entity according to the first message, including: The network management function entity sends the second message to the service address allocation proxy function entity according to the first message and the seventh message.

12. The method according to claim 10 or 11, characterized in that, The method further includes: The network management function entity sends an eighth message to the edge gateway according to the sixth message or the seventh message. The eighth message is used to request to configure the network segment route corresponding to the address network segment information.

13. The method according to any one of claims 8-12, characterized in that, The address information includes at least one interface address and first network planning information. The first network planning information is used to indicate the information of the network where the at least one interface address is located.

14. A method for allocating interface addresses, characterized in that, The method includes: The service interface automation system receives address information from the service address allocation proxy function entity. The address information is used to indicate the addresses allocated for the interfaces of at least one interface type of the first network function; The service interface automation system generates the interface configuration of the first network function according to the address information.

15. The method according to claim 14, wherein Before the service interface automation system receives the address information from the service address allocation proxy function entity, the method further includes: The service interface automation system sends a third message to the service address allocation proxy function entity. The third message is used to request to allocate addresses for the interfaces of at least one interface type of the first network function.

16. The method according to claim 15, wherein The third message is specifically used to request to allocate a preset number of addresses for the interfaces of the at least one interface type, and the address information is used to indicate the preset number of addresses.

17. The method according to any one of claims 14 - 16, characterized in that, The address information includes at least one interface address and first network planning information. The first network planning information is used to indicate the information of the network where the at least one interface address is located.

18. An interface address allocation method, characterized in that, The method includes: The service address allocation proxy functional entity sends a first message to the network management functional entity, and the network management functional entity receives the first message from the service address allocation proxy functional entity. The first message is used to request the allocation of an address for at least one interface type of a first network function; The network management functional entity sends a second message to the service address allocation proxy functional entity according to the first message. The service address allocation proxy functional entity receives the second message from the network management functional entity. The second message is used to indicate the address information of the at least one interface type of interface; The service address allocation proxy functional entity sends the address information to the service interface automation system. The service interface automation system receives the address information from the service address allocation proxy functional entity. The address information is used to indicate the address allocated for at least one interface type of a first network function; The service interface automation system generates an interface configuration for the first network function according to the address information.

19. A method for allocating interface addresses, characterized in that, The method includes: The service address allocation proxy functional entity sends a first message to the network management functional entity. The first message is used to request to continue using a first address allocated for an interface of a first interface type of a first network function; The service address allocation proxy functional entity receives a second message from the network management functional entity. The second message is used to allocate a second address for the interface of the first interface type.

20. The method according to claim 19, characterized in that, The first message includes at least one of the following: information for indicating the first network function, information for indicating the first interface type, or information for indicating the first address.

21. The method according to claim 19 or 20, characterized in that The second message includes at least one of the following: information for indicating the first network function, information for indicating the first interface type, or information for indicating the second address.

22. The method according to any one of claims 19 to 21, characterized in that, The second message is further used to indicate a valid duration, which is the duration for which the second address can be allowed to be used.

23. The method according to any one of claims 19 to 22, characterized in that, The method further includes: The service address allocation proxy functional entity sends a third message to the service interface automation system. The third message is used to request to update the first address to the second address.

24. The method according to claim 23, wherein The third message includes at least one of the following: information for indicating the first interface type, information for indicating the first address, or information for indicating the second address.

25. The method according to any one of claims 19 to 24, characterized in that Before the service address allocation proxy functional entity sends the first message to the network management functional entity, the method further includes: The service address allocation proxy functional entity receives a fourth message from the service interface automation system. The fourth message is used to request the allocation of the first address; The service address allocation proxy functional entity sending the first message to the network management functional entity includes: The service address allocation proxy functional entity sends the first message to the network management functional entity according to the fourth message.

26. The method according to claim 25, characterized in that, The fourth message includes at least one of the following: information for indicating the first interface type, or information for indicating the first address.

27. A method for allocating interface addresses, characterized in that, The method includes: The network management function entity receives a first message from the service address allocation proxy function entity, and the first message is used to request to continue using a first address allocated for an interface of a first interface type of a first network function; The network management function entity sends a second message to the service address allocation proxy function entity according to the first message, and the second message is used to allocate a second address for the interface of the first interface type.

28. The method according to claim 27, wherein The first message includes at least one of the following: information for indicating the first network function, information for indicating the first interface type, or information for indicating the first address.

29. The method according to claim 27 or 28, characterized in that, The second message includes at least one of the following: information for indicating the first network function, information for indicating the first interface type, or information for indicating the second address.

30. The method according to any one of claims 27 to 29, characterized in that, The second message is further used to indicate a valid duration, and the valid duration is the duration for which the second address can be allowed to be used.

31. A method for allocating interface addresses, characterized in that, The method includes: The service interface automation system receives a third message from the service address allocation proxy function entity, and the third message is used to request to update a first address corresponding to an interface of a first interface type of a first network function to a second address; The service interface automation system updates the first address to the second address according to the third message.

32. The method according to claim 31, wherein The third message includes at least one of the following: information for indicating the first interface type, information for indicating the first address, or information for indicating the second address.

33. The method according to claim 31 or 32, characterized in that, Before the service interface automation system receives the third message from the service address allocation proxy function entity, the method further includes: The service interface automation system sends a fourth message to the service address allocation proxy function entity, and the fourth message is used to request to allocate the first address.

34. The method according to claim 33, wherein The fourth message includes at least one of the following: information for indicating the first interface type, or information for indicating the first address.

35. A method for allocating interface addresses, characterized in that, The method includes: The service address allocation proxy function entity sends a first message to the network management function entity, and the network management function entity receives the first message from the service address allocation proxy function entity, and the first message is used to request to continue using a first address allocated for an interface of a first interface type of a first network function; The network management function entity sends a second message to the service address allocation proxy function entity according to the first message, and the service address allocation proxy function entity receives the second message from the network management function entity, and the second message is used to allocate a second address for the interface of the first interface type; The service address allocation proxy function entity sends a third message to the service interface automation system, and the service interface automation system receives the third message from the service address allocation proxy function entity, and the third message is used to request to update the first address to the second address; The service interface automation system updates the first address to the second address according to the third message.

36. A communication device, characterized in that, The device includes: a module for performing the method according to any one of claims 1-17, or a module for performing the method according to any one of claims 19-34.

37. A communication device, characterized in that, The communication device includes: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device is caused to perform the method according to any one of claims 1-17, or the communication device is caused to perform the method according to any one of claims 19-34.

38. A communication system, characterized in that, It includes at least one of the following: a service address allocation agent functional entity for performing the method according to any one of claims 1-7, a network management functional entity for performing the method according to any one of claims 8-13, or a service interface automation system for performing the method according to any one of claims 14-17.

39. A communication system, characterized in that, It includes at least one of the following: a service address allocation agent functional entity for performing the method according to any one of claims 19-26, a network management functional entity for performing the method according to any one of claims 27-30, or a service interface automation system for performing the method according to any one of claims 31-34.

40. A communication chip, characterized in that, Instructions are stored therein. The communication chip includes: a logic circuit and a communication interface. The logic circuit is used to execute computer instructions, and the communication interface is used for the communication chip to communicate with other devices or chips. When the logic circuit executes the computer instructions, the method according to any one of claims 1-17 is implemented, or the method according to any one of claims 19-34 is implemented.

41. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions. When the computer program or instructions run on a computer, the computer is caused to perform the method according to any one of claims 1-17, or the computer is caused to perform the method according to any one of claims 19-34.

42. A computer program product, characterized in that, The computer program product includes a computer program or instructions. When the computer program or instructions are run by a communication device, the method according to any one of claims 1-17 is executed, or the method according to any one of claims 19-34 is executed.

Images